Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2018.2.0b8
Issue ID
1051638
Regression
No
[Recorder] Invalid path in Movie recorder throws Encoder error
To reproduce:
1. Download attached project "newRexTest2.zip" and open in Unity
2. Open "SampleScene" scene
3. Go to Window > General > Recorder > Recorder Window
4. Set the Options as shown in the attached screenshot
5. Click on "START RECORDING" button
6. Observe that Console starts spamming lots "Unable to encode video frame" errors
7. Press "STOP RECORDING" button
8. Observe that Console prints error:
"VideoMediaEncoder::~VideoMediaEncoder 8 encoding errors.
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)"
Notes:
- This issue reproduces only on OSX
- Errors that are occurring in Windows are shared in Comments section
Reproduced on Unity 2018.2.0a3, 2018.2.0b8 and 2018.2.0b11
Could not reproduce this issue on Unity 2017.1, 2017.2, 2017.3, 2017.4, 2018.1 and 2018.2 because for some reason Recorder becomes corrupted
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- TextMeshPro InputField view is not updated when OnEndEdit is triggered
- The "Open Frame Debugger" button in the Game View toolbar not only opens the Frame Debugger window but toggles between enabling/disabling the Frame Debugger when pressed
- HDRP Water renders black when the PrecomputedAtmosphericAttenuation is set to zero
- [FrameDebugger][WebGL] Frame Debugger does not display any data when running WebGL build
- Selected Sample Stack remains showing in the Profiler when the frames are cleared and there is no data to select
Add comment