EOS M3 porting - page 49 - DryOS Development - CHDK Forum
supplierdeeply
« previous next »
Pages: 1 ... 44 45 46 47 48 [49] 50 51 52 53 54 ... 67   Go Down

EOS M3 porting

  • 663 Replies
  • 241305 Views
*

Offline srsa_4c

  • ******
  • 4262
Re: EOS M3 porting
« Reply #480 on: 03 / June / 2018, 17:30:23 »
Advertisements
That's a long post and I won't be able to answer everything at once.
Quote from: derMart on 03 / June / 2018, 07:24:10
I have build rev. 5021 for firmware 1.20f. The bitrate changing feature works like a charm without crashes there. One quirk however ist that the reported byterates for cbr mode are varying (ex.: at 0.25 modifier, byterates vary between 384KB/s and around 700KB/s), I have not checked the encoded video if it varies there too.
The bitrate is OK on my cameras, I assume the same on this one. The bitrate display is the one that isn't perfect: CHDK gets recorded file size in 3MB increments. At low bitrates, that results in a heavily inaccurate display. When you record for a longer time, the variation will gradually improve.
Quote
I have one big problem with CHDK on my M3 and this is the menu flickering issue reported on the M10.
It was also reported on the M3.
Have you tried switching off Canon features that draw various animated stuff on screen?

For D6 display related info, try browsing through these threads:
https://chdk.setepontos.com/index.php?topic=11316.0
https://chdk.setepontos.com/index.php?topic=12788.0
Quote
In the chdk code I have seen that for all DIGIT6 processors only draw to the active buffer is implemented.
Could a workaround be to implement drawing to both (or are there even more?) bitmap buffers simultaneously like for the older models done?
Of course this would be slow because redundant draw calls have to be done.
The slowness of drawing was one of the reasons why I did not implement drawing to both buffers.
Quote
A better strategy might be to blit one buffer after completed drawing a frame to the other or get to know when the active buffer changes? Do we have any information about such event?
We don't have our own display buffer, we write directly on Canon's. We also don't know when the buffers are swapped.
Quote
It seems some chdk osd items like the battery indicator flicker faster
Some parts of CHDK OSD are continuously redrawn.
Quote
How/when does chdk decide to redraw their osd stuff?
Some CHDK display modes (such as the menu) use "guard pixels". When the guard pixels are erased, we redraw.
Logged
*

Offline tiim

  • *
  • 1
Re: EOS M3 porting
« Reply #481 on: 07 / July / 2018, 16:03:26 »
Hello Everyone.

I'm new here.

I have been using CHDK on a number of P&S cameras, dating back to ~2009 on a PowerShot A7.

I have had an M3 since visiting Japan three years ago, when the camera was relatively new there. I have been lurking around, watching the development of the EOS M3 CHDK, and am very impressed with all your work, and THANK YOU!

I will share one thing about menu flickering:

I noticed erratic menu behavior, using fw 1.20f and CHDK 1.5.0-5066 full:

If you have AF enabled, the menu options jump vertically in menus that have no horizontal option (i.e. enter a value in milliseconds), the menu option (cursor) will jump as many spaces, up-to-down, as you have moved it.

If you are in a menu option that uses horizontal input, the cursor begins to jump side to side, and the further you move the cursor, the further the jump, back and forth.

If you are in MF mode, these cursor jumps do not happen.

In AF, you can temporarily 'calm the cursor down' by half-pressing the shutter button for a couple of seconds. This is how I figured out my work-around to MF mode.

Overall, the menu flicker (separate issue, and (less) noticeable on my other Canons) happens either in MF or AF, but appears less severe if you have a static background.

That is my input so far. I have a lot to figure out with CHDK on the M3, but coming from other cameras, it should not be too difficult.

Cheers,

Tim
« Last Edit: 07 / July / 2018, 16:09:44 by tiim »
Logged
*

Offline hyperion

  • *
  • 1
Re: EOS M3 porting
« Reply #482 on: 20 / July / 2018, 02:09:09 »
Hey All,

Was wondering if anyone can point me in the right direction.

I am trying to run a EOS M3 via HMDI into a capture card for continous video recording, however whenever the LCD times out so does the HDMI feed.

Is it possible to use CHDK to force the LCD to never time out?
Logged
*

Offline waterwingz

  • ******
  • 12044
    • Waterwingz
Re: EOS M3 porting
« Reply #483 on: 20 / July / 2018, 08:40:56 »
Quote from: hyperion on 31 / December / 1969, 23:15:20
Is it possible to use CHDK to force the LCD to never time out?
Yes.   It's an option available in the CHDK setup menus. 
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline mash.m

  • *
  • 2
