Messages

[5D mark III]

Some initial testing around the blazing fast raw_twk module. I also tested it with the magnificent crop_rec module on a 5D mark III.

Pros
5D mark III mlv_lite
1 - The 3xzoom mode grayscale preview crash bug is gone!
2 - Playback works great also with the magnificent crop_rec module(tested centred 5xzoom)
3 - 10bit, 12bit, 14bit works

Amazing new ! Can't wait to test the new 10/12bits build coupled with the super crop_rec module version

@DeafEyeJedi -- in 48/50p the vertical resolution is 1.67x smaller, which kills details and causes aliasing and moire. Most of wide angle shots are quite bad.

Switching to canon 25/24p mode and then overriding to 37fps means much more detail for me. BIG chance for me, crippled resolution in 48p mode was a reason for me to start looking for a new camera.

look at the aliased edges:
https://vimeo.com/148944224

Your work is just amazing ! Never saw your stuff before.
How did you grade it ? Which softs ? which luts (if used) ?
I dont saw informations.

For answer you about aliasing and moire on 50 and 60fps footage due to stretching, yes it's a small issue, but believe me, most of 95% people don't will see anything.
And for be honest, on your footage i'm not focused on it.

[ML / modules / raw_rec.mo]

I cannot find module for 5D Mark 2. That means there is not a proper settings available for 5D2 yet where every 2nd frame is not pink?

Check this post : http://www.magiclantern.fm/forum/index.php?topic=5601.msg174302#msg174302

Just replaces the module in your ML installation : ML / modules / raw_rec.mo


But yes, with the 5DII version there are pink frames issues. 10 and 12bits

Tried the 5D mark II with 12bits
Extract MLV with the new mlv_dump version and the line

Code Select Expand

--dng --no-fixcp --no-stripes

I got pink frame issue too

Now i will test the 5DIII

Even if we got issues, i'm sure it will fixe of everyone do tests.

Thanks @dfort for all these news builds !

EDIT:

Ttried with the 5DIII :

10 bits = Stable  | FPS override enabled
12bits = Got pink frame only on the first frame | FPS override enabled

[dual iso]

Just did some tests with dual iso on the 5D mk III.

I did not find any bigs problems, it work well.

Just saw some strange colored artifacts in the top border of image.
Not a real problem, i can resize (arround 10 pixels) a bit my footage and it's gone.

Thanks you for these news upgrades @AWPStar !

Work with dual iso footage is become more easy now.

Nice find Alex ! An additional small revolution in the magical world of magic lantern.

Thanks for your feedback !

Hello !

Made a new short movie :

https://vimeo.com/189647784

5D mark III RAW (crop3x build from 3 sept)
24-70mm F/2.8 + Kenko Variable ND Filter
Monopod (Stabilisation in Premiere)

Davinci Resolve 12.5 + lutify LUTs
Premiere Pro + Film Convert

@jzedurqn Nice work !

New builds:
- 5D3 1.1.3: magiclantern-crop3x.2016Sep05.5D3113.zip (build log)
- 5D3 1.2.3: magiclantern-crop3x.2016Sep05.5D3123.zip (build log)

Changes:
- synced to main builds
- vertical stripe fix removed (no more bad pixels and digital ISO issues)
- minor status icon fix
- backend updates (patchmgr branch)

Indeed, the crop mode appears to clip highlights a bit earlier, but certainly not by 2 stops. The raw histogram shows a difference of about 0.2 ... 0.3 EV on a blank wall.

This new build + new version of mlv_dump is the perfect combinaison, i just did some tests.

Thanks you Alex for your work. 

Hello Francis,

Do you use subfolders with specials characters like "é" "à" etc .. ?

I did the test with specials characters and MLV Mystic 0.5, i get empty folders too.

Cheers !

well i just tried the test with the diffuser in front, my light is powerless and the image isnt clean. I will get LED light in some days and renew this experience later.

in case, here anyway the .MLV :

https://www.dropbox.com/s/2p98vc3uxv83iij/M02-1449.MLV?dl=0

Sound very usefull, that mean we're able to use this unic "flat.mlv" for correct all our footage with vertical banding issue  and once created, you just execute in default into mlv_dump and be quiet for the next MLV  extractions?

Obviously those that I made could not be applied to everyone and everyone should create his own if need ?

I'm curious whether this technique can remove the dust spots as well. @GutterPump, can you take a flat field image with the lens on, and a diffuser in front of it, at these settings?

Code Select Expand


     Name:        'EF24-70mm f/2.8L USM'
     Focal Len:   24 mm
     Focus Dist:  356 mm
     Aperture:    f/18.20


Yes of course, i will try it tommorow !

First test done with the flat image :

https://www.dropbox.com/s/7d6kgl0cjmqexqz/flat_23aug_160iso.MLV?dl=0

tell me if I didn't made mistakes

I did a bracketing too with the same technic and silent pictures (bad pixels no fix)

https://www.dropbox.com/s/jvpz0qw9ap46pba/flat_DNG_bracketing.zip?dl=0

                                 

Second test

https://www.dropbox.com/s/cm7kdvv4gtyo96x/bracketed_sample_adv_int.MLV?dl=0

@GutterPump: can you take a flat field image? That is, an image without a lens, but with a piece of paper instead, like this. It should be exposed to the right, but not clipped.

