[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Jack: was Slight New Sound Problem



On 18/09/14 at 11:09am, Steve Litt wrote:
> On Thu, 18 Sep 2014 09:40:56 -0500
> "T.J. Duchene" <t.j.duchene@gmail.com> wrote:
> 
> > Good morning, Martin!
> > 
> > Before I can make suggestions, I need to know if you are using a
> > daemon such as Jack or PulseAudio or if you are using ALSA directly.
> 
> T.J (and anyone else),
> 
> I really want to use Jack, but every time I've tried, I failed
> miserably and gotten no sound. Is there some special mindset you need
> when installing/configuring Jack, and if so, where can I find out about
> it?

Well, it's quite straightforward to use jackd and no particular trick is needed.
Install jackd2 and its gui qjackctl and alsa-utils. Get rid or stop PulseAudio
and start qjackctl, see what happens and report (qjackctl has a nice message log
window)

Keep in mind that often no sound means that alsamixer volumes are muted or at 0 level which
seems to be the default.


> My understanding of Jack (and please correct me if I'm wrong), is that
> it's like being able to patchcord together all sorts of software
> sound processor boxes, in whatever configuration I want. I'd *love* to
> be able to do that.

Yes, jack compliant applications can be routed from/to every where. Non
compliant apps can also be routed with little tweaking (eg. flashplayer, skype)




-- 
« Nunc est bibendum, nunc pede libero pulsanda tellus »


Reply to: