วีดีโอ

Non-Infringing Exposure Visualization System Design: 1. Avoid Gamma Correction Instead of using gamma correction data directly from the camera to modify the image signal, we could use luminance (Y channel) or the histogram of brightness values to analyze exposure. This gives a basic idea of exposure without relying on gamma correction specifically. Alternative Approach: Calculate luminance directly from the image signal using a simple formula like Y = 0.2126 * R + 0.7152 * G + 0.0722 * B (standard luminance formula). Based on luminance values, determine whether pixels are overexposed or underexposed. 2. Modify the Color Mapping Scheme Instead of mapping exposure stops to a predefined color spectrum (e.g., +6 stops = white, -6 stops = black), create a custom color visualization that doesn't directly mirror the patent's gradient. Example Modification: Bright regions (potentially overexposed) are colored with shades of red or orange. Dark regions (potentially underexposed) are colored with shades of blue or purple. Mid-range exposure values are left as grayscale or shown in natural colors (unaffected). Difference: By shifting the color mapping scheme away from the specific stop mapping outlined in the patent (yellow-red for highlights and green-blue for shadows), we avoid the patented method while still giving a meaningful exposure visualization. 3. Adjustable Threshold System Instead of mapping specific exposure stops, use a dynamic threshold system where the user can adjust the boundaries of what is considered overexposed or underexposed. User-Adjustable Thresholds: Allow the user to manually set the luminance values for "overexposure" and "underexposure" via sliders. This would give flexibility and prevent reliance on the stop-based system described in the patent. Example: A slider could define the range of luminance values that are considered overexposed (e.g., values above 220 are marked as overexposed) and underexposed (e.g., values below 40 are marked as underexposed). These regions are then color-coded according to the custom scheme. 4. Different Visual Cues Instead of using color coding for all regions, consider using other visual indicators: Blinking or flashing regions for extreme overexposure or underexposure. Transparency or opacity adjustments to mark overexposed/underexposed regions, making those areas more or less visible. Grain or texture overlays applied to overexposed or underexposed areas instead of using colors. 5. Overlay-based Visualization Rather than generating a separate exposure information signal, create an overlay on top of the existing image (non-destructive). This overlay could be a separate image layer with different color mappings or visual indicators. The patented method focuses on creating a distinct "exposure information signal," whereas your system could use real-time overlays that don't generate a separate image signal. 6. No Separate Image Signal The patented system creates a separate exposure information signal alongside the original image. To avoid this, your LUT or visualization system would work on the original image without generating a second signal. It simply adds overlays or applies color transformations to the same image, which is not what the patent describes.

a method patent is wrong, it happened with sony and red and they lost, the whole company to sony. also if you change the patent list of about 20% it s not valid anymore, you can add steps or less steps change name change colors, change the step intervals, change the method, hahaha instead of all the +/- 6 steps you can make some other system method that lands the same but essentially, it s like saying i patent the act of taking a picture, they can go to peep

If everyone at BlackMag asks for it, it might come to resolve

doing a good job, it's a shame that they have shielded it and are threatening the common man

managed to make it myself, super easy to find it on reddit under the headline "Tried out the EL zone system on set. Very intuitive. Has anyone else tried it?" and with the assistance of chatgpt, it was basically done! HOWEVER, has anyone found a way to include the colour scale as well to the lut or is it just impossible to do?

I received the PYXIS yesterday with knowledge of the issues. First impression was great, beautifully finished. A day later, I'm filming a bit out of the window and notice how the rolling shutter is visible as soon as I hold the camera. I don't even want to talk about it when panning. Either you don't pan at all or you pan so fast that you don't care. A slow pan is hell. If I have to stabilize all the footage now, it's going to be hell. I'm just thinking about giving the camera back. My alternative would have been an FX3, but it was more expensive. But at least it uses the full sensor in 4k and also offers more FPS. Unfortunately, Blackmagic has a lot of limitations, including cropping the sensor and extremely large file sizes. I don't know whether the braw makes me happier.

EL Zone must be freeeeeeeeeeee. This is why we need Putin. Only Putin can stand for the freedom from capitalistic mainded folks

Does anyone had download the file and can share with me?

YOOOOOO please respond! I copied your code but nothing is working

__DEVICE__ float3 transform(int p_Width, int p_Height, int p_X, int p_Y, float p_R, float p_G, float p_B) { float3 in RGB = make_float3(p_R, p_G, p_B); Float3 out = in_RGB; float luminance = (p_R*0,2126 + p_G*0.7152 + p_B*0.0722); float mg = 0.18f; if (luminance >= (mg*pow(2,6.5))) { p_R = 255; p_G = 255; p_B = 255; } else if (luminance >= (mg*pow(2,5.5)) && luminance < (mg*pow(2,6.5))) { p_R = 245; p_G = 190; p_B = 192; } else if (luminance >= (mg*pow(2,4.5)) && luminance < (mg*pow(2,5.5))) { p_R = 229; p_G = 126; p_B = 140; } else if (luminance >= (mg*pow(2,3.5)) && luminance < (mg*pow(2,4.5))) { p_R = 255; p_G = 0; p_B = 0; } else if (luminance >= (mg*pow(2,2.5)) && luminance < (mg*pow(2,3.5))) { p_R = 247; p_G = 170; p_B = 71; } else if (luminance >= (mg*pow(2,1.5)) && luminance < (mg*pow(2,2.5))) { p_R = 244; p_G = 112; p_B = 42; } else if (luminance >= (mg*pow(2,0.75)) && luminance < (mg*pow(2,1.5))) { p_R = 255; p_G = 248; p_B = 166; } else if (luminance >= (mg*pow(2,0.25)) && luminance < (mg*pow(2,0.75))) { p_R = 249; p_G = 232; p_B = 0.0; } else if (luminance >= (mg*pow(2,-0.25)) && luminance < (mg*pow(2,0.25))) { p_R = 128; p_G = 128; p_B = 128; } else if (luminance >= (mg*pow(2,-0.75)) && luminance < (mg*pow(2,-0.25))) { p_R = 148; p_G = 200; p_B = 64; } else if (luminance >= (mg*pow(2,-1.5)) && luminance < (mg*pow(2,-0.75))) { p_R = 94; p_G = 186; p_B = 71; } else if (luminance >= (mg*pow(2,-2.5)) && luminance < (mg*pow(2,-1.5))) { p_R = 29; p_G = 167; p_B = 75; } else if (luminance >= (mg*pow(2,-3.5)) && luminance < (mg*pow(2,-2.5))) { p_R = 39; p_G = 174; p_B = 228; } else if (luminance >= (mg*pow(2,-4.5)) && luminance < (mg*pow(2,-3.5))) { p_R = 24; p_G = 116; p_B = 167; } else if (luminance >= (mg*pow(2,-5.5)) && luminance < (mg*pow(2,-4.5))) { p_R = 156; p_G = 126; p_B = 184; } else if (luminance >= (mg*pow(2,-6.5)) && luminance < (mg*pow(2,-5.5))) { p_R = 98; p_G = 71; p_B = 155; } else if (luminance < (mg*pow(2,-6.5))) { p_R = 0; p_G = 0; p_B = 0; } out = make_float3(p_R/255, p_G/255, p_B/255); return out; }

So i copied the code exactly, triple checked it and brought it into Resolve and nothing happened to the image

I know you’ve taken it down but since you aren’t selling it can you send it to me privately? I’m out of options on getting this feature

If anyone downloaded this before please message me!

awesome video! I want to use this to replicate other cinematographers and practice. I downloaded some stills from IMDB but when. i went. to use this dltc it was off... I believe I coded everything right, I tried transforming the stills to linear as well but the output color space could not be turned to linear. I am missing that grey card thing you have in one of your nodes. could that be affecting something? how would you go about using this with misc movie stills that you want to replicate?

