System: Windows 10 Home (with Fall Creator's Update 1709), PPro CC 2017 (reinstalled - more on that in a moment), MTS video files (which apparently have Dolby audio).
I have been videoing a monthly teaching series, whose sixth and last installment happened today (I had been putting them in the same project just to be tidy). Sometime in the last month I upgraded PPro to CC2018, and after I opened my project and let PPro "convert" it, it was having memory troubles while conforming the audio, with a variety of different errors happening when it would get partway through (sorry, I didn't keep notes of the wording, but I don't think that matters now). I simplified to only the newest footage, re-saved, rebooted, and tried opening again, and then while conforming the new audio my screen went black and never came back, requiring a hard shutdown. After reading of others having trouble with memory leaks in CC2018, and also noticing that I no longer had an export preset I had made, I decided to re-install CC2017 so that I could just finish this project before braving the new version.
Once the CC2017 version of PPro and Media Encoder were installed, I could open my project, but I got: "Dolby Codec must be installed to use this feature. Clicking OK will install and enable this codec for immediate use." I clicked OK, but my media files merely changed from "pending" to "offline". The Properties box says, "Offline: Media Type Mismatch". When I importing the new media file, I get video only, as if the file didn't even have an audio track. Properties successfully gives the video specs but doesn't mention audio. I deleted the Media Cache, Media Cache Files, and Peak Files folders, but I got the same behavior.
This is clearly related to the Dolby codec licensing, that PPro would now be dependent on the OS native codec. I guess I lost Dolby's codec when I upgraded and then downgraded again. But that leaves three burning questions:
- When that message comes up at load time, offering to install a codec, whose codec is it talking about, and why doesn't it actually do anything?
- I have Windows 10, so why can't it see the native codec? When I simply double-click on one of the files, something called "Movies & TV" (which looks very much like part of Windows, not a third-party player) plays the video and audio just fine. So it seems that the native codec is alive and well, so what's going on?
- What should I do now? CC2018 started the process of conforming audio and put a couple of .cfa files in Media Cache Files, so it apparently found the native codec. But it couldn't conform a 53-minute stream without crashing my PC in bizarre ways. Granted, I only have 8GB of RAM, but that has never caused me any trouble before.
26
Replies
AdChoices