WaveLog playback troubleshooting: silence, buffering, and dead URLs

When the dial moves but nothing comes out

Live radio over the public internet is fragile by nature. Stations change CDNs, geoblock regions, expire mount points, or sleep overnight. Before you assume WaveLog itself is broken, walk a short triage. Most “silence” reports resolve into one of: bad URL, local audio route, network middlebox, or a station that is simply offline.

Open WaveLog at wavelog.zettyfactory.com and keep this page nearby. If you are still building your list of stations, pair this with how to add stations and find stream URLs.

Triage order that saves time

1. Confirm device volume, silent switch (iOS), and correct output (Bluetooth vs speaker).
2. Try a second known-good station in WaveLog — ideally one that worked yesterday.
3. Open the stream URL in a desktop browser or VLC. If it fails everywhere, the station side is down or blocked.
4. Disable VPN / ad blockers / privacy relays temporarily.
5. Compare desktop vs mobile on the same network, then mobile on cellular.
6. Only then dig into WaveLog-specific library hygiene (My Channels duplicates, stale URLs).

Silence with a “playing” UI

The player can look active while audio never starts. Common causes:

• Muted tab or OS mixer. Browsers mute background tabs; macOS/Windows per-app volume may be at zero.
• Bluetooth handoff. Audio routed to dead headphones still in the paired list.
• Autoplay restrictions. Some browsers need a fresh user gesture after a long idle; tap play again.
• Codec mismatch. Rare mounts use formats a particular mobile browser refuses. Desktop may work while mobile stays silent.

Quick check: play a local music file or another site’s audio. If the device is silent everywhere, fix the OS audio path first.

Buffering that never ends

Endless buffering usually means packets are slow, filtered, or the server is accepting connections without sending media.

• Switch from Wi‑Fi to cellular (or reverse) to rule out captive portals and flaky AP.
• Pause other downloads / meetings that saturate the uplink on shared Wi‑Fi.
• Try again off-peak — small community stations sometimes overload on event nights.
• If only one station buffers while others are instant, replace that station’s URL (see the add-station guide).

Desktop vs mobile differences

The same stream can behave differently across clients:

• Desktop browsers often tolerate quirky redirects better and make it easier to inspect Network panels.
• Mobile Safari / Chrome are stricter about autoplay, background playback, and mixed HTTP content inside HTTPS pages.
• Low Power Mode / Data Saver can throttle media.
• Carrier DNS / private relay can alter which CDN edge you hit, changing geo results.

When filing a mental bug report, note: device, browser, network type, and whether the raw URL works outside WaveLog. That single sentence separates app issues from station issues.

Dead URLs and “it used to work”

Stream mounts rot. A URL that worked in spring may 404 in autumn after a transmitter upgrade. Symptoms: instant error, immediate end event, or HTML error page where audio should be.

1. Re-copy the stream from the broadcaster’s current listen page.
2. Update or replace the entry in My Channels rather than keeping zombies.
3. If the station moved to a player-only page with rotating tokens, you may not get a stable public mount — respect that limit.

Blockers, VPNs, and corporate networks

• Ad / tracker blockers sometimes treat streaming domains as trackers. Allowlist WaveLog and the station host temporarily to test.
• VPNs can fix geo blocks or create them. Exit in the “wrong” country and a licensed stream may refuse you; exit through a filtered node and mounts time out.
• School / office firewalls often allow HTTPS websites but cut long-lived media or unusual ports. Try cellular tethering as a control.

Geo and DRM limits (again)

Some broadcasters only authorize certain apps or regions. WaveLog cannot override a station’s access policy. If the official site plays only inside their branded player with DRM, third-party clients will fail even with a copied URL. That is compliance, not a missing WaveLog feature.

A five-minute field checklist

When you are away from a desk and only have a phone, run this compressed version:

1. Volume + output device OK?
2. Does a second WaveLog station play?
3. Toggle VPN / private relay off for one attempt.
4. Switch Wi‑Fi ↔ cellular once.
5. If still silent, open the station’s official site player. If that fails too, wait or find an updated mount later — do not thrash My Channels yet.
6. If the official site works but WaveLog does not, note the stream host and revisit on desktop with the add-station guide open.

Most travel-day failures stop at step 3 or 4. The expensive mistake is renaming and re-adding the same dead mount six times before checking whether the broadcaster is offline for everyone.

My Channels hygiene after fixes

After you restore playback, clean the library: remove duplicates, rename stations with clear labels, and keep one known-good “canary” station at the top for future triage. Future-you will thank present-you when silence returns on a travel network.

Still stuck after the URL plays fine in VLC but not in WaveLog? Note the format and contact path from the WaveLog product page / studio contact — include the stream host (not necessarily a private tokenized URL) and the device details above. For rebuilding a healthier list from scratch, return to finding stream URLs and adding stations.