Magic Lantern for 7D alpha 2

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

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.


inky38

Ok I hate to do this, but I'm going to ask a Noob question that others have also asked, but answers have yet to be provided that can help me.

Where the heck is the Silent Burst Sub menu.  Have looked through every menu under SHOOT, but can't find it. Have I got to enable something first or do I have to add an extra module, if so, where can I get it?

For info, I loaded ML onto my bootable 7D using Pelicans 1.38b EOSCard (August 3rd).   Dual ISO and File manager modules load ok.

jemabaris

Quote from: inky38 on August 04, 2013, 04:38:00 PM
Ok I hate to do this, but I'm going to ask a Noob question that others have also asked, but answers have yet to be provided that can help me.

Where the heck is the Silent Burst Sub menu.  Have looked through every menu under SHOOT, but can't find it. Have I got to enable something first or do I have to add an extra module, if so, where can I get it?

For info, I loaded ML onto my bootable 7D using Pelicans 1.38b EOSCard (August 3rd).   Dual ISO and File manager modules load ok.

I already answered that question in the other thread, but here once again


"download the following two files:

http://pel.hu/ML/autoexec.bin
http://pel.hu/ML/7D_203.sym  (right klick and save link)

find those two files in the ML folder on your CF card and replace them.

you will find the burst in the "shoot" tab.

good luck"

Haruki

Quote from: jemabaris on August 04, 2013, 04:49:17 PM
I already answered that question in the other thread, but here once again


"download the following two files:

http://pel.hu/ML/autoexec.bin
http://pel.hu/ML/7D_203.sym  (right klick and save link)

find those two files in the ML folder on your CF card and replace them.

actually, autoexec.bin goes to the root and not /ML

jemabaris

Quote from: Haruki on August 04, 2013, 04:53:16 PM
actually, autoexec.bin goes to the root and not /ML


I have never said that...

I wrote to replace the two files. for my understanding that means leaving them where they are, but maybe thats just me.  :D


i just read what i wrote again and yes,you are right :D it´s not all that clear. my bad

inky38

Quote from: jemabaris on August 04, 2013, 04:49:17 PM
I already answered that question in the other thread, but here once again


"download the following two files:

http://pel.hu/ML/autoexec.bin
http://pel.hu/ML/7D_203.sym  (right klick and save link)

find those two files in the ML folder on your CF card and replace them.

you will find the burst in the "shoot" tab.

good luck"

Ah my bad.   I assumed that the latest build retrieved using EOSCard.exe would have included that.

All working fine now

Cheers

baumrasen

hello again,
Quote from: angelom on August 04, 2013, 02:45:42 PM
There's another user with a problem while using a CF adapter, after he moved to a CF card no problem at all so it seems that CF adapters are not a good choice when used with ML.
OK, thanks. I will give it a try.

cu
baumrasen

jphansen

Yep v. 1.38 works.. I love you guys.. Such a great job you guys do.. BTW.. love the new GUI :-)

hypermobile

i assume there is no way i can put those 2 files on my CF-Card with the 7D itself...?!?!

