Hi,

Sorry in advance if this post is confusing.

I am trying to setup Pd to run headless on a Raspberry Pi with my midi controller. I need the controller to both send and received midi from Pd. I was referencing this page for command line options that I put in the startup flags preferences:

https://puredata.info/docs/faq/commandline

Right now I can only send midi to my controller, but not from my controller (so no midi inputs in Pd) My midi controller shows up in Pd as: /dev/midi1 in the Oss midi window.

I see this flag in the command line options and I want to use it: -midiaddindev

But it doesn't seem to work. Am I supposed to put the name of the device? Which I guess is "midi1" so it would be -midiaddinmidi1. Or should it work with just -midiaddindev?

Also, I want so specify Alsa midi. If I want to put more than one startup flag how do I format them? Are the separated by a comma as in: -midiaddindev,-alsamidi ? or no comma as in -midiaddindev -alsa midi?

Either way I do it I get this message: error parsing startup arguments. Or are these messages totally different than startup flags?
Sorry for the long rambling post. I hope my questions are clear.

Thank you.

Nick

@nicnut Hello Nick..... I would expect ......... -alsamidi -midiaddindev midi1 ...... but I cannot test that...
where midi1 is the name that Pd sees in midi-settings if you start Pd normally and select it from the menu bar.
David.

Hi,

Whale-Av, thank you for your reply. I put in my startup flag: -alsamid -midiaddindev midi1

and by doing that i don't have any startup flag error messages, so thank you for your help.

in the Pd window after startup now I am getting this:

Alsa Client 129 in:0 out:1
ALSA input error (snd_pcm_open): No such file or directory

To get my midi device to work I have to open the OSS-MIDI dialog box and in input device pulldown menu manually select midi1 device. Then it will start working. Is there anyway to have this set automatically upon startup? I tried different startup flags like -ossmidi and changing around the order of the flags, but nothing seemed to help. Let me know if you have any suggestions.

Thank you again,

Nick

@nicnut You could try "-alsamidi -midiaddindev midi1 -midiindev 1" (if "midi1" shows as device 1 when you select it manually).....
David.

Whale-Av, Thank you very much for your help. I got it to work.

I had to put -midiindev 2 for it to work. I guess, since in the pull down menu it was "none, midi1" my device was second in the list after none. It seems to work. I noticed that even if I didn't have my midi interface plugged in it was saying it was receiving midi on one port, so that sounded odd to me.

Also, upon startup midi input wouldn't work for my unless I opened the OSS-MIDI window, even though I didn't have to do anything other than open it. So, the startup flags I am using that seem to work are: -ossmidi -midiaddindev midi1 -midiindev 2

thanks again for your help!

Nick