StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHardware MIDI Out for Playback in Java?
text
Body
copied!<p>I am making a simple application to playback MIDI files in Java.<br/> I am using the <code>javax.sound.midi</code> library.</p> <p>I can retrieve my MIDI Out Device correctly (USB to MIDI Cable).</p> <p>But when I playback the sequence it always plays in the default sound synthesizer which is the host OS's General Midi (Soundfont) playback.</p> <p>The problem I am having is changing the default MIDI Out.</p> <p>When I execute</p> <pre><code>Receiver MidiOutReceiver; //instantiated earlier Sequencer MidiOutSequencer = MidiSystem.getSequencer(); MidiOutSequencer.open(); MidiOutSequencer.start(); </code></pre> <p>I hear the MIDI sequence reproduction out of the speakers.</p> <p>After referring to the <a href="http://jsresources.org/" rel="nofollow">documentation</a> <PRE> 3.10. The "Java Sound Sequencer" is implicitly connected to the default Synthesizer, 3.5. In your program you can obtain a Synthesizer instance yourself and connect it to a sequencer explicitly using a Transmitter / Receiver pair. So you know which Synthesizer is used. In case you obtained a Sequencer that is pre-connected to a Synthesizer, you can find out the Synthesizer by using the method getTransmitters(). </PRE> But there is not mention of how to explicitly use this Transmitter / Receiver pair and instantiate the Sequencer object with the new Default Synthesizer.</p> <p>I have the correct Transmitter and Receiver. But they are not playing out of the MIDI out.</p> <p>Also when I try</p> <pre><code>MidiSystem.getTransmitter().setReceiver(MidiOutReceiver); </code></pre> <p>It does not seem to change anything.</p> <p>How do I explicitly use this Receiver / Transmitter Pair with a Synthesizer so that the Default Sequencer will use my MIDI out port?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload