Messages

Tragic lantern 6D has eosm 2.0.2 and the built module should work on both. We just turned off the bit that makes it do 8 lines instead of 4.

roger, got it. thanks.

Dual iso from this should be convertable... dunno how the video will do.

https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/dual_iso.mo

yup, works like a charm! congrats. Could you commit this to the 700D module too?


thanks,
-Christian

EOSM has the same problem.

I have the impression that they're not using HHllHHll, but rather 4 each. I haven't understood cr2hdr's code sufficiently in order to propose a fix yet, though.

while we're at it: is there a current M repo I could check out and compile? tragic lantern doesn't seem to be it...

thanks,
-Christian

@funkysound: thanks, but I'm not looking for binaries (I have ML running on my M), but for a way to compile it myself

@feureau: oh, I wasn't aware of the tragic lantern fork. I just cloned it, but it also seems to be for 1.0.6 and no, I can't compile it either. Thanks for the hint!

could anyone please tip me off on how to compile ML for EOS M 2.0.2? I have the toolchain and everything and can compile it just fine for my 700D, but the EOSM target in the unified branch seems to be for the 1.0.6 firmware. How do I get an autoexec.bin for 2.0.2?

thanks a lot,
-d

has anyone here been successful in getting any useful dual-iso shots from the 700D? cr2hdr doesn't even convert them, complains about the interlacing method not being supported. It seems to me that the 700D has another line interleaving scheme than the 5Dm3. cr2hdr reports "BddB RGGB" for the 5Dm3 and "BdBd RGGB" for the 700D. Page 5 of dual_iso.pdf talks about an interleaving pattern of l,l,H,H,l,l,H,H... for the 5Dm3, but I think the 700D uses something like l,l,l,l,H,H,H,H,l,l,l,l,H,H,H,H....
To illustrate, I cropped the first top left 32x32 pixel out of a 5Dm3 and 700D CR2, respectively:



Needless to say, current cr2hdr interpolation algorithms do not like this.

any ideas?

thanks,
-Christian

the 700D definitely has another line interleaving scheme than the 5Dm3. cr2hdr reports "BddB RGGB" for the 5Dm3 and "BdBd RGGB" for the 700D. Page 5 of dual_iso.pdf talks about an interleaving pattern of l,l,H,H,l,l,H,H... for the 5Dm3, but I think the 700D uses something like l,l,l,l,H,H,H,H,l,l,l,l,H,H,H,H....
To illustrate, I cropped the first top left 32x32 pixel out of a 5Dm3 and 700D CR2, respectively:



Needless to say, current cr2hdr interpolation algorithms do not like this. I'll look into this some more, but maybe someone has some input already?

-d

Check your ver of dcraw. I had no issue with 600D, 700D can't test.

latest 9.19 in Fedora 19. Also, the "BdBd - Interlacing method not supported" is from cr2hdr, not dcraw. I'll have to dive into cr2hdr.c as soon as I find the time.

I'm having similar issues with a dual iso test shot from my 700D:

Input file     : /tmp/IMG_5884.CR2
Full size      : 5280 x 3528
Active area    : 5208 x 3476
White level    : 13482
Black borders  : 72 left, 52 top
Black level    : 1982
ISO pattern    : BdBd RGGB
Interlacing method not supported
ISO blending didn't work


according to the source, BdBd means is_bright[0] && is_bright[2], so maybe the 700D uses another interleaving than other cameras?

cheers,
-d

Darn, followed the instructions and got further but I'm getting a "missing symbol file b:/ML/Modules" error right after the firmware update screen pops up.  I checked and I have the EOSM_202.sym in the folder. What am I doing wrong here?

I had this problem too: you need to copy the modules directory into the ML directory, not on the root level.

-Christian