Uses of Midi Out
There must be a reason why Midi Out was developed and accepted. But why? There is already an export file function that gives the ability to load the file into a DAW and use with the plug- in of choice. You can also load the file into many stand-alone apps, though not all, for playback or more advanced functions. Furthermore, the files are small enough to email. Also, a single DAW centralizes the problem of finding audio and midi devices and drivers on the operating system and figuring out priorities. So, it seems that it has to do with the convenience and utility of using real-time playback of Msc. But I am now at pains to see this. ( beyond my own fascination with recreating 1980's hardware set-ups in virtual space.) I have only come up with these:
1) Allows the use in a stand alone sampler that doesn't facilitate midi import and playback
2) Allows the use of samplers and libraries that don't have VST versions.
Please enlighten me. If these are viable, then they could be refined. (Clue: Free playback (and clock) from Fluid's need for an open audio port for a midi driver. Let the destination worry about that. Its not audio. Strange. I can run a tape machine with printed sound even with the audio circuitry ripped out of it. ( I'll never be able to reproduce it unless I switch machines. Yet I can't send the midi out without the requirement for an open audio port for the midi drivers to see?)