Forum Replies Created

Page 1 of 2
  • Jenny Conway

    January 25, 2017 at 6:05 pm in reply to: Adobe AE Black Screen (Project Viewer)

    Great question! I wasn’t rendering to Cineform but that made me check my Output Modules and it looks like AE 2017 alters your previous settings. It changed it from an Avid DNxHD Codec to a DNxHR/DNxHD.

    I’m attaching a screengrab that compares output module settings and the pulldown re: the Avid codec settings (even the list has changed) in case that helps anyone.( I’ll also check with Avid to see if they’ve updated their codec).

    I did a test render in AE 2017 w the corrected codec and it works!

    Many thanks, Walter!
    Jenny

  • Jenny Conway

    January 25, 2017 at 4:24 pm in reply to: Adobe AE Black Screen (Project Viewer)

    Hi,

    Not sure if this helps but, after upgrading to AE 2017 and rendering from AE, I found my QT renders showed black (when viewed in QT 7 and wouldn’t read at all in QT 10). I tried exporting to Media Encoder 2017 only to have it crash repeatedly.

    But, what I found out, as I was trouble shooting: I can render out of AE 2017 to a QT file and, while it can’t be viewed in QT or be imported into AVID, if I then run it through Encoder 2015, the file is now playable in QT and able to be imported into Avid.

    It’s a pain to do the extra step but it’s possible your videohive assets could be treated in the same way?

    (I only upgraded in order to open a file sent to me, but I know I’ll stick w AE 2015 for the near future.)

    Jenny

  • Jenny Conway

    August 30, 2016 at 2:06 pm in reply to: Black levels crushed using DNxHD codec w AE upgrade?

    Hi Marcin & Piers,
    Sorry for the delay. I had the Avid export as a SAS (same as source). Then I put an Adjustment layer at the top of my comp and applied Color Profile Converter. For the Input Profile, choose HDTV (Rec. 709) and for the Output Profile, choose HDTV (Rec 709) 16-235. This will make it look slightly grayer in AE but when Avid imports it, the blacks are fine and it matched perfectly with footage in the Avid, without color shifting. Hope that helps? I plan to try a test w Media Encoder to see if it’s needed there but haven’t done it yet. Hope that helps.
    Jenny

  • Thank you, Chris- that worked! I set the Input Range as HDTV (Rec 709) and the Output as HDTV (Rec 709 16-235). We did a test and this seems identical to the 32 bit/Level technique so both are good.

    The takeaway I guess is that AE needs the Rec 709 full range 0-255 to work in but, if you don’t limit it to 16-235 on render/export, you’ll have level problems when it’s imported into the Avid again. Many thanks to you and Dave for your patience & advice!

  • Thanks you! I’ll give that a try!

  • PS sorry, never mentioned that the Avid files were exported Same As Source/709 each time.

  • Ok, Linear Output bad choice- boosted the white levels. So far the 32-bit (float) w an Adjustment Layer (w a Levels correction) that I noted above is the best option.
    Someone posted on a forum that “it’s best to work in the 0-255 range and use the legal range for delivery.” I still don’t understand why (especially if the workflow was a perfect match before) so I’m all ears if anyone knows more. Thanks!

  • Thanks, Chris. Hmm, I did try the Color profile converter but still had crushed levels- so I possibly had the settings wrong then?

    (I tried the Project Color Space=None and also as =HD 709 and tried the Color Profile settings as both Input=Project Working Space and Input=HDTV (Rec 709) but still not luck.)

    The only thing I didn’t try was the button for Linearize Input Profile- would that be something that would help? I’ll try a test- thanks for the suggestion.

    Jenny

  • Mov (QT mov as export and QT mov as render).

    Also tried replacing the original Avid movie w an exported OP1a as a test, but the crushing of black levels was still there. I’m stumped and, since I haven’t seen too many people posting about it, I’m just really curious as to what I’m missing.

  • Jenny Conway

    April 2, 2012 at 5:31 pm in reply to: back & forth movement linked to audio

    Yes, you’re right. That works perfectly! Thank you for untangling the problem for me- makes much more sense now!

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy