| 20 Jul 2022 |
 sjfloat | Is everything you like to use working for you right now? | 20:14:12 |
 Chris McDonough | i used harrison mixbus for many years (it's a fork of ardour, and closed source,that doesn't work clearly, but it's not difficult to replace) | 20:15:27 |
| Chris McDonough | and other stuff i just haven't tried yet tbh | 20:15:42 |
| Chris McDonough | i punted to my mac lol | 20:15:49 |
| sjfloat | I'm kind of minimal in terms of UI. I used ecasound for a long time before moving to Ardour. | 20:16:44 |
| Chris McDonough | any tool is probably too much tool for me honestly, i just mess around :) | 20:17:25 |
| Chris McDonough | the thing i tend to overuse most is a roland rc-505 looper, which is super convenient for recording stuff without any daw in sight | 20:18:15 |
| sjfloat | NIce | 20:18:35 |
| Chris McDonough | that doesnt work out of the box on linux but a kernel patch fixes it | 20:18:40 |
| sjfloat | Like, the editor for it? | 20:19:02 |
| Chris McDonough | as an alsa device... https://www.youtube.com/watch?v=eX_s2lLHRgM | 20:19:44 |
| Chris McDonough | its both pcm input and a midi device | 20:20:32 |
| Chris McDonough | i usually just set it up to be the master midi clock and use the knobs to adjust tempo, thats all the midi is good for to me | 20:21:06 |
| sjfloat | Oh, OK. | 20:21:31 |
| 21 Jul 2022 |
| sjfloat | I had a thought about testing some of these audio tools and configurations. Seems like we could use a combination of `nix-shell` and `wireplumber` to pull dependencies and arrange things so the utility under test could be run. | 11:41:10 |
| sjfloat | If pipewire is the future, then so is wireplumber, I guess. So we need to get our heads around that. | 11:43:03 |
| sjfloat | At the very least, we should be able to use this to share examples. But ideally we could create a test suite this way. | 11:44:26 |
| sjfloat | Also, we could create working audio environments just as we do for software development. | 11:47:42 |
| sjfloat | If anyone here is very acquainted with wireplumber, I may have some questions | 11:50:24 |
|  @denna:matrix.org joined the room. | 12:23:06 |
| @denna:matrix.org | In reply to @sjfloat:matrix.org
If anyone here is very acquainted with wireplumber, I may have some questions For wireplumber questions the pipewire channel his helpful: https://matrix.to/#/#pipewire:matrix.org | 12:25:10 |
| sjfloat | Awesome. Thanks. | 12:43:46 |
| sjfloat | So, having spoken with folks at that channel, they don't seem to think that it's something the user would use much. Nor does there seem to be any docs for that audience. | 17:15:55 |
| 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 |
