Name: fb126949 Date: 04/09/2004
Previous versions of the JDK never implemented Synthesizer.getLatency -- it always returned 0. For tiger, this was fixed, but unfortunately the method returns the latency in sample frames and not, as specified, in microseconds.
Since the latency of the synthesizer was essentially *increased* with tiger (in order to have constant latency), some JCK tests fail due to this unexpected long latency (see e.g. bug 4987585: Some MidiChannel methods are asynchronous.