8 Jul
2017
8 Jul
'17
12:59 p.m.
On Sat, 8 Jul 2017 20:56:02 +0300, alex wrote:
On 07/08/2017 08:54 PM, Ralf Mardorf wrote:
It doesn't harm.
But instead of continuing guessing, it's much more important to
redirect jackd's stdout und stderr to a log file, as explained by
precious replies.
Regards,
Ralf
--
Vote for apulse!
echo $(w3m https://aur.archlinux.org/packages/apulse |grep 'Votes: ')
Votes: 84 Updated: Sat Jul 8 19:59:34 CEST 2017
On Sat, 8 Jul 2017 20:37:51 +0300, alex wrote:
So do you recommend to add a delay after
launching jack and before
launching pd? On 07/08/2017 08:30 PM, Joakim Hernberg wrote:
If you start jackd at boot, you start it for the very
first time. If
you start jackd after that from command line, it's already in the
cache and might launch faster. I don't think it's the culprit, but it
explains that running software for the first time does take longer,
than starting it for the second time. Maybe you need a sleep to make sure that jack is
really running
before you start pd?
But the script runs fine when launched manually. It's
just that jack
won't run on boot.