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

boot hang

boot hang

With all nine cameras we have, we encounter boot hangs every now and then. Mostly with serial numbers below 1000#. This happens btw with all builds we used so far (14-17).

It´s definitely more often than 1 out of 50 boot-ups.
The only way to bypass this, was to always lower the power that is drawn from the camera by accessories during the boot process.
Let´s say you´ll use the LCD and the EVF, you sometimes get a boot hang. Switch the camera off, pull either the EVF or LCD and restart. Everything´s fine. But it´s quite annoying and for users who are new to the camera it does not inspire confidence at all:-

(In August, one of our cameras had been at Red for service -out of different reason-. Anyway, I´ve informed them also about the boot hangs. But they could not figure out anything.)
 
dont know if that was posted.... the magnify function is doing sometimes strange things... after switching back to normal view - black screen on lcd for example... switching in and out solves it....
 
So there are no other reported "invalid movie atom" corrupted clips except for me and one other person? This is very scary considering the clip is unreadable.
 
I'm getting audio codec faults and a green display on playback on a multiple times per day basis... I'd say 35% of the time we hit play I get that error. It's really bad.

We're shooting 2 cameras both jam synced with lockit boxes and recording guide audio via wireless back from the mixer. Both give playback errors all the time.

We've also had rare record errors. Today I had an "unknown error" after a playback error which caused the record circle in the interface to display but the camera was not recording. Had to reboot to fix. I also had a marathon bad string of boot hangs today... like 10 in a row. Finally after letting the camera sit for about a minute I finally got a boot... but that was in the middle of some live action stuff that couldn't be repeated. Overall a rough day for my camera.

A couple days ago I had another first. Apparently I had a bad black calibration and a gradient shaded rainbow appeared in the EVF. I thought it was just a funky display anomoly but it was actually on the the footage. A new black calibration fixed it but I lost a lot of shots. I've seen solarization in the EVF so I assumed it was like that. Wrong guess on my part.

The audio codec error is really killing us because we can't verify takes. Sometimes exiting and playing again will display the clips but that's very hit and miss and time consuming.

Can't easily send log files because drives are copied and wiped on set.
 
I have #100 and #1760. I have release build 17 on both. I get audio playback error and green screen on both cameras intermittantly. I have exactly what you describe. My solution is to play back 5 or so earlier clips working my way back to the clip with the error. Eventually it will play. I also get solarizations on my evf's every 5 or six boot ups. My solution is to immediately reboot to fix the evf. I do get some boot hangs but a reboot usually works fine.
 
4000 degree shutter

4000 degree shutter

I noticed by Build 17 release that when changing shutter settings in combination with "mode" odd shutter angles pop up, far beyond the maximium of 360. This was noted shooting 2K 120 FPS 1:2. Never noticed this in Build 16
 
black screen in 100 fps

black screen in 100 fps

One time i changed in 25fps 1/50 to 100fps Varidspeed 16:9 in build 17.4.1 and i only got a black screen and was still able to start and stop (saw the edgetime code running). Look like the sensor was off?? After rebooting it was over!!
 
Ramping worse than Build 16

Ramping worse than Build 16

In Build 16, the ramping duration is limited to 4 seconds or 6 seconds for the camera to act properly. In Build 17 this problem is fixed, we can choose whatever ramping duration we want. However, the auto exposure compensation in Build 17 goes backwards. You lose more light as you go from a lower frame rate to a higher one. We have to manually calculate and set the compensation, more unusable than the previous build.

In Build 16, when you map a user key to switch to RAW VIEW from REC709 and back, it will switch to REDSPACE VIEW instead, a very dangerous bug for users. I didn't have a chance to check the same bug on Build 17 before reinstalling Build 16. Can people with Build 17 on your camera please take a look and report your finding? Many thanks.

Recently, we left voice mail and sent in email questions to RED Tech Support but did not get any response. What's going on? Is it because it was a Vancouver number that RED wouldn't call back?
 
We had some serious hangs last week with build 17 on a rental. Several times took VERY long to reboot or just hung up. Haven't had a chance to test things myself but there were no issues with same user the week before on build 16.

Anybody know what this is? should we reinstall 17? Is there a new build coming soon?
 
AquaVideoRed206 said:
We had some serious hangs last week with build 17 on a rental. Several times took VERY long to reboot or just hung up. Haven't had a chance to test things myself but there were no issues with same user the week before on build 16.

Anybody know what this is? should we reinstall 17? Is there a new build coming soon?
Click to expand...

