Messages

I too recommend that you don't hardcode any exposure change to the DNG. But optional or a slider, that would be great and even other metadata.

Resolve 16 free version that i have does support CR2.

dont need it, i just wait a 1s or 2 so that resolve updates the image.

Resolve can import CR2, sure, but as you wrote yourself, the processing is extremely slow and the colors are somewhat off.

If you convert to C/DNG, the processing and rendering is done in real-time and the colors are correct.

Resolve can't handle CR2, you need to use Adobe DNG converter. CR2 to DNG

Then you have a real-time playback of your Timelapse.

What the hell... That makes no sense.

Go to Sub-Menu of Zebras, under Overlay Tab.

'When Recording: Show' - Note: as you are on 5D2 this might decrease the recording time as it requires more processing of the 5D2, so you might want to set it to Hide.
'Use RAW Zebras: Always'  - this will also show you a high quality RAW zebra overlay in Image photo review, really helpful.
'RAW Underexposure: 0 EV'

Thanks for the test, its nice to see the comparison first hand.

But I think you made a mistake in measuring the scene, ML Spotmeter does not measure the RAW data, unless you use RAW EV Meter.

For a much faster and accurate scene reading, I recommend you expose with RAW Zebras and RAW Histogram, especially if you want to hit the sweet spot of ETTR to maximize the DR. You can clip the Green channel and still reconstruct the highlights with Blue and Red channel. In certain scenes you can clip two channels and still be able to retain the highlights with some Post magic, but clipping two channels I would only recommend for Sky or naturally super brights, not clothing or walls as it can introduce unwanted artifacts in the reconstructed areas. And never ever faces.

Could you post 1 DNG from each test sample?

Nice! sticky this tread!

I feel safer getting my 3rd mkiii now!

I noticed Slimraw lossless compressed dng's can not be transcoded to MLV.

Does Mlv App "expect" lossless compressed dng's from MLV_dump to be able to uncompress/transcode them back to MLV?

Slimraw does a better compression than mlv_dump, I'd say about 10-15% more compression or put it this way, you can compress the lossless output from Mlv_dump with slimraw by another 10-15% or so, lossless.

Would you consider looking in to supporting lossless dng from Slimraw?

Been a couple years since I shot with my mkii. But i recall the 5d2 didnt go past 1600 ISO, anything above is digitally pushed in camera, but the anolog gain in the raw file is the same across 1600->3200->6400 (Or it was 3200 max). But feel free to correct me if I am wrong.

@bender@arsch

Shooting raw, the ISO is only affected by by the Analog gain meaning ISO 100, 200, 400, 800 etc. ISO 160 is a digital pull from iso 200, 320 is a digital pull from iso 400 etc, these intermediate ISO's do not translate to the final file, you can see it in effect by using RAW zebras, there will be no exposure change between iso 320 and 400.

And I cant play the video on my phone, but my phone is pretty messed up.

This is just a heads up!

Yesterday I got an error message I had not seen before on Batch_mlv. It's a bit of user error combined with design flaw.

Yesterday I found out that I have forgotten to bring my card reader, luckily I found my old Sandisk card reader deep in my laptop bag. The Sandisk reader does not work properly, as it will not finish any Copying or processes past 99.9%. But I'd atleast get 99% of my cards and I'd have to deal with the last 0.1% somewhen.

The bug is in its essence when you have the Output Folder Location set to a drive that is no longer connected to the computer. You would ofcourse not do this on purpose, but when you open Batch_MLV it prompts the window for your Input folder Location, but in the background the Output Location is by default set to the location of your previous conversion process, so if you were exporting to a T5 SSD and then disconnect it and few days later want to export to another location, this bug will most likely occur.
So no matter what Input folder you set, Windows prompts an error message saying "There is no disk in the selected drive". This lead me to believe my Sandisk reader had gone completely bananas. Bought another Card Reader today and experienced same issue and by this time I was thinking my cards had become corrupt.

Not until I noticed the Output Folder was set to a Drive Location not connected anymore.. I changed the Output and set the Input and it was all good.

TL;DR

If you get "There is no disk in the Drive" error message, check that your Output Locations is set to a Drive that is connected or "exists" for that matter.

Just a heads up.

Thanks again Danne for this really nice tool.

APP haha that's a new one.

And MPV

Its light and plays everythingand has no gamma shift.

Wired control REC, IRS, ISO, SHUTTER, TAKE PHOTOS, AUTOFOCUS, Real-time Preview, Manual Focus on 1DX MARK II, 5DS, 5DS R,  EOS R, 5D MARK IV, 5D MARK III, 5D MARK II, 6D MARK II, 6D, 80D.

"Real time preview", i only know that phrase from ML.

But this is very much Want>Need

Could you post the files? I'd like to compare myself.


If you could share your post process of the raw aswell.

SlimRAW can not be recommended enough.

