[Michael Phillips]

Another useful one that you don’t read about in the marketing materials is the ability to export ISO audio tracks now in QT and BWF. The next step would be to insert the track name (if entered) into the export files itself; for example the track info in the BEXT chunk of the BWF file. Would be great for deliverables such as 5.1 etc. Right now I do that my opening the BEF file in WaveAgent by Sound Devices and entering it there, but it could be done all in one step.

Michael

Michael Phillips

[Michael Phillips]

Select one or the clips:

1. Single frame advance key moves all frames + 1 frame
2. 8/10 frame advance key moves all frames + 8/10 frames
(reverse is true in both cases)

On a single clip:

1. Load and play in source monitor to desired frame and Mark IN
2. Play directly from bin to desired frame and Mark IN

Then use the “got to mark in” (Q key) and all clips will go to that mark.

Michael

Michael Phillips

[Michael Phillips]

Yes it is a good thing (finally), but as the thread indicates, with R3D workflows and starting in REDCINE X with spanned files, it will not work as only AMA sees the filename as filename_001 for the first of spanned files whereas everyone uses the SDK to pass the filename and spanned files are handled directly without the need for the _001.

Hopefully this will be addressed in an update to the R3D AMA plug-in.

Michael

Michael Phillips

[Michael Phillips]

The MediaFile names is not what is used in the conform. The original filename is tracked within the bin and part of the EDL or AAF that is exported for Resolve. If you look in your bin, you will see the original ProRes filename in the SOURCE FILE or TAPE column.

Michael

Michael Phillips

[Michael Phillips]

Bring up these two columns in the bin:

Source File
Tape

AMA will put the source in the Source File while anything captured will be in Tape (unless a MetaCheater type method was used with mergeing into an ALE file).

If you start off AMA to start, then do the second pass and it comes in with sources as Tape, then you won’t be able to relink between Source File and Tape in anything pre-v6.

In v6 you can relink across Source File and Tape except for scenarios where a spanned file was used from RED and AMA. The it still won’t work.

Michael

Michael Phillips

[Michael Phillips]

Will do. I get to telecommute. 🙂

And yes, the issue is the same with any application using Avid’s AMT for MXF wrapped DNxHD and AMA. They still deal with the source differently when it comes to RED. There is no need to track the _001 in the filename since the RED SDK handles the relationship. I suggested that the change be done in the R3D AMA plug-in with version 6 to not add the _001. We’ll see what happens.

Hope you’re well! I might be in LA the week of the 12th. I’ll come by and say hi to the Mike(s).

Michael

Michael Phillips

[Michael Phillips]

I brought this up during beta that the relink across SOURCE FILE and TAPE did not work with R3D spanned files when one of the processes uses REDCINE X. The _001 as MMost points out breaks the string match expected. This is something Avid needs to address either in the AMA plug-in or in the Avid AMT SDK used within REDCINE X.

Michael

Michael Phillips

[Michael Phillips]

I would suggest you start here:

https://www.amazon.com/Mastering-Digital-Cinema-Industry-Handbook/dp/0240808746/ref=sr_1_7?s=books&ie=UTF8&qid=1321756321&sr=1-7

Michael

Michael Phillips

[Michael Phillips]

Make sure the name used for the source is the same as what it used in Media Composer. Also, in Media Composer, were the assets brought in via AMA or captured from tape sources?

Michael

Michael Phillips

[Michael Phillips]

Are you exporting the AAF and importing that as well?

Michael

Michael Phillips