A propcase question... - page 2 - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: 1 [2] 3   Go Down

A propcase question...

  • 28 Replies
  • 7779 Views
*

Offline reyalp

  • ******
  • 14125
Re: A propcase question...
« Reply #10 on: 15 / October / 2020, 14:44:20 »
Advertisements
Quote from: Caefix on 15 / October / 2020, 12:58:37
:( The propcase question is answered, but this batteries keep a trap.
So, the problem is the AF frame setting is lost when the RTC battery is dead? Which camera(s) have you seen this on?

It's possible this setting can be set using UI properties.
Logged
Don't forget what the H stands for.
*

Offline Caefix

  • *****
  • 948
  • Sorry, busy deleting test shots...
Re: A propcase question...
« Reply #11 on: 24 / December / 2021, 10:06:59 »
Quote from: reyalp on 15 / October / 2020, 14:44:20
Quote from: Caefix on 15 / October / 2020, 12:58:37
:( The propcase question ...
So, the problem is the AF frame setting is lost when the RTC battery is dead? Which camera(s) have you seen this on?
That had other reason, I missed to shutdown cam after important settings before shotdowns
in the ) Ork of distortion ( battles.  :haha

At propset 3
Quote
#define PROPCASE_ASPECT_RATIO               294
doesn´t recognize the WIDE=16:9 setting, (const.1)   :blink:
So md_grid is always full display, related measurements calculate the black borders, affecting histogram, md_,...   :-[
Logged
All lifetime is a loan from eternity.
*

Offline reyalp

  • ******
  • 14125
Re: A propcase question...
« Reply #12 on: 24 / December / 2021, 16:30:52 »
Quote from: Caefix on 24 / December / 2021, 10:06:59
Quote
#define PROPCASE_ASPECT_RATIO               294
doesn´t recognize the WIDE=16:9 setting, (const.1)   :blink:
So md_grid is always full display, related measurements calculate the black borders, affecting histogram, md_,...   :-[
Does propcase 294 change when you change the aspect ratio in the Canon UI? Or do you mean it doesn't respond when you use set_prop? Which specific camera?
Logged
Don't forget what the H stands for.
*

Offline Caefix

  • *****
  • 948
  • Sorry, busy deleting test shots...
Re: A propcase question...
« Reply #13 on: 25 / December / 2021, 11:05:09 »
get_prop(294)=1 ... ??? Ix300  in Auto , LowLight & HS-Burst; s90 in A & LL; else 0.
Code: [Select]
++ #define PROPCASE_SERVO_AF                   297     // 0 = Servo AF off, 1 = Servo AF on,  2=ModeAuto
« Last Edit: 25 / December / 2021, 11:18:55 by Caefix »
Logged
All lifetime is a loan from eternity.
*

Offline reyalp

  • ******
  • 14125
Re: A propcase question...
« Reply #14 on: 25 / December / 2021, 17:08:27 »
Quote from: Caefix on 25 / December / 2021, 11:05:09
get_prop(294)=1 ... ??? Ix300  in Auto , LowLight & HS-Burst; s90 in A & LL; else 0.
Code: [Select]
++ #define PROPCASE_SERVO_AF                   297     // 0 = Servo AF off, 1 = Servo AF on,  2=ModeAuto

As you suggest, 294 seems wrong, because it's the same as propset 2, while other nearby propcases are moved.

If SERVO_AF moved by +4 (293 in PS2, 297 in PS3), it's a good guess the next one has as well.

Please:
1) Confirm that SERVO_AF is, in fact, on 297, changing from 0 to 1 depending on the Servo AF setting in the canon menu
2) Check the values of 298 when you change aspect ratio

However, on my propset 1 and 2 cams (A540 and D10), W doesn't change aspect ratio. It just adds black bars to the UI, without changing the viewport resolution. This means from a CHDK POV, it's not really an aspect ratio change. Anything that reads the buffer uses the same values as 4:3, and if zebra, edge, etc overwrites the black bars, it doesn't really matter.

So please check with PTP live view, if yo turn UI overlay off, does live view show normal image where the black bars are in W?

The comment on the wiki (https://chdk.fandom.com/wiki/PropertyCase) suggests 294 reflected some different behavior on SX1, but skimming the posts I'm not clear exactly what.
Logged
Don't forget what the H stands for.
*

Offline Caefix

  • *****
  • 948
  • Sorry, busy deleting test shots...
Re: A propcase question...
« Reply #15 on: 26 / December / 2021, 10:09:35 »
 :D 1) Confirmed that SERVO_AF is, in fact, on 297, changing from 0 to 1 depending on the Servo AF setting in the canon menu && changing to 2 in Auto.
 :-* 2) Checked the values of 298 when you change aspect ratio. No chance.
 :( 3)
Quote
This means from a CHDK POV, it's not really an aspect ratio change.

       So please check with PTP live view, if ...
:-[ 4) a) Yes, ...
Code: [Select]
> exec require'camtests'.runbatch{bench=true,shoot=true,filexfer=true,xfersizebugs=true}
passed 22
failed 4
Edit: 294 is i-contrast auto =1 else 0...  :)
« Last Edit: 26 / December / 2021, 11:19:30 by Caefix »
Logged
All lifetime is a loan from eternity.
*