I'd say go back to Build 16 and wait until enough reports on Build 18 come in that it seems safe to make the upgrade. We were able to limp through a shoot recently on Build 17, but it was a drag and in retrospect I wish we'd scrubbed it and downgraded to Build 16 on Day1. We saw the same reboot issues, and others (noted previously in this thread).
 
Build 17 experience (latest release ) :

1-Dark shaded bars rolling vertically across the image :

Specs :
-23.98,1/48th ,4k 16:9 redcode28,HMI magnetic ballast
-2 different RED cameras with build 17 ,2 different commercials, 2 different lighting package, 2 different genny,SAME CREW.

A month ago ,I came out of 25 day shoot on build 16 with these same camera settings and had no problem . hummm....
Of course the solution is to change to 1/60th ,but on the set we were all confused since everyone had worked in these conditions before and had no problems .And my DOP really wanted to stay at 1/48th.The next day ,The lighting dpt. budget busted when going electronic ballasts instead of magnetic . Guess who was not smiling that day ...

Many threads covered this issue but after reading All of them ,I see there are still doubts about the 23.98 and magnetic ballast combo with the RED ..Some say they were successfull some not ,depends on the conditions.Tell me if I 'm wrong but s that s not very reassuring.I even tested 24.00 at 1/48th ,and I still had the rolling bars...Really ? ya really...

So in the end ,is going 1/60th such a big compromise ? When knowing that staying 1/48th will be more expensive for electronic ballasts and possible sound issues?

2-Camera freezes : (Rebooting fixed all these minor bugs )
*after unmounting cf card
*after unplugging monitor cable
*after exiting playback mode

3-Playback mode button turning into a rec button.
While in playback mode, pressing the play button normally pauses the image but on 4 different occasions ,when I pressed it again the camera started recording instead of resuming playback .I could stop it with the rec button, but pressing the play button would again start recording instead of playback.
(Even after pressing the exit button each time) .It finaly stopped when I would press the rec button twice.

4-Occasional recording errors.
More often then on build 16 though ,happens on different cf card,every 40 clips or so . On different fan settings,A split second after you hit record You hear the fan go off but then turns back on .An error message that quickly disappears says ''Internal rec error'' .Clip shows up green in the MAC.
Next clip records fine .

5-Camera would not boot after battery change.
Happened 3 times in 1 day ,different batteries .Eventually woke up after a 10sec rest with no power attached. Camera too hot ?

6-Zooming X2 in playback mode.
build 16 In playback mode I could zoom in for focus check ,but not since I switched to Build 17.With 2 different cameras. Is it because we were in Raw View mode ?
 
I have had only two bugs pop up for me.
1080 playback had a strange color scheme, as if viewing an RGB image with one cable disconnected.
Upon power-cycling, one SDI output will "hang" on the "Powering Down" message (frozen) until the BNC is disconnected and reconnected. Not every time, but often.
Perhaps they are symptoms of the same root issue?
Otherwise, I've been trouble-free (knock on wood)
Cheers,
Harry
 
Harry Clark said:
I have had only two bugs pop up for me.
1080 playback had a strange color scheme, as if viewing an RGB image with one cable disconnected.
Click to expand...

You're looking at one link of the dual-link 4:4:4 HDSDI signal. Use the "PREVIEW" output for 4:2:2 1080p - note this is marked as "720p" on the ET breakout.
 
Ahhhh.
Thanks Cail. That makes sense and looks exactly like what one would expect in that case! :)
Cheers,
Harry
 
camera freze up, have to take battery of to shut down.

camera freze up, have to take battery of to shut down.

shooting stop motion, release build 17, 4K 16:9, resol 36, 1 frame, 1/2sec, shutter.(for high stops), burst, with reddrive.

After shooting, playback did not work, camera froze and stayed in recording mode. Did not powerdown and had to take the battery of. Reboot and could play back and everything look great.

New shooting stop motion, same thing happend.

Robert
 
Not automatically returning to 709 after playback

Not automatically returning to 709 after playback

I was shooting Build 17, 4K 2:1 RC36, REC709
On playback the camera switches to Redspace which is I understand is expected in this build, but it doesn't always switch back to REC709 after playback.
We missed it the first couple of times but then realized that if we physically switched to redspace and then back to 709 it would be OK.
This isn't a huge deal in post because it can be switched back but all the proxies of a few of our clips are in the wrong colourspace, which sucks for the rough cut.
 
You must log in or register to reply here.
Back
Top