Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - a1ex

#9401
Yes, the bugfix applies here too. Still not as good as ACR.

#9402
Just fixed a bug in UFRAW in highlight handling (seems to be some sort of overflow and it's present in 0.18 and current CVS). Before reporting it to the UFRAW bug tracker, I'd like you to try it and help me find a test case where the bug is really obvious.

matrix.patch (updated)

Here's my first try:

bug (posterize effects on hands; blown-out magenta):


fixed:


bug (magenta halo; harsh transition from overexposed highlight to background):


fixed:


bug (magenta cast; the LED was blue):


fixed:


If you have some really blown out RAW shot that you'd like to try recovering, let me know.
#9403
ML overrides Canon audio settings completely.
#9404
General Chat / Re: ML 2.4 ? For Canon 60D
April 19, 2013, 10:25:50 PM
You will see it when it will be ready. Unlikely in the next few months.
#9405
At that time I didn't have a 5D2.
#9406
Um.. I meant both versions (you said the older one works better). Actually, try all 3 of them: 2.2, 2.3 and nightly.
#9407
That's a bleeding edge algorithm.

Can you do an apples-to-apples comparison (same camera, same lens, same subject, same exposure, both algorithms)? Also include the nightly algorithm, which was tweaked since the Jurassic era.
#9408
Status update: latest findings about RAW histogram will allow me to integrate this algorithm in ML. This means flicker-free ramping from 1/8000 all the way to several minutes of exposure. That's called holy grail, right?

Don't expect it overnight. I have all the ingredients for this, but putting everything together is not trivial.
#9409
Did you actually try it?
#9410
Screenshots please (parameters + test scenes).
#9411
Feature Requests / Re: RAW overexposure warning
April 18, 2013, 05:50:10 PM
Yes, if the channels are not all blown out, you can recover the highlights.

Here's the difference between RAW and JPEG histograms:

RAW histogram:


JPEG histogram:


So.. the JPEG histogram says the blue channel is really blown out, but the RAW one says you can push the exposure to the right by 1 stop without any problem (or even 2 stops if you don't mind blowing the green channel a bit). Let's try 2 stops:



And, of course, the RAW looks just fine (to me) when developed at -1.5 EV. Except for the bottom-right corner where recovery didn't work.



Also notice that, on the RAW histogram, you can see the exposure difference as a simple translation (and you can count the EV from the grid).

P.S. I've used the Landscape picture style (default settings). With Neutral, the difference is not that big.
#9412
The difference will be 1 frame more or less, so not worth it.
#9413
This is quite easy with a PicoC script.
#9414
Feature Requests / Re: Time lapse, like the D800?
April 18, 2013, 12:26:52 PM
Yea, just port ffmpeg on the camera ;)
#9415
Feature Requests / Re: RAW overexposure warning
April 17, 2013, 11:43:04 PM
Alright, now you have true RAW histogram and zebras. 5D2 only.

To use, simply choose RAW in Canon menu and set histo/zebra to RGB. No new menus - it should just work.

https://bitbucket.org/hudson/magic-lantern/commits/115f297ac7c8
#9416
No idea, the channels are camera-specific, and I've only looked at 5D2.
#9417
Feature Requests / Re: RAW overexposure warning
April 17, 2013, 05:10:29 PM
I've found the 14-bit RAW data, now trying to decode it. So... RAW histogram and zebras should work without too much effort for the last picture (not for the ones already taken, though).

The module system is not yet ready for low-mem cameras (need to strip all the TCC part and keep the elf loader only).
#9418
Overriding at fast shutter speed didn't work. For bulb ramping I can just tweak the ISO to account for 1/8 EV steps and remove most of the flicker.

The 14-bit data is gold mine for RAW histogram and zebras.
#9419
14-bit data found at EDMAC #10 (0x4000048) on 5D2 :)

[TTJ] START RD1:0x4000048 RD2:0x64d1864
#9420
SDSf3:(0)  --  3 sdsMem1toRAWcompress-->(1)

Here, parameter z from the state object routine is a memsuite; initial size (before the call) is 0x2880000 (42MB), after the call, it shrinks to around 20MB. I believe it contains lossless JPEG data (compressed RAW). Signature: FFD8FFC4 (huffman compression).

SDSf3:(1)  --  3 sdsMem1toJpegDevelop-->(1)

Here, z is again a memsuite, initial size is 0xb58000 (11MB) and it shrinks to around 500K. It looks like JPEG data (FFD8FFDB).
#9421
Camera-specific Development / Re: Canon 1100D / T3
April 17, 2013, 08:48:37 AM
It should be rewritten to use memory chunks, see g3gg0's test code. 50D also needs it.
#9422
General Development / Re: ROM Map
April 16, 2013, 10:52:29 PM
Quote
F0000000 - F0FFFFFF: eos.rom0
F1000000 - F1FFFFFF: eos.rom0_mirror_F1
F2000000 - F2FFFFFF: eos.rom0_mirror_F2
F3000000 - F3FFFFFF: eos.rom0_mirror_F3
F4000000 - F4FFFFFF: eos.rom0_mirror_F4
F5000000 - F5FFFFFF: eos.rom0_mirror_F5
F6000000 - F6FFFFFF: eos.rom0_mirror_F6
F7000000 - F7FFFFFF: eos.rom0_mirror_F7
F8000000 - F8FFFFFF: eos.rom1
F9000000 - F9FFFFFF: eos.rom1_mirror_F9
FA000000 - FAFFFFFF: eos.rom1_mirror_FA
FB000000 - FBFFFFFF: eos.rom1_mirror_FB
FC000000 - FCFFFFFF: eos.rom1_mirror_FC
FD000000 - FDFFFFFF: eos.rom1_mirror_FD
FE000000 - FEFFFFFF: eos.rom1_mirror_FE
FF000000 - FFFFFFFF: eos.rom1_mirror_FF
C0000000 - CFFFFFFF: eos.iomem
#9423
Feature Requests / Re: RAW overexposure warning
April 16, 2013, 09:47:57 PM
Idea: load a stripped-down dcraw as a module and run it on the CR2.

Problem: building the RAW histogram takes 3 seconds on core 2 duo (1.5s with O3). How long it could take on ARM? 30 seconds?
#9425
QuoteEnableMainFirm

That's for unbricking, not for enabling the boot flag.