Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Losing the MIDI input when another device gets unplugged #3

Open
ncknamesound opened this issue Apr 8, 2018 · 0 comments
Open

Losing the MIDI input when another device gets unplugged #3

ncknamesound opened this issue Apr 8, 2018 · 0 comments

Comments

@ncknamesound
Copy link

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)

screen shot 2018-04-07 at 9 41 31 pm

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant