Search Issue Tracker

Won't Fix

Votes

0

Found in

5.1.6

Issue ID

UUM-139280

Regression

No

Errors are thrown when recording Movie and another type simultaneously when both output paths are with 'Assets Folder' type

Recorder

-

Steps to reproduce:

  1. Create and open a new project
  2. Install the Recorder Package
  3. Open the Recorder window
  4. Add "Movie" and "Image Sequence" recorder types on the left
  5. Set both recorder Output File paths to type "Asset Folder"
  6. Start recording, then stop recording
  7. Observe the Console

Actual results: Two errors are thrown

Expected results: No errors are thrown

Reproducible with versions: 4.0.0-pre.5 (2023.1.0a1), 5.1.6 (6000.4.3f1, 6000.5.0b4)

Tested on (OS): Windows 11 Pro (25H2)

Notes:

  • Not reproducible when recording only "Movie" type or only "Image Sequence"
  • Only reproducible when both path types are anything but "Asset Folder"
  • Errors read:

** WindowsVideoMedia error 0xc00d36c4 while reading C:\Users\[name]\Desktop\Test650b4\Assets\Recordings\Movie_006.mp4
** Error while reading movie: C:/Users/[name]/Desktop/Record/Assets/Recordings/Movie_001.mp4
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

  2. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.