-
Notifications
You must be signed in to change notification settings - Fork 2
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
undefined rxDAW, rxMidiIn, rxMidiOut #1
Comments
hi there! Darwin wasn't mentioned as being supported because I haven't tested it. So yeah, the name varies depending on (I guess) the midi driver. On linux there doesn`t seem to have have any id/count to differentiate devices so I only support one. There should be 3 devices but depending on the OS the midi in/out can be the same device. So my guess is that darwin return 2 midi devices, the DAW and the MIDI. The MIDI one being IN/OUT even though it's name has OUT. you could try something like this, it will use the midi out for input, might work (or not)
|
Seems works to me, i will test and send you PR
Btw, what about checks ins and outs before for's cycles?
And yes, looks like I have only 2 midi devices |
Well, now its work, but i receive some signal
And i don't know what is that :) |
I guess i accepted the merge request a little too fast hehe I should add some kind of minimal cli for listings midi IDs. Also my gomidi dependency is quite old and might have some bug. Maybe the out/in inversion in your patch creates some kind of exception. I just noticed you've put the midi |
As I asked above, in #issuecomment-806244760 outs come from ins, and ins from outs, idk why, but it works for me, for ex on text |
Hi there!
The text was updated successfully, but these errors were encountered: