| 21 Jul 2022 |
 sjfloat | However, I found that aj-snapshot still captures and restores alsa and jack connection graphs. | 17:16:20 |
| sjfloat | It stores the graph in an XML file, so I'm sure you could write and tweak them yourself. | 17:17:05 |
| sjfloat | And keep them under VC | 17:17:50 |
| sjfloat | I'm still considering going back to pulsewire though. My usual workflow for a long time has been to simply suspend it when things get serious. | 17:18:53 |
| sjfloat | And pipewire really seems to crush chrome on my box -- really painful. | 17:19:18 |
| sjfloat | These would be a very different thing than what people seem to be doing on NixOS though. On Debian, I started jack manually when I needed and didn't run it as a service. | 17:20:07 |
| sjfloat | * This would be a very different thing than what people seem to be doing on NixOS though. On Debian, I started jack manually when I needed and didn't run it as a service. | 17:20:48 |
| sjfloat | And I had different jack configs for different needs. Having it hardcoded in my system config has not been fun for me. | 17:22:02 |
| sjfloat | Has anyone had any luck with Cadence? | 20:55:25 |
| sjfloat | It installs, but it seems pretty much completely non-functional. | 20:55:44 |
| sjfloat | I'm guess in just totally incompatible with pipewire. | 20:57:44 |
| 22 Jul 2022 |
|  ckie (they/them) joined the room. | 10:45:35 |
| sjfloat | I'm seriously considering going back to pulse audio. Chrome is barely usable for me since switching to pipewire. | 16:37:38 |
| sjfloat | And there are jack tools that will never work with pipewire. | 16:38:13 |
| sjfloat | When I get a chance, I'd like to do more A/B performance testing. | 16:39:00 |
| 23 Jul 2022 |
| sjfloat | Several of the audio pages at https://nixos.wiki/wiki/Category:Audio are indicated as out of date. Would anyone be interested in helping me try amend that? | 14:11:58 |
| sjfloat | Actually, it would be good if there was a page for general audio. A lot of the confusion is around deciding what general config to chose. | 15:54:27 |
 Chris McDonough | TIL that sound.enable = true causes alsamixer persistence | 16:41:11 |
| Chris McDonough | did not know that | 16:41:14 |
| Chris McDonough | I have a hard time with wikis | 16:41:40 |
| sjfloat | So, you don't get that persistence otherwise? | 16:42:08 |
| Chris McDonough | apparently not? i guess it changes /etc/alsa.conf? | 16:42:30 |
| sjfloat | Ah | 16:42:38 |
| sjfloat | Configuring all of this in the system config often poses real problems for me. | 16:44:09 |
| sjfloat | Of course, in the case, alsa has local user config that overrides that, so maybe that's not an issue. | 16:44:48 |
| sjfloat | But I normally do a lot of on the fly changes. It's not really a system configuration that should be immutable. | 16:46:55 |
| sjfloat | I'm used to having different jack configurations for different projects or tasks, for example. | 16:47:47 |
| sjfloat | I use different external devices with different specs too, so the config can't be fixed. | 16:48:54 |
| Chris McDonough | i guess the nixy way of handling it (not saying it's.. uh... convenient) would be to write a derivation for each config | 17:23:39 |
| Chris McDonough | or figure out if there's some way to configure what you need to configure somewhere under $HOME | 17:24:25 |
