search

oxesoft / rpi-midi-ble

Raspberry Pi 3 as an USB-MIDI over BLE-MIDI device
68 stars 9 forks source link

No data transfered #8

Open AlGrenadine opened 5 years ago

AlGrenadine commented 5 years ago

Hi, I'm getting correct connection in alsa-seq-autoconnect : "Found source port ... Found destination port "BLE-MIDI Device" Connecting 20,0 to 129,0"

But on my iPad, when i send a midi sysex to the BLE midi port i get no answer and the reply sysex is not sent back to the ipad from the USB-connected midi device

AlGrenadine commented 5 years ago

Or is it because only midi sent to BLE is transfered to USB, but midi incoming to USB is not transfered to BLE ??

tchelomgf commented 5 years ago

When you create connections on alsa, they are one direction (from/to). You should create a connection from 20,0 to 129,0 and another from 129,0 to 20,0

AlGrenadine commented 5 years ago

Thanks, that's what i just figured. I need to modify this code to handle bidirectional bridging. Should i submit modifications?

tchelomgf commented 5 years ago

I´m not the owner of this code, it seems abandoned ... I´m not sure if your submission will be handled, you can create a branch for you.

BTW, have you figured out if lot of messages, notes or commands sent together cause mix up of data ? I've tested with notes, commands and SysEx messages and a complete message alone is transported fine, but if you send 2 or more SysEx messages together, or several note ON events together, they are mixed up. I've tried to debug it but, my lack of experience on bluetooth kernel made this unsuccessful.

AlGrenadine commented 5 years ago

"You should create a connection from 20,0 to 129,0 and another from 129,0 to 20,0 " Wouldn't it create a loop?

How did you send multiple messages together?

AlGrenadine commented 5 years ago

I've tried to "create a connection from 20,0 to 129,0 and another from 129,0 to 20,0" It now works, i'm getting data from usb and to usb BUT it also creates a midi loop :( Midi sent to BLE is also sent back to BLE and midi sent to USB is also sent back to usb... Big problem as it quickly overloads the USB and BLE

tchelomgf commented 5 years ago

I´ve setup the https://github.com/fralalonde/autoroute instead of the alsa-seq-autoconnect, check it out.

AlGrenadine commented 5 years ago

Thanks, but doesn't it create a midiloop too ?

AlGrenadine commented 5 years ago

Ok it's still a midi loop. What's needed is, let say if A is BTLE Server and B is USB midi interface : When midi gets to A it must be sent to B out, when midi data is received on B in it must be sent to A out. Without creating a loop. How to do this ?

AlGrenadine commented 5 years ago

Ok i've managed to create my own bridge app with seq_events etc... It works just as with aconnect or subscribtions and... it doesn't create a midi loop BUT looses sysex packets. aconnect also looses sysex packets so do subscribtions. So my question is how can i avoir these packet losses ?

tchelomgf commented 5 years ago

Well, I´ve also reported missing messages issues on BLE server stack. Could you check if those messages are missed on the BLE or on the bridge ?

AlGrenadine commented 5 years ago

How can i check ?