At Tue, 08 Dec 2009 17:20:39 +0000, Sid Boyce wrote:
On 07/12/09 22:12, Takashi Iwai wrote:
At Mon, 07 Dec 2009 17:18:54 +0000, Sid Boyce wrote:
On 07/12/09 16:34, Takashi Iwai wrote:
At Mon, 07 Dec 2009 16:10:20 +0000, Sid Boyce wrote:
On 03/12/09 01:15, Sid Boyce wrote:
My sound cards say they should be capable of 192K sample rate, but alsa seems to have a default of 48K. I tried the following in /etc/asound.conf, but it doesn't effect the change. I need it for alsa direct rather than for pulseaudio. # o /etc/asound.conf defaults.pcm.rate_converter "samplerate" Any clues?
This just changes the SRC engine to libsamplerate. For changing "defualt" PCM sample rate (supposing you are using dmix), set defaults.pcm.dmix.rate instead.
defaults.pcm.dmix.rate 19200
I shall have a look later to see what needs doing as jackd and python are the two involved, so when I've had the app configured to use e.g 96K, audio fails.
jackd is very likely using "hw" device, so there can't be no default rate. For python, I have no idea at all, but "default" should be used in general for such a use case...
OK, I started jackd with samplerate 96K, but sound isn't very clean, I suspect the application, as going back some months it would fail at 96K.
(snip)
The software under test asks for jack in /usr/bin (openSUSE jack-0.116.2), so why is it looking at jack2 in /usr/local/bin?
Likely you mixed up jack and jack2 from Packman. They are supposed to be compatible, but not fully, unfortunately.
Takashi Sadly no, I don't use packman and I've done exactly the same build in the Kubuntu VM under VirtualBox. Source ======= svn co http://subversion.jackaudio.org/jack/jack2/trunk
openSUSE 11.3 Milestone 0 (x86_64) =================================== # LD_LIBRARY_PATH=/usr/local/lib64 /usr/local/bin/jackd -V
This run pattern is already bad. The correct library path should have been set at the compile time, not at the runtime. This kind of hack gives just a pain instead of any gain.
It configured, built and installed in /usr/local, but when library paths are searched, it tries various directories unless LD_LIBRARY_PATH is set - without it, it finds libraries of the same names in /usr/lib64 and uses them, that's how OOo and others that use their own copies of system libraries work.
It depends on how you link the binary plugin object at the build time, too... Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org