TASCAM US-800

Talk about your MIDI interfaces, microphones, keyboards...

Moderators: khz, MattKingUSA

Post Reply
muzikermammoth
Established Member
Posts: 18
Joined: Sun Jun 09, 2019 6:10 pm

TASCAM US-800

Post by muzikermammoth »

This is for the older discontinued model. And for ubuntu studio. They were going at really cheap prices then so this was a great chance to try it out ...

To get this model to work on linux:
1. power on computer
2. power on usb device
2.1 tail -f /var/log/syslog
2.2 you'll see the kernel try to initialise some usb settings but without success
2.3 wait till the end when it stops and sets it registers a new interface driver snd-usb-audio, this took about 1 minute
2.4 watch aplay -l to continuously watch for the device to get registered
3. Before starting any application, jack needs to be configured with the exact settings for this to work
3.1 select the US800 as the default device in qjackctl ( i haven't tried this with ubuntustudio sound control )
3.2 set the input=8 and output=6
3.3 test audio
4. Configure pulseaudio. At this stage, pulseaudio should be trying to handoff to a jack soundcard, but it won't be able to detect it, and will use a dummy output instead.
5. pacmd to get to the command prompt for pulseaudio
6. list-modules to see all loaded modules. The one needed isn't auto loaded because jack wasn't properly configured.
7. load-module module-jackdbus-detect channels=6
8. test audio

At the moment audio seems to be working fine, but there's a short regular static burst, that sounds like it could be some kind of bus noise. But it could be my cables. Hopefully this is helpful to everyone who bought the soundcard. alsamixer won't be able to load the drivers
Last edited by muzikermammoth on Fri Feb 14, 2020 9:57 am, edited 1 time in total.

muzikermammoth
Established Member
Posts: 18
Joined: Sun Jun 09, 2019 6:10 pm

Re: TASCAM US 800

Post by muzikermammoth »

OK so don't use this for linux. It definitely doesn't work.

So other than the 1 minute boot up time before the kernel registers the device. After a certain period of it running, there are a bunch of no responses to the usb request blocks, and there'll be a sudden spike in urb misses and the device will become unresponsive. if someone can run this on a windows and figure out what to send to the device, there might be a way to get this working. But as it is, it isn't.

Post Reply