BUG REPORT - IMPORT ERRORS FILMIC PRO SUBSTITUTION RECURSION
The HEVC files generated by Filmic Pro capture at 30fps, 4k 2160P, FILMic Extreme, 10-bit LogV3 [shutter locked to 60Hz or Auto] when imported to Adobe Premiere Pro Version 15.2.0 Build 35 are generating thousands of "error reading frame *** @ xx:xx" substitution/recursion events on import and when either playing back the source clip itself or when embedding it in a sequence and playing that... Using Adobe Media Encoder to transcode the original Filmic Pro output into Apple ProRes 422HQ renders editable/usable files and is an acceptable workaround in the short term but obviously far less than ideal. I've searched the Adobe Premiere Pro support community in vain for anyone else experiencing the same problem with FilmicPro files on import and drawn a blank - is this issue a current "thing" or is it just me? "Help!" [Running WIN10 enterprise on a muscular HP workstation with an NVidia GTX1660Ti GPU running NVidia's Studio Driver Ver. 471.11 with Mercury Playback Engine GPU Acceleration enabled in project settings - no known issues importing 4K DolbyVision HEVC video files generated with the native iOS camera app or 4K 2160P files made with MAVIS - this problem is specific to FILMIC PRO]...
Auteur Savant commented
"EUREKA!" Problem solved... As it happens, it's all Cinegy's fault... to wit, the plugin "TurboCut" employing the Daniel2 codec for Adobe CC editing/encoder apps [see link below]... uninstall TurboCut [and for added good measure, clean your registry with something like CCleaner] and you're laughing! Additionally, as far as I can tell, that plugin was also causing substitution recursion "frame not found at time xx:xx" errors in other PremierePro workspaces/modules as well - specifically, graphics on importing Adobe animated titles/subtitles in Premiere Pro not to mention breaking Media Encoder on every attempt to transcode FilmicPro capture.
Curiously, TurboCut will work as designed on some platforms/installations without incurring substitution recursion errors on import/playback of FilmicPro capture or interfering with Media Encoder [and worth noting, if anyone else is having problems with this error, it occurs independently of which frame rates/codecs/resolution your FilmicPro clips were captured, it's all down to TurboCut]. So, to reiterate - although this problem has manifested on two desktop Windows workstations it hasn't on a laptop installation which is otherwise identical as regards operating system/Adobe apps. Go figure.
Well. There it is.
CINEGY TurboCut/Daniel2: https://www.daniel2.com/index.php/products/turbocut