Messages

Nevermind, Walter Schulz saved me in another thread.

Ok, I don't understand exactly why that worked, but it did, so thanks Walter Schulz!

Does this mean I am free from needing to ever use MacBoot again?

I should have clarified:

I've already got ml installed on the camera. I've been using a nightly build from April. I am traveling right now and don't want to deal with the 114 firmware update so I was planning on using this older nightly build for now. I recently got new 64gb cards and when I went to format them with ml I found that MacBoot would not recognize them. Then I went back and tried to reformat some of my older cards and still, MacBoot will not recognize that they're connected.

If you look at my other posts I made another thread last night which contains the debug results from MacBoot.

Hello,

Turndog did you get it to work?

I'm experiencing a similar problem in Yosemite with a 700D.

When I run MacBoot it refuses to recognize that I have an sd card connected. It just returns no suitable cards.

Please help!

I am trying to prepare my SD cards with ML for my T5i. I have done this a million times before (but not recently). I am using the macboot terminal command because of a permissions problem which arose on OSX Mavericks. I am presently running Yosemite.

Every time I try, Macboot scans my system and concludes "There are no suitable cards."

I have tried with all of my cards, both in the SD slot and with a usb adapter. It simply does not recognize that there is an SD card ready to prepare.

And yes, it's scanning for max 128gb and I'm using 64gb cards.

What could be wrong? Please help me format these. Thanks!


Edit:
BTW when I try the dropdown to select a card drive, there are no options.

Here's what it says:

Command 'sw_vers | grep ProductVersion | awk '{print $2}'' = '10.10.3'
   return code was 0
Command 'sw_vers | grep Build | awk '{print $2}' | sed s/[A-Z]/\ /g | awk '{print $1}'' = '14'
   return code was 0
maxsize=128000 testsize=140000 (128GB)
Scanning for suitable cards (128GB or less) ...
Command 'df | grep -e "/$" | sed s/[s/]/\ /g | awk '{print $2" "$3 }' | sed s/\ /s/g' = 'disk1'
   return code was 0
Command 'diskutil info disk0 | awk '/Total Size:/ {print    $3}'' = '500.1'
   return code was 0
Command 'diskutil info disk0 | awk '/Total Size:/ {print    $4}'' = 'GB'
   return code was 0
checking j=500000 k=500 testisize=140000 disk s= 'GB'
Disk 0 is too big (size=500GB)
Command 'diskutil info disk1 | awk '/Total Size:/ {print    $3}'' = '498.9'
   return code was 0
Command 'diskutil info disk1 | awk '/Total Size:/ {print    $4}'' = 'GB'
   return code was 0
checking j=499000 k=499 testisize=140000 disk s= 'GB'
Skipping system disk ...
Command 'diskutil info disk2 | awk '/Total Size:/ {print    $3}'' = '2.0'
   return code was 0
Command 'diskutil info disk2 | awk '/Total Size:/ {print    $4}'' = 'TB'
   return code was 0
checking j=2000000 k=2 testisize=140000 disk s= 'TB'
Disk 2 is too big (size=2000GB)
Command 'diskutil info disk3 | awk '/Total Size:/ {print    $3}'' = '2.0'
   return code was 0
Command 'diskutil info disk3 | awk '/Total Size:/ {print    $4}'' = 'TB'
   return code was 0
checking j=2000000 k=2 testisize=140000 disk s= 'TB'
Disk 3 is too big (size=2000GB)
Command 'diskutil info disk4 | awk '/Total Size:/ {print    $3}'' = '4.0'
   return code was 0
Command 'diskutil info disk4 | awk '/Total Size:/ {print    $4}'' = 'TB'
   return code was 0
checking j=4000000 k=4 testisize=140000 disk s= 'TB'
Disk 4 is too big (size=4000GB)
Command 'diskutil info disk5 | awk '/Total Size:/ {print    $3}'' = '2.0'
   return code was 0
Command 'diskutil info disk5 | awk '/Total Size:/ {print    $4}'' = 'TB'
   return code was 0
checking j=2000000 k=2 testisize=140000 disk s= 'TB'
Disk 5 is too big (size=2000GB)
Command 'diskutil info disk6 | awk '/Total Size:/ {print    $3}'' = '500.1'
   return code was 0
Command 'diskutil info disk6 | awk '/Total Size:/ {print    $4}'' = 'GB'
   return code was 0
