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
There's a slight issue with midistroke's ability to remember your midi input.
As far as I can tell the way the program remembers the last used MIDI input is by remembering it in the context of the list of inputs that were active at the time it was selected.
The reason why this is key is because when ANY of those inputs is no longer seen (say because its been disconnected) Midistroke goes into input 'none' (even if the actual MIDI input that was selected is still plugged in an active)
In my case a couple of my midi controllers are connected via bluetooth and sometimes they lose the connection. When that happens Midistroke goes into 'none', even though the midi device I'm using for the program is still connected and active.
There's no current workaround for this
The text was updated successfully, but these errors were encountered:
There's a slight issue with midistroke's ability to remember your midi input.
As far as I can tell the way the program remembers the last used MIDI input is by remembering it in the context of the list of inputs that were active at the time it was selected.
The reason why this is key is because when ANY of those inputs is no longer seen (say because its been disconnected) Midistroke goes into input 'none' (even if the actual MIDI input that was selected is still plugged in an active)
In my case a couple of my midi controllers are connected via bluetooth and sometimes they lose the connection. When that happens Midistroke goes into 'none', even though the midi device I'm using for the program is still connected and active.
There's no current workaround for this
The text was updated successfully, but these errors were encountered: