2 Aug
2018
2 Aug
'18
4:59 p.m.
Hi all,
After migrating to a freshly installed system, it seems jackd has decided not to honor my
settings in $HOME/.jackdrc anymore.
I have a (minimal, no deskop) install of ubuntu 17.10 and jackd1
when I startt my jack client it prints:
creating alsa driver ...
hw:MADIFXtest|hw:MADIFXtest|1024|2|48000|0|0|nomon|swmeter|-|32bit
but the contents of of ,jackdrc is:
/usr/bin/jackd -p512 -dalsa -r48000 -p64 -n2 -D -Chw:MADIFXtest -Phw:MADIFXtest
So I’m getting a period size of 1024 rather that 64.
copying .jackdrc to /etc/jackdrc also didn’t help.
Any idea why jack is refusing my settings?
This was working fine on my other system which should be more or less identical, but
obviously i'm missing something rather crucial here…
thanks!
fokke
2 Aug
2 Aug
6 p.m.
On Thu, Aug 2, 2018 at 8:59 AM, Fokke de Jong <fokkedejong(a)gmail.com> wrote:
Hi all,
After migrating to a freshly installed system, it seems jackd has decided
not to honor my settings in $HOME/.jackdrc anymore.
jackd itself never uses jackdrc.
it is used by either:
1) a control client (e.g. qjackctl)
2) a normal client that connects to JACK with no server running and the
NoStartServer option not set
i.e. it saves the "last used settings" so that they can be re-used in
contexts where there are no settings given.
6:14 p.m.
Hi Paul,
Thanks for your input. That clears one thing up for me.
Since I’m not using qjackctl, only one client that starts jackd, it makes sense that it;’s
using default values.
On my previous system it did always seem to use the ‘correct’ settings. So do you have any
idea what other place jackd might me getting its settings from? The client is the same..
cheers,
Fokke
On Aug 2, 2018, at 16:00 , Paul Davis
<paul(a)linuxaudiosystems.com> wrote:
On Thu, Aug 2, 2018 at 8:59 AM, Fokke de Jong <fokkedejong(a)gmail.com
<mailto:fokkedejong@gmail.com>> wrote:
Hi all,
After migrating to a freshly installed system, it seems jackd has decided not to honor my
settings in $HOME/.jackdrc anymore.
jackd itself never uses jackdrc.
it is used by either:
1) a control client (e.g. qjackctl)
2) a normal client that connects to JACK with no server running and the NoStartServer
option not set
i.e. it saves the "last used settings" so that they can be re-used in contexts
where there are no settings given.
6:25 p.m.
On Thu, Aug 2, 2018 at 10:13 AM, Fokke de Jong <fokkedejong(a)gmail.com>
wrote:
Hi Paul,
Thanks for your input. That clears one thing up for me.
Since I’m not using qjackctl, only one client that starts jackd, it makes
sense that it;’s using default values.
On my previous system it did always seem to use the ‘correct’ settings. So
do you have any idea what other place jackd might me getting its settings
from? The client is the same..
jackd itself will never save ~/.jackdrc either. That's done only by control
clients like qjackctl.
jackd has its own hardcoded defaults if none are available.
What is the client that starts jackd?
6:42 p.m.
The client is of my own making. And it doesn’t provide any settings to jackd, as I don’t
really see any options in the api to do that.
But it would of course be much better to setup samplerate, period size, etc from the
client.
If could tell me how to set: "/usr/bin/jackd -p512 -dalsa -r48000 -p64 -n2 -D
-Chw:MADIFXtest -Phw:MADIFXtest” this programmatically from the client that would also be
of great help!
It still remains a mystery to me how to could magically work on my other system..
cheers,
Fokke
On Aug 2, 2018, at 16:25 , Paul Davis
<paul(a)linuxaudiosystems.com <mailto:paul@linuxaudiosystems.com>> wrote:
On Thu, Aug 2, 2018 at 10:13 AM, Fokke de Jong <fokkedejong(a)gmail.com
<mailto:fokkedejong@gmail.com>> wrote:
Hi Paul,
Thanks for your input. That clears one thing up for me.
Since I’m not using qjackctl, only one client that starts jackd, it makes sense that
it;’s using default values.
On my previous system it did always seem to use the ‘correct’ settings. So do you have
any idea what other place jackd might me getting its settings from? The client is the
same..
jackd itself will never save ~/.jackdrc either. That's done only by control clients
like qjackctl.
jackd has its own hardcoded defaults if none are available.
What is the client that starts jackd?
8:40 p.m.
Am 02.08.2018 um 14:59 schrieb Fokke de Jong:
Hi all,
After migrating to a freshly installed system, it seems jackd has decided not to honor my
settings in $HOME/.jackdrc anymore.
I have a (minimal, no deskop) install of ubuntu 17.10 and jackd1
when I startt my jack client it prints:
creating alsa driver ...
hw:MADIFXtest|hw:MADIFXtest|1024|2|48000|0|0|nomon|swmeter|-|32bit
but the contents of of ,jackdrc is:
/usr/bin/jackd -p512 -dalsa -r48000 -p64 -n2 -D -Chw:MADIFXtest -Phw:MADIFXtest
So I’m getting a period size of 1024 rather that 64.
copying .jackdrc to /etc/jackdrc also didn’t help.
Any idea why jack is refusing my settings?
This was working fine on my other system which should be more or less identical, but
obviously i'm missing something rather crucial here…
thanks!
fokke
Any chance that you run your system as root?
8:47 p.m.
normally yes, I run it as root, but also when running it as a normal user WITH the
.jackdrc file in my home dir it’s not used.
On Aug 2, 2018, at 18:40 , Hermann Meyer
<brummer-(a)web.de> wrote:
Am 02.08.2018 um 14:59 schrieb Fokke de Jong:
Hi all,
After migrating to a freshly installed system, it seems jackd has decided not to honor my
settings in $HOME/.jackdrc anymore.
I have a (minimal, no deskop) install of ubuntu 17.10 and jackd1
when I startt my jack client it prints:
creating alsa driver ...
hw:MADIFXtest|hw:MADIFXtest|1024|2|48000|0|0|nomon|swmeter|-|32bit
but the contents of of ,jackdrc is:
/usr/bin/jackd -p512 -dalsa -r48000 -p64 -n2 -D -Chw:MADIFXtest -Phw:MADIFXtest
So I’m getting a period size of 1024 rather that 64.
copying .jackdrc to /etc/jackdrc also didn’t help.
Any idea why jack is refusing my settings?
This was working fine on my other system which should be more or less identical, but
obviously i'm missing something rather crucial here…
thanks!
fokke
Any chance that you run your system as root?
2096
days inactive
2096
days old
linux-audio-dev@lists.linuxaudio.org
6 comments
3 participants
participants (3)
-
Fokke de Jong -
Hermann Meyer -
Paul Davis