drew Roberts wrote:
the "save" button is to save current settings and only those as a named
those settings are the ones seen in that particular page
(Setup/Settings), being the ones strictly related to jackd arguments.
the "save" is about creating/updating a named preset. it is _not_ to
save nor commit the program configuration state to disk. still that only
occurs on program exit.
the other setup pages, Options, Display and Misc., all refer to global
user configuration options that refer to qjackctl behavior per se, not
the jack server settings.
> Is it that the save commits to an in memory config change but that change does
exactly. again, if you have several local instances of qjackctl running,
their configurations will most probably clash and step on each other
toes and only the last one that exits will prevail. that applies to
window positioning as well, the position of the last quitting is the one
that will get restored next time qjackctl starts.
configuration is read at qjackctl startup, changed in memory during
runtime and committed to disk on exit. that's one of the biggest and
fundamental reasons for the single application instance restriction.
again, you as human user, are not supposed to touch the configuration
file, so don't you bother where it's located nor named after
> I sometimes switch between my usb sound card and my internal soundcard. I stop
when you switch to a particular preset, that will affect the default
preset name that will get selected next time qjackctl runs (if you don't
call it explicitly through eg. qjackctl --preset=int48 command line)
rncbc aka Rui Nuno Capela
Linux-audio-user mailing list