Welcome to our community

Be a part of something great, join today!

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

DSMC Release v7.0.0

Azzie Scott said:
I tried to play back some clips in cam and the screen went black for about 10 secs and the fans ran at high speed just like it does when your upgrading the firmware. Then the playback screen would come back and I was able to review clips again. This happen to me three times during a shoot. My heart was racing. Hopefully this is something they can look into as well.
Click to expand...


Happened to me as well. Hopefully they'll fix it for the next update.
 
Amidst the issues some of you are having (which I sincerely do hope gets resolve for you guys soon), I want to go on record as having no issues with 7.0.0 so far. The internet tends to be a place where the negatives reviews are over-represented because the majority of the people with positive experiences don't post about it.
 
Aaron Lochert said:
Amidst the issues some of you are having (which I sincerely do hope gets resolve for you guys soon), I want to go on record as having no issues with 7.0.0 so far. The internet tends to be a place where the negatives reviews are over-represented because the majority of the people with positive experiences don't post about it.
Click to expand...

I also not having any issues with the latest firmware 7.0 on my Scarlet-W. It's been pretty solid! Positive experiences +1 :)
 
Tom Gleeson said:
Here is a video showing the jumping black levels in the DSMC2 EVF when switched between Legacy and IPP2 Pipelines. It starts in Legacy then swaps to IPP2
https://vimeo.com/237837256
Click to expand...

While I don’t have v7 installed yet, this is the exact shift I see when using LUTs in camera. Seems like the LUT takes over the whole touch screen image / gets a tad bit washed out.
 
Tom Gleeson said:
Here is a video showing the jumping black levels in the DSMC2 EVF when switched between Legacy and IPP2 Pipelines. It starts in Legacy then swaps to IPP2
https://vimeo.com/237837256
Click to expand...

Glad I'm not the only one seeing this... I noticed exactly the same thing. Wondering if Red techs are aware of the issue or not ?

Otherwise build 7.0 has been pretty solid so far and IPP2 is really a big step forward. :)
 
Homer Dulu said:
Michael from Wooden Camera reached out to me, and hopefully we can get my issue resolved. Didn't mean to slag off WC's stuff, the other stuff I've bought from them have been awesome! :)
Click to expand...

Update: Stopped by Wooden Camera in Burbank yesterday with the top plate, Michael took all of 10 minutes to resolve my problem. Really awesome customer service. Thanks Michael!
 
BrendanLeahy said:
What was the fix?
Click to expand...

Basically no image would show up on the monitor with the top plate installed, either direct mount or using a cable. I think there was an issue with the POGO passthru, but we didn't see any bent pins so it most likely was something internal. Michael replaced the module and voila, it started working again! Apparently it's not a common problem, so it's probably something specific to my own plate.
 
Did the update on raven, here to report that everything appears to look good. However the "Auto calibration" message popping up every now and then its bit annoying. Yes I did a sensor black shade calibration and everything, the message it still shows up. Anyone knows how to turn that off? or is this a bug or something?
 
Edry Hilario said:
Did the update on raven, here to report that everything appears to look good. However the "Auto calibration" message popping up every now and then its bit annoying. Yes I did a sensor black shade calibration and everything, the message it still shows up. Anyone knows how to turn that off? or is this a bug or something?
Click to expand...

The auto calibration will show up as your camera heats up and down as well I believe, especially anytime you switch frame rates. Sometimes it takes about 30 seconds to happen, so you may not see it until after a shot is ended or in the middle of monitoring while not recording. I do not believe it’s a bug, just more a cautionary notice to let people know what’s going on.

The camera used to look like it was freezing while autocalibrating before - so they added it to stop those customer support calls.
 
Anthony Berenato Jr said:
The auto calibration will show up as your camera heats up and down as well I believe, especially anytime you switch frame rates. Sometimes it takes about 30 seconds to happen, so you may not see it until after a shot is ended or in the middle of monitoring while not recording. I do not believe it’s a bug, just more a cautionary notice to let people know what’s going on.

The camera used to look like it was freezing while autocalibrating before - so they added it to stop those customer support calls.
Click to expand...

That makes a lot of sense! I submitted a ticked to red and they just got back to me with a similar message, I just wanted to double check and make sure this wasn't a bug or something. I was also told that if you do a manual calibration I'd not see this message. Good to know! Thanks a lot!
 
Edry Hilario said:
Did the update on raven, here to report that everything appears to look good. However the "Auto calibration" message popping up every now and then its bit annoying. Yes I did a sensor black shade calibration and everything, the message it still shows up. Anyone knows how to turn that off? or is this a bug or something?
Click to expand...

I, for one, appreciate this feature... For some time I thought perhaps my monitor was malfunctioning when things paused for a moment. I'd much rather know that the RED is "thinking" than to wonder if there was a hardware issue. Good addition.
 
I've been playing around with the new firmware with my scarlet-w and there is some nice stuff. One thing I am wondering is, that no matter what gamma, colour space I select the histogram stays the exact same. So is it only showing me the raw histogram now and not my selected gamma colour histogram anymore? Just trying to figure what it is showing me as before raw would show a squished histogram and dragon colour and gamma 4 would show more of a rec 709 histogram.

Also, before I was using some luts for viewing that I would add onto red raw or dragon colour, gamma look. Now I can choose to have a lut on my monitor but it will only show with red raw below so my luts for the gamma curves don't work. As well the screen goes very dark with my raw luts, so something is going on there and I'm not sure what.
 
Brandon Kelly said:
I've been playing around with the new firmware and there is some nice stuff. One thing I am wondering is, that no matter what gamma, colour space I select the histogram stays the exact same.
Click to expand...

The histogram is showing you the Log3G10 data (scaled so that black is at the left and sensor clip at the far right)

Graeme
 
Graeme Nattress said:
The histogram is showing you the Log3G10 data (scaled so that black is at the left and sensor clip at the far right)

Graeme
Click to expand...

Great thanks for that info. I am so used to the old legacy Red Colour/gamma that it will take some testing to get used to the new ways I suppose. So even on my Scarlet-W in image I should set it to log3g10 and then just select the monitor look I want for on camera? If I set it to Dragon colour/gamma 4 in the image menu the histogram will still show 3g10?

That is probably why in Monitor, when i choose to show a LUT that is made for RED raw it looks dark and flat, as it is basing it off of log3g10 for viewing on my monitor with scarlet W?
 
Last edited:
Tom Gleeson said:
Anthony,

In my workflow generally the proxies are never colour corrected. The proxies use is finished once the edit is locked and then we move to the R3D files. "Protecting" the blacks on the proxies is a mostly pointless exercise. If you were planning on finishing with the pro res files I suspect you would never bake in the look anyway.

I have started a support ticket with Red so will be interested if its considered a bug or a feature. As you correctly point out a possible "fix" is adjusting the curves to sit black back on to zero.

Even if a code value of 64 is the technically correct placement for black its the wrong place for a burnt in Proxy. I need my proxies to look good not washed out.
Click to expand...

Let me know what happens on this front. I'm assuming that it has something to do with the BT1886 Gamma Curve and matching the ACES standards, which I believe is near 2.4. I don't have much a need for in-camera proxies, but I'm curious as to what the recommended thought is.
 
Brandon Kelly said:
Great thanks for that info. I am so used to the old legacy Red Colour/gamma that it will take some testing to get used to the new ways I suppose. So even on my Scarlet-W in image I should set it to log3g10 and then just select the monitor look I want for on camera? If I set it to Dragon colour/gamma 4 in the image menu the histogram will still show 3g10?

That is probably why in Monitor, when i choose to show a LUT that is made for RED raw it looks dark and flat, as it is basing it off of log3g10 for viewing on my monitor with scarlet W?
Click to expand...

The camera has a degree of "per monitor" output capabilities, so if you do the primary development to a log curve like Log3G10 you can have any kind of "gamma" or "log" output on the different monitors.

Graeme
 
Graeme Nattress said:
The histogram is showing you the Log3G10 data (scaled so that black is at the left and sensor clip at the far right)

Graeme
Click to expand...

You mean you changed the histogram to show what the sensor sees, not according to color spaces and gammas? So we have more security in getting a proper exposed sensor each time?
 
You must log in or register to reply here.
Back
Top