Messages

When exactly?

In Av it can't bypass Canon limits (usually +/- 2 EV or +/- 5).

Yes, see the 7D thread, we want to release both updates at the same time. It will take a while, because we are a bit busy at work.

I still have some random issues like camera locking up on startup or not fully shutting down, so you'll have to take the battery out after each run.

If you have shot RAW, you can deflicker; if not... not.

You had shutter speeds faster than 1 second.

Works for me, just tried.

Preliminary conclusions:

- digital ISO affects the RAW data.

- it's not possible to leave the RAW unaltered and underexpose only the JPEG. Here's why:

Code Select Expand


SCS  :(6)  --  5 scsCapReady         -->(10) // digital ISO is overriden here
...
SDSf3:(0)  --  3 sdsMem1toRAWcompress-->(1) // RAW and JPEG are developed from the same memory area (MEM1)
SDSf3:(1)  --  3 sdsMem1toJpegDevelop-->(1)


- it might be possible to find MEM1 and build histogram on the RAW data when taking the picture

- highlight warnings can be used in LiveView (we can underexpose the preview there without altering the final image)

- it's possible to adjust ISO in very fine increments => flicker-free bulb ramping possible?

More info: http://www.magiclantern.fm/forum/index.php?topic=1915.msg23797

So... I'll disable this feature for now, but research continues. I'll try to make the warnings usable in LiveView only (non-invasive, and better than nothing).

The current (invasive) method can be still used if you are willing to throw away 2 bits of color depth and compile a custom dcraw/ufraw with modified clipping points (just divide them by 4). Worth the hassle?

From SCS state it's possible to override ISO in very fine steps.

e.g. MEM(0xc0f08030) = 1000 will underexpose by around 2 EV.

=> flicker-free bulb ramping for the entire shutter speed range is now possible?

It's right, green clips first. It's not true raw histogram, only the clipping points are correct.

[Don't use it for serious stuff; I've just noticed that it alters the RAWs too, not just the JPEG preview. It will remove 2 bits of color depth.]

Will be in tomorrow's nightly (5D2 only for now). It's quite tricky to use, and will underexpose the JPEGs by 2 EV.

Don't use it for serious stuff; I've just noticed that it alters the RAWs too, not just the JPEG preview. It will remove 2 bits of color depth. Was too good to be true

Quick HOWTO:
- Turn off peripheral correction.
- It needs calibration. Take a completely overexposed picture - it's used to compute the clipping points on the underexposed jpegs.
- Recalibrate every time you change pic style or white balance (but since you shoot RAW, you shouldn't need to change these).
- Use RGB zebras and histogram (the Luma ones won't work).
- Quick check: for overexposed pictures, the histogram peaks should align with the markers (if it looks strange, recalibrate).

Here's how it should look like:


And here's a sign that you should recalibrate (different WB, the peaks are no longer aligned):


Source code: https://bitbucket.org/hudson/magic-lantern/commits/174e18a5c3e5

For smooth ramping you need shutter speeds above 1 second.

Well... if you know what part of the image is overexposed, you can easily show the blinkies. And if you have access to raw data, you can compute the histogram too.

I have some ideas that might help with the blinkies part (JPEGs developed with -2 EV of digital ISO might be helpful).

Edit: yep, it's working on 5D2. For the impatient: MEM(0xc0f08030) = 500 in shootspy.c, stateobj_spy, and disable vignetting in Canon menu.

It's only in the nightly builds.

You can try with PicoC scripting; no idea how well it works on the M. You'll have to compile ML yourself.

Solved, try again tomorrow.

This was broken for two months and nobody noticed...

Post the log file.

See http://www.magiclantern.fm/forum/index.php?topic=1915 - no success yet.

You can try to port these (or just use them to save an IDC):

https://github.com/alexdu/ARM-console/blob/master/scripts/guessfunc.py
http://a1ex.magiclantern.fm/bleeding-edge/name_funcx.py

3. no, it's only for translating brightness to EV (it's reverse engineering the picture style on the fly).

3. calibrate it at home, or bring a flashlight.

4. choose a normally exposed picture, not a black one.

Correct, just pushed a fix for the 30-minute limit. Try again tomorrow.

How did you get that percentage?

Did you read that thread before posting?

Also, why opening a new thread on the same subject?

Disable the sticky half-shutter.

People who lack the most basic common sense are no longer welcome on this forum.

Here's a FAQ for you:
http://wiki.magiclantern.fm/faq?&#troll_questions