Search Issue Tracker
Fixed in 2017.1.0f3
Fixed in 5.6.X
Votes
24
Found in
5.6.0f3
Issue ID
909145
Regression
No
Video player doesn't play when building on Windows for OSX
Steps to reproduce:
1. Open user attached project on Windows
2. Build for OSX, x86_64 Architecture (Don't build for x86, it is confirmed not to work by design)
3. Load the build on an OSX machine and observe video not playing
Expected result: Video player works no matter what platform you build it from
Actual result: If you build on OSX for OSX - it works, if you build on Windows for OSX, it doesn't
Reproduced on 5.6.0f3, 5.6.1f1, 2017.1.0b4
Notes: No regression test because Video player wasn't part of UnityEngine class below 5.6
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mesh.GetIndexBuffer() requires Mesh's 'Read/Write' flag to be enabled to get its index buffer data in Builds
- [Backport] [Sprite Atlas V1] Editor crashes when calling SpriteAtlasUtility.PackAtlases
- Deterministic builds have different files when built from the same project
- PlayerBuildInterface.ExtraTypesProvider no longer provides types to IL2CPP
- Touch input is reset in Device Simulator when Unity Remote is killed
mayasarii876
Mar 08, 2022 10:00
http://103.56.148.201/
http://103.56.148.201/newmpo
http://103.56.148.201/mpo17
http://103.56.148.201/mpomm
http://103.56.148.201/mpotower
http://103.56.148.201/parisklub
http://103.56.148.201/juraganslot
http://103.56.148.201/mpo500
http://103.56.148.201/mpokick
http://103.56.148.201/mpoyes
http://103.56.148.201/xyzklub
http://103.56.148.201/betmpo
http://103.56.148.201/ogslot88
http://103.56.148.201/hoki777
http://103.56.148.201/mpojuta
http://103.56.148.201/299slot
http://103.56.148.201/mpo188
http://103.56.148.201/mpogacor
http://103.56.148.201/mpo300
http://103.56.148.201/rgo365
http://103.56.148.201/kingdom288
http://103.56.148.201/wigompo
http://103.56.148.201/mpo8899
http://103.56.148.201/mpopelangi
http://103.56.148.201/mpo555
http://103.56.148.201/dutampo
http://103.56.148.201/klik368
http://103.56.148.201/388hero
http://103.56.148.201/19dewa
http://103.56.148.201/mpoxl
http://103.56.148.201/mpoas
http://103.56.148.201/mposun
http://103.56.148.201/qqslot
http://103.56.148.201/mposport
http://103.56.148.201/dewa234
http://103.56.148.201/mesinmpo
cozyurt_unity
Jul 17, 2020 13:55
kedi maması köpek maması www.patilimama.com
dkathrina323
Dec 08, 2019 18:53
This post shares the steps to reproduce the problem 'Video player doesn't play when building on Windows for OSX'. http://fixprinternotresponding.com/ I think we can solve this problem if we follow these steps. Each step is clearly explained. Thanks for the information.
Markusn
Feb 22, 2018 00:11
Confirm still an issue with 2017.3.1f1
RoutineAyhan
Feb 14, 2018 10:47
Still an issue on 2017.3.1f1 (only on cloud builds (H.264) not locally).
mobfish_cai
Nov 28, 2017 09:01
I can confirm that cloud build won't have this issue anymore when build for windows.
Last time I checked, Cloud Build use macs.
Eric-B
Nov 20, 2017 00:43
Still an issue in 2017.2.0f3. When building for Mac on Windows, video playing works if transcoding to VP8, but video playing does not work if using H.264.
cronkie
Nov 06, 2017 15:38
I'm having this same issue on Unity 5.6.3f2 although I am experiencing it on Mac OSX standalone building (not cloud) to Windows executable. I've made sure the files are in a universal format that will play on both Mac and PC (H.264) and when I attempt to build my project as H.264 and/or transcode them as H.264 in Unity, I get nothing but a black screen. VP8 is a work around but the quality is so low for VP8 that it's not an option for a shippable product. I'm getting close to ship and am running out of ideas on how to get high quality video files to play back. Help!
konistehrad2
Aug 11, 2017 23:34
Correction: this doesn't happen if transcoding is set to VP8. It _does_ happen if transcoding is set to H.264.
konistehrad2
Aug 11, 2017 23:17
Tested on 5.6.0f3, 5.6.3f1.
Presents as described. Interesting side effect: the `format` field in the YAML meta changes from 0 to 1 when the project is simply opened on Windows from MacOS. So the MacOS editor will force this value to 0. The Windows editor will force this value to 1. This does not happen if transcoding is enabled.