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

It is, is that option not showing up on your camera, and if not, did it previously ?

HELP! Looks like Fantom power is not enabled in the channel 1/2 audio. Worked fine in latest release build
You can only choose bal.48+ in the channel 3/4 pro I/O analog
Or do I miss something?
 
Bug found in 3.3.3

Bug found in 3.3.3

Hi all.

Found a bug in Scarlet FW 3.3.3:


Settings -> DISPLAY -> MODES -> FOCAL DISTANCE -> switching between Imperial and Metric doesn't work, display remains imperial.

Works in 3.1.6.

Imperial doesn't make sense to me, so i hope this will be solved in the next update.


Thanks,


Martin Beek
 
Audio record and playback with phantom power are working fine for me. I am using cables made by our engineer, not Red cables; I don't know if that makes a difference.

Good shooting and best regards,

Leo
 
Hi all.

Found a bug in Scarlet FW 3.3.3:


Settings -> DISPLAY -> MODES -> FOCAL DISTANCE -> switching between Imperial and Metric doesn't work, display remains imperial.

Works in 3.1.6.

Imperial doesn't make sense to me, so i hope this will be solved in the next update.


Thanks,


Martin Beek

Yup, same here. You don't have to bother with the imperial stuff:P Take the first step in helping the USA make the switch. Anyone who are capable of shifting decimal points can work with the metric system. Not so easy the other way. 95% of the world is already on board with the metric system, lets make it 100!
 
Audio record and playback with phantom power are working fine for me. I am using cables made by our engineer, not Red cables; I don't know if that makes a difference.

Good shooting and best regards,

Leo

Good to know; I am using RED original XLR cables to fantom power a Sennheiser MKH416 - doesn't work in 3.3
 
Yup, same here. You don't have to bother with the imperial stuff:P Take the first step in helping the USA make the switch. Anyone who are capable of shifting decimal points can work with the metric system. Not so easy the other way. 95% of the world is already on board with the metric system, lets make it 100!

Nah. With all due respect to our metric centric friends, there's nothing wrong with using alternative units of measurement... or driving on the other side of the road for that matter. Besides it's not the fact that a unit of measurement is decimal or not, it's more a question of whether those units actually convey information to you.
 
I upgraded me Scarlet to 3.3 without problem. Now I want to upgrage the redmote to the matching 4.04 beta, but I'm having a problem. Page 200 of the Scarlet 3.3 manual says I need a file called REDMOTE_upgrade_setup.exe file. On Downloading and unzipping the Redmote firmware upgrade all I get is a file called redmote1.bin. I'm probably overlooking something simple, but I"d appreciate help as it's got me stumped. (I can find an redmote_upgrade_setup file in the prior Scarlet 3.18 firmware download, but don't know if this is compatable/safe to use with redmote 4)
 
I upgraded me Scarlet to 3.3 without problem. Now I want to upgrage the redmote to the matching 4.04 beta, but I'm having a problem. Page 200 of the Scarlet 3.3 manual says I need a file called REDMOTE_upgrade_setup.exe file. On Downloading and unzipping the Redmote firmware upgrade all I get is a file called redmote1.bin. I'm probably overlooking something simple, but I"d appreciate help as it's got me stumped. (I can find an redmote_upgrade_setup file in the prior Scarlet 3.18 firmware download, but don't know if this is compatable/safe to use with redmote 4)

The bin file is the firmware only. Download the DSMC Resources package from https://www.red.com/downloads - this contains the upgrade tool.
 
Nah. With all due respect to our metric centric friends, there's nothing wrong with using alternative units of measurement... or driving on the other side of the road for that matter. Besides it's not the fact that a unit of measurement is decimal or not, it's more a question of whether those units actually convey information to you.

In France altho we are a metric country I'd say over 90 % of the good focus pullers will work with imperial lenses. It somehow makes much more sense to pull focus from 17 to 10 feets rather than from 5.7 m to 3.3 m.
For those short distances the imperial system is much more meaningful / precise once you get used to it.
 
