18 Feb
2015
18 Feb
'15
3:03 a.m.
I have a Yamaha keyboard with USB MIDI out, and I'd like to get that MIDI signal
wirelessly to JACK running on my synth. What is the simplest way right now? I could
connect the keyboard to an RPi and then netjack it to the synth via wifi, but that does
not sound very simple to me :-)
--
Jonathan E. Brickman | jeb(a)ponderworthy.com | (785)233-9977
Ponderworthy | http://ponderworthy.com
Music of compassion; fire, and life!!!
18 Feb
18 Feb
7:31 a.m.
2015-02-18 4:03 GMT+01:00 Jonathan E. Brickman <jeb(a)ponderworthy.com>om>:
I have a Yamaha keyboard with USB MIDI out, and
I'd like to get that MIDI
signal wirelessly to JACK running on my synth. What is the simplest way
right now? I could connect the keyboard to an RPi and then netjack it to
the synth via wifi, but that does not sound very simple to me :-)
The simple solution here is to use cables ;)
Possibly there are usb extenders that can work over wifi. It'll likely cost
more than the keyboard though.
Regards,
Robert
--
*Jonathan E. Brickman** | * *jeb(a)ponderworthy.com
<http://login.jsp?at=02e47df3-a9af-4cd9-b951-1a06d255b48f&mailto=jeb@ponderworthy.com>**
| (785)233-9977 <%28785%29233-9977>*
*Ponderworthy | *
*http://ponderworthy.com <http://ponderworthy.com/>**Music of compassion;
fire, and life!!!*
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
9:05 a.m.
On 02/18/2015 04:03 AM, Jonathan E. Brickman wrote:
I have a Yamaha keyboard with USB MIDI out, and
I'd like to get that MIDI signal wirelessly to JACK running on my synth. What is the
simplest way right now? I could connect the keyboard to an RPi and then netjack it to the
synth via wifi, but that does not sound very simple to me :-)
If you have a RPi I would certainly consider setting it up as a MIDI to
WiFi transponder thingy. Otherwise you could look at devices like this:
http://www.thomann.de/nl/cme_widixu.htm
Jeremy
2:23 p.m.
On Wed, 18 Feb 2015, Jeremy Jongepier wrote:
On 02/18/2015 04:03 AM, Jonathan E. Brickman wrote:
Far as I can tell this is just the computer end. To use this the synth
needs to have wireless built in... or you also need:
http://www.cme-pro.com/proline/product-detail.php-product_id=8.htm
This is not wireless networking from what I can tell. So the computer's
built in wireless will not talk to it... which is why the dongle exists I
would guess.
--
Len Ovens
www.ovenwerks.net
I have a Yamaha keyboard with USB MIDI out, and
I'd like to get that MIDI signal wirelessly to JACK running on my synth. What is the
simplest way right now? I could connect the keyboard to an RPi and then netjack it to the
synth via wifi, but that does not sound very simple to me :-)
If you have a RPi I would certainly consider setting it up as a MIDI to
WiFi transponder thingy. Otherwise you could look at devices like this:
http://www.thomann.de/nl/cme_widixu.htm 
9:35 p.m.
hi, (now to the list)
On 02/18/2015 04:03 AM, Jonathan E. Brickman wrote:
iif you really don't get whether a proper usb cable is the best all
round solution to your problem, then i'll suggest to rig the rpi with
proper alsa-midi and yours trully qmidinet (--no-gui; set to alsa-midi
only), while at the other end, either wired or wireless, run qmidinet
again as well, but now taking jack-midi as the preferred interface. or
ipmidi, if windoze or macosx is on target. beware, the latter is not
quite free, charges may apply;)
hth.
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
I have a Yamaha keyboard with USB MIDI out, and
I'd like to get
that MIDI signal wirelessly to JACK running on my synth. What is
the simplest way right now? I could connect the keyboard to an RPi
and then netjack it to the synth via wifi, but that does not sound
very simple to me :-)
If you have a RPi I would certainly consider setting it up as a MIDI
to WiFi transponder thingy. Otherwise you could look at devices like
this: http://www.thomann.de/nl/cme_widixu.htm
9:59 p.m.
If you have a
RPi I would certainly consider setting it up as a MIDI
to WiFi transponder thingy. Otherwise you could look at devices like
this: http://www.thomann.de/nl/cme_widixu.htm
iif you really don't get whether a proper usb cable is the best all
round solution to your problem, then i'll suggest to rig the rpi with
proper alsa-midi and yours trully qmidinet (--no-gui; set to alsa-midi
only), while at the other end, either wired or wireless, run qmidinet
again as well, but now taking jack-midi as the preferred interface. or
ipmidi, if windoze or macosx is on target. beware, the latter is not
quite free, charges may apply;)
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.
--
Jonathan E. Brickman | jeb(a)ponderworthy.com | (785)233-9977
Ponderworthy | http://ponderworthy.com
Music of compassion; fire, and life!!!
10:16 p.m.
On 02/18/2015 09:59 PM, Jonathan E. Brickman wrote:
A USB cable is not the best solution to my problem. I have exactly one appropriate USB
port on my keyboard, and I don't want to wear it out -- I have seen far too many USB-A
and USB-B ports and cables wear out over the last five years for comfort. Haven't
worn out any MIDI DINs yet, but recent conversation has finally given me the answer to
some anomalies seen in some very fast music played through MIDI-DIN, so I have to start
the engineering for durable ultrareliable portable MIDI-USB, and a permanent dongle for
wireless of some sort seems the only practical way.
because you don't need anything else in between alsa(-midi) and the
wire(less); remember that usb-midi should be present on the rpi
primarily as an alsa-midi interface, from which qmidinet may pick up
directly and throw into the air (wlan) or copper (eth).
hth.
byee
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
If you have a RPi I would certainly consider setting
it up as a MIDI
to WiFi transponder thingy. Otherwise you could look at devices like
this: http://www.thomann.de/nl/cme_widixu.htm
iif you really don't get whether a proper usb cable is the best all
round solution to your problem, then i'll suggest to rig the rpi with
proper alsa-midi and yours trully qmidinet (--no-gui; set to alsa-midi
only), while at the other end, either wired or wireless, run qmidinet
again as well, but now taking jack-midi as the preferred interface. or
ipmidi, if windoze or macosx is on target. beware, the latter is not
quite free, charges may apply;)
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.
19 Feb
19 Feb
1:31 a.m.
On Wed, Feb 18, 2015 at 3:16 PM, Rui Nuno Capela <rncbc(a)rncbc.org> wrote:
A USB cable is not the best solution to my problem. I have exactly one
appropriate USB port on my keyboard, and I don't want to wear it out -- I
have seen far too many USB-A and USB-B ports and cables wear out over the
last five years for comfort.
Would you consider connecting a USB hub to the device in a semi-permanent
manner? Would solve the decaying port problem. I don't think at hub would
add any noticeable latency?
--
**** Listen to my FREE CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca
3:34 a.m.
A USB cable is
not the best solution to my problem. I have exactly one
appropriate USB port on my keyboard, and I don't want to wear it out -- I
have seen far too many USB-A and USB-B ports and cables wear out over the
last five years for comfort.
Would you consider connecting a USB hub to the device in a semi-permanent
manner? Would solve the decaying port problem. I don't think at hub would
add any noticeable latency? 
4 a.m.
On Wed, 18 Feb 2015 20:34:56 -0700 (MST), Jonathan E. Brickman wrote:
Of course, I could just use male-to-female extenders
instead of hubs.
I will probably do this in the short term, until I have better :-)
"UCE60 lets you locate your USB device or hub up to 60m (198 ft) from
you computer, overcoming the typical USB cable limitation. It
conditions the USB signals to communicate up to 60m using low-cost Cat
5/Cat 5e/Cat 6 cable." -
http://www.reichelt.de/USB-Kabel/ATEN-UCE60/3/index.html?&ACTION=3&…
4:15 a.m.
On Thu, 19 Feb 2015 05:00:42 +0100, Ralf Mardorf wrote:
On Wed, 18 Feb 2015 20:34:56 -0700 (MST), Jonathan E.
Brickman wrote:
If your device doesn't have MIDI sockets, there's also
http://www.kentonuk.com/products/items/utilities/usb-host.shtml
I don't know if USB to CAT or USB to MIDI does add delay or jitter.
Of course, I could just use male-to-female
extenders instead of hubs.
I will probably do this in the short term, until I have better :-)
"UCE60 lets you locate your USB device or hub up to 60m (198 ft) from
you computer, overcoming the typical USB cable limitation. It
conditions the USB signals to communicate up to 60m using low-cost Cat
5/Cat 5e/Cat 6 cable." -
http://www.reichelt.de/USB-Kabel/ATEN-UCE60/3/index.html?&ACTION=3&…
18 Feb
18 Feb
10:20 p.m.
On Wed, 18 Feb 2015, Jonathan E. Brickman wrote:
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.
--
Len Ovens
www.ovenwerks.net
then i'll
suggest to rig the rpi with
proper alsa-midi and yours trully qmidinet (--no-gui; set to alsa-midi
only), while at the other end, either wired or wireless, run qmidinet
again as well, but now taking jack-midi as the preferred interface. or
ipmidi, if windoze or macosx is on target. beware, the latter is not
quite free, charges may apply;)
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.
10:39 p.m.
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.
3359
days inactive
3360
days old
linux-audio-user@lists.linuxaudio.org
12 comments
7 participants
participants (7)
-
Bob van der Poel -
Jeremy Jongepier -
Jonathan E. Brickman -
Len Ovens -
Ralf Mardorf -
Robert Jonsson -
Rui Nuno Capela