A propcase question... - page 3 - General Discussion and Assistance - CHDK Forum

A propcase question...

  • 28 Replies
  • 2877 Views
*

Offline Caefix

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: A propcase question...
« Reply #20 on: 31 / December / 2021, 11:16:13 »
Advertisements
Edit: 294 is i-contrast auto =1 else 0...  :)
Could also be added...  :)
Code: [Select]
#define PROPCASE_ICONTRAST                          //  0=off, 1=auto  // PS2=290, PS3=294, PS4=296, PS6=295, N/A=  9,12,ILC?
Edit2:
Sx240: PS5=296 //  0=off, 1=auto
S110:   PS5=318 (0,1,200,400), & 319 (0=off,200%,400%, 1=auto)

Edit: PS(3 & 4) same here =
Code: [Select]
#define PROPCASE_TV2                             265     // (philmoz, May 2011) - this value causes overrides to be saved in JPEG and shown on Canon OSD
Edit2: Set PS5(298), default 0 to -1, now is stable 65535, like PS3 & 6, nice for chaining scripts...
« Last Edit: 31 / December / 2021, 17:11:21 by Caefix »
All lifetime is a loan from eternity.

*

Offline reyalp

  • ******
  • 13792
Re: A propcase question...
« Reply #21 on: 31 / December / 2021, 17:02:05 »
Could also be added...  :)
Code: [Select]
#define PROPCASE_ICONTRAST                          //  0=off, 1=auto  // PS2=290, PS3=294, PS4=296, PS6=295, N/A=  9,12,ILC?
PS5=318 (0,1,200,400), & 319 (0=off,200%,400%, 1=auto)
Yes, I started doing this when I made the other change, but then it got complicated:
D10 (PS2):
icontrast is 290, 0 = off, 1 = auto

SX160 (PS5):
296, 318, 319 all 0 = off, 1 = auto
Which camera is your PS5?

Elph130 (PS6):
295, 317, 318 all 0 = off, 1 = auto

G7 X (PS7)
COMBO BREAKER
There is no icontrast setting. Instead, there are two settings: "DR correction" with values Off, Auto, and 200%, and Shadow Correction with Off and Auto.
"DR Correction" is propcase 325 as 0, 1 and 200 respectively.
"Shadow correction" is 303, 0 = off, 1 = Auto

SX710 (also PS7)
has icontrast, both 303 and 325 are 0=off, 1=auto

SX730 (PS12)
308, 330 0 = off, 1 = auto
(aside, also has "Safety Shift" in 234, 0=ff, 1=on)

Elph180 (PS10)
305, 327 0 = off, 1 = auto

This raises the some questions:
* How to name them, especially the cams that have 3. We could do ICONTRAST1, 2, 3, but from G7X they have different meaning in some cases.
* For cams with multiple props but only the icontrast setting, can we control shadow/DR separately using the props? Or use the 200, 400 values, or values in between?

Quote
Edit2: Set PS5(298) to -1, now is stable 65535, like PS3, nice for chaining scripts...
Again, I really wouldn't recommend using random, unknown propcases as variables. If you want information to persist between script runs, use a file.
Don't forget what the H stands for.

*

Offline Caefix

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: A propcase question...
« Reply #22 on: 31 / December / 2021, 17:48:29 »
Sx240: PS5=296 //  0=off, 1=auto  :blink:
S110:   PS5=296 always 0;  318 (0,1,200,400), & 319 (0=off,200%,400%, 1=auto)

 Sx270, PS6: 317=1 on, 318 =0/0

M3, PS9: Highlight Tone Priority (D+) 313 = 96 on 0 off
// if 313==96 then 325=200 else both 0.
  Auto Lightning Optimizer=536=0..3,
 Last=Pc616

M100: PS12 Highlight Tone Priority 318 = 96 on 0 off
// if 318==96 then 330=200 else both 0.
296,308,330 always 00, Auto Lightning Optimizer not found... Pc554=0..3;
406: 0=vga, 1=other video, 2= no video
  Last=Pc688

Well, PC298 seems a common stable scriptable PC from PS2 3-12, default 0, max=
Debug Propcasepage tells 65535, get_prop(298)=-1, if set to -1.  ???
« Last Edit: 04 / January / 2022, 13:21:52 by Caefix »
All lifetime is a loan from eternity.

*

Offline Caefix

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: A propcase question...
« Reply #23 on: 03 / January / 2022, 16:13:28 »
 :) Added for a temporary reason
Code: [Select]
// viewport.h
extern int shooting_get_prop(int id);

// histogram.c
int var;
...
    var=shooting_get_prop(298);
    // if (var==0) var=1;
... to catch mysterious values/factors downlevel without recompiling...
Code: [Select]
@title propcase 298
@chdk_version 1.4
@param    p Propcase (Debug=298)
 @default p 298
 @range   p 0 1000
@param    q Param
 @default q 0
 @range   q -1 0x7FFF

print  "PS";get_propset(),"PC:";p,"=",get_prop(p)
set_prop p q
sleep 300
print q,"?=",get_prop(p)
end
Edit: 298 not available on Ps 2 cams. :(, 270 & 271 could be used instead.
Edit: 288, default 0, seems unused in Ps2-14.
« Last Edit: 04 / January / 2022, 14:56:03 by Caefix »
All lifetime is a loan from eternity.


*

Offline philmoz

  • *****
  • 3441
    • Photos
Re: A propcase question...
« Reply #24 on: 04 / January / 2022, 02:49:29 »
PROPSET number has been added to camera_info.csv in the trunk version.


In case it is of any use I have attached a CSV file of all the current PROPSET names and values across the 13 files.

CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

*

Offline Caefix

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: A propcase question...
« Reply #25 on: 04 / January / 2022, 13:17:23 »
PROPSET number has been added to camera_info.csv in the trunk version.

In case it is of any use ...
:) It is...
Code: [Select]
#define PROPCASE_DIGITAL_ZOOM_STATE         94      //G10 Digital Zoom Mode
// &&
#define PROPCASE_ASPECT_RATIO                   294
seems wrong on Propset2 (Ix870)

Ps2 :  94 : Wide=0, 1 else  ???
        218 : 0=L, 1=M1, 2=M2, 3=M3+"Iso3600"+Video, 4=S, 8=Wide
Last PC=293?, setting 298 =>> cam freezing (sound 7)

Ps3 :  94 : Wide=0, 1 else
        220 : 0=L, 1=M1, 2=M2, 3=M3, 4=S, 8=Wide
Last PC=336?

// PC288 seems behaving same as 298, even on Ps2.
« Last Edit: 04 / January / 2022, 15:29:04 by Caefix »
All lifetime is a loan from eternity.

*

Offline reyalp

  • ******
  • 13792
Re: A propcase question...
« Reply #26 on: 08 / January / 2022, 21:31:38 »
Quote
In case it is of any use ...
:) It is...
Code: [Select]
#define PROPCASE_DIGITAL_ZOOM_STATE         94      //G10 Digital Zoom Mode
// &&
#define PROPCASE_ASPECT_RATIO                   294
seems wrong on Propset2 (Ix870)

Ps2 :  94 : Wide=0, 1 else  ???
Thanks for point this out. It confused me for quite a while. The propcase 94 definition dates back to r434 (July, 2008), and is used to by code that was tested on many cams since, how could it be the wrong propcase?  :-[

The answer is: It's not the wrong propcase. Setting W mode disables digital zoom. If you have Digital zoom set to "Standard" (prop 94 = 1), it becomes "Off" (prop 94 = 0) when you select W. (Tested on D10 / propset 2)
Don't forget what the H stands for.

*

Offline Caefix

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: A propcase question...
« Reply #27 on: 26 / January / 2022, 12:29:23 »
Quote
« Last Edit: 27 / January / 2022, 14:08:07 by Caefix »
All lifetime is a loan from eternity.


*

Offline Caefix

  • *****
  • 888
  • Sorry, busy deleting test shots...
Re: A propcase question...
« Reply #28 on: 27 / January / 2022, 14:05:14 »
All lifetime is a loan from eternity.

 

Related Topics