Hi all,
I was wondering if anyone could help me remove an irritating behaviour of pure data which I've noticed lately. When running qjackctl, and selecting 'alsa midi' in pd to initialize its
it connects its output to all other midi inputs, and its input to all other midi outputs (including through-midi on both sides, meaning it is essentially sending midi to itself, as well as everything else.) This is mildly irritating during normal usage, but is now becoming outright unmanageable, as I am currently trying to write some scripts to automatically set up my audio environment for live performance (including midi and jack audio connections).
Can anyone suggest a way to supress this behaviour? Thanks.
n.b. Cross-posted this because I believe the subject concerns both lists.
Whoops! Somewhat garbled opening paragraph, there. Oh, well. You probably get the idea.
J
On Fri, May 11, 2012 at 4:07 PM, James Mckernon jmckernon@gmail.com wrote:
Hi all,
I was wondering if anyone could help me remove an irritating behaviour of pure data which I've noticed lately. When running qjackctl, and selecting 'alsa midi' in pd to initialize its
it connects its output to all other midi inputs, and its input to all other midi outputs (including through-midi on both sides, meaning it is essentially sending midi to itself, as well as everything else.) This is mildly irritating during normal usage, but is now becoming outright unmanageable, as I am currently trying to write some scripts to automatically set up my audio environment for live performance (including midi and jack audio connections).
Can anyone suggest a way to supress this behaviour? Thanks.
n.b. Cross-posted this because I believe the subject concerns both lists.
On Fri, 11 May 2012 16:07:44 +0100 James Mckernon jmckernon@gmail.com wrote:
Hi all,
I was wondering if anyone could help me remove an irritating behaviour of pure data which I've noticed lately. When running qjackctl, and selecting 'alsa midi' in pd to initialize its
it connects its output to all other midi inputs, and its input to all other midi outputs (including through-midi on both sides, meaning it is essentially sending midi to itself, as well as everything else.) This is mildly irritating during normal usage, but is now becoming outright unmanageable, as I am currently trying to write some scripts to automatically set up my audio environment for live performance (including midi and jack audio connections).
Can anyone suggest a way to supress this behaviour? Thanks.
n.b. Cross-posted this because I believe the subject concerns both lists.
Hi, I wouldn't know how to configure pd to not do this, however a dirty hack could be to use aj-snapshot to restore connections; you'd call it as last line of your script (maybe preeceded by a "sleep 3" to wait for all applications to have properly started) with the option (I don't remember which) to make it first disconnect all connections - i.e. it first disconnects everything, then makes only the connections you say him so (by passing him a file).
aj-snapshot is really neat and manages jack audio, midi and alsa midi connections.
HTH, renato
On 11/05/12 16:07, James Mckernon wrote:
'alsa midi' in pd to initialize its
it connects its output to all other midi inputs, and its input to all other midi outputs (including through-midi on both sides, meaning it is essentially sending midi to itself, as well as everything else.)
Can anyone suggest a way to supress this behaviour? Thanks.
I don't know if this still works in recent Pd, but it used to work to tell Pd to have two (2) alsamidi ports, then none are autoconnected.
$ pd -alsamidi -mididev 1 # this autoconnects pd everywhere $ pd -alsamidi -mididev 1,1 # 2 ports, and no autoconnections $ pd -version Pd version 0.42-6 compiled 08:43:13 Mar 19 2012
n.b. Cross-posted this because I believe the subject concerns both lists.
Claude
A little hacky, but it seems to work. Nice! The aj-snapshot and patchbay solutions also seem like they would be useful, and I'll remember them if I ever start working with those.
Cheers, J
On Fri, May 11, 2012 at 5:55 PM, Claude Heiland-Allen claude@goto10.orgwrote:
On 11/05/12 16:07, James Mckernon wrote:
'alsa midi' in pd to initialize its
it connects its output to all other midi inputs, and its input to all other midi outputs (including through-midi on both sides, meaning it is essentially sending midi to itself, as well as everything else.)
Can anyone suggest a way to supress this behaviour? Thanks.
I don't know if this still works in recent Pd, but it used to work to tell Pd to have two (2) alsamidi ports, then none are autoconnected.
$ pd -alsamidi -mididev 1 # this autoconnects pd everywhere $ pd -alsamidi -mididev 1,1 # 2 ports, and no autoconnections $ pd -version Pd version 0.42-6 compiled 08:43:13 Mar 19 2012
n.b. Cross-posted this because I believe the subject concerns both lists.
Claude
______________________________**_________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/** listinfo/pd-list http://lists.puredata.info/listinfo/pd-list
-
Claude Heiland-Allen -
James Mckernon -
renato