I once met a person that never drank water, only soft drinks. It’s not the unhealthiness of this that disturbed me, but the fact they did it without the requisite paperwork.

Unlike those disorganised people I have a formal waiver. I primarily drink steam and crushed glaciers.

  • 1 Post
  • 24 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle






  • WaterWaiver@aussie.zonetoTechnology@lemmy.mlethinically ambigaus
    link
    fedilink
    English
    arrow-up
    40
    arrow-down
    1
    ·
    edit-2
    11 months ago

    I’ve been encountering this! I thought it was the topics I was using as prompts somehow being bad – it was making some of my podcast sketches look stupidly racist, admittedly though some of them it seemed to style after some not-so-savoury podcasters, which made things worse.





  • The fact this issue is happening on both Pipewire and Pulseaudio also suggests it’s more likely a bug in the drivers… It might not be obvious on ALSA directly, but that doesn’t mean an issue doesn’t exist there…

    I probably made the overlap unclear, sorry:

    • Pipewire issues: My 2023 desktop and 2016 laptop, very different hardware.
    • Pulseaudio issues: All of my pre-2023 desktops and several family laptops

    I do a lot of middleware development and we’re regularly blamed by users for bugs/problems upstream too (which is why we’ve now added a huge amount of enduser diagnostics/metrics in our products which has made it more obvious the issues aren’t related to us).

    Eep, that’s annoying. You also probably don’t have direct interaction with the users most of the time (they’re not your customer) which makes this worse, people in a vacuum follow each other’s stories.

    In practice, very few people have issues with Pulseaudio (I haven’t seen issues since launch). Sometimes as well, keep in mind it can be the sound interface (especially if its USB)

    There might be a bias here because these problems are not persistent, ie a reboot fixes them.

    In regards to setup, most distributions will handle that anyway I’m guessing. So not sure why the configuration process should matter unless you’re in Arch or Slackware? As long as the distribution handles it, it shouldn’t matter. It’d really a non-issue honestly.

    That’s potentially more things different distros can do differently and more issues your middleware will start getting blamed for.

    Yes it’s not a problem for user-friendly distros, but why does the user friendliness problem exist anywhere anyway? It’s better to fix problems upstream, not downstream.


  • If you check SystemD, its a HUGE step up, which is why everyone is using it now

    I think that’s a “winners write history” situation. There were other options at the time that might have been better choices. Everyone uses it now because of Redhat and Debian being upstream to most users, desktop and corporate. I was not surprised by Redhat adopting it (it’s their own product) but Debian was quite the shock.

    Yes systemd is definitely a step up from traditional initscripts (oh god). In terms of simplicity, reliability and ease of configuration however it’s a step below other options (like runit). I don’t have distro management experience but, given the problems I’ve encountered with different init systems over the years, I suspect there would be less of a maintenance burden with the other options.



  • I’ve been using PipeWire this year on my Void Linux laptop & desktop. It’s been mostly OK but has a few problems. For years I have been using plain ALSA (with no custom configuration) because pulseaudio causes me regular issues across multiple machines (mostly silently failing).

    Pros:

    • I don’t have to use Chromium for my mic to work on online video conf (WTF Firefox)
    • “EasyEffects” lets me quickly fix crappy youtube audio (bad gain normalisation, way too much sibilance) with a minimum of effort.

    Cons:

    • Sometimes breaks all audio until I manually restart it (hey, just like pulseaudio. This problem never happens when using ALSA straight)
    • First time setup is complicated, involving environment variables, dbus user session buses and multiple daemons (running just pipewire isn’t enough). Why can’t it handle this all itself? Surely it should notice if these things are missing and just fix it itself? Compare this to straight ALSA where you (1) do nothing and then (2) everything works (except Firefox mic support)
    • I can’t have multiple audio outputs all unmuted at the same time. Eg my headphone output and my rear speaker output. If I override this (using alsamixer) then it gets forgotten next boot anyway, it seems to be out of scope of PipeWire’s understanding.


  • To add to this: “level design” typically covers things like the design of paths through the level (both physically and plot/objectives) and visibility of paths affecting player thinking and choices (ie making it clear to the player how to progress, not get lost). These are “big scale” things, not fine detail.

    “Gameplay design” typically covers things like movement, interaction and item/skill progression mechanics. The are “small scale” (or for inventories & skill trees: “no physical scale”) things.

    In practice the two terms do often overlap quite a bit, so you can argue basically anything to be in either category.



  • That looks super frustrating :|

    I just finished the last level of Perfect Dark (released in 2000 for N64). The hardest part was right at the end (boss fight with rockets being fired at you, one hit and you’re dead) and there are no checkpoints. I repeated this same level so many times and had to read a walkthrough in the end – it turns out I was stuck at a red herring.