Messages

I can't say anything about that exact filter, but I do a lot of such water scenes. My usual setup is a 1+kg carbon tripod, ND8 B+W filter (or a Chinese one, sometimes), not a large one. You can stack it with a CPL, but vignetting and flares become worse. The more surfaces you have, the more reflections you get.
I believe, any high density filter gives a noticeable color shift and some lack of sharpness. And no filter gives you a way to shoot in a broad daylight. F22 usually is a good solution, but you need some other shots (F8 or wider) to recover small details around in post. And flat frames to get rid of dust spots.
I prefer a moderate ND, then I can go with silent pictures at 0.1sec or multiple shots. You should align frames (perfectly!), then stack. Choose a tool you like, PS isn't the fastest one. If you have time, try video tools with optical flow (like Twixtor) - simulate more frames, then blend them.
Don't waste money too fast, get some practice, get some feel of it.

The first thing, which comes to my mind, is checking the card serial number (in-camera). If it's out of the Red-range, then it reduces writing speed. There are people, wanting to change these serial numbers but they lack low-level tools for CF. The other way is to find and patch these ranges in camera firmware. This may be a long way or a very long way 

And the last thing to try - switching cards in some way. What if the range check is done just once? When the card is initiated? Can we block the card-door sensor? The latest way of downgrading canon firmware appeared from such card fiddling.

For 5DII, please, check this thread. And Downloads> Experiments for other latest staff.
Failed auto test is not a problem. There are more dangerous things here 

May I ask you a question: isn't lightning "slow enough" to be caught by motion detection and full-resolution silent pictures? It might be tested with some video at home...

1) No additional sensitivity
2) I guess buffering happpens in RAM, then data slowly pass to the card. Getting free RAM is a good idea - unload all unused modules. Long time ago we even compiled without some features (defishing, etc.) to make ML smaller.
3) Is the bitdepth really critical here? You're shooting just a bright line. Everything else should be blended from a good long exposure frame. Isn't it?

Please, report on you experience. Check CHDK forum on that subject too.

a1ex had did some test a long time ago on 5d2 and had the CF card overclock for faster write speed.

It seems, there was a little problem with overclocking. Please, be cautious.

See this old thread.

All the nightlies found are for middle of 2018.

Look into Experiments section. By the way, fully working adtg_gui module is the perfect start to implement crop_rec video and/or custom adtg gains. Look how Reddeercity did it for 5D2 - lot's of these things are avialable for 550d (try it!).

Or just keep the camera and keep waiting. I use my 550D with great pleasure.

You have a plenty of options (I've tried all).

Split-screen is useful for dark conditions and fast shooting, when no other option is applicable. You'll waste a lot of shots, it takes time to get familiar to it. It's fun. It's very easy to install/uninstall it yourself.

Zoomed live view and tethered shooting are best suitable for macro and studio stills.
Focus peaking in live view is very effective, but it doesn't work with 100% zoom.

The fastest option is a chipped adapter. It enables built-in phase detection focusing (red dots it the optical viewfinder). I've tried a lot of adapters. The cheapest ones worked best for me. I tuned 5DII inner focus adjustment  for each lens (and wrote down the settings). Works perfect (except macro range). Programmable chips (with focus correction) were so wrong at default  "0", almost useless. 600D lacks inner focus adjustment.

In any case, you need widely opened aperture.

Not to interfere with the discussion, just to be a mediator here.

This standard is barely applicable to RAW files in terms of sensitivity. Camera producers use JPEGs for that case.

"ISO speed and ISO speed latitude values shall not be reported for raw images, however, because with raw images processing that affects the values has not been performed" (ISO 12232:2019). https://www.fastrawviewer.com/blog/fujifilm-x-series-iso-bracketing

The author of the software - Alex Tutubalin is one of the leading developers of LibRaw (not just the commercial part of the project). Fastrawviewer blog is very informative.
Looks like these two Alexes are the best experts on the question in the open-source world.
But both usually say, they know nothing. As Socrates did.

________
As Luther noted, there was a canon trick for intermediate ISOs (like 160) – exposure time was changed behind the scenes. Silently. But really it's not the case now. You can always use some moving (rotating) object to prove the same exposure for two frames.

You can still fix the mirror up without any software (just discussed here). I used Π-shaped piece of black velvet textured cardboard for that. So you can use USB for remote control and download CR2 files while shooting.

but pleaseeeee bring this to 5d2!

Already done: adtg_gui.mo works on all Reddeercity's builds for 5d2 + raw_diag.mo (portable module from Alex)
Some fast settings to start with - from my previous posts. Not consider as spamming 

And the whole CMOS/ADTG/Digic register investigation on ISO thread to study.

Welcome and... you have some real giants to compete with. Zerene Stacker is definitely the first one to mention.

I promised here this summer to provide better statistics on SNR while using reduced gains on 5D2.
A set of cloudy sky flats repeated twice. (Notice also, how much SNR is lost after 6 consequent shots, as the sensor becomes 7 degrees hotter). Numbers calculated with a fast PixInight script.

Code Select Expand


SNR = 26.42 db, K IMG_7671iso100_DFE111
SNR = 21.04 db, K IMG_7672iso200_DFE111
SNR = 16.76 db, K IMG_7673iso400_DFE111
SNR = 15.92 db, K IMG_7674iso100
SNR = 13.52 db, K IMG_7675iso200
SNR = 12.07 db, K IMG_7676iso400

SNR = 23.85 db, K IMG_7677iso100_DFE111
SNR = 19.55 db, K IMG_7678iso200_DFE111
SNR = 15.68 db, K IMG_7679iso400_DFE111
SNR = 15.27 db, K IMG_7680iso100
SNR = 12.92 db, K IMG_7681iso200
SNR = 11.63 db, K IMG_7682iso400


RawDigger produces a bit different results (and I cannot explain why), but the leader stays the same.
You can download the samples and check my math.

So it works, as expected. The only problem now: it's damn cold to tweak registers outdoors 

There is some open source project with Optical Flow - slowmovideo.granjow.net. Interpolating missing frames may be implementable here too...

No, that looks like actual data from the sensor. I get such bias frames adjusting analog iso register (between the main steps) (and I successfully use them as bais frames). Maybe you managed to set different iso for this part )

