Welcome to our community

Be a part of something great, join today!

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

Turn off the TC in the EVF - here's why!

Mark L. Pederson

REDuser Sponsor
Joined
Dec 28, 2006
Messages
7,145
Reaction score
1
Points
0
Age
59
Website
www.offhollywoodny.com
Build 15. EVF + LCD + Preview = no TC and frame guides on the preview output.

Disconnect the LCD (or EVF) and BAM you get your TC and preview back.

We spoke to the bomb squad today - they recreated the event and got word that simultaneous outputs only support TC & frame guides on TWO outputs and it defaults to EVF and LCD - turning the displays off on the preview.

Please Red Team -

TURN OFF THE TC IN THE EVF - DPs don't need it.

In fact, most DPs that shoot with us ask us if they can turn off most of the HUD in the EVF as they find it distracting. They want a "tally light and frame guides only" mode.

Regardless, we NEED TC display on the preview out. It is critical. Script supervisors demand it.

If you can't make it user definable, please set the default to LCD and PREVIEW for TC.

Thanks in advance!
 
As I've said many times before [and I know I'm backed up by everybody I've worked with], the HUD needs to be something that the operator can switch off!!! All I want are frame lines and a tally light in the EVF when I'm rolling. One of those buttons on the side can be assigned to turn all the TC and HUD back on whenever I please.
 
Build 15. EVF + LCD + Preview = no TC and frame guides on the preview output.

Disconnect the LCD (or EVF) and BAM you get your TC and preview back.

We spoke to the bomb squad today - they recreated the event and got word that simultaneous outputs only support TC & frame guides on TWO outputs and it defaults to EVF and LCD - turning the displays off on the preview.

That behavior appear to be coherent with what's described in the manual for build 15, V2.2.5 (pages 10 and 11). However, I agree about you point.
 
As I've said many times before [and I know I'm backed up by everybody I've worked with], the HUD needs to be something that the operator can switch off!!! All I want are frame lines and a tally light in the EVF when I'm rolling. One of those buttons on the side can be assigned to turn all the TC and HUD back on whenever I please.

YES please
 
the All ask for it...i agree!
 
We noticed this on Wednesday as well.

Even weirder though... with the same setup my Red now boots up with the HD-SDI outputs live, in other words we were able to be setting up the shot on the monitor whilst the EVF/LCD were showing the Initializing screen... This is actually a great feature that Red might now have accidentally stumbled upon because bootup times weren't much of an issue.

Paul
 
Now ... I PRAY that this is not a hardware limitation (overlays on "x" # of outputs) as any way you slice it you MUST have frame guides in the EVF.

You MUST have all displays on LCD - the ACs live by this.

and you MUST have TC on the preview out.

Until then ... script supervisors ... back to your stopwatches!!

Seriously - this is the ONLY thing we have to apologize for on set with the RED now.

Stuart ... can you give me hope ...?
 
Well though I agree with your sentiments Mark our clients here in Japan are all demanding clean HD-SDI outputs since they all want to record the stream to edit from.... yeah, I know, but that's their call and not ours.

So I'd make it user selectable in a perfect world, ON or OFF. Keeps everybody happy.

Cheers,

Paul
 
Me too

Me too

Best case, each output would be individually assignable for HUD, TC, Frame guides. Failing that, Mark's scenario is the one I face most often as well.

EVF - frame guides and tally

RedLCD - everything, with option of bigger image with TC only via toggle (mine does this now)

HDMI or HD-SDI - frame guides and TC only
 
I'm afraid it is a hardware limitation. Piping out extra video outs without any overlays (frameguides or TC) is simply a matter of forking out the hardware channels, but overlaying requires processing power. My guess is they didn't spec in fast enough parts and now its biting them in this little advertised restriction. I definitely agree with you that we need frameguides+TC on the HDSDI out even when using LCD and EVF. Without looking at their component breakdown I can't be sure, but sometimes saving $20 per chip can really bite you in the end and not be worth that $20.
 
I'm afraid it is a hardware limitation. Piping out extra video outs without any overlays (frameguides or TC) is simply a matter of forking out the hardware channels, but overlaying requires processing power. My guess is they didn't spec in fast enough parts and now its biting them in this little advertised restriction. I definitely agree with you that we need frameguides+TC on the HDSDI out even when using LCD and EVF. Without looking at their component breakdown I can't be sure, but sometimes saving $20 per chip can really bite you in the end and not be worth that $20.

Hard to know what Red can and can't do with existing hardware. I am waiting for an "official" "we can" or "we can not" from Stuart ...
 
Frame Guides

Frame Guides

Hard to know what Red can and can't do with existing hardware. I am waiting for an "official" "we can" or "we can not" from Stuart ...

Ultimately there ARE some hardware limitations...

But we are not finished improving this aspect of the camera yet. :construction:
 
Ultimately there ARE some hardware limitations...

But we are not finished improving this aspect of the camera yet. :construction:

Well ... for what it is worth - embedded TC in the preview output gives me options for displaying TC on client/script supervisor monitor.

And the moment you do THAT we are going to do a crazy cool DDR application for playback and on-set meta-data tagging.

In case anyone is unaware - there is an SDK for the stuff from Drastic Technologies -

http://www.drastictech.com/product_qcpro.html
 
I agree with Blair that each output should have ANY combination of stuff, or nothing, and be user selectable. Just like in "pro" film and HD cameras. Very basic concept and one we've been asking for for two years now.
I remember EARLY on in the existence of reduser.net there were several discussions about this. Lots of us were clamoring for this kind of control. The response from Red seemed to be, "what's video village?" "why do you need that?" "why a user box or customizable overlay?" and other surprisingly naive questions.
If there IS a hardware limitation to this (and other issues) PLEASE PLEASE PLEASE design the Epic to be more robust, even to the point that you might consider overkill BEFORE you set the price point. Let's not cripple the next camera to make it cheap. Especially considering the generous trade-in offer; that will make the "final" price of the Epic much more affordable, regardless of whether you need to increase the price by a few thousand.
Please.
Cheers,
Harry
 
Back
Top