Michael Phillips
1
COW Coin
Forum Replies Created
-
Richard is asking how the MXF files got created in the first place – via a third party dailies system like Resolve, or via a transcode via AMA linking directly to the camera originals? The answer you provide, changes the answer we provide.
Michael
-
I think there may be presets for exporting to Sorenson, I have never used them. I just go with creating a QT reference and opening that file up in either Sorenson, MPEGstramclip, Adobe Media Encoder, FCPx, or whatever weapon of choice for creating your streaming deliverables.
Michael
-
Compressing for streaming is an art form to strike the perfect balance of size versus quality. I would start by saying that using direct QuickTime export out of Media Composer is not the best solution. I would suggest mixdown/render/tanscode everything to DNxHD in your timeline and export as a QuickTime reference out of Media Composer and use the supplied Sorenson Squeeze that comes with Media Composer or even MPEG Streamclip does a better job than direct export out.
Michael
-
Third party hardware for video I/O has been around since v6. I am sure there is something in the documentation that explains SDI monitoring setup. Also know that the button in the timeline toolbar for turning ON/OFF external monitoring also works with third party hardware, so make sure that is active as well. In MC, go to TOOLS menu and hardware I believe and see what settings you have access to.
Michael
-
You don’t mention where you are starting your workflow –
1. AMA link in Media Composer, stay AMA, export AAF, link to camera originals in Resolve
2.AMA link in Media Composer, transcode to of offline proxy, export AAF, link to camera originals in Resolve
3.AMA link in Media Composer, transcode to of mastering DNxHD media, export AAF, link to MXF media
4. Start in resolve, create MXF/DNxHD, then come back to Resolve and either link to camera originals or MXF.Michael
-
One shouldn’t have to go modifying TAPE MOBs and the such when doing these workflows. That is especially painful in a file based world where each clip is its own unique name. Only in some file formats, if embedded was used such as Arri Alexa ProRes workflows does that become an issue to be mindful of, since AMA does not use embedded anything.
Starting dailies workflow in Resolve, AMA linking and vice versa will use both Source File and Tape, but since v6.5. one has the ability to relink between those two columns provided the metadata value is the same. With v7, you can use any column as source to relink on, and any of the timecode columns.
Te issue here, “seems” to be inconsistent REEL ID creation which should not happen if properly managed.
Michael
-
You need to download the most recent version of 6.5.4 from the Download Center.
Michael
-
Instead of using AAF, export the individual clips as MXF/DNxHD36, put the, into the mediafile folder and drag clips from MediaTool or by importing the msmMMOB.mdb from the mediafile folder that contains the media. What does the TAPE field say the? Any difference?
Also, from the conformed sequence that you color corrected, are you exporting out a new AAF or exporting same AAF. It’s a subtle but important step in roundtrip workflows.
Michael
-
Are you syncing in Redcine X, or is this audio recorded to the R3D file directly? If the latter, try exporting BWF from Redcine for a few clips and import those to see if the levels are the same or not once in Media Composer. This will start the process of elimination as to what the issue might be.
Michael
-
In v6.5 you could relink between TAPE and SOURCE FILE, or TAPE to TAPE or SOURCE FILE to SOURCE FILE. In v7, you can relink based on any column as source and any timecode column. A clip in Media Composer will have either TAPE or SOURCE FILE with metadata. It is very rare to not have either one.
I am going to assume you started AMA, went to Resolve, and when the clips get rendered out of Resolve, the REEL (as seen in the media pool) should be the same. When coming back to MC you can relink to selected if you have to and set SOURCE/TARGET as common REEL. I am not a fan of modifying TAPE, especially in a file based world where each clip is its own source unless the camera creates embedded REEL.
Michael