Then more it is advertised, then further from science it becomes.
"Once trained, the color chart is no longer necessary," – they say. The water in my bath has different color every morning. So does the ocean, I believe.
It's a good research but it's going to become a button push process for gopro or something alike. That's a pity.

And on the other side, there are also brilliant "unscientific" old ways to solve the problem like trashing the Blue channel (and reconstructing it from the rest) and guessing the depthmap (Kolor and Adobe used that for Dehaze feature).

- post process the mlv file, ie merge with mean or median statistics

Already implemented in mlv_dump. Simple average only. Not yet included in the GUI.

Code Select Expand


-- Image manipulation --
-a                  average all frames in <inputfile> and output a single-frame  MLV from it
--avg-vertical      [DARKFRAME ONLY] average the resulting frame in vertical direction, so we will extract vertical banding
--avg-horizontal    [DARKFRAME ONLY] average the resulting frame in horizontal direction, so we will extract horizontal banding
-s mlv_file         subtract the reference frame in given file from every single frame during processing
-t mlv_file         use the reference frame in given file as flat field (gain correction)


Banding is always there. At iso 6400 its simply hidden under aggressive amplifier noise. There was a great experiment to correct it in camera.

From my photo experience banding is partly corrected with bias and dark frames and finally goes away after applying flats.
There are special tools for that like Superbias and Canon Banding Correction scripts in PixInsight.
Video case is a bit more complex as we don't have optical black areas in the frame.

According to the Calculator, it should. Test the card, read its specification and find the way to recycle it safely

May the --force be with you 

I referred to windows version of cr2hdr-20bit
https://builds.magiclantern.fm/jenkins/view/Other%20tasks/job/cr2hdr-20bit/

Sometimes it ignores the files

Code Select Expand

Doesn't look like interlaced ISO
ISO blending didn't work


Running it with the --force option you get blended DNG plus information from the log like this

Code Select Expand

offset too large
You may get stripes at some lines finally (in the highlights, I believe).

Have you tried some --force?

Code Select Expand

cr2hdr.exe --force IMG.CR2

www.youtube.com/watch?v=x8OC7rE_kX8

You haven't removed the previous build before copying the latest one. There is no mlv_lite.mo in that branch. Remove ML folder and copy one from the downloaded archive. Does it work?

So much discussions about the black window...
Here are two more programs to hide cmd window - https://ffmpeg.zeranoe.com/forum/viewtopic.php?t=4744#p13619

And a C++ sample  here.

Script languages like Autoit/Autohotkey also run hidden processes without a problem.