home.social

#systemsoundserverd — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #systemsoundserverd, aggregated by home.social.

  1. @RogueAmoeba Also worth pointing out that, if I wasn’t an experienced Mac troubleshooter who knows about force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor, I would have no choice but to reboot my Mac in order to get things working right. That's just wrong. One of the main reasons for the very existence of #macOS is that our devices don't have to be rebooted all the time. Yet either you know all kinds of obscure workarounds or you have no choice but to reboot.

  2. @RogueAmoeba Also worth pointing out that, if I wasn’t an experienced Mac troubleshooter who knows about force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor, I would have no choice but to reboot my Mac in order to get things working right. That's just wrong. One of the main reasons for the very existence of #macOS is that our devices don't have to be rebooted all the time. Yet either you know all kinds of obscure workarounds or you have no choice but to reboot.

  3. @RogueAmoeba Also worth pointing out that, if I wasn’t an experienced Mac troubleshooter who knows about force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor, I would have no choice but to reboot my Mac in order to get things working right. That's just wrong. One of the main reasons for the very existence of #macOS is that our devices don't have to be rebooted all the time. Yet either you know all kinds of obscure workarounds or you have no choice but to reboot.

  4. @RogueAmoeba Also worth pointing out that, if I wasn’t an experienced Mac troubleshooter who knows about force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor, I would have no choice but to reboot my Mac in order to get things working right. That's just wrong. One of the main reasons for the very existence of #macOS is that our devices don't have to be rebooted all the time. Yet either you know all kinds of obscure workarounds or you have no choice but to reboot.

  5. @RogueAmoeba Also worth pointing out that, if I wasn’t an experienced Mac troubleshooter who knows about force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor, I would have no choice but to reboot my Mac in order to get things working right. That's just wrong. One of the main reasons for the very existence of #macOS is that our devices don't have to be rebooted all the time. Yet either you know all kinds of obscure workarounds or you have no choice but to reboot.

  6. I was initially tempted to blame a bug in one of my third-party @RogueAmoeba audio tools, namely either #SoundSource or #Loopback. But I knew very well it was actually more likely to be macOS itself.

    Ended up force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor and… sure enough, things were back to normal after that.

    Today’s Apple for ya. A picture of software unreliability and untrustworthiness.

    2/2

  7. I was initially tempted to blame a bug in one of my third-party @RogueAmoeba audio tools, namely either #SoundSource or #Loopback. But I knew very well it was actually more likely to be macOS itself.

    Ended up force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor and… sure enough, things were back to normal after that.

    Today’s Apple for ya. A picture of software unreliability and untrustworthiness.

    2/2

  8. I was initially tempted to blame a bug in one of my third-party @RogueAmoeba audio tools, namely either #SoundSource or #Loopback. But I knew very well it was actually more likely to be macOS itself.

    Ended up force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor and… sure enough, things were back to normal after that.

    Today’s Apple for ya. A picture of software unreliability and untrustworthiness.

    2/2

  9. I was initially tempted to blame a bug in one of my third-party @RogueAmoeba audio tools, namely either #SoundSource or #Loopback. But I knew very well it was actually more likely to be macOS itself.

    Ended up force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor and… sure enough, things were back to normal after that.

    Today’s Apple for ya. A picture of software unreliability and untrustworthiness.

    2/2

  10. I was initially tempted to blame a bug in one of my third-party @RogueAmoeba audio tools, namely either #SoundSource or #Loopback. But I knew very well it was actually more likely to be macOS itself.

    Ended up force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor and… sure enough, things were back to normal after that.

    Today’s Apple for ya. A picture of software unreliability and untrustworthiness.

    2/2