Besides open gate, the Cinema 6k and Pyxis has better rolling shutter than the Sony FX9 and the same 22ms as the Sony Burano that cost $25,000. People just complain too much and it’s really ruining the independent film maker’s world. The FX3 has less pixels and only shoot 4k. People need to stop complaining or just don’t buy the camera.

Any why to get a .cube file to test it with my monitor?

great. Thank you.

This is a great video !!! was able to create the DCTL , exactly. recoded what was shown in the video. Things seems to work but only problem is - the colors are not coming correctly as per the EL zone. Middle gray shows as +1 stop .. and only 4-5 band shows up when I use it on the exposure gray card DTCL I checked code multiple times and luminance range for each if else and RGB even thing looks fine in the code, but I nearly see the right EL zone for any of the exposure gray card. Any suggestion help is much appreciated

Where I can get this Grey Card FX? 13:15

I tried copying all the text from the code to recreate this DCTL for my use, and generate my LUT, but when I put the DCTL in the Davinci LUT folder and apply it to the video, nothing happens. I copied your code exactly as it is. Any tips?

Thank you for showing this I had no idea and I’ve been shooting black magic for 5+yrs

bro what the fuck 😲😲😲😲

Just so you guys know Monitor+ has El Zone support kind of "hidden", you need to press and hold the False color icon and it will show up!

Anyone has that link to the DCTL?

You're still losing material. The best thing to do is getting a camera with good rolling-shutter performance (or a global shutter). Sadly, a lot of the recently-released cameras' chip-readout times suck. Anyway, this video lacks any substantial demonstration of legitimate jello effect, which occurs during UP-&-DOWN movement.

Thanks

I copied the code, and it doesn't seem to be working correctly on my Ursa Mini Pro G2. It shows the wrong values. Do I need to alter the DCT for my camera dynamic range? How can I do this? 14-15 stops dynamic range. Need a monitoring lut. This is amazing stuff man!

This is pretty cool! It's easy enough to find the code and make the DCTL. The unfortunate thing is dealing with Linear gamma and having the wrong previews in the clip view.

mega

Atomos also has it as paid upgrade to their monitors.

I'm selling a Blackmagic Production Camera 4K that has GLOBAL shutter if you're interested.

does anybody still have the file or the link and could DM

Is there any place we can find this lut? Asking for a friend

wow nice! . I just bought a S5iiX :( @ChannelPanasonic please add this gyro thing on the next firmware !

Is there any chance of someone sharing this DCTL privately??? 🙏🏻🙏🏻🙏🏻 It's a shame a tool THIS GOOD is not allowed to be shared… 🥲 klqwdhjkqlwdh

Hi mate, thanks for the video and easy enough to code. Have you found underexposure to be way more sensitive than overexposure? Just seems to be far more limited range on the darker areas

Then when filming scenes you will need to stabilize in post, perhaps best to shoot a tad wider b/c you will need to crop.

I actually didn’t know this either. I know the gyro stabilization but never knew it would actually fix the jello effect. Very impressive and thank you.

It baffles me why this video is 8min long if its only one button?

WOW did not know this, thank you!!

Do you sell the DCTL for the EL Zone system? I’m clueless on how to make one. I want to study other films using the DCTL.

hy, is there any way to get the lut now?

More content please! Amazing videos

T H A N K Y O U ! ! !

this is genuis!!

AI helped me to generate code for this. It works nice inside davinci when log converted to linear before the DCTL node. I converted it to .vlt LUT and put into my lumix S5iix but everything is so dark on camera monitor.

I didn't known about this features. Thank You for sharing Yours knowledge

Whoa, I gotta try this!

thanks crack!!

This is fantastic, well done! Too late for the download but easy enough to rewrite my own code. Works great in Resolve, however, when I make a LUT the DCTL node is ignored, so I get a LUT with just the CST to Linear. Any ideas why?