Eskating cyclist, gamer and enjoyer of anime. Probably an artist. Also I code sometimes, pretty much just to mod titanfall 2 tho.

Introverted, yet I enjoy discussion to a fault.

  • 5.76K Posts
  • 3.1K Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle











  • That’s not what I’m saying at all. I’m saying Collaboras implementation is fundamentally unfit for use.

    I used to host a CODE server.

    It ran like shit, because it works by rendering the viewport on the remote system, not the client. Instead you essentially send every input to the server, wait for it to render the change, and then send that back to the client. Collabora is like using office software through vnc. Except all the time.

    The responsiveness is atrocious. Especially if you try to use it over a less than ideal connection.

    But it’s just fucking text data. It shouldn’t require the same infrastructure as remote gaming to be usable. It should be able to handle multiple seconds of latency, and just sync back up without the user ever noticing.

    But it can’t. Because it RENDERS on the server. Which means the tiniest hiccup in the connection between server and user causes noticable issues.





















  • AFAIK the “right” way to do this is use a virtual device for system audio, and have that in turn output to the actual audio interface, so you can keep it maxed out.

    But that doesn’t really feel like the ideal solution.

    That said I’m probably missing something. EasyEffects is able to process audio in ways that should enable what you’re asking for, I just don’t know how.

    Also, if you haven’t already, check out qpwgraph. It’s a virtual patch bay for routing audio around however you want.

    Best part, is it’s not an add-on, really. It’s just a GUI for capabilities that pipewire already has.



  • Also food delivery.

    In Finland, there used to be “pizza-online” which was really just a directory and ordering system for restaurants that already did delivery themselves.

    They took a very small comission, as the site didn’t really do anything except connect restaurant and customer (and provide a review platform). For a long time, they didn’t even have an app.

    You’d log in, select a restaurant, browse their menu and place an order. The order goes to the restaurant, and after that the site’s job was done.

    It was massively succesful. Every hole in-the-wall pizza place was on there. Finding good food was easy and cheap, and the restaurants reached more customers than ever. And the platform including reviews led to competition in not just price, but quality.

    Then pizza-online sold to foodora, and they got shut down, and participating restaurant were no longer allowed to deliver themselves, and the cut taken by the platform skyrocketed.




  • TL;DR

    Install an archival version of Bazzite or whatever else that corresponds to a date when you know it worked correctly.

    Bazzite in particular makes this fairly easy. They have straight forward instructions on how to roll back to a given version.

    If that fixes it, just use that version and don’t update.

    If you want to stick with Cachy, you can use the Arch Archive to downgrade your entire system to an earlier date, or just Gamescope.


  • AND I AM TELLING YOU TO DOWNGRADE THEM SO YOU CAN SEE IF AN EARLIER VERSION WORKS CORRECTLY, INSTEAD OF SWAPPING OUT THE ENTIRE DISTRO

    ONLY TO TRY THE EXACT SAME COMPOSITOR AS IF THAT WOULD FIX IT

    So instead of that, try earlier versions! Different distros from the same date are obviously likely to be running similar versions of Gamescope or whatever else might be the cause.


  • No.

    We use the word distro because they’re not really a fully separate OS. Just a different preset with either a lot or almost nothing swapped out as compared to the next.

    You are so hung up being correct here you’re missing what I’m actually trying to teach you.

    You need to be comparing different versions, not distros. Because the same version of the same software is going to have the same problem, no matter what distro you use.

    You don’t even know how to access system logs, and you expect to understand enough about this stuff to successfully correct me on why trying a different distro isn’t that helpful for troubleshooting?


  • Software packages that are different.

    No? The same software is the same software, regardless what distro you install it on.

    Gamescope running on top of KDE/Plasma in one distro will not be different from Gamescope running on top of KDE/Plasma in another distro.

    Distros are just presets. The vast majority have far more similarities than differences.

    What makes one distro different from another, is that it might come with gnome instead of KDE, pacman instead of apt, initd instead of systemd, systemd-boot instead of grub.

    Or any other litany of alternative packages that do the same things.

    But if you use the same software, then there is little difference between one distro and the next. The main difference is going to be that you installed the same code from a different distributor.

    That’s literally where the name “distro” comes from.