Undocumented uBASIC commands. - General Help and Assistance on using CHDK stable releases - CHDK Forum  

Undocumented uBASIC commands.

  • 8 Replies
  • 2590 Views
Undocumented uBASIC commands.
« on: 21 / March / 2008, 14:35:05 »
Advertisements
Deleted
« Last Edit: 22 / April / 2008, 14:37:31 by Barney Fife »
[acseven/admin commented out: please refrain from more direct offensive language to any user. FW complaints to me] I felt it imperative to withdraw my TOTAL participation. Nobody has my permission, nor the right, to reinstate MY posts. Make-do with my quoted text in others' replies only. Bye

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Undocumented uBASIC commands.
« Reply #1 on: 21 / March / 2008, 19:55:01 »
« Last Edit: 21 / March / 2008, 20:26:52 by PhyrePhoX »

Re: Undocumented uBASIC commands.
« Reply #2 on: 21 / March / 2008, 22:35:51 »
Deleted
« Last Edit: 22 / April / 2008, 14:37:51 by Barney Fife »
[acseven/admin commented out: please refrain from more direct offensive language to any user. FW complaints to me] I felt it imperative to withdraw my TOTAL participation. Nobody has my permission, nor the right, to reinstate MY posts. Make-do with my quoted text in others' replies only. Bye

*

Offline Jucifer

  • *****
  • 251
  • [A710IS]
Re: Undocumented uBASIC commands.
« Reply #3 on: 22 / March / 2008, 08:00:53 »
« Last Edit: 22 / March / 2008, 08:45:40 by Jucifer »


Re: Undocumented uBASIC commands.
« Reply #4 on: 23 / March / 2008, 02:12:38 »
Deleted
« Last Edit: 22 / April / 2008, 14:38:13 by Barney Fife »
[acseven/admin commented out: please refrain from more direct offensive language to any user. FW complaints to me] I felt it imperative to withdraw my TOTAL participation. Nobody has my permission, nor the right, to reinstate MY posts. Make-do with my quoted text in others' replies only. Bye

*

Offline Jucifer

  • *****
  • 251
  • [A710IS]
Re: Undocumented uBASIC commands.
« Reply #5 on: 23 / March / 2008, 06:43:26 »
No need for the () when scripting. But yes, proper documentation on everything would be nice. Nowadays most of the "special build" (fingalo, allbest) commands are in the trunk, so perhaps the whole ubasic scripting tutorial page should be revised? (Now that I remember; note to anyone, including self: that new parameter for md_detect_motion should also be properly documented...)

*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: Undocumented uBASIC commands.
« Reply #6 on: 23 / March / 2008, 07:26:17 »
(Now that I remember; note to anyone, including self: that new parameter for md_detect_motion should also be properly documented...)

Hmm... I believe you mean the OR'ed '8' bit in the 'PARAMETERS' argument of md_detect_motion, existing in allbest 34 and later if I'm not mistaken... 3 bits (1,2,4 decimal) used to be available, now there are 4:

1: make immediate shoot (shutter is pressed and released by md_detect_motion when motion is detected, to minimize the delay between detection and shooting)
2: log debug information into a file
4: dump liveview image from RAM to a file
8: when making immediate shoot, do not release shutter (the script can then decide how long to keep shutter depressed, for programmed continuous shooting length or photo review time when in single shoot mode). Currently will not affect operation unless '1' is also enabled.

Values must be logical OR'ed to enable more than one (sum the numbers of desired features together, for example to enable immediate shoot and no-shutter-release-on-immediate shoot but not others, set PARAMETERS to 9).

The RAM dump bit is missing from wiki as well, not that I really know or remember what it does (exactly which image is saved, to which file and in what format). The debug log bit should also be documented in a bit more detail (ie what debug info is written and to which file). I think they are mentioned elsewhere on this forum, though.

HTH

Re: Undocumented uBASIC commands.
« Reply #7 on: 23 / March / 2008, 14:12:18 »
Deleted
« Last Edit: 22 / April / 2008, 14:38:33 by Barney Fife »
[acseven/admin commented out: please refrain from more direct offensive language to any user. FW complaints to me] I felt it imperative to withdraw my TOTAL participation. Nobody has my permission, nor the right, to reinstate MY posts. Make-do with my quoted text in others' replies only. Bye


*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: Undocumented uBASIC commands.
« Reply #8 on: 23 / March / 2008, 15:39:47 »
Great, more stuff that's never been mentioned ANYWHERE before. So add all this stuff into the Wikia just like I do all the time. I'm not going to. Because I've had it with trying to get any documentation at all out of MX3 and others on the md issue. While you're at it, don't forget to mention how to release the shutter again with a sample script because that too needs to be explained.

Well, I know you've seen all I have, as this was introduced in the script writing motion detect too slow thread you were a part of and then later mentioned in allbest's r34 changelog. Not enough for formal documentation of course and easy to miss, but certainly the bits have passed before your eyes.

Shutter release is sort of obvious with the command
release "shutter_full"
as it happens just like when you aren't using MD immediate shoot. You just leave out the pressing.

As for an example script, I wrote one a month or two ago but I still haven't found the time to test it or actually even to upgrade to allbest 34 or newer (I'm still using an old custom build from and old trunk) and I know how much you despise people posting untested scripts.

Quote
Quite frankly, I'm at the point where I'd be just as happy deleting the whole scripting tutorial and allbest firmware usage pages, and be done with it. I'm the only one who has done any of that, so why not.

Both of you could have just saved everyone a sh*tload of work and trouble by typing the info you posted here, but in the right place on the Wikia instead. What? Did you expect me to translate it for you again?

Now that would be really helpful wouldn't it... I have never edited a wiki and expect there to be a registration process and a slight learning curve so that I wouldn't screw up everyone's formatting and page structure. I just haven't found the time and energy to familiarize myself with it, even reading the wiki is often tedious enough for me TBH.

If you want people to edit the wiki, you might want to give a few quick pointers on how easy it is (like by writing a really short wiki page with some ground rules if one doesn't exist) each time you encourage people to do it.

You need to keep in mind that we're all here on voluntarily for no profit other than making our own cameras better, learning stuff about them and making others happy as a consequence. I've worked with a fair number of engineers and I have grown to believe that the lack of interest for documentation is a fundamental factor in becoming one. Add language problems to that equation and you should understand quite well why people like you who can find the time to document things an are able to produce grammatically sensible material without a gun pointed to their head are so valuable, Barney.

 

Related Topics