Magic Lantern for 7D alpha 2

Started by g3gg0, December 23, 2012, 11:30:14 PM

Previous topic - Next topic

0 Members and 3 Guests are viewing this topic.

arrinkiiii

Quote from: tonybeccar on July 20, 2013, 04:40:28 AM
I know some people are using the 7D with HIGH bitrates... does someone have like a comparison of the video with and without the better bitrate?? I've read that people are shooting in ALL-I and 20x CBR... that seems too much!!! I'm thinking of investing in high speed cards but I'm not too sure about it...

Thanks!

Hi @tonybeccar, did you find any video comparison between ALL-I and IPB and max CBR and low CBR ??? I went some pages back and didn't find anything.

arrinkiiii

Quote from: feureau on July 19, 2013, 01:54:59 PM
You know, if you compile ML for 7D and post it here, I bet some lunatic here has the balls to run it in their camera. Then we can take it from there...

Indeed !!!

pest01

Hi, I'm new in the forum and I would like to ask if there are any further improvements on the 7d. I understand that is hard to manage with a dual processor camera but I'm curious if there is anyone working on the 7d to solve the case with raw video , dual iso and maybe a next alpha release.   It seems that there's more interest on the rest of the cameras since its easier on development, especially now with all this amazing new features that magic lantern team has succeeded.

It's sad that all this year's such a great camera like the 7d had and still has problems on further development. I'm asking this because magic lantern's software for canon's dslr's is a must for film making and 7d doesn't seem to catch up with the rest. In this case what do we do, buy a new camera to benefit all the features that ML has to offer or hopefully wait for someone to figure it out?

Thanks ML Team for all the effort and time that they given for as!!

arrinkiiii

Quote from: pest01 on July 24, 2013, 03:24:28 PM
Hi, I'm new in the forum and I would like to ask if there are any further improvements on the 7d. I understand that is hard to manage with a dual processor camera but I'm curious if there is anyone working on the 7d to solve the case with raw video , dual iso and maybe a next alpha release.   It seems that there's more interest on the rest of the cameras since its easier on development, especially now with all this amazing new features that magic lantern team has succeeded.

It's sad that all this year's such a great camera like the 7d had and still has problems on further development. I'm asking this because magic lantern's software for canon's dslr's is a must for film making and 7d doesn't seem to catch up with the rest. In this case what do we do, buy a new camera to benefit all the features that ML has to offer or hopefully wait for someone to figure it out?

Thanks ML Team for all the effort and time that they given for as!!

Yes, it's all true. Better to buy a new camera. Nobody is able to continuous the work of g3gg0 on the 7D. Im waiting that anyone can make a compile version of the dual iso, and so far... nothing.  Im on the wrong profession... i should be a programmer  ;D


Evil Flip

yep, the RAWvideo thing kinda stole our thunder.

ygor

Audionut uploaded a build with Dual Iso module here: http://www.magiclantern.fm/forum/index.php?topic=7139.msg61623#msg61623

You can try if you're brave (he didn't test).
[size=8pt]Canon 7D | Canon 10-22mm f/3.5-4.5 USM | Canon 50mm f/1.8 II | Sigma 18-200 OS 3.5-5.6 | Canon 580ex II
Landscapes[/size]

mucher

I guess that I am one of those "luna"s.  I load Audionut's autoexec.bin with Alpha 2 into 7D, nothing happens. I mean really nothing, the ML didn't load into camera. I download everything in Audionut's 7D build directory and put them all in CF card's root directory. And start up the camera again. Nothing happens, again. I don't visually see that my camera is damaged neither.

Audionut

I assume the 7D needs a devkit first before being able to use these new builds.

arrinkiiii

Quote from: Audionut on July 25, 2013, 05:05:11 AM
I assume the 7D needs a devkit first before being able to use these new builds.

:(   Damn...

a1ex

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.

arrinkiiii

Quote from: a1ex on July 25, 2013, 05:51:38 AM
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.

Know i understand why not exist one compile version for the 7D... because it's not legal !!! Good to know the reason  :D

...but still, went to see the link but can understand  how to do it  :-\    ...maybe Audionut can put a version with the bootflag and dual isso in one folder  that you just need to put in the CF card and tries out this wonderful feature in the 7D  ::) 

Not a programer but i can be a tester !!!

xmd5a

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?

xmd5a

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

Audionut

Try just the Dual_ISO module on the card first.


