as far as I know Adobe Premiere will not support anymore Dolby codec.
The only way, I think, is a thirdy part codec like Minnetonka or other.
Hope this will help though it is not a good new.......
Merhaba ; ben Erol (London Yapım Studios)
Selamlar Görüyorumki Bu konuyla ilgili şansızlık yaşayan bir tek 3-4 kişiyiz.
CC 2018'e güncellendim. CC 2017 projemizi CC 2018'de açtığımda, tüm MTS video dosyalarım çevrimdışı bulundu.bunun nedeni CC 2018'den Dolby Codec'i eksikliğinden kaynaklanıyor.AC3 .MTS ses codec bileşenini seslerini okuyamıyor. Bu şekil ses kullanan tüm 2018 kurulumlarını etkiliyor ve açmıyor. Premiere Pro cc,After Effects Cc, Media Encoder cc,Audition. Ama nedense CC 2017 de tamamen iyi çalışıyor hayırdır bunun içindemi para talep edeceksiniz bizden..
(High Sierra) iMAC kullanıyorum ve bütün bilinen yöntemler yollar hacklemeler hepsini denedim ama olmuyor bilen yomu acaba
Video dosyasını sequence yüklediğim zaman Violet renginde oluyor ve hiç bir şekilde ses dosyası gelmiyor lütfen update yapın ve sorun giderin yada fit verin.
Kimse varmı bilen acaba neden ses dosyası problemi yaşadığımızı ve düzeltme yöntemi olan?
For me, no, unfortunately it didn't work. My "dolbycodec.framework" was never deleted. I didn't erase any of my CC 2017 apps when updating to CC 2018. I even opened my time machine backup and found that "dolbycodec.framework" file from a September backup and overwrote my current one.
The strange thing is that a friend of mine has CC 2018, Mac High Sierra like me, and tested one of my MTS video files on his Premiere 2018. For him, it imported fine with audio and video. We've been trying to figure it out together and can't seem to figure out the mystery of why it won't work for me.
Adobe CC2018 uses native O.S. support for dolby.
This means that you can import Dolby if your O.S. manage it.
But if you want encode (output) dolby audio, you need external supports like Minnetonka or TMPGenc or others.
Try to "google" into Adobe support and you will find usefull informations.
Hope this will help
I am hunting the Apple ProRes 422 in the update as well... Anyone see it? Am I just missing it?
Found it! Never mind!
At least they finally acknowledged it - still don't see why they couldn't make the previous version available that does include the dolby support
If you install it though it does give you the 2017 AME too, which has the Dolby options. Then you can run 2018 & 2017 alongside each other. The ProRes codecs are found under the GoPro presets at the Video Codecs dropdown...
1 person found this helpful
Sorry for the difficulty! Try one of these suggestions if you've lost Dolby functionality:
1. Your simplest and best bet is to recover your CC 2017 apps as they were before you installed CC 2018. See if you can use Windows Restore to roll back the state of applications on your computer to before that time. On a Mac, you'd use Apple's Time Machine.
2. If you can't do that, then do you have a system backup or image from when you had CC 2017 installed, or perhaps it's installed on another machine? You could possibly use that backup together with the CC 2017 direct download links to get back to where you were before. At a minimum, you'll need both the Premiere Pro and Adobe Media Encoder apps.
3. If neither of those strategies recover a working CC 2017 for you, then you could try moving forward with CC 2018. You could use a third-party utility like Handbrake (a free open-source video transcoder) to convert your MTS/ACS files. Rename the files and reimport them into Premiere Pro. Then clear your media cache.
4. If none of the above work, then maybe consider upgrading to Windows 10 while it's still free, and press ahead with CC 2018 (if you're concerned about Windows telemetry, that's easily handled). Meanwhile, for Mac users, macOS upgrades are always free... Windows 8.1 or above and macOS 10.11 or above contain native support for Dolby decoding functions. Again, rename the applicable files and reimport them on your new setup. Then clear your media cache.
5. If you can't upgrade your operating system, can't move forward with CC 2018, can't go back to CC 2017, and are genuinely stuck with a project caught in the middle – and none of the above solutions work for you – then you could try contacting Adobe Customer Care to let them know and see if they can help.
6. Moving forward, when upgrading Creative Cloud apps, use 'Advanced Options' in the Desktop app to retain older CC versions rather than the default behavior, which is to remove them.
Hope that helps!
no — give us a solution.... we are all facing our deadlines
don't tell us to download win10 —
Moderator Note: Warning! Do not use profanity. It is against our guidelines.
I solved my own problem, although I am not sure exactly what did it. I mentioned that I cleared all my Media Cache and Peak files, which didn't solve the issue. Yesterday it did.
The one thing I did differently this time is that I went through my plugins folder: Library>Application Support>Adobe>Common>Plug-Ins>7.0 and purged all my 3rd party plugins that I no longer use. I had quite a few of them. I also deleted the 3rd party program FX Factory. I did this, cleared my media cache and peak files, imported my MTS file in CC 2018 and it imported with video and audio.
This is absolutely ridiculous.
Hi rmc, this is an issue with High Sierra not playing nicely with AME. I know because my laptop, running Sierra, transcodes these files fine. They can even be imported to Premiere 2018 on my High Sierra desktop with no audio issues whatsoever.
Wish Adobe would test on the newest software - on one of the two huge platforms they serve - to ensure things like this work out of the box. And of course we can't have the original 2017 files with the Dolby codecs working.
From having met some of the engineers at NAB the last five years ... that's a Mac-centric group, with also pretty decent PC experience ... and running every Mac rig you can think of.
So ... my guess is it's run on goodly variety of Macs before shipping and yes, newest OS. Of course, even the newest Mac "tower" has what, a five-year-old design on the mobo? They have announced they're going to develop a new mobo but I'm not holding my breath.
Eh, I'm running a two year old machine on newest OS. And this problem seems
widespread among Mac users, enough to have a few decent threads about it.
Tells me testing mightve overlooked certain configurations. Oh well,
hopefully a fix comes soon!
On Sun, Nov 5, 2017 at 5:51 PM R Neil Haugen <email@example.com>
Yea, but ... have you thought that you and some others may be having it, but thousands of others with identical or nearly identical may not? Which with so many of the issues like this is the case.
So when it's only a small subset of a small subset of the total user base, finding the 'cure' can be a bit of a puzzler. And that's why it doesn't get caught to begin with ... they may easily have had a rig just like yours but didn't exhibit this behavior.
3 people found this helpful
I got a solution on mac
I have 2 Mac I update just one to the new CC 2018 and have the same problem that all of u
after fight for days format install and do everything
what I do was,
Close all adobe aplications
copy the dolbycodec.framework from my other computer to the updated Mac on
and works my both versions of premiere CC 2017 and CC 2018 Worked Fine
NOTE: premiere CC 2018 works but a bit slow importing files MTS, after been imported everthing works perfect
I don't know if my file works in other computers if smb need leave a mail
Sorry if my English is not perfect
Thanks; any chance to do the same in macOS?
Sorry, we can't do that.
People can't really share licensed software components outside of an official distribution; it's not legal, nor a good idea.
See if you can get it from one of your previous system backups.
And check the #13 reply above for more suggestions on solutions for this issue.
it's not legal, nor a good idea
Maybe it is legal to throw awaya vital component that a lot of customers rely on, but is it a good idea? Do you find it fair? We'r all working here, nobody has time or money to waste. Now we're forced to find a third party solution for a thing we had already paid for, all because the Dolby encoder disappeared in a blink of an eye without notification. This thing doesn't make any sense.
Have to agree. Maybe we could get special permission from staff on this
forum? Since this solution is highlighted as a fix in another
thread, I don't think it's unreasonable to ask for this file.
2 people found this helpful
Folks, you have two companies involved here ... Adobe was just a licensee of a codec owned by Dolby Laboratories. Dolby owns ac3 outright. And has the right to license all usage.
Adobe can't give away something owned by someone else ... period.
By the way, neither company has said anything publicly about this, not one little word even. So it seems likely there's a breakdown in a usable agreement over licensing that property ... the Dolby ac3 codec.
And ain't none of us know what the breakdown was. Or probably will ever have a clue.
Is it a royal pain to many of us users? Oh, yea. Royal.
So is Apple never allowing their ProRes codec to be created on a PC. I get by fine with Cineform & DNxHD/R, but for many, it would be handy if they could export in ProRes on a PC. Nunh-unh. Not no way not no how.
2 people found this helpful
Nobody here can legally share those files, exactly for the reasons that Neil mentioned.
Furthermore, it's not a good idea because you should never install software files from unauthorized or untrusted sources onto your computer, at least if you care at all about your own security and privacy.
What happened is indeed unfortunate and was unexpected, and many of us here have spent a great deal of time trying to help out fellow users. The only external sources that could legitimately and safely provide those files are Adobe or Dolby, and clearly they are no longer able to.
This is why the suggested solution, if possible, was to pull those files from another system you have, or from your own computer's backups, or use Windows Restore or Time Machine to roll back the application state of your machine.
(And there are other possible solutions suggested on the related Forums thread shared above.)
Going forward, please consider retaining your previous versions of tools when upgrading, rather than the default behavior to remove them. With virtually any CC/CS Adobe app, you can have multiple versions installed on the same machine... (For video customers especially, this is considered a good practice.)
However, you have to explicitly tell the CC Desktop app to do this by unchecking the 'Remove old versions' box under the advanced settings of the update dialogue.
what if I already updated and removed my preferences? This is ridiculous
1 person found this helpful
How is this our problem? Adobe is one of the biggest software houses on this planet, and we're paying it every month. We should just have the same instrument we used to have, or at least a notification and some alternatives (also: a discount for a third party app, since this thing has been removed under our feet).
Well, we seem to be going around in circles... Have you actually read through the thread above, which offers several possible solutions that could work?
If you can't restore the previous functionality you had using the CC 2017 direct download links, or by using backups or a system rollback or from another computer, and if you don't want to upgrade to Windows 10 for free, then have you tried using third-party tools such as Handbrake? (also free)
If you recommend to update to Windows 10, you did not read everything either. I'm on a Mac.
Even if u update 10.13 mac os and have native Dolby Decoding support u cant play audio in premiere cc
I know quite a few Mac folk doing just fine ...
As I stated several times, I need encoding support, not decoding.
Adobe is forcing us to buy additional software after we paid for the CC for years, and without even giving a warning about the upcoming removal of the feature. I'm sure everybody can see I'm not crazy if I complain about this. Adobe makes the best software, but is not cheap: if I lose a feature, I expect a quick, painless solution.
You didn't state that several times. And if you continue to need a particular functionality that was unexpectedly removed, then continuing to use CC 2017 is one recommended option.
The situation is definitely unfortunate but it's really unusual for Adobe – in the past when there's been a significant change in support or requirements for a major tool, they'll give plenty of notice well in advance.
So something happened here that was exceptional and out of the norm, and apologies for the trouble you're going though.
That said, as fellow users on these forums, we're here to help try to find solutions and workarounds. Many of us who are unaffected are spending a lot of our own personal time here doing that.
I have a two year old iMac that has Adobe CC installed since I purchased it. My Premiere imports .MTS files with after updating to Premiere 2018.
Just installed High Sierra on a newer Mac Book Pro and then installed Adobe CC for the first time on this Mac Book and Premiere won't import .MTS files with audio. This is what I get. Clicking OK doesn't install the codec or solve the problem.
I'm going to attempt to copy the dolby codec from my other Mac and see if that fixes it.
I'm confused because I don't have this issue with 2017 version as everyone says, but I do have the problem with 2018 ... but I have Win 10, version 1709 OS Build 16299.64 ... so my 2018 version should be allowing me to input ac3 audio... RIGHT? but no go. I've google it to death ... can't figure this out.