Multiple Bug's (Live View / Zoom / Shoot) - page 7 - General Discussion and Assistance - CHDK Forum

Multiple Bug's (Live View / Zoom / Shoot)

  • 73 Replies
  • 2057 Views
*

Offline reyalp

  • ******
  • 12102
Re: Multiple Bug's (Live View / Zoom / Shoot)
« Reply #60 on: 28 / September / 2019, 21:58:25 »
Advertisements
It draws two numbers permanently on screen. First one would increase when setting focus failed due to a focus_busy timeout, second one would increase when focus was busy but did not time out. I've yet to find a camera where any of those numbers change from zero. Does anyone want test builds with this change?
I tried this on my cams (a540, d10, sx160, elph130, elph180, g7x, sx710hs). Tested using set_zoom, in various shooting and focus modes.

Never saw the numbers change from 0:0

This isn't due to your code, but both SX710 and G7X crash after set_zoom in video mode, unless MF or AF lock is set. They appear to be in continuous AF (propcase is 1), with no option to disable it outside of MF/AF Lock. shooting_can_focus has an exception that always allows SD over in movie mode, regardless of the propcase.
Interestingly the focus_busy check does not prevent this. I can't tell if the check is hit before it crashes.

edit:
g7x crash is
ASSERT!! FocusLensController.c Line 1106
Task name: PhySw

sx710
ASSERT!! FocusLensController.c Line 1063
Task name: PhySw
« Last Edit: 29 / September / 2019, 14:23:27 by reyalp »
Don't forget what the H stands for.

*

Offline Caefix

  • *
  • 39
  • Sorry, busy deleting test shots...
Re: Multiple Bug's (Live View / Zoom / Shoot)
« Reply #61 on: 03 / October / 2019, 13:55:13 »
 ??? Sx710...
Code: [Select]
!! Romlogs´ timestamp doesn´t add summertime hour !!

Wed Oct  2 21:13:05 2019,MF Test 3.1 Log
sx710hs,101a,CHDK_DE,1.5.0-5278
Mode:P,Continuous_AF:1,Servo_AF:0
tests : set_focus:1, set_aflock:1, set_mf:1, bypass:1
test,set,actual,result,prop.FOCUS_STATE,prop.AF_LOCK,prop.FOCUS_MODE,prop.REAL_FOCUS_MODE
1) Testing initial conditions
...interlock bypass function available
...set_mf function available
...start, , , ,0,0,0,0
...shot1,1190,2586,failed,0,0,0,0
2) Testing set_focus() only
...start, , , ,0,0,0,0
ASSERT!! FocusLensController.c Line 1063
Occured Time  2019:10:02 20:13:24
Task ID: 18939945
Task name: CaptSeqTask


Wed Oct  2 21:16:36 2019,MF Test 3.1 Log
sx710hs,101a,CHDK_DE,1.5.0-5278
Mode:P,Continuous_AF:0,Servo_AF:0
tests : set_focus:1, set_aflock:1, set_mf:1, bypass:1
test,set,actual,result,prop.FOCUS_STATE,prop.AF_LOCK,prop.FOCUS_MODE,prop.REAL_FOCUS_MODE
1) Testing initial conditions
...interlock bypass function available
...set_mf function available
...start, , , ,0,0,0,0
...shot1,2586,-1,focus_failure,1,0,0,0
2) Testing set_focus() only
...start, , , ,1,0,0,0
ASSERT!! FocusLensController.c Line 1063
Occured Time  2019:10:02 20:16:50
Task ID: 18939945
Task name: CaptSeqTask


