Skip to content

Losing the MIDI input when another device gets unplugged #3

@ncknamesound

Description

@ncknamesound

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions