Messages

I think it is better to cut 2 or 3 pixel lines/rows on top and left side.

Here is a link to problematic cr2 (waves in the center of the picture painted in the colors of the rainbow)
https://dl.dropboxusercontent.com/u/4624786/_MG_8792.CR2

It doesn't err70 anymore.

Cannot confirm that.

I think that pink highlights is a result of incorrect processing of clipped channels in some cases by cr2hdr.
"--force" option is needed because cr2hdr does not always detects that cr2 is interlaced. Option for reversed order of fields needed too.
One more comparison. No noise reduction (only "Remove dot noise" option), RPP. Aperture, shutter speed and processing settings are the same. Unbelievable clear shadows. (7D)
https://dl.dropboxusercontent.com/u/4624786/dual-iso_test2.1.jpg

Only this. It is a log from previous version
https://dl.dropboxusercontent.com/u/4624786/CRASH00.LOG
I'm leaving for two days now

Still hangs with Err70. First time I took 3 photos and got Err70, second time - 5 photos, third time - 3 photos.

I would only use it in photo mode for now, not live view.

I have no idea where to start to fix pink highlight problem.

I just take 1 to 30 pictures in photo mode and it hangs with err70 or card led lights and camera does not respond forever.
Pink highlights looks like a problem of cr2hdr because CR2's embedded jpeg-preview is ok.

Interesting...
For me it's worked like a charm. No hangout, no ERRxx, nothing.
Edit:
Yes, cr2hdr makes pink/magenta in the highlights in both situation (100-1600, 1600-100)

Tried again both versions of dual_iso.mo from last build. Same results - there are very unstable. ML works like a charm until I enable dual ISO module

After testing both versions for 3 hours I can say that their behavior looks like identical. All of them hangs camera like a hell. It is hard to take pairs of photos - one with dual iso and regular one. Camera very often throws Err 70. Removing battery helps. Also camera often hangs while saving dual-iso photo to card, switching to LiveView (with Dual ISO module "ON" of course).
Current version of cr2hdr does not works properly with default settings (Recovery ISO 1600). It returns DNGs with strange colors. But if I set recovery ISO to 100 and camera ISO to 1600 it works as intended.
Option "Dual ISO - Alternate frames only" was throwing Err 70 every time I tried it.

It works! Captured a dual-iso CR2 with "test build". Testing now. Thanks!

Try just the Dual_ISO module on the card first.

No luck
https://dl.dropboxusercontent.com/u/4624786/VRAM2.png

Boot time on 133x card is 3 seconds, 400x - 1 sec.

Successfully enabled bootflag and loaded Audionut's autoexec.bin. Bootflag on card should be enabled too. But modules are refusing to load.
Some screens
https://dl.dropboxusercontent.com/u/4624786/VRAM0.png
https://dl.dropboxusercontent.com/u/4624786/VRAM1.png
Any tips?

It is a CMOS temperature in some units.

@xmd5a how did you get your 7D to record for 90 minutes? 
I cant get my 7D to record longer than 12 minutes. Movie Restart feature seem not to work as well.

-Ray

You have to press record button again when recording stops.

My 7D stops recording after about 90 minutes of continuous shooting. The room temperature was 26 degrees Celsius.

REC/STBY - Beep doesn't work

Can not confirm that. Beep works.

"Limit bitrate to:" option is needed when shooting video in VBR mode. Otherwise if I have many cards with different speeds I have to change video settings. If invalid parameters are set then recording will stop. This makes bitrate manipulations unuseable. Also lack of this option limits safe ISO range due to excessive bitrate caused by noise and makes hard to determine this ISO for certain scene.

Found something strange. Audio meters in ML stops working after changing "Rec. level" in Canon audio settings (mode - Manual). Canon audio levels of course are working at that moment. Can't fix that without rebooting ML.

this bug only happens with features that were not enabled in this alpha.
so noone should have seen them.

what did you do when you encountered these bugs?

Got it. Trap focus leads to the fact that camera does not shuts down by "Auto power off" setting in canon firmware. Just load ML, take 1 photo with trap focus and wait longer than "Auto power off" is set. Camera will not power off for a very long time if not forever.

Before battery is over I took some tasklist screenshots. Here another bug: captured screenshots are named TEST.BMP without counter. So to view second and following images I have to rename them. This behavior probably can ruin card filesystem.
Here is my ML settings and these screens: https://dl.dropbox.com/u/4624786/ML_7Dalpha1_drain_battery_bug.zip
Hope this helps.

I see this problem right now. Autosleep is set to 2 min in canon firmware but camera does not went to sleep and red led does not blink like last time I caught this bug. What did I do: testing trap focus, recording short videoclips, looking at waveform and histogram in playback mode (picture style button), using SET+dial (exposure fusion up to 5 images). What can I do to diagnose problem before the battery runs out? Firmware alpha1, not bitrate monster.

no solution, as i cannot reproduce anymore
either its good or bad. i am not sure yet.

Maybe there is a way to implement full camera log (keypressings, camera state etc.)? I had this bug twice. Camera flashes by a card led one time a minute or so and drains battery.

I don't know why, but I can't open both your link

Correct link http://www.magiclantern.fm/forum/index.php?topic=3404.msg17691#msg17691

Noticed than Magic Zoom no more flickers. Also when REC/STBY notification is set to "Red Crossout" red box does not disappears properly when recording is started. Got a "dir error" message after Err70. "Flush rate" setting does not restores after reboot. True VBR feature is very useful.