pfluger

I finally managed to get autoboot working. I thought it might help someone if I shared roughly the steps I took:

- Get the 7D 1.23 firmware file (7d000123.fir) and patch per the instructions at http://www.magiclantern.fm/forum/index.php?topic=3974.msg58898#msg58898

- Flash this patched firmware file using EOS Utility. I used a very old 2.8.1.0 version of EOS Utility. I got an error (something like cannot write to media  card). I could work around it by putting the 1.23 fir file on the CF card and then starting the firmware update with EOS Utility. It still showed the error message but then started the firmware update using the .fir file I copied manually. I recommend using an empty CF card.

- Take the CF card out of the camera.

- If the flashing was successful you should see a couple of new files on the CF card (named something like ROM...bin). You can delete them.

- Copy the ML folder from the 7D Magic Lantern Alpha 2 to the CF card. Copy the autoexec.bin to the root folder of the CF card.

- Download the EOScard utility. You can find a link at http://wiki.magiclantern.fm/3rd_party_software

- Enable the EOS_DEVELOP and BOOTDISK flags (not sure if EOS_DEVELOP has to be enabled, but it didn't work without it for me)

- Put the CF card back in and start the camera. You should now be able to access Magic Lantern as usual by pressing the trash button.

Disclaimer: These steps worked for me, but I take no guarantee these will work for you :)

Audionut

Quote from: xmd5a on July 25, 2013, 11:31:01 AM
No luck
https://dl.dropboxusercontent.com/u/4624786/VRAM2.png

Pretty sure those errors are relating to raw.c, and this won't be included for 7D as it doesn't do raw video.
Or,

#undef FEATURE_EXPO_ISO_DIGIC  // not working, no idea why ->  test on master?

I've removed that line from features.h and it appears to have compiled fine.

You can try the updated build here  https://www.dropbox.com/sh/yp6dl9i104i1j2g/9Ta_9074YP

Big Fat WARNING
I have no idea of the consequences of my changes to the code.  I don't have my own 7D to brick first.
And to be honest, I think the problems are more related to raw.c then anything else.  The build is there for you to try and if are feeling brave.  But it comes with no warranty.

Pelican

EOS 7D Mark II, EOS 7D, EOS 5, EOS 100 + lenses (10mm to 300mm), 600EX, 550EX, YN600EX x 3
EOScard, EOS DSLR firmwares, ARMu, NiControl, etc.: http://pel.hu/down

feureau

Quote from: Pelican on July 25, 2013, 01:30:04 PM
Same error with the new version.


Hey, Pelican. Can you add this build to use with the EOS card please? :D

Pelican

Quote from: feureau on July 25, 2013, 04:37:09 PM
Hey, Pelican. Can you add this build to use with the EOS card please? :D
If somebody can produce regularly nightly builds on a constant link (like Nanomad do with other cameras) then I will set EOScard to use that link.

Edit:

Also, if someone could provide compiled modules then EOScard can install them too.
EOS 7D Mark II, EOS 7D, EOS 5, EOS 100 + lenses (10mm to 300mm), 600EX, 550EX, YN600EX x 3
EOScard, EOS DSLR firmwares, ARMu, NiControl, etc.: http://pel.hu/down

tonybeccar

YESSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!! :D :D :D :D :D :D :D Will test it tomorrow as I don't have my camera with me!!! THANK YOUUUUUUUUUUUUUUUUUUUUUUUUU!!!!!!!!!!!!!!!!!!!!!!!!!!!! Hope everything works fine! And oh my, the new menu!! :)

Audionut

Quote from: Pelican on July 25, 2013, 01:30:04 PM
Same error with the new version.

I've reverted a1ex's auto recovery option which I think will fix that error.

Updated build https://www.dropbox.com/sh/yp6dl9i104i1j2g/9Ta_9074YP

I'm confident it's going to get stuck on wanting DxO results, but I need to see what error message it's spits out after my last changes before I play with more changes.

edit:  There's an updated module in the test build folder in the above link you can try.  Not sure if you need to update the bin file, but I've included it anyway.  It's an ugly hack to the module which will be missing menu entries (dynamic range gained - midtone overlapping), but if it works!

xmd5a

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

oli4h

Hi folks,

Any chance to get a "ready to use" file - even with needs of reloading at each start?

wbr

mucher

I have no luck with Audionut's latest build @reply 721 neither.