DSMC Release v7.0.0

[Stefan Kraus]

Same thing with me. All 3 above.

Got the same on the Epic-W. minus the screen tear

Also one change I noticed the shared display output on side.
I used the port to plug in the Red monitor to check exposure/etc. when mounted on gimbal/drone and
when I unplugged I could have the hdmi to feed out a signal with it's own settings (no overlay etc.)
That's not possible anymore, the top display port has to be used.

 

[Mike Smith]

I can't find anything about any $100 upgrade, so I don't know what that's about. However, if the solution to the problem is a $100 paid upgrade that's just bullshit. Red blames WC and WC needs to us to pay for an upgrade. Why don't Red and WC just honor the third party collaboration that Red marketed so heavily before? I do not deal in workarounds, this is a broken deal. If I would have known that Red and WC after some time wouldn't collaborate I would have found another solution. You mean to say that when Red earlier said that they were in talks with WC, that was about getting WC to get out a $100 upgrade?

Can someone tell me why Red just can't implement support for WC's battery plate code into their firmware? What's the deal here? I understand that it's up to WC to provide it, but whenever they do Red would surely implement that into the next firmware? I'm no coder, but I have a hard time understanding what the problem actually is here?

Hi Christoffer,

See post #44 of this thread.

I can understand you being a bit annoyed at having to spend again on a product you already have, but it seems from post #44 that WC reverse engineered Red's protocols back when the two were not in a third party product agreement. It seems Red has now released communication protocols to WC and other third party product manufacturers as they have started to invite them to make compatible third party products. Pretty generous in my opinion. That these official protocols don't mesh up with WC's previous reverse engineering efforts on which they based previous products is not Red's fault or problem. Red had no control over WC's previous efforts. The way I understand it is WC had a go at making accessories based on their observations of Red's unreleased protocol at that time. A good effort and it sold their products. Well done WC. Red has now formalized an official third party protocol that WC and others can follow and can submit their offerings for Red to approve. That previous WC reverse-engineering no longer works with this new official protocol is something WC is responsible to sort out. It sounds like they are offering a $100 fix for your particular product as I understand it.

No-one's at fault here. Least of all Red. WC did some innovative work and made some unofficial (from Red's point of view) Red accessories that worked very well. Now they're part of the third party program and must use official protocols. So from now on, their Red accessories are guaranteed to be compatible. Your product (apparently) came before this agreement.

 

[Joachim Hoge]

I have the diagonal screen tear, but I had that a lot on the previous build as well. No other problem so far, but I just updated and have only used it on one small production

 

[Christoffer Glans]

Hi Christoffer,

See post #44 of this thread.

I can understand you being a bit annoyed at having to spend again on a product you already have, but it seems from post #44 that WC reverse engineered Red's protocols back when the two were not in a third party product agreement. It seems Red has now released communication protocols to WC and other third party product manufacturers as they have started to invite them to make compatible third party products. Pretty generous in my opinion. That these official protocols don't mesh up with WC's previous reverse engineering efforts on which they based previous products is not Red's fault or problem. Red had no control over WC's previous efforts. The way I understand it is WC had a go at making accessories based on their observations of Red's unreleased protocol at that time. A good effort and it sold their products. Well done WC. Red has now formalized an official third party protocol that WC and others can follow and can submit their offerings for Red to approve. That previous WC reverse-engineering no longer works with this new official protocol is something WC is responsible to sort out. It sounds like they are offering a $100 fix for your particular product as I understand it.

No-one's at fault here. Least of all Red. WC did some innovative work and made some unofficial (from Red's point of view) Red accessories that worked very well. Now they're part of the third party program and must use official protocols. So from now on, their Red accessories are guaranteed to be compatible. Your product (apparently) came before this agreement.

I'm failing to see how a $100 upgrade for something to work as intended upon purchase is generous at all.

Also, the WC V-Lock Cable-less blueshape came out after the third party collaboration agreement from Red, no?

 

[Mike Smith]

I'm failing to see how a $100 upgrade for something to work as intended upon purchase is generous at all.

I was talking about Red being generous. They made their intellectual property available to third parties so that the latter could make money selling Red-approved accessories, presumably for the greater good of Red accessory infrastructure.

Also, the WC V-Lock Cable-less blueshape came out after the third party collaboration agreement from Red, no?

If so, that would be WC's culpability. If they knew ahead of time what it should be but didn't do it and still expect you to pay $100, then that's their issue. That's why I would doubt that being the case. But you should ask WC about it. I personally don't think anyone's being dishonest here. Sometimes you just have to upgrade.

 

[Brendan H. Banks]

