Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Avid Media Composer Trouble converting t2i footage into dnxhd using Compressor…

  • Trouble converting t2i footage into dnxhd using Compressor…

    Posted by Edward Calabig on August 20, 2011 at 1:35 am

    I’m having trouble finding the correct Compressor settings to transcode my h.264 footage into DnxHD (36 or 175).

    My preset in Compressor is:
    File format: Quicktime movie
    video settings:
    Avid DNxHD codec
    frame rate current
    depth millions of colors+
    color levels 709
    alpha none
    resolution 1080p/23.976 DnxHD 175 (or 36)

    audio settings:
    linear pcm 48/16 bit

    When I look at the converted quicktime movie, it looks awful. What am I doing wrong?

    Thanks.

    Ed Cilley replied 14 years, 9 months ago 3 Members · 5 Replies
  • 5 Replies
  • Edward Calabig

    August 20, 2011 at 2:11 am

    Ok I’m trying mpeg streamclip now and going to export other format
    switching to dnxhd codec
    quicktime movie
    1920×1080 (unscaled)
    unchecked interlaced scaling (did not check deinterlace video

    The video looks much better except everything looks more flat than my proRes HQ transcode from compressor. Is this normal for DNxHD?

    Should I check deinterlace video or interlaced scaling?

  • Andrew Mckee

    August 20, 2011 at 6:04 am

    There is no need to convert DSLR footage in another application. Here are 2 ways to get footage into Avid.

    1) FIle -> Import – This will import the original movs and convert them to Avid MXF files in chosen resolution.

    2) Link to AMA Files – In version 5 or above this will bring in the native files but performance will depend on your system (definitely get better performance than FCP7 though). Most likely you will need to then transcode which will convert to Avid MXF files (although marginally faster than the import option)

    Andrew McKee
    Editor/Colourist
    Avid Certified Instructor – MC5.5
    Apple Certified Trainer – FCP7
    Pixelwizard.net

  • Ed Cilley

    August 20, 2011 at 12:50 pm

    Use option 1 that Andrew mentions. Options 2 is good if you have a ton of clips and will only be using a few clips, but playback of the H264 files via AMA gets slow in long sequences.

    _________________________________________________
    Anything worth doing at all, is worth doing well.
    – Philip Dormer Stanhope, Earl of Chesterfield

  • Edward Calabig

    August 20, 2011 at 4:50 pm

    Thanks I had a question though. Does the project save a d copy of the imported footage somewhere? I can’t find it in my project folder or in the source folder where my original h.264 footage is at?

  • Ed Cilley

    August 20, 2011 at 5:24 pm

    Avid works differently than FCP when it comes to file management. All imported media goes to the drive you specify on the import screen. (Hopefully you work with an external drive and not your system drive.) In other words, all media you work with in Avid, gets imported and new files created. Music, stills, video, everything gets imported to the following folder…

    You will find a folder called “Avid MediaFiles”. You really don’t need to navigate to this unless you are trouble shooting other issues. Also, the files you find in here won’t just open in QT, like your Capture Scratch files in FCP.

    This also makes media management easy, since all clips used in the project are stored in this one place and not just pointing to the original files which could be scattered on several drives. You may want to look at a program call Avid Media Mover by Random Video (https://www.randomvideo.com/products/mediamover_avid.html). This makes backing up an entire project really easy since it moves all media into one folder.

    Hope that helps.

    _________________________________________________
    Anything worth doing at all, is worth doing well.
    – Philip Dormer Stanhope, Earl of Chesterfield

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