[opensuse-factory] Changing alsa default sample rate
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? 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
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? Regards Sid.
Am I mistaken that this list is only for eye-candy and GUI debates? I'd think so by the number of questions I posed over years that have been met with total silence. Either like me nobody knows or nobody cares. I tend to use the distro for real stuff, not as complex as the requirement of rocket scientists, but to do much "simpler" stuff. An example of what I mean is as shown above. I can find solutions which apply to other distros which do not work with openSUSE, so someone who puts this stuff together should readily be able to offer a solution. Next connundrum:- #!/bin/bash # define name used in the RMI registry export NAME=SDR-SHELL export SDR_DEFRATE=48000 export JACK_BUFFER=1024 # start jackd (firewir-Phw:0 -Chw:1e fa-66) echo "starting jackd ..." #DELTA-44 pasuspender -- /usr/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/bin/jack_connect system:capture_1 ${NAME}_RX:il sleep 2 /usr/bin/jack_connect system:capture_2 ${NAME}_RX:ir sleep 2 /usr/bin/jack_connect ${NAME}_RX:ol system:playback_1 sleep 2 /usr/bin/jack_connect ${NAME}_RX:or system:playback_2 sleep 2 # start sdr-shell sdr-shell& ========================================================================== 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? Also running /usr/local/bin/jackd or using findsym to look for known jack2 symbols, can't be found, /usr/local/lib64 is a search path in findsym. # nm /usr/local/lib64/libjackserver.so.0.1.0|grep jackctl_server_create 0000000000048f40 T jackctl_server_create "which jackd" says /usr/local/bin, but the script explicitly says "/usr/bin/jackd". 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 ... /usr/local/bin/jackd: symbol lookup error: /usr/local/bin/jackd: undefined symbol: jackctl_server_create jack server not running? /usr/local/bin/jackd: symbol lookup error: /usr/local/bin/jackd: undefined symbol: jackctl_server_create jack server not running? /usr/local/bin/jackd: symbol lookup error: /usr/local/bin/jackd: undefined symbol: jackctl_server_create jack server not running? /usr/local/bin/jackd: symbol lookup error: /usr/local/bin/jackd: undefined symbol: jackctl_server_create jack server not running? slipstream:/usr/src # sample_rate = 48000 ::: 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. Set the frequency. Set the frequency. Set the RX Gain. Set the RX Gain. Saving settings... sdr-shell exiting. slipstream:/usr/src # which jackd /usr/local/bin/jackd # ps fax|grep jack 26583 pts/0 S+ 0:00 | \_ grep jack 26536 pts/0 S 0:00 pasuspender -- /usr/bin/jackd -dalsa -Phw:0 -Chw:2 -r48000 -p1024 -s -n2 26539 ? Ssl 0:00 \_ /usr/bin/jackd -dalsa -Phw:0 -Chw:2 -r48000 -p1024 -s -n2 No idea why it starts /usr/bin/jackd correctly, then tries to start the other one as that not what the scripts asks. 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
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
Am I mistaken that this list is only for eye-candy and GUI debates? I'd think so by the number of questions I posed over years that have been met with total silence. Either like me nobody knows or nobody cares.
It reflects nothing but the interest of readers of this ML... (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 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
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
Am I mistaken that this list is only for eye-candy and GUI debates? I'd think so by the number of questions I posed over years that have been met with total silence. Either like me nobody knows or nobody cares.
It reflects nothing but the interest of readers of this ML...
(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
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. 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 jackdmp 1.9.4 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2009 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details could not open driver .so '/usr/local/lib64/jack/jack_oss.so': /usr/local/lib64/jack/jack_oss.so: undefined symbol: _jack_get_microseconds could not open component .so '/usr/local/lib64/jack/jack_oss.so': /usr/local/lib64/jack/jack_oss.so: undefined symbol: _jack_get_microseconds jackdmp version 1.9.4 tmpdir /dev/shm protocol 7 gcc version 4.4.2 [gcc-4_4-branch revision 154496] (SUSE Linux) Kubuntu 9.10 x86_64 ==================== root@lancelot-desktop:/usr/src/JACK2/trunk/jackmp# LD_LIBRARY_PATH=/usr/local/lib64 /usr/local/bin/jackd -V jackdmp 1.9.5 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2009 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details no message buffer overruns no message buffer overruns jackdmp version 1.9.5 tmpdir /dev/shm protocol 7 root@lancelot-desktop:/usr/src/JACK2/trunk/jackmp# gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) 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
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...
Am I mistaken that this list is only for eye-candy and GUI debates? I'd think so by the number of questions I posed over years that have been met with total silence. Either like me nobody knows or nobody cares.
It reflects nothing but the interest of readers of this ML...
(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.
jackdmp 1.9.4 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2009 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details could not open driver .so '/usr/local/lib64/jack/jack_oss.so': /usr/local/lib64/jack/jack_oss.so: undefined symbol: _jack_get_microseconds could not open component .so '/usr/local/lib64/jack/jack_oss.so': /usr/local/lib64/jack/jack_oss.so: undefined symbol: _jack_get_microseconds
For such a problem, check ldd output to figure out what's going wrong. But I have no more time, so I hope anyone else will follow... Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
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. See at end of this article.
jackdmp 1.9.4 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2009 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details could not open driver .so '/usr/local/lib64/jack/jack_oss.so': /usr/local/lib64/jack/jack_oss.so: undefined symbol: _jack_get_microseconds could not open component .so '/usr/local/lib64/jack/jack_oss.so': /usr/local/lib64/jack/jack_oss.so: undefined symbol: _jack_get_microseconds
For such a problem, check ldd output to figure out what's going wrong.
But I have no more time, so I hope anyone else will follow...
Takashi
Thanks, I hope someone else will give it a try. The Kubuntu behaviour is correct, the openSUSE behaviour is not. slipstream:/home/lancelot/ftp/dec09/jack-1.9.4 # ldd /usr/local/bin/jackd linux-vdso.so.1 => (0x00007fff7a146000) libjackserver.so.0 => /usr/lib64/libjackserver.so.0 (0x00007fa3c8924000) <<================ libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa3c8708000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fa3c8504000) librt.so.1 => /lib64/librt.so.1 (0x00007fa3c82fb000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fa3c7feb000) libm.so.6 => /lib64/libm.so.6 (0x00007fa3c7d96000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fa3c7b7f000) libc.so.6 => /lib64/libc.so.6 (0x00007fa3c7824000) /lib64/ld-linux-x86-64.so.2 (0x00007fa3c8b4e000) slipstream:/home/lancelot/ftp/dec09/jack-1.9.4 # LD_LIBRARY_PATH=/usr/local/lib64 ldd /usr/local/bin/jackd linux-vdso.so.1 => (0x00007fff909ff000) libjackserver.so.0 => /usr/local/lib64/libjackserver.so.0 (0x00007f4ec5e67000) <<======================= libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f4ec5c4b000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f4ec5a47000) librt.so.1 => /lib64/librt.so.1 (0x00007f4ec583e000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f4ec552e000) libm.so.6 => /lib64/libm.so.6 (0x00007f4ec52d9000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f4ec50c2000) libc.so.6 => /lib64/libc.so.6 (0x00007f4ec4d67000) /lib64/ld-linux-x86-64.so.2 (0x00007f4ec60dc000) slipstream:/home/lancelot/ftp/dec09/jack-1.9.4 # Kubuntu behaves the same way, needing LD_LIBRARY_PATH set when multiple versions of libraries exist. 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
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
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
On 09/12/09 21:34, Sid Boyce wrote:
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.
I just did a "svn up", built and installed jack2, problem fixed. Some unknown reason the previous code was incompatible with openSUSE, but not with Kubuntu. slipstream:/home/lancelot/ftp/dec09/trunk/jackmp # LD_LIBRARY_PATH=/usr/local/lib64 /usr/local/bin/jackd -V jackdmp 1.9.5 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2009 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details jackdmp version 1.9.5 tmpdir /dev/shm protocol 7 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
At Thu, 10 Dec 2009 01:49:57 +0000, Sid Boyce wrote:
I just did a "svn up", built and installed jack2, problem fixed. Some unknown reason the previous code was incompatible with openSUSE, but not with Kubuntu.
Who knows which is "correct". It's possible that Ubuntu didn't do the right thing, worked just coincidentally. My rough guess is that it's a setup related with linker in jack2's wscript, and it's been fixed recently. Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 10/12/09 07:53, Takashi Iwai wrote:
At Thu, 10 Dec 2009 01:49:57 +0000, Sid Boyce wrote:
I just did a "svn up", built and installed jack2, problem fixed. Some unknown reason the previous code was incompatible with openSUSE, but not with Kubuntu.
Who knows which is "correct". It's possible that Ubuntu didn't do the right thing, worked just coincidentally.
Possibly, but behaviour from the very earliest distros like SLS, Slackware to SUSE 6.0, RedHat I have ever handled were all the same, I even have openSUSE scripts from way back that used LD_LIBRARY_PATH. This was the first time I saw it ignored.
My rough guess is that it's a setup related with linker in jack2's wscript, and it's been fixed recently.
Takashi
Most likely. 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
2009/12/7 Sid Boyce <sboyce@blueyonder.co.uk>:
Am I mistaken that this list is only for eye-candy and GUI debates? I'd think so by the number of questions I posed over years that have been met with total silence. Either like me nobody knows or nobody cares.
Interested to see how this works out. If you ask good questions, likely noone really does know the answer off pat, and archeological style dig for clues from obscure mail list & docs is necessary. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 07/12/09 17:32, Rob OpenSuSE wrote:
2009/12/7 Sid Boyce <sboyce@blueyonder.co.uk>:
Am I mistaken that this list is only for eye-candy and GUI debates? I'd think so by the number of questions I posed over years that have been met with total silence. Either like me nobody knows or nobody cares.
Interested to see how this works out. If you ask good questions, likely noone really does know the answer off pat, and archeological style dig for clues from obscure mail list & docs is necessary.
I have a habit of running into such issues. The previous big one was a kernel bug due to a typo that had been in the kernel for ages, but only bit with the then latest kernel. Only one other guy hit the same problem two weeks after I did. My background is in trying to break software well before it causes customer grief. 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
participants (3)
-
Rob OpenSuSE -
Sid Boyce -
Takashi Iwai