12 Jan
2005
12 Jan
'05
6:57 p.m.
So.. exams gone OK this semester, so i'm returning to linux-audio world :)
unfortunately my tascam us122 still dont work, and the new jack backend
doesn't even compile to me.. dont know what to do.. but, since someone
is using this thing right now on linux, i think there's hope even for me :)
willy@Zeryn:~$ uname -a
Linux Zeryn 2.6.10-mm3 #1 Wed Jan 12 21:01:17 CET 2005 ppc GNU/Linux
willy@Zeryn:~$ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.8rc2 (Wed Jan 05
06:44:40 2005 UTC).
willy@Zeryn:~$ jackd -d alsa -d hw:0
jackd 0.99.0
Copyright 2001-2003 Paul Davis and others.
jackd 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
JACK compiled with System V SHM support
loading driver ..
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
Sorry. The audio interface "hw:0" doesn't support any of the hardware
sample formats that JACK's alsa-driver can use.
ALSA: cannot configure capture channel
cannot load driver module alsa
willy@Zeryn:~$ cd Samples/HistoricalBeats
willy@Zeryn:~/Samples/HistoricalBeats$ aplay -v -D hw:0 amen.wav
Playing WAVE 'amen.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Hardware PCM card 0 'TASCAM US-X2Y' device 0 subdevice 0
Its setup is:
stream : PLAYBACK
access : RW_INTERLEAVED
format : S16_LE
subformat : STD
channels : 2
rate : 44100
exact rate : 44100 (44100/1)
msbits : 16
buffer_size : 16384
period_size : 4096
period_time : 92879
tick_time : 1000
tstamp_mode : NONE
period_step : 1
sleep_min : 0
avail_min : 4096
xfer_align : 4096
start_threshold : 16384
stop_threshold : 16384
silence_threshold: 0
silence_size : 0
boundary : 1073741824
willy@Zeryn:~/Samples/HistoricalBeats$
willy@Zeryn:~/Pacchi/jack-0.99.10.0usx2y$ ./configure
[...]
willy@Zeryn:~/Pacchi/jack-0.99.10.0usx2y$ make
[...]
make[3]: Entering directory
`/home/willy/Pacchi/jack-0.99.10.0usx2y/drivers/usx2y'
if /bin/sh ../../libtool --mode=compile --tag=CC gcc -DHAVE_CONFIG_H -I.
-I. -I../.. -I../../config -I../.. -I../.. -D_REENTRANT
-D_POSIX_PTHREAD_SEMANTICS -Wall -g -O2 -I../../config -I../.. -I../..
-D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -Wall -g -O2 -MT usx2y_driver.lo
-MD -MP -MF ".deps/usx2y_driver.Tpo" -c -o usx2y_driver.lo usx2y_driver.c; \
then mv -f ".deps/usx2y_driver.Tpo" ".deps/usx2y_driver.Plo"; else rm
-f
".deps/usx2y_driver.Tpo"; exit 1; fi
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../config -I../.. -I../..
-D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -Wall -g -O2 -I../../config
-I../.. -I../.. -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -Wall -g -O2 -MT
usx2y_driver.lo -MD -MP -MF .deps/usx2y_driver.Tpo -c usx2y_driver.c
-fPIC -DPIC -o .libs/usx2y_driver.o
usx2y_driver.c: In function `alsa_driver_setup_io_function_pointers':
usx2y_driver.c:292: error: `sample_moveswap_dS_s16' undeclared (first
use in this function)
usx2y_driver.c:292: error: (Each undeclared identifier is reported only once
usx2y_driver.c:292: error: for each function it appears in.)
usx2y_driver.c:300: error: `sample_moveswap_dS_s24' undeclared (first
use in this function)
usx2y_driver.c: In function `alsa_driver_configure_stream':
usx2y_driver.c:334: error: `SND_PCM_FORMAT_S16BE' undeclared (first use
in this function)
usx2y_driver.c:334: error: initializer element is not constant
usx2y_driver.c:334: error: (near initialization for `formats[3].format')
usx2y_driver.c:334: error: initializer element is not constant
usx2y_driver.c:334: error: (near initialization for `formats[3]')
usx2y_driver.c:335: error: `SND_PCM_FORMAT_S16LE' undeclared (first use
in this function)
usx2y_driver.c:335: error: initializer element is not constant
usx2y_driver.c:335: error: (near initialization for `formats[4].format')
usx2y_driver.c:335: error: initializer element is not constant
usx2y_driver.c:335: error: (near initialization for `formats[4]')
make[3]: *** [usx2y_driver.lo] Error 1
make[3]: Leaving directory
`/home/willy/Pacchi/jack-0.99.10.0usx2y/drivers/usx2y'
[...]
willy@Zeryn:~/Pacchi/jack-0.99.10.0usx2y$
if someone has some clue... :)
thanx for the time spent reading this
wil
---
Il jazz e' lasciare che la luce brilli, lasciarla essere.
-- Keith Jarrett
12 Jan
12 Jan
8:15 p.m.
On Thursday 13 January 2005 00:57, Antonio "Willy" Malara wrote:
So.. exams gone OK this semester, so i'm returning
to linux-audio world :)
unfortunately my tascam us122 still dont work, and the new jack backend
doesn't even compile to me.. dont know what to do.. but, since someone
is using this thing right now on linux, i think there's hope even for me :)
I'll recommend you to check whether you got the latest:
1) snd-usb-usx2y >= 0.8.7.1
2) jack-audio-connection-kit >= 0.99.44 (cvs)
If you praise hope, please, don't try with anything else :)
Take care.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
8:43 p.m.
I'll recommend you to check whether you got the
latest:
1) snd-usb-usx2y >= 0.8.7.1
willy@Zeryn:/usr/src/linux-2.6.10/sound/usb/usx2y$ head -6 usbusx2y.c
/*
* usbusy2y.c - ALSA USB US-428 Driver
*
2004-12-14 Karsten Wiese
Version 0.8.7.1:
snd_pcm_open for rawusb pcm-devices now returns -EBUSY if
called without rawusb's hwdep device being open.
willy@Zeryn:/usr/src/linux-2.6.10/sound/usb/usx2y$
checked! :P
2) jack-audio-connection-kit >= 0.99.44 (cvs)
that's what i've missing.. downloaded (from your website) and installed,
this time is compiling, but i have an error regarding hwdep.. i tought
there was another patch to apply, but i cant find it, that's what i get:
willy@Zeryn:/usr/src/linux-2.6.10/sound/usb/usx2y$
LD_PRELOAD="/usr/local/lib/libjack.so.0" /usr/local/bin/jackd -v -d
usx2y -d hw:0
getting driver descriptor from /usr/local/lib/jack/jack_alsa.so
getting driver descriptor from /usr/local/lib/jack/jack_dummy.so
getting driver descriptor from /usr/local/lib/jack/jack_oss.so
getting driver descriptor from /usr/local/lib/jack/jack_usx2y.so
jackd 0.99.44.11cvs
Copyright 2001-2003 Paul Davis and others.
jackd 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
JACK compiled with System V SHM support.
server `default' registered
loading driver ..
experimental alsa driver ...
hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
Couldn't open hw:0 for 32bit samples trying 24bit BE instead
Couldn't open hw:0 for 24bit BE samples trying 24bit LE instead
Couldn't open hw:0 for 32bit samples trying 24bit BE instead
Couldn't open hw:0 for 24bit BE samples trying 24bit LE instead
registered builtin port type 32 bit float mono audio
new client: alsa_pcm, id = 1 type 1 @ 0x100216a8 fd = -1
new buffer size 1024
registered port alsa_pcm:capture_1, offset = 4096
registered port alsa_pcm:capture_2, offset = 8192
registered port alsa_pcm:playback_1, offset = 0
registered port alsa_pcm:playback_2, offset = 0
++ jack_rechain_graph():
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
jackd: hwdep.c:263: snd_hwdep_poll_descriptors: Assertion `hwdep' failed.
Abortito
willy@Zeryn:/usr/src/linux-2.6.10/sound/usb/usx2y$
Take care.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
thanx SO MUCH with your help and your time spent with me :)
wil
---
Il jazz e' lasciare che la luce brilli, lasciarla essere.
-- Keith Jarrett
13 Jan
13 Jan
7:58 a.m.
Antonio "Willy" Malara wrote:
You don't have to look into kernel source code. Try this ones better:
modinfo snd-usb-usx2y
Oh, just in case we're missing something, also give the output of these:
cat /proc/asound/version
cat /proc/asound/cards
cat /proc/asound/pcm
cat /proc/asound/hwdep
Another one thing: if you wanna take advantage of the jackd bleeding edge
code for usx2y, please remember to load the snd-usb-usx2y module with the
nrpacks=1 parameter set, like this:
modprobe snd-usb-usx2y nrpacks=1
or under your /etc/modprobe.conf, something like this
options snd-usb-usx2y index=N nrpacks=1
(N is the soundcard index, probably 0 in your case, but not sure; check it
out from the /proc/asound/cards info) then starting jackd, use the
"hw:N,2" device name instead of just "hw:N" (the later should work
too,
but that's about using the regular alsa interface not the usx2y specific
one).
Good luck :)
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
I'll
recommend you to check whether you got the latest:
1) snd-usb-usx2y >= 0.8.7.1
checked! :P
9:13 a.m.
Rui Nuno Capela ha scritto:
(N is the soundcard index, probably 0 in your case,
but not sure; check it
out from the /proc/asound/cards info) then starting jackd, use the
"hw:N,2" device name instead of just "hw:N" (the later should work
too,
but that's about using the regular alsa interface not the usx2y specific
one).
Good luck :)
uhm.. seems i dont have hw:0,2.. here's what i got
Zeryn:/home/willy/jack-0.99.44.11cvs# modinfo snd-usb-usx2y
filename:
/lib/modules/2.6.10-mm3/kernel/sound/usb/usx2y/snd-usb-usx2y.ko
author: Karsten Wiese <annabellesgarden(a)yahoo.de>
description: TASCAM US-X2Y Version 0.8.7.1
license: GPL
parm: index:Index value for US-X2Y.
parm: id:ID string for US-X2Y.
parm: enable:Enable US-X2Y.
parm: nrpacks:Number of packets per URB.
vermagic: 2.6.10-mm3 preempt gcc-3.3
depends: snd-usb-lib,snd-page-alloc,snd-pcm,snd,snd-hwdep
alias: usb:v1604p8001dl*dh*dc*dsc*dp*ic*isc*ip*
alias: usb:v1604p8007dl*dh*dc*dsc*dp*ic*isc*ip*
alias: usb:v1604p8005dl*dh*dc*dsc*dp*ic*isc*ip*
Zeryn:/home/willy/jack-0.99.44.11cvs# cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.8rc2 (Wed Jan 05
06:44:40 2005 UTC).
Zeryn:/home/willy/jack-0.99.44.11cvs# cat /proc/asound/cards
0 [USX2Y ]: USB US-X2Y - TASCAM US-X2Y
TASCAM US-X2Y (1604:8007 if 0 at 001/003)
Zeryn:/home/willy/jack-0.99.44.11cvs# cat /proc/asound/pcm
00-00: US-X2Y Audio : US-X2Y Audio #0 : playback 1 : capture 1
Zeryn:/home/willy/jack-0.99.44.11cvs# cat /proc/asound/hwdep
00-00: /proc/bus/usb/001/003
Zeryn:/home/willy/jack-0.99.44.11cvs#
Zeryn:/home/willy/jack-0.99.44.11cvs# jackd -v -d usx2y -d hw:0,2
getting driver descriptor from /usr/local/lib/jack/jack_alsa.so
getting driver descriptor from /usr/local/lib/jack/jack_dummy.so
getting driver descriptor from /usr/local/lib/jack/jack_oss.so
getting driver descriptor from /usr/local/lib/jack/jack_usx2y.so
jackd 0.99.44.11cvs
Copyright 2001-2003 Paul Davis and others.
jackd 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
JACK compiled with System V SHM support.
server `default' registered
loading driver ..
experimental alsa driver ...
hw:0,2|hw:0,2|1024|2|48000|0|0|nomon|swmeter|-|32bit
ALSA lib pcm_hw.c:1155:(snd_pcm_hw_open) open /dev/snd/pcmC0D2p failed:
No such device
ALSA lib pcm_hw.c:1155:(snd_pcm_hw_open) open /dev/snd/pcmC0D2c failed:
No such device
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to
capture-only mode
cannot load driver module usx2y
registered builtin port type 32 bit float mono audio
Delay Count
----- ---------
1000 0
----- ---------
Total 0
new client: alsa_pcm, id = 1 type 1 @ 0x100216a8 fd = -1
starting server engine shutdown
freeing shared port segments
stopping server thread
last xrun delay: 0.000 usecs
max delay reported by backend: 0.000 usecs
freeing engine shared memory
max usecs: 0.000, engine deleted
no message buffer overruns
cleaning up shared memory
cleaning up files
unregistering server `default'
Zeryn:/home/willy/jack-0.99.44.11cvs#
wil
---
Il jazz e' lasciare che la luce brilli, lasciarla essere.
-- Keith Jarrett
11:05 a.m.
Antonio "Willy" Malara wrote:
Zeryn:/home/willy/jack-0.99.44.11cvs# jackd -v -d usx2y -d hw:0,2
getting driver descriptor from /usr/local/lib/jack/jack_alsa.so
getting driver descriptor from /usr/local/lib/jack/jack_dummy.so
getting driver descriptor from /usr/local/lib/jack/jack_oss.so
getting driver descriptor from /usr/local/lib/jack/jack_usx2y.so
What? Look: this jack_usx2y.so thing is surely outdated--it belongs to my
older jackd versions, where usx2y support was implemented on a stand-alone
backend driver.
Please, I urge you to remove all jack related stuff from
/usr/local/{bin,lib,include} and then (re)install the newer one. Don't
tell me I didn't warn you ;)
jackd 0.99.44.11cvs
The new (official) usx2y backend was merged into the alsa one, so you
better run the newer jackd with the "alsa" driver instead of the, now
vanished, "usx2y". Start it like this:
a) Using the plain alsa pcm interface:
jackd -d alsa -d hw:0
b) Using the bleeding-edge usx2y hwdep pcm (aka "rawusb") interface:
jackd -d alsa -d hw:0,2
Both modes are perfectly legal but, with this later one, you can run on
much lower latency settings (e.g. -p64 -n2) without crackling your ears :)
Be advised however, that you get far better results if you're running
jackd in realtime mode (-R) *and* under the help of a RT capable kernel,
like 2.6.10-mm1 with Ingo's V0.7.34-01 realtime-preempt patch.
If you really want to work on your us122, seriously, I guess there's no
better way to get around it. IMHO.
Bye now.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
24 Jan
24 Jan
1:16 a.m.
Rui Nuno Capela wrote:
Both modes are perfectly legal but, with this later
one, you can run on
much lower latency settings (e.g. -p64 -n2) without crackling your ears :)
i recollected ideas once again and i've found all the errors i did,
excuse me because you have explained to me many and many times and i've
never understood, basically i tougth that nrpacks was optional for
lowlatency, and frankly for now i want only to use this card, i'll see
for lowlatency after i have a constant sound out of this, even with
100ms latency; then, i found (you were right) a couple of files from
preivous compiling of jack, i removed, recompiled and it gone ok, then i
missed that you merged the jack usx2y driver with alsa's one, so i
retried to recompile everything, new alsa (1.0.8), new jack (0.99.48)
and i've been able to run jack, the card is recognized, but still it
have troubles..
Zeryn:/home/willy/Pacchi/jack-0.99.48-cvs20040122# jackd -dalsa -dhw:0,2
-r44100 -p64 -n2 -S
jackd 0.99.48
[...]
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0,2|hw:0,2|64|2|44100|0|0|nomon|swmeter|-|16bit
control device hw:0
ALSA/USX2Y: EXPERIMENTAL hwdep pcm device hw:0,2 (aka "rawusb")
configuring for 44100Hz, period = 64 frames, buffer = 2 periods
Couldn't open hw:0,2 for 16bit samples trying 24bit instead
Couldn't open hw:0,2 for 24bit samples trying 32bit instead
Sorry. The audio interface "hw:0,2" doesn't support any of the hardware
sample formats that JACK's alsa-driver can use.
ALSA: cannot configure capture channel
i've tried with plug layer (-d plughw:0,2) and it worked, i get some
xruns, but the audio is a loud continous noise.
Be advised however, that you get far better results if
you're running
jackd in realtime mode (-R) *and* under the help of a RT capable kernel,
like 2.6.10-mm1 with Ingo's V0.7.34-01 realtime-preempt patch.
unfortunately i cant compile realtime preempt patches, i've tried almost
any version but they seems to be linux/x86 only. i keep searching some
kind of lowlatency patches that i can apply succesfully
If you really want to work on your us122, seriously, I
guess there's no
better way to get around it. IMHO.
unfortunately i know
Bye now.
bye, and excuse me
wil
---
Il jazz e' lasciare che la luce brilli, lasciarla essere.
-- Keith Jarrett
4:56 a.m.
Antonio "Willy" Malara wrote:
First thing you're missing is probably the realtime-lsm module. Without it
you can't run "jackd -R ..." as a regular user (only as root?).
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Both modes are perfectly legal but, with this
later one, you can run on
much lower latency settings (e.g. -p64 -n2) without crackling your ears
:)
[snip] Zeryn:/home/willy/Pacchi/jack-0.99.48-cvs20040122#
jackd -dalsa -dhw:0,2
-r44100 -p64 -n2 -S
jackd 0.99.48
[...]
loading driver ..
apparent rate = 44100
creating alsa driver ...
hw:0,2|hw:0,2|64|2|44100|0|0|nomon|swmeter|-|16bit
control device hw:0
ALSA/USX2Y: EXPERIMENTAL hwdep pcm device hw:0,2 (aka "rawusb")
configuring for 44100Hz, period = 64 frames, buffer = 2 periods
Couldn't open hw:0,2 for 16bit samples trying 24bit instead
Couldn't open hw:0,2 for 24bit samples trying 32bit instead
Sorry. The audio interface "hw:0,2" doesn't support any of the hardware
sample formats that JACK's alsa-driver can use.
ALSA: cannot configure capture channel
i've tried with plug layer (-d plughw:0,2) and it worked, i get some
xruns, but the audio is a loud continous noise.
What hardware is this?
Anyway, try some deffensive approaches:
1) jackd -R -d alsa -d hw:0 -r44100 -p1024 -n2 -S
2) jackd -R -d alsa -d plughw:0 -r44100 -p1024 -n2 -S
3) repeat without nrpacks=1 parameter
Be advised
however, that you get far better results if you're running
jackd in realtime mode (-R) *and* under the help of a RT capable kernel,
like 2.6.10-mm1 with Ingo's V0.7.34-01 realtime-preempt patch.
unfortunately i cant compile realtime preempt patches, i've tried almost
any version but they seems to be linux/x86 only. i keep searching some
kind of lowlatency patches that i can apply succesfully
26 Jan
26 Jan
12:36 a.m.
Rui Nuno Capela wrote:
What hardware is this?
that's an apple ibook, g3 (750fx) processor at 700mhz clock and 128mb of
ram (i'm going to buy some more), motherboard in /etc/cpuinfo is shown
as "PowerBook4,3 MacRISC2 MacRISC Power Macintosh" the usb controller is
a "USB Controller: Apple Computer Inc. KeyLargo/Pangea USB" which is OHCI
anything else i'm missing?
Anyway, try some deffensive approaches:
1) jackd -R -d alsa -d hw:0 -r44100 -p1024 -n2 -S
with & without the nrpacks=1 i get:
[...]
configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
Couldn't open hw:0 for 16bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 32bit instead
Sorry. The audio interface "hw:0" doesn't support any of the hardware
sample formats that JACK's alsa-driver can use.
[...]
2) jackd -R -d alsa -d plughw:0 -r44100 -p1024 -n2
-S
again, i've a similar behaviour with or without the module parameter:
jack would start giving the advise i'm using the plug layer, it gives me
a storm of xruns, more frequent with nrpacks=1, fewer without the
default nrpacks, but on connecting ports with jack_connect in both cases
jack dies with this error:
ALSA: could not complete playback of 1024 frames: error = -32
cycle execution failure, exiting
DRIVER NT: could not run driver cycle
jack main caught signal 12
no message buffer overruns
Zeryn:/home/willy#
First thing you're missing is probably the
realtime-lsm module. Without it
you can't run "jackd -R ..." as a regular user (only as root?).
yeah, i can run jackd -R only as root, but that's not an issue for now,
i want first to get this card usable, then all the security issues
Cheers.
ciao
wil
---
Il jazz e' lasciare che la luce brilli, lasciarla essere.
-- Keith Jarrett
7396
days inactive
7410
days old
linux-audio-dev@lists.linuxaudio.org
8 comments
2 participants
participants (2)
-
Antonio "Willy" Malara -
Rui Nuno Capela