| 28 Sep 2022 |
 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 |
| sjfloat | Yeah, that's my approach. I use git-annex to store audio files. | 14:59:22 |
| sjfloat | i.e. tracks from recording. | 14:59:44 |
| ctem | Same here. I haven’t published my configs yet but wrote this design document as a start to describe a NixOS/mesh VPN/git-annex way to collaborate. | 15:01:44 |
| magnetophon | Oh, nice! I started using annex (for audio files) at one point, but got a bit overwhelmed by it. Maybe I should look into it again! | 15:02:54 |
| sjfloat | At the time I started using it, git didn't support large files. Native git might be a better choice now -- I don't know for sure. | 15:03:56 |
| ctem | I’d hoped that by the time I got to writing that document that everything would be solved by IPFS, but for now I think git-annex is still best-in-class. | 15:04:01 |
| ctem | It has a borg remote that’s great for use with, for example, an SBC w/a big backup drive attached to it (presumably stuck in the corner of the room of as many collaborators as possible). | 15:06:22 |
| magnetophon | Why annex on top of borg instead of just annex? For the encryption? | 15:07:26 |
| ctem | Yes, for a collaborative setup, encryption is part of it. Compression and dedup are also a big help. | 15:08:38 |
