Forgive me my probably silly question, but I have just started to enter the Ardour/Linux-World and could not find help elswhere. I use Ubuntu-Studio and a Tascam US-122. The latter is correctly installed because in Audacity I can record properly. But as far I can see Audacity is not using JACK, but refers to ALSA directly.
When I try JACK+Ardour there is no input. JACK is running and Transport activated. The Input-source of my tracks is set to Capture_1 and Capture_2. Does that sound correct? And what are the most obvious things I could have missed?
The most obvious thing I can think of is this: Have you activated the red button of the track you want to record to, in addition to the big red button in the transport?
In addition, you can check that you really have the “captures” connected to the track or tracks you want to record to by means of the connect button in qjackctl.
By the way, this one can be useful: http://www.out-of-order.ca/tutorials/ardour/
I hope it helps
Pablo
Thanks for your answer and sorry, I had been offline for a while.
Of course I used the recording-button correctly. When I try recording, a wave-graph is created but with no signal on it. The Captures seem to be connected properly to the ardour-tracks in JACK. In your two links I did not (yet) find anything that solved my problem.
Here is the messages I get from Jack, while I fumbled a little with the settings.
I have also considered connecting to the IRC-channel for support, but did not find a way how to register with irc.freenode.net. I have an irc-client (pidgin) installed but it asks for an existing account. How could I create one?
Have you set up JACK as described in these instructions? First, you should check to make sure your US-122 is connecting to JACK correctly. With a microphone connected to your US-122, start JACK and open the Connections window, then connect capture_1 to playback_1. Can you hear the microphone?
Just enter mibbit.com from the link provided in the Support tab and change the nickname. I think you don’t need anymore.
You have lots of xruns! yes, check JACK instructions.
Pablo
Ah! Thanks - this was the link I had long searched for. After I selected the right hardware-device and adjusted the frames-rate I dont get xruns anymore.
Yet I have swapped one problem for three more:
In the JACK-settings I can only select the “US-x2y” (hw:1) and one of its two inputs (hw:1,0). If I select the former I dont get anything to connect in the JACK-connections window (no “system”, no “ardour”). So I have to choose the first channel only. But this might be a driver-problem I have to solve separately.
If I connect capture_1 to playback_1 I hear nothing. I tried to check the alsa-mixer but “alsamixer -c 1” gives me “no mixer elems found”.
When I try recording in Ardour, it always stops after 5 seconds and tells me my harddisk was too slow. I use a recently bought Thinkpad R61 so I dont think this is the case. I also think it did not do this last time I tried it.
edit: It also tried H/W-Monitoring, as someone on the linked page suggests, and connected
also_pcm-Monitor_1 to playback_1. If I do this in addition to connecting to capture_1 then i get a humming noise, that increases with every time I speak into the microphone. This was the closest to recording I have got yet. Any ideas?
Hi Artur!
If you use the Search function on top of the page and enter US-122 you will see several posts on how to get it working with alsa and jack. Then you may post in one of these threads if you have more specific questions.
I really cannot help you as I use a PCI card and don’t know about USB devices.
The “hard disk too slow” issue has also been discussed here.
I’m sure you’ll see things clearly and have your system up and running soon.
Regards
Pablo
Thank you very much, Pablo! I have rarely been pointed to the search function as polite.
Yet it seems I am not even smart enough to get this one running. For “us-122” I get only 15 hits, most of which are hardware recommendations. None seems to get me much further - especially since my driver already works (even though one input only), since recording and playback works fine with Audacity. My main aim is to get running Ardour. The second input can wait.
For “hard disk too slow” I get exactly one hit - this thread. And a wider search did not help either.
Anyway. I will search on and keep my eyes open for any information.
As far as I can see everything you name is in place. Alsa-firmware is not a package, right? because it does not show up in Synaptic. But I have copied the extra firmware-files into the right place, when I set up my installation, if this is what it means. And as I say: it works with Audacity (without Jack).
I may have put it misleadingly above: The full entry in qjackctl is indeed “hw:1 TASCAM US-X2Y”. But when I select it, I do not get a single input to connect in Jack. I only get some when I pick “hw:1,0 US-X2Y Audio #0”.
Anyway, the most reasonable thing indeed seems to be to update my system against these new repositories first. I just have to wait until I have enough bandwith for that.
The former way of installing the US-122 firmware was to download the ALSA firmware, Unzip it and as root create a “firmware” folder in /usr/share/alsa/ and create a udev rule in /etc/udev/rules.d/ The udev rule came from an ALSA Wiki page about the US-122. Is this how you installed your US-122?
I had some difficulties with my US-122 killing JACK after 120mins using that setup, however not the same ones that you are experiencing.
I installed the Alsa-firmware (It is a package) from ematech, it creates a different udev rule for the US-122, and voila it works great.
The only caveat is that you will need to delete or comment out the original tascam-55 rules in the /etc/udev/rules.d/ folder after you install the ematech Alsa-firmware package.