| 28 Sep 2022 |
 magnetophon | ctemThat's great to hear, thank you! Of course I was mainly scratching my own itch! :) | 14:28:14 |
 sjfloat | I have had some interaction with the wiki maintainers about what we're trying to do here. They were very open to it and helpful. | 14:28:23 |
| sjfloat | And then I failed to follow through 🙄 | 14:29:20 |
 ctem | Haha, it happens to us all. As for minijackson's idea of an audio production nixpkgs workgroup, I wonder how that might shape up. | 14:30:28 |
| magnetophon | > And then I failed to follow through 🙄
No worries, step by step! | 14:30:34 |
| 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 |