Offline reyalp

  • ******
  • 14125
Re: A propcase question...
« Reply #16 on: 28 / December / 2021, 21:13:16 »
Quote from: Caefix on 26 / December / 2021, 10:09:35
Edit: 294 is i-contrast auto =1 else 0...  :)
Thanks. In trunk 6029, stable 6030 I updated PS3 so PROPCASE_ASPECT_RATIO is 298, since this is likely equivalent to the PS2 prop, and having it on a propcase that represents something completely different is worse.

Notes for future reference:
The story with PROPCASE_ASPECT_RATIO on PS2 (and probably PS3) is mess. It was apparently introduced for SX1 (via the note on the propcase wiki https://chdk.setepontos.com/index.php?topic=3410.msg32416#msg32416), which was an early (first?) supported camera with a physical 16:9 screen. It is the only camera that defines CAM_HAS_VARIABLE_ASPECT, which in turn goes into camera_info and is used in the zebra module (in draw_zebra_no_aspect_adjust  >:(). The zebra logic that references PROPCASE_ASPECT_RATIO is only used if  CAM_HAS_VARIABLE_ASPECT is set. This SX1 special case could probably be removed by making it use draw_zebra_aspect_adjust, but I don't feel like trying to do that blind.

Later propsets use the aspect ratio prop in their lib.c for viewport functions, but not directly in the zebra module.

Quote
Code: [Select]
> exec require'camtests'.runbatch{bench=true,shoot=true,filexfer=true,xfersizebugs=true}
passed 22
failed 4
If you post the output, I can check whether the failures are something that needs attention.
Logged
Don't forget what the H stands for.
*

Offline Caefix

  • *****
  • 948
  • Sorry, busy deleting test shots...
Re: A propcase question...
« Reply #17 on: 30 / December / 2021, 11:01:19 »
DILITIT  >:(~~*  :o
« Last Edit: 31 / December / 2021, 11:23:26 by Caefix »
Logged
All lifetime is a loan from eternity.
*

Offline reyalp

  • ******
  • 14125
Re: A propcase question...
« Reply #18 on: 30 / December / 2021, 13:52:20 »
Quote from: Caefix on 30 / December / 2021, 11:01:19
PS 298 is a Joker, default 0, You can set a stable value for following scripts
It most likely behaves similar to sx1, if there are any PS3 cams with equivalent display setup.

Quote
Edit: How about appending cam´s propcase to the camera_info.csv lines?
Seems reasonable to me.
Logged
Don't forget what the H stands for.
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: A propcase question...
« Reply #19 on: 30 / December / 2021, 15:50:08 »
Quote from: Caefix on 30 / December / 2021, 11:01:19
Edit: How about appending cam´s propcase to the camera_info.csv lines?


camera_info.csv is currently generated only from values found in the makefiles, not the source code.
Adding the propset value would require parsing the platform_camera.h file.

Logged
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)
Pages: 1 [2] 3   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal