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

REDCINE-X Build 351... finally.

quentin please report this back once you tried ...

i always judged red color reproduction quite Bad ...

now...
i don't know yet...but from what i am seeing from people that compared RC1 and RC2 on the same gamma space ...red color 2 looks more a saturation thing to me and not a real new color matrix way different ...

see the example of miltos pilatilos on page 3 ... (because comparin redspace/redspace combination to RC2/RG2 is not fare to judge the improvement of RC2 (RS/RS in my opinio as always been a very very bad image ( i mean "out from the box " compared to other cameras))

g
 
Mark Phelan said:
Yes, wish it was available a long time ago, it even helps those of us who are color challenged! Thank you, it is much appreciated.
Click to expand...

The code for RG2/RC2 has been in testing for an extended period, and gone through quite a few tweaks as I got feedback from Jim on how it looked on his extensive collection of R3D footage.

Graeme
 
Gunleik Groven said:
That sounds very cool. Wonder how that would practically work, though, but conceptually that sounds very interesting.
Click to expand...

Well, it came to me as a way of working round a challenge I had encountered when using curves to try and make fine adjustments when images don't span the full recorded range of values. Say with a dimly lit low key night scene or just one where the contrast didn't take the highlights or shadows to the extremes. Currently you may only have a couple of handles within the actual range used by the image to play with and fine control is really difficult. You also have to sort of guess and play about to get feedback as to where that range you want to get into begins and ends on the curve, looking at the proportional distances along the histogram and using those same approximate positions on the curves works fairly well but is a bit hit or miss here. This is my idea for a solution to that. Essentially it would do what curves does but in a different interface which would be more intuitive to use for certain applications (so you would still want to have curves available as another tool).

How it would work in context of the other tools is a good question. My though it is that it should be at a known stage in the signal chain, possibly before curves and maybe even before Lift gamma Gain so that it can be used to give you a batter basis to work from with those tools and use them more effectively. You might even want the position in the image processing pipeline to be user selectable.

Perhaps this is something for a more advanced tool like Storm but I quite like the idea.
 
Gunleik Groven said:
That sounds absolutely right as everything seems to be done with curves and not gain in the MX signalchain.

You could probably replicate the "2" results with a curveadjustment to "redgamma".

Cheers

G
Click to expand...

M, M-X, Scarlet or Epic all use curves and not gain to achieve the end image. That was the major change with B30 and FLUT, extending the underlying curve engine to floating point throughout the image processing chain. This has allowed us to add in support for EXRs with over-bright code values, REDLogFilm, REDGamma. REDGamma2 has been especially designed to work in harmony with the FLUT system.

Graeme
 
Graeme Nattress said:
The code for RG2/RC2 has been in testing for an extended period, and gone through quite a few tweaks as I got feedback from Jim on how it looked on his extensive collection of R3D footage.

Graeme
Click to expand...

On behalf of all Red users thanks for you work on this Graeme.

You might also want to get in there with some Fashion stuff that has to be matched with stills like we have been working on at The Post Factory in London. It's all so color critical and demanding it's not true. And those fashion stills we have to match look beautiful too.

Tweaking the matrixing for this kind of stuff will reap serious rewards I'm sure.
 
Graeme Nattress said:
M, M-X, Scarlet or Epic all use curves and not gain to achieve the end image. That was the major change with B30 and FLUT, extending the underlying curve engine to floating point throughout the image processing chain. This has allowed us to add in support for EXRs with over-bright code values, REDLogFilm, REDGamma. REDGamma2 has been especially designed to work in harmony with the FLUT system.

Graeme
Click to expand...

Cool.

I have tested for that on MX footy, but not on M

Doing the first redlogfilm online/VFX prep on a 4 episodes M series Right now, and even though I hadn't tested for it, what you say is what it looks like -:)

Thanks for all the new color-goodies.

really make life a lot simpler!

Cheers.

G
 
Redrocet out of date

Redrocet out of date

after downloading and installing and then opening i get a message that my Redrocket card needs Driver 1.3.5.0 and firmware 1.1.10.1

I can't seem to find that on the support page. Anyone have a link to it?

Thanks.....
 
I get this problem on the 64bit RedcineX but not on the 32bit version. Is there something I can do?

RedcineX64bit.jpg
 
Quentin_B said:
On behalf of all Red users thanks for you work on this Graeme.

You might also want to get in there with some Fashion stuff that has to be matched with stills like we have been working on at The Post Factory in London. It's all so color critical and demanding it's not true. And those fashion stills we have to match look beautiful too.

Tweaking the matrixing for this kind of stuff will reap serious rewards I'm sure.
Click to expand...

Are the guys doing the photoshopping playing fair though! If they are using selective area correction, you'll never be able to fully match their still images without power windows/tracking masks!
 
I installed the driver update the Jim posted but it still gives a warning when launching RedCine-X about needing to update the driver/firmware for rocket use, any one else having this problem?
 
Oh yes, Jim. I am hot to run some older M and MX stuff through this build. Even hotter to run my Epic footage (Gigabyteage?) through it. Soon...

Thank you for yet more wonderful progress. Y'all ROCK!

Mike
 
Ryan Manes said:
I installed the driver update the Jim posted but it still gives a warning when launching RedCine-X about needing to update the driver/firmware for rocket use, any one else having this problem?
Click to expand...

Install the driver. Shut down. Boot. Install firmware. Shut down. Boot. Done.
 
I'm currently cutting a project in Adobe Premiere CS5 on Mac Pro with Red Rocket installed.

Will updating the Red Rocket firmware 'break' the communication between the rocket and Adobe Premiere?
I should probably wait...
 
btw, I have been playing with RC2/RG2 a bit this morning. Pretty sweet, thanks RED!

This leads me to a question I've been wondering for a while. If there is a thread on this already, please link. Let's say I do an on-set one light with RC2/RG2 (or any of the other combos for that matter). The offline files will then have those new color characteristics built into them, but the R3D of course remains unchanged. How do I pass along the information to a post house that isn't going to use RCX at all? They have to eventually go back to the raw file and finish the coloring, but how do they get the "correct" information from me? Confusing?
 
AaronPicot said:
btw, I have been playing with RC2/RG2 a bit this morning. Pretty sweet, thanks RED!

This leads me to a question I've been wondering for a while. If there is a thread on this already, please link. Let's say I do an on-set one light with RC2/RG2 (or any of the other combos for that matter). The offline files will then have those new color characteristics built into them, but the R3D of course remains unchanged. How do I pass along the information to a post house that isn't going to use RCX at all? They have to eventually go back to the raw file and finish the coloring, but how do they get the "correct" information from me? Confusing?
Click to expand...

They either have to use RCX or wait for the color-goodies to populate the SDK driven applications...
 
Wasn't aware you had to manually run the firmware in Terminal. Just assumed it was all self contained in the driver.pkg My bad its working now

Thanx anyway
 
I've been transcoding a batch of clips with REDLINE set to 6... Unfortunately something seems to have gone wrong though - the exports are done, so to speak, but the Prores proxies won't open in QT, VLC or FCP - FCP doesn't even recognize the files!

Is it due to REDLINE, or is it build 351? I just don't know whether I should let the batch finish in the hopes that it somehow has to finish the whole batch before I can use all of the files, or restart... Could someone please advise? I'm on a tight deadline cos we're doing a feature, so I need to make a decision very soon.
 
You must log in or register to reply here.
Back
Top