| So,
Okay, couple things to hit on. First of all, the clearing of the cache, dumping of preferences, and simply rebooting the machine is all great advice as a starting point. Do those things before any others.
Preferences alt+Shift when opening program Media Cache: Edit>Preferences>Media. You could try cleaning the database but in extreme cases you can just trash your whole cache folder, and have PPro recreate it next launch (note that might not be sanctioned advice from the likes of Todd Kopriva, who is awesome).
You mentioned Prores and Cinec. First, Cinec. While it was an interesting experiment, I have not been able to rely on it for Prores media conversions. First, it’s incredibly slow. Second, it creates bad media. Not every time, but often enough to be untrustworthy. It is a hack, not a supported solution.
If the media in question came from Cinec, well, I’d say try something else.
But lately there have also been a few Prores related issues, and I’m wondering if this is the case.
But you’ve also mentioned that you were creative DnXHD files. So I do’t know if that is an issue. CC handles DnXHD itself, whereas (from memory of the CS6 days) the DnX codecs had to be installed at the system level. That is something to look at. If you were using this codec in a Quicktime MOV, then Quicktime itself is something to look at.
carey Thanks Casey,
I realize everyone likes to get tons of info, was just looking to see if anyone has experienced this type of sudden change. The reason I didn't include all the codec info, etc is because it's been business as usual, then suddenly it stops importing correctly which is why I doubt it is any format or codec issue.
However - I'm using premiere pro version 6.0.5 and updated yesterday after experiencing issues but no change. I work on a PC, Windows 8.1. My routine has been pretty simple. I've been working in AE 6, outputting files to DNxHD, importing in to premiere and normally no problem. It may also import a file that didn't work on a second try or after restarting premiere.
In my mind, clearly a premiere issue. I did also do some conversions to ProRes using CINEC, also a standard procedure and it's had same symptoms with both before and after.
Eric
|