Inspiring

Question

Dolby codec issue on Windows 10

Forum|Forum|8 years ago
December 31, 2017
5 replies
9016 views

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.

This topic has been closed for replies.

Ji-

Participant

I solved a similar problem with the Dolby codec at Premiere CC 2017 using Audition CC 2017.
I imported the clip into Audition and then exported the sound to wav.
I imported Wav into Premiere CC 2017 and paired it with the video on the timeline.

OsakaWebbieAuthor

Inspiring

I finally got the courage to try installing CC2019 to see if the memory leak has been fixed. (Even though I unchecked the box "Remove old versions", it's still a little scary.)

It took forrrrrever to conform (perhaps a half hour or so for a 53-minute video), but PPro's memory usage did not rise while conforming - in fact, it gradually reduced a little bit! And nothing crashed. So it appears that the "ppro-using-the-windows-codec" memory leak has been fixed in CC2019.

NangaParbat

Known Participant

@OsakaWebbie well I have exactly the same problem you described. I also updated to Premiere CC18 during a running project (with *mts-videos and dolby 5.1). That lead to your described errors and I went back to CC17. Now I also have lost all media or at least they can only be reconnected again with loosing audio. Have you by time found a solution for this? Would be great, thanks a lot!

OsakaWebbieAuthor

Inspiring

No, I'm sorry, I haven't heard any new news. The precious Dolby file is lost when you upgrade to CC18, and if you find CC18 unusable because of the memory leak and reinstall CC17, you won't get the codec file again because of some licensing issue. If you have a backup of your computer before you upgraded to CC18, get the codec file from there. I previously linked the forum post that has the path, but here it is again: Re: Premiere 2018 - A Disaster!

If you don't have a backup, look for a coworker/friend/etc. who uses CC17 (or earlier version), and do two things: (1) warn them not to upgrade until Adobe fixes the memory problem, and (2) copy their codec file. I don't think it's legal for me to post my copy of the file (if it was no big deal, Adobe would still be including it in the CC17 installation), but if you can find it internally somehow, that's probably okay, as it simply restores your installation to how it was before CC18.

NangaParbat

Known Participant

Well if others are facing this problem too:

I can confirm what OsakaWebbie wrote to the missing dolby-Licence. In my case it helped with the following steps:

Get the Dolby-file from someone else as described in the previous posts
AND rename all folders, where your video-footage (In my case *.mts Sony AVCHD) is located. Then relink them in Premiere.

Good luck!

M

mattd53033019

Participant

I solved the problem! in regards to getting the Dolby codec to work in premiere pro 2018 on a windows computer

I contacted Microsoft directly via live chat as I found Adobe was really not being helpful, just giving the same rehotoric that windows 10 should support the codec.

The solution is to update your audio drivers.

Right click on the start menu

Select device manager

select sound, video and game controllers (or sound drivers)

From your list of drivers, right click on each one and select "update driver"

Select search automatically for updated driver software.

Restart your computer after the new drivers have been installed

And that should fix the issue for you.

OsakaWebbieAuthor

Inspiring

Apparently that worked for you, but on both audio drivers I have, that action said, "The best drivers for your device are already installed."

S

sl3p

Known Participant

I'm having the same problems, where I can't open any earlier project, or create a new project as the audio file is missing.

These are the error message I get when I try to open a previous project file (2017.1.2 release)

And if I try a new project file, I'll get the 2nd image, but will have the problem of not finding any audio file

These are things I tried that haven't worked

1) I tried updating the audio drive and it didn't work.

2) Currently, my new computer is on the PoweSpec G351, using Windows 10 home

(it has the latest video card and powerful cpu chip so doublecheck to know it can handle anything hardware stand point

3) (I have the PP CC 2017.1.2 release installed not 2018

4) I even tried the create a common folder trick No Audio after update? Premiere Pro CC Import Issue Fix! | Film Learnin - YouTube

Anyone have any other suggestion or solution to the problem?

E

excited_Genie16B8

Legend

What specific version of 2017 is installed?

OsakaWebbieAuthor

Inspiring

I currently have 11.1.2 (22) Build. I don't know what flavor of 11 I had before I upgraded to 12.

E

excited_Genie16B8

Legend

Yep, that's a problem. That version will not use the Windows Dolby codec.

You can try upgrading to 2018 with the caution below, or try installing 2017.1.4.

To get around the memory leak, you will need to import only a few clips at a time. Let them conform, save the project, close PP to release the memory. Open the project again and repeat as necessary.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded