Sorry if this question has been answered before, but I've read a number of articles on how to get this to work, and I'm not sure where I'm going wrong. I'm hoping someone could point me in the right direction.
(please bear in mind - I'm relatively new to Ubuntu, but happy to learn)
I'm on Ubuntu 11.10, Kernel 3.0.0-14-Generic
I have the alsa-tools, alsa-firmware-loaders, and alsa-firmware packages installed,
Then, I've unbound the USB 2.0 controllers.
typing: cat /proc/asound/cards in the terminal returns:
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xd4700000 irq 45
1 [US122L ]: USB US-122L - TASCAM US-122L
TASCAM US-122L (644:800f if 0 at 007/006)
Here's where I run into problems - when I open qJackctl, and enter the Settings menu, set interface to usb_stream:1, hit Ok and press Start, I receive the following errors:
"D-BUS: ResetParameterValue('engine:name'):
Unknown engine parameter 'name'.
(org.jackaudio.Error.UnknownParameter)"
then
"D-BUS: ResetParameterValue('driver:midi-driver'):
Unknown parameter 'midi-driver' for driver 'alsa'.
(org.jackaudio.Error.UnknownParameter)"
finally,
"Could not connect to JACK server as client.
- Overall operation failed.
- Unable to connect to server.
Please check the messages window for more info."
Here's the printout from the messages window.
23:45:41.357 Patchbay deactivated.
23:45:41.372 Statistics reset.
23:45:41.464 ALSA connection change.
23:45:41.802 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
23:45:41.843 ALSA connection graph change.
23:46:58.096 D-BUS: ResetParameterValue('engine:name'): Unknown engine parameter 'name'. (org.jackaudio.Error.UnknownParameter)
Wed Jan 18 23:46:58 2012: ERROR: Unknown engine parameter 'name'
23:50:43.913 D-BUS: ResetParameterValue('driver:midi-driver'): Unknown parameter 'midi-driver' for driver 'alsa'. (org.jackaudio.Error.UnknownParameter)
Wed Jan 18 23:50:43 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:50:43 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:50:43 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:50:43 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:50:43 2012: driver "alsa" selected
Wed Jan 18 23:50:43 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:50:43 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:50:43 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:50:43 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:50:43 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:50:43 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:50:43 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:50:43 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:50:43 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:50:43 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:50:43 2012: ERROR: Unknown parameter 'midi-driver' for driver 'alsa'
23:51:01.366 D-BUS: JACK server is starting...
Wed Jan 18 23:51:00 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:51:00 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:51:00 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:51:00 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:51:00 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:51:00 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:51:00 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:51:00 2012: Saving settings to "/home/kevin/.config/jack/conf-jack1.xml" ...
Wed Jan 18 23:51:00 2012: Starting jack server...
Wed Jan 18 23:51:00 2012: Using System timer as clock source.
Wed Jan 18 23:51:00 2012: JACK compiled with System V SHM support.
Wed Jan 18 23:51:00 2012: loading driver "alsa" ...
Wed Jan 18 23:51:00 2012: apparent rate = 44100
Wed Jan 18 23:51:00 2012: creating alsa driver ... usb_stream:1|usb_stream:1|1024|19|44100|0|0|nomon|swmeter|-|32bit
Wed Jan 18 23:51:01 2012: configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 19 periods
Wed Jan 18 23:51:01 2012: ALSA: final selected sample format for capture: 24bit little-endian
Wed Jan 18 23:51:01 2012: ERROR: ALSA: got smaller periods 2 than 19 for capture
Wed Jan 18 23:51:01 2012: ERROR: ALSA: cannot configure capture channel
Wed Jan 18 23:51:01 2012: ERROR: cannot load driver module alsa
Wed Jan 18 23:51:01 2012: ERROR: Failed to start server
23:51:03.388 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Any help would be greatly appreciated.
Thanks,
Kevin
[SOLVED] Tascam US-144 & Ubuntu 11.10
Moderators: MattKingUSA, khz
-
KevinGormley
- Established Member
- Posts: 5
- Joined: Thu Jan 19, 2012 2:20 am
[SOLVED] Tascam US-144 & Ubuntu 11.10
Last edited by KevinGormley on Sun Jan 22, 2012 6:10 pm, edited 1 time in total.
Re: Tascam US-144
I don't have that card but I would look at these outputs. Feel free to post them here:
cat /home/kevin/.config/jack/conf-jack1.xml
Also
cat /proc/asound/modules ~/.asoundrc
and try setting the periods/buffer to 3, instead of 19.
cat /home/kevin/.config/jack/conf-jack1.xml
Also
cat /proc/asound/modules ~/.asoundrc
and try setting the periods/buffer to 3, instead of 19.
-
KevinGormley
- Established Member
- Posts: 5
- Joined: Thu Jan 19, 2012 2:20 am
Re: Tascam US-144
Hi Pablo,
Thanks for the suggestions, I probably should have thought to open that xml file.
Here's what I'm seeing in there
<?xml version="1.0"?>
<!--
JACK settings, as persisted by D-Bus object.
You probably don't want to edit this because
it will be overwritten next time jackdbus saves.
-->
<!-- Wed Jan 18 23:51:00 2012 -->
<jack>
<engine>
<option name="driver">alsa</option>
<option name="realtime">true</option>
<option name="verbose">false</option>
<option name="client-timeout">500</option>
</engine>
<drivers>
<driver name="net">
</driver>
<driver name="alsa">
<option name="device">usb_stream:1</option>
<option name="rate">44100</option>
<option name="period">1024</option>
<option name="nperiods">19</option>
<option name="hwmon">false</option>
<option name="hwmeter">false</option>
<option name="duplex">true</option>
<option name="softmode">false</option>
<option name="monitor">false</option>
<option name="dither">n</option>
<option name="shorts">false</option>
</driver>
<driver name="alsa_midi">
</driver>
<driver name="oss">
</driver>
<driver name="firewire">
</driver>
<driver name="dummy">
</driver>
</drivers>
</jack>
as for cat /proc/asound/modules ~/.asoundrc, I get this:
0 snd_hda_intel
1 snd_usb_us122l
# The usb_stream plugin configuration
pcm.!usb_stream {
@args [ CARD ]
@args.CARD {
type string
default "1"
}
type usb_stream
card $CARD
}
ctl.!usb_stream {
@args [ CARD ]
@args.CARD {
type string
default "1"
}
type hw
card $CARD
}
I've edited the .asoundrc before, and I'm pretty sure it's correct., but maybe my problem is somewhere in that conf-jack1.xml file...
Thanks for the help!
Thanks for the suggestions, I probably should have thought to open that xml file.
Here's what I'm seeing in there
<?xml version="1.0"?>
<!--
JACK settings, as persisted by D-Bus object.
You probably don't want to edit this because
it will be overwritten next time jackdbus saves.
-->
<!-- Wed Jan 18 23:51:00 2012 -->
<jack>
<engine>
<option name="driver">alsa</option>
<option name="realtime">true</option>
<option name="verbose">false</option>
<option name="client-timeout">500</option>
</engine>
<drivers>
<driver name="net">
</driver>
<driver name="alsa">
<option name="device">usb_stream:1</option>
<option name="rate">44100</option>
<option name="period">1024</option>
<option name="nperiods">19</option>
<option name="hwmon">false</option>
<option name="hwmeter">false</option>
<option name="duplex">true</option>
<option name="softmode">false</option>
<option name="monitor">false</option>
<option name="dither">n</option>
<option name="shorts">false</option>
</driver>
<driver name="alsa_midi">
</driver>
<driver name="oss">
</driver>
<driver name="firewire">
</driver>
<driver name="dummy">
</driver>
</drivers>
</jack>
as for cat /proc/asound/modules ~/.asoundrc, I get this:
0 snd_hda_intel
1 snd_usb_us122l
# The usb_stream plugin configuration
pcm.!usb_stream {
@args [ CARD ]
@args.CARD {
type string
default "1"
}
type usb_stream
card $CARD
}
ctl.!usb_stream {
@args [ CARD ]
@args.CARD {
type string
default "1"
}
type hw
card $CARD
}
I've edited the .asoundrc before, and I'm pretty sure it's correct., but maybe my problem is somewhere in that conf-jack1.xml file...
Thanks for the help!
Re: Tascam US-144
Hi,
periods/buffer=19 seems like a very rare value to me. It normally should be 2 or 3.
Cheers, Pablo
periods/buffer=19 seems like a very rare value to me. It normally should be 2 or 3.
Cheers, Pablo
-
KevinGormley
- Established Member
- Posts: 5
- Joined: Thu Jan 19, 2012 2:20 am
Re: Tascam US-144
Hi Pablo,
Sorry, I didn't mention the periods issue in my last post. I recall changing it before when I noticed that all of the screenshots of the qjackctl settings menu online had much smaller values than I had. Unfortunately, it did not appear to have any effect. I'll try again tonight and monitor the output more carefully to see if I can find any hints to the problem.
Thanks again!
Sorry, I didn't mention the periods issue in my last post. I recall changing it before when I noticed that all of the screenshots of the qjackctl settings menu online had much smaller values than I had. Unfortunately, it did not appear to have any effect. I'll try again tonight and monitor the output more carefully to see if I can find any hints to the problem.
Thanks again!
-
KevinGormley
- Established Member
- Posts: 5
- Joined: Thu Jan 19, 2012 2:20 am
Re: Tascam US-144
Argh! Still no luck.
Worse still, now I start getting those error messages when I start Jack without setting up the soundcard (previously I was able to use it where it would use my computers internal Mic. Now I get those same errors, except it doesn't crash at the end; it just appears to continue running, and if I start a drum sequence in Hydrogen, it starts playing it.
Really think I'm stuck here... anyone who has any ideas about this, please help! Thanks everyone.
Worse still, now I start getting those error messages when I start Jack without setting up the soundcard (previously I was able to use it where it would use my computers internal Mic. Now I get those same errors, except it doesn't crash at the end; it just appears to continue running, and if I start a drum sequence in Hydrogen, it starts playing it.
Really think I'm stuck here... anyone who has any ideas about this, please help! Thanks everyone.
-
KevinGormley
- Established Member
- Posts: 5
- Joined: Thu Jan 19, 2012 2:20 am
Re: Tascam US-144
Scratch that.
Got it working. Not sure what I did that made it work, but for anyone else trying this, over the last hour I changed the name of the preset, and messed with a few of the settings. Also, I installed TuxGuitar, Timidity, and tuxguitar jsa package (in order to get sound out of Tuxguitar).
I have a feeling that this installed some module for Midi that was previously throwing up errors. Might be worth a shot.
Not gonna question miracles here - but thanks for your help guys! Delighted to have this working. Don't think I'll ever go back to Windows now!
Got it working. Not sure what I did that made it work, but for anyone else trying this, over the last hour I changed the name of the preset, and messed with a few of the settings. Also, I installed TuxGuitar, Timidity, and tuxguitar jsa package (in order to get sound out of Tuxguitar).
I have a feeling that this installed some module for Midi that was previously throwing up errors. Might be worth a shot.
Not gonna question miracles here - but thanks for your help guys! Delighted to have this working. Don't think I'll ever go back to Windows now!
-
eikakot
- Established Member
- Posts: 103
- Joined: Fri Jan 29, 2010 2:24 pm
- Location: Vilnius, Lithuania
- Has thanked: 7 times
- Been thanked: 3 times
- Contact:
Re: [SOLVED] Tascam US-144 & Ubuntu 11.10
thats great to see someone got it working. something like 4 years ago i was trying to get it working and had to sell it after all.. Cool usb interface for its price by the way
-
timbulimbu
- Posts: 1
- Joined: Sat Mar 03, 2012 1:01 am
Re: [SOLVED] Tascam US-144 & Ubuntu 11.10
I also want to confirm that I got TASCAM US-144 working on Ubuntu oneric. I have not tested it much yet, but both playback and recording are working fine in Audacity.
I followed the same tutorials as the OP and got stuck almost at the same place. My working qjackctl settings:
Realtime: check
Priority: default
Frames/period: 256
Periods/Buffers: 2
interface: usb_stream:1
Input channels: 2 # changed from (default)
Other values are left default.
Another nuance is that first I configured the jack only for playback:
Audio: Playback only
instead of
Audio: Duplex
Then, the playback magically started to work. After stopping jackd, I changed it back to Duplex and also got recording working. Not sure, why did this matter. But I'm there now. It remains to be seen, if there are any practical problems like too many xruns, but I give it a try tomorrow and try to record/mix some song.
Hope this helps somebody and encourages those US-144 users, who have not got it working yet on Ubuntu to give it another try.
I followed the same tutorials as the OP and got stuck almost at the same place. My working qjackctl settings:
Realtime: check
Priority: default
Frames/period: 256
Periods/Buffers: 2
interface: usb_stream:1
Input channels: 2 # changed from (default)
Other values are left default.
Another nuance is that first I configured the jack only for playback:
Audio: Playback only
instead of
Audio: Duplex
Then, the playback magically started to work. After stopping jackd, I changed it back to Duplex and also got recording working. Not sure, why did this matter. But I'm there now. It remains to be seen, if there are any practical problems like too many xruns, but I give it a try tomorrow and try to record/mix some song.
Hope this helps somebody and encourages those US-144 users, who have not got it working yet on Ubuntu to give it another try.
Re: [SOLVED] Tascam US-144 & Ubuntu 11.10
@ timbulimbu: thank you very much!
This did the trick for me too, using a Tascam US-122L. Different from all other sources I found were two things:
- set Input channels from default to 2
- first configure for playback only, stop jack, switch to duplex, start jack et voila.
This did the trick for me too, using a Tascam US-122L. Different from all other sources I found were two things:
- set Input channels from default to 2
- first configure for playback only, stop jack, switch to duplex, start jack et voila.