On 12/10/2011 06:22 PM, Rob Owens wrote:
On Sat, Dec 10, 2011 at 08:02:32AM -0800, Ryan Billing wrote:
On 12/10/2011 05:34 AM, Rob Owens wrote:
I bought a Behringer UCG102 and am trying to get it to work on my son's
computer before Christmas.  He's running Debian Squeeze.  Does anybody
have it working on Squeeze?

My UCA202 works on Debian Lenny, Squeeze and Sid.  I think you will get 
this working if you play around with the selections for input device and 
output device.

Does it matter if pulseaudio is running on the machine?  Or does that
get bypassed as soon as the jack server is running?

-Rob

------------------------------------------------------------------------------
Learn Windows Azure Live!  Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for 
developers. It will provide a great way to learn Windows Azure and what it 
provides. You can attend the event by watching it streamed LIVE online.  
Learn more at http://p.sf.net/sfu/ms-windowsazure
_______________________________________________
Rakarrack-users mailing list
Rakarrack-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rakarrack-users

Pulseaudio is probably your problem. My experience so far with pulseaudio and jack is that they don't play well together. A good test is to disable pulseaudio. I have not tried it in Debian ( I don't know whether you are using the /etc/init.d/... file, or the userspace stuff).

Per Ubuntu ( I have tried this on Linux Mint), you can edit
/etc/pulse/client.conf

uncomment the line:
autospawn=yes
And change it to
autospawn=no

Then you may need to edit daemon.conf and uncomment this line:
allow-exit = yes

After saving your changes to the PA configs, then at the command prompt (as your username)
me@debian ~ $ pulseaudio -k

That should kill it and it won't come back until you manually start it again.  If you want to restore things to normal, you can copy the client.conf file to a backup then copy it back when you are done and start pulseaudio.  You could also make a script to do this and add it in qjackctl's interface so it automatically changes the config and kills pulse, then starts it again when you stop it.

Of course, my suggestion is to
# apt-get remove pulseaudio

Because I don't think it actually adds much value, and that one line is much easier than tweaking config files ;)

Anyway, kill pulseaudio then try starting jackd with the tips I gave you in the last time around and see if things work out better.  Pulseaudio has traditionally been a thorn in the side to JACK users.  In defense of PulseAudio, there is significant work being done to improve the cooperation between the two, but I don't think you will get those versions packaged in Debian stable (I haven't checked the status of this for a long time, so I don't know whether it is in Sid).

I think some people like to use jack as the main audio server that starts at boot time, then use Pulse as a jack client.  I don't know how well that works, but something to let rattle in the back of the head in case you go experimenting some day.

I hope that helps.
Transmogrifox