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

EPIC / SCARLET Firmware 3.3

I believe 1k was an afterthought - a "oh look, because we can" extra bonus treat, not part of the original specs. Throwing in extra little bones to their users when they dig them up is exactly consistent with the gospel of RED. Your perception is entirely backwards. Not to beat what should already be the dead horse...

How did saying that something is a shame manage to get some of you guys so bent out of shape. I asked what was seemingly a pretty valid question, that then got answered, to which I inferred it was shame. Sheesh, carry on with the discussion about how great the build is.
 
has someone problem with lcd stuttering when panning? i tried 3.2.19 now, but it is same. lcd stuttering was fixed in 3.2.16 and was working ok.
 
Last edited:
- is there a way to just switch between 100% clean and normal DSMC menu without cycling thru all other modes ? I tried to create a setting for that but I had only 1 monitor connected and couldn't access the save preset menu while in clean mode ! Would this work if I connect an SDI with menu to create the 'clean EVF' preset ?

Yes, you should be able to setup a preset like that using an SDI monitor to control the camera. However, your preset would include, in that case, MENU mode for the SDI monitor. if you are OK with that then it should work.

Unfortunately since you can only create presets in camera and it requires one screen to be in menus mode to do so there are going to be some limitations.
 
3.3 is great. Still going to test out more but the new features and visuals on screen are nice to work with. The only thing I have noticed so far is a 24.98 FPS option on 4K with Scarlet. Is the still the 24.00 FPS option but labelled wrong? Sorry if this has been mentioned, came to the thread late and haven't read through all of the pages. As many have also mentioned, the videos are well appreciated, very informative.
 
To add to this, I checked it on my Scarlet. The Aperture setting works great and the Focus setting worked fine after switching the Focus Mode once. Now it works in any Focus Mode. Remember the Lens has to be in AF mode. . . . But the display is fine. I'm not sure if I understand correctly what you mean by wobbling numbers, but the display / appearance of the numbers themselves are stable.

Hi Patrick. Thanks for the feedback. I had switched my focus mode to several different ones during the course of this testing, so I don't think that was the problem. I was mostly in "single" AF mode when I encountered these issues, but to be absolutely sure what's going on, I will do a more methodical test switching in and out of different modes and then testing the lens dialog responsiveness. What I meant by "wobbling numbers" is that when you rotate the navigation scroll wheel, the numbers jump a bit from 2.8 (I was running the lens wide open most of the time because of low light in the room where I was testing) to 3.0, 3.? and back to 2.8. This was happening in a flash as you scroll, with the numbers always settling back to 2.8 immediately, no matter how rapidly or slowly you scroll. There would be an instantaneous flicker in screen brightness concurrent with these number jumps as if the lens was trying to dial in a different f-stop but could not do it. The numbers would MOST of the time change in the focus distance parameter but had the aforementioned behaviors of displaying long distances that serve no practical purpose at all.

About the focus size increment: as far as what I heard, the team is working hard to make this happen.

Great to know. I understand completely (well, not really, but I can imagine) how difficult a task this must be. I just wasn't sure what limitations there might be on the ability to implement it, and I didn't want to keep harping on it if it's not doable.

I have found one more thing which would be great to have added:

When you map a Cycle Function (like Focus or DisplayCheck Mode) to a button, have the display not read out "Key Action: Display Check Mode: cycle" but name the actual mode it has been set to. Of course this can only be done for non-user-presets, but it would make the standard cycle modes a lot more comfortable. For Display Check Mode this may not seem all that necessary because the look of the screen changes, but for example focus cycle is hardly useable because you have no clue (or feedback) to what mode you just set it to.

+1 on that . I eliminated the default cycle AF mode behavior of my SH button because I found that cycle function useless without some display of what mode you are actually in. I actually wish there was some way to eek out a little bit more screen real estate somehow on the menus overlay for the LCD so that you could have continuous indication there of your AF mode.

Also for the RED team: would you want the log files to see what caused the spontaneous, immediate shutdown of my camera when I was playing around with presets and key mapping? If so, is it just a matter of copying the log file that is on the REDMag that was inserted in the camera when the shutdown happened?
 
Sounds like a great build, unfortunately our Epic-M is back for the upgrades. Can't wait to get it back and try out this build
 
has someone problem with lcd stuttering when panning? i tried 3.2.19 now, but it is same. lcd stuttering was fixed in 3.2.16 and was working ok.

Yes, I'm getting the stuttering as well, but not all the time. It seems to happen for a brief period after having made some selection or other inside one of the menus.
 
someone says that restart camera or unplug monitor helps. im on 3.2.16 for now which is without any stutter or issues.
 
+1 on that . I eliminated the default cycle AF mode behavior of my SH button because I found that cycle function useless without some display of what mode you are actually in. I actually wish there was some way to eek out a little bit more screen real estate somehow on the menus overlay for the LCD so that you could have continuous indication there of your AF mode.
Worse than useless; it's possible to press that button accidentally and shift from single mode to manual (or whatever comes next) and, without knowing it, be out of AF mode entirely.

I noticed that when you display the lens dialog (easiest way is up arrow on navigation group when in the aperture slot), the scroll wheel on the navigation group --both on the side handle and on the redmote -- do not actually change the aperture values as I assume they are meant to.
This may not be what you're looking for; it changes the values without bringing down the menus. But if you're using the side handle to change ISO, iris, etc., the most flexible and quickest way I've found so far is to use the top four SH buttons combined with the front rotor programmed to "slot: next value" and "slot: previous value."

These button functions and presets have gotten pretty slick.
 
Love the update...BUT once I shut the camera down the camera will no longer start up. Fan spins LCD on Side handle lites up then camera stops/fails starting up.

I have had to reflash the update 4 times now and the samething has happened everytime I shut the camera down for the 1st time.

Any help/fix for this? I'd love to use this build here soon.

Thanks a bunch,

-Dane
 
@Dane

Will it boot up the first time after the 3.33 firmware update, but subsequent reboots don't work?

Try this:

under maintenance - restore factory defaults.

Power down.

Force upgrade to 3.33

restore factory defaults again.

power down

power up.
 
@Dane

Will it boot up the first time after the 3.33 firmware update, but subsequent reboots don't work?

Try this:

under maintenance - restore factory defaults.

Power down.

Force upgrade to 3.33

restore factory defaults again.

power down

power up.

Yep, subsequent reboots will not work. I'll give your tip a try. Thanks!

-Dane
 
Stuart or RED TEAM:
I had a glitch come up...

I set a preset for the "power up" sequence and couldn't boot the camera anymore when plugged into the A/C Adapter.
I could boot it via Sidehandle REDvolt, removed the preset and it booted nicely after that.
 
someone says that restart camera or unplug monitor helps. im on 3.2.16 for now which is without any stutter or issues.
Is it possible that the SDI and HDMI are both enabled?

I seem to remember the first time I went to that setup screen, the SDI was already enabled, but ... I could be imagining that?

I use only HDMI. Maybe I clicked in the wrong place, and the SDI got checked by mistake?

I'm just thinking that it must use some extra CPU to process the signal for SDI and HDMI - and that could be causing the behavior you are seeing?
 
Yep, subsequent reboots will not work. I'll give your tip a try. Thanks!

-Dane

Seems my camera wasn't liking presets I was loading from previous builds. I went though and recreated all the presets within the new build and the camera is rebooting properly.

Thanks Dan!

-Dane
 
Back
Top