Wed Oct  2 21:20:49 2019,MF Test 3.1 Log
sx710hs,101a,CHDK_DE,1.5.0-5278
Mode:P,Continuous_AF:0,Servo_AF:0
tests : set_focus:1, set_aflock:1, set_mf:1, bypass:0
test,set,actual,result,prop.FOCUS_STATE,prop.AF_LOCK,prop.FOCUS_MODE,prop.REAL_FOCUS_MODE
1) Testing initial conditions
...interlock bypass function available
...set_mf function available
...start, , , ,0,0,0,0
...shot1,2160,513,failed,1,0,0,0
2) Testing set_focus() only
...start, , , ,1,0,0,0
...shot1,400,607,failed,1,0,0,0
...shot2,800,666,passed,1,0,0,0
3) Testing set_aflock()
...start, , , ,1,0,0,0
...set_aflock(1), , , ,1,1,0,0
set_prop.AF_LOCK(1)
...start, , , ,1,1,0,0
...shot1,600,607,passed,1,1,0,0
...shot2,1000,950,passed,1,1,0,0
...set_prop.AF_LOCK(0), , , ,1,0,0,0
...set_aflock(0), , , ,1,0,0,0
4) Testing set_mf()
...start, , , ,1,0,0,0
set_mf
...start, , , ,0,0,1,1
...shot1,800,833,passed,0,0,1,1
...shot2,1200,1296,passed,0,0,1,1
...set_mf, , , ,0,0,0,0
5) Done
Wed Oct  2 22:12:41 2019,MF Test 3.1 Log
sx710hs,101a,CHDK_DE,1.5.0-5278
Mode:P,Continuous_AF:0,Servo_AF:0
tests : set_focus:0, set_aflock:1, set_mf:1, bypass:0
test,set,actual,result,prop.FOCUS_STATE,prop.AF_LOCK,prop.FOCUS_MODE,prop.REAL_FOCUS_MODE
1) Testing initial conditions
...interlock bypass function available
...set_mf function available
...start, , , ,0,0,0,0
...shot1,2843,468,failed,1,0,0,0
2) Testing set_focus() only
   ..disabled
3) Testing set_aflock()
...start, , , ,1,0,0,0
...set_aflock(1), , , ,1,1,0,0
set_prop.AF_LOCK(1)
...start, , , ,1,1,0,0
...shot1,600,594,passed,1,1,0,0
...shot2,1000,1059,passed,1,1,0,0
...set_prop.AF_LOCK(0), , , ,1,0,0,0
...set_aflock(0), , , ,1,0,0,0
4) Testing set_mf()
...start, , , ,1,0,0,0
set_mf
...start, , , ,0,0,1,1
...shot1,800,807,passed,0,0,1,1
...shot2,1200,1241,passed,0,0,1,1
...set_mf, , , ,0,0,0,0
ASSERT!! LiveImageTask.c Line 261
Occured Time  2019:10:02 21:13:26
Task ID: 9764880
Task name: _imageSensor4


Wed Oct  2 22:15:37 2019,MF Test 3.1 Log
sx710hs,101a,CHDK_DE,1.5.0-5278
Mode:P,Continuous_AF:0,Servo_AF:0
tests : set_focus:0, set_aflock:1, set_mf:1, bypass:1
test,set,actual,result,prop.FOCUS_STATE,prop.AF_LOCK,prop.FOCUS_MODE,prop.REAL_FOCUS_MODE
1) Testing initial conditions
...interlock bypass function available
...set_mf function available
...start, , , ,0,0,0,0
...shot1,2354,1356,failed,1,0,0,0
2) Testing set_focus() only
   ..disabled
3) Testing set_aflock()
...start, , , ,1,0,0,0
...set_aflock(1), , , ,1,1,0,0
set_prop.AF_LOCK(1)
...start, , , ,1,1,0,0
...shot1,600,621,passed,1,1,0,0
...shot2,1000,984,passed,1,1,0,0
...set_prop.AF_LOCK(0), , , ,1,0,0,0
...set_aflock(0), , , ,1,0,0,0
4) Testing set_mf()
...start, , , ,1,0,0,0
set_mf
...start, , , ,0,0,1,1
...shot1,800,859,passed,0,0,1,1
...shot2,1200,1356,passed,0,0,1,1
...set_mf, , , ,0,0,0,0



Autozum4 -->>
ASSERT!! ComputerZoom.c Line 2148
Occured Time  2019:10:02 21:25:58
Task ID: 15007773
Task name: CZ
All lifetime is a loan from eternity.

*

Offline srsa_4c

  • ******
  • 3998
Re: Multiple Bug's (Live View / Zoom / Shoot)
« Reply #62 on: 03 / October / 2019, 16:55:36 »
I tried this on my cams (a540, d10, sx160, elph130, elph180, g7x, sx710hs). Tested using set_zoom, in various shooting and focus modes.

Never saw the numbers change from 0:0
Thanks.
Now I start to wonder whether this check actually does something on sx210, 230, or is it some kind of voodoo that the last ztest builds (apparently?) survived set_zoom'ing.

Quote
This isn't due to your code, but both SX710 and G7X crash after set_zoom in video mode, unless MF or AF lock is set. They appear to be in continuous AF (propcase is 1), with no option to disable it outside of MF/AF Lock. shooting_can_focus has an exception that always allows SD over in movie mode, regardless of the propcase.
I guess an extra check in shooting_set_zoom() could help with that.

How about sx50hs-100c testbuild?
Included in the attached pack. Diskboot.bin files are in separate directories in the archive, copy them to the card root when testing a camera.
Please watch the numbers displayed in the top left corner while testing and tell us if you see anything else than 0:0 there.
Quote
Is there a check (zoom_busy or focus_busy) in get_shooting() ?
There is no such check.

Quote
PS: a list of some other distorted cams ):(( Ixus 120,125,130,230,240,310,870+980, S90,95, SX 200
      Some Zoom lever issues: SX 200,220,240,260,610
Please add firmware version to the list.

Difference from the last patch:
Code: [Select]
Index: platform/sx200is/platform_camera.h
===================================================================
--- platform/sx200is/platform_camera.h (revision 5278)
+++ platform/sx200is/platform_camera.h (working copy)
@@ -94,6 +94,10 @@
 
     #define CAM_HAS_FILEWRITETASK_HOOK      1
 
+    #define CAM_USE_OPTICAL_MAX_ZOOM_STATUS 1   // Use ZOOM_OPTICAL_MAX to reset zoom_status when switching from digital to optical zoom in gui_std_kbd_process()
+    #define CAM_USE_ALT_SET_ZOOM_POINT      1    // Define to use the alternate code in lens_set_zoom_point()
+    #define CAM_USE_ALT_PT_MoveOpticalZoomAt 1    // Define to use the PT_MoveOpticalZoomAt() function in lens_set_zoom_point()
+
     #define CAM_SD_OVER_IN_AF               1
     #define CAM_SD_OVER_IN_AFL              1
     #define CAM_SD_OVER_IN_MF               1

*

Offline Caefix

  • *
  • 39
  • Sorry, busy deleting test shots...
Re: Multiple Bug's (Live View / Zoom / Shoot)
« Reply #63 on: 04 / October / 2019, 13:49:26 »
?? which numbers ( :blink: : :blink: ) There´s the bat-icon...
My buggy sx230 (auto only, dead mode-dial)
 1st impression & romlogs...
-- zoom lever issue is back. (unexpected complication of buggy cam)

 >:( How to crash Sx200 ?? :haha
Distortion is gone,
Zoom lever issues: is_pressed gives a beep, no move; is_key 1-3 clicks.
btw. S90 flows as stable, )( only.
     Ixus145 survives all mftest settings, but none set_zoom. ( )(? )
!! bi.platform() get´s info from ps.fi2, so that loglines could be confusing...
--- :...,....1....,....2....,....3....,....4....,....5....,....6....,....7....,....
)( : Ixus 120_100e, 125_101a, 130_100c, 230_100e, 240_101a, 310_101a, 870_102b + 980_101b
     S90_101c,S95_100h
Some Zoom lever issues: SX 200_100c ,220_101a, 240_100c, 260_100c, 610_100a
« Last Edit: 08 / October / 2019, 12:48:01 by Caefix »
All lifetime is a loan from eternity.


*

Offline srsa_4c

  • ******
  • 3998
Re: Multiple Bug's (Live View / Zoom / Shoot)
« Reply #64 on: 09 / October / 2019, 14:27:52 »
?? which numbers ( :blink: : :blink: ) There´s the bat-icon...
The "bat icon" is actually 0:0 (zero, colon, zero). Have you seen those zeroes change while running zoom and focus tests? If they never change from zero, that would mean my zoom related patch is completely useless.
Quote
Some Zoom lever issues: SX 200_100c ,220_101a, 240_100c, 260_100c, 610_100a
I suspect all these have multi-speed zoom, and it's likely the order of KEY_ZOOM_OUT/KEY_ZOOM_IN entries in keymap that causes problems. Except for sx610 where they zoom key definition might be incomplete/wrong (blind port). I'll make test builds for these later.

*

Offline Caefix

  • *
  • 39
  • Sorry, busy deleting test shots...
Re: Multiple Bug's (Live View / Zoom / Shoot)
« Reply #65 on: 09 / October / 2019, 14:43:35 »
I never saw any 0:0 or else.
Is any menu´s setting disturbing?
Nevertheless Sx210 & 230 work fine now.
I added get_tick_count(), to autozum5.lua lines, maybe that tells something together with romlogs´ timestamps.
 (I don´t know what is unimportant...)

Starting Sx210ztest6 menues´current line is red on amber,
running script makes it transparent in white. Any Context?
Well, transparent numbers would be a first honest step to save the world...  :D
« Last Edit: 10 / October / 2019, 12:27:12 by Caefix »
All lifetime is a loan from eternity.

*

Offline srsa_4c

  • ******
  • 3998
Re: Multiple Bug's (Live View / Zoom / Shoot)
« Reply #66 on: 11 / October / 2019, 19:02:58 »
I never saw any 0:0 or else.
See attached image for a hint.

Also attached is an archive with test builds for 3 of your cams. This test is for the zoom lever issue: all these cams have multi-speed zoom, I changed the order of zoom key definitions in kbd.c.
I'd like to note that the chdkptp zoom buttons do work on my sx280 with or without this change, so it's possible that these test builds won't solve the problem.

Quote
Starting Sx210ztest6 menues´current line is red on amber,
running script makes it transparent in white.
So, the CHDK menu colors change after running a script? Have any photos?

*

Offline Caefix

  • *
  • 39
  • Sorry, busy deleting test shots...
Re: Multiple Bug's (Live View / Zoom / Shoot)
« Reply #67 on: 12 / October / 2019, 14:28:41 »
 :-[ More )( : Ixus115_101b, 200_101c, SX40_100i
other ZoomLeverIssues: SX40, SX50, all are multispeed zoom.
SX40 ZL blocks in nonalt if Zoom!=0

Tested ZLI sx200,220,240 no success.
SX50 threw 2x MotionVector in Auto, 2nd immediately after starting !helperl.bas

Ixus200 is some chameleon, even colored console, inspires a set_color_statement. HowToDo?
-> Colors depend on playmode on some cams.
« Last Edit: Yesterday at 10:52:16 by Caefix »
All lifetime is a loan from eternity.


*

Offline srsa_4c

  • ******
  • 3998
Re: Multiple Bug's (Live View / Zoom / Shoot)
« Reply #68 on: Yesterday at 12:47:06 »
Tested ZLI sx200,220,240 no success.
That's too bad. Unfortunately, none of my cameras have this problem, which means I can't do research to find out the reason.

Quote
-> Colors depend on playmode on some cams.
The menu (and CHDK) colors do depend on camera mode on many cameras, that's normal. There is a palette viewer in the CHDK menu, you can see the available colors for yourself.

About zoom testing.
I asked you several times to please watch that 0:0 debug display while you test. The only thing I currently care are those numbers. If you never see anything else than 0:0, that means the "solution" you're currently testing is not a solution.

*

Offline Caefix

  • *
  • 39
  • Sorry, busy deleting test shots...
Re: Multiple Bug's (Live View / Zoom / Shoot)
« Reply #69 on: Yesterday at 13:46:04 »
 :( What happened between...?
All lifetime is a loan from eternity.

 

Related Topics