Messages

You can check the timer value periodically with get_ms_clock_value.

Or, for your case:

int aux = INT_MIN;
if (should_run_polling_action(10000, &aux)) ...

This call is not blocking, so you can use it from vsync without pausing LiveView.

Canon deletes these files if you reboot the camera before clicking delete (at least on 5D3).

It shouldn't be hard to implement this.

On Linux I run cr2hdr *.CR2

No idea if this works on Windows, but try it.

Well, I'd use 13000 or higher. If there are no burned areas, the only side effect should be picture being a little brighter than normal, and maybe a few clipped pixels (and highlight recovery should catch them). If there are burned areas, it will use the true white level.

Right now, auto exposure won't work in raw video, because the digital ISO gain is not applied to raw data.

But if you include the post deflicker algorithm in raw2dng, you may even get something usable. Worth trying IMO.

dcraw uses 13584 (hardcoded). And yes, since the white points changes with ISOs, it makes things difficult; for now, I just use the smallest value from burned areas, if it's above 10000. Probably a bit overkill, maybe 13000 should be a better starting point?

What camera and ML version?

(tried it on 5D3, worked just fine)

[raw files (*.CR2 or *.RAW).]

Updated the converters (download from first post):

cr2hdr:
- fix memory leak, tested with 100 GB of pictures
- white level autodetection (should fix pink highlights)
- exiftool fix from jpaana, not tested but looks OK

raw2dng:
- fix memory leak, not tested (should be OK with large clips)

I did not address the black level issues yet.

If you are having issues with image quality, please upload the raw files (*.CR2 or *.RAW).

I don't use After Effects, but here's a plugin that does it in VirtualDub: http://bit.ly/frame-merger

or grab your C compiler and modify raw2dng to average all the video frames and output a single DNG. Or, average every X frames and output a DNG sequence with less frames. I'm sure others will find it useful.

There is a working build for the 7D in the 7D alpha2 topic.
The produced files (ISO 100/1600 and ISO 1600/100):
http://pel.hu/down/100_1600_7D.CR2
http://pel.hu/down/100_1600_7D.DNG
http://pel.hu/down/1600_100_7D.CR2
http://pel.hu/down/1600_100_7D.DNG

In these files, the white level is close to 13000; in my 7D test sample it's 15382. Normally you get these values with intermediate ISOs (160, 320).

If you change the white level in cr2hdr.c to 13000 instead of 15000, these files will be converted without pink highlights. Now trying to figure out how to get this value from exif or what settings to use to get raw values higher than 15000.

For very long exposure, recording at 1fps or so and averaging the frames in post should do the trick.

With this, you will also get better dynamic range (for example, when averaging 16 pics, the standard deviation of the noise should be 4 times lower, so you effectively get 2 stops of extra DR if I'm not overlooking something).

Bring a power adapter and enable the intervalometer. Let us know if it works

On battery it will last around 10 hours, in standby.

Yeah, use the menu and find the safe timer values.

I've posted a link above.

Looks OK. Not sure what else to try, so just play with partitions, cluster size and stuff like that.

Where's the /x ?

Screenshot please.

If you use a DOS prompt (command.com, not cmd.exe) and list the files, do you see AUTOEXEC.BIN?

Or, in cmd.exe, try dir /x (it should show AUTOEXEC.BIN, but it should not show long file names).

Does the camera boot when the card is bootable?

Yes, there is difference if you format the card on PC. Maybe cluster size or other stuff like that could make a difference (even creating a smaller partition is worth trying).

Did you try formatting it as FAT32?

http://discuss.howtogeek.com/t/how-can-i-format-a-128gb-usb-stick-to-fat32/3934/2

See this for how to enable the bootflag: http://www.magiclantern.fm/forum/index.php?topic=3974.msg58898#msg58898

The only issue is that one can't legally distribute that FIR file, so you must create it yourself.

The safe timer limits need to be adjusted (35fps is too much). Adjust the timers manually and see when the image gets restored.

Upload a sample.

For 550D, the address for ADTG function is at 0xff27ee34, and for CMOS, 0xff27f028.

I didn't try these numbers, and I have no idea how Indy got these RAM addresses. Afaik, the 550D runs all the code from ROM (but there may be exceptions).

I'm already getting over 120 MB/s in camera with Komputerbay 32GB 1000x (file write benchmark in playback mode, where most Canon tasks are idle). Actual recording speed: 109 MB/s at 24p.

FYI, 1000x means 150 MB/s, http://en.wikipedia.org/wiki/CompactFlash#Speed .

Just tried mine (Komputerbay 32GB 1000x): at 2560x1090 23.976 it records around 1000 frames (estimates 1500). Will try to fix that (the buffering algorithm should really get 1500 frames, but it's stopping early).

Writing speed is around 109.5 MB/s (minor drop at the 4GB barrier). With exfat there should be no drop.

At 2560x1280 I get around 200 frames (both real and estimated).

Settings: 23.976, global draw on, no overlays enabled, all hacks from raw submenu enabled.