USB Remote Switch in CHDK - version 2 implementation thread - page 19 - General Discussion and Assistance - CHDK Forum
supplierdeeply
« previous next »
Pages: 1 ... 14 15 16 17 18 [19] 20 21 22 23   Go Down

USB Remote Switch in CHDK - version 2 implementation thread

  • 220 Replies
  • 74043 Views
*

Offline msl

  • *****
  • 1280
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: USB Remote Switch in CHDK - version 2 implementation thread
« Reply #180 on: 27 / April / 2014, 17:35:45 »
Advertisements
Quote from: mr.burns on 27 / April / 2014, 11:48:55
what is the 's' value for in function 'enable_highspeed_usb(s)?
Read waterwingz's description: http://chdk.setepontos.com/index.php?topic=7127.msg111731#msg111731

Quote from: mr.burns on 27 / April / 2014, 11:48:55
And what it has to do with the #define CAM_REMOTE_HIGHSPEED_LIMIT 0?
#define CAM_REMOTE_HIGHSPEED_LIMIT =>  Set lowest timer value settable by user.

msl
Logged
CHDK-DE:  CHDK-DE links
*

Offline mr.burns

  • ***
  • 223
Re: USB Remote Switch in CHDK - version 2 implementation thread
« Reply #181 on: 28 / April / 2014, 03:42:23 »
Hi msl,

thanks!
Logged
2 x IXUS 860IS 100c
2 x Powershot S110 103a
*

Offline Werner_O

  • *
  • 6
Re: USB Remote Switch in CHDK - version 2 implementation thread
« Reply #182 on: 05 / May / 2014, 18:25:21 »
Hello alltogether,

Quote
I think its time to enable this feature in the 1.3.0 trunk unless anyone has an objection?

This is exactly what I think. When will this feature be available for all?

Im really tired to handle with USB remotes, which do not do that what they should because of the current problem to recognize the USB impulse length exactly enough.

Kind regards
Werner_O
Logged
*

Offline waterwingz

  • ******
  • 12139
    • Waterwingz
Re: USB Remote Switch in CHDK - version 2 implementation thread
« Reply #183 on: 05 / May / 2014, 19:14:26 »
Quote from: Werner_O on 05 / May / 2014, 18:25:21
When will this feature be available for all?
I guess the short answer is that it will be available when there is consensus that it is not dangerous to do so.  (Which is different than saying it's safe to do so.)   I think that we are at that point.

Quote
Im really tired to handle with USB remotes, which do not do that what they should because of the current problem to recognize the USB impulse length exactly enough.
Note that this seems to be bigger problem with some cameras than others.  And that the built-in USB remote modes do not benefit from this patch - just scripting.
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline msl

  • *****
  • 1280
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: USB Remote Switch in CHDK - version 2 implementation thread
« Reply #184 on: 16 / May / 2014, 17:02:58 »
Quote from: waterwingz on 27 / April / 2014, 11:32:35
I think its time to enable this feature in the 1.3.0 trunk unless anyone has an objection?

*push*

The activation brings more insights.

msl
Logged
CHDK-DE:  CHDK-DE links
*

Offline msl

  • *****
  • 1280
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: USB Remote Switch in CHDK - version 2 implementation thread
« Reply #185 on: 29 / July / 2014, 09:18:02 »
I have a small problem when I use the usb remote control as key ("remote").

Code: [Select]
...
repeat
    wait_click(sleep)
    if is_key("remote") then
 ...
Is 'sleep' > 0 then is all fine. With 'sleep'=0 is_key("remote") does not work.

Is this a bug? Or is wait_click(0) and is_key("remote") not possible?

msl
Logged
CHDK-DE:  CHDK-DE links
*

Offline waterwingz

  • ******
  • 12139
    • Waterwingz
Re: USB Remote Switch in CHDK - version 2 implementation thread
« Reply #186 on: 29 / July / 2014, 09:30:14 »


Quote from: msl on 29 / July / 2014, 09:18:02
Is 'sleep' > 0 then is all fine. With 'sleep'=0 is_key("remote") does not work.  Is this a bug? Or is wait_click(0) and is_key("remote") not possible?
Can't look at this until tonight but I'm wondering if this works with a different key? Like is_key("menu") ?

Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline msl

  • *****
  • 1280
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: USB Remote Switch in CHDK - version 2 implementation thread
« Reply #187 on: 29 / July / 2014, 09:43:42 »
Quote from: waterwingz on 29 / July / 2014, 09:30:14
Can't look at this until tonight but I'm wondering if this works with a different key? Like is_key("menu") ?
Thanks for your reply.

Yes, it's works. The timeout value for wait_click is optional. Without argument or with 0 wait_click waits infinity to a key input. See also: => http://chdk.wikia.com/wiki/CHDK_scripting#wait_click

Without an argument for wait_click() I have the same problem with is_key("remote").

msl
Logged
CHDK-DE:  CHDK-DE links
*

Offline waterwingz

  • ******
  • 12139
    • Waterwingz
Re: USB Remote Switch in CHDK - version 2 implementation thread
« Reply #188 on: 29 / July / 2014, 09:49:16 »
So wait_click () is not checking the remote status for a change. Likely an oversight on my part two+ years ago but easy to fix. I'll take a look tonight.
« Last Edit: 29 / July / 2014, 10:01:05 by waterwingz »
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline msl

  • *****
  • 1280
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: USB Remote Switch in CHDK - version 2 implementation thread
« Reply #189 on: 29 / July / 2014, 09:59:43 »
Great. Thank you for your tireless engagement.

msl
Logged
CHDK-DE:  CHDK-DE links
Pages: 1 ... 14 15 16 17 18 [19] 20 21 22 23   Go Up
« previous next »
 

Related Topics