On Fri, 15 Feb 2013 09:30:56 +0000 (GMT)
Jim Lesurf wrote:

In article , Jim Price
wrote:
On 14/02/13 22:56, Davey wrote:

Indeed. I have no idea what Jack is, but it is there, in /usr/lib64.
But what happens otherwise if I remove it?


Jack is handy for music production, as you can often use some of the
features of your sound card which might not be supported by ALSA alone.

I continue to wonder about that. I haven't ever use 'Jack'. Never needed
it, despite recording things as well as playing and processing them. But my
impression is that it has been developed as a 'user friendly' sic way to
do things which its creators *think* people "can't do" with ALSA.

Jack allows you to look at audio links in a totally different way. It uses ALSA
to make the physical connections, but (using something like Qjackctl) presents
all the information in a sane manner. The problem arises when using something
like Audacity, which although very good in it own right, is a bodge when
connecting up.

I simply could not do much of the composition work I do without jack. I can, and
do kick out pulseaudio as a waste of resources, and *never* use Audacity for
recording. Timemachine is just so much simpler, reliable and above all routable.


--
W J G