Topics

I've been reading a bit about LUA scripting as well as the API but I couldn't find a way to disable the Wi-Fi function.

I'd like to create a script that when pressing the remote shutter halfway (or maybe even by clapping), the 6D would turn off Wi-Fi and automatically start recording (the camera doesn't record when Wi-Fi is enabled).
This would be really useful when recording myself since I don't have to go to the camera and then go back to my position where I previously focused myself.

Hi,

I want to donate some money but I noticed there's only a bitcoin option in the donation page.

Is there a way to donate using PayPal?

Right now I can only use the Wifi feature to monitor or download pictures using the Canon Camera Connect app, but that isn't quite useful. Would it be possible to bypass this



and record while monitoring?

Both in Safari




and Chrome

Today I broke my shutter and while downloading my images I saw some logs on the card. I was thinking maybe those are useful for developers? Let me know if you want then, I can upload the logs for you.

PS: Not sure where to post this, sorry if it's in the wrong subforum.

Recently I went out on a shoot and when I came back and checked my pictures I noticed there are a lot of dead pixels on my images. Since the camera is brand new, I thought maybe Magic Lantern is causing this? I will take a few more samples tonight with and without ML just to check this, but thought I should post the samples in the meantime to get some feedback from you guys.

EXIF is Canon 6D, 25s, ISO 1600.

ML version magiclantern-v2.3.NEXT.2013Nov16.6D113

I converted a raw file using DPP then cropped it in PS. All crops are from the same picture. And yes, I noticed this stuff on a lot of pictures on the same place.

These are 100% crops:





This one is a 300% crop, notice the X pixel:



Pretty weird.

Is ML causing this?

Thanks in advance!

Hi developers,

I recently bought a Samyang 14mm and it's a full manual lens. I'm okay with that, but there's one thing that bothers me and it's related to the camera not being able to read the aperture of the lens because it doesn't have a chip.

Being used to chipped lenses, I never experienced this, but now I noticed that both my 60D and 6D don't show the correct brightness when on live view mode. Even worst, the exposure readings I get are way off. Often I get underexposed images so it's a must to check the histogram (something I always do anyway). But the downside of all this is that it's almost impossible to use a semi-manual setting, like say aperture priority.

Now, what I'm thinking is: is it possible to cheat the aperture and force a fixed one in the camera? I think if the camera reads for example f/2.8 it will show a correct exposure reading. But maybe I'm wrong.

What do you think, is this possible?

Hi guys,

I noticed this weird issue a few days ago when I was post processing some of my shots. When I go to live view I see all the information ML shows, and at the bottom left I can see the focal length is wrong.

Let's say I'm shooting at 17mm, ML shows 32mm. If I go to 50mm, ML shows 42mm. I tried moving the lens a bit and sometimes it changes to the actual focal length, but then it goes to the wrong value again. I also tested with a Canon 18-55 and that's working fine, so the problem seems to be the Tamron 17-50 lens. I don't have other lens to test.

I'm not sure, but I think this wasn't happening a few months ago (I'm not sure when or why it started). I was thinking maybe it's a problem with the contacts on the lens? What do you recommend to clean them?

I also deleted the config file but the problem is still there. I'm using a 60D.

Thanks!

I've been using ML on a 60D for quite a while. I recently acquired a T3i and now I want to install ML on it as well.

I was wondering, is it okay to use the same card on both cameras?

Thanks

Hi everybody.

I want to share with you my new film featuring some places from around my hometown in Argentina.

Some shots were shot with Magic Lantern, others with cheap intervalometers and others with Dynamic Perception's Stage Zero.

Any feedback is appreciated. Hope you enjoy it.

Thanks for watching!

Last night when setting up a timelapse I noticed that 30 seconds are not really 30 seconds (at least not according to ML).

I set my camera in manual for a 30 second exposure, but when I went into live view I saw it says 32" instead of 30".

Why is that?

Just what title says:



It's happening to me in Chrome 21.