Messages

Shoot. I missed that on the back! Definitely won't be good for raw video then.

Anybody have faith in this guy DIGIGEAR SLIM CF Adapter : SD SDHC SDXC WiFi-SD eyefi to Type I Compact Flash Card https://www.amazon.com/dp/B00XO2KSEO/ref=cm_sw_r_cp_api_i_fUb5EbC9GZKB4 paired with a fast SD card for continuous full frame (1.0x) recording?

Thanks so much Levas! I think 12bit lossless will do it for me! I will be relying pretty heavily on that UHS module to get continuous recording (24.00fps) for interviews. Is there any risks when using the UHS module? Is there any risks with damage to the card/camera? Corrupted frames?

On the 6D, Is full width 1824x1026 recording continuous with uhs module and 12bit recording? Is full width continuous with 10bit and uhs module?

And by the way if you try it see last image of "color space transform" and look at "tone mapping" choose "luminance mapping" and set "adaptation" slider

Thanks so much!!! Where should I set the adaptation slider? What's the difference of a low value and a high value?

I will give this a try! But I already have cdngs made from months ago. Can I still change the white level? Are there no other IDT's the play nice with ml raw without having to alter the source file?

It is enabled by default, because most cameras need these corrections. Appart from that, this needs nearly no time in processing. As the name says (RAW correction) the RAW data is corrected and the corrected RAW is saved into cDNG. After having exported the cDNG, there is no easy way to correct it afterwards.

You can open all your files in one session, uncheck it for one clip, CTRL+C, CTRL+A, CTRL+V.
OR
You can open one file, uncheck RAW corrections, save the receipt. Load this receipt as default receipt. https://github.com/ilia3101/MLV-App/wiki#22-edit

Thanks all for the replies! Very very helpful!

So most cameras need this correction? Are they present, and I'm just not noticing them?

If the image looks good, does leaving "vertical  stripes" on, degrade an already good image?

Is there anyway to disable "RAW Correction" by default? It is enabled on all of my clips by default, and "Vertical Stripes" is always set to "Normal." Does MLV app alter the RAW data if the "Vertical Stripes" is always set to "Normal?" With that enabled, it's still exporting RAW right (if I export to cDNG?)

Thanks all! I'll try a few of those suggestions! Is there no way to open in a text editor Or something and view the code that would reveal it to be raw data?

Thanks Walter. I already did that. Can you provide a technical approach?

I've received a .DNG sequence from a coworker, and the files are incredibly small (like 200kb-ish a frame.) My suspicion is that they exported a .JPG sequence, and then converted the .JPG's to .DNG (which apparently you can do that???)

How can I check if a .DNG is really raw data? Can I open in a text editor? Is there a utility that makes it easy?

Thanks all!

I see! Thank you. I don't see an advantage for it. Is it probably best to leave it at "0"?

In normal default raw MLV recording, there is no crop on the 6d, crop is 1.00.
You can select 1824 x 1026 as highest resolution in 16:9 aspect ratio.
The 1824 horizontal pixels come each from 3 pixels binned together (so the origin is from 3 x 1824 = 5472 pixels, the full width of the sensor of the 6d).
The 1026 vertical are from every third line on the sensor, (skipping 2 lines every time), so every 3th line is read, 3 x 1026 = 3078 pixels. (This is for 16:9 aspect ratio, sensor is 3:2 aspect ratio)

So I just realized, that Canon markets the 6D as "FULL HD 1080p." But that's not true, is it? They're upscaling the image in normal canon firmware???

Sry, no idea what your talking about. Where do you see or set the black level in ML menu? "0" will never be correct (with a Canon cam) and will lead to pink shadows.

Its in "Movie">"Image Fine-Tuning." Whats the use of changing the black level in ML menus?

Are there any built-in IDT's in Reslove that work play nicely with DNG's from MLV?

No. The white and black point is set by ML in the cam. MLVApp reads this metadata and allows to adjust it in the case it wasn't correct.

In the ML menus, the black level is always set to "0" even if I change the bit depth. Is it still setting the correct value in the metadata then?

Magic Lantern 81 ISO is 100 ISO in the menu , if you don't have magic lantern installed , you don't get 81 ISO .

Thanks @reddeercity! In the ML menus, it still says ISO 100. Do I set a "negative gain" with "ML digital iso?" Do i need to enable "Expo. Override?"

How do I enable the use of iso 81?

Does MLVapp automatically set black & white points for the footage depending on its bit depth? Or should we be doing that manually?

Also should I always be doing something in the "RAW Correction" panel? if the stream looks good, then I can disable it yes?

@levas thanks for all the info 

[But the frame you're looking at, is not what it looks like.]

But the frame you're looking at, is not what it looks like.
The black borders are readout pixel for pixel, there is no binning in the black border part.
So what you see is a black border made out of ~160 black pixels, readout one by one, no binning there, and the rest of the width is ~1872 pixels binned together(original read from 5616 pixels, each 3 pixels binned together to one)

@Levas & @reddeercity thanks again for all the useful info. See the linked images below.

I mocked up a few images.

If the image @reddeercity was not 3x3 binned, and shot at full resolution - it would look like this? (Black borders are 160px from left. 18px from top.)

https://ibb.co/BsrZJq9

And to confirm I'm understanding correctly, ML handled the image this way? (Green pixels are full pixel readout, and pink area is 3x3 binned)

https://ibb.co/tPG900b

@Levas please see image below. (Let me know if it doesn't work.)

https://ibb.co/SwZRjck

Looking at the green boxes, which image is the sensor's 36mm x 24mm area?

If it is the left, then roughly 8% to 10% of the 36mm x24mm sensor is "cropped" by black pixels?

I did a quick test build with no image offset , in other words I recorded the whole sensor black border & all .

First 3x3 (FHD) 2040x1267 , this is the raw_image dump
(I didn't adjust the black level , sorry it 128 should be 112 for 10bit )


Here the 5D2-3x3-Raw_Dump_dng-ppm-png.zip
If you do a crop in IrfanView you get 1880x1250 ,
which the offset is correct in raw.c  160 pixels left & 18 pixel from the top
Though this would help people understand better how the sensor is configured 

So including the black pixels, the sensor is actually larger than 36mmx24mm, yes?

? I yet said 5D2 has 11.92 ,no 11.16
what @ilia3101 posted is not correct .
image below from this post from a1ex https://www.magiclantern.fm/forum/index.php?topic=10111.msg98281#msg98281

What does ML do to get the extra dynamic range? Why would canon original firmware "suppress" the dynamic range?

How many stops of Dynamic range is the 5D2 capable of in normal MLV raw (NOT dual iso?)