Forum Replies Created

Page 157 of 428
  • Michael Phillips

    April 25, 2014 at 8:55 pm in reply to: Avid/Resolve workflow shifting timecode

    Did you make individual clips out of Resolve or a timeline as single clip? If the source clips were NDF and they came back as DF that could explain a shift. And why would TAPE names needs changing, were those not preserved withing Resolve?

    Michael

  • Great! But it would be a great feature to matchframe to the original audio in a .sync file directly from the timeline… Another feature request. 🙂

    Michael

  • In the timeline, source tracks, turn off the V track so that only A tracks are highlighted, or the ones you want to match to, and do a matchframe again. You may need to map the matchframe to the buttons below the source monitor or make sure that the source monitor is active when clicking matchframe.

    Michael

  • When you make EDL and such, the clip knows the sources it came from. If you want match back to the audio clip during editorial, you do the standard matchframe to bring up the .sync clip, then turn off the V channel and do a matchframe again from the source side and it will load the original BWF file at the same position.

    Michael

  • Michael Phillips

    April 24, 2014 at 11:56 am in reply to: Bob Zelin wasn’t too kind to X

    I should note that CDL support has been part of Media Composer since 2006 – and recently with v7 is actually part of the source side color transform so changed can be applied during post and updated as needed. But the ability to import CDL via ALE, edit and send out ASC via EDL has been there for a while. It just gets a lot more interesting with v7. I will actually be doing a Moviola webinar on this workflow Tuesday.

    Michael

  • Michael Phillips

    April 23, 2014 at 9:10 pm in reply to: Bob Zelin wasn’t too kind to X

    But RAW is still not unlimited dynamic range and you do want to bring in to sweet spot of the sensor. And while RAW does allow more flexibility in exposure, the camera can switch between RAW and other codecs where such a filter would be great to have.

    Michael

  • Michael Phillips

    April 23, 2014 at 8:19 pm in reply to: Avid will not import Tape ID meta data

    That is another way to deal with it, create a column common to both clips with the same metadata. TapeID is one that is used in some instances, but seems to be user generated except when importing BWF and then it’s populated for some reason. Probably because the BWF metadata chunk has a Tape field in it and that is where it is mapped.

    I will sometimes use Labroll and Camroll as a common metadata field as I can generate an EDL using those columns as source REEL if needed.

    Michael

  • Considering Avid’s legacy where storage requirement really limited it to one job, gas been the basis of project/media management from the get-go. But that is longer the case and Avid’s “media management” hasn’t really kept up with the times. It should be a relatively easy task of selecting the entire project, a bin, a selection of clips and do a right-click (copy/move) command to the OS level to perform this task rather than all the permutations needed today.

    Also keep in mind that if you are using DMF (Dynamic Media Folders) that a project name is NOT associated with those clips, so MediaTool, sorting, and third party tools will not see that to automate of these processes. See my blog on DMF considerations: https://24p.com/wordpress/?p=141

    The same goes with the new “Managed AMA” feature. I find more people turning that off as its benefits were never clearly defined by Avid as to where it helps, or not depending on workflow. I do know that my MediaTool is full of AMA clips which I guess is managed, but I can’t delete them, even when I have deleted them from the project.

    Michael

  • Michael Phillips

    April 23, 2014 at 11:33 am in reply to: XDCAM import problem

    I usually try linking via clip first before folder to make sure the correct Sony AMA plug-in is being used. So in yor example, use the link to file and select “C001A01.mxf ” directly with each of the plug-ins. Once you know you can link to it, note which one you are using then use the “folder” version of the AMA plug-in and work your way backwards in the folder structure until it works. There is only one level of hierarchy that will work and I never remember which one, so I do the different levels until it does. My guess is either the PROAV or the CLPR folders. Also make sure there are strange characters or slashed (/) in any of the folder names, but from your example, it does not seem to be the case.

    Michael

  • Michael Phillips

    April 23, 2014 at 11:27 am in reply to: Avid will not import Tape ID meta data

    It’s an either/or situation between AMA and dailies systems. Sources are tracked in either the “Tape” field or the “Source File” field. Only Avid creates clips with Source File via import or AMA linking. All third party applications making native MXF for Avid can only put that info in the “Tape” field. There is no option to make “Source File” with third party systems, even when using Avid’s SDK to create media. This has been a long time request.

    But, that is not an issue – your dailies have this info in the Tape field, but then you AMA link for the conform. This is done by highlighting the sequence and all the AMA linked files and doing a “relink to selected”. In this relink dialog box you can relink any column or timecode column as needed. And the ability to relink between Tape and Source File has been there since v6 and got better in 6.5.

    The one issue that might arise is when creating the dailies in the first place; how was the REEL ID assigned to start with? In a bin, display both Tape and Source File, compare a dailies clip with the same clip linked via AMA and see that they are the same (or close, AMA will have the extension). If they are, the above will work, if not, you got a different issue and we can take it from there.

    Michael

Page 157 of 428

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