checking j=500000 k=500 testisize=140000 disk s= 'GB'
Disk 6 is too big (size=500GB)
Command 'diskutil info disk7 | awk '/Total Size:/ {print    $3}'' = '5.0'
   return code was 0
Command 'diskutil info disk7 | awk '/Total Size:/ {print    $4}'' = 'TB'
   return code was 0
checking j=5000000 k=5 testisize=140000 disk s= 'TB'
Disk 7 is too big (size=5000GB)
Command 'diskutil info disk8 | awk '/Total Size:/ {print    $3}'' = '3.0'
   return code was 0
Command 'diskutil info disk8 | awk '/Total Size:/ {print    $4}'' = 'TB'
   return code was 0
checking j=3000000 k=3 testisize=140000 disk s= 'TB'
Disk 8 is too big (size=3000GB)
Command 'diskutil info disk9 | awk '/Total Size:/ {print    $3}'' = '2.0'
   return code was 0
Command 'diskutil info disk9 | awk '/Total Size:/ {print    $4}'' = 'TB'
   return code was 0
checking j=2000000 k=2 testisize=140000 disk s= 'TB'
Disk 9 is too big (size=2000GB)
There are no suitable cards

I am filming a live event in two weeks, and the organizers want to me to connect my T5i to a projector screen at the event, for the audience. Problems:

1) The LCD shuts off when HDMI is connected, so I can't see what I'm shooting unless I'm looking at the projector.
2) The Magiclantern GUI appears on the HDMI output. Hitting the info button cycles through the canon display options, but there's no way to get a image totally clear of overlays.

I don't need an actual "clean" video for external capture, I just need the LCD screen to keep working with ML, while outputting "clean" hdmi to the projector. Is this remotely possible?

Any ideas??

Edit:
OK I figured out how to clear the overlays... but the problem remains- I need to use the LCD simultaneously. Is this possible?

Hello, I am working with two 700d cameras for record wedding and we are very interested in some options that magic lantern can give us. Principally, the peak, the vumeters and the middle step of ISO. We installed the magic lantern nightly.2014sept12.700d.113. And it works decently in the first look. But it is very important to know if i can trust in the stability of this version in a wedding recording we can´t have a fail with the camera, it could be very bad for our work. I would like that someone could respond about the question if i can use this version of magic for this three options or maybe another more stable version or at this time is not recommended use any versión for fieldwork.

Thanks to all and specially to the developers for this great work.

I´m sorry for my poor english

I have never had any stability problems with using ML on the job. I've encountered some glitches while updating firmware and messing with modules, but nothing that has ever compromised my work. Just be diligent with updating to the latest version, and if you're playing with unfamiliar features, always be sure to test it out before it's an important shot.

