Welcome to our community

Be a part of something great, join today!

  • 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 :)

Exporting R3D for stock footage

Ami

Banned
Joined
Oct 18, 2010
Messages
2
Reaction score
0
Points
0
Hi everyone.
I have shot on Red last Saturday,green screen footage and 4K in resolution.
The main aim is to distribute the shots as stock footage.

Now, the problem I have is - which is the best codec that I need to use, which will keep the 12 bit 444 format of the Red, but will be easy on the weight?

I have searched the entire web and haven`t found any proper answers. everybody kept sayin` different answers. I hope you can help me out.

I have tried so far to export to:
DPX - too heavy
Tiff - insanely heavy
Cinform - not heavy but still big [plus, can anybody that does not have the software see the footage?]

I have heard about Cineform raw and about "storm".

And another thing, I don`t want to lose the resolution, if there was a way to cut the original files that could be amazing. but can`t do that on any app. at least not that I found.

Ami
 
Hi Amy,
welcome to the forum. I shoot about 90% for stock on my RED so have a bit of experience here.
That said, your going to get a different answer from probably every person responding....as you well should since we all have our favorite codec or have experience using one more than the other.

....What you'll also find is WHAT IS YOUR END MARKET? what do your stock footage clients MOSTLY require? if for TV or for FILM? what?
...for me it is mostly tv and at 29.97 although i find myself going back and forth from 24 to 30. As for codecs....most houses i work with want delivery in Prores. But that should be asked of the stock house you intend to keep your work with.

My Method:
*originally i transcoded all my R3d files to prores 4444. After six months i had WAY too much in digital files. So, after analyzing my footage and options I chose to go with Prores 422 HQ with Crhoma enabled. This (in my opinion) allows you or anyone plenty of room to do any further color work and i really don't see the advantage of transoding to prores4444 over 422HQ for 99% tv work. Saved me a HUGE amount of disk space as i'm embarking now upon 20TB of footage and THEN---you have to back that up.....so sure great to keep it all 4444 or other heavy resolutions, but space becomes a factor at some point if you are shooting a lot of stock.

**I realize my method may not work for others, but it works for myself and mainly it is what my clients expect and work with regularly.

Keep in mind, you never loose access to transcode to ANY codec just by going back into RCX or soon Storm and accessing the R3d your client wants and spitting out that clip in the desired codec.

In fact i'm not considering making only proxi files and then when asked for a clip, can access it via clipfinder and chug out the file for my client as required.

Good luck
 
And another thing, I don`t want to lose the resolution, if there was a way to cut the original files that could be amazing. but can`t do that on any app. at least not that I found.

STORM can't currently trim R3D files, although it will be able to in future. You CAN trim R3Ds with the latest version of REDcineX. That would seem to be your best solution. The best way to maintain quality is not to transcode, although you do rely on your end users understanding how to work with R3D.
 
STORM can't currently trim R3D files, although it will be able to in future. You CAN trim R3Ds with the latest version of REDcineX. That would seem to be your best solution. The best way to maintain quality is not to transcode, although you do rely on your end users understanding how to work with R3D.

That's our vision: don't transcode until you absolutely have to, preferably at and for final delivery. We know that is a bit of a dream right now, but really believe that in a few years it will be the norm. Why ditch some of your image if you don't have to?

Back in the practical world ... we appreciate you'll need to deliver whatever your clients ask for, so we're making that possible in STORM (including trimmed R3D as soon as we can).
 
That's our vision: don't transcode until you absolutely have to, preferably at and for final delivery. We know that is a bit of a dream right now, but really believe that in a few years it will be the norm. Why ditch some of your image if you don't have to?

Back in the practical world ... we appreciate you'll need to deliver whatever your clients ask for, so we're making that possible in STORM (including trimmed R3D as soon as we can).

That being said....when your footage is also posted on a website....for example Ocean Footage; Mammoth HD; Artbeats and many others....they will need files in the form of a codec in order for potential customers to preview said clips...as well as a way for production companies to review a variety of submitted clips. Yeah...i agree, until the time comes where everyone lives in digital and up to date software etc.....but that's a ways off IMO when it comes to selling stock to potential productions or for sale on stock websites or houses.
 
That's our vision: don't transcode until you absolutely have to, preferably at and for final delivery. We know that is a bit of a dream right now, but really believe that in a few years it will be the norm. Why ditch some of your image if you don't have to?

Back in the practical world ... we appreciate you'll need to deliver whatever your clients ask for, so we're making that possible in STORM (including trimmed R3D as soon as we can).

.....that begs a question....will Storm allow for archiving and creating proxis of R3D (graded footage) for review when scanning for footage/shots based on metadata ....say, i'm looking for an orca hunting sealions or a jewel eel foraging in the sand.....??? then i could view all relevent proxies and finally based on clients likes/needs THEN transcode out to that codec they request delivery on? Basically more concerned with the digital archival capabilities.
Thanks.....
 
  • Thread starter
  • Banned
  • #7
Thank you Johnny! I am going to try your methods.
Thank you Nick! it worx! wow!
Thank you Chris

I have another tiny question:
Since my material is all shot on green screen

http://www.youtube.com/kikoman522

Which codec is the best in weight and quality to deliver a duplicate of the original clip [for each clip] with alpha channel?
 
We also decided to offer our footage in ProRes HQ. If someone needs more colour depth and quality he/she could also download directly the original R3D-File from our site (which costs more). But because ProRes is still not used too much in the PC-World we also think about an additional distribution format.
By the way: does anybody knows how to generate proxies with Redcine X after trimming the R3Ds?

Cheers
Thomas.
 
ProRes 4444 can hold an alpha channel and is very close to keeping full quality.
 
.....that begs a question....will Storm allow for archiving and creating proxis of R3D (graded footage) for review when scanning for footage/shots based on metadata ....say, i'm looking for an orca hunting sealions or a jewel eel foraging in the sand.....??? then i could view all relevent proxies and finally based on clients likes/needs THEN transcode out to that codec they request delivery on? Basically more concerned with the digital archival capabilities.
Thanks.....

Johnny, that should work in STORM already. If you were viewing proxies in FCP then you could pass STORM an XML timeline of them and it would relink to the original R3D for you.

Hope that helps!
 
Hi guys,
So, Which codec is the best in weight and quality to deliver a duplicate of the original clip [for each clip] with alpha channel? [besides prores]
 
Back
Top