Nick found that the new Pure Java JSyn was using a latency value that
was too optimistic. We both had glitching on Windows 7 under Eclipse.
I changed the default output latency for Windows from 30 to 80 msec.
You can tune the latency for your application. Use a low latency value
for highly interactive applications like drums. But if latency is too
low you will hear glitching. For non-interactive apps or apps with slow
controls use a higher latency to avoid glitching. Windows will require
higher latency than Mac or Linux.
Suggested output latency:
Mac Linux: 20 - 50
Windows: 70 - 150
It is hard to predict the proper latency for any given situation. Use
whatever works for you.
The device drivers may not allow you to set an exact latency. But you
can "suggest" a latency value. To set the suggestedOutputLatency with
the new API with Pure Java JSyn use:
// Create a context for the synthesizer.
synth = JSyn.createSynthesizer();
// Set output latency to 123 msec.
synth.getAudioDeviceManager().setSuggestedOutputLatency( 0.123 );
// Start the synthesiser using the suggested latency.
synth.start();
In the old API use:
synthContext = new SynthContext();
synthContext.initialize();
synthContext.setSuggestedOutputLatency( 0.123 );
Phil Burk
---------------------------------------
SoftSynth, Audio Research and Development
http://www.softsynth.com/75 Pleasant Lane, San Rafael, CA, 94901 USA
Office/Fax: +1-415-453-4320
Mobile: +1-415-846-4370
---------------------------------------
_______________________________________________
JSyn mailing list
JSyn@...
To change digest mode or to make other administrative changes visit:
http://music.columbia.edu/mailman/listinfo/jsyn