Seeing that you have two cameras, you might want to try shooting with ML on only one of them. Also, keep in mind, because ML is only installed on the SD card, you could have an extra card without ML, in case you wanted to use just the Canon menu. But make sure that the blank card is NOT formatted for DSLR booting (if you format the card on a computer with Macboot/Eoscard and then delete the ML files, the camera will still try to boot the card, but there's no ML to boot, so the camera will basically be a brick until you pull the battery and use another memory card).

Good luck!

Thanks!

Where can I find v6 of the VOL_64 module?

I've just updated from an old nightly build (July22) to the most recent one, and the Volume 64 module won't load. The error message says that the module is version 5, and ML expects v6.

http://www.zenoshrdlu.com/macboot/macboot.html

Derp, thanks.

I was just updating my SD cards to the latest nightly build for my 700D. A week or two ago, I updated my system from OSX snow leopard to mavericks. I just updated the java sdk, but for some reason Macboot refuses to prepare the memory cards.

With debug on, it says:

Suitable cards present: 1
scripts=false chdkboot=false chdk32boot=false dslrboot=true
Command 'diskutil unmountDisk disk9' = 'Unmount of all volumes on disk9 was successful'
   return code was 0
making DLSR-bootable - format=2
making FAT32 DSLR-bootable
Command 'printf "EOS_DEVELOP" | dd bs=1 count=11 seek=0x47 conv=notrunc of=/dev/disk9s1' = '!Error

dd: /dev/disk9s1: Permission denied'
   return code was 1
Command 'diskutil mountDisk disk9' = 'Volume(s) mounted successfully'
   return code was 0



Am I screwed?

So if you are using the June 25th Nightly, your saying this Vol64 module is not working for you? Because I myself tested it with the June 25th nightly and it worked perfectly, I get no error messages?

I don't know what has changed with the shutter speeds, I have not been coding for awhile so I have not kept track of all the new changes with ML.

Maybe you need to clean your ML config file and the module config files?

Yup that did it. Thanks!

I recently recompiled a version just last night to get my cams up to date and also the module. Let me know if this one doesn't work for you.
https://bitbucket.org/mk11174/700d113/downloads/VOL_64_June_25_2014.zip

Now, before I get the cryptic message screen, it gives me this upon booting:

"
Camera was not shut down cleanly.STBY
Skipping module loading

"

I have no idea what it means "shut down cleanly," I always wait for the red light to stop blinking before I touch the memory card slot.

Also, I've noticed that the shutter speed for video of 1/47 now appears to be 1/45; I'm wondering if this is just an interface thing or if it's actually rolling a fraction of a second slower now?

Hey everybody,

For a few months I've been using the 64 notch audio module that mk11174 posted a while back. Worked great, my only gripe was having to manually transfer the module and settings folders upon updating nightly builds.

I stopped updating probably a few weeks ago, and just tried running the latest nightly (June 25).

I've found that the audio 64 module doesn't seem to work any more, I'm getting this cryptic annoying message about it, and the feature is no longer accessible.

I'm assuming that the module is no longer supported; I'm wondering if there's a workaround and / or if precise audio controls will be properly integrated into the nightly builds soon? It was a lot quicker and easier to switch between AGC and manual settings than diving into the canon menu.

And yes, MZ flickers, no fix for that yet, but its not so bad of your not moving around much. I don't know what happen to the green indicator box for it, it has never had it or worked on this camera as far as I know.

Somebody should work on this, because the flicker is kind of annoying, and green focus confirmation would make this feature super awesome. I also wish I could activate magic zoom using the live view magnification buttons, rather than focus ring + half shutter. That said, right now I can make the box disappear with the - button, but I wish it was set up to formally work with + as well.

And thanks for the audio modules mk11174, working great for me!

[ML has nothing to do with the module, try at your own risk and if module is buggy, just ask me for help because it is not part of the great ML.]

Hi, I just want to make note to protect ML from support questions while using the vol adjust module.

ML has nothing to do with the module, try at your own risk and if module is buggy, just ask me for help because it is not part of the great ML.

I don't want the Devs bother by questions for this module even though the module is very basic and straight foward, you adjust the mic input from 0 to 21 or 0 to 64, I know, sound hard 
but I really want to make it clear for the Devs of ML, its not supported by ML, I will be your only support for it.

When the audio chip is coded by whoever, I will delete the module from the forum since it won't be needed.

Again, the values for the dB version are most likely wrong, I tried to get the real values and make sure they are what they say, but the document is to complicated for me 
I just simply felt like beefing the GUI up so I did, simple as that.

But the modules, whichever you choose to use work just fine for what I intended, control mic input from within ML GUI and it works just fine for me and other users so feel free to try it out if you want.

Ok, so just to confirm, is the 0-64 version identical in function to the Canon menu?

The audio meters should be working the latest nightly, I made the changes a few days ago. 

Hey mk11174, I'm still on 1.1.1, running your Feb 26 build. I'm just trying to decide if/when it's worth the firmware upgrade, because right now I'm doing perfectly well with this old version. I'm just wondering, as of right now, if the current nightly build of 1.1.3 is up to par with the Feb 26 111?

how do you guys handle the formatting issue ?

Is formatting the card on computer as good as on camera ? So far I allways formatted the card on camera, delted magic lantern and put it back on afterwards.

Formatting on a computer is really just deleting files/folders from the card individually, while formatting in the camera is wiping everything and resetting the DCIM/MISC folders and stuff like that. Formatting on the camera is the safest way to make sure the filing system is configured right for the camera to save photos/videos properly.

I would say that the best way to do it is to manually remove ML from the card on a computer, and then reformat it in camera as usual.

Or if i delete every single video on camera, is it as good as formatting ?

I would recommend against this. I've always avoided deleting files individually, because over time it can screw with the negative space on the card and cause problems with the card's filing system. The best way to do it is to let the camera handle it and wipe/reset everything at the same time. Deleting every single video individually is completely different from reformatting, and could certainly cause problems.

Looking at the card1 shutter speeds, it looks like you are using the build right before my last one which does not have the fps/shutter fix because those are the exact speeds I was getting before the fps/shutter fix.

Maybe start over, delete the autoexec.bin and the ML folder on card1 and re-download https://bitbucket.org/mk11174/t5i/downloads/ML_700D_Meters_Feb_26_2014.zip and see what happens.

Card2 is the way you want it to be, that sounds like it is using the shutter fix.

The card type should not be changing any of these things.

Sometimes if you do a copy over of the autoexec.bin file and ML folder, something may not overwrite and you will be using the older versions, thats why its best to start fresh and delete them first and unzip the new ones to card to be 100% sure.

Ok, all set. I was pretty sure that I copied the same file and folder onto both cards, but evidently something got messed up.

So the only other thing at this point, is the problem that if I try to reformat a card with ML in camera, it freezes the camera and fails to completely reformat. I can always just wipe the card on my laptop, but it kind of worries me that the camera has lost the ability to reformat cards with ML running on them.

Hey, I've just noticed something weird, I'm not sure what this means (or if it has anything to do with the shutter angle discussion above).

I have ML installed on two different cards. The shutter speed options are different, even though they have identical copies of mk11174's most recent build with audio meters.

On the 1st card (used to install ML on the camera), the shutter options are:
1/27
1/34
1/41
1/52
1/68
1/82
1/100
1/140
1/160
1/210
1/270
1/320
1/420
1/540
1/650
1/840
1/1100
1/1300
1/1700
1/2200
1/2600
1/3500

On the 2nd card, the options are:
1/31
1/39
1/42
1/47
1/60
1/78
1/85
1/94
1/120
1/160
1/170
1/190
1/240
1/310
1/340
1/370
1/480
1/620
1/680
1/750
1/960
1/1300
1/1400
1/1500
1/2000
1/2600
1/2800
1/3000
1/4100

While the Canon menu settings are set to 24p, Card 2 lists the fps @ 23.973, however card 1 lists the shutter speed at 21.576. I'm trying to keep as close to 1/48 for standard shooting (so I guess 1/52 on card 1 and 1/47 on card 2).



EDIT: I just realized, I should probably mention (and might have to do with the fps variation) that they are different brand cards, where card 1 has a speed of 24mb/s, and card 2 is 30mb/s. I guess I'm wondering, is this a glitch in ML, or is it actually shooting at a different framerate than what the canon menu is set as because the card isn't fast enough? 

If you would like an up to date build with audio meters I updated my version so it is up to date as of today Feb 26 2014. Also includes the fps/shutter value fix.
https://bitbucket.org/mk11174/t5i/downloads

Awesome, thanks!

Also, I figure I should let you guys know: When I was installing ML on my T5i, I went through the same procedure as when I installed on my T3i, but with the T5i I never reached the green text screen. For a few moments after loading the firmware, there were some scattered blocks of black/white static pixels on the lcd, starting with the upper left corner, and then there was a long horizontal block of static pixels near the center of the screen. It was quite worrisome at first, especially because I never saw the green text screen, but after turning the camera off and reloading the card, ML works fine. Except, when I've tried to reformat the card with ML on it, the camera fails. It gets to "rewriting bootflags" and just completely freezes, not even the off switch works, the only way to shut it off is by pulling the battery. I've tried reformatting with keeping and deleting ML, and both times freeze the camera when it gets to rewriting bootflags.

I expect these kinds of glitches because it's a work in progress, I just wanted to make sure you guys knew about this stuff. Otherwise, it all works great!

Perhaps try clicking on the word Features in that link you posted

Derp, thank you.

Ok, after trial and error debugging with Glassescreditsroll, I came up with a good temp solution for fulltime meters that works exactly the same on the 650d and 700d https://bitbucket.org/mk11174/t5i/downloads/ML_700D_Meters_Jan_30_2014.zip

The primary feature I need is the audio meters. Should I use this version mk11174 linked above, or are audio meters available yet on the general nightly build here: http://builds.magiclantern.fm/#/

It would be really great if there was a file attached to the nightly builds that listed which features are fully operational, and which are still in progress (or is there, and I just don't know where to look?).

Thanks guys, you are wizards for making this possible.

https://bitbucket.org/mk11174/magic-lantern/downloads/700D_all%20you%20need%20MagicLatern.zip

Awesome, thanks!

I've been trying to figure out the .fir for ages. I've finally registered to say thank you.

So I'm wondering, how long did it take to bring a stable release to the 600d?

I know there's no way to estimate a timeframe on upcoming versions, I'm just trying to gauge how long it's taken in the past.