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 <[email protected]>: > > > >> Date: Tue, 7 Jul 2015 21:48:12 +0200 >> From: Pierre Massat <[email protected]> >> 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 > > _______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > >
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
