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

Post B16 comments here...

Red-evf

Red-evf

The only thing that was odd was that my EVF did not match the Red LCD or the Panasonic 17" montor that we had on set. The ...colors are very saturated, and depending on the shot look a bit posterized when the EVF overexposes the scene.
Click to expand...

There is a bug in the current Beta Build 16 that can cause the wrong gamma to be selected for the RED-EVF.

That can be a cause of the saturation error you describe; it should be fixed in the next beta build.
 
Stuart English said:
Do you have OPEN GATE selected? When the shutter value is in red text, the camera is telling you that its not able to perform the request that you have made of it.... The reason I ask about OPEN GATE is that it doubles the sensor capture frame rate, so shutter angles above 180 degrees (i.e 1/48th sec at 24 fps) are no longer available, as the sensor is operating at 48 fps in this case....
Click to expand...

Hi Stuart,

Thanks for your response, I had just found open gate in the op's manual and was going to post an answer to my own question, but you beat me to it!

Vince
 
I just did a shoot exclusively using the RED drive (2k 16:9 96fps), with B16. We were triggering the camera with a Panavision FIZ. I noticed that when the camera sat still for more than 10 minutes or so, when it was put into record, I would get a record error. My suspicion was that the drive is spinning down when it's not been used after a few minutes. Is that true? I tried using playback to spin up the drive if it had been a while between takes, but on two occasions, after the first error, the camera repeated the record error on the very next take. I'd love to know if anyone else experiences this issue.
 
blueapplesmedia said:
I noticed that when the camera sat still for more than 10 minutes or so, when it was put into record, I would get a record error.
Click to expand...

No haven't experienced that. I have let the camera for something like 1 hour still and then recorded without codec error. Personnaly I was only able to break the codec once, today during testing. I really cannot imagine why. The error stayed a few seconds, and when I shot the exact same scene just after it went well. No more codec error since.

Hopefully this will be fixed by build 16 release.

thanks,
antoine.
 
B16 Test - Sudden Blur shooting in 113fps

B16 Test - Sudden Blur shooting in 113fps

B16
500ASA
113 fps, Redcode28, Red CF card.
Two occasions during the shot that some bad frames will be introduced.
 
twlim said:
Wonder if anyone else has this same experience? Lim
Click to expand...

I am waiting to be able to get on the RedRelay to upload the quicktime movie to show the bad frames interspersed between the good frames. Lim
 
playback in camera:
don't know if this is a bug or a feature-but clips play back based on current metadata, not the metadata the clip was shot in.
for example shot a test clip at 1000asa and one at 200asa- both properly exposed for that asa. when i played back the first clip it was dark- until i changed the ASA of camera back to 1000 asa. Again, in certain ways it can be a feature- look at different ASAs after you have already shot something in camera, but also can cause momentary fright- "hey! it wasn't that dark when i shot it!"
 
Jarred Land said:
One piece of advice I can to help with the confusion, and its what I do here, is to take the camera and set it up right beside the system you use to process R3D files.

Point the camera at something with a nice range of contrast ( a bit of blow out, something just under blow out, and dark dark dark shadows) , take a shot and leave the camera on. Open the files in Red Alert, and compare what is going with the histograms etc.

Its much easier to put the connection together when you can directly compare what you see on your camera, to what you see in Red Alert and final output, and it will help build a little confidence (hopefully)
Click to expand...

I wonder if you could port a shell app of what you've just said above so that connected by the USB, you could rig an iPhone to do the same thing but feeding the vision to the iPhone. It's prob not powerful enough.
 
Purely clerical, but the main site (red.com) needs its faq updated to reflect the new features. Us Red-savvy types may already know that stuff but, as we all know, there's a ton of misinformation (usually from haters) out there.
 
v3.1.5's Joystick Sticks

v3.1.5's Joystick Sticks

I just updated to Build 16 v3.1.5
One thing that I noticed, joystick's behavior changed.
When I set up:
System> Sound>
joystick moves to the right is fine, but to the left, I have to press down, then to move joystick to left.
It needs a little trick, I think it a bug.
 
Build 16 v3.1.5

Build 16 v3.1.5

Otherwise, incredible, so much better than B15, I shot about 20 minutes with Grad-ND.6 and Grad-ND.3, interior and exterior, It's beautiful.
I did shot v3.1.2, but I can see the real result now.
I'm so happy about it.

chosei said:
I just updated to Build 16 v3.1.5
One thing that I noticed, joystick's behavior changed.
When I set up:
System> Sound>
joystick moves to the right is fine, but to the left, I have to press down, then to move joystick to left.
It needs a little trick, I think it a bug.
Click to expand...
 
Jim, Why has the minimum shutter speed in Timelapse been reduced to 1/2 a second?
Us time-lapsers like to shoot 1 or even 5 second shutter speeds sometimes.
Also - why when shooting with a 1/3 shutter speed will the camera not manage to record a full 3 frames per second?
 
twlim said:
B16
500ASA
113 fps, Redcode28, Red CF card.
Two occasions during the shot that some bad frames will be introduced.
Click to expand...
From other posts here, I think 113fps might be on the ragged edge of performance as far as recording to the CF cards goes. Probably more so with high detail, contrast scenes like the example you show. Try the same scene backed off to 110fps and see if it happens again. My guess is it won't, based on feedback here. also you could try recording to the RedDrive if you have one.

HTH

Paul
 
48fps @ 2k and 3K setting pretty please.

48fps @ 2k and 3K setting pretty please.

I posted a similar question but would like to post here to Jim or anyone at Red, For those out there that find Anamorphic useful it would be very useful if you could select 48fps in 2K and 3K as a shooting speed. Any chance of that being a choice in Build 16 Release?
 
48 fps

48 fps

I posted a similar question but would like to post here to Jim or anyone at Red, For those out there that find Anamorphic useful it would be very useful if you could select 48fps in 2K and 3K as a shooting speed. Any chance of that being a choice in Build 16 Release?
Click to expand...

As a Project TIME BASE or a Varispeed? You already have the latter, what's your application for the former?
 
visceralpsyche said:
From other posts here, I think 113fps might be on the ragged edge of performance as far as recording to the CF cards goes. Probably more so with high detail, contrast scenes like the example you show. Try the same scene backed off to 110fps and see if it happens again. My guess is it won't, based on feedback here. also you could try recording to the RedDrive if you have one.

HTH

Paul
Click to expand...

Paul, I suspect what you said could be the cause. Red has taken note, as always with all our feedbacks, and is investigating. It is always a good feeling that when we do battle in the front line, we will not be left behind. - Lim
 
Stuart English said:
As a Project TIME BASE or a Varispeed? You already have the latter, what's your application for the former?
Click to expand...

48 fps Digital Cinema in both 2k and 4k deliverables. 3K@48 for 4K@24 fps

Project time base might make it easier to sync multiple cameras.
 
Stuart...Would 24 Timebase Tri-Level synced Reds stay in sync both running 48fps in varispeed?
 
You must log in or register to reply here.
Back
Top