Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

ProRes Spanning

I tried using the utility on ProResLT files from the Weapon. The app gave an error : "ERROR: in /Volumes/Macintosh HD..... unsupported audio compression in movie....."

Anyone have the same error or have a successful go at it? Looks like the audio is Linear PCM 32 bit Endian...
 
First time shooting on a RED and handling the data myself a week ago. Having 100+ folders for a quick shoot was pretty time consuming. Had to open each drop directory, select each prores clip, and copy the lot over. Am I missing a faster way to import .mov or even .r3d? Much thanks
 
Randy Panado said:
First time shooting on a RED and handling the data myself a week ago. Having 100+ folders for a quick shoot was pretty time consuming. Had to open each drop directory, select each prores clip, and copy the lot over. Am I missing a faster way to import .mov or even .r3d? Much thanks
Click to expand...

You do know you can search folders for file types correct? Give *.mov a try if this is your chosen method.

I highly recommend not touching the folder structure regarding .R3D files. You're going to shoot yourself in the foot. 3rd party NLEs can "see" this folder and file structure.
 
Phil Holland said:
You do know you can search folders for file types correct? Give *.mov a try if this is your chosen method.

I highly recommend not touching the folder structure regarding .R3D files. You're going to shoot yourself in the foot. 3rd party NLEs can "see" this folder and file structure.
Click to expand...

Thanks Phil. Still learning the r3d workflow (which is why I used the prores files to deliver). Appreciate the reply!
 
Eric Haase said:
I tried using the utility on ProResLT files from the Weapon. The app gave an error : "ERROR: in /Volumes/Macintosh HD..... unsupported audio compression in movie....."

Anyone have the same error or have a successful go at it? Looks like the audio is Linear PCM 32 bit Endian...
Click to expand...

Eric, yes we just had this error yesterday.
 
kylebainter said:
Eric, yes we just had this error yesterday.
Click to expand...

SO how are people using the ProRes files recorded by the camera then? The camera has been out several months now right? RED should have really offered a solution to this when the feature was enabled, similar to how Convergent Designs published a software utility for the way their recorder records segmented ProRes. Put the feature in REDCINE- Quicktime stitcher or whatever you want to call it.
 
Would you prefer to have a new large quicktime written (replacing the spanned clips) or having a very small .mov file referencing the original clips into a single one but requiring to keep original files in place...
 
Thanks Mika! ;)

Probably efficiency wise the best would be a QT ref file but for editorial maybe a single file would be better?

Anyway R3Ds would still be splitted so...
 
Mikael Lubtchansky said:
Would you prefer to have a new large quicktime written (replacing the spanned clips) or having a very small .mov file referencing the original clips into a single one but requiring to keep original files in place...
Click to expand...

I would prefer one big quicktime, so that there are no extra steps required. Hand prores quictimes to the client and you're done. no explaination, just like with the Alexa.
 
Here is what the utility should do:

Take all .mov ProRes (or DNXHD mxf) files out of RED folder structure (copy is OK) and put them in a single directory or chosen new folder structure. IF prores or dnxhd mxf files are spanned for a particular clip, combine the spanned files into one files, maintaining the original filename (same as the R3D file) and original continuous timecode. Editor should be able to use these new files and then seamlessly match back to R3D for online, same as he would if the files had been transcoded from R3D files.

I bet everyone would be willing to pay at least $20 for this simple utility, although RED should have made one included with the camera.
 
Eric Haase said:
I tried using the utility on ProResLT files from the Weapon. The app gave an error : "ERROR: in /Volumes/Macintosh HD..... unsupported audio compression in movie....."

Anyone have the same error or have a successful go at it? Looks like the audio is Linear PCM 32 bit Endian...
Click to expand...

My test using the utility was fine but I didn't have audio on the files. I'll redo the test with audio.
 
Hello

I may have something to fix this...

so I'm looking for 3 (and only 3 sorry in advance) good beta testers willing to :

run on El Capitan
run on latest beta camera FW and record some prores on dsmc2
play with premiere and other apps to verify conforming back to R3D is fine at various speed
send some usefool feedback

With this tool for now you can :
- create small reference mov link files inside the .rdc folders (will break if the file is moved so needs to be re-generated for now)
- export whole new merged PRORES clips to a separate folder (takes more time and disk space obviously)

It is only for OS x 10.11 and pre FW 6.3 camera files seems to have issues being referenced for now...

#bigthingshavesmallbeginings


13178775_910503579061029_8001660771573396902_n.jpg
 
Your the guy to do it. Foolcontrol is amazing
 
Jon Dishler said:
Sent a PM
Click to expand...

Thanks Jon. Good if you can test on fcpx too. Will email you.

Closed beta now. thanks guys and hopefully good news soon for everyone else.
 
You must log in or register to reply here.
Back
Top