Re: EOS M3 porting
« Reply #484 on: 09 / October / 2018, 06:07:24 »
Hi,

i´m new to chdk cause i get a faulty m3 that is working again now. i have installed chdk without any problems. Now i like to use the camera as a small setup for astrofotography. at the moment i use the intervall script, but it is limited to 30 seconds at max. is there a blub script out where i can select longer shooting time as 30 seconds?

Markus
Logged
*

Offline reyalp

  • ******
  • 12690
Re: EOS M3 porting
« Reply #485 on: 09 / October / 2018, 13:46:51 »
Quote from: mash.m on 09 / October / 2018, 06:07:24
Now i like to use the camera as a small setup for astrofotography. at the moment i use the intervall script, but it is limited to 30 seconds at max. is there a blub script out where i can select longer shooting time as 30 seconds?

Markus
I'm not clear which script you are using, but you should be able to set overrides longer than 30 seconds in the CHDK menu if the script itself doesn't set shutter speed.

You could also try https://chdk.wikia.com/wiki/Lua/Scripts:_Fixed_Exposure_Intervalometer which lets you easily select shutter speeds between 1/64 and 256 seconds

There is no "bulb" mode in CHDK. The shutter speed must be set before the exposure starts.
Logged
Don't forget what the H stands for.
*

Offline waterwingz

  • ******
  • 12044
    • Waterwingz
Re: EOS M3 porting
« Reply #486 on: 09 / October / 2018, 14:07:12 »
Quote from: mash.m on 09 / October / 2018, 06:07:24
Hi,

i´m new to chdk cause i get a faulty m3 that is working again now. i have installed chdk without any problems. Now i like to use the camera as a small setup for astrofotography. at the moment i use the intervall script, but it is limited to 30 seconds at max. is there a blub script out where i can select longer shooting time as 30 seconds?

Markus
http://chdk.wikia.com/wiki/Meteor_Intervalometer_with_Dark_Frame_Management
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline mash.m

  • *
  • 2
Re: EOS M3 porting
« Reply #487 on: 10 / October / 2018, 11:11:09 »
Quote from: reyalp on 09 / October / 2018, 13:46:51
I'm not clear which script you are using, but you should be able to set overrides longer than 30 seconds in the CHDK menu if the script itself doesn't set shutter speed.

You could also try https://chdk.wikia.com/wiki/Lua/Scripts:_Fixed_Exposure_Intervalometer which lets you easily select shutter speeds between 1/64 and 256 seconds

There is no "bulb" mode in CHDK. The shutter speed must be set before the exposure starts.

Hi, that was a very usefull hint. I´m often use Magic Lantern, but chdk is completely differently. i was able to override the shutter time and the aperature at chdk menu and use the a interval script in TV mode of the camera. Works like sharm  :D

Thanks, now recording without shutter will be nice. i saw that some People here are still in Progress. hope this will happen at near future.

markus
Logged
*

Offline darkest_star

  • *
  • 4
Re: EOS M3 porting
« Reply #488 on: 29 / November / 2018, 14:39:34 »
Hello chdk-m3 developers,

I'm a Canon camera user since many years. Since my cams doesn't support focus bracketing natively I came across to CHDK.
Currently I have access to an EOS M10 (FW 110d) and EOS M3 (FW 1120f), a EF-M 15-45mm and a EF-M 18-55mm lens. On both cams I got chdk installed and running.
But if I try to run several bracketing scripts it seems to me that get_focus as well as set_focus doesn't work as expected.
Function get_focus always returns "0" regardless of which focus distance was adjusted at the lens. set_focus doesn't sets the focus.
I have this effect on both cams and with both lenses.

Are these functions currently not implemented in EOS M3 (as well as M10) port?

Thanks in advance,
Uwe
Logged
EOS M3 (120f), EOS M10 (110d), PS G1X Mark II
*

Offline srsa_4c

  • ******
  • 4262
Re: EOS M3 porting
« Reply #489 on: 29 / November / 2018, 18:39:14 »
Quote from: darkest_star on 29 / November / 2018, 14:39:34
Are these functions currently not implemented in EOS M3 (as well as M10) port?
No, unfortunately not. This is mentioned in camera notes (camnotes.txt). My attempts to find a working focus control method have not been successful (I would not say it's impossible, it's just substantially different from PowerShots). I don't know if Ant has found something on the M3, but even if, it's not in the source.
Logged
Pages: 1 ... 44 45 46 47 48 [49] 50 51 52 53 54 ... 67   Go Up
« previous next »
 

Related Topics