chdk in the DIGIC6 world - page 20 - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: 1 ... 15 16 17 18 19 [20] 21   Go Down

chdk in the DIGIC6 world

  • 201 Replies
  • 170277 Views
*

Offline Mlapse

  • *****
  • 584
  • S95 S110
Re: chdk in the DIGIC6 world
« Reply #190 on: 11 / November / 2020, 04:01:27 »
Advertisements
since my m10 seems to be unrepairable i could look fresh at the options.

and since replacing the s95 can wait a year.
it might be the moment to try porting myself.
as far as I can tell the M100 has the same sensor as the M3, so that might not be bold enough.
maybe I should start looking for a M200 with it's quicker sensor and dive into that.


Logged
frustration is a key ingredient in progress
*

Offline c_joerg

  • *****
  • 1251
Re: chdk in the DIGIC6 world
« Reply #191 on: 11 / November / 2020, 06:20:48 »
Quote from: Mlapse on 11 / November / 2020, 04:01:27
as far as I can tell the M100 has the same sensor as the M3, so that might not be bold enough.
No, the Senor of M100 is different and much better than the M3 Sensor.
M100 has more Dynamic Range and has a very fast Dual Pixel AF

Quote from: Mlapse on 11 / November / 2020, 04:01:27
maybe I should start looking for a M200 with it's quicker sensor and dive into that.
If you can live without CHDK…
https://www.magiclantern.fm/forum/index.php?topic=23296.0
I think M100 and M200 have the same Sensor.
« Last Edit: 11 / November / 2020, 06:26:03 by c_joerg »
Logged
M100 100a, M3 121a, G9x II (1.00c), 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
*

Offline reyalp

  • ******
  • 14125
Re: chdk in the DIGIC6 world
« Reply #192 on: 24 / January / 2021, 02:37:13 »
I added a finsig_thumb2 match for live_free_cluster_count discussed in https://chdk.setepontos.com/index.php?topic=11927.180

Verified on g7x, sx730 and matching the value srsa_4c found for sx700
Logged
Don't forget what the H stands for.
*

Offline srsa_4c

  • ******
  • 4451
Re: chdk in the DIGIC6 world
« Reply #193 on: 24 / January / 2021, 16:39:41 »
Quote from: reyalp on 24 / January / 2021, 02:37:13
I added a finsig_thumb2 match for live_free_cluster_count
Thanks for doing that. I wonder if this should be tested prior to switching D6 (and 7) ports to the variable-based cluster count.
Logged
*

Offline reyalp

  • ******
  • 14125
Re: chdk in the DIGIC6 world
« Reply #194 on: 24 / January / 2021, 18:26:01 »
Quote from: srsa_4c on 24 / January / 2021, 16:39:41
Thanks for doing that. I wonder if this should be tested prior to switching D6 (and 7) ports to the variable-based cluster count.
My feeling is we don't need to test every cam, but it would be good to test a range of versions. I updated g7x, sx700, sx710 and sx730. With those verified, I'd be comfortable updating any DryOS r54-59 digic 6. I think if we verify at least one dry 52 cam (I think you already checked sx280?) and one digic 7 that's probably good enough. IMO the chance of bad matches is low, it's pretty complicated and ends on ldrd which is a rare instruction, and the offset is 0x38 for all of them.

If we make this the standard for digic 6-7, we could make the original GetDrive_FreeClusters not listed in stubs_entry.S.
Logged
Don't forget what the H stands for.
*

Offline srsa_4c

  • ******
  • 4451
Re: chdk in the DIGIC6 world
« Reply #195 on: 25 / January / 2021, 17:49:03 »
Quote from: reyalp on 24 / January / 2021, 18:26:01
(I think you already checked sx280?)
I checked the variable via the misc value display, but did not change the port yet. My intention was to add a camera.h define and change GetFreeCardSpaceKb() in platform/generic/wrappers.c.
Quote
If we make this the standard for digic 6-7, we could make the original GetDrive_FreeClusters not listed in stubs_entry.S.
Makes sense, in this case no new define would be needed.
Logged
*

Offline reyalp

  • ******
  • 14125
Re: chdk in the DIGIC6 world
« Reply #196 on: 25 / January / 2021, 21:56:45 »
Quote from: srsa_4c on 25 / January / 2021, 17:49:03
I checked the variable via the misc value display, but did not change the port yet. My intention was to add a camera.h define and change GetFreeCardSpaceKb() in platform/generic/wrappers.c.
Thanks. Updated for all cams in trunk 5728.
Logged
Don't forget what the H stands for.
*

Offline srsa_4c

  • ******
  • 4451
Re: chdk in the DIGIC6 world
« Reply #197 on: 21 / February / 2021, 10:11:31 »
Found something that looks like a more traditional movie_status fw variable. Can be found in a function called from UIFS_StopMovieRecord_FW, 0x8d38 in sx280 102b. That function (sub_FC135AC0) could be something like is_movie_recording. Values found when doing short recordings:
0 - stopped, not recording
4 - recording in progress
5 - recording being stopped

As discussed here, EOS M models appear to be able to record up to three ~4GB files without interruption. The camera's movie decoder, however, doesn't seem to like the resulting huge files.
Logged
*

Offline reyalp

  • ******
  • 14125
Re: chdk in the DIGIC6 world
« Reply #198 on: 22 / February / 2021, 01:11:44 »
Quote from: srsa_4c on 21 / February / 2021, 10:11:31
Found something that looks like a more traditional movie_status fw variable. Can be found in a function called from UIFS_StopMovieRecord_FW, 0x8d38 in sx280 102b. That function (sub_FC135AC0) could be something like is_movie_recording. Values found when doing short recordings:
0 - stopped, not recording
4 - recording in progress
5 - recording being stopped
Nice find. I added the function as unused in trunk 5747.

The variable might be called MovieState in the canon firmware (sx280 102b fc135b1a). It seems to have a few more possible values than the traditional movie_status, at least 8 and 9.
Logged
Don't forget what the H stands for.
*

Offline kitor

  • *
  • 20
Re: chdk in the DIGIC6 world
« Reply #199 on: 10 / April / 2021, 03:46:13 »
Quote from: srsa_4c on 05 / November / 2017, 10:46:14
I'd be interested in seeing that new drawing system. I was thinking about using the RGBA buffer(s), but have not attempted to make an implementation.
If yours proves to be a usable alternative, we could remove the D6 related mess from core/gui_draw.c (and elsewhere) and implement the new system on all D6 ports.

This is funny, I just felt 4 years behind and 3 steps ahead  :)

kitor from Magic Lantern here. One of our Discord members just sent a link to this thread, which I somehow missed during my research.
From what I saw in CHDK source code, it still uses YUV to render things on Digic 6, maybe that's why I stopped digging.

Anyway, I did research on Digic 7 / 8 / X EOS and found that they not only have this RGBA buffer, but can support many of them (which is not exercised by Canon until Digic 8 ).
Details are in this thread: https://www.magiclantern.fm/forum/index.php?topic=26024

I suspect Digic 6 will be similar, not sure if it has layers support, but with RGB buffer used to draw GUI and information that at lest one Digic 6 EOS has XimrExe call - I'm pretty sure that basic rules should apply there too.

[e]
And I just saw this thread, I was even mentioned there. It is funny to find how much research got duplicated :) But let me switch to mentioned thread.
https://chdk.setepontos.com/index.php?topic=12788.0
« Last Edit: 10 / April / 2021, 05:07:49 by kitor »
Logged
Magic Lantern / EOS R / 200D
Pages: 1 ... 15 16 17 18 19 [20] 21   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal