Luigi, Typically KBHit takes keyboard input from the "console" from which chuck, Audicle, or miniAudicle was started. Since normally on OS X, miniAudicle is not started from the Terminal but from clicking on it in the Finder/etc., so there is no console, and thus no way for KBHit to get input. Ideally, the console monitor in miniAudicle could send keystrokes to KBHit, but this hasn't been implemented yet. One alternative would be to the Hid API, which can recognize keystrokes no matter where they are typed, and is more versatile in general. If you wanted to stay with KBHit, you could start miniAudicle from the command line and use the Terminal window to enter keystrokes (to do this, open up Terminal.app and type /path/to/ miniAudicle.app/Contents/MacOS/miniAudicle, then hit enter (where "/ path/to" is typically "/Applications")). Or you could use regular command line chuck. spencer On Sep 10, 2007, at 10:37 AM, Luigi Rensinghoff wrote:
Hi Chuckers
Well, the quality of free software, depends on the mailing lists ;-)
I am on a Macbook using miniaudicle, for some reason KBHit does not produce any output.
Nobody wants to answer ???
Please !!!
Luigi _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users