eos M10 port - page 22 - DryOS Development - CHDK Forum supplierdeeply

eos M10 port

  • 221 Replies
  • 96818 Views
*

Offline srsa_4c

  • ******
  • 3904
Re: eos M10 port
« Reply #210 on: 03 / January / 2019, 18:52:57 »
Advertisements
was wondering if I can help testing some things.
i have firmware and automatic update functioning.
I assume you mean loading CHDK automatically (from a locked card) and loading CHDK via the firmware update menu?

As I'm not using the fimware update method regularly, I might not be aware of possible bugs that only show up when using that boot method. Some other DIGIC 6 cameras have various problems with CHDK loaded via the firmware update menu, but I have not seen any on this camera. If you can find some, please report them.

Quote
so i tested that first by using a script that support zoom and that froze the camera.
I was going to say why would you want to use a zoom script on this camera, but then I realized that the set_zoom() script command did indeed crash the cam. So, thanks for reporting that. Should be fixed in revision 5147.

*

Offline Mlapse

  • ***
  • 184
  • A480 A490 S95 M10
Re: eos M10 port
« Reply #211 on: 04 / January / 2019, 02:03:58 »
I was going to say why would you want to use a zoom script on this camera, but then I realized that the set_zoom() script command did indeed crash the cam. So, thanks for reporting that. Should be fixed in revision 5147.

thanks, in my opinion disabling a function is better than crashing the camera by mistake..
the second thing i can report, but maybe that should be in the screen flicker menu thread.
I noticed that scripts that use an osd (white box with blue header) the height is not right making it hard to read (text lines overlap), and with most camera's i own that box is in the top middle of the screen, while here it is top left, see picture
« Last Edit: 04 / January / 2019, 02:05:42 by Mlapse »
frustration is a key ingredient in progress

*

Offline srsa_4c

  • ******
  • 3904
Re: eos M10 port
« Reply #212 on: 05 / January / 2019, 12:53:34 »
in my opinion disabling a function is better than crashing the camera by mistake..
Agree.
Quote
the second thing i can report, but maybe that should be in the screen flicker menu thread.
I noticed that scripts that use an osd (white box with blue header) the height is not right making it hard to read (text lines overlap), and with most camera's i own that box is in the top middle of the screen, while here it is top left, see picture
That's an issue that affects all D6 ports: these have (by our choice) higher resolution screens AND a larger default font. AFAIK scripts can't easily know when they run on one of those cameras, and they all use hardcoded coordinates and font sizes.

*

Offline Mlapse

  • ***
  • 184
  • A480 A490 S95 M10
Re: eos M10 port
« Reply #213 on: 06 / January / 2019, 04:33:31 »
Quote
That's an issue that affects all D6 ports: these have (by our choice) higher resolution screens AND a larger default font. AFAIK scripts can't easily know when they run on one of those cameras, and they all use hardcoded coordinates and font sizes.
ah, i can change a number.
solved it for now by editing one of the scripts i use. I did not know if there is a digic6 flag available for scripts to use, so made one.

doubling the height works good enough for me and makes it readable.
ok, i am no programmer, but maybe this can be solved -for now- with something simple like:
# Digic6             true  "line height double Digic6"
if (Digic6 == true) then line = line*2 end

but then it has to be put into every script and is a manual setting, it is not a neat solution
hereby the UI script i adapted and has an extra flag at the bottom in the menu for doubling height. (sorry Waterwingz for this crude hack into your clean code)
if it's TRUE in my a480 it creates loose lines, but is still readable until you put that flag on FALSE and get the original size back.
If implemented I would advise setting the flag on FALSE as default.

« Last Edit: 16 / March / 2019, 09:57:35 by Mlapse »
frustration is a key ingredient in progress


Re: eos M10 port
« Reply #214 on: 06 / January / 2019, 15:14:41 »
hereby the UI script i adapted and has an extra flag at the bottom in the menu for doubling height. (sorry Waterwingz for this crude hack into your clean code)
You are breaking my heart here.  Okay, I'm just kidding about that. Scripts are made to be hacked.

Having said that, we need to add a way to detect & handle this script side (assuming there is really no way to do this today).

Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline Mlapse

  • ***
  • 184
  • A480 A490 S95 M10
Re: eos M10 port
« Reply #215 on: 06 / January / 2019, 16:20:03 »
Quote
Having said that, we need to add a way to detect & handle this script side (assuming there is really no way to do this today).
maybe a separate functionfile you can call that adds x2 to line height and doubles space from the left to the osd if triggered by screen resolution.
what i notice is that screen flicker is a lot less with this so that helps.

I am more curious in how to figure out to get the focus going on the M10. i would like to take a go at zoom at infinity. Ant already made some progress as I read. But it was unclear to me how to get that info from my lens (the 15-45 was not in his list)
« Last Edit: 06 / January / 2019, 16:22:41 by Mlapse »
frustration is a key ingredient in progress

Re: eos M10 port
« Reply #216 on: 06 / January / 2019, 16:24:25 »
Quote
Having said that, we need to add a way to detect & handle this script side (assuming there is really no way to do this today).
maybe a separate functionfile you can call that adds x2 to line height and doubles space from the left to the osd if triggered by screen resolution.
what i notice is that screen flicker is a lot less with this so
Traveling now so don't have time to search but I'm very sure we have been down this path before.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline Mlapse

  • ***
  • 184
  • A480 A490 S95 M10
Re: eos M10 port
« Reply #217 on: 06 / January / 2019, 16:27:46 »
Quote
Traveling now so don't have time to search but I'm very sure we have been down this path before.
forget about me mentioning it, enjoy your travels
frustration is a key ingredient in progress


*

Offline Mlapse

  • ***
  • 184
  • A480 A490 S95 M10
Re: eos M10 port
« Reply #218 on: 08 / January / 2019, 13:58:55 »
I was looking for ways to limit long exposures on the m10 when doing day to night shots and found out the strangest thing.
what you see is the result of a short timelapse of the same night view, i just alter settings inbetween shots to get a different limit from the divider.
resulting in 2, 4, 8, 15 and 30 second limit for exposure(i know the log shows 32, so does canon)...maybe i can also get even shorter stops from it and inbetween values, but i'd really have to test a lot more.
it may not be as finetuned as what i hoped, but I think it is great

Day 1 Tue Jan  8 19:45:39 2019 Oldest image set to : 100_0801/IMG_0028.JPG
Day 1 Tue Jan  8 19:45:39 2019 IMG_0028.JPG tv: 4.0 f: 4.5 ISO: 100 bv: -763  V: 7.043 T: 23
Day 1 Tue Jan  8 19:46:07 2019 IMG_0029.JPG tv: 2.0 f: 4.5 ISO: 100 bv: -763  V: 6.998 T: 24
Day 1 Tue Jan  8 19:46:23 2019 set LCD off
Day 1 Tue Jan  8 19:46:42 2019 IMG_0030.JPG tv: 8.0 f: 4.5 ISO: 100 bv: -763  V: 7.052 T: 24
Day 1 Tue Jan  8 19:47:37 2019 IMG_0031.JPG tv: 32 f: 4.5 ISO: 100 bv: -723  V: 6.980 T: 25
Day 1 Tue Jan  8 19:47:51 2019 IMG_0032.JPG tv: 8.0 f: 4.5 ISO: 100 bv: -723  V: 7.025 T: 25
Day 1 Tue Jan  8 19:48:07 2019 IMG_0033.JPG tv: 2.0 f: 4.5 ISO: 100 bv: -723  V: 7.016 T: 25
« Last Edit: 08 / January / 2019, 14:53:55 by Mlapse »
frustration is a key ingredient in progress

*

Offline Mlapse

  • ***
  • 184
  • A480 A490 S95 M10
Re: eos M10 port
« Reply #219 on: 15 / January / 2019, 12:07:02 »
the M10 needs an ND apex96 value of 192 to start off properly when running rawopint.

But more prudent  ;) has somebody thought of a way to move to the left when setting values instead of the non-available zoom buttons on the m10?.....
it is a small issue, i just set the numbers in the script to my likings to prevent me set to too much default again.

i only thought sv was a bit weird, i assume it is the iso200 i set?
and another thing, although i lowered to iso200 i think the tsensor is still high....but that could be rawopint
« Last Edit: 15 / January / 2019, 13:11:08 by Mlapse »
frustration is a key ingredient in progress

 

Related Topics