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

build 17 bugs

Best practices request

Best practices request

Which QT version? The old one had the white/black frame problem.

What is the current recommended matrix of MacOS version, QT, FCP, RA, RC, etc for the latest release and beta camera firmware builds?

Would love to have a sticky that I can check quickly when I am setting up for a new show... Deanan? Stuart?
 
ViewRAW does not show any of the changes to the image. That so the metering and the image is not incluenced by the RGB processing.

Hello Deanan, and thanks for trying to clear it up but I did know (and love) that about ViewRAW, which is why I tried to make clear:

"And before you ask, it most definitely sticks showing the metadata based image; contrasted, saturated and boosted from the WB and ISO settings."

I was trying to emphasize that it was stuck unable to go into ViewRAW mode but was also no longer influenced by changes to the RGB processing. The "look" that it was stuck showing had the higher contrast, higher saturation and a boosted luminosity based on the white balance settings and the higher ISO settings... but the look would no longer change when those setting were changed.
 
update...

update...

Hi Stuart,

Well there is no signal at all. I have to keep reconnecting the HDMI several times until it sends a signal. a bit hit and miss. Keep plugging and unplugging and eventually the monitor says there is a signal and shows it.

I shot extensively this weekend and I can report the following issues (which may well be user error on some parts)

1: Occasionally the EVF shows normal view (full sensor), but it looks like the output to the LCD and the HDMI are magnified. Even when you playback the footage it appears to be zoomed in. At first I thought I'd recorded in 2K by accident as the FOV was totally different. Then of course I checked I was not magnified. Exiting back to see a live signal still shows the display zoomed in. However the EVF showed normal view. I had to reboot to solve it.

2. Tried playing some clips back last night and it said 'cannot play the clip ...... corrupted'. I freaked. It just showed a green screen and then the error message. It said this on a few clips . Once I got home and off loaded the clips they were fine. phew....

3. sometimes all my outputs just went green, a bit like a false color wash. It flickered on and off for a while like a loose connection, but stabalised after a while.

4. At the end of the shoot I saw some artifacting in the EVF, almost like a 'static', around the edges of objects. Imagine false colour was turned on, but on an overlay layer so you could still see the color from the real image underneath. This didn't come out of the HMDI or the LCD, only on the EVF. I just shot with it as we were running out of time and it wasn't on the R3D.

I think thats it, brain is a little fried. I'll post more later if I remember anything. Remmber this is my first red shoot so I hope at least some of this is just workflow Im not used to...

OH - feature request with False color. I was getting my cameraman used to exposing in false color as to what colour corresponded to which zones (normal, under, unacceptably under etc). Could you do false colour banding overlay on the histogram, so its instantly obvious? Like vertical bands as a gfx overlay. Then you could see exactly where those zones fall on the histogram. would be a useful feature I think. Then you could see where any part of your image fell.
 
Hello Deanan, and thanks for trying to clear it up but I did know (and love) that about ViewRAW, which is why I tried to make clear:

"And before you ask, it most definitely sticks showing the metadata based image; contrasted, saturated and boosted from the WB and ISO settings."

I was trying to emphasize that it was stuck unable to go into ViewRAW mode but was also no longer influenced by changes to the RGB processing. The "look" that it was stuck showing had the higher contrast, higher saturation and a boosted luminosity based on the white balance settings and the higher ISO settings... but the look would no longer change when those setting were changed.

That's more clear now. Have you tried to restore the factory settings on the camera?
 
Have an issue, when I try to playback a 4K 16:9/25p/36 sequence in the camera: A green screen shows up and the message: WARNING! Audio-fault playing.....
Is this because of the higher datarate? Any ideas? Ok, wasn't to lazy to search to long if somebody else had the same problems. By the way: When I open the files in redalert or redcine, they seem to play properly.
 
Audio error on playback

Audio error on playback

Have an issue, when I try to playback a 4K 16:9/25p/36 sequence in the camera: A green screen shows up and the message: WARNING! Audio-fault playing.....
Is this because of the higher datarate? Any ideas? Ok, wasn't to lazy to search to long if somebody else had the same problems. By the way: When I open the files in redalert or redcine, they seem to play properly.

Thats is a bug uncovered by the field testing of Beta Build 17. Affects camera playback only, as you described.
 
is that similar to the 'corrupted clip' message I was getting? Transfered to the drive its ok. I was also shooting 25fps 4K16:9 redcode 36
 
Thats is a bug uncovered by the field testing of Beta Build 17. Affects camera playback only, as you described.
We have to test it more but we've noticed that if you disabled the audio channel the problem disappears on camera playback.
 
Error on playback

Error on playback

is that similar to the 'corrupted clip' message I was getting? Transfered to the drive its o.k.

It could be, there are two or three playback errors like this that we uncovered.
 
Thats is a bug uncovered by the field testing of Beta Build 17. Affects camera playback only, as you described.

Found this bug today as well - disabling audio "fixes" it, but playback MOS won't always work...

BTW - Recording to drive - doesn't happen when shooting to CF...
 
tiny bug?

tiny bug?

Hello again,
it seems on build 17_v3.3.9 that all settings
remain in place, booting after booting, except the box "S4 ilens" which is ON again at each new booting, is this common ?
Could it be cured ?
__________________
 
busy shoot week and I had 3 internal fault errors whilst trying to record to the red drive .

4K 16:9 25fps redcode 36. build 17

one was a busy high street and two others a c/u of car radio. very odd. I rebooted and it was ok.
 
Loaded up the release version of build 17 and am sad to report that I am still getting "hanging" on boot up. It is intermittent (doesn't happen all the time).

The same workaround usually solves it...unplug the LCD and the viewfinder.

Anyone else continuing to experience this?
 
Loaded up the release version of build 17 and am sad to report that I am still getting "hanging" on boot up. It is intermittent (doesn't happen all the time).

The same workaround usually solves it...unplug the LCD and the viewfinder.

Anyone else continuing to experience this?

Dylan, We meet again :)

Loaded one camera with B17 prior to the firmware release and yes can confirm that we too had the return of the false boots. Intermittent like your experience, but not banished like B16.
 
Loaded up the release version of build 17 and am sad to report that I am still getting "hanging" on boot up. It is intermittent (doesn't happen all the time)

Anyone else continuing to experience this?

Yeah, I still get that sometimes. Also, when recording audio to I've gotten audio codec playback errors. The screen sometimes goes all green when that error happens. Kinda freaks people out when I'm verifying the last take and it happens. I definitely don't enjoy that much. But I like 1:1 magnification.
 
Yeah, I still get that sometimes. Also, when recording audio to I've gotten audio codec playback errors. The screen sometimes goes all green when that error happens. Kinda freaks people out when I'm verifying the last take and it happens. I definitely don't enjoy that much. But I like 1:1 magnification.

Oh no! audio codec errors too? both the boot up issue and the audio codec errors plagued me in build 16.

I love the new features of Build 17 but think that the priority should be fixing old bugs, before focusing on new features. And it looks like I am not the only one experiencing them!

Fixes - pretty please!
 
Back
Top