Toggle "Frame Replacement for Decode Errors" feature off.
In a QC critical enviroment, the red frame for decode errors was an incredibly helpful warning of potental corrupt frames in a file.
If this visual warning is replaced with a duplicated frame then the potential file issues become much harder to spot and/or more time-costly to verify.
If frame replacement is seen as a critically usful feature, please allow users to toggle it off/back to the old way.
With this new feature, Premiere updates past 13.0.2 become unusable in a QC environment/workflow, and users (us included) will be forced to switch to other software for critical evaluation.
Ryan
shared this idea
-
Paul Willis
commented
I echo this statement. This feature doesn't work properly and detects errors when non are present, leaving is wasting time and re-opening projects until errors stop.
Clips will randomly show this error while editing, making it impossible to work and export a master. The exact same files may have worked properly 10 minutes earlier, or be fixed by re-opening the project, using a different computer or just sometimes switching between Metal and OpenCL. There is no consistency to the errors or workarounds, we just have to keep re-opening projects until it stops.
Errors are detected at random on:
ProRes 422HQ
ProRes 4444
DNxHD 185x MXF
Photoshop files
We have 6 Macs all suffering from the same problem.
4x MacPro Trash cans - all 64GB - High Sierra 10.13.6
1x iMac 5k - High Sierra 10.13.6
1x MacPro 2010 - Nvidia TitanV - High Sierra 10.13.6
We're running a 10GbE network with Rockstar storage.
-
Cole Freedman
commented
Totally agree and this happens all the time where the "error retrieving frame" warning will appear and then the sequence will become black and unplayable, at least having media offline stresses the issue.