Date: Tue, 7 Jul 2015 21:48:12 +0200 From: Pierre Massat pimassat@gmail.com Subject: [PD] Using midi
Dear list,
I am trying to understand how midi works in Pd, and how to facilitate the connection to a midi device.
I m using Pd 0.46-6 on AVlinux with JACK. When using JACK, OSS midi doesn't work. ALSA does, but in an odd way (at least to me).
Pd doesn't appear as a writeable midi client in JACK by default, until I ask Pd to open port 1 (or any non-zero positive integer it seems). I can then automate the connection in JACK using a patchbay profile.
Is there no easier way ? Is it possible to save the midi device in Pd the way sound settings are saved ? It would be nice if we could send a message to Pd when loading a patch to open a specific midi port.
Cheers,
Pierre.
I have solved some jack-midi problems with a2jmidid as described here:
https://wiki.archlinux.org/index.php/JACK_Audio_Connection_Kit#MIDI I hope this helps. -- Jeff
Hi Jeff,
Thank you for your reply. a2j is running by default in my version of AVLinux, that's what I'm using. Using the patchbay in QJackctl I managed to make the connection between Pd and the controller persistent. The problem lies with Pd now, in the sense that the midi port is not open by default, and I have to manually open it every time I start Pd.
So I was wondering if there was a way to open the port by default at startup. Perhaps with a startup flag ?
Cheers,
Pierre.
2015-07-08 21:36 GMT+02:00 Jeff Sandys jpsandys@gmail.com:
Date: Tue, 7 Jul 2015 21:48:12 +0200 From: Pierre Massat pimassat@gmail.com Subject: [PD] Using midi
Dear list,
I am trying to understand how midi works in Pd, and how to facilitate the connection to a midi device.
I m using Pd 0.46-6 on AVlinux with JACK. When using JACK, OSS midi doesn't work. ALSA does, but in an odd way (at least to me).
Pd doesn't appear as a writeable midi client in JACK by default, until I ask Pd to open port 1 (or any non-zero positive integer it seems). I can then automate the connection in JACK using a patchbay profile.
Is there no easier way ? Is it possible to save the midi device in Pd the way sound settings are saved ? It would be nice if we could send a message to Pd when loading a patch to open a specific midi port.
Cheers,
Pierre.
I have solved some jack-midi problems with a2jmidid as described here:
https://wiki.archlinux.org/index.php/JACK_Audio_Connection_Kit#MIDI I hope this helps. -- Jeff
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Thu, 2015-07-09 at 09:22 +0200, Pierre Massat wrote:
The problem lies with Pd now, in the sense that the midi port is not open by default, and I have to manually open it every time I start Pd.
So I was wondering if there was a way to open the port by default at startup. Perhaps with a startup flag ?
pd -alsamidi -mididev 1
If you need more ports, specify more numbers to -mididev:
pd -alsamidi -mididev 1,2,3
BTW. there is also a menu entry "File" -> "Preferences" -> "Save all settings", which is supposed to write all current settings to a file (on Linux: ~/.pdsettings). It seems it saves the settings correctly, but pd doesn't create any ports when started without any cmd options. Maybe this is a bug?
Roman
Great, thank you Roman ! I will try this flag tonight.
Pierre.
2015-07-09 9:53 GMT+02:00 Roman Haefeli reduzent@gmail.com:
On Thu, 2015-07-09 at 09:22 +0200, Pierre Massat wrote:
The problem lies with Pd now, in the sense that the midi port is not open by default, and I have to manually open it every time I start Pd.
So I was wondering if there was a way to open the port by default at startup. Perhaps with a startup flag ?
pd -alsamidi -mididev 1
If you need more ports, specify more numbers to -mididev:
pd -alsamidi -mididev 1,2,3
BTW. there is also a menu entry "File" -> "Preferences" -> "Save all settings", which is supposed to write all current settings to a file (on Linux: ~/.pdsettings). It seems it saves the settings correctly, but pd doesn't create any ports when started without any cmd options. Maybe this is a bug?
Roman
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
- Roman Haefeli reduzent@gmail.com [2015-07-09 03:54]:
On Thu, 2015-07-09 at 09:22 +0200, Pierre Massat wrote:
The problem lies with Pd now, in the sense that the midi port is not open by default, and I have to manually open it every time I start Pd.
I posted similar questions to this list a few weeks ago, and IOhannes also pointed me towards an external object for pd, saying "the "mediasettings" library provides a [midisettings] object that allows you to query and set the midi devices."
Without jack I also use aconnect to connect alsa midi ports (although I wished this could be handled by device name, not id number, from within pd vanilla). There is an [aconnect] external as well.
So I was wondering if there was a way to open the port by default at startup. Perhaps with a startup flag ?
pd -alsamidi -mididev 1
If you need more ports, specify more numbers to -mididev:
pd -alsamidi -mididev 1,2,3
BTW. there is also a menu entry "File" -> "Preferences" -> "Save all settings", which is supposed to write all current settings to a file (on Linux: ~/.pdsettings). It seems it saves the settings correctly, but pd doesn't create any ports when started without any cmd options. Maybe this is a bug?
It feels like one, but I have learned to accept it as a given thing. So, whenever you want midi, also specify the -mididev along with it.
It would be so cool to have pd connect to alsa devices by name as well as by alsa index number. (2 cents)
best, P
Thank you Peter, I will try your suggestions as well. It would indeed be very nice if we could connect to devices by name !
Cheers,
Pierre.
2015-07-09 16:24 GMT+02:00 Peter P. peterparker@fastmail.com:
- Roman Haefeli reduzent@gmail.com [2015-07-09 03:54]:
On Thu, 2015-07-09 at 09:22 +0200, Pierre Massat wrote:
The problem lies with Pd now, in the sense that the midi port is not open by default, and I have to manually open it every time I start Pd.
I posted similar questions to this list a few weeks ago, and IOhannes also pointed me towards an external object for pd, saying "the "mediasettings" library provides a [midisettings] object that allows you to query and set the midi devices."
Without jack I also use aconnect to connect alsa midi ports (although I wished this could be handled by device name, not id number, from within pd vanilla). There is an [aconnect] external as well.
So I was wondering if there was a way to open the port by default at startup. Perhaps with a startup flag ?
pd -alsamidi -mididev 1
If you need more ports, specify more numbers to -mididev:
pd -alsamidi -mididev 1,2,3
BTW. there is also a menu entry "File" -> "Preferences" -> "Save all settings", which is supposed to write all current settings to a file (on Linux: ~/.pdsettings). It seems it saves the settings correctly, but pd doesn't create any ports when started without any cmd options. Maybe this is a bug?
It feels like one, but I have learned to accept it as a given thing. So, whenever you want midi, also specify the -mididev along with it.
It would be so cool to have pd connect to alsa devices by name as well as by alsa index number. (2 cents)
best, P
- Pierre Massat pimassat@gmail.com [2015-07-09 10:44]:
Thank you Peter, I will try your suggestions as well. It would indeed be very nice if we could connect to devices by name !
Mediasettings is supposed to be able to do that, check its help file (which I haven't yet been able to decypher).
-
Jeff Sandys -
Peter P. -
Pierre Massat -
Roman Haefeli