Forum Replies Created

Page 7 of 428
  • Michael Phillips

    February 20, 2020 at 4:25 pm in reply to: Avid to Premiere AAF with Multiclips?

    Unfortunately, there is no support for Group clips and AutoSync clips via AAF to other systems. Each system has its own way of creating and representing those relationships and the work to translate hasn’t been done.

    Michael

  • Michael Phillips

    February 18, 2020 at 7:03 pm in reply to: Tape Name| Reel Name | Red Cine X Pro

    If you create MXF OPAtom (not OP1a), and you ensure that REEL is set to filename in Resolve settings, the resulting MXF file will have the filename in the “Tape” column.

    Michael

  • Michael Phillips

    February 14, 2020 at 7:47 pm in reply to: Tape Name| Reel Name | Red Cine X Pro

    MXF contains the TAPE name as metadata in the MXF wrapper and does not use the filename you see at the desktop level. Conversely, Media Composer does not support embedded REEL in a MOV file and will only use the filename. That value is tracked in the Source File column.

    Michael

  • Michael Phillips

    February 6, 2020 at 10:46 pm in reply to: ReLink Nightmare

    Why not just export an AAF and relink in Resolve to the camera masters? That is how it is done on many many projects.

    Michael

  • Do your video sources have audio as part of the master clip on which to sync with?

    Michael

  • I don’t see an image posted there, but as an FYI timeline waveform sync was designed for “grouping” and less so for double system audio syncing if that is what you are trying to. That may explain some of the results, but not all of them.

    If you repost the image, can you also post the “before” timeline as well?

    Michael

  • As a general note, and it is a common mistake – because a file is MXF does not mean it is automatically compatible with Media Composer. There are several things to consider when working with MXF:

    • MXF is a wrapper/container format and can contain codecs of different flavors within it.
    • MXF also has different methods of referencing the assets, OPAtom and OP1a. OPAtom has all essence tracks (V and A) as separate files. This is what you commonly see with Avid MediaFiles native folder structure. OP1a contains all the essence files into (1) single file. Only the more recent versions of Media Composer have started supporting this.
    • The codec needs to be compatible with Media Composer. The rule is if you can transcode/consolidate, it is a native codec.

    Here is a somewhat dated Avid whitepaper on MXF – it’s a good starting point for Media Composer and MXF.
    https://www.avid.com/static/resources/common/documents/mxf.pdf

    Michael

  • Michael Phillips

    January 7, 2020 at 6:38 pm in reply to: Blue waveform in source monitor

    Just went back into MC, latest version and also see the blue waveform in the source monitor:

    Michael

  • Michael Phillips

    January 4, 2020 at 8:00 pm in reply to: Avid: Video playback issues, can hear audio

    Need a bit more info…

    AMA linked media?
    If AMA linked, what created the file? is it a camera original or transcoded?
    If transcoded, what was used?
    Avid Native Media in Avid managed MediaFile folders
    When you say MXF, which is a wrapper, what codec is inside it?
    Do other files from the same camera/transcode process work properly?
    Media Composer version
    OS platform and version
    Software only, or IO hardware attached?

    Michael

  • Michael Phillips

    January 3, 2020 at 10:02 pm in reply to: Blue waveform in source monitor

    I believe Job is right and I did not want to be misleading – the blue/black waveform is only in the bin thumbnail view and not in the Source monitor when loading an audio-only source clip. Now why it shows up in your source monitor is quite the mystery.

    Michael

Page 7 of 428

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