-- Forwarded message --
From: Ingo Scherzinger i...@miamiwave.com
To: 'pd-list' pd-list@iem.at
Date: Mon, 17 May 2010 09:10:27 +0200
Subject: [PD] udev usb midi interfaces
Hi,
does anybody know the search path to get udev information about usb midi
interfaces?
It
Hi,
On Mon, May 17, 2010 at 11:28:42AM +0200, Daniel Wilcox wrote:
Why udev rules then ...? I use the portaudio index of the soundcard to pass
to pd with -audiodev on startup (I use -nogui and alsa) and another script
which parses aconnect -io to determine the alsa mdii index, then calls
Thank you Dan,
I'll check out both ways and see which one will work best.
Ingo
Subject: [PD] udev usb midi interfaces
Hi,
does anybody know the search path to get udev information about usb midi
interfaces?
It should be something like udevadm info -a -p / ??? .. I'm not realy sure
Here's the pd start script I use (it's called at login):
http://trac.robotcowboy.com/browser/robotcowboy/trunk/scripts/rc_starts_pd
http://trac.robotcowboy.com/browser/robotcowboy/trunk/scripts/rc_starts_pd...
the trac is a bit empty right now as I just set it up last week.
On Mon, May 17, 2010
I'll check this one also to see if I can change it to work with my setup.
BTW udevinfo has changed to udevadm info on my system (Ubuntu 10.04). I
hope it still does the same thing.
Ingo
Here's the pd start script I use (it's called at login):
Hi Frank,
I had tried assigning the devices as described in the
MultipleUSBAudioDevices article before but I kept losing my soundcard. Now
I tried it again and gave ALL midi interfaces a vendor id. This finally
works!
Originally I had the plan of using 2 internal midi interfaces and assign
them
