[=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=]
[<<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>><<>]
[=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=]
Stardate: 20250720.2337
Location: The Lab
Input Device: HOSAKA -> booji
Audio: The Church - Starfish
Visual: nano
[=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=]
OCC 2025 DAY VII: Interfacing Triton with P1610 (cont.)
Saturday was busy so I was not able to work on the Triton <-> P1610
connection until today (Sunday.) I found this article [1][2] by
sndrtj to be quite helpful in getting the Triton to work with the
P1610 via the Keystep.
Testing hardware communications
- Look for MIDI device: aconnect -i
- Show key presses on Keystep: aseqdump -p (client ID)
Installation of qsynth jackd qjackctl
- configure jackd
- configure qsynth
Test Keystep - SUCCESSFUL
Plug in Triton to Keystep via 5-pin MIDI cable
Test Triton - SUCCESSFUL
HTML [1] Using a USB midi keyboard on Ubuntu
[2] PDF copy of article
[=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=-=x=]