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

CineForm Officially Supports Red One

Jay A. Kelley said:
If Avid and Cineform ever worked together... That would be a game changing event wouldn't it?

I wish

Jay
Click to expand...
Jay, Jimmy is referring if AVID were Jaws and CINEFORM were chum. The point is: it's not if they were, 'cause to each its own.

If by any chance, AVID would buy CINEFORM this might be a great thing in any way other than as for the CINEFORM's owner(s) pockets. Not exactly for the typical CINEFORM customer. Only for the typical AVID customer.
 
Adobe's got a lot more money then Avid
and judging by how companies like Red, Cineform, ect are able to write plugins for them with far greater ease then for the others...I'd say Premiere has the most modern code base.

I'm pretty sure Red was working on Avid workflows just as long as Adobe.

If Avid and Apple don't watch it...Adobe will steamroll them in the next couple versions...(as soon as there audio issues are worked out)
 
joelnet said:
So if I batch process files on a PC can I then work with them under OSX and edit in Final Cut? Or is this whole thing really meant to work in Premiere on a PC?
Click to expand...

Currently the tool runs on a PC, yet it output is PC or Mac.

R2CF your.R3D new.avi -- generates a 4K 4:4:4 AVI
R2CF your.R3D new.mov -- generates a 4K 4:4:4 MOV

Unfortunately FCP can't do 4K, work around is to window to 4000x2048 (or similar.)

So the Mac equivalent is
R2CF your.R3D new.mov -r -(48,0,4048,2048) -- generates a 4000x2048 cropped RAW MOV ready for FCP.
 
And MetaFuze is free that can also be driven by lne command and be used in a multi node render for faster processing...

Michael
 
David Newman,

I tried encoding R3D file to cineform mov file running in my MacBook under Parallels under Windows Vista and used R3D file with audio. The output movie doesn't contain audio.

Is the support for audio not yet done?
 
And the quicktime movie doesn't have timecode?

My command script was r2cf ABC.r3d output.mov
 
The SDK doesn't have audio yet, so we aren't offering it, but we are ready for it. We have been told it is very close, so fingers crossed for a new SDK release soon. Timecode is currently going into the video sample (as with all source metadata data), and that is being currently read by Premiere on the PC. Based on the level of interest from Mac users, we will add a timecode track for MOV applications, sooner or later. A show of hands for Mac interest would be nice. We are focusing a little more on Adobe Premiere under Windows for the initial release (where this is posted) as we have the strongest workflow there.

P.S. Glad to hear is running under Parallels, we hadn't tested that.
 
Timecode,

It first when i read that the quicktime didnt have timecode I was like, why? Its a total Necessity.

But then, i thought about it. Cineform is an intermediate file format. That means only in disaster should you need to go back to the r3d files, and you would probably manage to get the same timecode back out of them. Its not really like your doing an online/offline with these things.. This is your footage for all intents and purposes...

Of course, having the timecode there would be nice....But I understand why you may not actually need it...
 
yes! mac please

yes! mac please

i used adobe on pc. and cineform, on pc.
i was happy with it.
then came the red.
i bought a mac. and i bought both finalcut studio pro AND Adobe cs3 for mac.
now it turns out the best solution will be Adobe and cineform, again.
i'm really glad to hear that.
BUT.
please. i'm not one of those guys who like to jump from one computer to another, pc, mac, whatever.
now i have a mac. it's lovely, fast and easy. I'm happy with it.
please, cineform, don't make me do mac/pc switching any time i need red footage.
go for a Mac version!

i'll be waiting for it to crossgrade my cineform licences.

thanks.
 
Alex, if you can run the converter on Windows (or Parallels or Bootcamp) you can create CineForm MOV files directly instead of AVI files. Choosing MOV instead of AVI is a simple parameter in the converter and the associated batch files.

The converted files can be used in FCP or PPro (Mac). Remember FCP has a 4000-wide limitation but you can also control this through the converter. But initially I think you'd create Express files.

Although we don't have our RT engine inside PPro-Mac or FCP, you should get very nice performance, expecially with the Express files. Our SetActiveMetadata app for Mac allows you to change Active Metadata.

To create 3D LUTs on Mac you must use the trial version of Speedgrade On Set (free 30-day trial) from the Iridas website.

