Forum Replies Created

Page 150 of 428
  • Michael Phillips

    June 5, 2014 at 12:43 pm in reply to: HDTV monitor calibration

    I watched a webinar yesterday on the SpyderHD product from Datacolor. Something to consider if your on a tight budget.

    https://spyder.datacolor.com/portfolio-view/spyderhd/

    Michael

  • It’s more that the project be closed than MC not running, but I am always sure there will be no issues with MC not running. I have see corrupt bins that come up with ???? as a name when copying bins into a project that is open.

    Michael

  • I use the “open bin” and have it show up in the project window, then do a “save as” to the open project or copy bin contents to a new folder created within that project.

    or

    At the desktop level, with MC not running, copy bin into the project folder.

    Michael

  • I only see this with multitrack monophonic and option to create one master clip upon import. If you:

    1. Import all clips as individual tracks and autosync
    2. Create a poly file in WaveAgent

    I’ve reported same behavior in 8.x beta.

    Michael

  • It is a good fix, too bad Avid doesn’t promote the workflows that it now allows. Most people don’t know it was fixed to behave this way, making it more a new feature than a bug fix in my opinion.

    Michael

  • With v7, the CDL values do not have to be baked in which is different than passing the CDL values along which has been supported since v3. With v7, you can keep the images “LOG” and update CDL values when needed.

    Michael

  • I did a Moviola Webinar where I show LUT and ALE merge using Resolve.
    https://moviola.com/webinars/4k-with-avid-blackmagic-design/

    It’s a $9.95 rental charge, but seeing as I make money off that, I highly recommend it. 🙂

    Michael

  • Richard – Avid has finally made the merge non-destructive in 7.0.3 where an ALE will only replace/overwrite the fields in the ALE and not all fields associated with the master clip –

    https://24p.com/wordpress/?p=132

    Michael

  • I always advocate for double system audio sync in Media Composer as well, but sometimes that it not possible, or as you say, other deliverables require a sync in the dailies tool. I wish Media Composer would offer better support for embedded metadata when it comes to conform. This has been a known issue for a while. The QT AMA is limited to only filename an timecode and everything else is lost so formats like Alexa shooting ProRes, or Prores/DNxHD on a BMD camera loses the metadata… that’s what got me to develop my own AMA plug-in for song metadata since the QT AMA left all the info behind. More info on that at https://www.mus-id.com

    I have also written many blogs on how to get metadata into Media Composer at https://www.24p.com/wordpress

    Michael

  • AMT is Avid Media Toolkit that allows third parties to create native MXF wrapped essence. This, combined with a DNxHD license, gives them the ability to create native MXF/DNxHD. It also has the ability to create an AAF of the resulting clip.

    AMT does not create the ALE. ALE is created by the manufacturers creating the files whether they use AMT or not. This is why you will find some inconsistencies between programs as to how and where metadata is stored.

    Typically, AMT creating MXF/DNxHD will only have limited metadata – it puts the filename as Tape and primary timecode (typically TOD) into START. All other metadata is usually provided via the ALE as a merge or as you have noted, as an import/relink.

    Personally, if there is an AAF created, I will:

    1. Copy MXF files to Avid MediaFiles folder
    2. Drag and drop AAF files into bin. These will relink automatically to media
    3. Merge ALE into existing master clips.

    I have seen instances where just importing an ALE and relinking has been very hit and miss with the ability to stay linked – especially with audio tracks. MOS clips seem to fare better. Some people have never had a problem –

    Michael

Page 150 of 428

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