No monitor out support being even planned

[Scott Simmons]

It will all be fine down the line, plenty of options will be there sooner then later.

Maybe .. but this camera has been out for over a year now (and in development longer than that) and post has pretty much been an afterthought. It took a year to get an SDK and third parties working on their own to offer up usable options to what RED was offering on their own. I think a lot of us on post are waiting, have been waiting, will be waiting .... etc.

 

[Pxion]

Personally I think if RedCine had a basic waveform / parade / vector, it will be a perfect tool to do 'first light' and then transcode. This will especially help people without dedicated hardware to work around this limitation and display on a calibrated monitor.

From a programming perspective, creating these scopes is very straightforward, you sample pixels from the R3D raw and plot their Luma, RGB values etc. in the appropriate scope format. In its simplest form, they do not have to process pixels at full res, or even at real-time.

I think it all depends on how Red is prioritizing their efforts. If RedCine would be open-source, this feature could be rolled in by a handy programmer in the Red community...

 

[ThomtheEditor]

It will all be fine down the line, plenty of options will be there sooner then later.

Unfortunately that's exactly my point, that the word straight from Red is that this feature is not even being discussed or conceptualized.

If RedCine would be open-source, this feature could be rolled in by a handy programmer in the Red community...

Hopefully within the first few hours :shifty:

Also, any update on when that SDK has been pushed back to yet?
Everytime i ask it's oh a few more weeks :construction:

 

[Shawn Nelson]

And this surprise you all how? Redcine is made by Scratch, its in their best interest to make it incomplete and buggy.

My money is on Crimson. I'm on the edge of my seat waiting to see what Ian does with the SDK

 

[Pxion]

And this surprise you all how? Redcine is made by Scratch, its in their best interest to make it incomplete and buggy.

My money is on Crimson. I'm on the edge of my seat waiting to see what Ian does with the SDK

Sure, RedCine = Assimilate. But I don't think they keep it incomplete and buggy on purpose. That just wouldn't make business sense.

Also, Crimson is a conforming tool. As of now, it is in no way helping to do a good 'first light' in RedCine, which is the subject of this thread.

 

[ThomtheEditor]

Ah yes, but if we had a redcine-esque room in color to directly manipulate the R3d image (white balance, gamma, iso, etc) it would make it moot!

Then the ideal processing route, for macs, would be redrushes for your conform->fcp to cut->color to finish (also with the sdk maybe AE would be able to pull directly, very exciting seminar coming up on what adobe is planning to do with R3d's) that would make me a happy editor!
~T

 

[William Wedig]

It still doesn't make sense to me that there are tons of scopes and waveforms on the camera and none in RC. I understand it's a 'first light program' but I'm not doing anything to my image on a computer monitor unless I have a scope of some kind, and even then I'm not doing a lot (which I guess is the point, I'd just really like to have those blacks down at 0 IRE instead of 10 to begin with).

 

[Pxion]

William,

I fully agree. Maybe a 1st thing to have in RedCine (before scopes + monitors) is a simple 'picking' tool that lets you pick the black and white point. After picking, these are set to predetermined values (e.g. 0 and 100 IRE) and optional are color corrected to black and white resp.

This should just be trivial to implement...

The only safe method to do 1st light right now is doing a white balance by clicking a white point and type in / move around curve nodes and check with the Histogram if everything is legal while maximizing the range.

Or am I missing some undocumented tools?