Skip to main content
czar_film
czar_film
Participant
April 19, 2018
Answered

DNxHD MOV Import in Premiere CC 2018 and Transcode Media Encoder doesn't work anymore

  • April 19, 2018
  • 4 replies
  • 8183 views

Hello,

we have an issue on the Premiere cc 2018 and Media Encoder. DNxHD Files exported from AVID in Mov Container are not recognised anymore.

In premiere they show up just as soundfile and Media Encoder is black. Same files work fine in CC 2017 both Media Encoder and Premiere.

We tried the update but this issue is a fundemantal disadvantage. What could be the problem or don't they support this codec anymore...

I installed the CC 2018 on a mint OSX Sierra at an MacPro Late 2013. As mentioned the additional installed Media Encoder CC 2017 works fine.

Any help would be appreaciated.

Thanks,

Thomas

    This topic has been closed for replies.
    Correct answer czar_film

    Here is the answer from Masku2000. I suspected it's related to the abandonded 32bit support. I don't know why Adobe thinks, no one needs this support anymore...

    "We've taken a look at the file - this particular file has multiple "Image Descriptors", i.e. multiple Codecs in the same file. This was previously supported via 32-bit QuickTime, and we are no longer able to support these types of files."

    4 replies

    camw73698184
    camw73698184
    Participant
    May 17, 2018

    I believe this is a mixed resolution issue.  I just ran across this recently in my own workflow.  It sounds like we have a similar set up to you.  I usually work at DNxHD115, but I made a quick edit of some DNxHD175 footage, but the timeline still had a DNxHD115 slate on it.  Each exported Qucktime would come through Encoder as solid black.  I went back to Media Encoder 2017 and it was not a problem.  I just tried a test replacing the DNxHD115 slate with DNxHD175 version of it, and it went through perfectly.

    Several versions ago of Media Encoder, it would freak out with mixed resolution Quicktimes and put solid red frames whenever the footage was different from the first frame of the Quicktime's resolution.  That was finally resolved with a Media Encoder update, but now seems to be back with this new version of the same issue.

    One work around (which we used at the time of the red frames), is to throw an empty effect layer on top of your entire sequence.  This layer will render at one resolution and then your mixed resolution timeline should go through Media Encoder 2018.  I haven't tested this method, but it worked in the previous incarnation of this issue when we would be exporting daily works in progress of a cut.

    czar_film
    czar_filmAuthor
    Participant
    May 17, 2018

    Thank you very much for the comment. I remember the red frame problem well, but we didn't had an resolve for this. But that sounds logical. I will take look!

    S
    splooiecavalier
    Participant
    May 11, 2018

    Thomas,

    I'm having the same issues.  A project that I made a few months ago before the update, now won't link the footage because it doesn't recognize the footage as having a video track.  Have you tried importing DNxHD 220 vs DNxHD 145?

    czar_film
    czar_filmAuthor
    Participant
    May 14, 2018

    Hi,

    Masku2000 wanted to take a look at the file. No answer...

    We haven't tried other bitrates.

    But basically we load AVID with DNxHD36 and want to have a quick same as source export.

    Using other bitrates would mean, that we have to do a transcode, which means it takes a lot longer.

    If we would do that, we could also use ProRES.

    Thomas

    masku2000
    Adobe Employee
    masku2000
    Adobe Employee
    April 20, 2018

    Yes of course you can send a private link to me directly

    masku2000
    Adobe Employee
    masku2000
    Adobe Employee
    April 19, 2018

    Can you provide a link to download a sample file that you are having problems with?

    czar_film
    czar_filmAuthor
    Participant
    April 20, 2018

    I did a few tests. And the problem is not really reproduceable. Some files work in Media Encoder CC 2018 and some files don't. In CC 2017 they all work.  all files were exported from AVID via same as source.

    Since our workflow depends on that, we will use Media Encoder CC 2017 right now. Since some editors used CC 2018 on their private machines I have to do the update at some point. But it's really disappointing that after 1 year of CC 2018 and a first glimpse by me there are not reproduceable errors. Also that h.264 in Mov Container is not supported anymore is quite disappoiting (expecially on OSX), since some clients and also Software like ProTools still use that.

    Can I send you a private link, since the files are sensitive and as stated I can't reproduce the problem...?

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices