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

eos M10 port

  • 284 Replies
  • 117360 Views
*

Offline srsa_4c

  • ******
  • 4217
Re: eos M10 port
« Reply #220 on: 15 / January / 2019, 13:00:03 »
Advertisements
has somebody thought of a way to move to the left when setting values instead of the non-available zoom buttons on the m10?.....
In case you're talking about a numeric input field: half press the shutter to move the cursor.

sv: "speed value", can be translated to ISO (see APEX.pdf)

*

Offline Mlapse

  • ***
  • 239
  • A480 A490 S95 M10
Re: eos M10 port
« Reply #221 on: 15 / January / 2019, 13:02:55 »
thanks, saves a lot of time.

well in that case, set the cam on iso200, locked it in the script. but when the script starts, you see higher than 200 values pop up first in the log.
« Last Edit: 15 / January / 2019, 13:12:32 by Mlapse »
frustration is a key ingredient in progress

Re: eos M10 port
« Reply #222 on: 10 / October / 2019, 08:19:03 »
Hi there

Since I am completely new in CHDK and everything similar I did not quite understand some of the things discussed in this topic (mainly because I am not into this kind of coding/developing)

So here a quick question:
Am I able with the stuff on CHDK for the M10 to deactivate the automatic LCD Display off?
Better said, can I turn this off for the HDMI output?

I wanted to use the m10 as my streams main camera, but with the display output turning off after 3 minutes (longest time I can set) this is not possible :(
I checked for a lot of things, but was not aware I also need to look up if a camera turns off the Video Signal for its HDMI output after the same time as the build in display :|

*

Online reyalp

  • ******
  • 12537
Re: eos M10 port
« Reply #223 on: 10 / October / 2019, 16:17:42 »
Hi there

Since I am completely new in CHDK and everything similar I did not quite understand some of the things discussed in this topic (mainly because I am not into this kind of coding/developing)

So here a quick question:
Am I able with the stuff on CHDK for the M10 to deactivate the automatic LCD Display off?
Better said, can I turn this off for the HDMI output?

I wanted to use the m10 as my streams main camera, but with the display output turning off after 3 minutes (longest time I can set) this is not possible :(
In the CHDK menu, CHDK Settings->Disable LCD Off: Always should be what you want. I'm not 100% certain this works with HDMI out, but there's no obvious reason it shouldn't. If it doesn't, please post here.
Don't forget what the H stands for.


Re: eos M10 port
« Reply #224 on: 29 / February / 2020, 01:53:43 »
Hello everyone.

I noticed that the largest aperture I can choose to override in CHDK's menus is f/1.8 (also the shooting.c file does not show an aperture larger than f/1.8). There are some lenses with larger apertures, such as the Canon EF-M 32mm f/1.4 lens. Is it possible to extend the aperture range so that a lens like the Canon 32mm will be fully supported by CHDK at its largest aperture?

Thanks.

*

Offline srsa_4c

  • ******
  • 4217
Re: eos M10 port
« Reply #225 on: 29 / February / 2020, 10:30:06 »
I noticed that the largest aperture I can choose to override in CHDK's menus is f/1.8.
Indeed, that was the fastest lens in my possession. I just had a look in the override menu and found that it's buggy when out-of-range.
Quote
There are some lenses with larger apertures, such as the Canon EF-M 32mm f/1.4 lens. Is it possible to extend the aperture range so that a lens like the Canon 32mm will be fully supported by CHDK at its largest aperture?
I can add more entries to the aperture list. But, the Canon APEX96 numbers are often off by a varying amount and I would prefer values that are actually used.
Can you help out by making a list of aperture values, using that lens? A range of f/1.4 ... f/8 would probably be sufficient.

The procedure would be:
- in CHDK menu: Miscellaneous stuff -> Debug parameters -> Debug data display [Props], Propcase/Paramsdata page [2]
- enter a shooting mode that allows setting aperture
- set aperture to largest, half press the shutter
- note the following: Av number on Canon screen, value after '23:', value after '29:'
- reduce aperture by one step, half press, take a note; repeat until you reach f/8

Propcase 23 is PROPCASE_AV, 29 is PROPCASE_USER_AV.

Re: eos M10 port
« Reply #226 on: 29 / February / 2020, 12:58:37 »
I only use the Cannon 22mm f/2 lens (I didn't buy the more expensive 32mm f/1.4 lens yet). Here are its values.
First column corresponds to 23 value, second to 29 value. f-numbers tested in descending order: f/2, f/2.2, f/2.5, f/2.8, f/3.2, f/3.5, f/4, f/4.5, f/5, f/5.6, f/6.3, f/7.1, f/8

192 192
228 224
252 256
288 288
324 320
348 352
384 384
420 416
444 448
480 480
516 512
540 544
576 576

*

Offline srsa_4c

  • ******
  • 4217
Re: eos M10 port
« Reply #227 on: 29 / February / 2020, 13:17:39 »
I only use the Cannon 22mm f/2 lens (I didn't buy the more expensive 32mm f/1.4 lens yet). Here are its values.
First column corresponds to 23 value, second to 29 value. f-numbers tested in descending order: f/2, f/2.2, f/2.5, f/2.8, f/3.2, f/3.5, f/4, f/4.5, f/5, f/5.6, f/6.3, f/7.1, f/8

192 192
228 224
252 256
288 288
324 320
348 352
384 384
420 416
444 448
480 480
516 512
540 544
576 576
Thanks. That's pretty consistent, values are matching for all lenses in their common Av range. Looks like User Av steps are 1/3EV apart and the displayed values are only approximations.
I'll add new entries to the list accordingly and post a note here when done.

edit:
Added larger apertures (f/1.2, 1.4 ...). The Av override selector in menu has the usual issues: exact (I assume) values are shown rather than rounded ones, and the list includes a few garbage entries due to a CHDK bug.

Also, from now on, the wheel_left() and wheel_right() script functions are functional.
« Last Edit: 29 / February / 2020, 15:04:22 by srsa_4c »


Re: eos M10 port
« Reply #228 on: 01 / March / 2020, 03:32:18 »
 
Looks like User Av steps are 1/3EV apart and the displayed values are only approximations.
To me it looks very consistent
We have seen here https://chdk.setepontos.com/index.php?topic=13532.20 that the real Aperture can be changed in 1/8EV Steps (12 APEX96 values).
If you change the aperture in canon menu from f2 to f2.2 (APEX 192 + 32 = 224), then the real aperture change from APEX 192 + 3* 12 = 228.
If have not understood, why the real aperture changes in 1/8EV steps and not in multiple  of 1/3EV steps (may be 1/9EV Steps).
 
Added larger apertures (f/1.2, 1.4 ...).
The Canon EF 50 mm/1,2 L USM together with the Viltrox ef-eos m2 Speedbooster
http://www.viltrox.com/en/index.php?m=index&a=show&cid=145&id=228
gives you an Aperture from f1.0. ;)
M100 100a, M3 101a, 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

Re: eos M10 port
« Reply #229 on: 08 / March / 2020, 03:00:19 »
I'm trying to take a sequence of pictures with the same exposure but with varying aperture values from f/2 till f/8. I set set_av96_direct to be the 29 values (192,228,252...) and set the values of set_tv96_direct to be the current get_tv96 value at f/2 minus the differences of the 29 values (0,-36,-60,...) and didn't modify the value of set_sv96. The pictures have very similar exposures, but the first image at f/2 seems to have a slightly different exposure (see attachment - which shows all images from f/2 till f/4). Is there a way to achieve constant exposure also at f/2?

 

Related Topics