here is another workaround which works, but with some limitations.
This thread is about re-routing of MIDI data to antother channel within a track. I say re-routing because it does not matter if you enter MIDI data in a track with a Keyboard of with a MIDI file, each data (at least each note) arrive with a MIDI channel "attached" to it.
I have finally found a VST plug-in (64-bits) that does the job: SELECTOR by Vague Software: https://www.kvraudio.com/product/selector-by-vague-software
Steps to follow:
* download the plug-in and make sure that ALK2 finds it when it scans for VST plug-ins
* create a MIDI track (not Instrument, I explain why later)
* set SELECTOR as an FX.
Problem : when I click on the cross to display the plug-ins, I cannot see SELECTOR in the list. I have to select any other plug-in, then click on the 3 horizontal bars at the left of this plug-in, click on "Choose plug-in", and then I can choose SELECTOR_x64. Is it a bug?
* click on the plug-in title (SELECTOR), its window will open. Turn the channel wheel to the required channel number.
Now all MIDI data that goes through SELECTOR is re-routed to the channel number which you have selected with the wheel. You can check it by adding a second FX plug-in like "MIDI_Polysher" which has a light blinking when MIDI data arrives on a specific channel. If MIDI POLYSHER is after SELECTOR in the row of FX plug-ins, then it should confirm that the data is effectively re-routed.
Now 2 Options.
Option 1, you use an external MIDI gear (Hardware synth, Hardware Expander...) : simply select your Hardware MIDI port as output and you should be fine.
Every time that you create a new track you will need to add a new SELECTOR plug-in to re-route to another channel (ex: Re-routing to channel 1 on Track 1, Re-routing to channel 2 on track 2, etc.). So you might end-up with several SELECTOR plug-ins on your screen, that all look the same, but they actually differ on the channel selected. Once you have set the channel you can close a plug-in, the setting is saved.
Option 2, you use a software Sound Generator on the same computer. I have tried with Steinberg Halion (standalone, not VST). I have created a virtual MIDI port using BOME-MIDI-Translator. ALK2 sends its data to the MIDI IN of the virtual port. The MIDI OUT of the virtual port is bridged with the MIDI IN (within MIDI-Translator). Steinberg Halion gets its data from the virtual port. Basically it works. There is a problem though: both ALK2 and Halion try to open all available physical MIDI ports on the computer. It does not matter if the port is not-selected in ALK2 or set to "not connected" in Halion. In reality all physical MIDI ports are opened by each software and this causes conflics between both. Actually as I am writing those lines I realize that there could be also a conflct with the Audio ports, but in my case I have an RME Audio interface whose driver is multi-client.
Anyway I could get this configuration running by opening first BOME-MIDI-Translator, then ALK2 and then Halion. If I change the order, Halion or ALK2 cannot open the required MIDI ports. They do not display any error message. There is simply no sound because the MIDI stream is blocked on its way.
OK, too complicated.
Second part of my experiment: what happens if I try with an Instrument track?
I have created an instrumentt track with Halion as a VST Instrument. As soon as I select SELECTOR as FX plug-in, Halion stops receiving MIDI data. It seems to me that the FX slots in Instrument tracks are designed for audio plug-ins only, not for MIDI plug-ins. As a user I would need both.
Finally I would like to ask zenAudio to give us the option to disable the Audio engine in case we want to work 100% with MIDI. As soon as I start ALK2 my CPU gets running at 20-30% load, although I have no audio track in the project. This is a loss of heat and energy, not good for our planet! Thanks for reading .