Author Topic: Canon EOS M  (Read 391319 times)

me.n.khof4sh

  • Just arrived
  • *
  • Posts: 2
Re: Canon EOS M
« Reply #1100 on: October 22, 2016, 09:29:38 PM »
Hello Guys  :)
I'm new here and have a question.
Is it possible to make a headphone jack for 700D with ML?
If it is, please explain for me how.
I'd be glad for your help.

dfort

  • Hero Member
  • *****
  • Posts: 1548
Re: Canon EOS M
« Reply #1101 on: October 23, 2016, 03:01:41 PM »
Is it possible to make a headphone jack for 700D with ML?

You posted this in the wrong topic. This is for the EOSM. The 700D topic is: http://www.magiclantern.fm/forum/index.php?topic=5951.0

Here's a list of features for each camera: https://builds.magiclantern.fm/features.html

Sorry, headphone monitoring for the 700D isn't on the list. That means that the developers haven't been able to get it working--yet.
EOSM.202 EOSM.203 700D.115 5D3.*

dfort

  • Hero Member
  • *****
  • Posts: 1548
Re: Canon EOS M
« Reply #1102 on: October 23, 2016, 03:35:49 PM »
Hi,
I am using ML everythings works fine for months, but since I started to shot long exposure even manual or intervalometer from ML, always raw photos, and different setups, SD cards, etc., I´ve got corrupted photos, below ejemple, so anyone had any similar one? even I´m thinking in a hardware problem....

https:[email protected]/30394580436


Could you provide more information? Things like what is the date of the build you're using, at what shutter speed does this occur, what are your settings? CR2 or DNG or ?? Have you tried uninstalling ML and seeing if this is still occurring? That might point to a hardware issue.

By the way you can display images from flickr by "sharing" using "BBCode" and posting only the img tag. For example:

Code: [Select]
[img]https://c5.staticflickr.com/6/5827/30394580436_64f811d2e1_z.jpg[/img]
Make sure you keep the image resolution less than 900x900 pixels as stated in the Magic Lantern Forum Rules.

EOSM.202 EOSM.203 700D.115 5D3.*

dfort

  • Hero Member
  • *****
  • Posts: 1548
Re: Canon EOS M
« Reply #1103 on: October 23, 2016, 05:33:18 PM »
@Flash_Gordon came up with an interesting idea turning the EOSM into a wildlife trap camera. I came up with a simple solution using a lua script that keeps the LCD active indefinitely but it requires a custom build from the lua_fix branch. It isn't ideal, a better solution would be to allow the LCD to power down and still be able to trigger the camera with Audio RemoteShot but that requires digging deep into the ML code and it might not even be possible.

I posted a package with the custom build and instructions on how to set it up if anyone wants to try it out.

https://bitbucket.org/daniel_fort/magic-lantern/downloads/EOSM_wildlife_trap_2016-10-23.zip
EOSM.202 EOSM.203 700D.115 5D3.*

wildstray

  • New to the forum
  • *
  • Posts: 9
Re: Canon EOS M
« Reply #1104 on: October 23, 2016, 06:15:00 PM »
Hello all, about EOS M do you notice a poor battery life? It seems to me really poor (not even an hour of usage). Better with a compatibile battery, worse with the original Canon one.
Thanks to ML I noticed that CPU usage never decrease below 40%... is it normal? What's the idle cpu load for other cameras? Maybe the reason for poor battery life and what's using the CPU so much? (LV?)

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 9711
  • 5D Mark Free
Re: Canon EOS M
« Reply #1105 on: October 23, 2016, 06:23:17 PM »
60D: 57% in photo mode (30fps, global draw off).

Drops to 26% with FPS override at 10 FPS.

wildstray

  • New to the forum
  • *
  • Posts: 9
Re: Canon EOS M
« Reply #1106 on: October 23, 2016, 06:40:15 PM »
60D: 57% in photo mode (30fps, global draw off).

Drops to 26% with FPS override at 10 FPS.

Thank you a1ex! So it seems that CPU usage is related to LV...
EOS M with FPS override at 10 FPS has 20% cpu usage... good for battery... but the camera become unusable.
AF slows down proportionally to FPS. It's already slow without override... at 10 fps it takes 4-5 seconds to focus :o
In the 60D AF slows down?

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 9711
  • 5D Mark Free
Re: Canon EOS M
« Reply #1107 on: October 23, 2016, 06:59:04 PM »
Yes, it does.

Powersave idea: drop to 10 FPS after X seconds of idle time, switch back on half-shutter press (or on any key press).

wildstray

  • New to the forum
  • *
  • Posts: 9
Re: Canon EOS M
« Reply #1108 on: October 24, 2016, 02:42:40 AM »
Powersave idea: drop to 10 FPS after X seconds of idle time, switch back on half-shutter press (or on any key press).

Great idea. I just wrote some modifications to powersave.c, it works... but there is an annoying issue: with touch or keypress the camera returns instantaneously responsive, while with half shutter there is a little delay... little but noticeable...   :-\

Code: [Select]
diff -r 15fce5b49b23 src/powersave.c
--- a/src/powersave.c   Sat Oct 08 16:22:41 2016 +0200
+++ b/src/powersave.c   Mon Oct 24 02:31:13 2016 +0200
@@ -129,6 +129,7 @@
 static CONFIG_INT("idle.display.gdraw_off.after", idle_display_global_draw_off_after, 0);
 static CONFIG_INT("idle.rec", idle_rec, 0);
 static CONFIG_INT("idle.shortcut.key", idle_shortcut_key, 0);
+static CONFIG_INT("idle.display.fps_on.after", idle_display_fps_on_after, 0);
 
 /* also used in zebra.c */
 volatile int idle_globaldraw_disable = 0;
@@ -143,6 +144,8 @@
 static int idle_countdown_display_off_prev = 50;
 static int idle_countdown_globaldraw_prev = 50;
 static int idle_countdown_clrscr_prev = 50;
+static int idle_countdown_fps = 50;
+static int idle_countdown_fps_prev = 50;
 
 /* this will block all Canon drawing routines when the camera is idle */
 /* (workaround for 50D) */
@@ -154,7 +157,7 @@
 
 int idle_is_powersave_enabled()
 {
-    return idle_display_dim_after || idle_display_turn_off_after || idle_display_global_draw_off_after;
+    return idle_display_dim_after || idle_display_turn_off_after || idle_display_global_draw_off_after || idle_display_fps_on_after;
 }
 
 int idle_is_powersave_enabled_on_info_disp_key()
@@ -166,7 +169,8 @@
 {
     return (idle_display_dim_after && !idle_countdown_display_dim_prev) ||
            (idle_display_turn_off_after && !idle_countdown_display_off_prev) ||
-           (idle_display_global_draw_off_after && !idle_countdown_globaldraw_prev);
+           (idle_display_global_draw_off_after && !idle_countdown_globaldraw_prev) ||
+           (idle_display_fps_on_after && !idle_countdown_fps_prev);
 }
 
 void idle_force_powersave_in_1s()
@@ -174,6 +178,7 @@
     idle_countdown_display_off = MIN(idle_countdown_display_off, 10);
     idle_countdown_display_dim = MIN(idle_countdown_display_dim, 10);
     idle_countdown_globaldraw  = MIN(idle_countdown_globaldraw, 10);
+    idle_countdown_fps         = MIN(idle_countdown_fps, 10);
 }
 
 void idle_force_powersave_now()
@@ -181,6 +186,7 @@
     idle_countdown_display_off = MIN(idle_countdown_display_off, 1);
     idle_countdown_display_dim = MIN(idle_countdown_display_dim, 1);
     idle_countdown_globaldraw  = MIN(idle_countdown_globaldraw, 1);
+    idle_countdown_fps         = MIN(idle_countdown_fps, 1);
 }
 
 int handle_powersave_key(struct event * event)
@@ -229,6 +235,7 @@
     idle_countdown_display_off = sensor_status ? 25 : idle_display_turn_off_after * 10;
     idle_countdown_display_dim = sensor_status ? 25 : idle_display_dim_after * 10;
     idle_countdown_globaldraw  = sensor_status ? 25 : idle_display_global_draw_off_after * 10;
+    idle_countdown_fps         = sensor_status ? 25 : idle_display_fps_on_after * 10;
 
     if (reason == -2345) // disable powersave during recording
         return;
@@ -379,6 +386,16 @@
         idle_globaldraw_disable--;
 }
 
+void idle_fps_en()
+{
+    set_config_var("fps.override", 1);
+}
+
+void idle_fps_dis()
+{
+    set_config_var("fps.override", 0);
+}
+
 #ifdef CONFIG_KILL_FLICKER
 
 static void black_bars_50D()
@@ -463,6 +480,11 @@
     if (idle_display_global_draw_off_after)
         idle_action_do(&idle_countdown_globaldraw, &idle_countdown_globaldraw_prev, idle_globaldraw_dis, idle_globaldraw_en);
 
+    #ifdef FEATURE_FPS_OVERRIDE
+    if (idle_display_fps_on_after)
+        idle_action_do(&idle_countdown_fps, &idle_countdown_fps_prev, idle_fps_en, idle_fps_dis);
+    #endif
+
     /* zebra.c */
     extern int clearscreen;
     if (clearscreen == 2) // clear overlay when idle
@@ -611,6 +633,17 @@
             .help = "Turn off GlobalDraw when idle, to save some CPU cycles.",
             //~ .edit_mode = EM_MANY_VALUES,
         },
+       #ifdef FEATURE_FPS_OVERRIDE
+        {
+            .name = "Turn on FPS override",
+            .priv           = &idle_display_fps_on_after,
+            .update         = idle_display_feature_print,
+            .select         = idle_timeout_toggle,
+            .max            = 900,
+            .icon_type      = IT_PERCENT_LOG_OFF,
+            .help = "Turn on FPS override when idle, to save some CPU cycles.",
+        },
+       #endif
         MENU_EOL
     },
   }
@@ -633,5 +666,7 @@
 void idle_globaldraw_en() { }
 void idle_force_powersave_now() { }
 void idle_force_powersave_in_1s() { }
+void idle_fps_en() { }
+void idle_fps_dis() { }
 #endif 
 

longpvo

  • Just arrived
  • *
  • Posts: 2
Canon EOS M5 ?
« Reply #1109 on: November 09, 2016, 06:26:07 AM »
Can I install ML on the new M5 ? Looks a great combination for product photography (custom cropmark/ghost image + focus stack)

Walter Schulz

  • Hero Member
  • *****
  • Posts: 5378
Re: Canon EOS M
« Reply #1110 on: November 09, 2016, 09:45:44 PM »
M5 and EOS M are playing different games. EOS M shares codebase with Canon DSLRs. M5 shares with Canon's Point-and-Shoot. It would be quite a big task to port. Look for CHDK port instead.

longpvo

  • Just arrived
  • *
  • Posts: 2
Re: Canon EOS M
« Reply #1111 on: November 24, 2016, 10:26:22 AM »
I meant the EOS M5, there is a difference ? ..

Walter Schulz

  • Hero Member
  • *****
  • Posts: 5378
Re: Canon EOS M
« Reply #1112 on: November 24, 2016, 02:10:09 PM »
I meant EOS M5, too ...

funkysound

  • Freshman
  • **
  • Posts: 74
Re: Canon EOS M
« Reply #1113 on: November 26, 2016, 10:49:06 AM »
I just realized that "movie crop mode" does not show up under Modified if I use it. Is it supposed to be this way or does it just happen with my M?
EOS 600d, Tamron 17-50mm 2,8 with stab., Tamron 70-300mm, Canon 50mm 1:1,8, Sigma 10-20mm 4-5,6, Sigma 30mm 1,4,  EOS M with 18-55mm, 22mm and EF adapter, tons of more glases incl. FD/FL, EOS 70D, Canon 18-135mm STM

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 9711
  • 5D Mark Free
Re: Canon EOS M
« Reply #1114 on: November 26, 2016, 12:20:21 PM »
To appear in the Modified menu, an item must also have a CONFIG_INT entry (to be saved in ML config file). Otherwise it doesn't know which is the default state, so it can't tell whether it was modified or not.

You'll need to use a new variable (other than video_mode_crop, which is global and updated from Canon settings aka properties).

Fairly easy coding task, although it requires a little attention to details.

Licaon_Kter

  • Senior
  • ****
  • Posts: 495
  • M
Re: Canon EOS M
« Reply #1115 on: November 27, 2016, 10:38:21 PM »
Wasn't this (crop mode) something that had an issue on EOS M? It got reset on restart or something.

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 9711
  • 5D Mark Free
Re: Canon EOS M
« Reply #1116 on: November 27, 2016, 10:47:18 PM »
Then, adding a config entry will solve that as well.

dfort

  • Hero Member
  • *****
  • Posts: 1548
Re: Canon EOS M
« Reply #1117 on: November 27, 2016, 11:06:32 PM »
I believe that the problem was that if you turn on crop mode then switching to a non ML card, you get stuck in crop mode for video. Yep--just tried it. Put camera in crop mode, remove the card, restart the camera and it stays in crop mode.

Would it be possible to turn off crop mode on shutdown then turn it back to the desired state from the configuration file on start up? Of course this wouldn't help if the camera crashes.
EOSM.202 EOSM.203 700D.115 5D3.*

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 9711
  • 5D Mark Free
Re: Canon EOS M
« Reply #1118 on: November 27, 2016, 11:39:08 PM »
Should work if you call movie_crop_hack_disable() from ml_shutdown.

dfort

  • Hero Member
  • *****
  • Posts: 1548
Re: Canon EOS M
« Reply #1119 on: November 29, 2016, 07:02:07 AM »
Should work if you call movie_crop_hack_disable() from ml_shutdown.

Yes it does.

https://bitbucket.org/hudson/magic-lantern/pull-requests/776/disables-crop-mode-hack-when-turning/diff

Next we can take a look at the Modified menu thing.
EOSM.202 EOSM.203 700D.115 5D3.*

dfort

  • Hero Member
  • *****
  • Posts: 1548
Re: Canon EOS M
« Reply #1120 on: November 30, 2016, 08:28:11 AM »
So close. Just need to figure out how to read the config file and switch to the saved mode when restarting the camera. The movie_crop_hack_disable() from ml_shutdown trick works great when switching to non-ML cards but we should be able to restore Movie crop mode if that's what was saved in the config file.



https://bitbucket.org/daniel_fort/magic-lantern/commits/bca4abfb0e8d9c63bfcf8fc244bb2db32fbb9c15
EOSM.202 EOSM.203 700D.115 5D3.*

dfort

  • Hero Member
  • *****
  • Posts: 1548
Re: Canon EOS M
« Reply #1121 on: December 06, 2016, 08:07:14 PM »
Just discovered that Canon released a firmware update for the EOSM on November 29.

Quote
Firmware Version 2.0.3 incorporates the following fix:

Corrects a phenomenon in which when using the camera with the EF-S 18-135mm f/3.5-5.6 IS USM or EF 70-300mm f/4-5.6 IS II USM lens, even if lens aberration correction is set to "Enable", correction will not be applied.

Looks like the same update that the 100D, 650D, 700D, 70D and perhaps others got recently.

No big deal but porting a minor firmware update might be an interesting advanced beginner project. (Is that an oxymoron?)
EOSM.202 EOSM.203 700D.115 5D3.*

cluna

  • Just arrived
  • *
  • Posts: 1
Re: Canon EOS M
« Reply #1122 on: December 12, 2016, 12:58:22 AM »
hey so I went to uninstall ml and I did something wrong now I'm stuck when I try to turn it on the light just flashes green with a black screen but if I take out the sd card and battery and only put the battery back in it will start up any ideas ?

dfort

  • Hero Member
  • *****
  • Posts: 1548
Re: Canon EOS M
« Reply #1123 on: December 12, 2016, 07:21:53 AM »
@cluna

The bootflags on your card and camera are still active. If you put in a card that doesn't have the bootflag set it should work fine. If you want to uninstall ML properly, put ML back on your card and run the install process (firmware update) again but wait 1 minute before restarting the camera. There is a countdown timer on the bottom of the install screen. That will remove the bootflags from both the camera and card.
EOSM.202 EOSM.203 700D.115 5D3.*

branex

  • New to the forum
  • *
  • Posts: 3
Re: Canon EOS M
« Reply #1124 on: December 20, 2016, 06:27:30 PM »
Hi. Long used ML on different cameras. Very interested in the question. Is there a possibility of follow focus like other cameras. It's just the perfect camera for gimbal. And it would be nice to control the lens without an additional servo. Sorry for the quality of English.