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

new REDCINE-X feedback

I just received my RED Rocket... and I've noticed that the Sharpness and Denoise sliders (in REDCine X) can't be changed... why is this?
 
BajaProductions said:
I don't know...but if i were to guess...as i am now, i think that RED has not yet come out with a REDCODE Quicktime component that can reliably transfer the new color science info in the transcodes to QT. HOPING that this is addressed and taken care of in the next redcine and QT component release. I can see the differences DRASTICALLY when working with underwater footage.
Click to expand...

The gamma change has nothing to do with the Quicktime component (which only is for the QT wrappers and not transcoded quicktimes).

This is Quicktime gamma problem where quicktime changes the gamma of what it displays depending on the codec, monitor space, application, or the output.

You can take the same movie file and play it in QT7 player, QTX player, FCP, or out through a kona and they will all look different.

If we try to hack it and fix it for one codec, it'll break another one, or it'll break video out, or in another app. There's no fix for this until the Quicktime system itself is fixed.
 
Jean Déraps said:
I just received my RED Rocket... and I've noticed that the Sharpness and Denoise sliders (in REDCine X) can't be changed... why is this?
Click to expand...

Rocket has a fixed debayer algorithm where as software debayer has alot more flexibility.
 
Shawn P said:
I am testing the cropping options.

1st what is the reason you would use, Fit Width, etc, etc, or 2x or .9x?

2nd if I'm asked to do a 4:3 crop, I set it up with a Center Crop, (seems simplest). Then I take those dimensions and apply them to my ouput as well? I ask because I've been only getting a full image in my ProRes422(HQ) files when I choose Full Debayer. When I choose 1/4 I get squeezed up to the very top.
Click to expand...

Fit width will do an automatic fit of the horizontal resolution regardless of the output resolution and add letterboxing where necessary.

2x is for anamorphic. Ie. fit width and desqueeze 2x at the same time.
.9x is for NTSC non square pixels.

We'll take a look at the Qtr output.
 
Deanan said:
The gamma change has nothing to do with the Quicktime component (which only is for the QT wrappers and not transcoded quicktimes).

This is Quicktime gamma problem where quicktime changes the gamma of what it displays depending on the codec, monitor space, application, or the output.

You can take the same movie file and play it in QT7 player, QTX player, FCP, or out through a kona and they will all look different.

If we try to hack it and fix it for one codec, it'll break another one, or it'll break video out, or in another app. There's no fix for this until the Quicktime system itself is fixed.
Click to expand...

Deanan,
that said, what is the most stable of codecs RED has seen that takes full advantage of the new color/flut controls that RED has developed? Most reliable WYSIWYG codec?
Thanks for the reply as i now no prores is dead.....but funny enough when i used old redcine v20 the saturation was back...and newer builds with new color science rendered out washed out desaturated looks. So that is what my test results have show me....but if i can no longer get a reliable transcode to prores, I'd better begin looking at a better codec deliverable.
Thanks....

EDIT: Actually, i'm not even sure this problem is a GAMMA SHIFT....I'm not certain that is what the desaturated look is from.
 
Deanan said:
.9x is for NTSC non square pixels.
Click to expand...

Can I put in a request to have a PAL equivalent added to a future release. And anamorphic SD ratios included too.
 
just noticed a weird possible bug... I've been taking snapshot frames and sending them to a specific folder. This works great unless I happen to make the batch monitor window active. At that point RCX seems to complete the export of the particular image in the queue but never updates after that so the batch monitor remains on "Running" for that file and does not proceed to the next file in the list. I have to Force quit and go again.
One other small thing that seems to be happening is that the output file (for snapshot) no longer indicates the frame of the snapshot. All mine are indicating 0000000. This used to show the frame number. I hope this is of some help....
 
Deanan said:
The gamma change has nothing to do with the Quicktime component (which only is for the QT wrappers and not transcoded quicktimes).

This is Quicktime gamma problem where quicktime changes the gamma of what it displays depending on the codec, monitor space, application, or the output.

You can take the same movie file and play it in QT7 player, QTX player, FCP, or out through a kona and they will all look different.

If we try to hack it and fix it for one codec, it'll break another one, or it'll break video out, or in another app. There's no fix for this until the Quicktime system itself is fixed.
Click to expand...

This is the most frustrating thing ever. What's the point of grading footage in RedcineX and transcoding to ProRes if the grade you dial in will not be represented in the file? Some productions want to just use the one light from the transcode for simplicity- it happens way more often than it should. You dial in a grade an then who knows what everyone will be looking at- some will see it close to what you intended and others might see it washed out and desaturated or too cool. There is no consistency. At least with an F900 I can dial in a look on the paintbox on a calibrated monitor and it will exist on the tape to a broadcast standard. I love the potential of this system but until the consistency issue is fixed, the full potential won't be fully realized.

Are there any workarounds to achieve WYSIWYG color from the one light grade in RCX down the chain? I'm starting a pilot tomorrow.
 
Eric Haase said:
This is the most frustrating thing ever. What's the point of grading footage in RedcineX and transcoding to ProRes if the grade you dial in will not be represented in the file? Some productions want to just use the one light from the transcode for simplicity- it happens way more often than it should. You dial in a grade an then who knows what everyone will be looking at- some will see it close to what you intended and others might see it washed out and desaturated or too cool. There is no consistency. At least with an F900 I can dial in a look on the paintbox on a calibrated monitor and it will exist on the tape to a broadcast standard. I love the potential of this system but until the consistency issue is fixed, the full potential won't be fully realized.

