• IOhannes m zmölnig zmoelnig@iem.at [2015-05-21 17:58]:

On 05/21/2015 10:45 PM, Peter P. wrote:

...

Dear list,

I am wondering how to use the -midiadddev flags. What is the difference between -mididev and -midiadddev, and does this apply to midi on a linux system?

The mailing list search engine reveals no result for the searchstring "midiadddev" strangely, so here we go.

Furthermore, when using alsa-midi, is there a way to set the connections on the alsa patchbay from within vanilla Pd (sans using IOhannes' aconnect external nor aconnect from the command line after Pd has been started)?

i usually use qjackctl for that which despite it's name can also handle alsa midi and can monitor connections to auto-connect (or disconnect) them by name.

Yes, that's what I am using until now as well, but I would like to avoid qjackctl's auto-connect in order to keep my midi connection scheme independent, on a per-patch basis, within the startup shell script, but without spawning a second (aconnect) process after launching Pd.

But I think I remember Miller once explained on this list why including aconnect's functionality within Pd itself was somehow difficult or not advisable.

thanks, P

Hi list,

• Antoine Villeret antoine.villeret@gmail.com [2015-05-22 03:20]:

Hi,

you can handle alsamidi connection with iem's (or should I write iohannes') [aconnect] external. you will need zexy to deal with space in alsa device name, and then yiu can connect devices according to their name in a per-patch basis.

Thanks for your help Antoine, and thanks IOhannes for writing aconnect. Do you, Antoine, happen to have an example of how to connect by device name instead of number? Do I pass the name to aconnect in the same message format than the numbered version?

I am also wondering how aconnect can tell different instances of Pd apart. I fear it can not detect the instance of Pd that aconnect is part of when multiple Pd's are running. Does anyone have an oppinion on this?

Thank you so much! P

Dear Antoine,

• Antoine Villeret antoine.villeret@gmail.com [2015-05-25 17:37]:

hi,

here is a patch that automatically connects all alsa midi input devices to puredata alsamidi input and the puredata output to all midi output devices it uses zexy's llist2symbol and symbol2list to replace space in device name with "_"

it's not exactly what you need but could be a good start

Thank you. I did already looked at it as part of aconnect's documentation, and am impressed by the Pd-object patchability.

As you say, it is not (yet) exactly what I am looking for, but sure is interesting as well. Thanks for pointing me towards it.

In case someone started following this thread by now only, let me sum up:

I am still looking for a way how to have Pd connect to alsa midi devices by their name, and without possible confusion with other Pd instances on the same machine. This is on Linux.

best, P

On 05/30/2015 09:55 PM, Antoine Villeret wrote:

But maybe it could be a nice feature to be able to choose the Pure Data alsa sequencer client name. For example with a string following the -alsamidi flag and/or in the midi settings dialog box.

most likely a new flag, as it would make parsing easier.

but while we are there: i would also like to to be able to set the jack client name from the cmdline.

ideally the flag used would be agnostic of the actually used backend.

smdf IOhannes

Nah.. I'm reading it here :)

M

On Sun, May 31, 2015 at 12:42:52AM +0200, Antoine Villeret wrote:

should we open an official feature request on SF ?

-- do it yourself http://antoine.villeret.free.fr

2015-05-31 0:35 GMT+02:00 IOhannes m zmölnig zmoelnig@iem.at:

...

On 05/30/2015 09:55 PM, Antoine Villeret wrote:

...

But maybe it could be a nice feature to be able to choose the Pure Data alsa sequencer client name. For example with a string following the -alsamidi flag and/or in the midi settings dialog box.

most likely a new flag, as it would make parsing easier.

but while we are there: i would also like to to be able to set the jack client name from the cmdline.

ideally the flag used would be agnostic of the actually used backend.

smdf IOhannes

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

• Miller Puckette msp@ucsd.edu [2015-05-30 19:30]:

Nah.. I'm reading it here :)

by the way, what was the problem with specifying alsamidi ports, to which to connect to, on the command line? I remember a reason why it was too complicated or something?

Thanks again for looking into this, P

hello, Miller and al.

I would like to know the state of this feature has it been implemented yet ? I can't see any new flag on the 0.46-7

cheers

antoine

-- do it yourself http://antoine.villeret.free.fr

2015-05-31 4:31 GMT+02:00 Miller Puckette msp@ucsd.edu:

There are just WAY too many command line options already so I try to avoid adding yet more... but here I think I can make one option both name the "alsa MIDI" device and the Jack one - so that sounds worth it. Maybe there are other places I shoudl use the name (lke on the Pd window to disambiguate that ?)

cheers Miller

On Sat, May 30, 2015 at 09:51:22PM -0400, Peter P. wrote:

...

• Miller Puckette msp@ucsd.edu [2015-05-30 19:30]:

...

Nah.. I'm reading it here :)

by the way, what was the problem with specifying alsamidi ports, to which to connect to, on the command line? I remember a reason why it was too complicated or something?

Thanks again for looking into this, P

Dear Antoine,

• Antoine Villeret antoine.villeret@gmail.com [2015-05-30 15:56]:

Hi,

as it is defined in Pd's source, on line 98 of s_midi_alsa.c, the "Pure Data" name of Alsa Sequencer Client is fixed. And it is the same for all instance of Pd.

Yes, they only get higher client index numbers assigned as individual instances are created.

As far I know there is no way to change a client name from another client (I tried to do so without success by modifying aconnect).

This is not what I had in mind, I was just curious if a Pd instance knows about its own client name and, especially, index number, so that further actions (aconnect object, aconnect binary via shell external, ...) can be taken without confusing instances.

But maybe it could be a nice feature to be able to choose the Pure Data alsa sequencer client name.

Hm, this could be a nice solution to avoid ambiguity.

For example with a string following the -alsamidi flag and/or in the midi settings dialog box.

Actually it would also be sufficient to specify the other alsamidi ports this instance of Pd should connect to. But I am not sure if this can be done, and I remember Miller or someone else once explaining why it is hard to do.

[...]

...

In case someone started following this thread by now only, let me sum up:

I am still looking for a way how to have Pd connect to alsa midi devices by their name, and without possible confusion with other Pd instances on the same machine. This is on Linux.

Peter