Hm... I will once again carefully check this before the 1.9.3 release, but seems that SunVox still have some bug with the public MIDI input port...
If briefly, SunVox has the public MIDI input port, which is always open for all apps. This port can receive the MIDI events from any channel. So you don't need to change any MIDI settings in SunVox at all. Just set SunVox as the destination in your MIDI host app.
But... For some reason this public port works only when the first MIDI controller is enabled and its channel is set to ANY :(
Here is the temporary solution.
1. Open SunVox -> Preferences -> MIDI -> remove all the controllers here.
2. Set MIDI controller 1 to some unused device; for example - "Network session 1".
3. Set the channel of this device to ANY.
4. Select some SunVox synth.
5. Go to another MIDI application: i tested it with MIDI Wrench, Apollo and littlemidi:
- Apollo: in MIDI routing enable SunVox in the left column;
- littlemidi: Settings -> CoreMIDI Outputs -> SunVox -> enable Seq A/B out;
- some other app: set the SunVox as the MIDI destination.
Also you always can use an alternative way, where the SunVox connects to another apps with the virtual MIDI port.
1. Open some MIDI host (Apollo, Cubasis, etc.)
2. Open SunVox -> Preferences -> MIDI -> select the appropriate MIDI input device (with the same name as the MIDI host app). For example - Cubasis.
3. Select some SunVox synth.
4. Go to the MIDI host and enable output to the Virtual MIDI. For example, in Apollo you need to choose the "Apollo" MIDI destination. In Cubasis - Virtual MIDI.