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 issues?

S

SF Geek

Banned
Joined
Dec 28, 2006
Messages
860
Reaction score
0
Points
0
It seems that since changing over to build 17 that my camera hangs on bootup more often. It never hangs for more than two times in a row but it seems to hang 1/3 of the times I boot it up, regardless of battery capacity. I also had playback errors at least three times with a green screen and the "Rocketio playback error". I was able to get playback after trying a few times. I also had a clip that seems corrupted, even on the drive. When I try to play a quicktime proxy, the error comes back as "The movie file could not be opened. An invalid public movie atom was found in the movie." The file doesn't work with Red Alert, Red Rushes, or Redcine.

All of the issues might not have anything to do with 17, but I've never had the last two issues before.
 
We had some serious hangs on a recent rental shoot, took 15 minutes or so before could boot up again. Same people used it a week earlier on build 16 and I've never had a problem with it before. Was going to contact RED, but haven't gotten around to checking it myself.
 
  • Thread starter
  • Banned
  • #5
I've really been noticing bootup hanging, at least 50% of the time.
 
I have experienced boot hanging since B15.

Yes, seems to happen more often now. I am glad to finally have a hot swap battery mount, so the boot hang will only be an issue at the start of the day and after lunch - as oppossed to having a bunch of people standing around nervously waiting.

What's the word RED?
 
Hello,

First question, is this where we report Build 17 bugs ? Maybe this category should be renamed Release Build bugs, or, rather, a new category should be started called "Build 17 Bugs".

Anyway, we have started a feature last week, this is going to HD, so it seemed logical to go with Build 17 and use the 4KHD mode, also we wanted to enjoy the benefits of 1:1 pixel zoom and the supposed improved reliability of Timecode sync (see below).

We are shooting 25 fps.

So...

First off, we have had a few boot hangs, but well, I've always had those since build 13.

Secondly we had a few Audio Playback errors with the green screen. Only the first couple days.

Then we started getting some banding in the EVF, and it's getting worse, today the EVF was barely useable. I tried rebooting, resetting to factory defaults and changing the cable for a new one, no change. This evening I reinstalled build 17 but haven't had a chance to check with the EVF yet, I'll do that first thing tomorrow morning.

Also, it happened twice today, the camera got stuck in Raw view, I don't know how. I was able to go into the menu and switch it back, but how the hell did it switch from Redspace to Raw view ?

About Timecode, we are using a TC generator plugged in to the camera at all times, yet it still seems to be off, when we check it in standby there is an approximate 1 second delay on the camera. As soon as we start recording it jumps forward to something close to the correct TC, but actually off by a few frames (this was checked in post afterwards). This has also been the case on the previous film shot with my camera with build 16.

Besides that the camera is performing well, but these things are a hassle, particularly the EVF. The DP is getting quite upset about that. I have to say we are shooting in very cold conditions right now. Could that be causing our problems ? We'll see if things change in a warm environment.

Cheers,
Damien
 
There's already a thread for B17 errors...

Apparently, the solution is to not use playback when audio has been recorded. (If audio is not being recorded, make sure it's turned off.)

I want to jump to B18 but haven't heard anything positive with it... B17 has too many nice features that I'm used to... Won't go back to B16 but something should be done to fix this build before releasing "another" build.

Are we even ready for B18/B19? (Only if it fixes the current bugs...) Can we fix the R1 bugs now? Or are Scarlet/Epic renders more important?
 
Shawn Booth said:
There's already a thread for B17 errors...

Apparently, the solution is to not use playback when audio has been recorded. (If audio is not being recorded, make sure it's turned off.)

I want to jump to B18 but haven't heard anything positive with it... B17 has too many nice features that I'm used to... Won't go back to B16 but something should be done to fix this build before releasing "another" build.

Are we even ready for B18/B19? (Only if it fixes the current bugs...) Can we fix the R1 bugs now? Or are Scarlet/Epic renders more important?
Click to expand...

Thanks for the reply.

Yes, the Audio Playback error is minor in my book. I've always found a way to play back the clip never the less.

The other problems are more problematic. I forgot to mention, the image on my camera also sometimes switches to peaking while in Redspace or Raw View and no way to switch it off, really odd.

Cheers,
Damien
 
The EVF does have odd behaviors from time to time doesn't it? Cable switching doesn't help, power cycling usually does but I've found the best solution for certain issues (whole camera system) is:

Acceptance.

And I move forward and keep shooting... while grumbling under my breath of course. Some problems are just there like visiting in-laws...
 
Shawn Booth said:
The EVF does have odd behaviors from time to time doesn't it? Cable switching doesn't help, power cycling usually does but I've found the best solution for certain issues (whole camera system) is:

Acceptance.

And I move forward and keep shooting... while grumbling under my breath of course. Some problems are just there like visiting in-laws...
Click to expand...

Some things I can live with, but yesterday the banding on my EVF was so severe, I consider it unacceptable, as does the DP I'm working with. We have 3.5 more weeks of shooting, he doesn't want to keep shooting like this.

I've reported this issue through Red support, not all the other ones, yet...

Cheers,
Damien
 
Update,

After a reinstal last night : no change.

However this afternoon we were inside, and in a much warmer environment, banding seems to have nearly disappeared. I'll give updates as our shoot advances.

Cheers,
Damien
 
B16 was stable as hell. 17 booty much loinger and in 50% hangs. I do not record audio nor has the feature been enabled. The wheel on the EVF does not switch anything anymore. Buttons work. Rest I had no issues. Thinking about going back to 16.
 
Going Back

Going Back

Markus Rave said:
B16 was stable as hell. 17 booty much loinger and in 50% hangs. I do not record audio nor has the feature been enabled. The wheel on the EVF does not switch anything anymore. Buttons work. Rest I had no issues. Thinking about going back to 16.
Click to expand...

Has anyone gone back to 16? I start a week long shoot Monday and I am considering going back.
 
If you do go back to 16, use 17 first to check focus when you prep with your lenses and then go back.
 
used b17 the first time on a commercial production and i had the feeling the boot time takes longer and i had to unplug everything (lcd, evf, drive) before booting.

several times the booting started, camera display just said "booting" and did not show the usual dates, infos, etc. - suddenly the fan became loud and camera seemed to restart.

@damien:
my evf stopped working from one day to another - but it was cold. i tried to warm it up, but didn't improve. did your warming up improve the picture?

regards,
martin
 
I got the "invalid public movie atom" too! I need to convert the r3d file to a QT because the proxies don't work.. but it quits out of Red Alert, Red Cine, and Red Rushes. I kind of NEED that 20 min. interview clip too. FCP editor.

was anyone else able to find a solution to this problem?
 
Build 17 boot hangs

Build 17 boot hangs

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?
 
I'm going back to 16. The "invalid public movie atom" corruption in 17 is too risky to have in a release build. Luckily it happened on a bad take, but if it was an important shot I can guarantee that that director and production company would not use the red after that. Boot hangs are annoying. Corrupt clips are unacceptable.
 
You must log in or register to reply here.
Back
Top