Author Topic: ML on EOS-M2  (Read 120957 times)

gukuangshi

  • New to the forum
  • *
  • Posts: 6
Re: ML on EOS-M2
« Reply #350 on: December 21, 2018, 04:05:53 AM »
Peak focus and zoom in focus work well on my eos m2 using MD 58 1.4 lens (magiclantern-Nightly.2018Dec14.EOSM2103). And the interval time-lapse is also great. But the temperature is growing fast,and the power consumption is fast. I hope that next vision will fix the high power consumption.  New functions such as digital interpolation zoom and trap focus are expected.  Please keep trying! We will do some test and feedback.

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3737
Re: ML on EOS-M2
« Reply #351 on: December 21, 2018, 08:51:57 AM »
Excellent report! A+

Ok--so it looks like the "C" build is the most stable but it doesn't show the lens focal length. This is actually from Danne's crop_rec_4k_mlv_snd_isogain_1x3_presets_EOSM2 branch with some of the lines in raw.c commented out.

Found the problem. The EOSM2 uses lens properties like the other Digic 5 cameras while the EOSM uses a different set of lens properties. Let's see if the December 20 build that is on my Bitbucket downloads page is any better.

Here's the commit if anyone wants to see what's going on.
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102

gukuangshi

  • New to the forum
  • *
  • Posts: 6
Re: ML on EOS-M2
« Reply #352 on: December 21, 2018, 09:34:45 AM »
magiclantern-Nightly.2018Dec20.EOSM2103.zip now is available for eos m2, I don’t find any deadly bug, and it works well on my camera. The temperature is rising fast and I wonder it can be solved or not. 

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3737
Re: ML on EOS-M2
« Reply #353 on: December 21, 2018, 05:53:18 PM »
@gukuangshi - Welcome to the forum!

using MD 58 1.4 lens

You're using a Minolta MD Rokkor 50 mm f/1.4 or is it a MC Rokkor-PF 58 mm f/1.4?



In any case, the ability to adapt so many different lenses is one of the strong points of this camera.

The temperature is rising fast and I wonder it can be solved or not. 

Using LiveView on any camera will raise the temperature and being a mirrorless camera it is always in LiveView mode. Now is ML causing the temperature faster than normal? Hard to see because the Canon overlays don't show the sensor temp. I don't have the EOSM2 in my hands at this time but what I did was to run this test on an EOSM. Turn on the camera with ML and checked the starting temperature, in my case 18C. Then pulled the card and turned on the camera and let it sit on LiveView for 1 minute, the temp rose to 24C. Let the camera cool back down to 18C and turned it on again this time with ML running for 1 minute--same results. Try it on the EOSM2, you should see the same results.

I hope that next vision will fix the high power consumption.

I'll let you figure out how to test this out, chances are power consumption will be pretty much the same whether or not you're using ML. Of course if you start using some of the advanced features like Danne's 100fps 4k feature  :P it will probably burn through batteries.

New functions such as digital interpolation zoom and trap focus are expected.

Don't expect too much right away, we're still trying to make a somewhat stable build for this camera. Check out the Feature comparison matrix page. If a feature isn't working on the EOSM, it probably won't work on the EOSM2.
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102

JohanJ

  • Freshman
  • **
  • Posts: 88
Re: ML on EOS-M2
« Reply #354 on: December 21, 2018, 11:10:15 PM »
Found the problem. The EOSM2 uses lens properties like the other Digic 5 cameras while the EOSM uses a different set of lens properties. Let's see if the December 20 build that is on my Bitbucket downloads page is any better.
I can confirm that lens focal information works perfectly with the new December 20 build! I will continue testing with this build (let's call it D) and will post results asap.

I promised earlier to post the error log from the crashing DUO-ISO module. Here we go:

Code: [Select]
Locking cache
Lens moving (1561,  0)
Scanning modules...
Load modules ...
  [i] Load:  dual_iso.mo
Linking ..
tcc: error: undefined symbol 'mlv_set_type'
  [E] failed to link modules
updating Movie Tweaks -> Movie Logging
updating Movie Tweaks -> Time indicator

60D.111 / 100D.101 / M2.103

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3737
Re: ML on EOS-M2
« Reply #355 on: December 22, 2018, 02:24:49 AM »
Error reproduced on EOSM. New test build posted -- the winter solstice build.

Gee are we that far along that we're testing modules? Note there are issues with dual_iso on this camera:

Code: [Select]
    else if (is_camera("EOSM2", "1.0.3")) // WIP found movie mode but photo mode is taken from EOSM
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3737
Re: ML on EOS-M2
« Reply #356 on: December 22, 2018, 06:04:53 PM »
In order to find the addresses missing in dual_iso we need to use the iso-research branch. Lucky for us the patch manager was recently merged into iso-research so we should be able to use the patches needed for the EOSM2. Not sure if the LiveView hack Danne posted in Reply #330 is needed. You tell me -- iso-research build posted on my downloads page.
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102

JohanJ

  • Freshman
  • **
  • Posts: 88
Re: ML on EOS-M2
« Reply #357 on: December 22, 2018, 07:23:51 PM »
Some more test results based on build magiclantern-Nightly.2018Dec21.EOSM2103

I tested all functions in Expo menu in M mode, most of them even in Av & Tv as far as applicable. Everything works just fine except the following:

- Expo. Presets -> Press SET: SET activates Canon LV menu (might be as designed for M/M2?). With setting "Press Info" toggeling between two modes works fine (but you can't reach Canon Info screen anymore, of course).
- Expo.Override crashes the cam in LV if ExpSim is activated same time! To get out there I have to pull the battery! At least 4 different crash logs are written on the card.

Code: [Select]
CRASHLOG0.LOG

ASSERT: 0
at ./LvCommon/LvGainController.c:893, Evf:17bd0
lv:1 mode:3

Evf stack: 1be758 [1be8a0-1bdca0]
0xUNKNOWN  @ ca14:1be898
0xUNKNOWN  @ 36684:1be870
0x0003637C @ ff0d6258:1be858
0xUNKNOWN  @ 363ac:1be848
0xUNKNOWN  @ 478e00:1be820
0xUNKNOWN  @ 36434:1be800
0x00017B84 @ 1363c:1be798
0x00001900 @ 17bcc:1be790
0x0044C478 @ 44c57c:1be758

Magic Lantern version : Nightly.2018Dec21.EOSM2103
Mercurial changeset   : 577a7023a9f9 (crop_rec_4k_mlv_snd_isogain_1x3_presets_EOSM2) tip
Built on 2018-12-22 01:17:20 UTC by rosiefort@Rosie-Forts-Computer.local.
Free Memory  : 384K + 1911K

CRASHLOG1.LOG

ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_READOUTDONE_INTERRUPT_EVF, NULL, 0 ) )
at ./Evf/EvfState.c:520, **INT-D9h**:11bdc
lv:1 mode:3

debug_task stack: 2abfb0 [20fbd8-20dbd8]
0x0044C478 @ 44c57c:2abfb0

CRASHLOG2.LOG = CRASHLOG3.LOG = CRASHLOG4.LOG

ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_SETPARAM_INTERRUPT_EVF, NULL, 0 ) )
at ./Evf/EvfState.c:503, **INT-E0h**:11b9c
lv:1 mode:3

debug_task stack: 2abfb0 [20fbd8-20dbd8]
0x0044C478 @ 44c57c:2abfb0


CRASHLOG5.LOG

ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_VD_INTERRUPT_EVF, NULL, 0 ) )
at ./Evf/EvfState.c:545, **INT-6Ah**:11c40
lv:1 mode:3

debug_task stack: 2abfa0 [20fbd8-20dbd8]
0x0044C478 @ 44c57c:2abfa0

==> Pulled battery!


- Expo.Override seems to work fine if ExpSim is off

Besides these observations all functions in Expo menu are stable (as they are in Overlay menu as well as in Focus menu). More to come!
60D.111 / 100D.101 / M2.103

JohanJ

  • Freshman
  • **
  • Posts: 88
Re: ML on EOS-M2
« Reply #358 on: December 22, 2018, 07:33:45 PM »
In order to find the addresses missing in dual_iso we need to use the iso-research branch. Lucky for us the patch manager was recently merged into iso-research so we should be able to use the patches needed for the EOSM2. Not sure if the LiveView hack Danne posted in Reply #330 is needed. You tell me -- iso-research build posted on my downloads page.

In fact the latest change in magiclantern-Nightly.2018Dec21.EOSM2103 made it possible to load Dual ISO without crashing but it cannot be used. When activating DualISO in Expo Menu you get the following message:
Code: [Select]
ISOless PH err(15)
I will look into the iso-research build later. I would like to finish tests on the current standard build first.
60D.111 / 100D.101 / M2.103

JohanJ

  • Freshman
  • **
  • Posts: 88
Re: ML on EOS-M2
« Reply #359 on: December 22, 2018, 07:57:08 PM »
Thanks Walter. I can see that dfort was involved in this discussion. let's see where it brings us from there.

Sent from my SM-G930F using Tapatalk

60D.111 / 100D.101 / M2.103

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3737
Re: ML on EOS-M2
« Reply #360 on: December 22, 2018, 10:10:41 PM »
Hum -- seems that Walter's post got flagged as a "Hall of Shame" post. Here it is:

About ISOless errors:
https://www.magiclantern.fm/forum/index.php?topic=7139.msg197139#msg197139

That's the same issue I pointed out in Reply #356. Follow Bilal's instructions to find the addresses and I'll plug them into the code.
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102

critix

  • Contributor
  • Member
  • *****
  • Posts: 113
Re: ML on EOS-M2
« Reply #361 on: December 23, 2018, 10:30:21 AM »
You tell me -- iso-research build posted on my downloads page.
I ran the iso_research bracket and below put the result from the adtg_gui logs:
Code: [Select]
Canon EOS M2 1.0.3
00f00000:     803 (was 84b)      ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d93f0 Analog ISO (most cameras)
00f00003:     f08 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d93f6 Analog ISO on 6D
00f00004:       2 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d93f8 ISO-related?
00f00006:     78b ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d93fc ISO 50 or timing related: FFF => darker image
00028882:     41c (was 40e)      ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d8640 ISO ADTG gain (per column, mod 4 or mod 8)
00028884:     41e (was 410)      ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d8644 ISO ADTG gain (per column, mod 4 or mod 8)
00028886:     418 (was 40e)      ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d8648 ISO ADTG gain (per column, mod 4 or mod 8)
00028888:     41c (was 40e)      ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d864c ISO ADTG gain (per column, mod 4 or mod 8)
==================================================================
Canon EOS M2 1.0.3
00f00000:     803 (was 84b)      ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d93f0 Analog ISO (most cameras)
00f00003:     f08 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d93f6 Analog ISO on 6D
00f00004:       2 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d93f8 ISO-related?
00f00006:     78b ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d93fc ISO 50 or timing related: FFF => darker image
00028882:     41c (was 40e)      ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d8640 ISO ADTG gain (per column, mod 4 or mod 8)
00028884:     41e (was 410)      ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d8644 ISO ADTG gain (per column, mod 4 or mod 8)
00028886:     418 (was 40e)      ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d8648 ISO ADTG gain (per column, mod 4 or mod 8)
00028888:     41c (was 40e)      ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d864c ISO ADTG gain (per column, mod 4 or mod 8)
==================================================================
Canon EOS M2 1.0.3
00f00000:     803 (was 86f)      ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d93f0 Analog ISO (most cameras)
00f00003:     f08 ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d93f6 Analog ISO on 6D
00f00004:       2 ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d93f8 ISO-related?
00f00006:     78b ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d93fc ISO 50 or timing related: FFF => darker image
00028882:     41c (was 400)      ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d8640 ISO ADTG gain (per column, mod 4 or mod 8)
00028884:     41e (was 400)      ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d8644 ISO ADTG gain (per column, mod 4 or mod 8)
00028886:     418 (was 400)      ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d8648 ISO ADTG gain (per column, mod 4 or mod 8)
00028888:     41c (was 400)      ISO=0 Tv=125 Av=56 lv=1 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d864c ISO ADTG gain (per column, mod 4 or mod 8)
==================================================================
Canon EOS M2 1.0.3
0002c002:     190 (was 19f)      ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=4ac30 addr=416d8f04
0002c080:       0 (was ff)       ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=4ac30 addr=416d8f08
0002c0c1:       0 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46374 addr=416d977c
0002c517:       0 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46140 addr=416d9734
0002c518:       0 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46140 addr=416d9738
0002c519:       0 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46140 addr=416d973c
0002c026:       0 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46140 addr=416d9730
00028830:       1 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46160 addr=416d85f8 Only slightly changes the color of the image (g3gg0)
000288b0:       0 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46160 addr=416d85fc
0002805f:      c1 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46270 addr=416d7b7c Shutter blanking for x5/x10 zoom
00028061:      c1 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46270 addr=416d7b80 Shutter blanking for LiveView 1x
00028172:     3b7 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46270 addr=416d7b84 PowerSaveTiming 'on', set to Line count + 1
00028173:     46a ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46270 addr=416d7b88 PowerSaveTiming 'off', should be slightly below FPS timer B
00f00000:     86f ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d9456 Analog ISO (most cameras)
00f00001:     4ce ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d9458 Vertical offset
00f00002:     742 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d945a Horizontal offset / column skipping
00f00003:     f08 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d945c Analog ISO on 6D
00f00004:       2 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d945e ISO-related?
00f00005:      20 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d9460 Fine vertical offset, black area maybe
00f00006:     78b ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d9462 ISO 50 or timing related: FFF => darker image
00f00007:     800 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d9464 5D3: image fading out; 6D, 700D: vertical offset
00f00008:     800 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d9466 Unknown, used on 6D
00f00009:      81 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46284 addr=416d9468
0006c079:     525 (was 929)      ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=445d4 addr=1be2d4
0002c082:       0 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46338 addr=416d8c78
0002c09b:     177 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46338 addr=416d8c7c
0002c00d:    5249 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46338 addr=416d8c80
0002c00e:       7 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46338 addr=416d8c84
0002c00f:       7 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46338 addr=416d8c88
0002c010:       7 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46338 addr=416d8c8c
0002c011:       7 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46338 addr=416d8c90
00028882:     400 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d8640 ISO ADTG gain (per column, mod 4 or mod 8)
00028884:     400 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d8644 ISO ADTG gain (per column, mod 4 or mod 8)
00028886:     400 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d8648 ISO ADTG gain (per column, mod 4 or mod 8)
00028888:     400 ISO=0 Tv=125 Av=56 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=Evf pc=46364 addr=416d864c ISO ADTG gain (per column, mod 4 or mod 8)
==================================================================
Because the file is bigger, we just put some of it ... the rest is in the link below:
https://drive.google.com/open?id=1z7W6sY1AhmRss0wRiYWW7vjZCgWzSbMR
I hope it's ok what I put ... If it's done differently, please tell me to restore ...
Thank you
Canon 1300D, 500D, EOS M, EOS M2

JohanJ

  • Freshman
  • **
  • Posts: 88
Re: ML on EOS-M2
« Reply #362 on: December 23, 2018, 11:44:05 AM »
Follow Bilal's instructions to find the addresses and I'll plug them into the code.
Well, I hope I got it right. ADTG-GUI came up with same values both for video and for foto mode:
Code: [Select]
Evf:46284:416d93f0 v=2051(0x803) nrzi_dec=4093(0xffd)
At least I can find these values in Critix post too.
60D.111 / 100D.101 / M2.103

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5923
Re: ML on EOS-M2
« Reply #363 on: December 23, 2018, 12:41:53 PM »
Could you try this module?
https://bitbucket.org/Dannephoto/magic-lantern/downloads/dual_iso.mo

Test both photo and movie mode.

i put in your register here in dual_iso.c:
Code: [Select]
    else if (is_camera("EOSM2", "1.0.3")) // WIP found movie mode but photo mode is taken from EOSM
    {
        is_eosm2 = 1;

        FRAME_CMOS_ISO_START = 0x416d93f0; // CMOS register 0000 - for LiveView, ISO 100 (check in movie mode, not photo!)
        FRAME_CMOS_ISO_COUNT =          6; // from ISO 100 to 3200
        FRAME_CMOS_ISO_SIZE  =         34; // distance between ISO 100 and ISO 200 addresses, in bytes

        PHOTO_CMOS_ISO_START = 0x416d93f0
; // CMOS register 0000 - for photo mode, ISO 100
        PHOTO_CMOS_ISO_COUNT =          6; // from ISO 100 to 3200
        PHOTO_CMOS_ISO_SIZE  =         16; // distance between ISO 100 and ISO 200 addresses, in bytes

        CMOS_ISO_BITS = 3;
        CMOS_FLAG_BITS = 2;
        CMOS_EXPECTED_FLAG = 3;
    }

JohanJ

  • Freshman
  • **
  • Posts: 88
Re: ML on EOS-M2
« Reply #364 on: December 23, 2018, 01:21:14 PM »
Could you try this module?
https://bitbucket.org/Dannephoto/magic-lantern/downloads/dual_iso.mo
I put the module into Dforts build December 21 and started in photo mode but the module fails to load with the same error as posted here. Dfort made a minor change in reply #355 which fixed it.

There was another message repeatedly printed to the console:
Code: [Select]
Black 1/5: mean too different (8152, ref 8013+-0.00)
Maybe worth to look into it too, this message does not show when going back to dfort's original DUAL_ISO.mo
60D.111 / 100D.101 / M2.103

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5923
Re: ML on EOS-M2
« Reply #365 on: December 23, 2018, 01:34:36 PM »

JohanJ

  • Freshman
  • **
  • Posts: 88
Re: ML on EOS-M2
« Reply #366 on: December 23, 2018, 01:58:36 PM »
No more linking error but
Code: [Select]
ISOless PH err(8)Now with error code 8 instead of err(15) both in photo and video mode.
60D.111 / 100D.101 / M2.103

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5923
Re: ML on EOS-M2
« Reply #367 on: December 23, 2018, 02:02:05 PM »
Oki. Are you able to compile? If so play around with changes in dual_iso.c and compile and put it on to your camera.
I have ran out of time atm...

Maybe only one place should have its registry changed?

Code: [Select]
int err = isoless_enable(PHOTO_CMOS_ISO_START, PHOTO_CMOS_ISO_SIZE, PHOTO_CMOS_ISO_COUNT, backup_ph);

JohanJ

  • Freshman
  • **
  • Posts: 88
Re: ML on EOS-M2
« Reply #368 on: December 23, 2018, 03:45:39 PM »
Made another observation: the value for CMOS[0] is alway the same 416d93f0 when
  • Dual_iso.mo was not loaded
  • Dual_iso.mo was loaded but not activated
  • Dual_iso.mo was loaded and activated
Does that make sense?
60D.111 / 100D.101 / M2.103

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3737
Re: ML on EOS-M2
« Reply #369 on: December 23, 2018, 07:08:25 PM »
@Danne -- you need to fix this formatting error:

Code: [Select]
        PHOTO_CMOS_ISO_START = 0x416d93f0
; // CMOS register 0000 - for photo mode, ISO 100

Should be:

Code: [Select]
        PHOTO_CMOS_ISO_START = 0x416d93f0; // CMOS register 0000 - for photo mode, ISO 100

Does that make sense?

CMOS register 0000 doesn't change between photo and movie mode on this camera? That doesn't make sense but this camera is full of surprises. You don't need to load dual_iso to find the right values. Set the ISO to 100 and follow Bilal's instructions. Try using the iso-research for this. Do screenshots and post them if possible.

In the meantime I posted a new build that has PHOTO_CMOS_ISO_START and FRAME_CMOS_ISO_START set to the same address. Let's see if that clears up the ISOless PH err(?).
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5923
Re: ML on EOS-M2
« Reply #370 on: December 23, 2018, 07:26:31 PM »
isoless 8 still persists.
Can confirm the same adress for both movie and photo mode. I can also confirm that you can manually set dual iso cmos[0] register and achieve dual iso.
There are two photo mode switches on eosm2. The 1 one actually gives another register than in movie mode and in photo mode. I tried using that one instead but no luck. So maybe there´s some hook in register that do not apply still for cmos registry? SOmething similar seems to happen with crop_rec. cmos doesn´t seem to change using that code too.

critix

  • Contributor
  • Member
  • *****
  • Posts: 113
Re: ML on EOS-M2
« Reply #371 on: December 23, 2018, 07:39:39 PM »
Hi!
@dfort, I have memory error when i try to use adtg_gui with iso-research.2018Dec22.EOSM2103.zip:
Code: [Select]
shoot_malloc(1.0MB|TMP|DMA) FAILED AT adtg_gui.c:1004, log_iso_regs.
Canon 1300D, 500D, EOS M, EOS M2

JohanJ

  • Freshman
  • **
  • Posts: 88
Re: ML on EOS-M2
« Reply #372 on: December 23, 2018, 08:28:04 PM »
You don't need to load dual_iso to find the right values. Set the ISO to 100 and follow Bilal's instructions. Try using the iso-research for this. Do screenshots and post them if possible.
I did all this already following Bilal's  instructions using your the ISO research build from your repository.  The result is posted in #362. Same values for photo mode 2 as well as video mode made me suspicious whether I did right or not so I repeated a couple of times but in the end it was no difference.

In the meantime I posted a new build that has PHOTO_CMOS_ISO_START and FRAME_CMOS_ISO_START set to the same address. Let's see if that clears up the ISOless PH err(?).
Unfortunately the result is the same as posted here
60D.111 / 100D.101 / M2.103

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3737
Re: ML on EOS-M2
« Reply #373 on: December 23, 2018, 09:39:44 PM »
I have memory error when i try to use adtg_gui with iso-research.2018Dec22.EOSM2103.zip:

I updated the latest build with the latest adtg_gui module. See if that works. magiclantern-Nightly_with_adtg_gui.2018Dec23.EOSM2103
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102

JohanJ

  • Freshman
  • **
  • Posts: 88
Re: ML on EOS-M2
« Reply #374 on: December 24, 2018, 01:24:09 AM »
I updated the latest build with the latest adtg_gui module. See if that works. magiclantern-Nightly_with_adtg_gui.2018Dec23.EOSM2103
Ok, now photo mode and video mode show different results. A strange thing was that in photo mode I got even 2 different values, one before taking a picture and another one after taking a picture (both having dual iso activated). But ever since then the second value got kind of persistent and I cannot reproduce the initial one (though I have a screenshot, but ... never mind). So here are the new values for COMS[0]:

Photo mode 2--> Value after taking a shot -> since then kind of persistent
Code: [Select]
Evf:46284:416d949a v=2231(0x8b7) nrzi_dec=3877(0xf25)
Video mode --> this is the same as in previous tests based on iso_research build
Code: [Select]
Evf:46284:416d93f0 v=2051(0x803) nrzi_dec=4093(0xffd)
60D.111 / 100D.101 / M2.103