Messages

@Jonit: funny, that really works - overexposing by far, and then EV=-4, Highlight Reconstruction = on. You can see the focus pixels.
@Jonit: this does only work, when leaving Focus Pixel Fix enabled. When switching it Off, those pink dots are away.

@dfort: I also recorded some frames, one clip overexposed (@10bit), another with normal exposure (@14bit) using Danne's rewire preset @ 1736x1158. I uploaded the clips with an receipt, so you can see them good in MLVApp. Does this help? It seems there are different types of focus pixels - some are very good to see (white, center), others not so good to see (dark grey, everywhere). The dark ones are good visible in the overexposed clip, processed like Jonit did.


https://www.dropbox.com/s/beswhuzkoin7axr/FocusPixelEosM_Rewire.zip?dl=0

Some notes:

• It include ELNS block in metadata, so most editor may fail to open to MLV files.
  @Ilia3101 and all others devs of MLV processing tools. May be a good chance to add support for it or make editor robust and skip unknown blocks

Done for MLVApp. But it is 100% untested. Need such a MLV file. Some frames are enough.

what I did also understand now, when recording 14bit lossless, focus pixels can be removed in MLV App with the "Fix Focus Dots" set to on. No need for 3x3 chroma smoothing. This seems to be only good for 10-12 bit recordings.

After we got focus pixel maps for the new presets, there is no need for chroma smoothing. Until this, it will be the only simple way to remove them.

...and I who just thought I had to switch on the Dual ISO button!

In general... yes... and then the fun begins! Without correcting some parameters dual iso files should look 100% identical. But then you can push things much harder until you see artifacts.

Hi,
I just used DualPixel for the first time
Unfortunately I did not get the result I wanted...
I use a mk III and compared two exposures - one with and one without Dual Iso
Dual Iso was set to +2 EV
In MLV app 1.5 I clicked on force on The Dual Iso file and then set it to on
Then I processed the two files (that looked identical in MLV...) to two H264 movies, opened them in Photoshop and compared
BUT I cannot see any difference in the shadows!!!
What did I do wrong?
/ olof ☹️

How did you process the two files? If you just enable dual iso, and do nothing more and export to h264, you will loose all data you got before. If you use e.g. the lighten slider = 75 (pushing shadows) you will see a huge difference. I set sharpen to 100 to make the effect more visible.

Without dual iso:


With dual iso:


See the noise in the shadow left and below the tree.

Ok, so "Movie Crop Mode" has still to be set manually. x3 zoom mode works fine. When selecting 2.35:1 : is there a way to crop the top and bottom of the liveview?
In terms of 25fps I was a tiny bit more satisfied before with yesterdays build - because I got 25.000fps and with some Shutter fine tuning I got exactly 1/50.000s. Identical to my 5D2. Now we get 25.003 and 1/50.006s (tuning @ -0.23ms). Is it possible to get the exact thing when activating 25fps in submenu?

[so push canon menu button and back to set the preset fully]

And no need to press menu button ?

->

Once Movie crop mode is enabled it will stay enabled upon restart as well. Upon restart it will start in x3zoom so push canon menu button and back to set the preset fully.

Okay. Done. Here you are: https://www.dropbox.com/s/70ig9z535kixmk0/binningtest3.zip?dl=0

Deleted the lines for the menu in the script. First picture has "wonderful moiree", but camera won't record a second picture. Instead doing so, screen turns 9/10 white. When pressing menu 2x between the 2 shots, I get a picture... but I will "shake" the camera with that. So... I delete only the 1st menu open/close? Or wouldn't help that?

@a1ex: when running the script, canon menu pops up before taking a picture. Maybe after that, moiree is away? Doing that manually it looks like that:

1. just configured
2. pressed 2x menu button (enter&leave canon menu)

Updated the script and run again. https://www.dropbox.com/s/oi5y5ebntdh2rnp/binningtest2.zip?dl=0
Sorry... we're very poor here... all 4 lights were on. But I raised ISO, so it should look better now. Vertical stripes are still there.

One more finding: I was able to see the aliasing with magic zoom function in liveview. I then pressed somehow 2x canon menu button, enter, leave. After that all the aliasing stairs were away - using the "bad" mode. Recorded another MLV and it looked like the one with -4+4 skipping at top and bottom. Maaaaagic.

How do I enabling the mode:
- switch on camera
- activate crop_rec setup "... rewire ..."
- crop_mode = ON
- leave ML menu
- record

