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
This will connect a port from the Midihub to the MicroMonsta. But which port?
I think most users would expect, after seeing the listing above, for it to be the second port, that is [36:1]. I am making both amidiminder and amidiview interpret Midihub:2 this way - as a partial match against the port name.
The old amidiminder treats ':2' as a match on the ALSA id, so [36:2], which is the third Midihub port. I'm adding a syntax to explicitly mean match by ALSA number: Midihub:=2 - but I can't imagine it is all that useful.
Since this is a breaking change (should your rules use port numbers) - I'm looking for opinions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Say your system looked like this:
And you run this command:
& amidiview connect Midihub:2 MonstaThis will connect a port from the Midihub to the MicroMonsta. But which port?
I think most users would expect, after seeing the listing above, for it to be the second port, that is [36:1]. I am making both amidiminder and amidiview interpret
Midihub:2this way - as a partial match against the port name.The old amidiminder treats ':2' as a match on the ALSA id, so [36:2], which is the third Midihub port. I'm adding a syntax to explicitly mean match by ALSA number:
Midihub:=2- but I can't imagine it is all that useful.Since this is a breaking change (should your rules use port numbers) - I'm looking for opinions.
Beta Was this translation helpful? Give feedback.
All reactions