Are there any workarounds to achieve WYSIWYG color from the one light grade in RCX down the chain? I'm starting a pilot tomorrow.
Click to expand...

Prores is accurate for me from RedCineX to FCP.

h.264 gets a bit brighter.
 
Mike Gross said:
Prores is accurate for me from RedCineX to FCP.
Click to expand...

Is this on your computer monitor or on an SDI output (Rocket in REDcineX and AJA/BlackMagic in FCP)?
 
Shawn P said:
I've actually quite using RedCineX and gone back to useing RedRushes and editing and finishing using the Proxies.

I don't know what it is, but ProRes aside, outputting proxies from Clipfinder 2.2 are washed out. Out of RedRushes they are beautiful. Off of the camera they are washed out watching them in Quicktime unless I re-output from RedRushes, then they look great.:cheers2: Thats assuming your white balance was done properly in camera.


TESTING TESTING TESTING (imagine an hour going by and I go back to retest in RedcineX for comparison)(with alternative setting to what I first used)

Ok, now with the new quicktime I downloaded from Rob I can use RedCineX and these settings without washout. I find if I set or use Redcolor and Redspace, set the Saturation to .90, contrast to .11 and render out Prores422HQ for offline.

Mileage may vary.
Click to expand...

Shawn, do you mean the new beta QT that you have to manually load? I did this a long time back and still continue to get washed out-desaturated transcodes. OR is there another QT beta that actually fixes this? I think we are up to beta 4.0??
 
Shawn P said:
Thats the one John. I have to use Redcolor and Redspace or it will look washed out.
Click to expand...

Now that i have not tried...I'll give that a look and try with redcolor/redspace. I just cannot imagine that doing that is a fix, but i'm prepared to try it. I of course have been setting color space to redcolor/redgamma.
 
Build 247 feedback

Build 247 feedback

Hey all,
where do we post feedback on build 247 ?

Everytime i try to take a snapshot....nothing happens. I've setup my preferences, but finally the system locks up and i have to do a restart on the system--can't force close redcine-x, but rather i have to hold down the on/off button on the mac.
 
OK, this is my first post on the subject. Overall, positive. comments would be
build 194 (windows), and 2?? (mac)
i) Can't Preview R3Dsat 100% on mac. Latest version just closes instantly. imac, 256mb ATI. Earlir version said not enough memory (4gig?)
ii) On windows, much better (even though only xp 32bit=3gig), but cant view r3ds at LESS than half res. (ie, no 1/4, 1/8, 16th etc), which effectively means I can't preview motion from usb drives.
iii) On windows, everything freezes and hangs if I move windows about while batch window has active jobs. pausing jobs prevents the freeze.

thanx, keep up the good work, but for the love of god give us R3D trimming, the system for archiving right now sucks lots.
 
redcine x look presets

redcine x look presets

Hi

so it just occured to me that when i'm saving a look preset, it's not saving any of the lift/gamma/gain changes I made for me to alter. Whats strange is that it is applying it to any image I want but if i try to tweak any component of lift/gamma/gain it reverts back to position zero...any thoughts?
 
Don´t know somebody mentioned this before, but to have sound in RedcineX Windows version: Big thank you!
247 win is the first version which works on my comp well, without crashing and with a well working H264 output.
Like the interface a lot.
Starts to be fun with Windows too!
Thanks,
Marc
 
RCX 252 feedback

RCX 252 feedback

just been trying regenerating QT proxies in 252. This seems to be a small bug:

in the export settings dialogue the output location is not responding to any of the options. It would make sense to me that a default which simply overwrites the reference files in the clip folder would be the most efficient. But RCX asks every time for the location of the output file(s). As a consequence it seems to be impossible to generate new reference files for several clips at the same time - which is actually what I want to do. Am I missing something?

I did regenerate some QT ref files one .R3D file at a time but I still have to choose the destination folder. Curiously if I have one of the ref files selected in the finder that particular ref file is NOT regenerated but the rest are.

I hope this is of some help

peter
 
Repeatable and unrepeatable bugs, Build 252, Mac

Repeatable and unrepeatable bugs, Build 252, Mac

Repeatable: If I put clips into a bin, quit REDCINE-X, eject the CF card the clips are on, then restart REDCINE-X, the clips in the bin show up with Xs (as expected), but if the CF card is remounted, those binned clips can't be viewed even in the browser (other, unbinned clips on the CF card can be).

Fix: Quit & restart REDCINE-X.

Happened once: I ran REDCINE-X, exported some clips, etc. At some point (I think while switching between REDCINE-X and FCP) the Viewer window went white. I quit REDCINE-X, pulled the CF card, tried to restart REDCINE-X. Got one bounce in the dock, then nothing; console messages said:

7/3/10 2:48:15 PM [0x0-0x8b08b].com.red.RedCineX[2508] redexport: incorrect number of args to process: 2
7/3/10 2:48:15 PM com.apple.launchd[374] ([0x0-0x8b08b].com.red.RedCineX[2508]) Exited with exit code: 128

Deleting prefs didn't help; got the same behavior on every attempt to relaunch. The abortive launch didn't put up an OS X quit message, and no REDCINE-X logs were generated.

Fixed it by reinstalling REDCINE-X from the zipfile, and despite my best attempts to break it the same way, it keeps on working.

Running OS X 10.5.8 (still!) on a 15" MacBook Pro 2 C2D 2.33 GHz 3 GB RAM ATI 1600 GPU.
 
You must log in or register to reply here.
Back
Top