Page 1 of 1
Tascam US-122Mkii Not supported-True?
Posted: Wed Feb 01, 2017 2:16 am
by Prsman
Hi everyone, I'm new here. I have a Tascam US-122 MKII usb audio interface that I would like to use with Linux. I found a couple of web sites that give instructions on how to configure it. But on the ALSA web site it lists this card as not supported. Has anyone here got it to work under Linux? Is there a list of cards that are known to work with Linux? I have spent three days trying to get it to work, I think I am flogging a dead horse.
The card shows up in /proc/asound/cards. Jack wont connect the input to the computer. If anyone can help one way or another I'd be grateful.
Web site instructions below. Thanks
http://linuxmao.org/Tascam+US-122+MKII? ... l+Materiel
Re: Tascam US-122Mkii Not supported-True?
Posted: Sun Feb 05, 2017 8:04 pm
by progwolff
I had a US-122 MKII too.
The audio output was working without problems, although I had some strange noise every ten minutes or so, which were persistent until I unplugged the interface and plugged it in again. But this problem did also exist on MS Windows.
I got the audio input working once, but can't exactly remember how I did it. I think I blacklisted snd-usb and loaded a driver for a different Tascam device. As I couldn't get rid of the recurring noises, I switched to a different interface.
Re: Tascam US-122Mkii Not supported-True?
Posted: Mon Feb 06, 2017 9:16 am
by CrocoDuck
Apparently the US-144MKII can be controlled by the 122L driver. Maybe the process to make the 122MKII to work is similar to
the one to make the 144MKII to work.
Prsman wrote: Is there a list of cards that are known to work with Linux?
There are few but they are old on not very often updated. I think perhaps ALSA matrix is the best resource...
Re: Tascam US-122Mkii Not supported-True?
Posted: Mon Feb 06, 2017 11:35 am
by progwolff
I just got my hands on my old Tascam US 122mkII.
Using Arch Linux 4.9.4-1-ck, these are the steps how I got the audio inputs working:
Blacklist snd_usb_audio. For this, add the line
to /etc/modprobe.d/50-blacklist.conf.
Reboot your system. Plug in the Tascam interface.
now finds a TASCAM US-122L instead of the TASCAM US-122mkII which is found with snd_usb_audio loaded.
Now continue as described at linuxmao:
edit ~/.asoundrc:
Code: Select all
# got from http://www.nabble.com/tascam-us122l-and-ccrma-td24036395.html
# thanks to Karsten
# The usb_stream plugin configuration
pcm.!usb_stream {
@args [ CARD ]
@args.CARD {
type string
default "0"
}
type usb_stream
card $CARD
}
ctl.!usb_stream {
@args [ CARD ]
@args.CARD {
type string
default "0"
}
type hw
card $CARD
}
Start jack:
Code: Select all
jackd -P80 -dalsa -dusb_stream:1 -r96000 -p128 -n2
There are however only few combinations of parameters that work with this interface, these seem to do the trick.
Re: Tascam US-122Mkii Not supported-True?
Posted: Mon Feb 06, 2017 11:59 pm
by Prsman
Thanks for the replies. I am only using this for rakarack and guitarix, not recording, so noise wont bother me.
I'm running Mint 18 Cinnamon. Progwolff, your reply might explain why I get this:
Code: Select all
~ $ cat /proc/asound/modules
0 snd_hda_intel
1 snd_usb_audio
2 snd_usb_audio
Number one is the tascam card and 2 is my webcam. As I am new to linux, how do I modify the .asoundrc file from Linuxmao?
Code: Select all
~ $ cat /proc/asound/cards
0 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xfe024000 irq 21
1 [MKII ]: USB-Audio - US122 MKII
TASCAM US122 MKII at usb-0000:00:02.1-2, high speed
2 [Camera ]: USB-Audio - PC Camera
V Micro. Corp. PC Camera at usb-0000:00:02.0-3, full speed
What and where do I put into the asoundrc file? Thanks.
Re: Tascam US-122Mkii Not supported-True?
Posted: Tue Feb 07, 2017 1:53 am
by MattKingUSA
I had one of these a while back and ended up giving it to my brother. I could not get it to work under Linux.
Re: Tascam US-122Mkii Not supported-True?
Posted: Tue Feb 07, 2017 9:34 am
by progwolff
Prsman wrote:What and where do I put into the asoundrc file? Thanks.
Just put it to ~/.asoundrc (which expands to /home/$USER/.asoundrc)
Re: Tascam US-122Mkii Not supported-True?
Posted: Tue Feb 07, 2017 11:57 pm
by Prsman
Thanks for the replies everyone. I tried the blacklist and reboot/replug-in and the card does not show up at all. Something weird is this has two, yes two drivers. From hwinfo:
Code: Select all
20: USB 00.0: 0000 Unclassified device
[Created at usb.122]
Unique ID: cLrx.lsbtgcyGIpB
Parent ID: k4bc.OqydEZZ981A
SysFS ID: /devices/pci0000:00/0000:00:02.1/usb1/1-2/1-2:1.0
SysFS BusID: 1-2:1.0
Hardware Class: unknown
Model: "TEAC TASCAM US-122mkII"
Hotplug: USB
Vendor: usb 0x0644 "TEAC Corp."
Device: usb 0x8021 "TASCAM US-122mkII"
Revision: "1.00"
Serial ID: "no serial number"
Driver: "snd-usb-audio"
Driver Modules: "snd_usb_audio"
Speed: 480 Mbps
Module Alias: "usb:v0644p8021d0100dc00dsc00dp00icFFisc00ip00in00"
Driver Info #0:
Driver Status: snd_usb_audio is active
Driver Activation Cmd: "modprobe snd_usb_audio"
Driver Info #1:
Driver Status: snd_usb_us122l is active
Driver Activation Cmd: "modprobe snd_usb_us122l"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #19 (Hub)
I think its time for this device to take a long walk off a short pier. If anyone has an idea, if not I will close this post. Thanks
Re: Tascam US-122Mkii Not supported-True?
Posted: Wed Feb 08, 2017 3:30 pm
by progwolff
snd_usb_audio is active.
As I said, you will need to blacklist snd_usb_audio.
Re: Tascam US-122Mkii Not supported-True?
Posted: Wed Feb 27, 2019 6:16 pm
by alfredo
Hi, the instructions given by progwolff works for me but I have a question.
Why is necesary to reboot to get the card detected ?
I start ubuntu (with the card plugged), it doesn't get detected. I unplug and plug again the card, still doesn't get detected. I reboot and the card is detected.
Somebody knows if there is a command to run to get the card detected without rebooting ?
I tried with sudo modprobe snd-usb-us122l with no luck ...
Regards, Alfredo
Re: Tascam US-122Mkii Not supported-True?
Posted: Sun Mar 03, 2019 8:24 pm
by alfredo
Hi, this seems to do the trick for me
sudo rmmod snd_usb_us122l
sudo modprobe snd_usb_us122l enable=1 index=1 id=1
For more details see
https://wiki.briata.org/doku.php
Regards, Alfredo
Re: Tascam US-122Mkii Not supported-True?
Posted: Tue Apr 07, 2020 3:44 pm
by hdr
progwolff wrote: ↑Mon Feb 06, 2017 11:35 am
I just got my hands on my old Tascam US 122mkII.
Using Arch Linux 4.9.4-1-ck, these are the steps how I got the audio inputs working:
Blacklist snd_usb_audio. For this, add the line
to /etc/modprobe.d/50-blacklist.conf.
Reboot your system. Plug in the Tascam interface.
now finds a TASCAM US-122L instead of the TASCAM US-122mkII which is found with snd_usb_audio loaded.
Now continue as described at linuxmao:
edit ~/.asoundrc:
Code: Select all
# got from http://www.nabble.com/tascam-us122l-and-ccrma-td24036395.html
# thanks to Karsten
# The usb_stream plugin configuration
pcm.!usb_stream {
@args [ CARD ]
@args.CARD {
type string
default "0"
}
type usb_stream
card $CARD
}
ctl.!usb_stream {
@args [ CARD ]
@args.CARD {
type string
default "0"
}
type hw
card $CARD
}
Start jack:
Code: Select all
jackd -P80 -dalsa -dusb_stream:1 -r96000 -p128 -n2
There are however only few combinations of parameters that work with this interface, these seem to do the trick.
I did the steps above, but it doesn't work:
Code: Select all
jackd -P80 -dalsa -dusb_stream:1 -r96000 -p128 -n2
jackdmp 1.9.12
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2018 Filipe Coelho.
jackdmp 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
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 80
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Device reservation request with priority 2147483647 denied for "Audio1": org.freedesktop.DBus.Error.NoReply (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply,
Failed to acquire device name : Audio1 error : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broke
Audio device usb_stream:1 cannot be acquired...
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server