Hello all to the WC Mount Crew! Last night I wrote a nice e-mail out to info@woodencamera.com and received an e-mail back fairly early this morning. I'm going to share that below, as I feel like this is the proper space and with consideration of informing customers so they know how to plan ahead. I'm posting this with hopes that it will not disrupt any lines between RED and WC within the third-party program, but merely because there are a lot of people asking questions with absolutely no concrete answers... So, I did what Brent mentioned and asked them directly.



That's all I've got. Hopefully it will calm the fire instead of start a new one. I think a $100 board replacement is okay with me (especially considering how much use I've gotten out of my current one), but I'm also a little bummed that RED couldn't keep that bit of code in-tact until that board offering was made by the end of the year... Granted I know that every little bit of old code cutting counts in regards to adding new features to a camera's boards.

So...

RED has stated in this and other threads (http://www.reduser.net/forum/showthread.php?161594-DSMC2-RELEASE-CANDIDATE-BUILD-V7-0-0RC4/page2):
"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."
"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."
"As has been said in other threads, RED is actively working with WC as a member of our Third-Party Hardware Development Program. As to if/when their product will be compatible with our current protocols, that is up for them to state, not us, as it is a WC product we are speaking of here."

Then WC says:
"Start a support ticket at RED.com using the link below to ask for them to enable communication for the Cable-less Battery Module. This would be the quickest and easiest solution as it would only require them to add back a few lines of code to their firmware."

Hmm.
My conclusion: WC is subtly suggesting that the only real solution will be to buy their new PCB (option 2) whenever that is ready.

P.S.: Thank you Anthony for this info!

I don't have much more to say on this topic aside from what I have posted previously (yesterday as well as prior to that). But let me be VERY clear that sending a support ticket to RED will be a complete waste of your time and our time.

But I will reiterate - this is very, very simple. RED improved our communication protocols, among other things in this firmware version. Any third party product who may have reverse engineered our prior protocols would not be supported. The onus would be on that third party to join our Third Party Hardware Development Program to ensure compatibility moving forward. As I have stated, you can see on our Approved Third Party Product page that WC and RED are engaged. Also remember, Third Party RED approval is on a product-by-product basis, not blanket approval on every product a company makes.

It is very frustrating to read "it would only require them to add back a few lines of code to their firmware". As you can imagine, in this IPP2 version of firmware, there is a shit ton of code behind the scenes. Would you guys be okay if we crippled some of that to go back to our prior gen protocols to support a product that is not a RED approved product? That is very myopic.

You cannot praise us for innovating, yet there being shock and dismay when a third-party product RED never approved (ie, including providing our communication protocols) loses functionality.



I don't know how many ways/times I can say it is very clear RED and WC are engaged. This is THEIR product, not RED's. If you want a product supported by RED, buy ours or an approved third party product.

I am going to stop now before I say something I will regret later.

I can't find anything about any $100 upgrade, so I don't know what that's about. However, if the solution to the problem is a $100 paid upgrade that's just bullshit. Red blames WC and WC needs to us to pay for an upgrade. Why don't Red and WC just honor the third party collaboration that Red marketed so heavily before? I do not deal in workarounds, this is a broken deal. If I would have known that Red and WC after some time wouldn't collaborate I would have found another solution. You mean to say that when Red earlier said that they were in talks with WC, that was about getting WC to get out a $100 upgrade?

Can someone tell me why Red just can't implement support for WC's battery plate code into their firmware? What's the deal here? I understand that it's up to WC to provide it, but whenever they do Red would surely implement that into the next firmware? I'm no coder, but I have a hard time understanding what the problem actually is here?

From the earlier pages, it's super documented back there. I know this is a long thread so I included some of the important info.

 

[Audy Erel]

Release Build 7.0.1 is already here!

https://www.red.com/downloads?category=Firmware&release=final

Nice improvement in record start response time (from ~2 seconds to just a second fast! | Scarlet-W), Thanks RED!

 

[Donald MJ Anderson]

Fixed Record Start/Stop sounds enable :smile5:

 

[Aaron Lochert]

I couldn't get the 7.0.1 firmware to install off a UDF formatted card.

Had to switch back to fat32 to get it to load in. Just throwing this out there for anyone who might run into problems.

 

[Ryan Sauve]

After the latest firmware update (from 7.0.0 yo 7.0.1), my Epic-W startup time went from about 53 seconds to 48 seconds. Sooooo is this going to be normal and expected boot time for the camera going forward?

 

[Homer Dulu]

"Fixed Apple ProRes elevated black levels in IPP2 mode" YUS!!

"Fixed intermittent high fan speed during camera shutdown or entering playback" YUSS x2! It always freaks people out when the fans spin up like crazy on playback.

"Added support for future RED accessories" Ooohh looking forward to seeing what these are...

I wonder if they fixed the Adaptive Preview Quiet Record bug when it was quiet during standby and fans operating during record.

 

[Caleb Ware]

Since I updated my SW my boot time went up heaps and the Initialising boot screen often flicks up twice as well as the screen regularly calibrating/freezing and Ive noticed banding in 2k prores HQ. Anyone else had similar issues? Hoping the new firmware might help fix this...

 

[Brad Harris]

I couldn't get the 7.0.1 firmware to install off a UDF formatted card.

Had to switch back to fat32 to get it to load in. Just throwing this out there for anyone who might run into problems.

Aaron,

The Support team just tested this in-house and were not able to replicate.

If you're still experiencing this issue, please submit a request on support.red.com and we'll help troubleshoot this with you.

Thanks.

 

[Nik Lachajczak]

Is this an UPgrade??!
So.. Ive had this version 7.0 installed on WEAPON MG 6k for about a month. Theres a lot of mixed reportage on how good this version is. Most people seem happy with it .. some decidedly not. And a lot of inconsistency with the actual bugs. Ive been slowly moving towards the dissatisfied camp unfortunately. Its just so buggy. But in weird and unpredictable ways:
Ive experienced:
-Incompatibility with formerly compatible lenses (the most recent being on a sigma 150-500 that first caused an unpredictable shutdown and then a refusal to record on any of the 3 rec buttons.?? And the touch screen stopped working. wtf? it was very bad timing as im currently out in the desert shooting wildlife. Had a great hazy long lens of emus all set to go..then WTF (again!) this remains unresolved. Im not really keen on rolling back to 6.4 as that was really! buggy. And i cant go further back (which is a bummer cause my camera was rocking with earlier versions
-The boot time is inexorable. Why is it soooo long? Ive timed it a few times and its not even consistent.. but its always 30 secs + which is a lifetime
-Occasionally modules go offline esp the DSMC2 side handle
-The fan control is erratic to say the least. Adaptive was always my go to..but thats all over the shop with speeds and timing
-i can induce vertical lines onto my 9" touch if i go to play back ..which wont go away unless i power down again..
also .. I havent seen any sign of audio recording with variable frame rates. which i was keen on.

There may be other things that ive forgotten about.. but just these few issues are time consuming and frustrating in the field.. maybe this Version is optimised for heliums & 8 k etc??
A lot of extra stuff in there..i realise.. but most of it i will never use..and funny little thingss...like - I use the timelapse function all the time .. and for some reason the engineers saw fit to add a little graphic as the interval passes. It looks cheap & nasty and is totally unnecessary.. and i sort of wonder if theres more stuff buried in there that was fine just the way it was.. just taking up that little bit more processing power. I would def be in favour of a 7. whateva that was a stripped back or at least fully functioning across the whole RED camera range.. so here i wait in a very hot cabin waiting for the heat to drop so i can head back into the desert.. with my buggy camera.. ok . melted brain rant over and out!

 

[Oron Cohen]

referring to posts #161-164 and also to my own post from earlier, Does anyone knows/checked if the new 7.0.1 let you choose to use the histogram for the LUT/Gamma curve you are on and not only showing the histogram for Log3G10?
Without this feature I have a hard time to convince myself to upgrade.

I mean if I put REDgamma4 I want to see the histogram for this gamma, is that possible?

 

[Jon Carr]

Anyone else getting the record proxy error While shooting UDF? Mostly getting it with 2k ProRes LT, it stops for a while when I use a less compression ProRes.

 

[Charles Bergquist]

I can confirm that the WC plate no longer transmits data. Went into their store and was told it will be a $100.00 upgrade and I’m assuming downtime for the plate. They should be doing it for free. I really like the low-mode about the plate but I’ll definitely be switching to a Red Battery plate after this move by Wooden Camera. They should just update any customer that bought the reverse engineered plates.

 

[Bob Gundu]

I can confirm that the WC plate no longer transmits data. Went into their store and was told it will be a $100.00 upgrade and I’m assuming downtime for the plate. They should be doing it for free. I really like the low-mode about the plate but I’ll definitely be switching to a Red Battery plate after this move by Wooden Camera. They should just update any customer that bought the reverse engineered plates.

Just make sure your battery works ok with the RED one.

 

[Chris McKechnie]

View attachment 105384 Anyone else getting the record proxy error While shooting UDF? Mostly getting it with 2k ProRes LT, it stops for a while when I use a less compression ProRes.

ALL THE TIME using the same settings.

 

[Kevin D'Haeze]

View attachment 105384 Anyone else getting the record proxy error While shooting UDF? Mostly getting it with 2k ProRes LT, it stops for a while when I use a less compression ProRes.

Yes, I have had that same issue.