my Cardreader...just passed away..rip AARG(^^%$&&*(*(* >:( >:( >:(

Pelican

I've made a new patch file which works with the same 1.1.0 fw but creates a 2.0.3 fw update so you can skip the EU part...
http://pel.hu/ML/booton.bsdiff
Use the same way as the previous patch.

Also I made another patch which disables the bootdisk flag on the 7D so your camera goes back to the 'normal' state when doesn't load autoexec.bin at every start
http://pel.hu/ML/bootoff.bsdiff
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

edingacic

Quote from: Pelican on August 04, 2013, 07:33:28 PM
I've made a new patch file which works with the same 1.1.0 fw but creates a 2.0.3 fw update so you can skip the EU part...
http://pel.hu/down/bootpatch203
Use the same way as the previous patch.

what do you mean by skip the EU part?

arrinkiiii

Quote from: pit3k on August 03, 2013, 09:28:55 PM
Does it work?

The ETTR module just load fine, i turn it on in ML menu... then i didn't try anymore how to figurout ETTR works.

The module autoexpo module didn't able to load.

What is the big differences from the last nightlybuild (4 august)?

feureau

Quote from: arrinkiiii on August 04, 2013, 08:12:48 PM
The ETTR module just load fine, i turn it on in ML menu... then i didn't try anymore how to figurout ETTR works.

The module autoexpo module didn't able to load.

What is the big differences from the last nightlybuild (4 august)?

Nothing big. Just minor fix and typo.

Also, ETTR for anyone interested: http://www.mediafire.com/?wkbc2nwiz3p9g6r

Pelican

Quote from: edingacic on August 04, 2013, 08:04:51 PM
what do you mean by skip the EU part?
You don't have to download, install, run EU just skip the whole thing.
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

pre10dr

EU = Eos Utility , as far as i understood pelican he build a version of the patched firmware which enables bootflag WITHOUT needing to push the update via eos utility.

I appreciate the work all the pros do here but sometimes I would like to see less use of (not commonly used) acronyms. There are newcomers out there who will not understand all these terms and it will take longer to explain them afterwards then doing it in more detail first.

crazyrunner33

Quote from: feureau on August 04, 2013, 08:46:11 PM
Nothing big. Just minor fix and typo.

Also, ETTR for anyone interested: http://www.mediafire.com/?wkbc2nwiz3p9g6r

Thanks!  RGB Zebras work now, I wish I would have waited for I went out to test RAW in crop mode.
5D Mark III, 7D

edingacic

Quote from: feureau on August 04, 2013, 03:26:26 PM
August 4 build:

http://www.mediafire.com/?z4ogo4t7atb1zow

Thanks works great I used to have this scripts folder not found now it is fixed. 

danistuta

I've got Alpha 2 copied on my Compact Flash. How can I upgrade to this version?
Please could you explain steps to use it?
Thanks.

jalejake

Quote from: Pelican on August 04, 2013, 09:00:19 PM
You don't have to download, install, run EU just skip the whole thing.

Did I get this right.. with these two patches I can make firmware "update" files for the 7D,
I can rename the files to for example "7D_203_booton.fir", and "7D_203_bootoff.fir", and with the firmware update function INSIDE my 7D, I can now switch the bootflag on and off without a computer? Can I have the two files on my card simultaneously to be able to do this switch on the go too?

danistuta

Two question:
- Is there a way to use last  firmware (with raw video) witohout enable autoboot?
- I've got Canon 2.0.3 firware installed...is this the correct procedure? http://www.magiclantern.fm/forum/index.php?topic=3974.800
- Once do it, which firmware is on my 7d? 1.2.3 or 2.0.3? Possible disable autoboot ML and use camera in normal mode with 2.0.3 firmware?
Thanks

Pileot

Quote from: pre10dr on August 04, 2013, 09:35:32 PM
EU = Eos Utility , as far as i understood pelican he build a version of the patched firmware which enables bootflag WITHOUT needing to push the update via eos utility.

I appreciate the work all the pros do here but sometimes I would like to see less use of (not commonly used) acronyms. There are newcomers out there who will not understand all these terms and it will take longer to explain them afterwards then doing it in more detail first.

Sorry if im slightly slow on the comprehension here but basically what your saying is we make the firmware.fir file, put it on the SD card, then run EOScard (the latest one, 1.38b) and eoscard does everything from there, no need to update the camera firmware?
How does the camera bootflag get set?


britom

You just have to patch the original 2.0.3 firmware with the files provided by pelican using the bspatch.exe utility from my guide. Then you put the .fir file in the cf card and select firmware update so we dont have to use EOS Utility anymore to patch the older 1.2.3 version of the patch.

The only thing this does is to enable the bootflag so you can load autoexec.bin version of Magic Lantern. Your camera will still run 2.0.3 firmware after this.

I can edit my original guide if anybody wants, but some guy made a more detailed guide in a new thread so he should update that one.
7D Builds with RAW support: http://bit.ly/14Llzda

LiFou

Quote from: flofifull on August 04, 2013, 12:00:50 AM
I did some quick tests in my garden with silent pics burst this afternoon. ;)
https://vimeo.com/71649487



Hi! Im new i the ML because i just found out that my 7D can do RAW video. What do I need to record a RAW files? I just try it but it recorded only some *.422 files and no RAW files. I'll be happy for any answer or ling to some answers :)

Pileot

Quote from: britom on August 05, 2013, 12:32:47 AM
You just have to patch the original 2.0.3 firmware with the files provided by pelican using the bspatch.exe utility from my guide. Then you put the .fir file in the cf card and select firmware update so we dont have to use EOS Utility anymore to patch the older 1.2.3 version of the patch.

The only thing this does is to enable the bootflag so you can load autoexec.bin version of Magic Lantern. Your camera will still run 2.0.3 firmware after this.

I can edit my original guide if anybody wants, but some guy made a more detailed guide in a new thread so he should update that one.

So generate firmware.fir
put on card
in camera do firmware update
then use EOScard to get latest MagicLantern on your card OR download the files manually and place on card

missing anything?

Im "some guy" and wanna make sure im 100% clear on the steps before I try to advise people to do something different. Will have the other thread updated right away.

Can we change the steps so we generate the firmware.fir file, run EOScard, and THEN move firmware.fir onto the card? Then update the camera through firmware update in the camera menu? Or should we run the update before EOScard? (meaning we would have to plug the card from the computer to the camera to the computer and back to the camera agin)

britom

That should do, but might be necesary to rename firmware.fir so the camera recognizes as a update. Or probably not, magic lantern alpha 2 is named magic.fir and it works.

Haha Sorry i didnt recognize you and thank you by the way.

I think the order can be changed, just keep in mind that the camera will read the autoexec.bin file only if the bootflag is enabled. I think is more practical like this: Patch firmware file > Prepare CF card (Copy firmware file and magic lantern) > Firmware update. Camera should turn on with ML. It should work but someone needs to try it first.
7D Builds with RAW support: http://bit.ly/14Llzda