| 22 Feb 2024 |
 PowerUser64 | Yeah unfortunately the pipewire implementation of JACK does not play nicely with all things | 07:39:20 |
| PowerUser64 | https://github.com/BespokeSynth/BespokeSynth/issues/500 | 07:39:42 |
| PowerUser64 | ^ this is the main problem | 07:39:53 |
| PowerUser64 | Redacted or Malformed Event | 07:40:00 |
| PowerUser64 | all applications built with JUCE have this problem | 07:40:14 |
| PowerUser64 | basically there's only a 5% chance the thing you're trying to open will be able to connect to the sound card | 07:41:36 |
| PowerUser64 | and the more ports the application has, the greater the chance it will fail | 07:42:10 |
 @fractivore:cyberia.club | In reply to @poweruser64:matrix.org
Does anyone here use pipewire and jack2 at the same time? I found out that pipewire can make a jack client and directly connect to jack, but it's not working for some reason. I tried asking this in the pipewire matrix room but no one responded so I figured I'd ask here too just in case there's anyone doing this on NixOS (like I'm trying to). Well I use both, but so far I've just been manually switching between configs, one which uses PipeWire and one which uses jack. | 16:44:26 |
| PowerUser64 | In reply to @fractivore:cyberia.club
Well I use both, but so far I've just been manually switching between configs, one which uses PipeWire and one which uses jack. I used to do that, and I would still do it if I could, but unfortunately I need to run JUCE applications (ones with this annoying bug that require JACK2) as well as use multiple sound cards provided by pipewire 😕 | 21:50:56 |
| PowerUser64 | The pipewire wiki says wireplumber has an alsa.jack-device option that can be set to true to enable a bridge, but it also says it's deprecated. Despite this, the wireplumber source code still mentions the option. The nixos wiki gives an example of how to enable a similar option, which I tried mimicking to enable this other option, but it seems to not be working right or something because wireplumber doesn't create a device when I should have it enabled. | 22:07:22 |
| 24 Feb 2024 |
|  Danne sch (Danne_sch) joined the room. | 03:06:56 |
| Danne sch (Danne_sch) | Hello, I am having problems using the internal speakers on my hp envy x360. I have been trying to get it to work the past few days now but nothing has worked. | 03:09:16 |
| 26 Feb 2024 |
| PowerUser64 | In reply to @danne_sch:matrix.org
Hello, I am having problems using the internal speakers on my hp envy x360. I have been trying to get it to work the past few days now but nothing has worked. is the sound card visible in alsamixer? | 04:30:56 |
| PowerUser64 | In reply to @poweruser64:matrix.org
The pipewire wiki says wireplumber has an alsa.jack-device option that can be set to true to enable a bridge, but it also says it's deprecated. Despite this, the wireplumber source code still mentions the option. The nixos wiki gives an example of how to enable a similar option, which I tried mimicking to enable this other option, but it seems to not be working right or something because wireplumber doesn't create a device when I should have it enabled. Okay, I did some more digging and it seems that pipewire IS loading my configuration files correctly, but it just can't connect to jack for whatever reason. Not sure why yet. | 04:32:11 |
| PowerUser64 | 
Download image.png | 04:32:45 |
| PowerUser64 | ^ systemctl --user restart pipewire && journalctl -f --user-unit pipewire | 04:32:54 |
| Danne sch (Danne_sch) | In reply to @poweruser64:matrix.org
is the sound card visible in alsamixer? I think so | 09:35:07 |
| @fractivore:cyberia.club | So... It's not finding the file that acts as the socket. It tries to read or write from that non-existent socket, resulting in an IO error. | 13:48:23 |
| @fractivore:cyberia.club | Possibly there is some different convention in use by PipeWire vs regular JACK. | 13:49:02 |
| @fractivore:cyberia.club | Can you make the log more verbose at all? Maybe we can get some visibility into the socket's name. | 13:49:52 |
| PowerUser64 | In reply to @danne_sch:matrix.org
I think so Hmm, maybe try changing some settings on it in alsamixer then? It's possible there's a setting preventing it from outputting anything. | 18:05:47 |
| PowerUser64 | In reply to @fractivore:cyberia.club
Can you make the log more verbose at all? Maybe we can get some visibility into the socket's name. Good question. I'm not sure if I can. If there is a way to make it more verbose, I'm not sure what it would be. I have seen this error before when working with Jack applications, and I agree, it is a very nondescript error. | 18:07:50 |
| PowerUser64 | Maybe it's possible to enable more logging in the pipewire unit file? I might take a look there. | 18:08:46 |
| PowerUser64 | (possibly by passing -v or something to the launch command) | 18:09:37 |
| 28 Feb 2024 |
|  @/yvan:matrix.org left the room. | 15:45:01 |
| 1 Mar 2024 |
|  @adham-omran:matrix.org joined the room. | 09:00:50 |
| 2 Mar 2024 |
|  @qyriad:katesiria.org joined the room. | 19:34:32 |
| 3 Mar 2024 |
| @fractivore:cyberia.club | Somebody is working on a SilverBlue image for content creation and they're including nix as one of 3 package managers: https://github.com/tulilirockz/Atomic-Studio | 03:56:50 |
| @fractivore:cyberia.club | I gave them my NixOS audio config as reference and they're including everything from that as default 🙂 | 04:07:47 |
 Minijackson | that's cool, congrats! 🎉 | 08:12:48 |
