Joe Shemesh
Well-known member
Sent an Incident Ticket with a concise version of the below post with absolutely no response.
Stuart replied to my post on the boards - sent him a PM and then heard nothing.
I'd like to know what else I should have done in order to get some help. Managed to limp through the week by not powering the camera down for 4 days and nights and have now shipped it off for upgrade program - with Body Hot issue still persisting.
Sure thing Michael/Stuart - doing very long days on-set with no connectivity to the web (plus the time difference) has made posting somewhat difficult . Also didn't want to alarm all other users (incase this is an isolated set of issues) until I'd heard back re my incident report.
Until updating to Build 20 V20.1.2 a few days ago, I'd only operated my RED using Build 16 and 18, and in both cases not had a single issue in almost a year of shooting. Needless to say, it came as a surprise to be faced with multiple issues 2 days after installing new SW.
Some of our issues
Day 1 - Body Hot Warning and corrupted back screen display on first boot-up of the day (7.30am exterior shot on a bitterly cold winter's morning). After numerous tries to boot up, with the same result, I reinstalled Build 20 V20.1.2 - only to be faced with the same issue again. On boot-up 10 or so, Body Hot Warning disappeared and all seemed to be fine but.......
Now, repeated 'RED Drive Incompatible with project warning' on trying to record 4K anamorphic. Having already lost nearly 2 hours, it was decided to record at Redcode28 to 8Gb CF cards.
Battery % readout stuck on 'DC' regardless of power supply.
Powering up after 45min lunch break resulted in Body Hot Warning again and took 5 reboots before warning disappeared.
Day 2 - Body Hot Warning and corrupted back screen display on first 8 reboots. Once initialized properly, seems anything longer than an immediate reboot, after changing batteries, results in the Body Hot Warning which affectively locks up all camera functions again. In the hope of not being faced with this problem tomorrow morning, I've decided to leave camera running on DC power through the night.
RED Drive working fine with Redcode36 4K anamorphic today.
Battery readout 'DC' only.
Stuart - unless I'm missing something, I've not been able to recover a log file on failed initializing because the camera menus freeze up, only allowing powering down. Unless you have any interim suggestions, I'm due to send camera back to US this coming Monday for audio board upgrade, so will try and get through the next few days of the shoot.
best
joe
Stuart replied to my post on the boards - sent him a PM and then heard nothing.
I'd like to know what else I should have done in order to get some help. Managed to limp through the week by not powering the camera down for 4 days and nights and have now shipped it off for upgrade program - with Body Hot issue still persisting.
Sure thing Michael/Stuart - doing very long days on-set with no connectivity to the web (plus the time difference) has made posting somewhat difficult . Also didn't want to alarm all other users (incase this is an isolated set of issues) until I'd heard back re my incident report.
Until updating to Build 20 V20.1.2 a few days ago, I'd only operated my RED using Build 16 and 18, and in both cases not had a single issue in almost a year of shooting. Needless to say, it came as a surprise to be faced with multiple issues 2 days after installing new SW.
Some of our issues
Day 1 - Body Hot Warning and corrupted back screen display on first boot-up of the day (7.30am exterior shot on a bitterly cold winter's morning). After numerous tries to boot up, with the same result, I reinstalled Build 20 V20.1.2 - only to be faced with the same issue again. On boot-up 10 or so, Body Hot Warning disappeared and all seemed to be fine but.......
Now, repeated 'RED Drive Incompatible with project warning' on trying to record 4K anamorphic. Having already lost nearly 2 hours, it was decided to record at Redcode28 to 8Gb CF cards.
Battery % readout stuck on 'DC' regardless of power supply.
Powering up after 45min lunch break resulted in Body Hot Warning again and took 5 reboots before warning disappeared.
Day 2 - Body Hot Warning and corrupted back screen display on first 8 reboots. Once initialized properly, seems anything longer than an immediate reboot, after changing batteries, results in the Body Hot Warning which affectively locks up all camera functions again. In the hope of not being faced with this problem tomorrow morning, I've decided to leave camera running on DC power through the night.
RED Drive working fine with Redcode36 4K anamorphic today.
Battery readout 'DC' only.
Stuart - unless I'm missing something, I've not been able to recover a log file on failed initializing because the camera menus freeze up, only allowing powering down. Unless you have any interim suggestions, I'm due to send camera back to US this coming Monday for audio board upgrade, so will try and get through the next few days of the shoot.
best
joe
