Changing the sample rate in version .99

Installation & Configuration Linux
#14

There’s the problem.

ALSA: cannot set channel count to 2 for capture ALSA: cannot configure capture channel

You cannot use exactly 2 channels.

Alsa should sort it out by itself but apparently it doesn’t. You can try to set the number of input channels higher. It only works for me on an Phase88 also with envy24 chip, when i use 12 channels (8 analog input, 2 spdif, 2 intermal mixer).

You might have to try every number between 4 and your number of inputs plus 4 until you find the right one.

Then it will complain about the playback channels, because of the same problem. For me playback channels are 10. Try to set them as well and jack should start running.

And this might be another one, but i’m not sure.

required capabilities not available capabilities: =

This means that the old capability module isn’t working and maybe the new one doesn’t either. You could check that (if jack is running) with

ps -C jackd -cmL

That should return two threads that have “FF” scheduler instead of “TS”. If all have “TS”, you don’t have realtime, which will lead to xruns.

#15

  1. there is generally no good reason to try to control the number of channels. just let JACK use all the available channels. it was probably a mistake to make the option to ask for less channels than actually exist so visible.

  2. messages about “capabilities” means that jackstart is being used and it should not be used on anything but a 2.4 kernel patched to enable capabilities. i very much doubt if anyone here is using 2.4.

#16
  1. I was suggesting the first because without parameters on channels his jackd started with zero channels.

    hw:0|hw:0|1024|2|88200|0|0|nomon|swmeter|-|32bit

Maybe it’s a problem with the old version of jack or a misconfiguration of alsa?

  1. You’re right about that it should not be used anymore.

If i remember right, this module is still available. In the standard kernel of edgy. Maybe jackstart was used or jack in ubuntu was compiled to use this module (what i doubt).

Anyways using qjackctl seems to be a bad idea.

#17

You should definitely not specify -i2 -o2 with an ice1712 card, just let jackd work it out by itself as Paul suggested. If you want to see how many channels are running you can use jackd -v option. You’ll probably see 2 input ports and eight output ports (the eight outputs can be sent to the Audiophile’s hardware mixer if required, but I wouldn’t bother as Ardour’s mixing is better quality).