We'll have a Mac-native converter in the reasonably near future, but if you can use Windows to convert (for now) you can explore the workflow on Mac.
 
chocblu said:
Timecode,

It first when i read that the quicktime didnt have timecode I was like, why? Its a total Necessity.

But then, i thought about it. Cineform is an intermediate file format. That means only in disaster should you need to go back to the r3d files, and you would probably manage to get the same timecode back out of them. Its not really like your doing an online/offline with these things.. This is your footage for all intents and purposes...

Of course, having the timecode there would be nice....But I understand why you may not actually need it...
Click to expand...

Yes, timeline is an artifact of the offline world, have bunch of inherent issues. 99% of CineForm onlines don't need timecode, but like I said we do include timecode today for those who need it, it just not exposed in MOVs yet.
 
David Taylor said:
Alex, if you can run the converter on Windows (or Parallels or Bootcamp) you can create CineForm MOV files directly instead of AVI files. Choosing MOV instead of AVI is a simple parameter in the converter and the associated batch files.

The converted files can be used in FCP or PPro (Mac). Remember FCP has a 4000-wide limitation but you can also control this through the converter. But initially I think you'd create Express files.

Although we don't have our RT engine inside PPro-Mac or FCP, you should get very nice performance, expecially with the Express files. Our SetActiveMetadata app for Mac allows you to change Active Metadata.

To create eD LUTs on Mac you must use the trial version of Speedgrade On Set (free 30-day trial) from the Iridas website.

We'll have a Mac-native converter in the reasonably near future, but if you can us Windows to convert (for now) you can explore the workflow on Mac.
Click to expand...
i know, i must confess, i am so ignorant.
I have never dared to go and see what exactly parallels is.
i have always feared that it could possibly require a windows license installed in my mac and this is something i'm not ready for. i'd rather have a clean windows pc sitting side to side with my mac.
but, still, i'd rather have a mac and work just on it with a little more room over my real desktop and a little more space on my hard drives.
then i hope the wait for a mac version won't take too long.
i'll be faithfully waiting.
sorry about this...

alex.
 
Arno said:
The express script gives a message 'please entry the path to work on' but does not bring any window to select the path. Is it normal? Do you have to edit the script with the correct path?
Click to expand...

Sorry, the scripts they weren't intended to be double clicked on. We will do the GUI that will remove the need for the scripts very shortly (although some will still find the scripting handy.) To do a batch conversion today go the to the Start Menu -> Programs -> CineForm -> Tools -> R2CF...

This will open a shell (command prompt) and offer initial instructions on the conversion. From here type:

cscript scripts/BatchExpress.vbs [R3Dpath] [outputPath]

If you R3D files are located on v:\project1\ and you output path is v:\master, your common line will be:

cscript scripts/BatchExpress.vbs v:\project1 v:\master

It will place all the express files in v:\master\express
 
I just completed some more extreme testing to match production environments. I batch converted all of Open Cut 1.0 -- 115 minutes of 4K R3Ds -- first as express files, then as 4K CineForm RAW masters.

Here are the stats:
It completed the DPX thumbnails in 3 minutes.
It completed the 1K Express file output in 90 minutes, averaging 30.6fps.
If completed the 4K Masters in 15 hours, averaging 3.1 fps.

R3D source 168GB
DPX thumbnails 88MB
CineForm Express 1K files (AVIs) 12.5GB
CineForm Master 4K RAW files (AVIs) 131GB (Filmscan1 quality.)

If you had one hour of footage in 1-hour shooting day, everthing could be batched including Express files and Masters overnight in 8 hours using a single PC.
 
If I were to do a color correction in RedCine, is there a way to maintain or access that color metadata across the R2CF conversion process?
 
David Wilson said:
If I were to do a color correction in RedCine, is there a way to maintain or access that color metadata across the R2CF conversion process?
Click to expand...

Yes are no. We don't currently bake in any camera metadata for good reasons, so the question is whether we can simult the camera settings in Active Metadata (with 3D LUTs we can.) A nice SDK feature would be output the camera profile as a 3D LUT, rather than coefficients to algorithms that remain internal to the SDK.
 
You must log in or register to reply here.
Back
Top