Forum Replies Created

Page 318 of 428
  • Michael Phillips

    March 14, 2011 at 1:30 pm in reply to: Exporting for 16:9 project

    The 16:9 or 4:3 check box in the QT export is only for QT player, not a flag for MPEG2 encoders. That needs to be set manually in the encoders parameters to allow it to put the 16:9 flag into the resulting file. If coming from standard def into Sorenson, you need to deselect “maintain aspect ratio” and set an x and y that is 16:9.

    Michael

    Michael Phillips

  • Michael Phillips

    March 10, 2011 at 12:23 am in reply to: Interlace to progressive

    I think you may need to transcode first for it to become 720p (progressive).

    Michael

    Michael Phillips

  • Michael Phillips

    March 9, 2011 at 1:34 am in reply to: Auto Sync Multi Track Audio

    With v5, AutoSync gives you control of which tracks remain or are removed from the resulting .sync subclip. If you want the audio tracks with the video to remain, then select the keep audio and which tracks. For example. 1-2. Then for the audio file you are syncing to that, select the range you want to keep that pertains to that camera. Unfortunately this does support tracks that skip – for example, you can keep tracks 5-7 but not only 5 and 7.

    Michael

    Michael Phillips

  • Michael Phillips

    March 3, 2011 at 2:16 am in reply to: Avid export to broadcast

    Which broadcaster are exporting to? All of them have a delivery requirement document you can request to meet their needs.

    Michael

    Michael Phillips

  • Michael Phillips

    March 3, 2011 at 2:15 am in reply to: Mc 5.0

    All patches and read me’s:

    https://www.avid.com/US/support/downloads/patches

    Michael Phillips

  • Michael Phillips

    February 22, 2011 at 4:55 pm in reply to: Transcoding Question

    Can whomever sent you the files transcode to a format that is supported?

    Michael

    Michael Phillips

  • Ah – I thought that might be it, and not 23.976 versus 24.00. iTunes has a similar request; progressive over interlace.

    With that being the case, open your 59.94 sequence in a 1080p/23.976 project. The Media Composer will automatically provide frame rate conversion as well as interlace or 2:3 removal on the cuts creating 23.976p. Transcode/render entire sequence, then export QT reference and encode per specs as needed, or go out to an HD deck as 1080p/23.976 native.

    Michael

    Michael Phillips

  • Also, can you point me to any documentation on the 24.000 requirement for Netflix?

    Thanks –

    Michael

    Michael Phillips

  • Interesting… must be drafting off the DCI spec then for deliverables.

    Can I assume your 23.976 master is native? Meaning no pulldown?

    One method if it is, is to output to HDCAM or similar 23.976 capable deck as 23.976 from your original native 23.976 timeline. Then switch deck to 24.000 and recapture as 24.000 in Media Composer and deliver your file based deliverables from there. That’s what I did for the 25fps deliverables on a feature I produced a few years back.

    If you have no deck, and the 23.976 is native with no pulldown do:

    Video only QT export same as source.
    Audio only WAV

    Create a 1080p/24.000 project and:

    Video: enter “ignoreqtrate true” in console. Import QT reference. This will now play frame for frame at 24.000fps (.1% faster).

    Audio: Open WAV file in WaveAgent (free from https://www.sounddevices.com) and change sample rate from 48kHz to 48.048. I know it sound backwards but for this workflow, it is what’s needed. Set audio import settings to do a pull-up/down. And import. Audio should now be running .1% faster to be in sync with your frame for frame speed up on video.

    Export/encode as needed for output.

    I don’t know if Sorenson or other encoders can do a “pullup” frame for frame conversion in this scenario as part of the encode process. That would certainly eliminate a few steps – but the above is relatively fast since there is no transcode to picture or audio.

    If your sequence has pulldown in it – then that is a different scenario. Let me know where we stand now.

    Michael

    Michael Phillips

  • I think what you’re saying is you have a 59.94 master with pulldown. Cadence may be continuous throughout, or it may not? And now you need to deliver a native 23.976 or native 24.000? If 24.000 you will also need to sample rate convert audio to maintain sync and 48kHz.

    Please clarify the above questions and we can proceed.

    Michael

    Michael Phillips

Page 318 of 428

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