I think BM Ursa does the black shading as a Sensor Calibration as you need to keep the camera with lens cap on for 5-10 mins for it to finish, this will remove the magenta cast that develops over time. I don't know how the Red equivalent works. But Ursa is not like DFA where you need to do it in post, you probably can, but that is not how the built in black shading works.

I remember some Sony TV's also had built in Image cleaning (maybe they still do), basically it was "White Shading" with a built in White Screen that you should leave on for 5 mins to get clean blacks and colours.

This ended up in the wrong thread, delete post please

Okey thank you, I will look at it when I have time.

OKey, I am not aware of this Power Timing Registry issue, what does it do? I don't see it on 123.

And I believe Francis wants to use the camera in normal 3x3 14 bit lossless, only gaining the increased capacity and post-process. Is there also an issue there?

Again, not sure how it works on 113, but on 22 july 2018 - Fir 123, when in High Fps modes, to avoid crash when toggling through 5x,10 and back to 3x3 you can set Half-Shutter press to Clear Overlays and holding Half-shutter while toggling through, this way it does not crash.

If you can intermediately get the footage in to L*a*b colour space, you can use saturation on a*b channels to get rid of Chroma noise, this also works well with Moire. Then convert the colour space back to your working space.

But examples of the problem are always preferred.

The Crop_rec_4k.2018jul22 for Fir. 1.1.3 is stable and (I believe) still running on most cameras that are using lossless builds. 

The same build for fir 1.2.3 can cause some memory errors caused by RAW_twk and MLV_play. Which does not brick the camera, but it makes you stuck with that build until A1ex fixes it. I am stuck on this build but I can still use both my cameras except for playing MLV in camera, which will turn up nasty error messages and  A1ex's recommendation for me was to stay away from anything that initiates these errors.
Not being able to play MLV in camera is not a big deal for me, as you can't judge a performance by it anyways, you'll need an external recorder for that. Though, it is unfortunate that I can not test Danne'e 4k Builds, they seem very interesting.

Which brings me to Danne's 4k builds. https://www.magiclantern.fm/forum/index.php?topic=23041.0
They offer even further tuning of the 5D3, like Pseudo 5k Resolution and other very interesting stuff, but I have no first hand experience with it and I have no idea if it is stable or a deep menu dive for every operation.

Danne's Batch_MLV works 100% with Lossless 14 bit. I do recommend you get the newest version of it though, as Danne added the -skip--xref option which will make sure that all MLV audio is converted, this was an issue before where none or only parts of the audio were in the final output.
Newest Batch_MLV Build: https://www.magiclantern.fm/forum/index.php?topic=10526.msg215946#msg215946

Good Luck and as always, do as much reading as possible beforehand, read the thread on Danne's 4k build for the ins and outs and ask around if you are in question of something, this is a forum after all.

Good stuff as alway, Francis.

But you should look in to Lossless 14 bit, you effectively double the amount you can record to your cards, with 100% same quality(lossless). Also increases file transfer 2x, post-production works with about half of the bandwith, meaning almost doubled performance in NLE and Grading programs.

If you feel unsure about it, buy a 2nd 5d3 and install it for testing and to get a hang of the lossless 14 bit post process as the Legacy converters won't work with. But there is mlv app and Danne's Batch converter. Both are superb.

Its overall a win win and if you get a 2nd 5d3, you can do multicam too, further increasing delivery.

Without knowing the post-process of this image, there is no way to tell. How is it in MLV app?

Post a cut mlv file.

Alternatively, is there a Grid placed over the light?

I can't tell exactly what happened or how. This happened years ago and I only reported the issue give or take 2 years later when something similar came up on the forum. But the fact of the matter is, that the only thing out of the ordinary that I did at the time, from having this card working 100% for 2 years or more, was to set Canon recording to both cards and ML Card Spanning on, the moment I hit record the camera crashed and I had a corrupted filesystem, this I do remember. What order I did it in, I don't remember, maybe it was that build containing some weird bug or/and it was my way of operation causing it. Just like I have Error 70 and memory errors on my two 5D3's that no one else has, even though I am running same build that thousands of others are using, somehow my way of operation is causing this to happen it seems... I might add that I don't feel I do anything special during shooting, I shoot a lot but very rarely ultra long takes like filling 128gb cards with one or two clips.

Ah okey, thank you for clarifying.

IIRC, the 5D3 is able to save the images on both cards (CF and SD). This feature would have been useful here.

This, together with ML Card spanning is what caused my Lexar card to get corrupted. To clarify, I set in Canon menu to save to CF and SD and then I set ML Card Spanning too. Then recorded a clip where the camera instantly crashed and the card could not be used. It was me being stupid, I had forgotten how the Card Spanning worked, and thought I had to do it also in Canon menu. The card works today, but has a slightly lower speed and when there is about 5 GB (128 gb) left on it, it have very unstable speeds and the camera will stop recordings.