RedCineX PRO build 2 AAF/MXF Bug

[Joel Barnett]

Hi,

Tried the new RedCine-X Professional Build 2 today, however I believe we have come across a bug.

After rendering out offline versions of our epic footage through RCX-Pro at 1/4 debayer MXF, we brought the ALE into avid and tried to relink the media.

The files did not relink. We then saw that the ALE contained timecode starting at 01:00:00:00 for the media. We then pulled in the AAFs as well, they seemed to have TOD timecode, but the reel name is simply "A" not "A001_C001_xxxxx".

We were able to relink to the AAFs however this is quite useless as the reel-names are incorrect, and would have to be manually entered.

I have attached a screenshot of the imported ALE (bottom red) and the AAF (top green)



Is anyone else having this issue.

Cheers,

Joel

[M Most]

Unless there's some specific metadata in the ALE that you're using down the line in post production, you can always put the MXF files directly in a numbered folder under the Avid MediaFiles/MXF tree. When Avid starts up, it will scan that folder and create 2 files, one of which is the .mdb file. If you create a new bin, and drag that .mdb file in from a Finder window, it will automatically populate the bin with all of the master clips, based on the metadata in the MXF files themselves. However, as I said, if you need some of the additional metadata (camera settings and the like) you'll still need to relink to the information in the ALE.

[Joel Barnett]

I am aware of this. However all the mxf media (when using media tool or draging in .mdb file) have the wrong metadata. They do not have the correct reel names (reel name is 'A') , which is why I cannot relink the ALE in the first place.

Sure the clips will import when doing your suggested method, however it wont be of any use when it comes to preparing EDLs and will require all the reel names of the clips to be entered manually.

[MichaelP]

Yes, I notice this over the weekend and put a "caution" thread in the Avid forum about using REDCINE X PRO. I have already alerted the devs at RED as to the issue.

Michael

[MichaelP]

David from RED responde in the other thread that this is fixed in the next release of REDCINE X PRO (v3) and is not an issue in REDCINE X 501.

Michael

[Jesse Korosi]

Hey guys,
I had been going back and forth with David from RED about this issue when the release of version 2 first came out. It has indeed now been fixed in version 3 and as always, I have to say they were very quick to make this fix and come out with the next version which was great to see!

Cheers,