Welcome to our community

Be a part of something great, join today!

Register 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 Beta-Build 18...

Blue Screen

Blue Screen

I thought this was a feature to let you know the camera rebooted itself do to an error ....the blue screen was good since it let you know the camera rebooted
Click to expand...

Yes there was this small side benefit, but a bug is still a bug and its now gone.
 
has this build fixed some of the anamorphic bugs such as shading on the directors monitor and the 4k ana quicktime playback issues.
 
I can't seem to find the new release. All I see is version 3.6.0 that was released in November. Was the new build taken down?
 
SF Geek said:
I can't seem to find the new release. All I see is version 3.6.0 that was released in November. Was the new build taken down?
Click to expand...

I think so too.
 
The guys are looking into it... not sure what happened there.
 
I just pushed it live again. We had some data issues on RED.com so rolled back to prior database and we lost the build I posted Friday. If you have any other issues (eg, with your web account or something, please PM me). Sorry for any inconvenience...

BC
 
Meaning of "stall."

Meaning of "stall."

By eliminating the stall that is mentioned in the first time, by "stall" do you mean the 90+ sec boot-up time? This would be HUGE news if it was.
 
Joe Taylor said:
By eliminating the stall that is mentioned in the first time, by "stall" do you mean the 90+ sec boot-up time? This would be HUGE news if it was.
Click to expand...

I believe it means eliminating the false starts, when it would just hang on "booting..." forever.
 
GPI trigger

GPI trigger

The GPI change was only to change the default setting of GPI B (as suggested)

No reason for ramps to no longer work, but I'll test that to verify.


(EDIT) A Varispeed Ramp initiated from GPI trigger works fine for me...
 
Stuart, were you able to identify the "PlayBack" "Clip" setting messing up the Color space from REDSPACE to REC709? This is a bug that needs to be addressed IMO. It kept me confused for the better part of a week trying to figure out what was causing it and how to fix it.
 
You can choose to have the camera playback the clip with either the cilps metadata or the current settings in the camera. It has been found that one of those, I forget which, mike's post seems to indicate clip, will often reset your viewing space to rec 709
 
OK.

Also, time for me to be the bad guy, but can't we have the initializing icon out of the frame on boot up, maybe on the release build?
 
J. Eric Camp said:
You can choose to have the camera playback the clip with either the cilps metadata or the current settings in the camera. It has been found that one of those, I forget which, mike's post seems to indicate clip, will often reset your viewing space to rec 709
Click to expand...

Correct, Florian Stadler was kind enough to respond to a post I put up a few weeks ago regarding this issue. Once we switched to PlayBack/Camera all our issues went away.

Also, did anyone else notice in this new build that the tint defaults to -5? Is this found by the RED team to be the optimal setting for consistency in the image Color ie, taking out a small amount of green.
 
Stuart English said:
The GPI change was only to change the default setting of GPI B (as suggested)

No reason for ramps to no longer work, but I'll test that to verify.


(EDIT) A Varispeed Ramp initiated from GPI trigger works fine for me...
Click to expand...

Ok, so I was finally able to activate a ramp using a GPIO trigger but only under these circumstances, let me know if this all sounds kosher...

GPIOs A&B must both be set to ramp/cued or one or the other has to be off.

If any GPIO is set to Rec. then the record works but ramp does not.

The ramp setting under the varispeed menu neeeds to be set after the GPIO trigger setting are set.

Lastly regardless of which GPIO is set (A or B) if either one is turned off (unchecked) then the only active port is the lower port (this is A I believe).

If this is all the way it should be and not something specific to my camera then it would be nice to have both Rec. and Ramp functionality available at the same time on each of the two ports.
It hasn't come up yet but I can foresee a situation on a crane or vehicle mount where having both would be necessary.
 
GPI trigger

GPI trigger

Ok, so I was finally able to activate a ramp using a GPIO trigger but only under these circumstances, let me know if this all sounds kosher...

GPIOs A&B must both be set to ramp/cued or one or the other has to be off.

If any GPIO is set to Rec. then the record works but ramp does not.

The ramp setting under the varispeed menu neeeds to be set after the GPIO trigger setting are set.

Lastly regardless of which GPIO is set (A or B) if either one is turned off (unchecked) then the only active port is the lower port (this is A I believe).
Click to expand...

Nope to all of the above.

Upper connector is GPI A, lower is GPI B

I just changed GPI B to RAMP, then enabled VARISPEED and RAMP, and set RAMP to ON EVENT.

Then I press the red Record button to start the varispeed capture, and hit the GPI to start the ramp.
 
You must log in or register to reply here.
Back
Top