Trent Lillehaugen
Red Team
- Joined
- Aug 22, 2011
- Messages
- 1,172
- Reaction score
- 0
- Points
- 0
Yes, you can always place an upgrade image in a "force_preset" folder to force the upgrade on boot.
Welcome to our community
Be a part of something great, join today!
Updated Firmware, REDMAG now no worky... =(
- Thread starter Jarek Zabczynski
- Start date
Yes, you can always place an upgrade image in a "force_preset" folder to force the upgrade on boot.
Mike Garrick
Well-known member
Thanks Trent nice to know ......still deciding which way to jump.
P.S. Also thanks Tim about the "live" lemo connection bit.
P.S. Also thanks Tim about the "live" lemo connection bit.
Michael Pyon
Well-known member
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.
- Thread starter
- #24
Jarek Zabczynski
Well-known member
- Joined
- Apr 3, 2007
- Messages
- 2,410
- Reaction score
- 4
- Points
- 38
- Location
- Los Angeles
- Website
- www.jarek.com
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.
Mike Garrick
Well-known member
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.
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.