-> when pressing 2x menu button before recording, all is fine.
-> maybe this is why Danne was not able to reproduce?!

Got it. I enabled silent picture mode manually, run the script -> bingo.
Here are the files: https://www.dropbox.com/s/o3sohi4i88xhwe3/binningtest.zip?dl=0

The setup tested should be:

Code Select Expand


        skip_top = 82;
        skip_right = 60;
    skip_bottom = 2;

->the yesterdays setup "with stairs"

Hm... still have problems with the script. Again no picture. Then I setup silent shoot manually - no prob - working with halfshutter and DNG availlable.

Sorry... found it... too stupid. I have to load silent.mo! Will test again now.

@ a1ex: I tried running your script... I saw the outputs "preparing, 1st, 2nd, finished...", but where do I find the pictures? Can't find anything on my card... 

Edit: halfshutter for taking a silentpic? Is that correct?

How does the last build perform?

I would say even worse... the moiree is so extreme, that you can see it in liveview already.

I think, first of all, we need a simple strategy to reproduce. I loaded the ISO 12233 test chart, printed with a laser printer... not perfect, but should be enough. I took EF-M 18-55 STM @ 55mm, fully open. And now you might see which picture is which setting:


I think the pics look very different... see the focus pixels and the amount of moiree.

Yes, that looks like what I see here. Best use a wideangle lens where a lot is in focus. Then search trees and hard contrast edges at 45°. Very easy to reproduce this way.

Brew isn't supported on OSX 10.9 (or the packages needed). So no chance for your app. It won't install anything.

-4+4 equals:

Code Select Expand

        skip_top = 78;
        skip_right = 60;
    skip_bottom = 6;

...if the register screen does what we think it does...

86 and -2 as suggested would become

Code Select Expand

        skip_top = 86;
        skip_right = 60;
    skip_bottom = -2;
And then we have a fat white border at the bottom.

Have you tried out? Oh man... I really don't understand what happens here.

I cannot reproduce the issue described so I really suggest you download my branch and get right into crop_rec.c and compile crop_rec.mo with any optimised settings you come up with. It´s easy with Compiler.app.

What a shame it seems I am the only one getting this. Unfortunately I am here with OSX 10.9, which is not supported by your compiler app (or by brew).

Build used is: crop_rec_4k_mlv_snd_isogain_1x3_presets_2019Feb17.EOSM202
-4+4 looks perfect. Registers have 82 and 2 by default, you wrote

Build before:
-2+2 looked perfect. Registers were 84 and 0 by default.

So I think the math behind is not default+offset, it is default-offset. The algebraic sign (+ instead of -) should be wrong - or I am... confusing... 

So I would try 86 and -2 next.

@Danne:
I expect indeed a sign error somewhere. I again tested the first build after the red line (the one with the stairs). Reproduced all I saw yesterday. BUT: reg_skip_top=-4 and reg_skip_bottom=+4 looks perfect
What happens for:

Code Select Expand


        skip_top = 86;
        skip_right = 60;
    skip_bottom = -2;

@jacquaviva
Activate it once for one clip, Ctrl+C (maybe activate in mask chroma smoothing only), Ctrl+A, Ctrl+V.

Placebo?
Anyway. Here´s a build with your proposed settings working best:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg208959#msg208959

Here is the feb 15th build compiled exactly before the thin red line fix in commit tree(compiled today and renamed):
https://bitbucket.org/Dannephoto/magic-lantern/downloads/crop_rec_4k_mlv_snd_isogain_1x3_presets_2019Feb15.EOSM202.zip

No, don't think so. The "stairs" are very easy to identify at 45° edges, same for the red line. But what happened for your "rewire=old" preset? Why activates it the stairs, and -2+2 doesn't. And all this does not fit to yesterdays build. Something must be wrong.

Will test again the posted builds.

Very strange. Do we have a kind of sign error somewhere? Don't understand all this at all.

The only two settings without bottom line are rewire=old and rewire=off-2+2. But in rewire=old I get stairs, hard focus pixels and more artifacts. So in this build I prefere rewire=Off, reg_skip_top=-2, reg_skip_bottom=+2.

You'll find a png with some marked areas in the frame where I looked at details and my receipt file.
https://www.dropbox.com/s/wddfxe3p7zmdsn1/RewireTestrun.zip?dl=0