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

David Newman said:
You are using a NVidia card in the wrong mode. NVidia has incorrect support for YUV overlay, so turn "Force YUV" off in the Playback settings.
Click to expand...

Thank you very much David.
 
I need my own bailout

I need my own bailout

Apparently my brain has turned to concrete because I simply cannot figure out the right entry to turn individual R3D files into 1920x1080 cineform avis.

When I enter my information at the prompt following the example and hit enter, it immediately jumps to the next line and says "done."

Can anybody bail me out here and show me how I should make the entry?

Thanks,
 
In the "scripts" folder there are scripts to convert to either 1920x1080 444 or 1920x1080 422. Are you running the scripts, or are you running the R2CF command tool separately?
 
David Taylor said:
In the "scripts" folder there are scripts to convert to either 1920x1080 444 or 1920x1080 422. Are you running the scripts, or are you running the R2CF command tool separately?
Click to expand...

I'm running the command separately because I have tons of footage and have a deadline that won't allow batching the whole thing first.
 
OK. Give the following switch settings a try:

-q4 -w1920 -h1080 -p1

"-p1" says to do a 4K decode from the SDK
"-w1920" and "-h1920" define the scaled image size
"-q4" says use CineForm Filmscan 1 quality mode

This will produce a CineForm 444 file. If you want a YUV file you'd add a "-y" switch.

NOTE: This will produce a letterbox 1920x1080 (remember your source is 2:1). If you want a non-letter box you can add the "-z" switch which will do a center crop.

Following is a link to the Tech Note with the parameters: http://www.cineform.com/products/TechNotes/RedOneWorkflow.htm.

Can't wait for the GUI, huh? :-)
 
David Taylor said:
OK. Give the following switch settings a try:

-q4 -w1920 -h1080 -p1

"-p1" says to do a 4K decode from the SDK
"-w1920" and "-h1920" define the scaled image size
"-q4" says use CineForm Filmscan 1 quality mode

This will produce a CineForm 444 file. If you want a YUV file you'd add a "-y" switch.

NOTE: This will produce a letterbox 1920x1080 (remember your source is 2:1). If you want a non-letter box you can add the "-z" switch which will do a center crop.

Following is a link to the Tech Note with the parameters: http://www.cineform.com/products/TechNotes/RedOneWorkflow.htm.

Can't wait for the GUI, huh? :-)
Click to expand...

Thank you David. As soon as I return to my office, I'm going to give it a try.
 
Here is beta of Prospect 4K packed with tweaks to help Red users.

Version 3.4.4 adds:

* more curve options for encoding and decoding through Active Metadata. Basically you can set the output curve to match that of RedSpace, non-destructivily, as an Active Metadata option. If you want this as the default, add -dR to the switches in the R2CF batch scripts. This will make your outputs be pretty much the same as RedCine. Within Premiere's Active Metadata controls the new curves are now available for content you have already converted.

* While CS3 has it memory issues, we made it work so much better for 4K finishing in 32-bit float. Our decoding in Premiere now uses less than half to one fourth the memory of before, greatly eliminating the Premiere low memory warnings. Export your timelines to 4K 4:4:4 CineForm AVIs with much more ease.

* Faster sync playback for audio within Premiere Pro.

Link http://www.miscdata.com/cineform/P4Kb184.zip

P.S. If you download a P4K build 184 beta before this post, you like have a older version. Please download again.
 
awsome David...and David(s)

keep it coming....:gun:
 
David - it is likely not entirely cricket to ask this here but...

Do I need to uninstall CS3 in order for P4K to assign itself to CS4?

I uninstalled P4K b183, followed by an install of CS4 and then I installed P4K b184. I doesn't seem that CS4 recognizes P4K and the program crashes on attempting to open existing projects.

I realize I should probably file a support ticket for this but thought maybe others making the CS3-4 change would appreciate the information as well.
 
David Wilson said:
David - it is likely not entirely cricket to ask this here but...

Do I need to uninstall CS3 in order for P4K to assign itself to CS4?

I uninstalled P4K b183, followed by an install of CS4 and then I installed P4K b184. I doesn't seem that CS4 recognizes P4K and the program crashes on attempting to open existing projects.

I realize I should probably file a support ticket for this but thought maybe others making the CS3-4 change would appreciate the information as well.
Click to expand...

Just point the Cf install directory to CS4's plugin directory...
 
Hold on guys. Don't install CS4 if you want to use CineForm. CS4 is missing the API we need, Adobe will be releasing a patch in a month -- other accelerator vendors like Matrox are also affected. Even then we need to upgrade a bunch of components to support CS4, the upgrade will bump Prospect to version 4.0 -- this will happen in the December time frame.
 
Christopher Grant Harvey said:
David, exporting 4K 4:4:4 how many minutes have you exported as a test... just to give us a guide?
Click to expand...

We haven't done anything really long, that would have delayed the beta release. My series of tests we around 5 to 10-minutes. As the overal system usage for these exports are between 200-300MB lower, we feel confident about long exports. You might still see the compiler error message at the end, yet the file producted is fine and the error is miss-named. Premiere seems not to have enough memory to import the new 4K file and close the 4K render at the same time (Adobe clearly does test beyond HD.) Simply say OK on the error pop-up and import the new AVI manually.

Note: All my testing was done on a HP xw8600, 8core with 4GB RAM under XP Pro SP3 32-bit. I also have thge /3GB switch set in the boot.ini
 
David Newman said:
Hold on guys. Don't install CS4 if you want to use CineForm. CS4 is missing the API we need, Adobe will be releasing a patch in a month -- other accelerator vendors like Matrox are also affected. Even then we need to upgrade a bunch of components to support CS4, the upgrade will bump Prospect to version 4.0 -- this will happen in the December time frame.
Click to expand...

Thanks David. Suspecting somesuch, I didn't uninstall CS3. I'm happy to wait...
 
David....I know you'll hate this question....but anyway

with all the CUDA buzz about right now, would you ever consider offloading some of the processing off the CPU and on to the GPU

sort of a hybrid port to CUDA?
I know you've indicated before that it is not neccesary, just thought I'd get your opinion
 
mdharrington said:
David....I know you'll hate this question....but anyway

with all the CUDA buzz about right now, would you ever consider offloading some of the processing off the CPU and on to the GPU

sort of a hybrid port to CUDA?
I know you've indicated before that it is not neccesary, just thought I'd get your opinion
Click to expand...

Until a GPU don't slow us down, we will stick with the CPU. Compression, particular high-end compression, is not a good fit for GPUs. While a hybrid codec that does some CPU work and some GPU work is fine, that design is best for presentation only, not for post-production where the output of the decoder may be feed into other CPU based operations (the ping-pong from GPU to CPU is still a bottleneck.)
 
RedLog is basically the default, although we use the SI-90 log as there was already a lot of footage that used that (match existing 3d LUT.) SI Log is base 90, RedLog is base 100, the difference is tiny.

The green line is SI-90 (default), the red line is RedLog (you can just see it below the green line.) For reference the cyan line is Gamma 2.2 and the Yellow line is RedSpace.

To exactly match RedLog the switches are -eL100 (which mean encode with Log 100) and -b0 (level the black offset at 0.)
 
You must log in or register to reply here.
Back
Top