Per the instructions in “Run Elk on Boards”, I connected a Keith McMillen QuNexus USB-MIDI controller to the Pi Hat, plugged in headphones, started Sushi (I had to add a “&” to the end of the command shown on the webpage), and connected the MIDI ports (16 for the kbd, 128 for Sushi) with aconnect.
I don’t hear anything when I play the keyboard. Are there other debugging tools to confirm that the audio outputs are working, and that the MIDI keyboard messages are being received by Sushi?
I don’t have MIDI running on my board yet because I don’t have a direct USB output MIDI device and my MIDI setup is overly complicated, so I can’t really help with that part yet. But, you can test the audio output to the headphone jack with
In addition to what @NeonSilicon said, which is probably the best way to check if the audio output is working on your board, to debug MIDI messages you can do the following:
Launch aseqdump and connect your MIDI device to it with aconnect. You should see incoming MIDI messages
Launch SUSHI with the --log-level=debug flag. This will turn on MIDI logging among the other things, if MIDI messages are received properly, you should see lines like this in SUSHI’s log file:
[2019-12-14 15:39:56.501] [debug] [alsamidi] Received midi message: [e0 0 3e 0] timestamp: 358983144
Which config / plugin are you testing? With the latest build the MDA JX10 VST2 version can stop outputting sound. We investigate the problem and, although very weird, I’m more surprised that it actually sounds in other configs / setups.
It’s using an old-school Chamberlein State Variable Filter that blows up under certain conditinos. I have the same problem with latest GCC on my X86 Linux machine. We tried several build options for the VST2 version but without any luck so far… interesting that the VST3 version doesn’t seem to exhibit the same problem apparently.
thank you for your detailed explanation.
Most things you mentioned I got to work and tested yesterday. The arp example worked for me as well as the aseqdump, displaying my MIDI Data coming from my keyboard. As @Stefano and you wrote there is this error with the VST2 version in the new build, so I tried the VST3.
This version sadly only produces permanent (white)noise.
I´ll give it another try today
I´ve found the mistake.
I only tried, but not described, the HDMI/Keyboard version of interacting.
With SSH everything works as expected.
But only with the VST3 version of the synth like @rcohen mentioned.
If I could suggest an addition to the very basic getting started Elk tutorial it would be to add Neonsilicon’s suggestion. Some folks like myself would love to have the simplest of tests without having to hook up a keyboard. I poked around for too long trying to find something to audibly verify my kit after getting everything put together and flashed.