Hi,

I am using a pd~ object and trying to have it start up with audio on and alsa midi selected. I have a startup message that says "pd dsp 1;" which starts up the audio. But how can I specify alsa midi? I tried alsa-midi alsa midi and a few other things.

Is there a start up message for this? thanks, Nick

by "start up message" you mean inside the patch, right?

because, there's also the command line option "pd -alsamidi" (for starting Pd)..

@shaker yes I meant inside the patch in a message object.

I tried it out. I put [; pd -alsamidi ( in a message box on a patch in my Rpi. I got "pd: unknown message -alsamidi "

Let me know if theres another message I can try. Is there a list of pd messages somewhere on line? I thought I saw one before.

thanks, Nick

@nicnut @nicnut I think you can only do that with the [midisettings] object...... or the startup flag as @Shaker says.
You can compile it for your system from this..... audio-midi-settings.zip
Unzip it, put it in a folder on your Pi, cd to the folder in a terminal and type.... make
Messages into [midisettings] can set the driver (and other stuff).
But you can only have midi objects in the main patch, and will have to pass messages on through to [pd~] (see [pd~] helpfile).
David.

@nicnut you cannot put it into a message like that. sorry if it wasn't clear. it's a startup flag that you use in the terminal or via ascript when starting the Pd application.
here's more: https://puredata.info/docs/faq/commandline
Haven't gotten pd~ to work here and i don't know if it suits your workflow, but if for starting pd (the program) you add "-alsamidi" on the command-line, pd will be started with ALSA-MIDI checked.

Thank you both for your suggestions.

My ultimate goal here is to do multithreading so have my patches run more smoothly. I was going to include some midi stuff in the Pd~ object patchs I'm using. I hit the ceiling on CPU in most of my patches. I'll keep looking into this.

THanks @whale-av for the audiosettings patch

@nicnut Found something.....
You can change midi driver with the message to Pd [midi-setapi x (..... where x is the index of the driver in the Media Settings list (ALSA-MIDI, OSS-MIDI or whatever) starting at 0 if there is actually a choice, ((or requiring 1 if there is not...???... but then we would not be using it)).

Unfortunately this opens the Midi setup menu.
You can then re-apply the Midi settings for that driver with a [midi-dialog 0 0 0 0 1 0 0 0 1 2( message....... with the correct data of course as collected from Pd like this......... get_set_midi.pd
It will be applied even though the Midi setup window will be left open showing the previous setup (which could be the same of course).
A bit of a messy explanation I'm afraid. I don't know how to close that window, but it shouldn't matter.

So something like......
[midi-setapi 1, midi-dialog 0 0 0 0 1 0 0 0 1 2(
sent to Pd.
David.

@whale-av wow awesome. I can't wait to try this out later. I'll let you know if it works for me.

Also, side note: Raspberry Pi 4 came out last night, now with 4 gigs of Ram. That might be a big performance improvement from the current 1 gig. maybe I won't need to do all these crazy things to have a patch perform in a normal way. we'll see. thanks for all the help on this.

nick