sx700 porting - page 18 - DryOS Development - CHDK Forum  
« previous next »
Pages: 1 ... 13 14 15 16 17 [18] 19   Go Down

sx700 porting

  • 184 Replies
  • 103274 Views
*

Offline CanonUser9000

  • *
  • 27
  • A570 - S95 - S100 - SX220 - SX700 - EOSM
Re: sx700 porting
« Reply #170 on: 11 / January / 2021, 05:56:22 »
Advertisements
PropertyCases for Digic VI (SX700 and others)?

Hi,
has anyone newer information regarding PropertyCases https://chdk.fandom.com/wiki/PropertyCase#Digic_V_.28propset5.29 for this cams?

I've started some investigations on this topic using the script propdump.lua by Morris Johns (see https://chdk.fandom.com/wiki/PropertyCaseDump), however I feel this to be somewhat painfull because

1. this script logs at the bottom of the logfile only one difference found even if more than one differences exist and had been displayed at script end via the UI.

2. the log files are named with file types like .1, .2., ... what makes them unable to be opend with the CHDK text viewer directly on the cam (so after each script run the SD card has to be removed to display the results). File names like PROPDUMP1.LOG and so on would help here.

Unfortunately I'm not good at LUA scripting to modify propdump.lua. But if some with more knowledge would update propdump.lua to make it more convenient, I can offer to do deeper research on PropertyCases for SX700 and probably other Digic VI cams (if this might be valuable for other CHDK users).

Best regards

 
Logged
*

Offline reyalp

  • ******
  • 14080
Re: sx700 porting
« Reply #171 on: 11 / January / 2021, 13:17:40 »
Quote from: CanonUser9000 on 11 / January / 2021, 05:56:22
PropertyCases for Digic VI (SX700 and others)?
Generally, propsetN.h in the source (or CHDK/LUALIB/GEN/propsetN.lua) is the more comprehensive source these days. That wiki page isn't updated much, although there's probably some items that don't appear in the propset files.

sx700 is propset 6 http://tools.assembla.com/svn/chdk/trunk/include/propset6.h

For a completed port, the propset file should have all the commonly used props verified already, so additional research is only need if you want to do something unusual, or research for its own sake.

Note that propsets don't really correspond to digic version, there are digic 4 cameras, and most digic 6 cameras use other propsets.

Quote
2. the log files are named with file types like .1, .2., ... what makes them unable to be opend with the CHDK text viewer directly on the cam (so after each script run the SD card has to be removed to display the results). File names like PROPDUMP1.LOG and so on would help here.
I'm not familiar with that script, but FWIW, if you use the "text file reader" -> "open new file" menu item instead of going from the file browser, you should be able to open any file.

That said, my preferred to way to investigate propcases is the chdkptp devutil extension. See https://chdk.setepontos.com/index.php?topic=13569.msg138496#msg138496 for a brief explanation.
Logged
Don't forget what the H stands for.
*

Offline CanonUser9000

  • *
  • 27
  • A570 - S95 - S100 - SX220 - SX700 - EOSM
Re: sx700 porting
« Reply #172 on: 12 / January / 2021, 10:07:08 »
Thank's - that helps much!
Logged
*

Offline CanonUser9000

  • *
  • 27
  • A570 - S95 - S100 - SX220 - SX700 - EOSM
Re: sx700 porting
« Reply #173 on: 13 / January / 2021, 10:16:29 »
PropCase # 167: Direct timelaps video recording in (Full)HD with SX700 (and some others?)

Hi,
I have'nt found something about this feature on this forum so I've checked some PropCases from http://tools.assembla.com/svn/chdk/trunk/include/propset6.h, in particular

PROPCASE_VIDEO_FRAMERATE [167]

This PropCase is RW and has (at least for the SX700) the following additional values:
 3 = 240 fps
 4 = 120 fps
 5 =  60 fps
 9 =   6 fps *)
10 =   3 fps *)
11 = 1.5 fps *)

*) like used in MINIATURE mode (but this mode is HD only and blures top and bottom of the video).

I do not belive that video recording may be driven beyond the HW limits with this, but setting PropCase # 167 allows direct timelaps recording in (Full)HD. So the usual CHDK process to take a series of still pictures and generate the TL video in post is much easier now for this series of cams. To do TL video without any blur (like in MINIATURE mode) I've done the small script TL_FHDe.bas attached.

Have fun and share Your experience.

In addition setting PropCase # 167 via an override option from the CHDK menu may be a topic developers can hook on.
Logged
*

Offline CanonUser9000

  • *
  • 27
  • A570 - S95 - S100 - SX220 - SX700 - EOSM
Re: sx700 porting
« Reply #174 on: 21 / January / 2021, 09:00:23 »
CHDK OSD: Show Remaining Videotime

The CHDK menu on the SX700 provides an option to display Remaining Videotime [ Don’t, hh:mm:ss, KB/s, both ].

However this display is not updated correctly during video recording - pls see attached screen shoot. Is there a chance to fix that at one of the next builds?
Logged
*

Offline reyalp

  • ******
  • 14080
Re: sx700 porting
« Reply #175 on: 21 / January / 2021, 14:08:23 »
Quote from: CanonUser9000 on 21 / January / 2021, 09:00:23
CHDK OSD: Show Remaining Videotime

The CHDK menu on the SX700 provides an option to display Remaining Videotime [ Don’t, hh:mm:ss, KB/s, both ].

However this display is not updated correctly during video recording - pls see attached screen shoot. Is there a chance to fix that at one of the next builds?
Probably not, at least not without significant reverse engineering. Digic 6 cameras don't appear to update the free disk space while recording.
Logged
Don't forget what the H stands for.
*

Offline srsa_4c

  • ******
  • 4451
Re: sx700 porting
« Reply #176 on: 21 / January / 2021, 15:23:10 »
Quote from: reyalp on 21 / January / 2021, 14:08:23
Digic 6 cameras don't appear to update the free disk space while recording.
I believe I found a version of GetDrive_FreeClusters that updates during recording. I mis-identified it as GetDrive_TotalClusters in the M10 port, only corrected it in changeset 5633. You could try identifying it in your cams, it's the first routine with an AvailClusters.c assert.
If my guess is correct, the stub for sx700 is 0xFC0668E7 (100d and 100e).
Logged
*

Offline reyalp

  • ******
  • 14080
Re: sx700 porting
« Reply #177 on: 22 / January / 2021, 00:50:29 »
Quote from: srsa_4c on 21 / January / 2021, 15:23:10
I believe I found a version of GetDrive_FreeClusters that updates during recording. I mis-identified it as GetDrive_TotalClusters in the M10 port, only corrected it in changeset 5633. You could try identifying it in your cams, it's the first routine with an AvailClusters.c assert.
If my guess is correct, the stub for sx700 is 0xFC0668E7 (100d and 100e).
Hmm, on G7X, the equivalent of that function (100d fc06e693) appears to return exactly the same value as the current GetDrive_FreeClusters, including not updating while recording video.

@CanonUser9000 if you want to test, here's a build for sx700 100e using the function srsa_4c mentioned
Logged
Don't forget what the H stands for.
*

Offline CanonUser9000

  • *
  • 27
  • A570 - S95 - S100 - SX220 - SX700 - EOSM
Re: sx700 porting
« Reply #178 on: 22 / January / 2021, 09:40:25 »
@reyalp:
Thank's a lot for the testbuild.
Unfortunately there is no change regarding the OSD during video recording - display ist still "0000 KB/s  -00:00:01" on the SX700.
Logged
*

Offline srsa_4c

  • ******
  • 4451
Re: sx700 porting
« Reply #179 on: 22 / January / 2021, 13:56:17 »
Quote from: reyalp on 22 / January / 2021, 00:50:29
Hmm, on G7X, the equivalent of that function (100d fc06e693) appears to return exactly the same value as the current GetDrive_FreeClusters, including not updating while recording video.
Yeah, I'm getting the same result on the sx280. Newer models, such as g5x and sx730, have a function that looks identical to the one in m10. I guess it's possible that those cams behave like the m10.
Logged
Pages: 1 ... 13 14 15 16 17 [18] 19   Go Up
« previous next »
 

Related Topics