Problem extracting audio from r3ds fc 10.1.3

David,

I think RED may have told us about a the SDK, but if they did it obviously slipped through the cracks. Hopefully this won't happen again.

As we don't have access to any RED kit here, it would certainly be useful for everyone if you were able to try X2Pro against your kit whenever you are aware of any changes that RED make.

As we've just released this new version, our reviews have been hidden behind an "All Versions" button. We would be very grateful if you could find the time to leave a review for this new version.

OK. Got it. I really should run a quick test once in a while when a new RED SDK is released to avoid these kinds of potential deadline disasters.

Battistella

David,

v2.4 of X2Pro is now available so you can delete the beta and update from the app store.

Thanks for your help in testing the beta.

Hi David,

Thanks for letting us know.

It has been submitted to the app store, so when the next release is approved by Apple, it will include this fix.

Have tested this build on the "old" sequence and it does open and read the Dragon R3D's


battistella

Unable to test yet as I am on the road through the end of the week.

Did you try this beta version? Was it able to convert your project with the R3D clips?

We have a beta version of X2Pro which we think should solve the issue you are hitting here with RED clips.

Would you be interested in trying it and letting us know how it goes before we submit it to the app store? If so, it is available on our FTP site using the same credentials as you were using previously.

The beta will stop working after about a month and the app store approval process often takes weeks, so please let us have feedback as soon as possible so we can decide if it is ready for submission to the app store.

Not yet I'm afraid.

Any movement on this Graeme?

We'll let you know as soon as we have a version that you can try.

Just as an FYI.

I sent you an r3d trim. There should be two tracks of empty audio in the trim. If there is no audio then the camera's audio tracks were disabled. (I will double check my r3d trim settings)

When I trim an r3d using RCX then it is creating a NEW R3D file (from the original) this is why it might be reporting as a RCX clip.

I suggest you implement the new SDK from RED as they now have released a new camera sensor (red Dragon) and the R3D file it records is slightly different to the R3D recorded by a RED EPIC MX camera.

I suspect this is all SDK related on your end as this is Dragon camera footage.

So, in a few weeks, when there might be something to test, please let me know. In the meantime I will find some kind of workaround. What a drag.

Battistella

David,

I can see that it is a trim because it is 6.67 seconds long where the original (according to your first fcpxmls) was 17.95 seconds long. I can also see that it was last modified by REDCINE-X.

The clip you just uploaded appears to have no audio tracks, which means that I still can't reproduce the issue here. I really need a clip with audio tracks otherwise X2Pro will just skip over the clip completely and will just create the AAF.

Is the original version that causes the error in X2Pro straight from the camera, or has it gone through REDCINE-X too?

If it's too hard to get one of the original files with audio to us, it seems likely that it's the SDK version causing the error, and we are planning to update X2Pro to use a newer version in the next few weeks, so we could give you a version to try when it's ready?

FYI. it is a r3d trim of the whole file. including audio. (even though there was no audio recorded).

battistella

Graeme Robinson wrote: David,

If there is no audio in the R3D files, X2Pro doesn't try to extract the audio so it will not have any errors to report. Both of the clips that you uploaded had no audio, so I'm unable to reproduce the error that you are seeing.

It doesn't matter whether the audio is completely silent; If there is any audio at all in the R3D file (that hasn't been disabled in FCP X) X2Pro will try to extract the audio (even if it is silent) and put it into the AAF.

In order to reproduce the error that you are seeing, I need a clip with audio that we know causes the issue on your system. This could be the one I mentioned in my previous post or a smaller clip that has audio and is known to produce


The FCPXML never references proxy media, it always points to the original source media. This is probably because the proxy media is only used so that users can edit very high resolution media on systems that would struggle with editing the full resolution media in real-time; it's not intended to be used outside of the editing application (FCP X).

Im saying that once FCPX renders a proxy file, including 24 bit 48K audio, then when it comes to audio, the XML should reference the proxy audio instead of trying to extract that audio from the r3d, or we should be able to tell it to reference that audio. Would save MOUNTAINS of time.

battistella