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 9 (1.5.0) first impressions

Overall Build 9 seems fairly stable, with the exception of playback mode which seems to lock-up if you move between clips quickly. This has happened about 4 times.

I had a few "codex errors" with build 8, but so far none in build 9. In both build 8 and 9 I never experienced a "crash" that rendered the camera inoperable for more than 2-3 minutes.

Locked up the camera while displaying the Focus Assist. Couldn't exit the menu or gain access to any other menu. Power down and disconnect to clear.
 
I locked up last night after trying to get out of playback of some 2K 72fps footage and could not power down. I disconnected the battery, waited a minute reconnected and powered up but it would not boot. I tried a few times and no luck so I went to bed. This morning it booted fine...anybody experience something like this ?
Aloha
-A
 
Right on joelnet, life is what you invent.
Aloha
-A
 
I've found build 9 beta to be quite unstable. About 80% of the time, menus will be non-responsive in the back of the camera. When the menus were active, they'd randomly cease functioning. It took about 10 reboots to downgrade to the previous firmware.

Doesn't bother me - it's beta firmware - but dammit... I wanted to play with some of the new toys!
 
Its a Cam-puter

Its a Cam-puter

Steve and I had a similar issue when we upgraded for some overcranked 2K and then went to downgrade back to the 9/25 build for straight 2:1 4K. It took 3 tries before it got happy with the older build. Not sure why this is, just don't panic if your first attempt to re-flash the firmware seems to have failed. To my knowledge repeating the up or downgrade procedure will eventually drive out the bugs and order will be restored.

On this same note I advise patience when the computer, I mean camera, no I mean computer, is acting up. Pull the plug to the battery and wait at least 30 seconds, let everything reset - plug it back in and wait some more - then hit the power button.

I don't want to embarrass anybody but on one of my gigs the camera department (who was working directly with the camera while I was cloning CF cards) started telling me that you had to cycle the power at least 3 times to get the camera to work. I found it odd that I could always get it back on track with only one power cycle, turns out they were punching the button every few seconds without giving it time to clear the registers or whatever it does when powered down. Those extra 20 or 30 seconds may seem like forever with an entire production waiting on you but in my experience its worth every second it takes to shoo the gremlins so that you have hours of trouble free operations ahead instead of minutes.

TREAT IT LIKE A COMPUTER with a beta OS - because it is.
 
...

TREAT IT LIKE A COMPUTER with a beta OS - because it is.

Is this an official statement? Or is it stable for a work environment in an earlier firmware version with some options turned off?

I am always out there bragging about this camera to my piers and my clients - but I wouldn't be willing to shoot with one until "lockup" problems are resolved. And as geeky as I am, I don't want to be dealing with uploading firmware on-set while everyone waits around killing any momentum and confidence in the footage.

There are many "film" people out there wanting to see RED fail. So let's all make sure current users stay on top of these issues.
 
Is this an official statement? Or is it stable for a work environment in an earlier firmware version with some options turned off?

I am always out there bragging about this camera to my piers and my clients - but I wouldn't be willing to shoot with one until "lockup" problems are resolved. And as geeky as I am, I don't want to be dealing with uploading firmware on-set while everyone waits around killing any momentum and confidence in the footage.

There are many "film" people out there wanting to see RED fail. So let's all make sure current users stay on top of these issues.

The version we are discussing is a BETA BUILD, not the release build which is recommended.

btw- I find that I need to reboot twice after flashing...after the first reboot the firmware crashes or slows down...a second reboot and I have been pretty stable except for playback. I'll try it out again today and see if I can crash it w/o going into playback mode.
 
Exposure Meter box

Exposure Meter box

Then what are the check marks that occasionally appear inside the boxes?

Exposure hints.. i.e when do each of R G B channels hit a range of values just prior to upper / lower clip.
 
Focus Assist driven lock up comment

Focus Assist driven lock up comment

Locked up the camera while displaying the Focus Assist. Couldn't exit the menu or gain access to any other menu. Power down and disconnect to clear.

Try this, and please let me know if it dos or does not work. If the above happens, go to the VIEWFINDER menu and uncheck the METERS box. Then press the EXIT key, is camera operation restored?
 
Try this, and please let me know if it dos or does not work. If the above happens, go to the VIEWFINDER menu and uncheck the METERS box. Then press the EXIT key, is camera operation restored?

Stuart, screen was stuck and all buttons were locked up. There was no menu access via buttons or the ability to 'Exit' or 'Undo'.

Happened while displaying Focus Assist once and another with Luma Waveform up.
 
Beta Build 9 v 1.5.1

Beta Build 9 v 1.5.1

1.5.1 is posted

And should address the lockup issue. Thanks for the feedback guys.

As always with a new build please test in your application before placing on a job...

BTW - With the camera powered up, press the UNDO key plus the Joystick to force the Status Display to show the camera's P.I.N number (which may say n/a) plus the firmware Build number and version number plus "usage meter" - this in quoted in minutes not hours at the moment.
 
And should address the lockup issue. Thanks for the feedback guys.

As always with a new build please test in your application before placing on a job...

BTW - With the camera powered up, press the UNDO key plus the Joystick to force the Status Display to show the camera's P.I.N number (which may say n/a) plus the firmware Build number and version number plus "usage meter" - this in quoted in minutes not hours at the moment.

Thanks Stuart.

I also noticed w/ 1.5 that I am unable to set the clock. I have not tried with other builds or 1.51 yet. It is off by 13 hrs.

I'll do some more tests when I get in the studio this am.

Is there a seperate system clock besides the time of day TC?
 
ver 1.5.1

How do you change the system time???
I went into TIMECODE and when I change the hours to the correct hour, it does not stick. My clock is 13 hours off.

EDIT:
When I select JAM SYNC it syncs, but when I unselect JAM SYNC it does not revert to time of day.

Shouldnt we have a separate internal clock?
 
MORE INFO ON 1.5.1

So far I have been unable to crash this firmware. Playback is rock solid now. I am also able to instantly record from playback mode and then jump right back into playback...very fast!

It appears that playback quality has been lowered...is this my imagination? I see alot of banding in playback.

Another issue- It seems that the fan is now louder when recording than in the previous firmware (setting is the same- QUIET).
 
It appears that playback quality has been lowered...is this my imagination? I see alot of banding in playback.
According to the release history page, since the first release of build 9 (1.5.0), they "Removed Image Analysis from Playback mode to prevent camera lock-up." Perhaps this is contributing to lower quality review.

Good to hear it's not crashing on you, however... I was having problems with the camera locking up just doing standard things like changing the shutter speed.
 
Back
Top