X2Pro not working with .r3d files

Hi I'm having a similar problem with .r3d files and wondering if there is a newer or non-standard version of X2pro available as per the discussion below. my problem is the AAF creation returns this error:

The following fatal errors were found:
Processing element ProjectElement
Processing Audio element
Processing element AudioElement
Extracting audio
Extracting Audio
Processing element SequenceElement
Processing element VideoElement
Track number exceeds number of tracks in asset [A004_C054_0615OQ]
Processing element SpineElement
Processing element ClipElement
Processing element GapElement

No AAF file has been generated.
X2Pro Audio Convert 4.2.2

I tried eliminating the file A004_C054_0615OQ completely to check if it was that single file causing problem. AAF failed again listing a different .r3d problem.

Advice asap greatly appreciated. here is the fcpxml

thks so much,
Ryan

Dear Josh and Brendon,

If you upgrade to the latest version 4.0.29 we believe this is now resolved.

Yours sincerely

Josh, I have sent you an email

Hi Graeme,

Great news, that will be super helpful. Please send me the link.

I also have a colleague that owns a weapon + X2pro and having same issue. Can I forward you his email so you can send to him also?

Thanks,

Josh

Brendon, I have emailed you directly

Hey Graeme,

We have a couple users having issues with RED Weapon audio in our office that are trying to turn around projects today. Can you send me the updated version to see if that will fix our issue?

Thanks!

Josh,

We now have a version of X2Pro that uses the newest RED SDK so it should be able to convert your project that uses RED files created by new RED cameras and/or firmwares. Unfortunately we still can't get it into the app store without help from RED, but I would like to offer you a temporary licence for a version that is licensed outside of the app store, and isn't subject to the same restrictions.

If you want to try this version, let me know and I will forward you download details.

Dear Josh,

Apologies for the delay, thought you would appreciate an update, the current r3d sdk if incorporated in X2PRO will allow this media to be processed (we tested and proved here), however this SDK cannot be included in an X2PRO release as it will fail AppStore authorisation. As such we are waiting for the next version of the R3D SDK, which probably can.

If you are desperate we could look at building you a RLM version of the X2PRO code that would incorporate the current R3D SDK.

Yours sincerely

James

I think X2Pro might be struggling because your RED clips were created using a newer version of RED firmware than X2Pro 4.0.12 uses to extract the audio. I have been told that we are working on getting X2Pro to use the latest RED SDK, which will hopefully solve the problem.

Unfortunately not. FCPX won't allow you to relink the optimised files once removed from their folder in the project file structure - it comes up with some error message about the audio channels not being the same.

The only workaround that worked for me was getting XtoCC app and then exporting my project into Premiere, relinking media and then exporting an AAF that way.

Thanks,

Josh

Dear Josh,

Would be grateful if you could confirm that the workaround proposed by Graeme did the trick.

Many thanks.

Perfect. Thats what I thought.

Thanks,

Josh

The MOVs that FCP creates in transcoded media/high quality media is what you want to relink to, but you need to copy/move them out of that location first.

I think that's what you are saying too.

Sorry just to clarify.

'If you do this, make sure you relink to copies of the optimised media, not the actual files that FCP X creates because otherwise it may remove the optimsed files before doing the relink, and the end up relinking to nothing, leaving you with black&silent clips in your project.[/li]'

I'm going to pull the .mov files out at route directory level in the folder and reconnect my project to these manually. Its creating a load of .movs in - transcoded media - high quality media. Is this what you mean?

Thanks Graeme, giving that a go now.

The firmware I'm running now is 6.3.47 but shot this footage last year so was probably on the previous version.