Hi all, some infos:
suse 10.1 32bit
alsa 1.0.11-32
alsa-firmware 1.0.10-13
alsa-tools 1.0.11-16
jack 1.101.1 (new 'cause I read there's a better support for us428 in new
versions)
I load the firmware with usx2yloader, then i run us428control. Everything seems
fine: 1-2 ins, midi in and
hi,
> One of those patches is targeted about some issues regarding whether the
> snd-usb-usx2y driver is built with debug support. In my case, the us224
> audio playback and input monitoring only shows up when one builds
> alsa-driver-1.0.4 with ./configure --with-debug=full . You can check if
> t
Hi and welcome.
I have a us224 and it's fairly working after some exchange on alsa-devel
list and a couple of specific patches since 1.0.4, which I think are now
available on cvs.
To my knowledge, the us428 is the big brother of us224. IIRC the driver
and userland development has been almost base
hi,
i need some help getting the tascam us428 running, hoping anybody has
already managed to do this.
i'm using alsa 1.0.4 on a gentoo system with kernel 2.6.5. i manually
installed alsa-driver 1.0.4 over the original modules from the kernel
tree.
the us428 seems to be recognized by the system,
Hi,
I'm getting closer to using the Tascam US428 on RedHat 8.0 with ALSA
1.0.1 on a low-latency 2.4.21 kernel. I've managed to get the Tascam to
show up in /proc/asound/cards and in the list of devices on Audacity. I
even got a 0.5 second burst of sound followed by a complete system
freeze (runni
Hello,
I just realized the Tascam US428 is usable with ALSA now.
Could anybody tell me about the latency?
I have it running on w2k using PD and the portaudio-asioport and somehow it
takes 1 input buffer and 4 output buffers (which are not adjustable
(latency= 5*buffer). Contrary the RME 9652 just
