Of course, as with jlooch, these little buttons are also useful if you really can't stand some of the sounds.
Phil's latest version of JSyn does in fact address this problem by raising the audio synthesis thread priority. You will have to run the program as root (or su) under Linux to take advantage of this feature, however.
If the button is in the green/+ state (), it means the thread is running or is marked for running; in the red/- state () it signals that the thread is stopped.
As amazingly cool as the little graphics thingies are, they can get truly obnoxious when they start popping themselves up in front of the editor windows you are using to fix bug report number 71872871. The graphics bg checkbox invokes the java window toBack() method, which should put the graphics behind other stuff already on the screen. It does in fact do this under Linux, but I'm not so sure that it works properly running as an IE applet. Oh well.
Ok, I lied. There is some history, primarily related to the synthesis algorithm used. jnissa doesn't use any sampled guitar or plucked sounds -- it's all created by an algorithm developed by Charles Sullivan (back when he was an undergraduate!) extending the basic Karplus-Strong ("plucked string") synthesis technique. Amazing guy, Charlie. I've had hours of endless enjoyment through the years fooling with this algorithm, and what you hear with jnissa is almost entirely generated by this synthesis method.
You can read how this approach works in Charlie's original article published in the Fall, 1990 Computer Music Journal (vol. 14, #3): Extending the Karplus-Strong Algorithm to Synthesize Electric Guitar Timbres with Distortion and Feedback. The Computer Music Journal is published quarterly by the MIT Press. Alternatively, you can download the source code for the objects I wrote implementing this algorithm in JSyn. There's even a nice, terse README file included to hopelessly confuse the unsuspecting code-hacker.
Check the source code if'n' ya really
wants an answer to this question.
Q. Why won't it run properly on my machine XXX?
This is an extremely fascinating and interesting question. Although time and space prevent me from going into great detail here, I can say briefly that the question warrants deep consideration and will most likely engage issues of great importance. One good suggestion is to scan the answer to a similar question rhetorically posed (and answered) in the Semi-Silly Answers to Semi-Silly Questions section of the jlooch web page. I am certain that it will address more specific points that are beyond the scope of the present document. As in any human endeavor, the hope is that all that ends will indeed end well. In truth, each one of us can partly judge our success and/or failure by the point in our striving towards completion that we declare, unequivocally, "our goal has been attained". Thus it is, and ever shall be.
Q. Whoa -- that was quite an answer! But are there any known bugs?