How to get the thread a sequence plays on?

Question

Hi, this is sort of a continuation of an earlier question... I have a sequence that plays back with imperfect timing. I would like to 'get a hold' of the thread that it plays back on in order to check / change its priority, etc.
But a Sequencer is an interface; and it is gotten from the MidiSystem, which is also an interface. I am stumped as how to go about accessing the Java Sound Sequencer thread which does in fact get created by my program when I get a Sequencer from the MidiSystem.
An excellent suggestion was given to me to extend Sequencer, then use the Thread.getCurrentThread() on my "MySequencer" object. To get a Sequencer, you call MidiSystem.getSequencer() - I can't figure out how to get a "MySequencer" (object that extends Sequencer) rather than a Sequencer from the MidiSystem.
So, to be clear, my question is - Is there a way to get a reference to the thread that a sequence plays back on?
Forgive me if this is a boneheaded question... I should have taken more Java classes back when I was in school...
Thanks

Answer 1

You think the GUI should be sluggish and keyboard and mouse capture delayed so someone can hear Fur Elise with precise timing as they laggingly scroll through a JTable with their mouse while waiting a few seconds for button clicks to occur?YES! That's ABSOLUTELY what I am suggesting. In none of my previous posts have I said or even suggested that the MIDI file was to be playing in the background have I? This program is about real time music recording and playback. Live, that is.* In front of an audience*. If a midi burp were OK with me, I would not have been pursuing this, would I? Everything I have posted is in relation to the timing needs I have for this program. I don't care if the flippin' screen goes blank, if the MIDI timing is good.
OK?
Briefly: The program has two main ... uh.. use cases. First, the GUI is used to pre-program which clips are to played where. This is not done in real time, so I am indifferent to any consideration of timing. It is mainly for this that I use the JTable. But in the Second case, when the play button is hit, the sequence plays and the clips are triggered according to what was previously been entered int the JTable. This sequence plays a drum track which I play along with. The sequence also triggers the clips to be played (via MetaMessages) which have to be to be in time with everything else - or else the program is utterly useless. So I hope you can see that at this point, the GUI doesn't really matter that much, but the timing of the MIDI sequence is crucial.
I agree with you that perfect midi timing might not be all that important for everyone. But here's a quote from the Java Sound tutorial:
"The Java Sound API does not include sophisticated sound editors or graphical tools, but it provides capabilities upon which such programs can be built."
Surely Sun would not expect application designers to go to the trouble of building such programs if the Java Sound API was designed to deliver flawed Midi timing at best? Am I mistaken in thinking that stable Midi timing is possible? From all that I have read over at the Java Sound Resources web site it seems that not everybody suffers from bad MIDI timing.
-Scott