<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I'm not sure who is using the midi port (could be jack itself or<br>
qjackctl). Could you do a:<br>
<br>
/sbin/fuser /dev/snd/midiC5D0<br>
<br>
that should give you a process id of who has it open and then you can<br>
find who is keeping it busy. If something is using the sequencer the raw<br>
midi port will be busy as well...<br>
<font color="#888888"><br>
-- Fernando</font><br></blockquote></div><br>Thanks, Fernando.<br><br>Well, I can't say anyone lied to me because, yes, if jack/qjackctl are running with nothing connected to a particular rawmidi port through qjackctl that I can use amidi. However, once anything, sequencer or midi keyboard, is connected it will block anything else from outside of qjackctl and give the messege I mentioned. Curiously, fuser shows nothing for midiC5D0, but if I run the following as root I get....<br>
<br>[root@ceres sean]# /sbin/fuser -v /dev/snd/*<br> USER PID ACCESS COMMAND<br>/dev/snd/controlC0: root 3926 F.... jackd<br>/dev/snd/controlC6: sean 3274 F.... mixer_applet2<br>/dev/snd/pcmC0D1c: root 3926 F...m jackd<br>
/dev/snd/pcmC0D1p: root 3926 F...m jackd<br>/dev/snd/seq: root 3921 F.... qjackctl<br> root 3926 F.... jackd<br><br><br>It doesn't change whether I have something connected to a midi port or not. It is always the same.<br>
<br>You actually revealed a lot to me. Thank again. <br><br>I am left hoping for something I can read and write sysexe files that uses jack, however now. I can disconnect the rawmidi port in qjackctl if I need to so it:'s not totally unworkable.<br>
<br><br>--Sean<br>