Yes, you can always place an upgrade image in a "force_preset" folder to force the upgrade on boot.Originally Posted by Mike Garrick
|
|
06-17-2012, 07:29 PM
Yes, you can always place an upgrade image in a "force_preset" folder to force the upgrade on boot.
06-17-2012, 08:15 PM
Thanks Trent nice to know ......still deciding which way to jump.
P.S. Also thanks Tim about the "live" lemo connection bit.
06-17-2012, 11:19 PM
This is starting to scare me about updating firmware for my cam. I have a very important shoot in a couple of weeks and I just don't want to risk it and have these errors to happen. looks like i'll be waiting for RED to come out and acknowledge these glitches.
06-18-2012, 12:21 AM
I've only updated to release builds and this is my first problem. I've gone back to the previous build and feel confident in that. But I hear ya, it's a little unsettling when a software updates turn your camera into a $15k brick.
I still have faith in RED though! I'm sure this will get resolved by the next build.
06-18-2012, 12:45 AM
UPDATE !!!
It appears my problem has been solved ...fingers crossed.
As stated before I got the split white screen & after a couple or retry's with the upload/update thing I was still getting the problem.
Then I decided to check the black shading status of the sensor & I noticed the pixel formation was split between 2 sides of the screen with the boundary happening at exactly the same place as boundary of the half white screen. Anyway I performed a black shade & now it appears to be working as intended with numerous starts up with no sign of the half white screen . Normally I black shade before a job, just didn't get around to it yet after the update.
So my take on this is always perform a black shade after updating the software.
| « Previous Thread | Next Thread » |
