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

New Build

SF Geek

Banned
Joined
Dec 28, 2006
Messages
860
Reaction score
0
Points
0
How's the testing going with the new build? I just want to reiterate that the initializing logo could go away and be replaced by a text only version that sits low in the look around area so there is a clean frame while booting up. We don't need the logo. Everybody knows what we're shooting on. EVERYBODY.

thanks
 
  • Thread starter
  • Banned
  • #2
Still testing? It's been a while.
 
I agree- seems like it has been awhile since the builds have been updated. Whatever happened to the 4.5k mode? The builds used to come out a lot more frequently, and their status was updated. But ever since the scarlet and Epic have been announced / re-announced it seems to have gone dead....
 
The builds came hot and heavy as we frantically fixed problems and enabled features. All that is left are the hard features to enable. We are working on the next build but because their isn't the same sense of urgency as before, we are taking our time to get each build right.

As for 4.5K mode, it is a bonus. We'll put it out as soon as we can, but it was never in any spec. It was my idea to add it. I'm waiting just as you are, but patiently. :-)

Jim
 
The updates were frequent because besides the additions they were also fixing the firmware/codec bugs.

Now that the camera is out of beta and almost stable (only the random boot failures remain) i think we will not see new build so often. I believe we might never see the 4.5k mode but i still hope we will.

EDIT: Oops! Jim was faster!
 
Jim, just remember to add shading for outside the guides :)
 
Jim, just remember to add shading for outside the guides :)

.... and clips thumbnail for playback from the camera

and many other obvious features but I guess they will not happen.
 
  • Thread starter
  • Banned
  • #9
Ahem. Actually the camera isn't totally stable. There are still playback issues with build 17. I know there are people that don't have issues, but there are many people that do. I'm not looking for new features. I just want full stability of the camera plus the least amount of high detail codec issues, like Leo's voodoo tree. I don't need 4.5k or any other options. Just need what I said , plus a clean frame while the camera initializes and like someone else said, it would be nice to be able to darken the areas around the assigned frame guides.
 
I'm glad to hear that things are still being worked on- the slow down to the release of builds and the timing of the announcement of the new cameras coincided a little too close- so it felt a little odd from a customer stand point. But I do understand that future builds will be slower to be released.

I agree with what has been mentioned here- get rid of that Red Logo on the screen- what is the point of having instant preview if it is covered by a large logo?

Faster startup / boot up times are alway welcome.

Thanks again Jim for all the work you and your team have been putting in to the camera. I've enjoyed shooting with it. :)
 
I'm very much looking forward to 4.5K.

Stephen
 
As long as we are on the subject,

Voltage display, auto shutdown based on voltage.

Lets not forget the pesky roll# bugs. Not a huge deal but it throws a wrench into the works for fast reloads

Cleaner boot up screen.

Scan reverse for low mode steadicam. ( Had a DP on a TV Pilot shake his head in dismay and say, "why the hell wouldn't you have that on a professional camera?")

also the weird solerized viewfinder bug. Again not a big deal to unplug and replug, but it's a pain.

Making it so that it doesn't take forever to scroll up to 120 fps.

Love my Reds, just saying.....

Cheers,

Nick "Not trying to piss of feature givers" Gardner
 
We are working on the next build but because their isn't the same sense of urgency as before, we are taking our time to get each build right.

uh, actually i'm still on b16 because got scared of playback errors on b17, reported here on reduser, and do not like to use a beta on production ... this would be ok as b16 is ok, but when my 16GB cards will finally arrive i guess i'll have to move on ... what i think is we miss is a bugfree 16GB CF compliant build .... or the infamous playback errors on b17 are more limited than i think?
 
I still use B17 because i have 16 gig cards and I have the new upgrade, so I like the ipin setup and the user generated frameguide. It just sucks to always have to explain why the image went green during playback and a big error warning shows up on the monitor.
 
The builds came hot and heavy as we frantically fixed problems and enabled features. All that is left are the hard features to enable.

I get audio codec playback errors (greenscreen) every day I shoot.

It's a fantastic camera but if someone there hasn't been working on that playback bug but is instead working on the new cameras that would be kinda wrong IMHO. That bug has been there since November.
 
Scan reverse for low mode steadicam. ( Had a DP on a TV Pilot shake his head in dismay and say, "why the hell wouldn't you have that on a professional camera?")

I second that! I shot a commercial last week where half the shots were low mode steadicam. It's not difficult to reverse them in post but it costed time.
 
I get audio codec playback errors (greenscreen) every day I shoot.

It's a fantastic camera but if someone there hasn't been working on that playback bug but is instead working on the new cameras that would be kinda wrong IMHO. That bug has been there since November.

Agreed, I get the green screen fairly often as well. :(
 
I agree with several of the posts: I consider it far more important to make the camera more stable than to add new features. Soooooo many problems with B17. Clients are a little fed up with this; some even turned back to film or HD.
We had to reinstall B16 on our two cameras: no more problems... but we can´t use our six 16GB CF cards!
Please... Build 18 final release as soon as possible... It´s already been for months in beta.
Guido
 
I agree with several of the posts: I consider it far more important to make the camera more stable than to add new features. Soooooo many problems with B17. Clients are a little fed up with this; some even turned back to film or HD.
We had to reinstall B16 on our two cameras: no more problems... but we can´t use our six 16GB CF cards!
Please... Build 18 final release as soon as possible... It´s already been for months in beta.
Guido

Do you change your CF module after upgrading B17?

We update to B17 both cameras two months ago and have no one problem.
 
I'm still on build 16 on my camera because of the bugs people reported on build 17, but last week I had to work with a rental camera (a newer one) that came with build 17... Had loads of green screen bugs when trying to play back footage... Also, there was a microphone plugged in that needed phantom power, and I noticed that I needed to reactivate the phantom power checkbox in the menus every time I restarted the camera.

This build has been released so long ago, I wonder why these bugs are still there ?

Are these issues still there in beta build 18 ?
 
Back
Top