All listening guides

Product help

TrueMusic Playback Recovery: What to Check Before Clearing Data

Separate a silent player, an unavailable recording, an app update, and missing local downloads. Follow a checklist that preserves useful evidence and saved selections.

By TrueMusic.app · Updated · 6 min read

01

First identify what failed

Write down the track title, artist, version, and page where the problem appeared. Then try one other available recording. If the second plays, you have evidence of a recording-specific problem; if neither plays, investigate the player, device, or connection. This comparison narrows the problem but does not identify its cause by itself.

A page loading successfully is not proof that its audio source is reachable. Similarly, missing lyrics or a video preview does not prove the audio is broken: those features use separate requests. Change one thing at a time so your next observation is useful.

Choose the smallest useful check
What happenedNext checkWhat it can tell you
The player moves but you hear nothingPress play directly; check tab mute, volume, and audio outputWhether sound is blocked or going to another device
One recording failsTry another available recordingWhether the failure is specific to the first selection
The interface fails after an updateReconnect, then reload onceWhether the app can load its current files
Downloads are missingCheck the original device, browser profile, and site addressWhether you are looking at the storage where they were saved
02

Check sound before resetting anything

Use the visible play control yourself rather than expecting a newly opened page to start audible playback. Browsers can restrict autoplay until the visitor interacts with the page. Check whether the browser tab is muted and whether Bluetooth headphones or another output are selected. If the play position advances, look at these checks before deleting data.

For a shared room, ask one person to coordinate a single change and wait for the result. If one listener is silent while others hear the same recording, check that listener's sound and page interaction first. This is a diagnostic suggestion, not a guarantee of perfect synchronization.

03

Know which saved item you are protecting

TrueMusic stores downloaded audio and its track information in this browser's local database. The listening planner separately saves a track list when you choose Save track list on this device. Neither is an audio backup in your account. Moving to another browser or device does not move these local items with you.

The app also caches interface files so an installed web app can open without fetching every file again. Those interface files and downloaded recordings are different stores. Clearing all site data is broader than refreshing the interface and can remove both local recordings and the saved planner list.

What a saved item actually contains
ItemContainsPreserve it before troubleshooting
Listening planner saveTrack names and lengths in this browser; target and gaps are not savedExport the current plan as a text file
Planner text exportNames, durations, target, gaps, and calculated running orderKeep the file outside browser site storage; it contains no audio
Offline downloadA local audio file and track metadataRecord important titles and authorized source links; do not assume sign-in restores the file
Cached interfaceApp files used to open the interfaceWhile online, check that the app opens before depending on offline access
04

Handle an app update while connected

When TrueMusic detects a waiting web-app update, it shows an Update ready message with a Reload button. Save any planner changes and choose a suitable break in listening before using it. The installed app keeps its current file set until the update is activated.

For certain failed app-file loads, TrueMusic attempts a recovery reload. Its cache cleanup first checks that a fresh HTML page is reachable and skips cleanup if that check fails. This path does not directly delete the download database or planner save. It is narrower than the browser's Clear site data command, but it cannot restore content a browser has already removed.

If the app is still inaccessible, record the error and reconnect before another attempt. Do not uninstall or clear all browser storage as your first offline troubleshooting step: you may remove the interface you need to reach your downloads.

05

If local recordings or a plan have disappeared

Check whether you switched devices, browser profiles, private browsing sessions, or site addresses. Browser storage is associated with a site origin; the scheme, host, and port matter. Return to the original context before concluding that data was deleted.

Browsers manage storage limits and can remove nonpersistent site data. Private browsing also has a different storage lifetime. A missing local file is not necessarily an account problem. If the file was removed and you have no permitted copy elsewhere, this guide cannot recover it. For the planner, a previous text export lets you manually re-enter names and lengths; the planner currently has no import control.

06

Prepare for a connection-free session

Only save audio when the source and rights holder authorize the copy. While connected, open Downloads and check the exact recordings you plan to use. Then briefly disconnect and test the beginning of each saved selection on the same device and browser. Restore the connection afterwards. This is a check you should perform, not a claim that every device has passed it.

A successful start does not guarantee an uninterrupted long session, but it is better evidence than an untested download label. Keep a separate note of important recording details. If you use the listening planner, export the finished running order too; a timed text plan is useful even if the player or saved local list later becomes unavailable.

07

Send evidence that support can use

Describe what happened before and after one check. Include the browser, device, page path, track title and version, whether another recording played, and whether you were online. For update failures, include the displayed error and whether the Update ready message appeared.

Do not send passwords, sign-in codes, cookies, or a URL containing a private token. The checklist below builds a report from your answers on this page. It does not inspect your library or send anything; review it before copying it into an email.

Work through your playback problem

Choose a symptom and tick each check after trying it. Your answers stay on this page and are not saved or sent. Copy your report before leaving.

Checks to try
Contact support