Forum Replies Created

Page 297 of 428
  • Thanks John – that was my understanding for Mac; Fast import is the way to get rewrapped ProRes from QT to MXF. AMA is for instant access and editing, but not as a means to rewrap via a consolidate to MXF to be “Managed Avid Media”.

    Maybe AMA/consolidate will be implemented in the future as it is more logical, allows for viewing and selection before the process as well as triage within the clips themselves.

    Michael

    Michael Phillips

  • Thanks John. The question now is what where the times associated with either method? Was one fast than the other? Did the import process say “fast import” while importing? And if so, how did that compare to the transcode process?

    Or another test; with AMA/transcode. Select the same codec as the source and time it, then select a different codec and time it. What are the times between those two? This will indicate whether it is a straight copy, or a decode + re-encode process is happening.

    Michael

    Michael Phillips

  • Michael Phillips

    February 26, 2012 at 7:09 pm in reply to: AVID AAF to Resolve, dissolve issue

    Does an EDL behave the same way?

    Michael

    Michael Phillips

  • Logically a “consolidate” is only a copy/rewrap to Avid managed media, but does not work that way on Windows for whatever reason since technically, it is still only doing playback.

    I need to get on a Mac version to see what’s it’s doing, but then again, “logically” it would still be a copy/rewrap as part of the consolidate process – especially for entire takes (and not sub-spans of files). I remember doing it once as a transcode during beta, and while it “fast”, it was decoding and encoding from and to the same codec. But I will test and get to the bottom of this. The Avid website didn’t offer much detail on this specific process.

    Michael

    Michael Phillips

  • Quick test under 6.0.1 on Windows 7. I understand the fact that it doesn’t allow for Prores encoding… but since the incoming file is ProRes (HQ), the rewrap process should not invoke an encode process.

    1. AMA to ProRes(HQ) file. Plays back fine. Highlight and click on consolidate/transcode. Go through first screen of settings, then second about linking master clips to target drive. Click OK. Get message to check error message in console. Lots of info about how codec being read not supporting, resorting to sample player. So no rewrap “copy” of ProRes file to Avid managed media. Logically, this would be the way to do it.

    2. Since there is no encode on Windows 7, the “fast import” was not even a choice since I could not select ProRes(HQ) as a target resolution. Dead end.

    So it seems, unless I am missing a step, that ProRes on Windows is AMA playback only. Select alternative codec (DNxHD) for render and/or transcodes. I will need to get a v6 on my Mac to test there.

    Michael

    Michael Phillips

  • Unless something changed in 6.0.1, I was told that the rewrap was done as part of the “fast import” process. During beta I entered a bug that my ProRes was being transcoded with AMA, and that was the response I got. I agree that an AMA “consolidate” logically, that’s how it should work. I will try to test it again today. I would be glad to stand corrected.

    Michael

    Michael Phillips

  • Then I really see no reason to involve ProRes at all since DNxHD and ProRes are really equivalents to each other. DNxHD 36 would be the way to go directly from REDCINE X as native MXF.

    Michael

    Michael Phillips

  • I haven’t tried in a while, but I thought in order to rewrap ProRes as MXF in Media Composer, it is not via AMA (it always transcodes, even if selecting same codec, rate, etc.). Rewrapped ProRes is done via import and should be a fast import.

    As far as overall workflow, are you intending to have the ProRes be your new submaster from which everything is derived and never go back to the R3D files for conform and mastering?

    Michael

    Michael Phillips

  • I believe the pulldown removal (advanced and normal) as well as variable frame rate flag capture only works while in a 720p.23.976 project over FireWire. This can be done in either a film or video project type.

    Pulldown removal was never implemented for 1080 format over FireWire or SDI.

    Michael

    Michael Phillips

  • Having that information defined for your production master allows for better tracking of source elements, mix and match, aspect ratio correction, color space conversion, etc. Even in offline, ensuring the timecodes and such is important if going to an online – especially if on a different system.

    Michael

    Michael Phillips

Page 297 of 428

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