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

Cody Stauffer

Cody Stauffer

Well-known member
Joined
Oct 29, 2012
Messages
137
Reaction score
0
Points
16
Location
Santa Monica
My 2k ProRes 4444 mov's are spanning, maxing out at 4.16GB each. Is there any workflows making these whole takes again when cutting I'm Premiere?

Thank you for any help!

Cody
 
R3Ds do the same thing. Is there a software problem in Premiere with reading them as a single file?
 
Yeah thats sorta what I'm asking. Not sure if I'm doing this wrong or if I need to something else... idk? Using media browser within Premiere to import.
 
I have the same problem. One shot is spanned into multiple 4Gb R3D files. Adobe Premiere and other programs combine these multiple files into one clip. However, the proxy files are spanned into multiple prores files as well with a max size of 4Gb. Unable to load as one clip into premiere. The ProRes loads as multiple separate clips. Really not a time saver as now have to combine all the separate clips to make one clip.
 
Bob Gundu said:
Someone do the math on the time to combine QuickTime files into one, versus rendering out proxy files from the R3D. :laugh:
Click to expand...
or exactly how long a 4gb file of prores 422 HQ is and proess 422 LT
so we can notify producers and post producers how long there clips will be.
thanks!
 
If the file system is FAT32, the files will always be like this.

I just don't understand why the file system for Red needs to be that. Use exFAT instead and we will have single files for both R3D and ProRes. But I'll guess we need a new camera for this since you can't change this as a firmware update?
 
FAT32 allows you open files on Windows 95 :cheers2: Kidding.

exFat is only recommended in flash memory storage and other external devices only. FAT32 allows for better data recovery. Them guys at RED love the details. :)
 
have you tried the Media browser in Premiere? It works with other spanned files. I have no red ProRes Files at the moment so that i could test it myself. But i Know that it works with the spanned R3D Files, and also with spanned AVCHD Files.
 
Bastian Meier said:
have you tried the Media browser in Premiere? It works with other spanned files. I have no red ProRes Files at the moment so that i could test it myself. But i Know that it works with the spanned R3D Files, and also with spanned AVCHD Files.
Click to expand...

As many other threads have pointed out, Premiere Pro's current release is woefully behind the times in terms of what RED started shipping in October of last year. We have been told that there is a decently-working beta that corrects at least some of these problems, but there's no public information about what what this beta contains or when it might be released. I would suspect that there will be a release around NAB, and it might well include the feature of recognizing spanned ProRes files in an R3D directory structure. But it doesn't do that right now, along with many other shortcomings in their RED support. Which is why I've started all my new projects in DaVinici Resolve 12.
 
yeah its very unfortuate. if you shoot at 4K HQ you will get :45 clips. and they are buried in sublayers of folders. not happy
 
A few concepts.

Quicktimes can indeed be re-wrapped.

As for workflow, there needs to be a more intelligent "sniffer" in several 3rd part NLEs to find and separate Quicktimes from REDCODE RAW. I know of one company working on that right this second, but CBB. Could be better.

Folder Structure/File Structure. RED adheres to a specific folder structure involving .RDM/.RDC/ (or simply magazine/clip) then that contains the .R3D or .MOV as well as the .RMD and more recently .RTN (preview thumbnail). Some sniffers are getting confused at this level as they detect the .R3D and not the .MOV. This needs to be improved upon.

I don't think they overall folder structure will change as it's been part of the workflow for years now and so many tools are dependent on it.

More or less what needs to be solved is more intelligent "sniffing". In terms of .MOV files that go straight to client or straight to air, a simple re-wrap tool would be handy. I've written a simple script to just extract .MOV from my mags and that works general editorial workflows.
 
kylebainter said:
Convergent design makes a prores stitching tool for their recorders. Not sure if it would work for this or not...
Click to expand...


Gave this software a go today. Brilliant!

You can use this to do the following after you pick the root folder on the MiniMag (or any folder on your computer)
1. It will scan each R3D folder to look for sequential Quicktime files.
2. If it doesn't find quicktimes, it will just copy the the R3D files to the destination location.
3. If it finds Quicktime files, it will combine them into one quicktime files and then rename it to not include the 001.
4. say awesome!


https://www.convergent-design.com/c...ple-prores-transfer-tool-v2-2.html?Itemid=519
 
Thanks Bob!

Have you tried it it works ok to reconform to R3Ds after the edit?

Everything matches well?

Is Resolve/Premiere able to match the R3Ds well if using the joined ProRes movs?
 
You must log in or register to reply here.
Back
Top