Help Getting Sound from r3d files

[vincelucero]

First off I understand we are in the beginning stages, and so far the camera has excelled in all aspects of production. We are very happy.

I have a huge challenge I need help with. We shot an interview 4k 16x9 and we are experiencing the same challenge from build 13 which is half of the quicktime is messed up (not half of the clip, but the bottom half of the frame through the entire clip) For small clips quicktime opens them fine (except for the corrupted bottom half) I can export the sound no problem, but for the interview it is a series of 2gb files that 1 quicktime points to. The quicktime won't ever open. This only seems to be the case for 4k 16x9 with multiple r3d files.

Thankfully we shot most of our interviews 2k 16x9 and they work perfect, as well as the day before we did 3k 16x9 and they are fine. We have never really worried about the 4k 16x9 messing up as redcine reads them fine and we still have our footage.....but redcine and redalert, as far as I know, do not export sound.

So is there any way on this planet to get the sound out of the r3d file. I have searched the forums for this answer but all I find is the sound is located in the quicktime proxy (WHICH CAN NOT PLAY!), and I need the sound from this one interview.

Thank you in advance for anyone from the red team to the forums who can help me solve this.

mahalo
scott

[Ken Corben]

If running QT 7.4 or above use one of the mac hacks to reinstall QT 7.3. This solved all of my problems in REDCINE, RED ALERT and QT player from camera generated proxies.

[vincelucero]

Thanks Sharkguy. Unfortunately didn't work for us. We've tried on multiple macs.

[Scott Mason]

I actually posted under vince's name to start this thread, but it is for our company.....

So in case anyone can find a fix that would be great (especially the members of red.) I know they are working on getting sound out of red alert and/or redcine so I am not worried. For anyone who is reading this looking for similar answers I have saved most of the clips that were shot 4k 16x9. FCP crashes when you import them, quicktime sometimes crashes when you scroll through them....so I opened the reference files and export immediately and I get my sound. I was able to save almost 20 clips this way (then export picture from redcine) but 3 clips crash when they are opened in quicktime so I have no way to get the sound. 1 is very important, 1 is MOS (thank god) and the third would be nice, but not as important as 1. The 1 clip is a series of r3d files and won't open on any computer in any ap. So I guess our only hope is red to find a way (quickly I hope, the show airs in a few weeks) to give us sound on our redalert, or redcine exports (hopefully redcine, as the same files are corrupt in redalert, but fine in redcine)

Red team - I would be glad to mail you a disk with the shot on it if you want to trouble shoot. I know you guys are busy and it is our fault for shooting 4k 16x9, but every other format works perfectly and I swear the 4k 16x9 worked when we tested it the day before but alas I see myself being very gun shy of 4k 16x9 for a little while (it is all good as the 2:1 works great, 16x9 is just easier for the conform but who really cares when it's 4k ;)


mahalo
scott

[Nick Shaw]

Not ideal I know, but doesn't build 14 now play back audio on the camera? If it was the only way, you could put the shot back onto a CF card, and use the camera to dub the audio onto something else. If you used the HDMI output, you could get the audio digitally (and strip it out with eg a Gefen HDMI switcher, or capture it with something like a Blackmagic Intensity) so then all you would need to do would be to line it up manually with the picture.

[David Didato]

What about the command line tool? Anybody tested if audio exports through it?

[leftydanger]

This is horrible news. I'm on a Macpro and using Quicktime 7.3 and can't get any 4K 16x9 proxies to open. It immediately crashes QT. (We shot some stuff on 3k and have had now problems with it.) Is there no way around this? Besides the aforementioned use the camera as a playback device strategy.

And if nothing works, shouldn't everybody be warned that if you like sound on your movies you can't shoot 4k 16x9? Because right now I have two hours worth of interview that I can't get any sound from.

Please help,
Joel

P.S. Everything looks beautiful. We love the images. And the RED is the best thing since sliced bread and Final Cut Pro. Just need that sound.

[Deanan]

We'll try to get you a tool to extract the audio.
In the meantime, can you try to remove the QT component
from your system. Reboot. Then open the QT wrappers in
QT player or FCP and extract the audio channels.

[jbeale]

The 4k 16x9 problem (doesn't play in Quicktime, Red Alert, etc.) comes up here in various threads literally every day now, so I agree there should be clear warnings put everywhere. The updated code to handle 4k 16x9 is supposed to be a few weeks out, but until that time, I suspect we will continue to hear about it daily.

[Deanan]

Sometimes I wish we'd never turned it on until we were fully ready on the software side.

[jbeale]

Not enabling the feature is safe, of course obviously there are many people happily shooting with it also who would be screaming if you didn't have it...
if I may be so bold, I think the key to managing the "bleeding edge" features strategy is to really emphasize what is and is not working, in every way possible. Right now, advisories and warnings about 4k 16:9 aren't very prominently displayed in places that I'd expect it would be, like red.com/support.

[Kenn Michael]

Exactly. Owners and shooters shouldn't HAVE to be browsing reduser.net to find out the scoop on important compatibility issues.

[leftydanger]

We'll try to get you a tool to extract the audio.
In the meantime, can you try to remove the QT component
from your system. Reboot. Then open the QT wrappers in
QT player or FCP and extract the audio channels.

Thanks for the quick response. Could I get you to dumb down your answer for me. By "remove the QT component" do you mean uninstall or kill the preferences or just trash the application? And if I do this, how do I then open the QT wrappers after reboot? And just to be clear: the QT wrapper is the same as the proxy, right?

Thanks in advance.

Joel

[Deanan]

Go to your system drive / libarary / Quicktime and move the file REDCODE.QT.component.

Then reboot... you can still open the wrappers in QT player
even with out the component. You'll see a white image but
then open the properties for the movie. Select the sound track
and timecode track and click extract.

Hope that helps.

[Dj Joofa]

Then reboot... you can still open the wrappers in QT player
even with out the component. You'll see a white image but
then open the properties for the movie. Select the sound track
and timecode track and click extract.

Hope that helps.

I saw a number of threads recommending audio extraction from QuickTime files. I think that will work with only pro version of Quicktime. Those users, who do not have pro version of QuickTime, can use the following application that I skimmed out of a project that I was working some time ago. Its mostly Apple code with some addition of mine.

http://www.reduser.net/forum/uploaded/7051_1205978376.zip

Unzip it and you are good to go. One you run and load a QT file, please go to Window->Extract Audio to extract it. You can define in and out points if you want to, and preview the audio within in and out points, before outputting it.

I have not tested it on any of Red proxies, but I hope that it works. Currently, it is only for Mac users, both PPC and Intel.

[leftydanger]

Go to your system drive / libarary / Quicktime and move the file REDCODE.QT.component.

Then reboot... you can still open the wrappers in QT player
even with out the component. You'll see a white image but
then open the properties for the movie. Select the sound track
and timecode track and click extract.

Hope that helps.

Thanks. That worked splendidly.

[Deanan]

Great!

[dmartos]

Compressor can extract the audio out of the .mov files and create friendly .aiff files. The only trick is to close its preview window before creating your batch. (Otherwise it may crash in the attempt of generating the preview).