You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a dreamblaster and I would like to be able to switch between that and the mt32-pi. Would it be possible to have a third option for the synthesizer sysex call that enables passthrough to the TX pin and doesn't do any internal audio processing, then when switched away it changes the passthrough setting back to whatever is defined in the mt32-pi.cfg file? Or a sysex to directly control passthrough and an option for disabling the mt32-pi synth?
The text was updated successfully, but these errors were encountered:
This would be possible as part of a planned MIDI routing feature where all different kinds of MIDI inputs (GPIO, USB, Pisound, network) can have their inputs optionally routed to the synth and each other, which will be more flexible.
Basically, gpio_thru is going to be deprecated and replaced with something like:
[midi]# GPIO input sent to synths and thru to outputgpio_route = synth, gpio
# GPIO input just sent thru to outputgpio_route = gpio
# USB input sent to synths and thru to USB outputusb_route = synth, gpio
This would also be controllable via SysEx.
I won't be accepting any PRs for this as I already have a design in mind and the MIDI code is going to be changed extensively.
I have a dreamblaster and I would like to be able to switch between that and the mt32-pi. Would it be possible to have a third option for the synthesizer sysex call that enables passthrough to the TX pin and doesn't do any internal audio processing, then when switched away it changes the passthrough setting back to whatever is defined in the mt32-pi.cfg file? Or a sysex to directly control passthrough and an option for disabling the mt32-pi synth?
The text was updated successfully, but these errors were encountered: