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 Camera Firmware release 5.1.55 and 5.2.21 beta

So I did my trusty torture test to see if what ever the change was, was it actually noticeable?

BOOM!!!!!! MOST CERTAINLY IS !!!

Toia your tweaks freaked me out, but thankfully when I looked carefully at the footage that splotchiness appears to just be from the JPEG compression.

I'll be interested though to see this on a "hard situation" like a green chroma wall. Do we lose edge chroma detail? If it's better for chroma keying then I see no reason to ever turn it off. If it's like chroma blur then I definitely need an on/off switch.
 
I don't see the on/off button as a problem. Pretty simple step it seems to me. Puts the decision in my hands in case it affects my footage adversely.

But just to be clear, can I debayer my footage with DEB on, save it and then import it into Premiere for instance as DEBbed footage?
 
I don't see the on/off button as a problem. Pretty simple step it seems to me. Puts the decision in my hands in case it affects my footage adversely.

But just to be clear, can I debayer my footage with DEB on, save it and then import it into Premiere for instance as DEBbed footage?


You can export it to any format you want with D.E.B. though the likely goal will be to implement this into the SDK so the Adobe Red Importer has a tick box for it so the metadata passes through for people who enjoy the .R3D and Adobe workflow.

You know... Like me :)
 
You can export it to any format you want with D.E.B. though the likely goal will be to implement this into the SDK so the Adobe Red Importer has a tick box for it so the metadata passes through for people who enjoy the .R3D and Adobe workflow.

You know... Like me :)
Heh, heh... Yeah, me too Phil. Nice to know there is a work-a-round until the SDK goes out and is implemented.
 
Glad to see the fix is getting close.

I don't think this is really implemented until it can be applied though the post pipeline, especially Resolve, which is the dominant software for both dalies and final grade. I don't know if many productions are going to go though the hassle of running everything though RedCine-X before loading it into Resolve.
 
Glad to see the fix is getting close.

I don't think this is really implemented until it can be applied though the post pipeline, especially Resolve, which is the dominant software for both dalies and final grade. I don't know if many productions are going to go though the hassle of running everything though RedCine-X before loading it into Resolve.

I agree. Especially, making it into the Red Importer into Premiere will be a big one for people too. It's a good start but it'll be 2-4 months before we see this in Adobe and Resolve, realistically speaking. I didn't get a Dragon to transcode out all my R3D files.

Any updates on the Magenta line issue? Anyone notice a difference on that?
 
So... Timecode Locking?

So... Timecode Locking?

Does this version recognize incoming timecode at 23.976 from lock boxes yet? This problem is a deal breaker in my market.
 
I don't see Dragon color / RG4 available in the release version in-camera. Go beta?
 
So "D.E.B." is just a color noise reduction algorithm? Have you guys considered talking Adobe into reworking ACR to do motion and R3D so you don't have to reinvent the wheel on all this stuff?

I believe this is more of a "new way" to debayer rather than a full blown noise reduction technique, hence it's an update really to the Color Science itself. I could be crazy and/or wrong though, but based on what I'm seeing I think it's more along those lines.

I would love for ACR to work with R3Ds, but it's far from optimized for motion work and is a very slow pipeline. Though I do it from time to time on uncompressed TIFs.



Does this version recognize incoming timecode at 23.976 from lock boxes yet? This problem is a deal breaker in my market.


I own and use a Zaxcom MAXX recorder. I am able to sync (green TC) a 23.98 project in camera with 29.97 set in my Zaxcom device and auto sync later successfully. It's good to inform your editor to work in "full seconds" just in case. Until there's an official fix from both parties there's this fix/hack/achievement unlocked.
 
Great that the Red team was able to get this into RCX, really a great achievement.…….But as I see it, until the DEB is implemented into the camera firmware/calibration this is just a temporary work-around. There's just to many variables when it's not the image capture device "driving the bus"…….Such a shame, there's just so many pluses to shooting with the Dragon, but it's looking increasingly likely we won't be seeing the full power of Dragon for a number of months.
 
Any updates on the Magenta line issue? Anyone notice a difference on that?


I`m surprised at how little info came with this release.

I guess Graeme/Red were burning the candle at both ends to get this fix out there but the guy writing the manual is burning his candle at one end and still has to hand in is assignment.
 
It has been stated in many earlier post they this fix is still in its infancy and will obviously be refined as time goes on.
I'm very pleased to see Red has in relative short terms fixed this issue and will in the future keep refining this problem along with continuing to upgrade our cameras.
thank you Red and a shout out to Phil for giving us the short version and long of what this means for us.
 
Glad to see the fix is getting close.

I don't think this is really implemented until it can be applied though the post pipeline, especially Resolve, which is the dominant software for both dalies and final grade. I don't know if many productions are going to go though the hassle of running everything though RedCine-X before loading it into Resolve.

Agree! Let's get it into SDK ASAP,

M
 
YES! Been awaiting this one! Thank you.
 
Any updates on the Magenta line issue? Anyone notice a difference on that?

It doesn't sound like this was addressed. The thread about this issue got shut down but the magenta line issue is more pronounced on Dragon than MX. Anyone know if this issue was worked on with this firmware?
 
It doesn't sound like this was addressed. The thread about this issue got shut down but the magenta line issue is more pronounced on Dragon than MX. Anyone know if this issue was worked on with this firmware?

Yeah it did get shut down, and I don't know the reason why that was. Would be great to have someone on new firmware test it vs an Epic MX. It's definitely something that people are going to start bumping into on projects.
 
I have been doing a very similar fix by using a Luma vs Saturation node in Resolve and taking all the chroma out of the deep blacks. This removes all the colour out of the noise and makes for nice crisp blacks.
 
Back
Top