| 28 Sep 2022 |
 ctem |
I'd like there to be a general audio landing page to help people decide how to choose a configuration that best supports their particular needs.
Were you thinking in terms of pro audio/music or more broadly?
| 14:32:41 |
 sjfloat | That would be one of the branch points. | 14:33:56 |
| sjfloat | If you're not doing pro audio, you'll likely take a different approach than the majority. | 14:34:34 |
| sjfloat | So I think the docs should reflect that and help with it. | 14:34:56 |
 magnetophon | For the non-pro usecase, I think pipewire is the way to go, and even for some pro usecases it's good. What do you two think? | 14:36:12 |
| sjfloat | * If you're doing pro audio, you'll likely take a different approach than the majority. | 14:36:53 |
| ctem | I definitely think pipewire is the future. So far, it seems to cover many jack-based use cases seamlessly as well. I know people who already have stable jack-based setups are reluctant to try pipewire, but for someone like me in a transitional period, I'm really happy to work w/it as it continues to develop. | 14:38:31 |
| sjfloat | Right. For most people, pipewire should satisfy out-of-the-box. | 14:38:39 |
| ctem | Have you hit any major snags w/pipewire in pro audio scenarios? | 14:40:48 |
| sjfloat | My main issue is it really crushes my browser, performance-wise. | 14:42:24 |
| sjfloat | So, I'm consider going a completely different route. In particular, I think I'll try to get as much of the audio stuff out of the system config as possible. | 14:43:52 |
| sjfloat | That's how I worked for years on Debian | 14:44:05 |
| sjfloat | So, for the time being, I may return to PA and running jack as a user. | 14:45:16 |
| magnetophon | I've been running two configs in parallel, one optimized for usability and battery life, and one for realtime. The first uses pipewire and the second jack and musnix. I haven't needed to boot into the audio config for a long time. | 14:47:59 |
| magnetophon | I haven't compared the performance/ battery life of pipewire to PA though. | 14:48:31 |
| magnetophon | sjfloat Which browser are you using? | 14:48:47 |
| sjfloat | Chrome | 14:49:14 |
| magnetophon | > So, I'm consider going a completely different route. In particular, I think I'll try to get as much of the audio stuff out of the system config as possible.
Why is that? For me, the main reason to start using NixOS, is so that I could have all my config (except dotfiles, so far) in a file. | 14:50:50 |
| sjfloat | Partially because I don't consider jack a system-level thing. I tend to manipulate things as part of what I'm trying to do. | 14:52:13 |
| sjfloat | I don't want my jack config that static | 14:52:32 |
| sjfloat | I agree that pipewire probably is the future. It just doesn't solve any problem that I have. | 14:53:42 |
| ctem |
I haven't needed to boot into the audio config for a long time.
Do you mean you've been able to use the first config sufficiently for pro audio?
I think I'll try to get as much of the audio stuff out of the system config as possible.
I took that as meaning you wanted it in your user config, e.g., with home-manager, but it seems you need it to be mutable?
| 14:53:44 |
| sjfloat | Yeah, I don't even want it in home-manager | 14:54:24 |
| magnetophon | ctem yes | 14:54:29 |
| sjfloat | I might have a session definition that changes my jack config | 14:54:43 |
| magnetophon | @ctem I have mostly been making music though. If I was recording I would definitly boot into thr RT kernel! | 14:55:24 |
| sjfloat | Now it would be awesome if I can get the entirety of my project in a nix-shell or something. | 14:55:27 |
| sjfloat | Then the project would be more hermetic and not subject to how a particular system was configured at a particular time. | 14:56:37 |
| sjfloat | Stated another way, I'd like my music projects to be decoupled from the system. | 14:57:44 |
| ctem | magnetophon: Noted. Thanks!
Now it would be awesome if I can get the entirety of my project in a nix-shell or something.
I’m also considering treating audio productions like programming projects, e.g., with a Nix flake specifying any hosts, plugins, etc. It would be interesting to solve music collaboration the Nix way.
| 14:58:31 |
