EOS M ** Alpha 1 ** [FIXED][DOWNLOAD]

[Marvin]

nice cup in the background

[Red3ull]

Hi,

what do you think is it possible to speed up AF performance?

Greetings from Austria
Martin

[g3gg0]

what do you think is it possible to speed up AF performance?

too early to even give even a rough estimation if this specific feature is possible.
we are a) checking what needs to be ported and b) what users would love to see on M.
so we take this as info, but cant give you any answer.

[jplxpto]

Well, that was fast IMO, I didn't expected to see the hello world in 2-3 days
Great job guys. Keep it going

Yes, they are doing a fantastic job.
The following will be the 650D

Nanomad, we are with you....

[coutts]

Found a memory address that changes rapidly as i swipe my finger across the screen, so, this is the start of implementing touch buttons to ML!!

0x4D868 --> represents pin-point area on screen (x and y pixels) being touched (some mapping of high/low to represent left/right/top/bottom of screen)
0x4D810 --> value=0x11100 when screen isn't being touched, value=0x11101 when 1 finger is held touching the screen
            --> value=0x11102 with 2 fingers touching the screen
            --> value=0x11103 with 3 fingers
            --> value=0x1104 with 4 fingers! Note: only the LSB seems to be used here, other bits seem to change sometimes. but the rightmost bit always changes to match how many fingers are touching the screen.


the first address, 0x4D868 seems to map the screen like this:

top left corner of the screen = 0x0000000
top right corner = 0x00002CF
bottom right corner = 0x1DF02CF
bottom left corner = 0x1DF0000

so, lower 3 bits represent the X coordinates, from 0 to 719 (720px wide)
middle bit is always 0
upper 3 bits represent the Y coordinates, from 0 to 479 (480px tall)


Looks like touch screens won't be hard



also, I found something related to audio levels, these 2 addresses change with ambient noise, so they may represent audio levels:
0x3F240
0x3F244

[jplxpto]

You are good

thumbs up

[jplxpto]

let the games begin

I know that this project is new, but the photo is of good quality ... I liked ...

[feureau]

Found a memory address that changes rapidly as i swipe my finger across the screen, so, this is the start of implementing touch buttons to ML!!

Awesome!! \o/

I wonder what can we use the multi-touch for...?

[0xAF]

I wonder what can we use the multi-touch for...?

What is the original purpose of multi-touch ? Do canon use it for something ?
Many things can be done with MT.

[nanomad]

Does it have pinch to zoom in playback mode? Maybe that's what it is for. If it isn't, we can probably implement it

[0xAF]

Does it have pinch to zoom in playback mode? Maybe that's what it is for. If it isn't, we can probably implement it

My thoughts were exactly the same...

[Pumpkinwaffle]

A nice feat would be to swipe U/D/L/R for iso, sound, aperture, WB...

A way to implement settings that aren't easily available through the knobs in liveview. (I don't know how easy it is fiddle with the settings on this camera but this could be a solution)

Maybe designing a touch menu for ML, Android/IOS style

Is the autofocus really slow then?

[feureau]

Is the autofocus really slow then?

Seems to hunt a lot. Maybe there's a way to disable contrast detect and rely solely on phase?

[jmrben]

Hi Guys,

Not sure if you have a welcome section, if so I will post in it next

The Eos M has not been enabled for tethering from Canon.  Is this something that Magic Lantern could enable? (obviously if it is succesfully ported etc)

Cheers

John

[a1ex]

Probably only with a custom client app (e.g. ML controller).

[jimijam]

Pinch-to-zoom is already enabled in playback mode (actually, it seems to be the only way to zoom in on the photo - I find it a little irritating and would definitely like to be able to double-tap the screen to 100% zoom). I don't think I've found pinch being used anywhere else. You could possibly use it to perform the 5x or 10x zoom, but you'd have difficulty doing it without stuffing up your current af-point.

The android app (https://play.google.com/store/apps/details?id=eu.chainfire.remoterelease) does not work for the eos-m (I presume it uses the tethering API).

Changing Av/Tv/ISO/exposure-comp/af-point using touch-only is very easy already. Altering the audio-recording level is a bit finnicky (or is this something the video guys set once and never really touch again?) and also it would be nice to "touch to focus" (like on a smartphone) - at the moment it's either "touch to set af point" (you then need to hit the shutter to af of course) or "touch to focus and take a photo" - nothing in-between.

Would be nice to have a way to lock/unlock the af-point to its current position as it's very very easy to touch the screen accidentally and muck up your selected point. A good option here would be if the video-record button could toggle it.... that button is currently unused in green-box or stills mode.

[HoloPed]

Could you unblock the software remote control options ?
All the EOS cameras can be operated with Canon's software SDK,
but the EOS M camera has these operations blocked in the firmware.

Thanks !

[Malcolm Debono]

Could you unblock the software remote control options ?
All the EOS cameras can be operated with Canon's software SDK,
but the EOS M camera has these operations blocked in the firmware.

Read reply #39

[HoloPed]

Read reply #39

Thanks, I missed that.
Is the protocol for the custom client public ?
Would I be able to write my own client ?
Thanks.

[a1ex]

PTP protocol is documented (see gphoto2 or ptpcam for example).

[coutts]

FPS register values (for enabling FPS control in ML). posting it here so it's documented somewhere.

Code: [Select]

NTSC:
LV (and all non-recording modes):
       TIMER_A: 0x20f020f
       TIMER_B: 0x7e5 / 0x7e6 [changes between the 2 twice a second]
       SHUTTER (1/60): 0x3B2 (same in all recording modes too)

Recording:
1080p 30fps:
       - same as LV conditions

1080p 24fps:
       TIMER_A: 0x20f020f
       TIMER_B: 0x9de / 0x9df

720p 60fps:
       TIMER_A: 0x20f020f
       TIMER_B: 0x3f2 / 0x3f3

480p 30fps:
       - same as LV conditions



PAL:
LV (and all non-recording modes):
       TIMER_A: 0x20f020f
       TIMER_B:0x7e5/0x7e6
       SHUTTER (1/100): 0x25e

Recording:
1080p 25fps:
       TIMER_A: 0x27f027f
       TIMER_B: 0x7cf (doesn't change)
       SHUTTER: 0x1f4

1080p 24fps:
       TIMER_A: 0x20f020f
       TIMER_B: 0x9de / 0x9df
       SHUTTER: same as lv

720p 50fps:
       TIMER_A: 0x27f027f
       TIMER_B: 0x3e7 (doesn't change)
       SHUTTER: 0x1f4

480p 25fps:
       TIMER_A: 0x27f027f
       TIMER_B: 0x7cf
       SHUTTER: 0x1f4

[jplxpto]

Thanks, I missed that.
Is the protocol for the custom client public ?
Would I be able to write my own client ?
Thanks.

http://www.magiclantern.fm/forum/index.php?topic=3401.msg16879#msg16879

[g3gg0]

FPS register values (for enabling FPS control in ML). posting it here so it's documented somewhere.

here is the right place:
https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdEZrXzBSZmdaSE9WVnpOblJ2ZGtoZXc#gid=0

[feureau]

here is the right place:
https://docs.google.com/spreadsheet/ccc?key=0AgQ2MOkAZTFHdEZrXzBSZmdaSE9WVnpOblJ2ZGtoZXc#gid=0

Btw, I see a 1920x1080 x5/x10 settings on the 7D. What is this? A x5 and x10 crop recording at 1080p?

[a1ex]

Plain x5/x10.