121–125 of 125 posts
Earlier quoted context omitted.
Debian Sid (aka Unstable) is just as bleeding edge as any other "rolling" distro.
Sid is a rolling unstable development build, that doesn't compare to a rolling stable release - particularly in regards to conversations on what users should expect.
Earlier quoted context omitted.
You can also munge the pw-dump output with jq, instead of needing something to be compiled. pw-dump | jq ' ( .[] | select(.type == "PipeWire:Interface:Metadata") | (.metadata // [])[] | select(.key == "default.audio.sink") | .value.name ) as $default_sink_node_name | .[] | select(.info.props["node.name"] == $default_sink_node_name) as $default_sink_node | . '
Yes. This is how I did it initially, before rewriting it using serde. However, as I mention here ( https://www.reddit.com/r/swaywm/comments/sks343/comment/hvn3... ), shell with jq was too slow -- particularly if you're holding down the volume key.
I recently made the switch in NixOS and found it pretty painless. Can't get my mic to work in Firefox though, and the other day I was looking through the manual trying to figure out how to use my HDMI screen's speakers rather than the built-in one and couldn't find the right incantation. Sounds like such rough corner cases will be a thing of the past soon. Congrats to the dev team!
Assuming you're talking about Bluetooth mics: If you're using pipewire-media-session (for example, if you're on NixOS 21.11 instead of NixOS unstable), then profile autoswitching [0] is disabled by default, so you have to use pavucontrol to switch from A2DP to HSP. Profile autoswitching is enabled by default in WirePlumber, which is the default session manager in NixOS unstable as of a few days ago. [0] https://wiki.…
(Kinda goes to show that enabling this feature by default is a good idea.)
Thanks, you just made my day!
I have been impressed how I've been able to make arbitrarily complex audio graphs in QJackCtl and it just works. I can even activate patch bays and it forces the audio configuration and applications (even browsers) stay happy. It's impressive how it manages to support connections that require reclocking and do the needed large ratio resampling needed behind the scenes, something that PulseAudio was never really able…
Dumb question: what did the Pipewire developers do that makes it so much better than everything else on Linux? Sound has been an absolute disaster area on Linux for decades and it seems like the Pipewire guys just flat out solved it. (I would say "suddenly", but Wim Taymans has been working on this directly for almost 7 years and worked on Gstreamer before it) What did they do so much better and differently?
Earlier quoted context omitted.
This is an aside , but I've been watching all the audio graph editor projects pop up and it's made me realize I want something like this for package management. A package maintainer should be able to specify something is a dev dependency, runtime dependency. I should be able to form a "user dependency" where I say Xwayland depends on sway - even though it doesn't. So when I remove sway it pulls out Xwayland with it.…
You can visualize dependencies as a graph with Guix out of the box [1]. While you can't easily setup "user dependencies" (except by editing the package definition) you can create profiles that install packages from a manifest file so you could have a profile with a manifest with xwayland and sway and then simply remove the profile if not needed. Guix already specifies runtime/dev dependencies. [1]: https://guix.gnu.o…