121–130 of 136 posts
An issue I've experienced very often is that sometimes when my laptops goes to sleep and I wake it up, the speakers occasionally aren't switched to unless I restart pipewire. Same thing for headphones, sometimes when I plug them in, they aren't switched to unless I replug it in a couple of times. Might be hardware related but situations like this make me feel like I should just use linux for servers instead of for a…
Earlier quoted context omitted.
Pipewire ends up being used to paper over Wayland deficiencies in some areas, thus why it's important for Wayland desktop ;) By itself it's essentially grand unification of audio servers that actually works better and is way less... opinionated about the only true way some things works, which was a problem with pulseaudio at times.
Separation of responsibilities is good, instead of having a mix of everything but not well enough situation with X11.
Earlier quoted context omitted.
Separation of responsibilities is good, instead of having a mix of everything but not well enough situation with X11.
Separation of responsibilities is something Wayland fails hard, by effectively hardcoding coexistence of significant part of display driver, windows management, simple things like windows decorations (which, thanks to Gnome's insistence, are by default only client-side, so your concerns invade internals of client apps!) etc.
But if anything it's X11 that tries to lump a ton of stuff together. Wayland is very minimalistic in comparison. That's why stuff like libinput and Pipewire are part of making a functional desktop.
Am I the only one that sees unfriendly input/output channel names with Pipewire in client software? (Bitwig, Ardour, Reaper, more? I would like to see "Input 1" or "Channel 1" and not some strange ciphers when trying to assign things in a little dropdown selector in a DAW)
Earlier quoted context omitted.
nah I'm okay thanks. X11 still works flawlessly for me.
The main issue is that X11 is an increasingly unmaintained case and all new development happens with Wayland anyway. So as long as you can deal with lack of support - I guess no need to move, but otherwise Wayland with KDE has been well usable for a while already.
Earlier quoted context omitted.
Separation of responsibilities is something Wayland fails hard, by effectively hardcoding coexistence of significant part of display driver, windows management, simple things like windows decorations (which, thanks to Gnome's insistence, are by default only client-side, so your concerns invade internals of client apps!) etc.
Just don't use Gnome. KDE is fine with server side decorations and it's false that Wayland mandates client side ones. Wayland ≠ Gnome and Gnome itself indeed made a bunch of pretty questionable decisions. But if anything it's X11 that tries to lump a ton of stuff together. Wayland is very minimalistic in comparison. That's why stuff like libinput and Pipewire are part of making a functional desktop.
More over, every "WM" in Wayland's case needs to implement the entire stack, even if it uses a common library for some of it.
And after similar length of development time, I'd say the result is still worse in many aspects than X11, and I say that as someone both using and praising a wayland-based compositor and lamenting that it pretty much locks me more than Windows used to
An issue I've experienced very often is that sometimes when my laptops goes to sleep and I wake it up, the speakers occasionally aren't switched to unless I restart pipewire. Same thing for headphones, sometimes when I plug them in, they aren't switched to unless I replug it in a couple of times. Might be hardware related but situations like this make me feel like I should just use linux for servers instead of for a…
What version of Linux did your laptop ship with?
I have the latest kernel version now.
Earlier quoted context omitted.
What version of Linux did your laptop ship with?
It had Fedora 36. So maybe Linux kernel 5.17 I have the latest kernel version now.
What vendor and model laptop was it? I'll make a note to avoid them in the future.
Earlier quoted context omitted.
> Have you tried Linux audio forums/community Actually I've gotten everything to work adequately but claiming the alsa/pulse/jack to pipewire transition wasn't just a new nightmare would be wrong, well for me. > "you need to use windows (or mac) to do anything serious" Correct and maybe! Serious as in commercial or production? Yes! Serious as in exploration in HCI and digital instrument creation and what kind of new…
Do you have some repos and/or write-ups on these projects? That sound pretty cool.
Maybe I'll do a write-up on the setup to make it easier.
Really I look at things like musique concrete, BBC radiophonic workshop and John Cage and think that's where, a few decades removed, all the modern sound has come from that's been so dominant for the past 40 years or so.
I want to embrace the new and weird so 30 years from now I can help be a historical part of building whatever is coming next.
Tomorrow's all we got!
I want to move my DAW to Linux, but giving up TotalMix is quite a blow... Not sure how well the NI Native Access crap is working on WINE either. Does anyone know?
[0] https://appdb.winehq.org/objectManager.php?sClass=version&iI...