Messages

You can combine it with FPS override. The current nightly may not sync correctly, but the next one will.

Small update, just added some cool stuff to the repo:

- silent burst mode working on 5D2 and 3 (roughly 30 pics at LiveView FPS and resolution)
- raw histograms and zebras are now showing the dynamic range from DxO

If you look at the uncompressed 422 recorder, you'll notice that 1920x720 is doable on the 1000x card. It's not working yet for raw, but the frame sizes are comparable (2741760 bytes for a 1904x720 YUV422 frame, vs 2399040 bytes for 2080*720 RAW).

I've also reworked the raw code to make it easier for porting - all camera-specific stuff is now in raw.c. The porting process goes roughly like this:
- add raw.o and chdk-dng.o to camera Makefile (in platform dir)
- read the comments from raw.c
- fill in the "blanks" in raw.c (look for #ifdef CONFIG_5D2/5D3 and add similar blocks for your camera)
- most values are found by trial and error; it's not hard, but it takes time
- enable the raw features in features.h (look at 5D2/3 for valid names)
- enable the debug stuff for testing / troubleshooting (RAW_DEBUG, RAW_DEBUG_DUMP, RAW_ZEBRA_TEST etc)
- probably the easiest one to port is FEATURE_SILENT_PIC_RAW (simple, not burst). After this is working, try burst. Finally, try the photo mode overlays, these are the hardest to get right.
- submit a pull request (or just paste your modifications here)

Enjoy!

Yes, see chdk-dng.c

Exposure override enables the aperture.

For buttons, I'm thinking at some way to tell in advance what buttons will be used by the script, so it will capture only those. Something like: setup_keys(SET, MENU, LEFT, RIGHT).

Just take normal pics and enable silent mode in menu.

Yes, look in bootflags.c. No idea about DMA on the cards; for that, one has to investigate the low-level file i/o routines.

I only scratched the surface and "fixed" a compatibility bug with certain cards on 5D3 (well, only a dumb workaround, but works for my kingston 266x): http://www.magiclantern.fm/forum/index.php?topic=2528.0

Module support is not yet mature, but it's the way to go for low-mem cameras. Not right now, but in the future.

For burst: Luke's video at 1:25. Don't expect everything overnight.

You will also need to copy the color matrix and white level from dcraw. It will also work with 5D2/3 values, but colors may be a little off.

For white level I'm thinking at some autodetection, because it seems to vary from camera to camera and also with ISO and shutter speed. Maybe hardcode it as around 13000, and auto increase it if there are pixels brighter than that. Better ideas?

I'm also trying to reorganize the code a bit, so the DNG converter would be completely platform-independent (without camera-specific constants, so we can load it as a module), and also I want to add macros for converting pixel coordinates from screen to raw image buffer (e.g. BM2RAW, LV2RAW etc). So I won't enable it on the other cameras right now, but I'll do it once the implementation will be a bit cleaner.

Feel free to experiment with it.

Watch Luke's video (with sound!) to find out.

Answer is here: http://nikonhacker.com/viewtopic.php?f=2&t=684

and in the sticky topics.

Look for AE_VALUE in consts.h. I couldn't find it on all cameras.

Not really, width is hardcoded to 2080. I may be able to crop the height, but I can't control the buffer size yet.

Continuous recording is a lot harder than short bursts, and right now it's beyond my skills, sorry.

The nightly seems broken, use this link for 5D2 until it's fixed. For 5D3 you need to compile yourself for now. The user-friendly installer still needs some work, so you have to use the developer kit and understand what you are doing. I'll look into it these days.

Some things to clear up:

- It doesn't save CinemaDNG, but just plain DNG, copied from CHDK. They have been doing this for years.

- This will not improve rolling shutter at all.

- Don't hold your breath for raw video. 24fps at 1080p is unlikely IMO, even on 1000x cards.

- HDMI out doesn't help. Here's why: raw image buffer vs recorded with hyperdeck shuttle uncompressed. Ignore the overlays.

- In continuous mode I've got 4fps of raw data (not DNG, just the raw image buffer) on a 266x card. G3gg0 got 12.5fps of YUV422 video on the Lexar 1000x card.

- I was able to record around 30 frames in burst mode, at LiveView FPS (24, 25, 30, 50, whatever). It takes roughly 1 second of "recording" to RAM and then half a minute of saving the DNGs to card.

Nevertheless, I find this very useful as a fast burst mode for stills, or when you want to save shutter clicks or just avoid noise.

Luke Neumann already tried this stuff and made a short video.

http://neumannfilms.net/2013/04/27/14bit-raw-video-on-canon-dslrs-with-magic-lantern/

Extreme vignetting is already done btw.

Yea, just crop it. Since I don't know how to autodetect the image height (other than hardcoding the image resolutions), I've just assummed a 2:3 ratio.

I've also tried with dcraw - opens fine. Not sure what's wrong.



dcraw.tiff

It opens just fine with ufraw here.

Grep is your friend.

http://www.codecoffee.com/tipsforlinux/articles/25.html

With the raw spotmeter you can read the brightness in stops. It's not yet accessible from scripts.

We can't even be certain if it's the final one, so just be patient until Canon publishes it.

There's a debug flag (lv_save_raw) that enables this. Coutts found it a few months ago on 6D, but back then we had no clue what it could be or how to decode it.

So, the missing piece from the puzzle was the 14-bit decoder from the raw histogram experiments, and the location of the LV RAW buffer (visible right away once g3gg0 understood how EDMAC works).

The DNG encoder from CHDK worked pretty much out of the box.

I'm now trying to sync FPS override with shutter speed, so you can take slow exposures too.

For simple stuff you can use bmp_printf. For more complex logs, I use dm-spy and DryosDebugMsg.

Or, custom logging code like this: http://www.magiclantern.fm/forum/index.php?topic=1915

There's no nightly for the 5D3 yet...

You can just count the stops till overexposure on the histogram, or read the spotmeter, and then count the clicks on the shutter speed dial. So if your test picture is underexposed a bit, you can tell at a glance how many stops you have to adjust.

Thou shalt not attempt to run Magic Lantern without reading the manual

http://www.magiclantern.fm/bestpractices

http://wiki.magiclantern.fm/faq?&#troll_questions