I’m guessing because it’s from the same developer as Arpeggionome Pro etc. Here’s what’s new:
PER-PLAYHEAD MIDI ‘DESTINATIONS’
You can now route each playhead to any MIDI Destination and MIDI Channel — the previous version only allowed routing by MIDI Channel. This makes it much easier to send each playhead to a different app or MIDI Port.
Check out Settings > Midi Output Settings, and notice that each Playhead (1-4) now has its own setting. There’s also an ‘All Playheads’ setting for convenience.
SYNTH ENABLED SETTING*
There’s now a setting to explicitly set the built-in synth on and off, allowing Fugue Machine to send MIDI and control the built-in synth simultaneously. Go to Settings > Synthesizer Settings.
*Synthesizing sound is expensive! So if you’re only using Fugue Machine as a MIDI sequencer, set Synth Enabled to OFF to save CPU resources.
AUDIOBUS 3 MIDI SUPPORT
Audiobus 3 brings MIDI support to Audiobus, and Fugue Machine is good to go :]
AUDIOBUS STATE SAVING SUPPORT
Fugue Machine now supports State Saving in Audiobus, making it possible to save/manage Fugue Machine patterns via Audiobus.
EXITING APP NOW PROPERLY FLUSHES MIDI NOTES
In previous versions, if you exited the app while Fugue Machine was running, there was a chance some MIDI Notes wouldn’t be turned off. Not a huge deal, but it’s fixed now.
ABOUT THIS UPDATE
Although this is a relatively minor update, getting the MIDI Destinations to route properly was surprisingly tricky! I wanted it to be foolproof… which required a system to ensure that redundant MIDI data would be filtered out.
Basically, thanks to this system, you can set the playheads to any Destination / Channel combination, and not have to worry about a connected MIDI device receiving duplicated MIDI messages.