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

Cineform v Red Raw Comparison Shots?

There is little point in the comparison, as the source will always be Redcode. If the Rawport wasn't discontinued, then the comparison would have been possible. While CineForm RAW can be applied to ARRI, Dalsa, Phantom or SI footage, different cameras and therefore different results. For Red foootage, CineForm is an online post and DI format, just as we are for every other compression or non-compressed camera source. CineForm 444 as DI is quality visually equivalent to posting with DPX files, just 4 to 7 times smaller files. We look forward to implementing the Redcode SDK, allowing easier conversion of Red media into the CineForm workflow.
 
so we will primarily be do 4:4:4 CineForm encodes until the SDK supports RAW (faster transcodes to small file sizes.)

David, how does this compare to the news that R3D files will be handled "natively" by Premiere Pro CS3 now? I still don't understand how that is going to work. Does that mean RAW-style CCing can be done in Premiere Pro or AE, or will the RAW color and exposure settings have to be done at some earlier stage?

Any ideas on how the RED/Adobe workflow without Cineform will work compared to with Cineform, now that Adobe is apparently supporting RED? I understand you cannot be completely objective, but still, I thought I would ask, since you know more about this stuff than most anyone here.
 
Native support has no impact on us, if anything is helps a little (saving us some work.) Remember most of the cameras we support have a native Adobe mode, users simply choose a CineForm workflow for a better experience. We will have a compelling workflow, but there is no point discussing the details when none for the components involved are out yet.
 
There is little point in the comparison, as the source will always be Redcode. If the Rawport wasn't discontinued, then the comparison would have been possible. While CineForm RAW can be applied to ARRI, Dalsa, Phantom or SI footage, different cameras and therefore different results. For Red foootage, CineForm is an online post and DI format, just as we are for every other compression or non-compressed camera source. CineForm 444 as DI is quality visually equivalent to posting with DPX files, just 4 to 7 times smaller files. We look forward to implementing the Redcode SDK, allowing easier conversion of Red media into the CineForm workflow.
__________________
David Newman
CTO, CineForm

Thank for shot of truth.

Much appreciated.

Files size 4-7 time smaller?

What is the ETA on a beta?

Thanks

Tek
 
QT proxies versus CineForm proxies on RED

QT proxies versus CineForm proxies on RED

I was always thinking about CineForm as a proxy file to the original RAW whatever it comes from.

Kind of like the QT proxy file on RED that is saved together with the RED RAW file when you finish the clip.

The only difference is that CineForm is fatter proxy allowing you to play real time right from the CineForm file without necessity of converting it to the QT but rather converting it to the CIneForm.

Is that right or I am getting confused here?

I would love to have CIneForm proxies created at the end of the clip on RED during the “POST” instead of QT proxies.

It looks like Apple converted itself right now to Apple Mobile and theirs focus is there, so counting on Apple to be serious right now about non profitable segment of theirs business it is bit unrealistic.
 
Tek,

4-7 times smaller than DPX (so there is no confusion.) 4K CineForm files are typically a little bigger than R3D source files.

Beta? CineForm Prospect 4K and NEO 4K have been out for a while, from DPX sources you can start using these products now. If you asking for R3D support we looking forward to receiving the SDK just like all other vendors.
 
The best idea would be to have a choice on the camera to create CineForm proxies or QT proxies.
David, talk to RED about it. QT is good for previews but not for work and grading real time.
CineForm proxies are good for both.

I had this idea of shooting to the CF cards memory and when camera is idle to create CineForm proxies to the hard disk. Camera is idle most of the time so when not recording, there is plenty of time to keep background process running doing something useful.
 
The only difference is that CineForm is fatter proxy allowing you to play real time right from the CineForm file without necessity of converting it to the QT but rather converting it to the CIneForm.

Is that right or I am getting confused here?

I would love to have CIneForm proxies created at the end of the clip on RED during the “POST” instead of QT proxies.

RedRushes does a fine job for us R3D to 720p Full/Half Res.

I think I would try Cineform for DPX replacement to save money on space.

At $2000.00 and drive cost is 50-75 cents GB it's making sense for now, when drive space drop to 10 cent per GB then there is no need.

I will do DPX all day.

Especially at that price $2000.00 USD

Tek
 
Problem is that Red Rushes do not allow you to grade the RAW and CineForm proxies could actually allow you to grade in 32 bit space without modifying the REDRAW.
The idea is to get out of RAW in real time only the data that is necessary for grading and only after you are happy with the final product, you can work on RAW.
DPX is too heavy and there is tons of unnecessary data in it for grading.
We need something lighter in terms of amount of data used.

All this RAW, you need only just for final product but for grading you need something that is intuitively predicting what you do need for the next step in grading process. Also previews in real time do not need all the data from the RAW.

Sure once you want to see it on 20’ preview screen you have to do final transcode but for the grading 1/10 of data is more than enough and you get it on demand when needed.
 
I was always thinking about CineForm as a proxy file to the original RAW whatever it comes from.

Kind of like the QT proxy file on RED that is saved together with the RED RAW file when you finish the clip.

The only difference is that CineForm is fatter proxy allowing you to play real time right from the CineForm file without necessity of converting it to the QT but rather converting it to the CIneForm.

Is that right or I am getting confused here?

Andrew,

The Cineform files are actually online quality. There is no need to conform like you do with proxies.

Transcode from Red RAW to Cineform 444. Then edit, grade, export your master file... you're done. Print it to tape, master it to DVD or Blu-Ray, or do a film out.

Once you have the files in the Cineform 444 format (codec), it's the simplest most straightforward post process possible.

-Thor
 
"best idea would be to have a choice on the camera to create CineForm proxies or QT proxies. David, talk to RED about it"

not going to happen !! the camera shoots Red raw = red proxies not X proxies ...
based on posts on DVXusers back in ? summer/fall ? 2006 , i would say Red & Cineform had talks/meeting = there will be NO Red camera processing cineform ...
 
CineForm requires trancoding REDRAW to CineFormRAW

I was thinking along the lines of creating CIneFORM Proxies that do not require transcoding but if REDRAW is present in the same directory (or linked) it works like transcoded CineForm.
 
Andrew,

The Cineform files are actually online quality. There is no need to conform like you do with proxies.

Transcode from Red RAW to Cineform 444. Then edit, grade, export your master file... you're done. Print it to tape, master it to DVD or Blu-Ray, or do a film out.

Once you have the files in the Cineform 444 format (codec), it's the simplest most straightforward post process possible.

-Thor


Hey Thor,

When do you transcode? Can you transcode from redcine to Cinefrom 444?

Thanks
 
Back
Top