Introduction
Introduction Statistics Contact Development Disclaimer Help
[=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
[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=]
You are viewing proxied material from booji.mutated.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.