Powershot SX150 IS Porting Thread - page 25 - General Discussion and Assistance - CHDK Forum

Powershot SX150 IS Porting Thread

  • 279 Replies
  • 63282 Views
Re: Powershot SX150 IS Porting Thread
« Reply #240 on: 31 / January / 2015, 14:43:00 »
Advertisements
Update for capt_seq.c point:

Thanks for test build.

I've attached an updated version of OnePush and TwoPush testing results. The original test file (before the synch hook update) can be found here http://chdk.setepontos.com/index.php?topic=8810.msg118914#msg118914.

The change largely seems to work better than hoped for (see synch test results desciption below)!

Not yet understood:
  • There are two cases in which shooting automatically occurs at the point I would have thought a 10 second timeout was meant to occur.
  • There is one case where shooting occurs when a switch is activated after a 10 second period where I suspected a timeout should have occurred

I've also attached synch testing results related to 88 stereo pairs. I had assumed the capt_seq.c change had enabled "synch"and not precision sync so I am currently quite mystified by the high level of synchronisation (and rather pleased ;)).

The synch test was undertaken with remote parameters: OnePush / Normal / Synch enabled. The cameras were in M mode and in Manual focus (my predicted use case settings) - nevertheless, I had expected (based on the results here for the A1200 http://chdk.setepontos.com/index.php?topic=8312.msg107601#msg107601) much greater deviation and at least one or two large outliers. This was not the case - the largest variation was approx 5ms. I assume I have been extraordinarily lucky.

Of course there is always the possibility of test operator error  :) - but before I test several hundred more pairs to find some real outliers and greater deviation it'd be appreciated if an obvious mistake/reason can be identified  ::)   
 

*

Online reyalp

  • ******
  • 12147
Re: Powershot SX150 IS Porting Thread
« Reply #241 on: 31 / January / 2015, 16:38:59 »
Not yet understood:
1. There are two cases in which shooting automatically occurs at the point I would have thought a 10 second timeout was meant to occur.
If I have understood your post and PDF correctly, this is expected behavior: Once the camera is waiting in the remote hook (shot initiated, waiting for synced shoot signal), it cannot be canceled. A timeout just allows it to proceed unsynced so the camera isn't hung indefinitely.

Did you test with just the capt_seq.c code change, or with the build I posted? I'd like to know if the build still boots and is able to shoot correctly so I can check in the code-gen re-write.

If you can the fast MD change (explained in http://chdk.setepontos.com/index.php?topic=10864.msg115089#msg115089) that would also be appreciated.
Don't forget what the H stands for.

Re: Powershot SX150 IS Porting Thread
« Reply #242 on: 31 / January / 2015, 16:57:14 »
If I have understood your post and PDF correctly, this is expected behavior: Once the camera is waiting in the remote hook (shot initiated, waiting for synced shoot signal), it cannot be canceled. A timeout just allows it to proceed unsynced so the camera isn't hung indefinitely.

Makes sense now - thanks.

Did you test with just the capt_seq.c code change, or with the build I posted? I'd like to know if the build still boots and is able to shoot correctly so I can check in the code-gen re-write.

With the build you posted: everything worked as expected...on second thoughts I think there was a problem with the pallette - I had a problem selecting items in the remote menu as they "disapperared" when selected - if you need the specifics of that i'll try to recreate (it didn't hold me back though, I just had to "guess" a change then select the next item in the menu to see if I had got it right).

If you can the fast MD change (explained in http://chdk.setepontos.com/index.php?topic=10864.msg115089#msg115089) that would also be appreciated.

Every intention to - but if I spend any more time at this on Saturday night my wife has just said the shortening of my "telomeres" will be the least of my worries  :blink:

Edit:
"so I can check in the code-gen re-write."

Ah - understood. I'll check that out and get back in the MD post.
« Last Edit: 31 / January / 2015, 17:05:36 by andrew.stephens.754365 »

*

Online reyalp

  • ******
  • 12147
Re: Powershot SX150 IS Porting Thread
« Reply #243 on: 31 / January / 2015, 17:17:48 »
With the build you posted: everything worked as expected...on second thoughts I think there was a problem with the pallette - I had a problem selecting items in the remote menu as they "disapperared" when selected - if you need the specifics of that i'll try to recreate (it didn't hold me back though, I just had to "guess" a change then select the next item in the menu to see if I had got it right).
This sounds like the normal CHDK screen refresh issue where the canon firmware redraws and the CHDK doesn't know it needs to. None of my changes should have affected UI drawing.

Quote
Edit:
"so I can check in the code-gen re-write."

Ah - understood. I'll check that out and get back in the MD post.
I only converted capt_seq.c code gen (basically, a way of doing the assembler code that reduces the chances of typos). This isn't connected to the MD thing, so I have checked in the code gen and remote hook parts.
Don't forget what the H stands for.


Re: Powershot SX150 IS Porting Thread
« Reply #244 on: 01 / February / 2015, 12:48:36 »
1.3 -> 1.4 "possible pallette problem?" description

In your 1.4 test build (http://chdk.setepontos.com/index.php?topic=6953.msg120288#msg120288):

record/alt/menu -> dark grey background:
  • unselected items are white characters
  • selected item are character invisible

playback/alt/menu -> dark grey background:
  • unselected items are white characters
  • selected item are black characters


In 1.3.0 3721 100a (pre-built zip download from DE site I think):

record/alt/menu -> dark grey background:
  • unselected items are white characters
  • selected item is light grey (but discernible)

playback/alt/menu -> dark grey background:
  • unselected items are white characters
  • selected item are orange characters



Another outstanding problem with this port is that fast MD is not implemented: http://chdk.setepontos.com/index.php?topic=10864.msg115089#msg115089

I've attached a test build with the MD update, the remote hook change described in the previous post, and capt_seq converted to code gen.
I'm (really) not sure of my method, but so far...

using your build (and using MD_Tune.bas) then this

- turns on the AF led 1 second after the MD starts
does not occur.

If MD_tune does not turn on the AF LED, try calling set_led with 1 and 2 and let us know which one turns on the AF.
How? (I can't see "set_led" in the MD_Tune.bas script).


It would be good to know if the dark frame subtraction control works on this camera, since the hook for that is in the same location as the remote hook.
I'll do that asap.

Re: Powershot SX150 IS Porting Thread
« Reply #245 on: 01 / February / 2015, 13:28:56 »
1.3 -> 1.4 "possible pallette problem?" description
Did you try the Reset Options to Default ... menu item in the CHDK Settings menu?
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline philmoz

  • *****
  • 3128
    • Photos
Re: Powershot SX150 IS Porting Thread
« Reply #246 on: 01 / February / 2015, 13:37:43 »
1.3 -> 1.4 "possible pallette problem?" description
Did you try the Reset Options to Default ... menu item in the CHDK Settings menu?

'Reset ALL Colors' should work, and would be a bit less severe (CHDK Settings --> Color Settings).

Phil.
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)

Re: Powershot SX150 IS Porting Thread
« Reply #247 on: 01 / February / 2015, 13:47:42 »
Did you try the Reset Options to Default ... menu item in the CHDK Settings menu?

&

'Reset ALL Colors' should work, and would be a bit less severe (CHDK Settings --> Color Settings).

Thanks - I had tried neither  :-[

Unfortunately neither make any difference.


*

Online reyalp

  • ******
  • 12147
Re: Powershot SX150 IS Porting Thread
« Reply #248 on: 01 / February / 2015, 16:14:58 »
If MD_tune does not turn on the AF LED, try calling set_led with 1 and 2 and let us know which one turns on the AF.
How? (I can't see "set_led" in the MD_Tune.bas script).
With a script. If you are using ptp, you can do something like
Code: [Select]
=set_led(0,1)
=set_led(0,0)
=set_led(1,1)
=set_led(1,0)
etc.
set_led only knows about 3 LEDs on this camera, so 0-2 should be all you need to check

Quote
It would be good to know if the dark frame subtraction control works on this camera, since the hook for that is in the same location as the remote hook.
I'll do that asap.
For reference:
If the CHDK option is set to "Auto", the canon firmware should take a dark frame if the shutter speed is set >= 1.3 seconds in the Canon UI. The display will probably show "busy" for roughly the same time as the exposure time.

If the CHDK option is set to "Off", no dark frame should be taken.

If the CHDK option is set to "On" the dark frame should be taken with a Canon UI shutter speed < 1.3 seconds.

It sounds like your menu issue might related to the palette changes in 1.4, maybe phil can provide some help with that. You can use chdkptp to take a screenshot, either using the live tab in the GUI or lvdumpimg -bm
Don't forget what the H stands for.

*

Offline philmoz

  • *****
  • 3128
    • Photos
Re: Powershot SX150 IS Porting Thread
« Reply #249 on: 01 / February / 2015, 16:29:12 »
Did you try the Reset Options to Default ... menu item in the CHDK Settings menu?

&

'Reset ALL Colors' should work, and would be a bit less severe (CHDK Settings --> Color Settings).

Thanks - I had tried neither  :-[

Unfortunately neither make any difference.

Post screenshots of the record and playback mode palettes and I'll see if it can be easily fixed (or improved).
This port does not have custom colors implemented so it won't be ideal.

Phil.
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)

 

Related Topics