> > Looked it up. I like a lot! I'll just have to get started :-) Tell > > me: why ALSA-MIDI on the RPi side? Does this mean I don't have to have > > JACK running on the RPi? That would be most extremely cool. > > If you are only using one path as in this case, Jack will serve no > purpose. Alsa is already there and keeping running bits as few as possible > will give the best timing. KB -> pi(alsa -> qmidinet -> wireless) > Or with Jack: Kb -> pi(alsa -> netjack - > wireless) > > The problem with netjack, is that one end runs as a backend and so if > network fails, jack fails. The master side will keep running if the slave > side is out of range, but the slave side jack would exit. If you were > running audio as well, then netjack might be better as it is all in one. Got it. Soo-eet. A lot simpler than I had thought. Hopefully I'll be able to get the RPi to do a peer-to-peer with the synth, that would keep things simple too. Thanks, folks!!! -- Jonathan E. Brickman | jeb@xxxxxxxxxxxxxxxx | (785)233-9977 Ponderworthy | http://ponderworthy.com Music of compassion; fire, and life!!! _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
