There have been times when we have loaded old project with AVCHD in them and Premiere has not automatically activated the codec and caused problems. We find the best thing to do is start a new project and load an AVCHD clip. When you first start using Premiere Pro CC2017 you have to activate the Dolby codec again even if you had a previous Premiere installed. The following are things we have noticed here at DVC To reset preferences and plug-in cache at the same time, hold down Shift-Alt (on Windows) or Shift-Option (on macOS) while the application is starting. Workaround: To fix this issue, uninstall Adobe Premiere Pro CC and Adobe Audition CC, and reset Preferences when you install the application again. I ssue: After upgrading to the latest release, you could be unable to edit any audio file using Audition from the Premiere Pro timeline. Dynamic link between Premiere Pro and Audition does not work For more information, see Troubleshooting errors related to clips displayed as red and white checkers with older projects that use Lumetri effects. Workaround: Remove the Lumetri effects and reapply the effects once again. Issue: When viewing old projects that use Lumetri effects after upgrade, you could see a red checkerboard display. Red checkerboard error seen after upgrade with older projects that use Lumetri effects For more information, see Troubleshooting linking and importing errors with AVCHD (MTS) and MP4 files after upgrading to Premiere Pro CC. Also check if this issue is related to your Creative Cloud(CC) activation. ![]() Workaround: Clean the media cache database folder. If you still see an issue, change the file directory where the AVCHD files reside and check if the issue gets resolved. Issue: When you try to import AVCHD (MTS) and MP4 files in your project using Premiere Pro CC, you could get an error message which says, “The file has an unsupported compression type.” This error could also be displayed with other Adobe audio and video products including After Effects and Media Encoder. The following issues are confirmed by Adobe on this web page: –november-2016-.html Imported clips have no audio after updating to the latest release not fun with 1,000+ subs.Īnyway, while not detrimental to my project anymore, I would still like to know the answer to this problem, especially since from what I have found in other sources is that the bluray standard does not have this gap issue, that it is only specific to Encore.The following is a list of known issues in the Premiere Pro CC 2017 (November 2016) Release. ![]() ![]() I was able to fix the above error message accidentally, just happened to randomly find a pair of subs too close, and when I moved them away, the error message, shown by the triangle with the exclamation mark, went away (Yes, I ran the fix gap automatically when right-clicking on the triangle, but still got the error above afterward).Īnyway, the project is error free-ish now, (not sure why it didn't automatically fix the single gap issue) but I have the painstakingly task of now fixing the synchronization between the audio and the subs, as it is all messed up since the import. This doesn't help too much when dealing with over 1,000 subs on the track, but at least I know what to look for. The ends of two subs will show at least one of the subs being red. ![]() Well, it doesn't help much in this project, but finally found what it looks like when there is an error with subtitles.
0 Comments
Leave a Reply. |