Tascam US-2x2

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

Moderators: MattKingUSA, khz

Post Reply
marianet
Posts: 1
Joined: Mon Nov 17, 2014 7:09 pm

Tascam US-2x2

Post by marianet »

I have tested a Tascam US-2x2 in a laptop with avlinux, and it works. I can record at 96 Khz.
It uses a USB class compliant driver.
andy_march
Posts: 2
Joined: Sun Nov 22, 2015 11:17 pm

Re: Tascam US-2x2

Post by andy_march »

cidian wrote:Thanks for sharing, good to know! I'm considering buying this interface, has anyone else had any experience with it?
I'm going to try one in today, so I will be able to share my impression if you are still interesting in it.
andy_march
Posts: 2
Joined: Sun Nov 22, 2015 11:17 pm

Re: Tascam US-2x2

Post by andy_march »

I have just bought one. As it described above - it works out of box (debian 8.2 jessie). Sampling rate is 96kHz but sample size is 16 bits and I can't change it using qjackctl. I will write again if solution is found.
Plenus
Posts: 1
Joined: Sat Feb 13, 2016 6:12 pm

Re: Tascam US-2x2

Post by Plenus »

I just bought a Tascam US-2x2, as an upgrade from my old Behringer U-Phono UFO202. I was very glad to see it has worked on Debian, as it gave me hope it would also work out-of-the-box on my Ubuntu 14.04.3 LTS ("Trusty"), but alas, no: plugging it in produced no new ALSA sound card entry. Also tried it on my laptop (same Ubuntu version). The Behringer always worked out-of-the-box, so I didn't really know what to try next. I did install alsa-firmware-loaders, but that had no effect that i can see.

Anything any other Linux users can tell me about what I might try to get ALSA to see it on Ubuntu? Thanks!

The output from cat /proc/asound/cards only shows my built-in sound card:

Code: Select all

 0 [MID            ]: HDA-Intel - HDA Intel MID
                      HDA Intel MID at 0xf0600000 irq 28
Here's the output from dmesg :

Code: Select all

[ 2747.882541] usb 2-1.1: new high-speed USB device number 9 using ehci-pci
[ 2747.976128] usb 2-1.1: New USB device found, idVendor=0644, idProduct=804f
[ 2747.976136] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2747.976141] usb 2-1.1: Product: TASCAM US-2x2
[ 2747.976144] usb 2-1.1: Manufacturer: TEAC Corporation
[ 2747.978168] hid-generic 0003:0644:804F.0008: hiddev0,hidraw4: USB HID v1.10 Device [TEAC Corporation TASCAM US-2x2] on usb-0000:00:1d.0-1.1/input0
Neonblack
Posts: 1
Joined: Thu May 25, 2017 1:59 pm

Re: Tascam US-2x2

Post by Neonblack »

Recent Debian unstable (May 2017) worked (almost) out of the box. On first connection, dmesg looked like this

[45628.886308] usb 3-4: parse_audio_format_rates_v2(): unable to find clock source (clock -110)
[45649.366609] usb 3-4: cannot get ctl value: req = 0x83, wValue = 0x201, wIndex = 0xa00, type = 4
[45649.366623] usb 3-4: 10:0: cannot get min/max values for control 2 (id 10)
[45654.486651] usb 3-4: cannot get ctl value: req = 0x83, wValue = 0x201, wIndex = 0xb00, type = 4
[45654.486655] usb 3-4: 11:0: cannot get min/max values for control 2 (id 11)
[45659.606713] usb 3-4: cannot get ctl value: req = 0x83, wValue = 0x201, wIndex = 0xa00, type = 4
[45659.606717] usb 3-4: 10:0: cannot get min/max values for control 2 (id 10)
[45664.726821] usb 3-4: cannot get ctl value: req = 0x83, wValue = 0x201, wIndex = 0xb00, type = 4
[45664.726824] usb 3-4: 11:0: cannot get min/max values for control 2 (id 11)
[45721.027831] usbhid 3-4:1.4: can't add hid device: -110
[45721.027843] usbhid: probe of 3-4:1.4 failed with error -110
[45721.027907] usb 3-4: USB disconnect, device number 10

After a while, it became alive on it's own.

[45721.291794] usb 3-4: new high-speed USB device number 11 using xhci_hcd
[45721.432618] usb 3-4: New USB device found, idVendor=0644, idProduct=8045
[45721.432620] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[45721.432620] usb 3-4: Product: US-2x2
[45721.432621] usb 3-4: Manufacturer: TEAC Corporation
[45721.977159] hid-generic 0003:0644:8045.0006: hiddev0,hidraw5: USB HID v1.10 Device [TEAC Corporation US-2x2] on usb-0000:00:14.0-4/input4

Similar experience with another device of this type. The other device was working after being connected to a windows machine (to see if it's not broken). Seems like there is something magic about the first power on.

Regards,

Martin
Post Reply