robert/alsa-scarlett-gui
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Improve "settings keep resetting" FAQ entry

Browse Source
This commit is contained in:
Geoffrey D. Bennett
2025-03-15 10:16:13 +10:30
parent 6677e5c87d
commit a34df84dfa
1 changed files with 28 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
FAQ.md
View File

@@ -94,23 +94,41 @@ to the user manual of your interface for more information.
The settings in the ALSA Scarlett Control Panel are automatically
saved in the interface itself (all series except 1st Gen), so they
“should” persist across reboots and even across different computers.
should persist across reboots, power cycles, USB disconnect/reconnect,
and even across different computers. This includes all routing,
mixing, and other control panel settings.
If you find that the opposite is happening — that every time you plug
your interface in, the settings get reverted, try disabling the
`alsa-state` and `alsa-restore` systemd services:
If you find that your settings are reverting whenever you plug your
interface in or power it back on, the most likely cause is the
`alsa-state` and `alsa-restore` systemd services. These services save
the state of ALSA controls on system shutdown to
`/var/lib/alsa/asound.state` and then restore it each time the device
is plugged in, potentially overwriting your interface’s stored
settings.
It can be rather annoying, wondering why your device is unusable or
needs to be reconfigured every time you plug it in or turn it on.
To fix this issue, disable these services:
```sh
sudo systemctl mask alsa-state
sudo systemctl mask alsa-restore
```
These services save the state of ALSA controls on system shutdown to
`/var/lib/alsa/asound.state` and then restore it each time the device
is plugged in. It can be rather annoying, wondering why your device is
unusable every time you plug it in, only to find that it’s because you
once shut down your computer with the Clock Source set to “ADAT” or
some such thing.
You can verify if this is the cause of your issues by:
1. Change some setting that is indicated on the device (the “Inst”
setting is a good).
2. Disconnect USB and notice the state of the setting on the device
has not changed.
3. Power cycle the device and notice the state of the setting on the
device has not changed.
4. Reconnect USB and notice the state of the setting on the device has
changed.
If the setting on the device changes at step 4, then the `alsa-state`
and `alsa-restore` services are the likely cause of your issues.
## Help?!