Getting Tascam US-144 to work under Ubuntu - 50 BTC

[Mahkul]

I have been trying to get this damn soundcard to work under Ubuntu for two days now. Anyone got it to work?

I followed this:

http://wiki.ubuntuusers.de/Benutzer/BigMc/Tascam_US-144

And this is what I get when trying to test:

Code:

mahkul@mahkul:~$ jackd -RP50 -dalsa -dusb_stream:1 -r44100 -p64 -n2
jackdmp 1.9.6
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2010 Grame.
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
JACK server starting in realtime mode with priority 50
audio_reservation_init
Acquire audio card Audio1
creating alsa driver ... usb_stream:1|usb_stream:1|64|2|44100|0|0|nomon|swmeter|-|32bit
Using ALSA driver USB US-122L running on card 1 - TASCAM US-122L (644:800f if 0 at 003/005)
configuring for 44100Hz, period = 64 frames (1.5 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 24bit little-endian
ALSA: use 2 periods for capture
Couldn't configure usb_stream
: Invalid argument
ALSA: cannot set hardware parameters for capture
ALSA: cannot configure capture channel
Cannot initialize driver
JackServer::Open() failed with -1
Failed to start server

However, when I start qjackctl I am able to press START:

Code:

01:24:56.052 Patchbay deactivated.
01:24:56.081 Statistics reset.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
01:24:56.108 ALSA connection graph change.
01:24:56.527 ALSA connection change.
01:25:05.018 Startup script...
01:25:05.019 artsshell -q terminate
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
sh: artsshell: not found
01:25:05.421 Startup script terminated with exit status=32512.
01:25:05.421 JACK is starting...
01:25:05.421 /usr/bin/jackd -dalsa -dusb_stream:1 -r44100 -p1024 -n2
01:25:05.424 JACK was started with PID=2977.
no message buffer overruns
no message buffer overruns
jackdmp 1.9.6
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2010 Grame.
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
JACK server starting in realtime mode with priority 10
audio_reservation_init
Acquire audio card Audio1
creating alsa driver ... usb_stream:1|usb_stream:1|1024|2|44100|0|0|nomon|swmeter|-|32bit
Using ALSA driver USB US-122L running on card 1 - TASCAM US-122L (644:800f if 0 at 003/005)
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 24bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 24bit little-endian
ALSA: use 2 periods for playback
01:25:07.609 Statistics reset.
01:25:07.628 Client activated.
01:25:07.655 JACK connection change.
01:25:07.664 JACK connection graph change.
01:25:11.360 Transport start.

When I try to play an MP3 file it looks like it's playing, but I can't hear a thing.

I will give 50 BTC to anyone who will sort this out for me.

[1715173023]

1715173023

[1715173023]

1715173023

[jungletek]

I think this is what's happening, but it's just a mildly educated guess at best, I'm much better with Wintel than *nix.

Maybe the problem is in the first pasted block of terminal output:

Couldn't configure usb_stream
: Invalid argument

means that you are somehow passing a bad commandline argument to the jack server and it fails to start, then in the second block of terminal output you have the client configured properly (hopefully) and running, but no server running to feed audio to it.

So, I would check the config file for the jack server, which I assume is "~/.asoundrc (in your home directory)" looking for a typo or other mistake near the "usb_stream" parameter(s). But then you're also getting socket errors, so it could be something else in that config file. I'll have another look at it tomorrow when I'm well-rested.

Apologies if you've already investigated and discounted this. Believe it or not, about a year ago I managed to get Ableton Live working through WINE with my crappy onboard sound at the time, with ASIO4All and MIDI working. Decent latencies too. But it was hellish to set up, both in its fiddliness and it's unfriendliness to noobs.

Let us know if this somehow manages to fix one thing and expose the next broken link in the chain.

Good luck fellow paint sniffer.

[teramit]

50 btc great