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

User Key / View RAW problem

Petri Teittinen

Well-known member
Joined
Apr 29, 2009
Messages
988
Reaction score
0
Points
0
Age
57
Website
www.saitti.org
I have an odd issue with VIEW RAW when mapped to a User Key. I've tried mapping to user keys 1 and 2, with the same effect.

The issue being that the view gets stuck in RAW mode, and pressing the User key does not toggle RAW view. Weirdly enough the button works like it should after I've mapped the function to the key, but stops working once the camera is shut down. In other words, the toggle no longer works after a re-boot.

I can force it to work by entering the menu and mapping the function to another User Key. But again, the button only works until the camera is shut down.

I'm now on 30.6.12 and the issue is still present. I first noticed the problem in the firmware which fixed the noisy blue channel (can't remember the version number, though).
 
I get this all the time. After your reboot, you have to manually switch the color apace to to REDcolor and then the function button will work. Odd though.
 
I get this all the time. After your reboot, you have to manually switch the color apace to to REDcolor and then the function button will work. Odd though.
Good to know I'm not alone in this. I was unaware of that trick, thanks!
 
I have an odd issue with VIEW RAW when mapped to a User Key. I've tried mapping to user keys 1 and 2, with the same effect.

The issue being that the view gets stuck in RAW mode, and pressing the User key does not toggle RAW view. Weirdly enough the button works like it should after I've mapped the function to the key, but stops working once the camera is shut down. In other words, the toggle no longer works after a re-boot.

I can force it to work by entering the menu and mapping the function to another User Key. But again, the button only works until the camera is shut down.

I'm now on 30.6.12 and the issue is still present. I first noticed the problem in the firmware which fixed the noisy blue channel (can't remember the version number, though).
I have this problem all the time, I have to remap just this function in the user keys, all others remain, but its not consistant
 
I think this is a long standing bug that's never been flagged up/moaned about too much since it's easy to work around, but yes, it's been there on every Red One I've worked with, although I'm not sure it's on every reboot.
 
RAW switch

RAW switch

When you have a chance, try the 31.8.10 Beta build. I am pretty sure that this was fixed somewhere along the line..

I'd need to dig into the sustaining log notes to tell you exactly where, but I do recall it was investigated ...
 
+1
In the big scheme of things, no big deal. But I get that issue quite frequently. Hoping the new build makes it vanish.
Cheers,
Harry
 
When you have a chance, try the 31.8.10 Beta build. I am pretty sure that this was fixed somewhere along the line.. I'd need to dig into the sustaining log notes to tell you exactly where, but I do recall it was investigated ...
Seeing as some folks are reporting issues after upgrading to 31.8.10 beta, I think I'll wait for the next release build instead.
 
I went to the lengths of making a demonstration video to illustrate this bug to the guys in support... be nice if it is tweaked in the newest firmware, I'll take a look :)

For what its worth, its a totally repeatable issue and understandable really from a programmers perspective. If you shut the camera down in view-raw the button stops toggling, shutting down in view-redcolor is fine. If it bugs you, try and remember to power off with the view in RC.
 
Firmware

Firmware

Seeing as some folks are reporting issues after upgrading to 31.8.10 beta, I think I'll wait for the next release build instead.

I'd suggest to give it a try. Those kind of reports happen every time we do a software release. Then funny enough they go away...
 
Back
Top