Getting Started Dramas - Recognising a Midi Controller

Hi all - first post. Newbie etc.

I am trying to get a Softstep midi controller to control effects settings in Ardour.

Ardour won’t recognise the softstep (just has a series of things like midi_capture_1, midi_capture_2) etc… if I run a2jmidid -e & it recognises it, then loses it again on reboot.

Am I going about this the right way?

If so, how do I get a2jmidid -e & to start automatically on boot?

I’m using ssh -X to run ardour.

Thanks,

Nick

Sorry - details etc:

Rasberrry Pi 5
Patchbox OS Bookworm ARM64 2024-04-04
New Pisound hat
Ardour 7 (successfully getting an audio input from the Pisound)

I’ve tried

aconnect -i → outputs as expected
aconnect -o → outputs as expected

aseqdump -p 24:0 → the hardware is getting the midi signals

..

The reason I ask “am I going about this the right way?” is that even though Ardour can recognise the softstep after a2jmidid -e , it is showing up as hardware (for output), but the midi-in still isn’t showing up.

It depends on the MIDI implementation you select, it should be easiest to deal with ALSA sequencer implementation, as it requires no special configuration at all, and works just fine.

Here’s a screenshot of a configuration that works for me:

Thanks for getting back to me.

I’m pretty sure your Audio Midi Setup looks quite a bit different to mine with regards options available.

I’m not alas able to take a screen-grab on account of deciding to make a protective box for the pi, the assembly of which wound up destroying the pi itself, continuing a theme of my life that started in about 2016.

Also I’m in New Zealand - so there’s quite a big lag reply-wise. Sorry.

Attached are screengrabs that I find troubling, taken yesterday prior to “the incident”

  1. midi port config

It worries me that there isn’t a binding… The default is “drop bindings” - I’ve left it at that, but that might not be right. There isn’t any hardware in the dropdown list that looks like a softstep

  1. Connection-managers. Output has rows for the softstep. Input doesn’t

Thanks again for your help - and I suspect this might be an “ardour problem”… but I’d rather communitise here on account of liking the whole open source hardware thing. I’ll get back to you when I have a working system again.

The Audio / MIDI Setup dialog appeared immediately after creating a session at Ardour startup.

Ah, it turns out in case the Jack server is already running, it does not allow you to select the MIDI driver to use, hides these options and forces you to use Jack MIDI implementation.

In that case, you’ll have to go with a2jmidid -e. One of the ways to make it start automatically is to make it a systemd service:

Run:

sudo nano /etc/systemd/system/a2jmidid.service

and paste the following contents:

[Unit]
Description=a2jmidid
After=jack.service
BindsTo=jack.service

[Service]
User=jack
Group=jack
Environment=HOME=/tmp
Environment=JACK_PROMISCUOUS_SERVER=jack
ExecStart=/usr/bin/a2jmidid -e
Restart=always
RestartSec=2

[Install]
WantedBy=multi-user.target

Press Ctrl+X and Y to exit and confirm writing to the file.

Then run this once:

sudo systemctl daemon-reload

To make systemd aware of the new .service file (or any changes)

And finally run this to make it run now and automatically on every boot:

sudo systemctl enable --now a2jmidid

To troubleshoot, use these commands:

systemctl status a2jmidid
journalctl -u a2jmidid

Hiya - Back again, New Pi etc.

Thanks for that - the a2jmidid is now running on boot instructions, and everything is showing up (I think) as it should in Ardour… although the midi signals seem to only come in on midi_input_2, which seems to be some sort of default/generic thing in a way that I don’t entirely understand.

So I still can’t get it to work, but I think this is an Ardour problem rather than a Pisound problem. It’s possibly also a Nick Taylor problem. More often that not, that’s what problems turn out to be.

Anyhoo… thanks for your help, and thanks for making this gear. I think what you do is inspiring. Hi from NZ.

So output through a2jmidid is working as expected, but the input ports are not providing any MIDI data?

Nope - it’s worse than that.

The tabs where it says misc / hardware… I didn’t realise that these could go horizontally as well as vertically. My brain simply didn’t register the tabs at the top.

I needed to do the a2jmidid as well - so thanks for that, but the final hurdle turned out to be me being (as they say) a muppet.

It’s all working perfectly now. Thanks for your help.

1 Like

Good to hear you managed to make it work!