Michael Phillips
1
COW Coin
Forum Replies Created
-
No problem – It would be interesting for you to drop each clip into the console and see what Media Composer thinks the MOB ID is, or I’ll put together the steps to use an AAF dumper to get that information. I suspect it is the on-board recorder repurposing MOB ID’s that caused this.
Michael
Michael Phillips
-
That’s the good and bad of AMA – the marketing side will make you believe it is native editing all the time – but as with all things, there are shades of gray – while it is true that it can work, I find it works best with non-DnxHD Avid native codecs and some up to 10-15 hours of sources. Also, if you need to do multicam, and such, AMA is not the way to go.
In your scenario, since you started AMA, you will need to transcode via AMA. Any color corrections you did should carry through the RMD file if you select that in the source settings (default) before the transcode.
Only v6 with the latest version of the AMA plug-in support the latest Color space, but does not yet support DRx should any of that been used on the footage.
Michael
Michael Phillips
-
Does the control panel not have a “add 2:3 pulldown” allowing the 23.976 to become 59.94?
There may also need to be a checkbox for progressive versus PsF as most monitors (other than broadcast ones) want to see progressive.
Michael
Michael Phillips
-
Perhaps you are running into the known issue with R3D files and relink when starting with AMA then relinking to files transcoded with REDCINE X Pro. The name of the MXF file is not the issue, it’s the fact that AMA puts the file name (including .r3d) in the Source File column and Redcine X Pro (using the Avid SDK) puts the filename in the TAPE column without the .r3d extension. This is further compounded by spanned files where AMA will see the filename with the _001 at the end of the filename while REDCINE X Pro will still be the original 16 characters.
Although some relinking between Source File and Tape was done in v6, it did not support the spanned file naming of R3D and seems to be your problem. You would need to transcode the AMA linked files to not have this issue.
Michael
Michael Phillips
-
In your case it’s a combination of amount of footage, type of drive, and AMA. At some point you will find yourself trnascoding… and when you do, make sure Media Creations is not set to FULL debayer as it will take a long time. 1/2 premium or 1/2 good are fine for HD finishing. Use full if you have a Rocket card.
Michael
Michael Phillips
-
I passed it along. Are you using Avid hardware or third party?
Michael
Michael Phillips
-
I have been happy with my Blackmagic Extreme 3D card – especially with the latest desktop video drivers which fixed the audio scrub crash. And it offers all the analog I/O for your legacy decks. I am only speaking for MC, I am just getting CS6 up and running and will be testing there as well.
Michael
Michael Phillips
-
Which codec are trying to capture to? Perhaps it can’t keep up for an MPEG format without codec assistance on the hardware. But seeing the superlong error message might help.
Michael
Michael Phillips
-
Well AMA managing lots of footage will slow down. Add to that the R3D format for debayering overhead, and whatever the connection to the drive (and if daisy-chained) all impact the overall performance expectation for the editor.
My cutoff for AMA for codec types is around 6 hours. Anything more, I will transcode up front. Some codecs that are native to the Avid codec library (formats you can transcode to in addition to DNxHD) will have a better time via AMA since the decode is not being done by QuickTime, etc.
I suspect you are set to green/yellow which affects the debayer extraction you are using. You need a chart to keep track of what MC is doing when it comes to debayering R3D. For example, if you shoot 4K, the green/green mode is only 1/2 debayer since the 1920×1080 project type does that on the fly for you as 1920×1080 is near 2K, and thus 1/2 of 4K. So green/yellow is 1/4 and yellow/yellow is 1/8th. But if you were to open that in a 720p project, then you would be starting at the next level down (1K) where green/green is 1/4, green/yellow is now 1/8th, etc. but may get you more performance due to removing some of the debayer overhead.
Michael
Michael Phillips
-
Do you find it bailing after the resulting file exceeds 2GB? I think MC knows how to make multiple files fro DNxHD for long captures, but perhaps not for other codecs. Or it could be that setting isn’t active in the capture settings.
Michael
Michael Phillips