Forum Replies Created

Page 11 of 428
  • Thanks Richard – forgot about that method…

    Michael

  • It’s not well thought out that the list is limited to only to “standard” columns in the bin and not custom ones imported by ALE or manually created in the bin. It’s even more strange that it shows column names that you can’t find from the list of all columns when adding one to the bin. ☹

    That being said, you can repurpose some of the supporting columns in that burn-in list (further frustrating that the list is no in overall alphabetical order…). For example, I repurposed the “Camera” and IDataLink” columns available for burn-in and added my custom data such as lens, etc. I made stuff up for the example, but you get the gist. Once those columns are in the bin, duplicate the column you want to display into those columns.

    Be aware that the IDataLink column that is available is not available in most project types, probably just film projects, but if you create a column with the exact name matching uppercase/lowercase it will work. Or use some other column like Camroll that may not already be in use. Labroll is not available in the bin but may also work if you create manually.

    Once that is done, then select those columns in the burn-in selection.

  • Michael Phillips

    October 22, 2019 at 2:44 am in reply to: Infra Red B&W – DNX Resolution?

    I would not recommend DNx 80 as it is for thin raster codec. Go DNxHD 115.

    Michael

  • I’ve never been able to get a clear response from Avid as to what differences to expect between Edit Protocol being checked or not. I did find through some trial and error that custom column metadata on source clips was not exported when Edit Protocol was checked.

    Michael

  • Michael Phillips

    October 5, 2019 at 2:51 am in reply to: DPX only importing the first 99 frames

    What’s the numbering format look like from the 99th and the 100th frame?

    Michael

  • Michael Phillips

    August 16, 2019 at 8:29 pm in reply to: Video Usage in Sequences from Clip

    As long as all the bins containing sequences are open, you can select 1 or more clips and choose “media relatives” and sequences will highlight that contain them. But there is no metadata value in the bin as a list to view the same.

    Michael

  • AutoSync always truncates to shortest contributing clip. You can try working with a grouped clip instead but will have to potentially deal with things like match frame, no out of sync indicators, etc. and remembering to “commit” Multicam edits when sending AAF’s etc.

    Michael

  • I think you’re out of luck. In doing the simplest of tests:

    1. 23.976 fps project
    2. AMA link to 59.94p material (59.94fps)
    3. audio recorded to be in sync with 23.976 material
    4. Create a sequence to create sync, subclip the sequence to a subclip
    5. Edit that into a new sequence (clips is named 60fps in the screenshot)
    6. Edit a section of the 59.95fps clip with no speed change via effect or source setting applied. Timeline now has two events with the same source footage, once as an AutoSync source clip, the other as its original.
    7. General EDL. Notice that the first event (60fps clip) has no motion indicator on it while the second even does.

    The AutoSync process removes any reference to a speed change as I believe the video takes on the properties of the audio in this scenario. There is no “flatten” or other .sync subclip undo process to bring that back. You’re only solution is to edit with a sequence as a source.

    Michael

  • I’ve started looking into replicating this but hope to have more time to do so. I’ve done a small test syncing a 25fps unadjusted video to audio via timeline autosync, and even a simple EDL does not indicate there is a time-based mismatch. More as I go along.

    Michael

  • Then I would try setting the playback to project rate in source settings before syncing and see if that helps in the AAF interchange.

    Michael

Page 11 of 428

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