hey there! i have a question: im trying to get pd (vanilla) to listen to my faderfox DX3 when started from the command line, i ran sudo pd -nogui -listdev
and got:

audio input devices:

1. bcm2835 ALSA (hardware)
2. bcm2835 ALSA (plug-in)
3. Faderfox DX3 (hardware)
4. Faderfox DX3 (plug-in)
   audio output devices:
5. bcm2835 ALSA (hardware)
6. bcm2835 ALSA (plug-in)
7. Faderfox DX3 (hardware)
8. Faderfox DX3 (plug-in)
   API number 1

no midi input devices found
no midi output devices found

then i ran:
sudo pd -nogui -alsamidi -mididev 3 test.pd where the test patch is just ctlin connected to print to see the midi activity

and got: Opened Alsa Client 128 in:1 out:1 but it does not seem to work. can anyone shed some light?

thank you!

@amazingrolo when you say "name" you mean the name that the pi detects my controller? as in "Faderfox DX3" for example?

@alexandros im using the pi only for this project, i might add controllers from time to time so i assume the port will change in these cases, right?

It's quite likely that the ports will change, but I'm no specialist when it comes ti MIDI, so I might be wrong. Better write a scripts that detects devices by name and retrieves the numbers which is then used in aconnect.

@francis666 said:

@amazingrolo when you say "name" you mean the name that the pi detects my controller? as in "Faderfox DX3" for example?

Yes exactly. I don't remember how you need to format it, I believe on launch it's something like pd -nogui -midiaddindev Faderfox DX3

(that said, I don't use aconnect so my suggestion might not apply at all)

@amazingrolo hm when i try this with or without " " (to keep the spaces) i get a "Couldn't find MIDI output device"....

Hey I'm now running into the same problem...did you ever find a fix for this? I can't seem to get my USB MIDI device to be recognised no matter what combination of startup flags I use...

Some more details, in case anyone else is able to jump in on this...running PD 0.47.1 on my Raspberry Pi headless on the latest raspbian stretch lite.

similar to @francis666, if I run sudo pd -nogui -listdev I get the following list:
audio input devices:

1. bcm2835 ALSA (hardware)
2. bcm2835 ALSA (plug-in)
3. Teensy MIDI (hardware)
4. Teensy MIDI (plug-in)
   audio output devices:
5. bcm2835 ALSA (hardware)
6. bcm2835 ALSA (plug-in)
7. Teensy MIDI (hardware)
8. Teensy MIDI (plug-in)
   API number 1

no midi input devices found
no midi output devices found

I'm hoping to use Teensy MIDI as a USB midi device. If I run aconnect I can see the MIDI input coming in so it's definitely working, it's just not getting recognised by PD. I've tried a number of different startup flag combinations, but there's something fishy about the "no midi input devices found" message that I'm getting there. What's going on? Any ideas? I've definitely done this a number of times in the past, just using the command sudo pd -nogui -midiindev 1 midwest.pd but that now doesn't seem to work.

The main recent change has been updating to Stretch and PD .47 from .46, is there any way that could be causing the problem?

I just faced the same issue. (fresh raspian stretch, pd 0.47.1)

#!/bin/bash
pd -nogui -alsamidi -midiindev 1 -midioutdev 1 /home/pi/midi-thru1.pd &
sleep 2
aconnect 20 'Pure Data:0'

solved it.

6 month and much more understanding of the command line later,
actually the combination of while ! aconnect device name:port device name:port; do sleep 1; is the the most reliable because it repeats until actual connection is made
setting a fixed delay time might work on one system but not on the other, plus it guarantees the least possible waiting time

thanks both for revisiting this. I'm not sure how to use those fixes though - I'm not very familiar with the command line at all! how do I use your while command to actually launch a patch?

oh actually I think I'm understanding it - it works if I launch the patch in the background using an ampersand, and then manually connect the ports using aconnect. it's still not really very elegant...I've seen a number of people running into this issue since the release of Stretch and PD 0.47.1. Does anyone have an explanation for why this is happening now? Is there ever any chance of it going back to being easy again?!