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

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.

It would be great if in one of the future builds this is somehow made easier to set up on one of the buttons.
Cycling between only two modes (menus and clean - bypassing all the other) is great.
Thanks!

George



--
 
Update on the issues with the lens dialog I reported in posts 184 and 207 of this thread:

The real culprit appears to be invoking and then using the scroll wheel on either REDMote or SH to change the aperture value when aperture value is displayed in one of the boxes on the REDmote. This may well be why Patrick (post 191) was unable to reproduce my problem on his Scarlet. I found just by experimenting that when the REDmote (docked, in this case) is displaying aperture value, both scroll wheels essentially stop functioning to move the aperture in either direction. Changing focus modes (AF or MF) has no effect on this whatsoever. But when you change the REDmote to a page that does NOT include aperture display, the problem magically disappears, and the scroll wheels on both REDmote and SH resume normal continuous adjustment of iris. The problem appears limited to aperture in the sense that the scroll wheels appear to behave correctly and consistently to change focus distance on the lens dialog menu whether or not the REDMote is displaying focus distance.

The problem is most evident with the REDmote docked. There seemed to be very sluggish/stubborn response on aperture change with the REDmote in wireless mode and displaying aperture value. I would consider it unusable but it is slightly responsive in wireless mode whereas it's totally unresponsive when docked. As with the RM docked, wireless control of aperture works very well when the REDmote is NOT displaying aperture value. And, of course, when the REDmote is off entirely, none of these problems surface.

I hope this helps the RED team trace the source of this bug as I would really like to use my REDmote to remotely control iris via the scroll wheel after invoking the lens dialog with a custom key map and preset. The practicality of this approach is much hampered if I can't have the REDmote displaying aperture value while I'm doing it.

Oh, and while doing this additional testing, my camera spontaneously shut off AGAIN. This is about the 4th or 5th time that's happened in the course of this custom key mapping stuff. I'll reiterate my willingness to send a log file if RED team would like to try to figure out why this is happening. I'm thinking it's build related, but if it seems otherwise to RED techs reading this, please let me know so I can open a support ticket.
 
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

I could not load presets I saved with 3.2.16, but the presets from 3.2.13 were accepted and are working fine.
 
Pretty excited about this new build, loads of interesting features. Look-around, simultaneous HDMI-HDSDI, Audio playback...

I just installed it, seems to be working fine except for one bug : it happened a few times after changing resolution on the touchscreen, the touchscreen became unresponsive but the camera kept working (buttons on the handle worked fine). Unplugging the monitor didn't help. Restarting the camera helped sometimes but more than once I had to restart the camera a few times before it fixed the bug. Stopping the camera the hard way by removing the power cord seemed to be more efficient, but I don't like doing that...
Re-installing the firmware didn't help neither. Anyone else seen this issue ? Is that a known bug or should I submit a log file ?
 
Had a quick four hour shoot this morning with the new beta firmware and didn't have any problems that would have affected the shoot. And audio playback was much appreciated as there was no sound guy on the shoot.

The only weird thing I did notice was that if I have my focus mode set to confirm:center, it seems to reset back to confirm:spot if I turn off the camera. I don't think it did that before.

Oh, and after I had opened the audio control menu by tapping on the audio meters on the touch screen I couldn't exit it by pressing the menu key on the side handle. I could exit the menu by tapping outside the menu on the touch screen. A reboot fixed it and haven't been able to reproduce it since.
 
Last edited:
Oh, and while doing this additional testing, my camera spontaneously shut off AGAIN. This is about the 4th or 5th time that's happened in the course of this custom key mapping stuff. I'll reiterate my willingness to send a log file if RED team would like to try to figure out why this is happening. I'm thinking it's build related, but if it seems otherwise to RED techs reading this, please let me know so I can open a support ticket.

Elizabeth -- please open a support ticket and send in your log. We should be able to track down the source of your spontaneous shut downs.
 
Last edited:
LOVE The update, had 2 1-day shoots and ran into an odd issue. about every 3rd or 4th time i would switch lenses and boot up it would not recognize the lens at all, and i could do nothing but hard shutdown. anyone seen this or know what to do? a simple reboot fixed it everytime, but i would get the message: "did not shutdown properly"... of course.
 
RED TEAM:

lcd stutter when camera is moving was succesfully fixed in 3.2.16 for me and now is again presented in 3.2.19 and 3.3.3. im in 25fps time base and only 30fps varispeed is smooth on lcd/evf.
please fix this.
 
Jared,

Are there more support for the Canon mount lenses in this build?
 
It would be great to have Presets work with the new Firmware versions.

Every time there is an upgrade (which is great), I have to spend an hour getting each camera back to the Presets that I use. It's frustrating...
 
It would be great to have Presets work with the new Firmware versions.

Every time there is an upgrade (which is great), I have to spend an hour getting each camera back to the Presets that I use. It's frustrating...

That shouldn't be the case. There are only a few settings with have been obsoleted and when you try to apply such a preset it will warn you. If you have preset files that don't work please open a support ticket and send the preset files in so we can fix any bugs in the BETA software.
 
I was simply asking about something that I had read over at DVXuser about the Scarlet now able to shoot 120fps @ 2k. Seems that it can't, and IMO that's a shame. Speaking from the gospel of RED, I don't see any need for a 1k function. That was my only point.

Net result, I currently rent the EPIC instead of buying the Scarlet.

Good day to you sir :]

That's good - you help give others an incentive to buy Epics, to rent to you and others who prefer to rent the higher feature set. Killing the Epic rental market is good for Red how?
 
Beta 3.3.3 is great. Just now getting a chance to sit down and explore it. Love the new Soft Keys on the touch screen edges. My excitement about this camera just does not go away.
 
Small suggestion for Keys, a toggle Guides option could be handy. We already have Show Dialogue: Guides but the addition of Toggle: Guides might be nice.

I realize the nature of most shoots renders quick toggle of aspect ratio guides irrelevant, but it'd be just another option in the infinitely open RED paradigm.

Diggin' every inch of progress!
 
Thanks for all the hard work RED Team. Seeing as this Build v3.3.3 includes many significant improvements, would it be possible to have it move on more quickly to become 'Release Build'? When might this happen? Any time soooooon???? Please : )
 
Anderson, this is something easily done with presets. Guides on/off, 16/9 to 1.85 or Blue guides to yellow...
Just create a guide setup you like, save a preset for that. Make the second one, save another preset.
Then see Trent's thread to understand how to make a button toggle between two different presets and voila !

Link : http://reduser.net/forum/showthread.php?p=1005810#post1005810
 
Completely wicked, thanks you Mikael for the heads up! You rock buddy, had not explored this manner of presets. Just another thing added to the list that this camera can do.
 
Ok, this presets UI needs work. Cannot argue that. Convoluted. How do I isolate particular frame guides to be applied as Presets. I've spent an hour on this and it's irking me big time.
 
That shouldn't be the case. There are only a few settings with have been obsoleted and when you try to apply such a preset it will warn you. If you have preset files that don't work please open a support ticket and send the preset files in so we can fix any bugs in the BETA software.

I have the same issue. Every time I upgrade I start from scratch and redo all my settings. I wish that newer firmware would recognize that I have presets built and just "add" the new features in. I don't feel the new firmware is aware (so to speak) of any presets and just takes the camera back to factory settings. It is a pain to setup everything again.

Of course I love new firmware upgrades so keep em comin!
 
Back
Top