In fact, the latency will be about as bad as when using the the Microsoft synthesizer that is typically bundled with Windows. Note that this approach is simple, but it will not give you low latency. You can then set JavaOx to take input from the virtual MIDI port and send it to Gervill, which is Java’s synthesizer. Where x is the device ID number as shown by the devices function – run it in GHCi to list all available MIDI devices and their numbers. You can then use the devices function to see what the numbers are for your installed MIDI devices and then use playDev to play to a specific device.

You will also need a virtual MIDI port such as LoopBe1. To run JavaOx, you will need a Java Runtime Environment. However, if you are unable to use Euterpea’s play function due to lack of a MIDI output device (which is rare, but nevertheless possible), you can use the solutions later on this page for minimizing playback latency via another synthesizer or you can use this version of JavaOx, a small program that routs MIDI messages and allows the user to send to Java’s on synthesizer. Usually Windows comes with a default MIDI synthesizer that will show up as the default MIDI output device.

Setting the Default MIDI Output Device.Working with MIDI on Windows can be a tricky thing when one wants to go beyond simply playing MIDI files and using the play and writeMidi functions in Euterpea. MIDI on Windows outside of a DAW (for non-Euterpea users).This page is intended specifically for Euterpea 2 users. If you are not a Euterpea user or are using the older Euterpea 1.1.1, you may find one of these other pages more helpful:

Microsoft gs wavetable synth sf2