Skip to main content
Participant
September 22, 2013
Answered

Premiere Pro CC, Dolby Digital License missing for MTS / AVCHD audio import?

  • September 22, 2013
  • 7 replies
  • 57068 views

Hi,

I'm running Premiere Pro CC on Mac 10.8.4 importing MTS files captured on a new Panasonic V720 Camcorder that records MTS / AVCHD files.

When I add the files to my project or drop them onto the timeline, the video appears fine but there's no audio and I get the warning message:

"This installation does not have a license to decode Dolby Digital audio".

I've tried switching from 5.1 to 2-channel audio on the camera in case that was the issue, no change.

The file plays fine on the mac with VLC player or MPlayer - mplayer is decoding audio with the FFmpeg AC-3 codec. I've imported MTS files created with other cameras (but presumably with different audio codecs) into Premiere fine with my current setup.


Any suggestions for getting this video and audio to work correctly?

Thanks!

This topic has been closed for replies.
Correct answer winned49044734

Hi everyone,

I had the same problems concerning .MTS files with the Dolby warning. The solution is simple, and it would be wise for Adobe to communicate this more clearly:

Apparently our institution got two license codes. In one you do have Premiere pro, but not a full working version! The problems you all have are in line with this code. I also had problems with not having MPEG2 output. So I went to look further on the net and discovered this about the two license codes... Now, with the new code I have MPEG2 output, and I can handle .MTS files.....

I hope I helped you all with this!

7 replies

epixilated
Participant
March 26, 2019

I have found that if I double click inside the project panel and then navigate to my video folder, the files it imports will have no audio. If however, I import by using the media browser, the files come in with audio.

Mike

Participant
December 18, 2020

I was having the same problem with Dolby audio and I tried a fairly quick work-around to this issue. I just imported the video/audio file into Microsoft Movie Maker and exported it out as an mp4 audio only file. Then I simply imported that file into Premiere and synced the audio to the original video. Easy. Good luck to anyone else with this problem.

Participating Frequently
November 3, 2017

Kevin,

Any news on this issue please? Would be great to know if I need to track down my CS6 discs or find a way to troll back to previous CC from Premiere (is that even possible?)

Thanks in advance

Matt

R Neil Haugen
Legend
November 3, 2017

In your CC Desktop app, you should have the "addendum" of 2017, the ".4" version, updated from the last public release as the new one has the Dolby codec discontinued. As well as CS6, and the original CC.

From ProDesignTools.com you can get further download links to versions ...

Adobe CC 2017 Direct Download Links: Creative Cloud 2017 Release | ProDesignTools

Neil

Everyone's mileage always varies ...
Participating Frequently
November 3, 2017

Cheers Neil - looks like the version you mention is CC (2017) 11.1.4

Is that right? Is the new titler present in this version of Premiere CC?

Either way I'll roll back to that for now - do you know if later releases will fix this issue? I'll refrain from updating until it is... Shame as all Sony AVCHD camera users will be affected until it's resolved.

Thanks for the help

Matt

Participating Frequently
November 2, 2017

HI Kevin,

Media is .MTS,. Properties within Premiere:

File Path: Z:\AVTEAMUK Promo Winter 2017\00055.MTS

Type: MPEG Movie

File Size: 115.22 MB

Image Size: 1920 x 1080

Frame Rate: 25.00

Total Duration: 00:00:43:04

Pixel Aspect Ratio: 1.0

VR Projection: None

System HPZ820 workstation Intel Xeon CPU E5-2695 v2 (2 processors), 32GB RAM, NVIDIA Quadro K4000 and K5000. Windows 7 Pro with SP1.

Adobe ID is (personal id removed by moderator. Please do not post sensitive info, this is an open forum)

Thanks

Matt

Participating Frequently
November 2, 2017

.MXF files are fine, only the .MTS footage I've shot is causing problems

Thanks

Matt

Kevin-Monahan
Community Manager
Community Manager
March 29, 2015

Hello Banta-Mug,

Any suggestions for getting this video and audio to work correctly?

I looked up your details and it appears that you were a university student at the time you posted this issue. I'm going to assume that you were working on an enterprise installation of Creative Cloud, but not the one with the correct video codecs (there are two different kinds of installations in an enterprise environment, like a university). If you are still using the same version, please contact your university's IT department and acquire the correct installation of Creative Cloud.

That should solve this issue for you and others on this thread.

Thanks,

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
winned49044734Correct answer
Participant
July 8, 2014

Hi everyone,

I had the same problems concerning .MTS files with the Dolby warning. The solution is simple, and it would be wise for Adobe to communicate this more clearly:

Apparently our institution got two license codes. In one you do have Premiere pro, but not a full working version! The problems you all have are in line with this code. I also had problems with not having MPEG2 output. So I went to look further on the net and discovered this about the two license codes... Now, with the new code I have MPEG2 output, and I can handle .MTS files.....

I hope I helped you all with this!

Kevin-Monahan
Community Manager
Community Manager
March 29, 2015

Hi W.Werd,

I had the same problems concerning .MTS files with the Dolby warning. The solution is simple, and it would be wise for Adobe to communicate this more clearly:

Apparently our institution got two license codes. In one you do have Premiere pro, but not a full working version! The problems you all have are in line with this code. I also had problems with not having MPEG2 output. So I went to look further on the net and discovered this about the two license codes... Now, with the new code I have MPEG2 output, and I can handle .MTS files.....

I hope I helped you all with this!

It appears you have an enterprise installation of Creative Cloud. Your IT department did not install the correct copy of Creative Cloud, the one with the video codec licenses. As you discovered, there are two. One with the video codec licenses and the one without them.

I assume that if others on this thread are experiencing this issue, they are might be enterprise customers. I am not certain, though, as no one else mentioned that they are in an enterprise environment. It's certainly something to check. This info has been shared on the forums in the past, but perhaps it could be better communicated, so thanks for the feedback.

Thanks,

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Participant
June 27, 2016

Hi there,

I'm not using an enterprise license (just student) and I'm having the same issue. PLEASE help!

Participant
February 23, 2014

I'm having similar problems with my Premiere Pro CC.  Interestingly enough I can export a 5.1 audio edit and the resulting file plays in 5.1 just fine through VLC Player, but while editing in Premiere Pro CC, all I get is stereo.  Same is true with Audition...

I'd appreciate any thoughts.  Thanks.

AviX1120
Participant
February 23, 2014

From all the research I did that night about this - DOLBY is not natively supported in CC

http://www.minnetonkaaudioshop.com/epages/MASIShop.sf/en_US/?ObjectPath=/Shops/MASIShop/Products/UDDCC

double check me

Known Participant
November 3, 2013

In short after reading LOTS of people complaining like you have, like I have like probably about 1 million people who own AVCHD cameras have that the most used format to shoot on for home /semi pro users is AVCHD and Premiere... get ready for this... take a deep breath.... DOESNT SUPPORT ITS AUDIO FILES. Its apparently licensed by DOLBY and you ahve to contact and minktonka company and pay.... really sit down first... take another deep breath... they want $300 for the plugin to make it work.

So Adobe have shafted.... is that a polite enough word... its customers who just want to play their files - not even encode the project to dolby digital - just play and edit their stuff. No even though you own that camera which only lets you shoot in that format and even though you are stuck wanting Premiere, adobe thinks that for the large monthly sum the world can go sit on its finger before they will sort this out.

Charming huh.

Adobe are you listening..... hello Adobe... have you gone mad Adobe... hello. Earth calling Adobe.

As someone pointed out you can play these files on quicktime, media player... so seems apple and microsoft PAY THEIR LICENCES ON BEHALF OF THE USERS OF THEIR PRODUCTS. Adobe must either be skinflints or maybe a nephew of theirs owns Minkytonkatoy firm who are selling that annoying plugin. Ever heard of download sites... cough cough.

Legend
November 3, 2013

you ahve to contact and minktonka company and pay.... really sit down first... take another deep breath... they want $300 for the plugin to make it work.

That only applies if you want 5.1 Dolby Digital export.  The plug-in has no bearing on supported formats for editing.

Known Participant
November 3, 2013

I hear you but bear in mind I am a veteran 15 year Premiere user and PC engineer. I dont say this stuff lightly. After not being able to load the AVCHD videos I found out that the plugin is not only required to Decode but to Encode. I found this by searching the forums and reading up. Also I went to Minnetonkas website where it comnfirms that it is required to decode and encode.  Prior to this I have installed and run the cleaner and reinstalled and it still happens so the lack of the codec is there, people on the forums are blasting about it, so unless I hear it from on high from Adobe, I suggest maybe you dont know much about this... or can  you explain more please. Many thanks.  At this point it looks so bad im going to put back on CS5 and that worked fine taking in AVCHD. Never had an issue.