On Wed, Nov 30, 2016 at 01:43:38PM +0100, Guido Aulisi wrote:
> IMHO Jack is a must for professional audio, because of its low latency
> and connection facility.
> You should run it with realtime scheduler and high priority, and in
> F24 there was a problem with systemd not configuring correct limits.
> I don't know if this problem has been corrected now.
Probably not. This bug?:
https://bugzilla.redhat.com/show_bug.cgi?id=1364332
> 2016-11-29 21:19 GMT+01:00 Przemek Klosowski <[email protected]>:
> > On 11/29/2016 12:58 PM, J. Bruce Fields wrote:
> >
> > I thought most of those music apps required jack to run--are you running
> > jack or not? If you are, then it's probably just the usual
> > jack/pulseaudio conflicts. Which Fedora seems set up to fix, but for
> > seem reason the fix doesn't work; I filed a bug here:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1390043
> >
> > I actually stopped using jackd because I felt it introduced more 'hidden
> > state' problems, and I was hobbling along with Pulse---I don't think jackd
> > is an absolute requirement. I don't want to mess around with setup every
> > time before running a music app, so maybe the way to go is to just run jackd
> > all the time?
Obviously the above bug would need fixing.
I doubt that's the only thing preventing jackd from running all the
time. I think there may have been some cost in CPU time?
--b.
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
