On 08/12/09 17:32, Takashi Iwai wrote:
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
I've done exactly the same under Kubuntu and openSUSE, "./waf configure --prefix=/usr/local --libdir=/lib64", "./waf build", "./waf install", so everything goes into /usr/local/bin, /usr/local/lib64 and the modules in /usr/local/lib64/jack/. waf is not a straight python script and with all it's tentacles, not easy to determine where or what (linker flags) LDLINKS would be appropriate. It is however very odd that LD_LIBRARY_PATH is honoured in Kubuntu but not in openSUSE at least for jack2. ====================================================================== #!/bin/bash # define name used in the RMI registry export NAME=SDR-SHELL export SDR_DEFRATE=96000 export JACK_BUFFER=1024 # start jackd (firewir-Phw:0 -Chw:1e fa-66) echo "starting jackd ..." #DELTA-44 pasuspender -- LD_LIBRARY_PATH=/usr/local/lib64 /usr/local/bin/jackd -dalsa -Phw:0 -Chw:2 -r$SDR_DEFRATE -p${JACK_BUFFER} -s -n2& # /usr/bin/jackd -dalsa -dhw:0 -r$SDR_DEFRATE -p${JACK_BUFFER} -n3& usbsoftrock -a -d & sleep 5 # start RX DttSP echo "starting DttSP ${NAME}_RX ..." /usr/bin/sdr-core --spectrum --metering --client-name=${NAME}_RX --buffsize=${JACK_BUFFER} --ringmult=4 --command-port=19001 --spectrum-port=19002 --meter-port=19003& sleep 5 # connect receiver echo "connecting receiver ..." /usr/local/bin/jack_connect system:capture_1 ${NAME}_RX:il sleep 2 /usr/local/bin/jack_connect system:capture_2 ${NAME}_RX:ir sleep 2 /usr/local/bin/jack_connect ${NAME}_RX:ol system:playback_1 sleep 2 /usr/local/bin/jack_connect ${NAME}_RX:or system:playback_2 sleep 2 # start sdr-shell sdr-shell& ========================================================================== Result ------- starting jackd ... execvp(): No such file or directory Version : 16.1 Starting daemon... Error binding to port 19004 starting DttSP SDR-SHELL_RX ... /usr/local/bin/jackd: symbol lookup error: /usr/local/bin/jackd: undefined symbol: jackctl_server_create SDR-SHELL_RX: can't make client -- jack not running?: No such file or directory connecting receiver ... name jack_connect /usr/local/bin/jackd: symbol lookup error: /usr/local/bin/jackd: undefined symbol: jackctl_server_create jack server not running? name jack_connect /usr/local/bin/jackd: symbol lookup error: /usr/local/bin/jackd: undefined symbol: jackctl_server_create jack server not running? name jack_connect /usr/local/bin/jackd: symbol lookup error: /usr/local/bin/jackd: undefined symbol: jackctl_server_create jack server not running? name jack_connect /usr/local/bin/jackd: symbol lookup error: /usr/local/bin/jackd: undefined symbol: jackctl_server_create jack server not running? slipstream:/usr/local/bin # sample_rate = 96000 ::: Configuration loading completed Adjusting font... Ascent 17 Adjusting font... Ascent 17 Adjusting font... Ascent 15 Adjusting font... Ascent 14 Adjusting font... Ascent 13 Adjusting font... Ascent 12 ::: Memory Cells loading completed Set the frequency. Set the RX Gain. filter_l is: -3220 and filter_h is: -670 Set the frequency. Saving settings... sdr-shell exiting. # nm /usr/local/lib64/libjackserver.so.0.1.0 |grep jackctl_server_create 0000000000048f40 T jackctl_server_create There it is as bold as brass, but somehow can't be found. In jack-0.116.2 symbols stripped. # nm /usr/lib64/libjackserver.so.0.0.28 |grep jackctl_server_create nm: /usr/lib64/libjackserver.so.0.0.28: no symbols Whatever, openSUSE isn't acting correctly. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org