Welcome to our community

Be a part of something great, join today!

Log in
  • 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 :)

DSMC2 RELEASE CANDIDATE BUILD V7.0.0RC4

Jarred Land

Jarred Land

Fire Chief
Staff member
Joined
Dec 27, 2006
Messages
10,644
Reaction score
33
Points
10
Enjoy.

WEAPON FIRMWARE (6K CF, 8K S35, 8K VV, 8K VV ANA) | https://www.red.com/downloads/5632ad24cc11fa24c10009fd
WEAPON FIRMWARE (MAGNESIUM ONLY) | https://www.red.com/downloads/57112c00104ec8361a001ab9
RED EPIC-W FIRMWARE | https://www.red.com/downloads/58deba68cc11fa6f4c000115
SCARLET-W FIRMWARE | https://www.red.com/downloads/57112c21104ec8361d001bae
RED RAVEN FIRMWARE | https://www.red.com/downloads/57112c46104ec8361d001bb4



SIGNIFICANT CHANGES SINCE PREVIOUS BUILD v7.0.0rc3
* Fixed camera freeze requesting extended clip info without media attached
* Fixed focus of top bar items when using keys
* Fixed RED Touch 7" LCD monitor curve not always applied on startup
* Fixed record error with R3D+QT and 4 channel audio
* Fixed stale 'Current Calibration Map' in Calibration dialog
* Updated IPP2 calculations to improve overall image brightness match between Legacy and IPP2 modes
 
Dan and Jason, that product is not an approved RED Third Party Product so we would not be able to support prior-version RED command protocols. WC would have to work with RED to make any necessary hard and/or firmware updates to their product, and then have it approved within the Third Party Product Development Program.

I, obviously, cannot comment if that discussion is happening between RED and WC at this time, burt note that WC does have an approved product, so rest assured there is collaboration between us and them within the Third Party Product Development Program.
 
Dan, read my second paragraph again. We are indeed working with them. I can only comment in the broader sense - with evidence being there is an approved WC product. I cannot speak to status of individual products. I know Mark would have to say the same party line as me.
 
??? Battery percentage was working in prior release builds, but not any longer??? For WC cableless plates, whats the problem now...
 
Brent@RED said:
Dan, read my second paragraph again. We are indeed working with them. I can only comment in the broader sense - with evidence being there is an approved WC product. I cannot speak to status of individual products. I know Mark would have to say the same party line as me.
Click to expand...

Does their D-Box have Red's approval or is it only the R/S adapter for their top plate at this point?
 
Mestizo, I already answered that: "that product is not an approved RED Third Party Product so we would not be able to support prior-version RED command protocols."

Jason J, in my original post is a link to the Approved Products page. I suggest you use that to reference what product is RED approved versus products design to be compatible with RED, yet not certified by RED.
 
Brent@RED said:
Mestizo, I already answered that: "that product is not an approved RED Third Party Product so we would not be able to support prior-version RED command protocols."

Jason J, in my original post is a link to the Approved Products page. I suggest you use that to reference what product is RED approved versus products design to be compatible with RED, yet not certified by RED.
Click to expand...
So if I understand you the code has been changed not to have battery info going forward for WC cableless plates, completely
 
Mestizo, this has nothing to do with WC on our end. RED updated communication protocols, period. If those changes were not accounted for by ANY third-party manufacturer, then the data would not be assimilated.

Kenneth, Jarred comments on future product, not me. But I can say this is not far in the future at all.
 
Brent@RED said:
Mestizo, I already answered that: "that product is not an approved RED Third Party Product so we would not be able to support prior-version RED command protocols."

Jason J, in my original post is a link to the Approved Products page. I suggest you use that to reference what product is RED approved versus products design to be compatible with RED, yet not certified by RED.
Click to expand...

Thanks!
 
Brent@RED said:
Mestizo, this has nothing to do with WC on our end. RED updated communication protocols, period. If those changes were not accounted for by ANY third-party manufacturer, then the data would not be assimilated.

Kenneth, Jarred comments on future product, not me. But I can say this is not far in the future at all.
Click to expand...

Just to confirm, us who have the WC Cable-Less V-Lock (BlueShape) will loose the ability to see battery percentage if we update to firmware 7.0.0? And WC need to feed you the necessary updates for their mount in order for it to be included in upcoming firmware? Is this something we can tell WC to do in order to speed things up on their end?
 
Christoffer Glans said:
Just to confirm, us who have the WC Cable-Less V-Lock (BlueShape) will loose the ability to see battery percentage if we update to firmware 7.0.0? And WC need to feed you the necessary updates for their mount in order for it to be included in upcoming firmware? Is this something we can tell WC to do in order to speed things up on their end?
Click to expand...

As RED, I cannot speak to what third party modules will or won't work with our system. That is a "them" question, not a "RED" question. However, if they have been put through the Third Party Program process with RED and are approved, they will be supported as long as the third-party stays compliant.

However, from comments here, that seems to be the case with this product (Ie, updates needed to be compatible).

If above is true, then yes.

No, as I have said, RED and WC are already in communication, in general.
 
Brent@RED said:
As RED, I cannot speak to what third party modules will or won't work with our system. That is a "them" question, not a "RED" question. However, if they have been put through the Third Party Program process with RED and are approved, they will be supported as long as the third-party stays compliant.

However, from comments here, that seems to be the case with this product (Ie, updates needed to be compatible).

If above is true, then yes.

No, as I have said, RED and WC are already in communication, in general.
Click to expand...

maybe it's just me, but all this sounds very confusing and far from reassuring.
 
Brent@RED said:
As RED, I cannot speak to what third party modules will or won't work with our system. That is a "them" question, not a "RED" question. However, if they have been put through the Third Party Program process with RED and are approved, they will be supported as long as the third-party stays compliant.

However, from comments here, that seems to be the case with this product (Ie, updates needed to be compatible).

If above is true, then yes.

No, as I have said, RED and WC are already in communication, in general.
Click to expand...

I understand you can't comment openly on business-related things like this. I just hope that you bring up the Cable-Less V-lock issues reported by some here, so that WC could collaborate with you on that one.
For me personally it's the only thing I have that's not Red, only because it's a lower mounted V-lock to enable use with my Red Bricks, so I unfortunetely don't have a choice to use Reds own V-lock to make the rest of my gear setup work properly.
Meaning things like this stops me from getting firmware updates. Since the WC V-Lock is the only one that enables Red Bricks on DMSC2 together with the DMSC2 top handle it's in my opinion kind of a priority for third party gear support, since it's the only one of it's kind.
 
You must log in or register to reply here.
Back
Top