Skip to main content
swmp
Participant
October 18, 2017
Answered

Premiere Pro CC 2018 - AVCHD no audio

  • October 18, 2017
  • 14 replies
  • 33820 views

I installed the 2018 version and when importing AVCHD clips (via media browser) no audio tracks where recognized.

In the 2017 version (runs parallel) the import works without any problems.

As with the latest updates, there is also the problem that when opening projects of the previous version the AVCHD clips are all offline.

The old tried and tested tricks like delete mediacache, rename clip folders and rename common folders do not work.

I can re-link the clips, but then get the error message that the audio tracks are faulty and can not be imported.

Any suggestions?

    This topic has been closed for replies.
    Correct answer Trent Happel

    Adobe Creative Cloud has moved to native Operating System (OS) support for Dolby Digital decoding (reading Dolby files) and is no longer providing support for encoding (writing) Dolby Digital and Dolby Digital Plus sound formats in the current and future releases of Creative Cloud.

    Dolby audio decoding

    Both Windows and OS X operating systems (Windows 8.1 or above and Mac OS X .11 or above) contain native support for Dolby decoding functions. Please update to the latest version of your operating system.

    Dolby Audio decode support for Windows operating systems

    If you run a Windows operating system on your computer, all recent versions now support some form of Operating System (OS) level decode for Dolby audio.

    There are a few exceptions, though:

    Older versions of Windows:

    • Windows 7: Windows 7 does not include the media package required to decode AC-3. The best solution is to upgrade to Windows 10.

    Adobe Creative Cloud apps use native OS support for Dolby

    14 replies

    Participant
    November 18, 2017

    I'm running Windows 7 in a windows 7 only environment. I'm just wondering what Adobe was thinking... AVCHD is a pretty common format... why release your platform knowing it's going to kill so many users projects.

    G

    ProDesignTools
    Community Expert
    Community Expert
    November 18, 2017

    They may not have had any choice.

    Neither Adobe or Dolby is saying what happened (perhaps legally restricted), but it has the hallmarks of a licensing dispute. So us trying to guess what went down is speculation.

    All we can say for sure is that this is highly unusual for Adobe – whenever in the past there has been a significant change in platform requirements or functionality, the company has always given plenty of notice well in advance. So, something very exceptional must have transpired for things to happen the way they did.

    Participant
    October 31, 2017

    Hi SWMP, Your OS is Windows?, In my case I have W10, when I imported AVCHD (MTS/AC3) Premiere informed that there isn´t Dolby codec, when accept (Click on buttom) it will install the codec. And works!!!

    But others users, say me thats no works for they...But, they aren´t admins, is necessary switch to admin user, open Premiere, Import the conflict media and accept install the codec. When switch to normal user, Premiere works without problems.

    Please testing that.. WORKS FOR ME!!!

    Inspiring
    November 2, 2017

    See my reply: That does not work any more, as Adobe removed Dolby Codec also from 2017-Version.

    Known Participant
    October 24, 2017

    Just circling back to report that I worked through Adobe Customer Care to have them re-install 2017.  So far, that seems to be working.  They believe the problem is not in Premiere 2018, but in my footage, since 2018 no longer supports Dolby codec.   I asked the tech who was helping me whether they planned to make it possible to continue using AVCHD footage in Premiere in the future and he said he didn't know. So for now, I am going to hold onto 2017 for as long as possible to edit what are now all my legacy projects shot on my Sony. 

    Inspiring
    October 25, 2017

    Hello everybody,

    The out of sync issue is not consistent. I created new project, cleared cache and so on. The biggest problem for me is that with the same camera and setting one clip is out of sync and the other is fine. Here below is the info of my .mts clip I have out of sync problem. When I play that clip in VLC player is fine. When I import into Premiere 2018 it's get out of sync.

    Trent HappelCorrect answer
    Participating Frequently
    October 18, 2017

    Adobe Creative Cloud has moved to native Operating System (OS) support for Dolby Digital decoding (reading Dolby files) and is no longer providing support for encoding (writing) Dolby Digital and Dolby Digital Plus sound formats in the current and future releases of Creative Cloud.

    Dolby audio decoding

    Both Windows and OS X operating systems (Windows 8.1 or above and Mac OS X .11 or above) contain native support for Dolby decoding functions. Please update to the latest version of your operating system.

    Dolby Audio decode support for Windows operating systems

    If you run a Windows operating system on your computer, all recent versions now support some form of Operating System (OS) level decode for Dolby audio.

    There are a few exceptions, though:

    Older versions of Windows:

    • Windows 7: Windows 7 does not include the media package required to decode AC-3. The best solution is to upgrade to Windows 10.

    Adobe Creative Cloud apps use native OS support for Dolby

    marks1188378
    Participant
    October 23, 2017

    Trent --

    This is urgent.  I work in WIN7 in a corporate environment for a very large public utility.  Upgrading my OS in not an option.

    Suddenly we are unable to use AVCHD footage.  There must be some work around or other solution.  We have many CC licenses and the upgrade to 2018 has just rendered your very expensive software useless.

    And of course I am on deadline to cut videos to be distributed to 20,000 employees this week.

    Who can I contact for help???

    Thanks,

    Mark

    Participating Frequently
    October 23, 2017

    I would suggest you contact Customer Care.

    For more information, please contact Adobe Customer Care.