• Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Suddenly lost output on Mac

    Scheduled Pinned Locked Moved Technical Help
    3 Posts 2 Posters 905 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mike_jones
      last edited by mike_jones

      Strawberry 1.0.22, MacOS 13.6.4 (Ventura).
      I've been using Strawberry with all my music mounted via an SMB share for months now. It was working on Tuesday. I left it sitting, paused, on Tuesday night. On Wednesday I was away from home all day. Thursday morning, I came back to my computer and hit play and....no music. I can see the track timer incrementing at the bottom of the window. I get sound for notifications and other things.
      As far as I can tell, there haven't been any changes to the system (no OS updates, for instance) in the last couple of days.
      Have tried

      • rebooting my Mac
      • making sure the share is mounted and I can access files in it
      • killing strawberry and starting it in a terminal window with --verbose

      Any suggestions for troubleshooting/fixing this?

      jonasJ 1 Reply Last reply
      Reply Quote 0
      • jonasJ
        jonas @mike_jones
        last edited by

        @mike_jones
        Go to settings / Backend / Output and select "Output to a soundcard on macOS".
        Select your device below, stop and start playback again and see if that works.

        M 1 Reply Last reply
        Reply Quote 0
        • M
          mike_jones @jonas
          last edited by

          @jonas
          Thanks. I tried that, didn't work, but it did cause me to wonder if there was something about the track (that I wasn't previously familiar with) that might be causing the problem. I put the output settings back to the wrapper sink, tried to play another track, and...it worked. The track that had me convinced something was wrong just had a significant period of silence at the beginning for some reason.

          Complete pilot error. Mea maxima culpa.

          1 Reply Last reply
          Reply Quote 1

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • First post
            Last post
          Powered by NodeBB | Contributors