[Ardour-Users] Faderport recognized at startup

jonetsu at teksavvy.com jonetsu at teksavvy.com
Mon Sep 19 14:35:53 PDT 2016

On Mon, 19 Sep 2016 23:22:31 +0200
Robin Gareus <robin at gareus.org> wrote:

> Mixbus 3.X is based on late Ardour 4.7+git but the Faderport surface
> is identical.

> > jackd is (Ubuntu)

> Mmh that's a rather old version (1.9.9 is also known potentially cause
> stalls on export). 

Yes, I know.  That's a bummer.  I compiled jackd from recent sources
but was missing the alsa part.  Could not find what the alsa headers
files can be...

> Do you use jack's MIDI drivers or a2jmidid?

Unfortunately, I use a2j+control.  Unfortunately because then I have to
unload it when working with Bitwig who happens to not need anything
superfluous for seeing the MIDI devices.

I must say this is a grey zone that I hope to clear out one of these
days.  What I would like is not to use anything else than the system
for Ardour to see MIDI devices.  Any suggestion regarding this ?

> Is the jack-port name of the Faderport identical after every reboot?
> Is the faderport jack-port visible when you launch Mixbus?

It is not visible from Mixbus if a2j_control was not launched.  Which
makes sense I guess.  For the name, I do not know.  I will check it out
the next times.
> Does it work with Mixbus' ALSA backend (no jack)?

Unfortunately I am not into testing things to this extent.  I always
use jackd.  Actually I would like to get rid of pulse audio
and only use jackd, although there's no real hard use case to
substantiate this.  Only cosmetics I guess.

This said, I could try not using jackd, if this is needed.


More information about the Ardour-Users mailing list