Tragic Lantern for EOS M

[gary2013]

 

[1%]

There is "logically" something wrong with how ML handles the info from this lens.

Probably ML is using some memory area that canon wants to use and some task/process hangs.

I'd say sure, use ANYTHING better and chuck it in the bin but this lens comes with a lot of EOS-Ms and/or costs like $150+.

[AnthonyEngelken]

the forum is here for "all of us" to help fix and test things for ML. NOT to debate about who's lens is better. There are plenty of other forums to have those pissing contests.

Sorry, just got off topic; my apologies.

[gary2013]

 

[gary2013]

 

[gary2013]

 

[1%]

Not sure, I can try to figure out the USB bug, maybe its related to the same thing. I had this on 6D where something wasn't patched right and wifi/usb would lock up on 112.

[gravitatemediagroup]

sorry if I missed this in a previous post,  am I supposed to delete another file when adding the DuelISO mod. 
I'm assuming it went in the mod folder, or does it go on the root? 

[Malakai]

Just had a thought. I never noticed the 18-55 efm shutter bug when i was loading the firmware via FW menu. Before the bootloading version. Perhaps there is something during bootloading that is causing the problem.

[nanomad]

@1%: What boot method are you using on the M?

[Malakai]

@1%
I just noticed in post #248 you managed to up a new autoexec file that fixed the bug for jupiter55. I tried that autoexec on the latest bootloading version but i just get flashing sd light and have to pull the battery to reset.

[Canon eos m]

I hate to bother the devs with my trivial problems but I'm so excited to try dualiso that i had to post . I have the module working but im on a mac and the build of cr2hdr that i compiled from the ML source isn't working. I know 1% posted a windows binary, so I pulled it up in my wine, however, the dcraw 9.19 isn't running under wine. Is there a trick to compiling it correctly? Am I using the wrong source?

You guys rock

Edit: tried building form TL-6D tree, too. same error...

Edit: so i got it a dcraw.exe 9.19 (http://www.centrostudiprogressofotografico.it/en/dcraw/) working in wine, but i still get the same error as i would running the native built one: Interlacing method not supported

Hi, I downloaded dcraw 9.19 but did but no relief. The dual-ISO photo will not convert with cr2hdr.exe.

[Malakai]

Can ML do HDR h.264 video? Ive been using the Film Picture style but if i could get HDR too that would be fantastic!


Edit: found it

[1%]

@1%: What boot method are you using on the M?

6D method. I have to double check restart address and the 2 locations but it looks right. It uses malloc for bvram but without it the kit lens still locks.

Before the bootloading version.

It was still booting the same just exploiting the FW menu first to restart.

[tetsu]

A totally unrelated question. I´ve been using the EOS M for timelapses and the intervalometer is one of the best ML features for me.

Is there a way to disable the liveview while taking photos on the EOS M using the the intervalometer of ML? I cant find a way to turn the liveview off, and the screen drains the battery so fast specially when doing timelapses.

[Canon eos m]

So maybe false alarm about the video:

9-2-CR2hdr-Raw2dng-EOSM.zip (72 KB)
https://mega.co.nz/#!5sRilQJb!bs1pIFbAFwxt7unCkIl3wm2VQbIyhn9fbXB_rsC-auQ


These are correctly built cr2hdr.exe and raw2dng.exe.. you need your own dcraw (9.19 is the latest) and exiftool.

Still says black subtraction failed but the files are coming out... I had lots of trouble using "other" versions. Dunno if you'll have all the libraries, built on mingw + mysys system win7x64.

Hi 1% please teach me to extract dual iso CR2's from the EOS M to dng.

[1%]

I don't think you can disable the screen completely. Power save with the shortcut might black it out, just set a dim/off value too and then hit info.

Post a Cr2, the utility worked for me on both LV and photo.

Another attempt to fix the lens issue, change boot to copy and restart. It doesn't fix the USB but try with the kit lens:

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/EOSM-COPY.zip

[tetsu]

I don't think you can disable the screen completely. Power save with the shortcut might black it out, just set a dim/off value too and then hit info.

Post a Cr2, the utility worked for me on both LV and photo.

Another attempt to fix the lens issue, change boot to copy and restart. It doesn't fix the USB but try with the kit lens:

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/EOSM-COPY.zip

I´ve tried, it worked the fist time then after restarting the camera locks up i have to remove the battery to boot it again. Do i have to flash the firmware again? There´s a EOSM_202.sym on your zip file, I dont know if i have to change the extension to fir.

[zuzukasuma]

I´ve tried, it worked the fist time then after restarting the camera locks up i have to remove the battery to boot it again. Do i have to flash the firmware again? There´s a EOSM_202.sym on your zip file, I dont know if i have to change the extension to fir.

EOSM_202.sym' is for putting in to ML\modules folder

carl.

[tetsu]

EOSM_202.sym' is for putting in to ML\modules folder

carl.

thanks, now i can´t shoot pictures even after turning it off then on quickly, reverting to previous version.

[zuzukasuma]

thanks, now i can´t shoot pictures even after turning it off then on quickly, reverting to previous version.

new version doesn't require such action like flash reboot.

[1%]

It didn't have any problems like that unless stuff is copied to wrong locations... but if the lens still doesn't work its not the boot method.

[gary2013]

 

[1%]

So the boot method isn't the problem.. with copy and restart it lets you come back from that sensor cleaning but still not shut down... I'd log it but at that point logging doesn't work... you can't touch shoot mem or stack space and they are 0.

[tetsu]

new version doesn't require such action like flash reboot.

i mean that the problem is still present, and even with this version i cant seem to shoot anything.