Still no luck compiling with alsa-midi support. I must still be missing
something.
Is this the correct configuration to compile?
./configure --enable-jack --disable-oss --enable-portmidi
Is portmidi MIDI through alsa? That's how it is described on the portmidi
site. Pd doesn't have an --enable-a
Am 28. April 2022 15:37:31 MESZ schrieb Samuel Burt
:
>Still no luck compiling with alsa-midi support. I must still be missing
>something.
>
ALSA-MIDI will be builtin on Linux by default, unless you explicitely disable
it (ALSA).
You must tell Pd to use it at runtime.
Either via the "-alsamidi"
I still havent tried pipewire, but as I understand qjackctl will let you
manage jack or pipewire. May be you will fix it by installing the a2j.
After initiating the audio run "a2jmidid -e &" or use it as a startup
script in qjackctl.
On Thu, Apr 28, 2022 at 8:42 AM Samuel Burt
wrote:
> Still no
Ok. This jostled some things loose for me. I believe I've compiled Pd
with the right flags.
Apparently, I had failed to test the option /dev/midi2. I noticed when
the keyboard
wasn't plugged in that only /dev/midi1 was listed. I'd still expect
when using -alsamidi that
Pd would show Alsa-style labe
Hi list,
I can't seem to get my head around different behavior of the [key] and
[keyup] objects on different OSes and even within the same OS. I
discovered that for depressed keys after an initial delay
-Pd on Debian will report repeated key ups and downs,
-Pd on Windows does not,
-Pd on OS X may
Pd 0.52-2 pressing and holding a key:
Windows11 (Tk 8.6.10 amd64)
key: 106
key: 106
key: 106
key: 106
key: 106
key: 106
key: 106
key: 106
key: 106
key: 106
keyup: 106
Debian11 (Tk 8.6.11 amd64)
key: 106
keyup: 106
key: 106
keyup: 106
key: 106
keyup: 106
key: 106
keyup: 106
key: 106
keyup: 106