Here's the pd start script I use (it's called at login): <meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://trac.robotcowboy.com/browser/robotcowboy/trunk/scripts/rc_starts_pd">http://trac.robotcowboy.com/browser/robotcowboy/trunk/scripts/rc_starts_pd</a><div>
<br></div><div><a href="http://trac.robotcowboy.com/browser/robotcowboy/trunk/scripts/rc_starts_pd"></a>... the trac is a bit empty right now as I just set it up last week.<br><br><div class="gmail_quote">On Mon, May 17, 2010 at 1:22 PM, Ingo Scherzinger <span dir="ltr"><<a href="mailto:ingo@miamiwave.com">ingo@miamiwave.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="DE" link="blue" vlink="blue">
<div>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy">Thank you Dan,</span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy"> </span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial;color:navy">I’ll check out both ways
and see which one will work best.</span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial;color:navy"> </span></font></p><font color="#888888">
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial;color:navy">Ingo</span></font></p></font><div class="im">
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial;color:navy"> </span></font></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal"><font size="3" face="Times New Roman"><span lang="EN-GB" style="font-size:12.0pt">Subject: [PD] udev & usb midi interfaces</span></font></p>
<div link="blue" vlink="purple">
<div>
<p class="MsoNormal"><font size="2" face="Arial"><span style="font-size:10.0pt;font-family:Arial">Hi,</span></font><font color="navy"><span style="color:navy"></span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial">does
anybody know the search path to get udev information about usb midi interfaces?</span></font><span lang="EN-GB"></span></p>
<p class="MsoNormal"><font size="2" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial">It
should be something like “udevadm info -a -p / ??? …”. I’m not realy sure how
to search for the soundcard either.</span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial">I
was using “lshal” which gives me a lot of information but I can’t tell which
part to use for the udev device rules.</span></font></p>
<p class="MsoNormal"><font size="2" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial">I
read Daniel Drake’s “writing udev rules” but he doesn’t mention sound at all.</span></font></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">Yeah, it's easy ... try</span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"> </span></font></p>
</div>
<div>
<p class="MsoNormal"><span><font size="1" face="Courier New"><span style="font-size:9.0pt;font-family:"Courier New"">udevinfo -a -p $(udevinfo -q
path -n /dev/</span></font></span><em><i><font size="1" face="Courier New"><span style="font-size:9.0pt;font-family:"Courier New"">your device</span></font></i></em><span><font size="1" face="Courier New"><span style="font-size:9.0pt;font-family:"Courier New"">)</span></font></span></p>
</div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"> </span></font></p>
</div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">and plug in the device ... this command will list all the udev
attributes it sees when it makes the sysfs usb tree. I use it it see what
attributes I can use for writing udev rules. Drake may not explciity list
"sound" or "midi" devices, but they are covered by the
tutorial as well ... just find where the device is mounted in /dev and use that
node in udevinfo.</span></font></p>
<div link="blue" vlink="purple">
<div>
<p class="MsoNormal"><font size="2" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial">I
really need to write some udev rules to straighten out my 2 usb midi interfaces
and soundcard that get mixed up all the time.</span></font></p>
</div>
</div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">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 aconnect again to connect pd with the midi device.</span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"> </span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">Actually, perhaps you are right as it would be nice to have udev run
aconnect whenever my midi device is plugged in.</span></font></p>
</div>
</div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><br>
-- <br>
Dan Wilcox<br>
danomatika<br>
<a href="http://www.robotcowboy.com" target="_blank">www.robotcowboy.com</a></span></font></p>
</div>
</div></div>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>Dan Wilcox<br>danomatika<br><a href="http://www.robotcowboy.com">www.robotcowboy.com</a><br>
</div>