Making scripting support optional - page 8 - General Discussion and Assistance - CHDK Forum

Making scripting support optional

  • 83 Replies
  • 23143 Views
*

Offline ultimA

  • ***
  • 137
Re: Making scripting support optional
« Reply #70 on: 10 / January / 2011, 00:10:56 »
Advertisements
Sry about the quality of the badpixel stuff. I don't know how it got through, most probably I didn't delete the old badpixel.bin. I hope I didn't cause too much frustration.

*

Offline ultimA

  • ***
  • 137
Re: Making scripting support optional
« Reply #71 on: 10 / January / 2011, 00:22:31 »
I'm back at home (& work) at last, and I'll have access to the ixus55 again. I'll make sure to investigate some of the things reported earlier. The ixus55 has this problem of shooting in scripts pausing indefinitely, unless you press the ALT-button twice. But this has existed even before I started to submit patches and I never inspected that problem closer. It might be related to state_shooting_progress getting stuck. While stuck, try exiting & reentering ALT-mode, see if it continous where it paused. If it does, I1ll guess it is the same problem. For that of course you'll have to try without your quickfix. I'm also sorry about my reaction speed lately, but as I've said, I was on a trip so access to computer, internet (and free time) was scarce.

*

Offline hwntw

  • ***
  • 159
Re: Making scripting support optional
« Reply #72 on: 10 / January / 2011, 04:45:30 »

I am unsure where my ptpcam came from [?].

Maybe I gave it to you ?
Yes, indeed you did and thank you.

Colin
Ixus 300HS S100


Windows 10

*

Offline fe50

  • ******
  • 3134
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: Making scripting support optional
« Reply #73 on: 10 / January / 2011, 06:52:26 »
The ixus55 has this problem of shooting in scripts pausing indefinitely, unless you press the ALT-button twice. But this has existed even before I started to submit patches and I never inspected that problem closer. It might be related to state_shooting_progress getting stuck. While stuck, try exiting & reentering ALT-mode, see if it continous where it paused.

 :D
Hmm - the Ixus 55 still has the shoot issue (described very well here: http://chdk.setepontos.com/index.php/topic,677.0.html - Problem with SCRIPT_WAIT_SAVE in the Ixus55 port).

As described there we could remove the check for propcase 205, it works well with a safe value for 'Script Shoot Delay', e.g. 10 or 20 (tested & documented in the german forum, http://www.wirklemms.de/chdk/forum/viewtopic.php?t=729] - IXUS und der shoot - Befehl).

Substitute shoot with click xxxx works in most cases, but you have to adapt the script...
« Last Edit: 10 / January / 2011, 06:54:15 by fe50 »


*

Offline hwntw

  • ***
  • 159
Re: Making scripting support optional
« Reply #74 on: 10 / January / 2011, 08:16:21 »
Hello,
ptpcam testing result: Ixus 95 build 1040, compile otions- PTP TextReader LUA_CALL_NATIVE (boot fails without this last option).
Ptpcam commands seem to work, except  -c (Initiating captue...
Your camera does not support InitiateCapture operation!) and --chdk, which produces this error < ptpcam.exe --chdk
unexpected return code 0x2005
error: cannot get camera CHDK PTP version; either it has an unsupported version or no CHDK PTP support at all >
Interestingly, this version of ptpcam from the DE site, works the same and as well without CHDK booted, with plain Canon FW.

Edit
Microfunguy's version of ptpcam --chdk WILL execute, but the camera does not recognise the ptpcam --chdk shell commands

Colin
« Last Edit: 10 / January / 2011, 08:37:07 by hwntw »
Ixus 300HS S100


Windows 10

*

Online reyalp

  • ******
  • 13438
Re: Making scripting support optional
« Reply #75 on: 10 / January / 2011, 12:07:08 »
Hello,
ptpcam testing result: Ixus 95 build 1040, compile otions- PTP TextReader LUA_CALL_NATIVE (boot fails without this last option).
Ptpcam commands seem to work, except  -c
As I have told you several times, the non-chdk parts of PTPCAM (everything that doesn't involve --chdk) are not related to CHDK PTP, and should not be expected to work. Whether they work or not is completely unrelated to CHDK.

LUA_CALL_NATIVE is not required for PTP functionality, it only controls whether two additional functions are added in luascript.c


Don't forget what the H stands for.

Re: Making scripting support optional
« Reply #76 on: 10 / January / 2011, 13:18:38 »
Microfunguy's version of ptpcam --chdk WILL execute, but the camera does not recognise the ptpcam --chdk shell commands

I cannot remember if it does or does not.

PTP and ptpcam are right of the bottom of my 'to do' list.

Also, though not referring to you, I have become fed-up with people who make requests and then do not carry-out tests I request.

I will continue to work on features that I want.


David

*

Offline hwntw

  • ***
  • 159
Re: Making scripting support optional
« Reply #77 on: 10 / January / 2011, 15:13:58 »
Deleted by a craven coward
« Last Edit: 28 / January / 2011, 18:00:12 by hwntw »
Ixus 300HS S100


Windows 10


*

Offline ultimA

  • ***
  • 137
Re: Making scripting support optional
« Reply #78 on: 10 / January / 2011, 22:17:13 »
A zip of five tiny quickfixes:

00 - Do not save raw while creating badpixel.bin. badpixel.bin creation should become somewhat (neglibly?) shorter and won't waste space.
01 - Fix: I believe this could be a bug. state_shooting_progress is written/accessed in multiple OS threads but does not have volatile qualifier. Add it.
02 - Fix: PTP_CHDK_ScriptSupport query doesn't reflect if Lua is available
03 - Fix: If the user tries to use a script language that is not available, provide an error message instead of crashing the camera
04 - Fix: english.lng was updated earlier, but not gui_lang.c. Also, update hungarian and german translations accordingly.

*

Online reyalp

  • ******
  • 13438
Re: Making scripting support optional
« Reply #79 on: 11 / January / 2011, 00:13:35 »
A zip of five tiny quickfixes:

00 - Do not save raw while creating badpixel.bin. badpixel.bin creation should become somewhat (neglibly?) shorter and won't waste space.
01 - Fix: I believe this could be a bug. state_shooting_progress is written/accessed in multiple OS threads but does not have volatile qualifier. Add it.
If there is such a bug, volatile is unlikely to fix it. It definitely won't cover two tasks *writing* the same variable. One spinning waiting for another to write is theoretically a valid use of volatile, but doesn't apply here.

I'm sure there are concurrency problems floating around CHDK, but I'm not going to start throwing volatiles at things without a concrete demonstration that there is a problem, and that volatile is the correct solution. Not that the performance impact would be noticeable in this case, I just don't want to further the (almost always) mistaken belief that volatile solves concurrency problems.
Quote
02 - Fix: PTP_CHDK_ScriptSupport query doesn't reflect if Lua is available
03 - Fix: If the user tries to use a script language that is not available, provide an error message instead of crashing the camera
04 - Fix: english.lng was updated earlier, but not gui_lang.c. Also, update hungarian and german translations accordingly.
Thanks for these.
Don't forget what the H stands for.

 

Related Topics