On Oct 8, 2015, at 7:41 AM, pd-list-request@lists.iem.at wrote:

From: cornicis <cornicis@googlemail.com>

Date: October 8, 2015 at 7:09:22 AM MDT

To: pd-list@lists.iem.at

Subject: Re: [PD] MIDI connection problem with commandline-parameters

Thanks for the fast response!

On 08.10.2015 13:55, IOhannes m zmoelnig wrote:

On 2015-10-08 13:39, cornicis via Pd-list wrote:

won't get any MIDI input 
(miditest.pd is just printing incoming midi notes).

isn't this what you want? if you don't get MIDI input, how can it print
incoming midi notes?

I guess there's some misunterstanding, I don't think that miditest.pd or
generally PD-MIDI is faulty, you're completely right: as long as nothing
is connected, nothing can get printed.
My problem lies in having my MIDI-controller connected on PD-startup.
Right now my only possibility to connect without GUI is to execute
"aconnect 20, 128" after PD has opened MIDI. To speak more concretely:
after starting PD with mididev-parameters I want to have Arduino
connected to PureData in aconnect -l. This works on my desktop machine
but not on the fresh updated raspberry.

$ puredata -d 3 -verbose -nogui -alsamidi -midiindev 1  -listdev

try "-mididev 2" (or "-midiindev 2" if you prefer)

I retried, but I already tested various configurations. For now I tried:
-mididev and -midiindev with parameters 0/1/2/3/20/21
-midiaddindev 'Arduino Leonardo' and 'Arduino Leonardo MIDI 1' which
unfortunately didn't open any ALSA Client.

As expected compiling 0.46.7 didn't help. Root privileges didn't help
either.

I'm pretty clueless what my next steps would be to trace this issue. As
MIDI works in ALSA and PD I think there has to be a communication
problem on opening the ALSA client. Maybe I'm missing a package? What's
involved in setting the MIDI connection on startup? I supposed that PD
uses aconnect itself to connect to MIDI devices, but maybe there's
something different going on?


Cheers,
Daniel