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

DSMC Beta Build v6.2.3 - This is a good one.

What is the low latency feature?

Can you comment on the 7" touch color improvements?
 
This looks like a great Beta, I've never used Beta firmware for a production.

Whats the consensus on using Beta for production ?

Obviously we would test beforehand, but you can't test for everything.

Do we have an ETA For the release version?

thank you thank you thank you once again Red !
 
...

This stuff ins't easy. Today is one of those days where I just sit back in my chair, look up to the heavens and thank whoever is up there for giving RED the best fucking engineers on the planet.

i have to whole heartedly agree. Your guys are incredible. This is a big one. A huge thank you to the whole team for this build. You guys rock!

This little discussion about adding stuff and losing boot times makes me wonder (and I'm just thinking out loud, not knowing if something like this actually works, makes sense, or if it is possible).

With some computer operating systems you can activate and deactivate installed add-ons if you don't need them to gain back startup time (or for debugging purposes).
What I'm getting at is: having a check list of startup options where you can choose to load or leave out what you want to boot could be helpful in this regard. So if there are things that you don't need to load, you could check off a feature and this might improve startup time. For example: if you don't have the canon mount, why load the canon presets? Maybe even whole features could be loaded like plug ins without messing up the rest of the firmware. Like for example: HDR-X. Don't need it today? Check it off and don't load it.

A modular firmware so to speak. if you can already make it work for hardware, why not for software, too... ;)
As I said this just popped into my head. I know this would be a huge task, but you and your team would know if something like this makes sense or if it's bullshit... I don't. ;) Also.... Your engineers would probably love, love, love you for a feature like that because it means they will have enough work for years to come...(on top of their already busy schedule) ;) hehehe...
 
Yeah ... this build is really, truly freeking AWESOME.

Many, many thanks to all the folks working behind the scenes at RED. REALLY GREAT STUFF.

Keep drinking whatever you all are drinking.
 
This looks like a great Beta, I've never used Beta firmware for a production.
Whats the consensus on using Beta for production ?
Depends on your production and crew. ;)

What i can say in general about my beta-experience (and i have installed nearly every build) is, that they are mostly great builds and what i would call usable for production. I just install them and forget that it's a beta. There have been some builds which i wouldn't have installed on a important shoot, but they got fixed reql quick.

RED's betas have a higher quality than what others call release.

Obviously we would test beforehand, but you can't test for everything.
If you really want the beta and it's features for a shoot, then install, test it and keep a backup of the last working firmwares on your laptop.
 
i have to whole heartedly agree. Your guys are incredible. This is a big one. A huge thank you to the whole team for this build. You guys rock!
+1! RED's firmware department is outstanding. Beats even famous open-source-projects for other cameras and pushes some companies to step up in that area. Still, there is nobody else doing what RED is doing for us.

A modular firmware so to speak. if you can make it work for hardware... ;)
Thats an idea that makes a lot of sense, at least to us - without knowing how current firmwares work. But if there is really a way to modularize the whole thing and make "drivers" (for modules) only load on demand, even separate some features to "plugins", then it would be something worth to consider.

However, i somehow have a feeling this is already realized in some ways. For example, accessories like the SH and Mounts have their own firmware.
 
i have to whole heartedly agree. Your guys are incredible. This is a big one. A huge thank you to the whole team for this build. You guys rock!

This little discussion about adding stuff and losing boot times makes me wonder (and I'm just thinking out loud, not knowing if something like this actually works, makes sense, or if it is possible).

With some computer operating systems you can activate and deactivate installed add-ons if you don't need them to gain back startup time (or for debugging purposes).
Basically what I'm saying is: having a check list of startup options where you can choose to load or leave out what you want to boot could be helpful in this regard. So if there are things that you don't need to load, you could check off a feature and this might improve startup time. For example: if you don't have the canon mount, why load the canon presets? Maybe even whole features could be loaded like plug ins without messing up the rest of the firmware. Like for example: HDR-X. Don't need it today? Check it off and don't load it.
A modular firmware so to speak. if you can make it work for hardware... ;)
As I said this just popped into my head. I know this would be a huge task, but you and your team would know if something like this makes sense or if it's bullshit... I don't. :)

Also.... Your engineers would probably love, love, love you for a feature like that because it means they will have enough work for years to come...( On top) ;) hehehe...

+1 to this.
 
The boot time is great, 19-20sec on the scarlet D.
But I lost the stabilization on my Canon 28mm.
 
Depends on your production and crew. ;)

What i can say in general about my beta-experience (and i have installed nearly every build) is, that they are mostly great builds and what i would call usable for production. I just install them and forget that it's a beta. There have been some builds which i wouldn't have installed on a important shoot, but they got fixed reql quick.

RED's betas have a higher quality than what others call release.


If you really want the beta and it's features for a shoot, then install, test it and keep a backup of the last working firmwares on your laptop.



Great points ! Danke Maik.....
 
After installing, the touch monitor does not come on.... it appears the camera is on but no monitor. Installed the non beta firmware and same thing. No one else had this problem?
Have you tried to disconnect and reconnect the LCD-cable after bootup has finished? It almost fixes all LCD-hickups for me, especially those split-screen-moments.
 
My SCARLET DRAGON loved the update. My EPIC DRAGON, notsomuch. Both have 7" touch monitors attached. The EPIC DRAGON is rolling timecode in the lower right of the monitor. There's a dialog box telling me that it's upgrading attached peripherals, and will take several minutes to do so. One of the peripherals is a side handle. The other is a PRO IO module. The SCARLET DRAGON has none attached. It's been 10 minutes...no movement along what I presume is the progress bar at the bottom of the dialog box.
 
This looks like a great Beta, I've never used Beta firmware for a production.

Whats the consensus on using Beta for production ?

Obviously we would test beforehand, but you can't test for everything.

Do we have an ETA For the release version?

thank you thank you thank you once again Red !

When I've run a beta build on a production I put a release build on a 64GB RedMag (that I don't use) in case something goes wrong that way i'm covered.
 
Holy shit. I can finally flip my 5" touch image on epic dragon. Woohoo! I'm so happy that epic is still getting so much love in the new weapon world.
 
Back
Top