[qjackctl]
> Hi Christoph - yes, that was the gui I was working on.
nice app for controlling jackd (start, stop, audio connections).
> Jack wont start for some reason from the CLI (I don't know why)
>
> Here is a transcript of the session attempt to start jackd
>
> audacity ~ # jackd -dalsa
I use an external USB breakout box and qjackctl shows the following
line:
/usr/local/bin//jackd -R -P83 -p64 -dalsa -dhw:2 -r48000 -p256 -n3
As you can see, it's a bit more than yours :)
> JACK compiled with System V SHM support
You should have mounted shm via /etc/fstab to get lower latencies. Mine
reads as the following:
none /dev/shm tmpfs defaults 0 0
[...]
> Couldn't open hw:0 for 32bit samples trying 24bit instead
> Couldn't open hw:0 for 24bit samples trying 16bit instead
> ALSA: cannot set number of periods to 2 for capture
> ALSA: cannot configure capture channel
> cannot load driver module alsa
> audacity ~ #
>
>
>
> I really don't know what the problem is, as ALSA works fine,
> its in use with audacity.
^^^^^^^^^^^^^
As long as your sound device is blocked by another app, you will not
succeed with any other app. Stop all apps. including soundservers like
artsd, esound, gstreamer and the like.
> Sadly, it turns out that ardour does not have the one specific
> functionality that I needed, but it may be useful anyway, and I would
> like to play with it.
Ardour is a great example for the power of OSS vs. commercial
applications. It's not only comparable but equal to apps like Ableton.
Best regards
ce
--
[email protected] mailing list