My EPIC spontaneously shuts down when the EVF is unplugged:
EVF plugged into the brain
Touchscreen LCD plugged into the Pro IO
Brain given priority in Settings/Audio-Video/Monitor Control/Priority

Does NOT happen when the Pro IO LCD out is given priority.

Is there a way to have active menus on both at the same time? I'd like to have the touch screen active out of the Pro/IO and maintain the usability of Menus in the EVF from the sidehandle. This way either myself or the AC could make adjustments.

Loving this build. So many great additions. Working for me flawlessly otherwise.
 
I've had a re-occurring issue on my Scarlet where when I switch from 4K to HDR, then change to 3K and set fps to 23.98, the exposure goes really dark. I adjust it so the exposure is correct, then as soon as I press record, it seems to fix itself and is back to the overexposed track maybe? So it appears that something in the switching to HDR mode is causing it to expose for the second, underexposed track. Not sure if this is a bug and it's not a big deal but thought I'd share.
 
I've had a re-occurring issue on my Scarlet where when I switch from 4K to HDR, then change to 3K and set fps to 23.98, the exposure goes really dark. I adjust it so the exposure is correct, then as soon as I press record, it seems to fix itself and is back to the overexposed track maybe? So it appears that something in the switching to HDR mode is causing it to expose for the second, underexposed track. Not sure if this is a bug and it's not a big deal but thought I'd share.

This is a (known) small bug where the display show the X-track in HDRx mode, instead of the base exposure. This was supposed to be fixed in the latest build - is that what You are running?
 
Pretty happy with the vast improvements in this build.. Audio on Playback... Sweet...
Ok, but we have a slight problem here on video out... HD-SDI out doesn't work... HDMI works fine... We went back to 3.2.19, but now we have the same problem, no video on HD-SDI..
So we've come back to 3.3.3 for now, cause audio on playback was important to us... and we're monitoring on HDMI out for now.
Any suggestions? Any advice?
We've already filed a log on the RED Support page... & awaiting their reply.

Thank you (in advance) for any help/suggestions.

Requesting RED support team to please offer us a solution to this problem... its long overdue...
Thank you!
 
Hey Jeetu,

please send a .log file to sean at red dot com

thanks!
 
Scarlet 3.3 -> lcd stutter is back!

Scarlet 3.3 -> lcd stutter is back!

It took me a number of support tickets, months and two firmware updates until the LCD stutter problem was solved; now it's back with 3.3.3 so i had to roll back to 3.2.19.
Many Scarlet and Epic users complaint about the LCD stutter in different threads. I hope the support team will look into this a.s.a.p.

Martin
 
Everything seems to be working ok with 3.3.

One question, is it normal to have a major lag in the sound over 24Hz hdmi?

The sound is there, but it's a quite considerable lag.
 
Everything seems to be working ok with 3.3.

One question, is it normal to have a major lag in the sound over 24Hz hdmi?

The sound is there, but it's a quite considerable lag.

No, that isn't normal. Please create a support ticket and send in a log file.
 
Just finished up a big job for a major video game company, shooting a long series of interviews on Scarlet, with firmware 3.3 . Worked like a champ. not a single issue.

This build has been the biggest leap forward yet, at least for me:)
 
No, that isn't normal. Please create a support ticket and send in a log file.
Had noticed some lag during the shoot (model commented on it), but re-checked each clip where I used clapper at beginning and end (recorded thru hdmi Intensity Pro to ProRes 422), and I don't see any lag at all.

Must have been a Mac OS X issue?

The R3D's don't have any lag either when I view them in Premiere on Win7.

I'd also mentioned seeing some trails thru hdmi earlier. Apparently, that just shows up on the monitor when using low light, as I'm not seeing anything on the R3Ds or the hdmi direct recording.

Wish could record at 23.98 thru HDMI, but ... don't expect to need the footage recorded thru hdmi except for use with immediate review of a shot, so .... basically happy.
 
Back
Top