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

Post B16 comments here...

BUILD 16 Camera lock -up

BUILD 16 Camera lock -up

I have done this twice now (on purpose)

This is FYI:

Set up a time lapse sequence ie:
5 sec interval
1fr
Speed 1/2 sec

Then I go into the sensor menu and set the shutter speed to 1/24.

I start recording then I stop and try to access the sensor menu and Freeze. . . Camera locks up (sometimes the camera says there is no sensor).

Shut down and restart, everything is fine until I try to access sensor menu again. The camera locks up.

Cycle the camera and this time access the system menu, then set-up, maintenance, then restore.

Everything works fine. Ive got some great time lapse.



Method
 
nomad said:
Why? Who's going to see the difference?

Regards,

Uli
Click to expand...

Because it's exactly double the frame rate of 24fps. It would make a difference wherever maths is required for vfx work etc. Just a guess on my part..

Ben
 
Sorry, maybe the problem is on my side, but I don't get the point. A frame is a frame, at whatever rate, a time-slice of reality.
You playback speed is fixed anyway, like 24 fps for cinema.

Regards,

Uli
 
Timelapse bug.

Timelapse bug.

Set up a time lapse sequence ie:
5 sec interval
1fr
Speed 1/2 sec

Then I go into the sensor menu and set the shutter speed to 1/24.

I start recording then I stop and try to access the sensor menu and Freeze. . . Camera locks up (sometimes the camera says there is no sensor).

Shut down and restart, everything is fine until I try to access sensor menu again. The camera locks up.

Cycle the camera and this time access the system menu, then set-up, maintenance, then restore.
Click to expand...

Which version of Build 16 Method? Is that 3.1.2 or 3.1.5?
 
Not necessarily. Actual 35mm film is being projected at 48 FPS with every frame flashing twice on the screen. Hence the "film look". Also DCI specs include 48 FPS and especially with digital it seems like way to go in the future. Back compatible with 24 FPS (with simple 2:1 throw away), but will allow for much smoother motion, especially on a big screen...

I am all for 48 FPS...
 
Hey Rion,

I'll try to duplicate this on my RED as well.

I'll post here or call if I can duplicate it on B16 3.1.5.

David
 
EVF problems

EVF problems

Don't know if it the software or hardware. Have upgraded to b16.
Got my evf the other day and found it had 2 very annoying problems. One might be a "get use to it" problem. It's the so called "rainbow" effect where if u pan your eyes you see the image split up in RGB.
The other problem is that the evf (and not the lcd or recorded image) seems to change color on the fly all the time. Like I had a scen with white sheets and i just put my hand in the frame and the picture turned slightly green. After I first notised it of course I started see the changes all the time. I shot a man walking around in a room with diffrent backgrounds and his face changed color all the time. When reviewing it i saw nothing of the changes either in evf or lcd.
Anyone notised the same thing?

Truls sweden
RED #528
 
EVF question

EVF question

The other problem is that the evf (and not the lcd or recorded image) seems to change color on the fly all the time. Like I had a scene with white sheets and i just put my hand in the frame and the picture turned slightly green. After I first notised it of course I started see the changes all the time. I shot a man walking around in a room with diffrent backgrounds and his face changed color all the time. When reviewing it i saw nothing of the changes either in evf or lcd.
Click to expand...

Lets see if we can take one variable out of this equation - can you turn DARK DETAIL off on the viewfinder and repeat that test?
 
cinepost35 said:
Any chance of squeaking one more frame a second out of 3K 16:9 Redcode36 to get from 47 to 48 fps the benefits would be HUGE ?
Click to expand...

Would like to repost this question to anyone on the RED Team as I feel it got lost in the shuffle.
 
3K max fps

3K max fps

Would like to repost this question to anyone on the RED Team as I feel it got lost in the shuffle.
Click to expand...

Media restriction. So yes we'd like to go one more fps too
 
Red-drive

Red-drive

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.
Click to expand...

The camera does not power the drives down no. I'll PM you with some extra questions...
 
3K 48 fps

3K 48 fps

Would it be possible to get the extra Frame on Red Flash or Future Faster Red Drives
Click to expand...

Same answer, its a possibility. Reason for the ask is understood.

3K 16:9 48 fps RC28 is available today of course.
 
Build 16 experiences

Build 16 experiences

We shot with B16 3.1.2 all day Friday (4k 2:1, Redcode 36, 23.98 fps to Red Drive on AC power). We had seemingly random Codec Failures all day. When we reformatted the drive it seemed to help. I updated to 3.1.5 over the weekend and shot all day today with the same settings. We had the Codec Failures, but not quite as frequently as before. We also ran the black shading which, together with reformatting the Red Drive seemed to work well for a while.
After a multiple frustrating Failures in a row, we decided to just drop the data rate to RC28. It solved all the problems for the rest of the day.
We were shooting against a white cyc for the entire shoot - not sure if that has anything to do with it.
We also noticed that if the camera was left on for an extended period between shots that it would reboot itself or freeze up requiring a reboot.
None of these problems happened under build 15, so I'm sure it's specific to the new firmware.
 
Sean Michael 808 said:
We shot with B16 3.1.2 all day Friday (4k 2:1, Redcode 36, 23.98 fps to Red Drive on AC power). We had seemingly random Codec Failures all day. When we reformatted the drive it seemed to help. I updated to 3.1.5 over the weekend and shot all day today with the same settings. We had the Codec Failures, but not quite as frequently as before. We also ran the black shading which, together with reformatting the Red Drive seemed to work well for a while.
After a multiple frustrating Failures in a row, we decided to just drop the data rate to RC28. It solved all the problems for the rest of the day.
We were shooting against a white cyc for the entire shoot - not sure if that has anything to do with it.
We also noticed that if the camera was left on for an extended period between shots that it would reboot itself or freeze up requiring a reboot.
None of these problems happened under build 15, so I'm sure it's specific to the new firmware.
Click to expand...

Was any of the white cyc overexposed?
 
You must log in or register to reply here.
Back
Top