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

build 17 bugs

Stacey Spears said:
I am curious, I have not had it hang at boot since switching to the EVF. It would hang every time with LCD.

So, those that experience the hang, is it with LCD, EVF or both?
Click to expand...

Yes, with both LCD and EVF - which is probably a fairly standard configuration for most folks.
 
I have yet to encounter the boot hang, however I do get the "rocket error" at least once a day (I am shooting everyday these days, thankfully) but it shows up and vanishes so fast I can never see anything other than "rocket"......

Also, still get the internal error message - this tends to happen when cutting and trying to start again quickly.

But on a positive note (don't feel like digging for the "RED is a Tank" thread), this past Friday I was filming a ring fight and thanks to loose ropes, both 215lbs+ fighters fell out of the ring and on top of a few of us ringside.... One fighter crashed down on top of Cassavetes who only lost power to the LCD... Had to reboot to get it back, but that was it. RED took a beating and kept going....

2259_1226438072.jpg
 
Pixel artifact on

Pixel artifact on

Had an entire scene today where every shot was peppered by these pixels of green and blue that appeared and then disappeared. If you connect the dots you get lines across the sensor. I've never seen this effect before, but this is my first time shooting on release Build 17.

The footage was shot RC36, 25fps, 4k 2:1, shutter 1/50, ISO 320 on B17 v3.4.1.

The rest of the footage from yesterday's shoot was fine, including an exterior day scene and exterior night. The only thing different about the scene with the pixel artifact was its extreme contrast, and how the odd pixels occurred around the highest contrast area of the frame.

We are now beginning the second day of the feature and because of this issue I will revert to B16, which is an unfortunate step back.

1384_1226571593.jpg
 
Stuck in Record Bug

Stuck in Record Bug

Used build 17 release version for the first time today.

Had a problem getting it to "cut" - repeatedly pressed both record buttons -held them down for a few seconds - still could not get the camera out of record mode. Rebooted - camera wouldn't reboot - disconnected LCD and EVF and then it booted. The problem reoccurred again and again. Haven't experienced any problems like this before.
 
Dropped frames to CF card

Dropped frames to CF card

Build 17 3.4.1

4k HD 28

records fine to Red Drive but both my cameras can no longer write to the CF cards.

First one camera did this then a day later the second camera started doing the same thing.

At first I thought it was a bad CF card writer, now with the same issue on both of my cameras I think it's the software. It first started after I upgraded to 3.4.1, I tried going back to build 17 3.3.9 but it didn't fix anything.

I'll try going back to 16, I'm scared to try 18...

Keith
 
Builds

Builds

Can you save the LOG file, then go back to 16 and see if that clears the issue up.

If it does can you go back to 17 and see if the issue is still there?
 
Can someone send me build 16?

Can someone send me build 16?

It's no longer available on the support page...

Thanks,

Keith
 
Build 17 and issues with View RAW toggle

Build 17 and issues with View RAW toggle

Clint Johnson said:
One of the first things I do with a newly installed build is to change the user assignable button 1 - from "Auto-White Balance" into "View RAW" mode.

It works for the first few changes but then refuses to change into View RAW mode... and thereafter refuses to show any of the changes subsequently made in any of the metadata settings. It still shows the last look used
Click to expand...

We are seeing the same issues with Build 17. Toggling between a preset Look/Redspace doesn't work after several hours of shooting, or a few reboots, or overnight. Haven't determined what the trigger is, but the ability to toggle in and out of View RAW just seems to vanish. Resetting the keymap has no effect, and the only fix we've found is re-upgrading the camera to B17 each morning. But the View RAW toggle is gone by lunch.

Other issues seen with 17...getting occasional boot hangs. The camera is being rebooted for batt changes, etc perhaps 10-12 times a day. Anecdotally, under 10-20% of boots hang. We are using the EVF and LCD, and both are attached before booting the camera. It nearly always boots fine if you cycle the power again immediately. It's just a pain, and occasionally slows us down on set when batts are being changed between takes. I'm told that unplugging the LCD before booting can make a difference. I still think I shouldn't have to do workarounds like that though.

I imagine this is unrelated to Build 17, but we are also occasionally seeing the image in the EVF turn completely red. Jiggling the EVF lemo seems to fix this. Worried we're going to lose the EVF on this shoot...
 
mjeppsen said:
We are seeing the same issues with Build 17. Toggling between a preset Look/Redspace doesn't work after several hours of shooting, or a few reboots, or overnight. Haven't determined what the trigger is, but the ability to toggle in and out of View RAW just seems to vanish. Resetting the keymap has no effect, and the only fix we've found is re-upgrading the camera to B17 each morning. But the View RAW toggle is gone by lunch.
Click to expand...

I am having this frustrating problem as well. Please fix this!

Thanks
 
Taylor Morrison said:
I am having this frustrating problem as well. Please fix this!

Thanks
Click to expand...

I have encountered this problem also. On my camera it seems the camera actually just switches to Raw View as the default view, if you go into the menu you can swith back to your prefered option : Redspace or REC709.

Annoying bug never the less, and not the only one in Build 17...

Cheers,
Damien
 
"Invalid public movie atom"

"Invalid public movie atom"

Shooting Build 17 4K, 16:9, 36

QT proxies playback response on one take: "An invalid public movie atom was found in the movie"
This in p.mov, M and H.
Playback possible in F.mov

The next take playback has no audio
Same as previous situation with only F.mov having audio.

On location so smooth QT F.mov playback on MacBook Pro not possible.

Any help RED?
Thank You.
 
It's all been mentioned, but just to chime in, I'm experiencing frequent boot up freezes...seems to happen most when I need the camera up and running the fastest :)

Also have the Playback audio error and message frequently on playback, clip will playback fine if I toggle up and down clips.

I know this has all been said... just writing for the record
 
I'm getting a camera error occasionally when pressing the record button. A message comes up that says "RECORD ERROR: INTERNAL FAULT". I have sent a log file to support but no response yet. Has anyone else had this?
 
Had BIG problems yesterday having gone to build 17...we could NOT get the camera to boot. Every time we tried to start the camera we would get a flashing rear screen or occasionally we would get the "Booting" announcement but then nothing.

I wondered perhaps if the power cable was getting bent due to our camera configuration so we moved the battery + drive from the rear to the top of the camera and in the process disconnected our EVF. The camera then proceeded to boot quite happily.

Not sure if this is a build 17 bug? It has never happened before.

Good news is that once we got up and running, our footage yesterday was stunning :biggrin:

Best wishes

Scott
 
I also had the same "invalid movie atom" and it wasn't the quicktime version that was messed up, it was the .r3d. I was not able to open the clip at all, in any program: quicktime, FCP, Red Alert, Redcine or RR. How many other people have these corrupted files since switching to B17??
 
You must log in or register to reply here.
Back
Top