I need to know if i must do this RAW video or standard RAW photo, anyway I'll do both

Additionally, can you take a bracketed image at the following settings?
- Subject: a blank out-of-focus wall, or anything else that looks flat without details (not critical, but the scene must be perfectly static)
- Movie mode, ISO 100...400, 1/100, image exposed to the right
- Advanced Bracket: 2 frames, 1 EV spacing, 0++, 1/100 ... 1/50 (that means, Tungsten lights in PAL land are fine)
- Silent Picture: simple (any file format is fine)
- Intervalometer: enabled (to avoid any camera motion), stop after 10 frames (it won't work from the first try).

I just noticed a bug with bracketing + simple silent pictures: in LiveView I need to wait some more after the exposure is changed. That's why I've set the intervalometer to stop after 10 frames - to work around this bug. Please upload only a successful pair of images.

The ratio of these two images (ideally 2) should reveal the stripe pattern.

Of course. I will do this tommorow at my work (more light in the piece if i want pass this experience), in waiting, i'm checkind steps by steps what i should do exactly
Is there no matter about the build ? i will use the 23aug  crop mod build

but I have no way to test - my camera shows absolutely no sign of vertical stripes...

You're very lucky .. That want mean, calibration made by Canon isn't so well for all camera ? There is problem problem about the reliability of their plant testing.. Or maybe it's a question of release's date.

You should look at this topic

We're very closer to the solution. It's just a question of waiting

Wow nice find .. Can't wait to try it  !

Finally, the last thing that was a little defect in the RAW video with the 5D Mark III is now completely fixed.

Got it, so Canon's correction is probably not perfect either, but the defect is probably visible only on extreme grades.

I assume mlv_dump --fix-stripes (or the old version, which does this by default) would fix the remaining stripes, correct?

Yes :

https://www.dropbox.com/s/czyypkn52z0k0vq/Timeline%201.mov_snapshot_00.00_%5B2016.08.29_16.17.19%5D.bmp?dl=0

I think it should better to set mlv_dump with --fix-stripes as defaut.

Thanks @GutterPump for all of your reports. Nice work!

You're welcome ! I was so frustrated with this issue, need to find the problem fast !

edit: narrowed down, it's from the vertical stripe fix. There are raw streams effected by digital ISO, and streams that are not. So far, I've assumed the LiveView raw stream is not affected by digital ISO, and the photo raw stream is always affected by it. Looks like I was wrong.

On 5D3, these raw types are affected by digital ISO: 2, 4, 14, 18.
These are not: 7, 8, 16, 23, 28, 34, 39, 50, 55, 58.
These have bad pixels: 4, 7, 8, 14, 23, 28, 39, 55.
These do not: 2, 16, 18, 34, 50, 58.

Please double-check my list (I may have missed some numbers) and check the vertical stripe status of those raw types. Ideally, we should pick a raw type that has neither bad pixels, nor hot pixels, and nor affected by digital ISO. If that's not possible, we'll pick the closest approximation (my current best guess is 8 ).

Test build (you can select the LV raw type from the Debug menu): zip

I tried this "special" version of ML, with 8 raw type, i don't discover any problem with and without ML digital ISO tweak at -0.3 EV

(Will do others and others tests but seem work well and better)

And the new version of MLV_dump erase correctly all the bad pixels ! And of course the verical stripes fix seem to work well too. (don't tried in crop mod)

EDIT :

I did a "stress test" in Resolve for view vertical stripes, the result is : there are always "but less" vertical stripes.
With and without ML Digital ISO
.MLV converted with the new mlv_dump
Was done in normal mode (not crop mod)
Always with the 8 raw type

you can watch here :

https://www.dropbox.com/s/f9tdfze9sdiz78v/MLTEST-28aug-vertical-stripes.mov?dl=0

Video is in DNXHD 444 codecs (dont view directly in browser, download is better)

Well thanks you Alex for your efficiency

Are we nearing the goal ? i will made ​​news tests tommorow if I have time. I hope we will see this crop build + vertical stripes fix in official version soon.

Place .MLV files you want to convert in a separate folder named by exemple "batch"

Choose this folder in MLRAWviewer, make your settings and destination folder, and press C for a batch processing.

I m not sure about dead pixels. Because when I convert the same footage with mlv viewer all image is clean. IMO the current Mlv_dump version can't analyse and fix all bad pixels.

I did the test with a white wall i get the same between mlv_dump and mlv viewer and with the boths builds.

I couldn,t see any pixels from these files? Did you select fixcp in mlv_dump?
http://www.magiclantern.fm/forum/index.php?topic=17021.msg171393#msg171393

Yes i select --fixcp in mlv_dump, you can see bad pixels in Resolve in the right/top border.
Or else if i dont use this command, entire footage is contamined by cold pixels.

e.g. :

from "M28-1516_23augbuild_isoteak_On_light" or "M28-1516_23augbuild_isoteak_Off_light" DNG folders

I dont know how to compile i dont have enough dev knowledges.. If anyone would like to try.

You will see in this zip :

https://www.dropbox.com/s/9efqoxex5o5xm1e/23augBuild_HL_issue.zip?dl=0

These hot pixels, especially in the border of footage made with 23aug build, i don't tried the fix cp2 setting, what command should i try ?