#5 jackd did not work with tascam us122 on minimac

open
nobody
None
5
2006-04-07
2006-04-07
piral
No

Hello there,
I tried jackd to get work with a tascam us122
usb-device on a minimac. Alsa is working well. Aplay
and arecord show the device and I can play and record
things. I get the following output when trying to
start jackd:

jackd -v -dalsa -dplughw:1 -r44100 -p512
getting driver descriptor
from /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.100.7
Copyright 2001-2005 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 ..
apparent rate = 44100
creating alsa driver ... plughw:1|plughw:1|512|2|
44100|0|0|nomon|swmeter|-|32bit
control device hw:1
configuring for 44100Hz, period = 512 frames, buffer
= 2 periods
You appear to be using the ALSA software "plug"
layer, probably
a result of using the "default" ALSA device. This is
less
efficient than it could be. Consider using a hardware
device
instead rather than using the plug layer. Usually the
name of the
hardware device that corresponds to the first soun
nperiods = 2 for capture
You appear to be using the ALSA software "plug"
layer, probably
a result of using the "default" ALSA device. This is
less
efficient than it could be. Consider using a hardware
device
instead rather than using the plug layer. Usually the
name of the
hardware device that corresponds to the first soun
nperiods = 2 for playback
registered builtin port type 32 bit float mono audio
required capabilities not available
capabilities: =
cap_ipc_lock,cap_sys_nice,cap_sys_resource+ep
new client: alsa_pcm, id = 1 type 1 @ 0x10023a88 fd
= -1
new buffer size 512
registered port alsa_pcm:capture_1, offset = 2048
registered port alsa_pcm:capture_2, offset = 4096
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()

the same happens with .r44100 -p1024 which is a
working setting on a i386 arch.

Here some more Information:

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'stable'),
(300, 'testing'), (1,
 'experimental') Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro
(charmap=ISO-8859-15)

Versions of packages jackd depends on:
ii  libc6                         2.3.6-4    GNU C
Library: Shared libraries
 an ii  libcap1                      
1:1.10-14  support for getting/setting
 POSIX.
ii  libjack0.100.0-0              0.100.7-1  JACK
Audio Connection
 Kit (librari
ii  libreadline5                  5.1-7      GNU
readline and
 history libraries ii  libsndfile1                  
1.0.15-2   Library for
 reading/writing audio

jackd recommends no packages.

-- no debconf information

thanks for any help.

R.P.

Discussion