Sender | Message | Time |
---|---|---|
26 Jan 2024 | ||
In reply to @Minijackson:matrix.orgSo I recognize a lot of those from AV Linux: MX Edition. A lot of them shipped with the distro so I'm not sure exactly which packs or whatever installed some of them. | 20:15:19 | |
zyn, Helm, oxefm | 20:15:26 | |
csound :P | 20:15:41 | |
as for getting a list I don't have any better suggestion than https://search.nixos.org/packages?channel=23.11&from=0&size=50&sort=relevance&type=packages&query=synthesizer | 20:16:33 | |
Oh yeah Helm is rad, I've used that one quite a bit | 20:16:37 | |
aeolus | 20:17:07 | |
Thanks for the recs, folks! Plenty of new stuff to try out! | 20:22:50 | |
In reply to @rampoina:matrix.orgI hadn't heard of this before. So it's like an old school music language and framework? Sounds like it could be fun to livecode in! | 20:23:33 | |
Hey neat, orca-c (esoteric livecoding language) has been packaged! | 20:24:47 | |
So is sonic-pi. I've had a lot of fun livecoding in both of these languages. I find sonic-pi a lot more practical but orca is really fun, it's almost like a video game. | 20:25:28 | |
Any recommendations for mastering plugins? I'm not very experienced with these in general. | 20:28:25 | |
In reply to @fractivore:cyberia.clubyes | 21:21:12 | |
there's also supercollider | 21:21:16 | |
for a more modern language | 21:21:22 | |
but csound is more batteries included | 21:21:28 | |
27 Jan 2024 | ||
01:58:55 | ||
In reply to @rampoina:matrix.orgahhh right, supercollider is used in sonic-pi's backend somehow | 08:20:25 | |
I just realized - nix shells might be a good way of doing temporary audio configuration changes, like a sample rate change! | 08:21:22 | |
In reply to @Minijackson:matrix.orgHmm, how did you make Ardour find the calf plugins? It was able to find a lot of these plugins in the default search paths after I installed them via my configuration.nix, but not the calf plugins, even though calfjackhost is installed. | 08:47:04 | |
In reply to @fractivore:cyberia.clubyou have to have this kind of config: https://github.com/musnix/musnix/blob/master/modules/base.nix#L77-L82 | 10:03:23 | |
make sure your $LV2_PATH var is correct and points to where your plugins are installed | 10:03:46 | |
and you should check that Ardour respects the $LV2_PATH value | 10:04:11 | |
(note: IIIRC the $VST3_PATH variable is not standard) | 10:04:39 | |
* (note: IIRC the $VST3_PATH variable is not standard) | 10:04:43 | |
In reply to @Minijackson:matrix.orgif it doesn't, you should be able to override it in the settings | 10:05:35 | |
You can also check "Preferences > Plugins > Scan for plugins" to see if there's any plugins that Ardour failed to load | 10:06:49 | |
In reply to @Minijackson:matrix.orgOh right, I forgot about that part! Thanks again! | 14:45:25 | |
Is it a bad idea to make my musical collaborators use NixOS for working on projects together? 🤔 I've had issues in the past when me and a collaborator try to work on the same ardour project file - the problem is we don't have all the same plugins, which need to be manually installed to the same version. | 16:36:33 | |
NIX IS basically completely solves this problem... But it's not something I would generally suggest to anyone that's not like already a super-technical open source nerd | 16:37:12 | |
* NixOS basically completely solves this problem... But it's not something I would generally suggest to anyone that's not like already a super-technical open source nerd. But I feel like just using my config isn't too much to ask. But they'll probably have to use it through WSL.... | 16:37:55 |