Case Study
macOS Audio Missing: Why Spotify and YouTube Were Silent
The Client’s Challenge
I recently worked with a client who was experiencing a confusing audio problem on his Mac. He was having no sound come through when trying to play music on Spotify and YouTube. This was highly frustrating because the audio was working perfectly inside his Digital Audio Workstation (DAW), Logic Pro.
The client was naturally confused. If his studio monitors and audio interface were working well enough for his production software, why was all system audio completely silent? It was a technical barrier interrupting his day, preventing him from referencing tracks or simply enjoying music outside of his session.
Session Setup
I began the remote session by establishing a secure connection to the client’s Mac desktop. This one-to-one service is what Audio Support is built around; it allows me to examine the full signal chain, hardware, and software setup without guesswork. The client had his usual Universal Audio (UAD) audio interface connected and running.
My first check was simply to play audio from different sources to confirm the issue was consistent. As the client reported, Logic Pro audio was crisp and clear, but Spotify’s output meters were moving without any corresponding sound from the speakers. This immediately pointed me towards a system-wide setting rather than an application-specific fault.

Diagnosis
The reason the client could hear audio in Logic Pro but not in other applications like Spotify or YouTube is due to a fundamental difference in how they handle sound. Logic Pro, like most DAWs, has its own internal sound settings page. The client had correctly configured this to play back through his audio interface.
Conversely, most consumer applications—such as web browsers, Spotify, and messaging apps—rely on the macOS default sound device. My hypothesis was that this default device was set incorrectly, directing the system’s main audio to a virtual location instead of the physical interface.I guided the client to the Sound Settings section within macOS Preferences. Sure enough, under the Output tab, the primary device was selected as a Virtual Audio Cable. This cable was likely left over from a past streaming, recording, or broadcasting setup and was routing all OS X audio internally to nowhere.
The Fix
The solution was a straightforward adjustment of the macOS default output setting. I simply needed to change the device from the non-physical Virtual Audio Cable to the correct hardware.
We had two solid options here: either select his UAD interface directly, or choose his custom Aggregate Device, which he used for specific studio routing. Since the goal was to restore general system audio, we switched the default output to his main UAD interface.
The moment the change was applied, the problem was instantly resolved. As the client played a track on Spotify, the sound came through his studio monitors as expected, confirming the hypothesis was correct and the core issue was a simple configuration error within the operating system.
Result
The one-hour session resulted in the client having full system audio restored across all applications on his Mac. Spotify, YouTube, and all other non-DAW applications were playing back through his primary audio interface, allowing him to use his studio monitors for referencing and general listening again. The client was able to immediately get back to his creative work.
Reflection
This case is a classic example of a holistic diagnosis being essential. A manufacturer helpdesk for Spotify would tell the client to check the Spotify app settings, and an Apple representative might ask him to reboot. However, the true cause was a conflict between the professional (DAW) and consumer (OS X default) audio layers.
When troubleshooting studio setups, it’s critical to look beyond the crashing application and examine the full signal chain, especially the bridge between the professional audio world (DAWs, interfaces) and the operating system’s default settings. In macOS, if you have no sound outside your DAW, the system’s default audio output is always the first place to check.
Closing Thoughts
These frustrating audio configuration issues are common in complex studio environments. They often come down to a single setting in an obscure preferences panel, but finding it requires experience with the whole system.
I help musicians and producers worldwide solve problems like this every day. If you’re struggling with macOS audio setup, I’ll help you fix it and get back to creating.
Recent Reviews
Let’s Get Your System Running Smoothly.
No automated tickets, no waiting queues — just one-to-one help from an experienced music technology specialist. I’ll connect to your system remotely, identify the issue, and guide you through the fix.
I usually reply to enquiries within a few hours during UK weekday daytime.
Once you make an enquiry, I’ll read it personally and reply with initial advice or a link to book a remote session if needed.
For booked sessions, you’ll receive a secure AnyDesk link and we’ll talk via WhatsApp or voice chat. Sessions last up to an hour — long enough to diagnose the cause and apply a practical fix.
Make an Enquiry
I’ll reply personally as soon as I can — usually within a few hours during UK daytime.
Book Your Session Securely Online
You can book your Audio Support session instantly using the secure form below.
Choose a time that suits you — I’ll confirm by email and send remote-access details before your appointment.

Outside the UK? Use the Timezone icon to book in your local time.
- 💳 Session fee: £90 per hour (UK Pound Sterling)
- ⏱️ Availability: Usually within 1–2 days.
- 🗓️ Duration: Each session lasts one hour.
- 🔁 Rescheduling: Sessions can be moved up to 24 hours in advance.
- 🔒 Security: Remote access is one-time only and closes automatically when the session ends.
- 🌍 Timezone: Default times shown are UK (GMT/BST). Use the timezone Icon to set to your local time
You don’t have to keep guessing what’s wrong — I’ll help you find the cause and fix it, so you can get back to making music.
More Case Studies
Recent problems solved for real clients.
macOS Audio Missing: Why Spotify and YouTube Were Silent
25 November 2025
Client’s Question
Why does my Mac have no sound from YouTube/Spotify but works in Logic Pro?
Session Result
macOS default sound device correctly set, system audio restored to UAD interface.
Read Full Case Study Report: macOS Audio Missing: Why Spotify and YouTube Were SilentFocusrite Missing MIDI Notes in Cubase: A Driver Reinstall Fix
25 November 2025
Client’s Question
Why are my Cubase MIDI notes missing with my Focusrite interface?
Session Result
Full polyphony restored after Focusrite driver reinstallation.
Read Full Case Study Report: Focusrite Missing MIDI Notes in Cubase: A Driver Reinstall FixFixing Fuzzy High Notes for a Twitch/YouTube Singer
25 November 2025
Client’s Question
Why do I get fuzzy sound in my microphone when I sing high notes?
Session Result
Microphone distortion eliminated; clean, professional vocal chain configured in OBS.
Read Full Case Study Report: Fixing Fuzzy High Notes for a Twitch/YouTube SingerAI as a Creative Partner: A Case Study on Using Suno with Cubase
23 November 2025
Client’s Question
How can I use Suno AI with my own acapella from Cubase?
Session Result
Created a custom, AI-generated backing track in Suno from a Cubase vocal export.
Read Full Case Study Report: AI as a Creative Partner: A Case Study on Using Suno with Cubase