BTW latency shouldn’t be an issue when overdubbing. You can monitor the track being recorded with `zero’ latency by routing the input to the Audiophile’s hardware mixer along with the playback from Ardour’s master outputs. I’ve been using this technique for a long time with my ice1712 cards with no latency problems at 1024 frames/period. Low software latency is only required for MIDI etc., if you have zero latency hardware monitoring like on the ice1712.

#18

Another thing:

/usr/lib/libjack0.100.0-0/jack_alsa.so
getting driver descriptor from /usr/lib/libjack0.100.0-0/jack_dummy.so
getting driver descriptor from /usr/lib/libjack0.100.0-0/jack_oss.so
jackd 0.101.1

You have libjack0.100-0 and jackd 0.101.1, ie. different versions. Could that be one of the problems?

#19

required capabilities not available
capabilities: =

I seem to remember seeing this message with an earlier version of jackd (0.97 ?) even when jackstart wasn’t being used. IIRC it was a bogus message and it got fixed, but I can’t remember when.

jackd -v -R -dalsa -r88200 -p512 -n2 -D -Chw:0

Instead of the above I’d suggest:
jackd -R -P80 -dalsa -r88200

Don’t forget to specify the -P80, which sets how high a realtime priority it gets. It defaults to -p1024, -n2 and hw:0 for both playback and capture so you don’t need to specify those.
You should use the largest buffer size possible for
reliability (which is 1024 for ice1712) - remember you have zero latency hardware monitoring.

#20

jrigg - thanks for catching the clashing JACK versions.
this is almost certainly the cause of the problems being reported with qjackctl.

we are slowly working out how to avoid these issues, but for now, it is almost never going to work to have two versions of JACK installed. the typical case occurs after installing an (older) version of JACK via a package management system, which ends up in /usr/bin and /usr/lib, and then later installing from source which ends up in /usr/local/bin and /usr/local/lib.

one of the two versions of JACK that are installed needs to be removed. removing the packaged one is probably easier and closer to what you actually want.

#21

Don’t know if this has anything to do with it, but I had a similar problem with my RME. I could not change the samplerate with qjackctl.

However, once I compiled the RME driver as a module instead of building it into the kernel it worked.

#22

Sorry to say but I’m kind of lost here. What is the best approach for me to take to get things correct.

I did install a package for Ubuntu. Should I uninstall jack? If so, what then? I’ve never complied anything. So I don’t know where to start. Detailed baby steps are what I need. I’ve only been using Linux for about 3 weeks (and a lot of that was taken up with ALSA and video driver issues), so it’s all very new to me.

I looked in the package manager both Jackd and libjack are listed as version 0.101.1-1.

I have been able to record/playback with what I have now, however, the sound quality doesn’t seem as good as I was getting with Audacity, Krystal, or Ableton under windows. Perhaps that different issue.

#23

he is running Ardour first and it is initiating its very own JACK session.

you have to start qjackctl before you start any jack clients. server, then client.

most likely you are not connecting to qjackctl because you don’t have realtime privileges.

#24

niko123456: the information you are providing is incorrect.

#25

pk1, please show the results of the following commands:

ls -l /usr/lib/libjack*
ls -l /usr/local/lib/libjack*
ls -l /usr/bin/jack*
ls -l /usr/local/bin/jack*

Regarding audio quality, that seems rather unlikely. But lets not address that until we get your system configuration figured out.

#26

Here you go:

ls -l /usr/lib/libjack*

pk@pk-desktop:~$ ls -l /usr/lib/libjack*
lrwxrwxrwx 1 root root 25 2007-01-27 10:46 /usr/lib/libjack-0.100.0.so.0 -> libjack-0.100.0.so.0.0.23
-rw-r–r-- 1 root root 57340 2006-06-21 03:12 /usr/lib/libjack-0.100.0.so.0.0.23

/usr/lib/libjack0.100.0-0:
total 112
-rw-r–r-- 1 root root 4100 2006-06-21 03:12 inprocess.so
-rw-r–r-- 1 root root 4624 2006-06-21 03:12 intime.so
-rw-r–r-- 1 root root 49208 2006-06-21 03:12 jack_alsa.so
-rw-r–r-- 1 root root 7028 2006-06-21 03:12 jack_dummy.so
-rw-r–r-- 1 root root 29048 2006-06-21 03:12 jack_oss.so

ls -l /usr/local/lib/libjack*

pk@pk-desktop:~$ ls -l /usr/local/lib/libjack*
ls: /usr/local/lib/libjack*: No such file or directory

ls -l /usr/bin/jack*

pk@pk-desktop:~$ ls -l /usr/bin/jack*
-rwxr-xr-x 1 root root 82080 2006-05-09 20:46 /usr/bin/jackbeat
-rwxr-xr-x 1 root root 4384 2006-06-21 03:12 /usr/bin/jack_bufsize
-rwxr-xr-x 1 root root 4860 2006-06-21 03:12 /usr/bin/jack_connect
-rwxr-xr-x 1 root root 59800 2006-06-21 03:12 /usr/bin/jackd
-rwxr-xr-x 1 root root 4860 2006-06-21 03:12 /usr/bin/jack_disconnect
-rwxr-xr-x 1 root root 100644 2006-08-01 21:08 /usr/bin/jackeq
-rwxr-xr-x 1 root root 3972 2006-06-21 03:12 /usr/bin/jack_freewheel
-rwxr-xr-x 1 root root 6468 2006-06-21 03:12 /usr/bin/jack_impulse_grabber
-rwxr-xr-x 1 root root 5632 2006-06-21 03:12 /usr/bin/jack_load
-rwxr-xr-x 1 root root 6384 2006-06-21 03:12 /usr/bin/jack_lsp
-rwxr-xr-x 1 root root 7920 2006-06-21 03:12 /usr/bin/jack_metro
-rwxr-xr-x 1 root root 3756 2006-06-21 03:12 /usr/bin/jack_monitor_client
-rwxr-xr-x 1 root root 8564 2006-06-21 03:12 /usr/bin/jackrec
-rwxr-xr-x 1 root root 4380 2006-06-21 03:12 /usr/bin/jack_showtime
-rwxr-xr-x 1 root root 5748 2006-06-21 03:12 /usr/bin/jack_simple_client
-r-sr-xr-x 1 root root 11832 2006-06-21 03:12 /usr/bin/jackstart
-rwxr-xr-x 1 root root 8464 2006-06-21 03:12 /usr/bin/jack_transport
-rwxr-xr-x 1 root root 3948 2006-06-21 03:12 /usr/bin/jack_unload

ls -l /usr/local/bin/jack*

pk@pk-desktop:~$ ls -l /usr/local/bin/jack*
ls: /usr/local/bin/jack*: No such file or directory

#27

Debian/Ubuntu’s confusing package naming isn’t helping here. I just checked Debian Testing (which Edgy is based on AFAIK) and it has a jackd' package (version 0.101.1) and a separatelibjack0.100.0’ package, which is actually libjack version 0.101.1 despite its name.

You can check what package versions you actually have with the dpkg command:
dpkg --list jackd
dpkg --list libjack0.100.0

(That’s a double hyphen in front of the list option, just in case your browser uses a typeface that merges them together).

#28

pk1, you said earlier in the thread that you managed to record at the correct sample rate. Things to remember:

Don’t specify -i or -o numbers (specifying -i0 or -o0
is the same as not specifying any and causes ALSA to use
the correct number by default).

Make sure that .asoundrc has been removed. If you are
using the plug device the quality will be bad, so get rid of it. You shouldn’t need any .asoundrc just to record with a single sound card.

#29

Here is the output:

pk@pk-desktop:~$ sudo dpkg --list jackd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
++±==============-==============-============================================
ii jackd 0.101.1-1 JACK Audio Connection Kit (server and exampl

pk@pk-desktop:~$ dpkg --list libjack0.100.0
No packages found matching libjack0.100.0.

–
I tried “dpkg libjack” without a version number and got the same:

pk@pk-desktop:~$ dpkg --list libjack
No packages found matching libjack.

With “dpkg libjack*” this is the results:

pk@pk-desktop:~$ dpkg --list libjack*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
++±==============-==============-============================================
ii libjack0.100.0 0.101.1-1 JACK Audio Connection Kit (libraries)
un libjackasyn0 (no description available)

So it looks like libjack and jackd are different versions.

#30
pk1, you said earlier in the thread that you managed to record at the correct sample rate. Things to remember:

Don’t specify -i or -o numbers (specifying -i0 or -o0
is the same as not specifying any and causes ALSA to use
the correct number by default).

Make sure that .asoundrc has been removed. If you are
using the plug device the quality will be bad, so get rid of it. You shouldn’t need any .asoundrc just to record with a single sound card.

Thanks for the tip. I now have qjackctl set a zero for I/O.

I have deleted asoundrc.

#31

On rechecking the package name it’s `libjack0.100.0-0’.
Sorry, my mistake.

You can specify -i0 -o0 or not use the -i -o options at all, it should give the same result (at least it should on the command line - I’m not sure if qjackctl defaults to that, so you might need to tell it to use -i0 -o0).

#32

On the sound quality issue:

Operator error!

I found I had inadvertently cranked the bass EQ knob all the way up on my mixer. Everything sounds a lot better now.

#33

Since I didn’t hear any different, and the system seems to working alright. I’m just going to leave things as they are. Thanks for the help in setting the sample rate and configuring Jack properly.
I’m going to test lowering the sample rate from 88200 until latency becomes an issue then raise it back up a notch.