Skip to content
⌂ Home

ECHO NEXT User Guide

This guide is written the practical way: where to click after opening the app, what a normal result looks like, and where to check first when something goes wrong.

You do not need to understand the engineering first. Learn to import local songs, play them, find them, and switch output devices; then move on to lyrics, the equalizer, remote libraries, and plugins. The official product does not provide third-party streaming-platform search, login, online playback, or downloads.

Installed from Steam? Cloud, achievements, Listen Together, Workshop, and Pro DLC are in Using the Steam edition. Daily listening is the same as the website build: import files, then play.

If you are new, read in this order:

  1. Start with Quick Start or the “First use” section on this page.
  2. Prefer learning day by day? See the First Week plan.
  3. Once you hear sound, read Daily Listening.
  4. Stuck? Match your symptom in Common stuck points.
  5. Albums or covers a mess? See Library.
  6. Lyrics off? See the Lyrics guide.
  7. Enable remote libraries and plugins last.

If you only want to know how one page works, jump straight to its section. This page is the full manual; the shorter guides above are better for following along click by click.

What you needJump to
First run, afraid of breaking thingsFollow along from zero and Places beginners should not touch
Copy an exact click pathShortest paths to common goals
Import and organize musicLocal library, Import Folder, Songs, Albums
Playback, queue, playlistsQueue, Playlists, Playback controls, Lyrics
Sound tuningAudio output and HiFi, Equalizer, ReplayGain and loudness
Remote libraries and devicesRemote library, LAN playback, Plugins
Something brokeCommon diagnosis routes and What to include in a report
Page nameWhat it is for
Import FolderAdd a local music directory to ECHO NEXT
InboxNewly imported, not-yet-organized tracks
SongsThe main all-songs list; daily search starts here
AlbumsAlbum wall and album details
ArtistsBrowse the library by artist
QueueThe temporary playback order
PlaylistsLong-term saved sets of songs
LikedQuick-mark favorite tracks
HistoryFind what you recently played
Remote LibraryWebDAV, Jellyfin, Emby, Subsonic, and other external sources
LAN PlaybackDLNA, AirPlay, and other local-network devices
Settings -> PlaybackOutput device, WASAPI, ASIO, ReplayGain, the playback chain
Settings -> EQ / DSPEqualizer, preamp gain, DSP processing state

A few technical names stay in their original form throughout: audio protocols, file formats, plugin permissions, and third-party tools such as WASAPI, ASIO, FLAC, and ReplayGain.

This section assumes you have never used a music player like this. Do not rush to understand every term; walk through it once. If you can play, find songs, and adjust output, you are through.

Remember three places on screen:

Screen areaWhat you use it for
Left menuDecides what you are doing now: import, find songs, browse albums, change settings
Middle listShows the current page’s content: song lists, albums, playlists
Bottom playerTells you whether playback actually started: title, cover, progress bar, and volume live here

Do not scan the whole drive right away. Prepare a small test directory and prove the basic chain first.

  1. Create a folder on your computer, for example D:\Music\Test.
  2. Put 3 to 10 tracks you know are good inside.
  3. Include at least one normal MP3.
  4. If you have FLAC, add one FLAC too.
  5. Do not start with exotic formats, corrupt files, or cloud placeholders.
  6. If the songs are on an external drive, confirm the drive is plugged in.
  7. If the songs are in a cloud sync folder, confirm the files are really downloaded, not just cloud placeholders.

Pick test files like this:

File typeWhy it is a good test
Normal MP3Easiest to play; confirms the basic sound chain
Normal FLACConfirms lossless files and tag reading
An album track with a coverConfirms cover and album display
No ultra-rare formatsRound one proves the app works; do not challenge the edges yet

Once the test folder plays, import the full library. That way, when something breaks, you know whether basic playback is broken or the problem comes from a large library, special files, or device settings.

Get local playback working in five minutes

Section titled “Get local playback working in five minutes”

Goal: confirm ECHO NEXT can scan your local songs and play them.

  1. Prepare a small folder such as D:\Music\Test.
  2. Put a few tracks you know are healthy inside, ideally MP3 and FLAC.
  3. Open ECHO NEXT.
  4. Leave settings alone for now; look at the left menu.
  5. Find Import Folder.
  6. Click Import Folder.
  7. The system shows a folder picker.
  8. Navigate to D:\Music\Test.
  9. Select the folder, not one song inside it.
  10. Confirm the import.
  11. Back in ECHO NEXT, wait for scanning to start.
  12. Do not poke dangerous settings mid-scan; let these few files finish.
  13. If the UI says scanning, reading, or importing, wait a moment.
  14. Open Inbox.
  15. Check whether those tracks appeared.
  16. Open Songs.
  17. Find one of the normal MP3s.
  18. Double-click it, or hit the play button.
  19. Check whether the bottom player shows the current song.
  20. Check whether the progress bar starts moving.
  21. Check that the volume is above 0.
  22. Listen for sound in your headphones or speakers.

A normal result:

PlaceNormal behavior
InboxNewly imported tracks visible
SongsTitle, artist, and duration visible
Bottom playerShows the current track
Progress barMoves forward during playback
Audio outputYou hear sound

If every item is normal, the most important step is done: local import and basic playback work. Lyrics, the equalizer, and remote libraries can all wait.

If you cannot see the imported tracks, check in this order:

  1. Did you select a folder, and not an empty directory?
  2. Does the folder actually contain audio files?
  3. Are the files real local files, not cloud placeholders?
  4. Is the scan still running?
  5. Check both Inbox and Songs.
  6. Is there leftover text in the search box? Clear it.
  7. Are the file extensions common audio formats such as MP3, FLAC, WAV, M4A?

If there is no sound, do not rebuild the database. Check in this order:

  1. Is the system volume muted?
  2. Is ECHO NEXT’s bottom volume too low?
  3. Is the current output device the headphones or speakers you are using?
  4. Try another MP3 you know is good.
  5. In Settings -> Playback, switch the output mode back to System or shared output.
  6. Turn off EQ, ReplayGain, and speed change.
  7. Play again.

After the first success, check four things

Section titled “After the first success, check four things”

Once the small test folder plays, run four simple checks.

  1. In Songs, confirm titles, artists, and durations look roughly right.
  2. In Albums, confirm albums appeared.
  3. Play a track with a cover and confirm the bottom player shows it.
  4. Type part of a song title into the Songs search box and confirm it is found.

Read the results like this:

SymptomWhat it meansDo first
Plays, but the title is garbledUsually source-file tag encoding or tag contentCheck the same file’s info in another player
Plays, but one album split into severalInconsistent album name, album artist, or disc numberSee “Organize one album” below
Plays, but the cover is wrongEmbedded or folder covers are inconsistentCheck the source files before clearing any cache
Cannot find a songWrong search terms, unfinished scan, or a leftover filterClear search and filters, then look in Songs

The goal of this round is not a perfect library. It is confirming the app can read files, display them, and play them.

Goal: add your long-term music directory to ECHO NEXT.

  1. Confirm the small folder test already works.
  2. Confirm the drive holding the full library stays online.
  3. For external drives, confirm the drive letter will not suddenly change.
  4. For NAS or sync drives, confirm the network is stable.
  5. Confirm you are importing the music root, not the whole system drive.
  6. Do not sweep C:\, download caches, game folders, or program folders into the scan.
  7. Open Import Folder or Folders.
  8. Select the full music root, for example D:\Music.
  9. Start the import.
  10. Let the first scan run to completion.
  11. You can browse Songs while it scans, but do not start a full remote index at the same time.
  12. A busy computer during the first scan is normal, especially while reading many covers and tags.
  13. When the scan ends, open Albums.
  14. Check that the album wall looks roughly right.
  15. Open Artists.
  16. Check for obvious duplicates or garbled names.
  17. Open Inbox.
  18. Check the newly imported content.
  19. Play a few tracks in different formats.
  20. Only then start tag cleanup, playlists, and lyrics.

A slow first scan does not mean something broke. It has to read files, tags, covers, durations, and album info. Large libraries take time.

After the full import, resist bulk fixes. Look in this order:

Look atWhy
Songs countConfirm roughly everything came in
InboxSee where the new content landed
AlbumsSpot obviously split albums
ArtistsSpot garbled or duplicated artists
Shuffle a few tracksConfirm more than the test folder plays

If you have tens of thousands of songs, day one only needs import, search, playback, and albums working. Do not combine bulk tag rewriting, cache clearing, database rebuilding, plugin installs, and a full remote index on day one.

The simplest daily flow:

  1. Open ECHO NEXT.
  2. Go to Songs.
  3. Use the search box, or switch to Albums for albums.
  4. Find what you want to hear.
  5. Play it directly, or right-click to add it to the queue.
  6. A temporary batch goes in the Queue.
  7. Long-term keeps go into Playlists.
  8. Special favorites get a like; find them later in Liked.
  9. Forgot what you just heard? Check History.

Goal: correct album display, correct track order, correct cover.

  1. Open Albums.
  2. Search the album title.
  3. If the album appears more than once, open each and inspect the tracks.
  4. Check that every track’s album name matches.
  5. Check that every track’s album artist matches.
  6. Check that track numbers run 1, 2, 3.
  7. For multi-disc albums, check disc numbers.
  8. If anything is wrong, go back to Songs.
  9. Find those tracks.
  10. Right-click and edit tags.
  11. Return to Albums and confirm the merge.
  12. If the cover is wrong, check the embedded cover or the folder cover.

The fields that matter most:

FieldWhy it matters
Album nameNames the album; tag field album
Album artistDecides whether same-named albums merge; tag field albumArtist
Track numberSets the track order; tag field trackNo
Disc numberSets multi-disc order; tag field discNo
YearShown as the release year; tag field year
CoverDetermines how the album wall looks

Goal: keep a batch of songs long term.

  1. Open Songs.
  2. Search for the songs you want.
  3. Select one or more.
  4. Right-click.
  5. Choose add to playlist.
  6. Pick an existing playlist or create a new one.
  7. Open Playlists.
  8. Find the playlist.
  9. Confirm the songs are inside.
  10. Next time, start from Playlists directly.

Suggested playlist categories:

PlaylistPurpose
DailyWhat you play most
New, to sortJust imported, undecided
Headphone testBass, vocals, soundstage, sibilance
Hi-res testHi-Res, DSD, different sample rates
NightStable loudness, not harsh
CarRoad listening

Goal: hear sound first, chase higher-end output later.

  1. Play a known-good track on the default output first.
  2. Once you hear sound, open Settings -> Playback.
  3. Find the output device.
  4. If unsure, use System output.
  5. For stable daily Windows output, try WASAPI Shared.
  6. Only if you specifically want exclusive access, try WASAPI Exclusive.
  7. Only with a professional sound card, try ASIO.
  8. After every mode switch, play the same song and confirm.
  9. On any problem, switch back to the last working mode.
  10. Turn off EQ, ReplayGain, and speed change while adjusting output.

How to judge whether output is healthy:

ItemNormal behavior
DeviceYou can see the headphones, speakers, or DAC you want
PlaybackProgress moves after pressing play
SoundNo pops, no obvious stutters, no strange speedup
StatusNo persistent errors
Track changePrevious and next work
  1. Play a song first.
  2. Open Lyrics.
  3. See whether lyrics appear automatically.
  4. If none appear, check the lyric source settings.
  5. If the whole file is early or late, adjust the time offset.
  6. If the wrong version matched, pick a candidate manually.
  7. If the font is too small, adjust the size in lyrics settings.
  8. If a busy background hides the text, enable readability enhancement or change colors.

There is no official platform MV search. If you attached a local video or a custom URL yourself, treat it as extra picture and do not expect millisecond alignment with the audio. Details in the Lyrics guide.

  1. Open Remote Library.
  2. Choose the source type: WebDAV, Jellyfin, Subsonic, and so on.
  3. Fill in a display name.
  4. Fill in the server URL.
  5. Fill in the account and password or token.
  6. Choose a sync mode.
  7. Click test connection first.
  8. Save only after the test passes.
  9. Try browse-only or a small index first.
  10. Build the full index once things are stable.

Do not launch heavy jobs against a huge remote library right away. Confirm connect, browse, and play first.

  1. Open Plugins.
  2. Look at the plugin name and source first.
  3. Open the plugin details.
  4. Review the permissions it requests.
  5. Be especially careful with settings:write, library:write, and network.
  6. Enable only if you trust it.
  7. After enabling, watch the activity summary and logs.
  8. If the plugin errors, disable it first.
  9. Repeated startup failures may get it quarantined by the host.

Beginners should start with the sample plugin only. Do not enable high-permission plugins from unknown sources.

This section is for “I do not know what is happening right now.” Do not panic; figure out which page you are on and what kind of thing you are doing.

You clickedYou are looking at
SongsThe song list
AlbumsAlbums
ArtistsArtists
FoldersLocal import directories
InboxNewly imported tracks
QueueThe current temporary playback order
LikedFavorites
HistoryPlayback history
PlaylistsLong-term playlists
Remote LibraryRemote source configuration
LAN PlaybackLocal-network casting devices
PluginsPlugin management
SettingsGlobal settings

The bottom player shows the current playback state. Check in order:

  1. Is there a song title?
  2. Is there a cover?
  3. Is the button showing play or pause?
  4. Is the progress bar moving?
  5. Is the volume too low?
  6. Are there error messages?
  7. Is the current output device correct?

If a list has songs but the bottom player never changes, you probably only selected a song and never actually started playback.

The right-click menu tells you what the current object is.

Right-click targetYou may see
Local songEdit tags, open folder, copy path, delete
Remote songAdd to queue, play, like — fewer local file actions
AlbumPlay album, add to queue, edit album tags, save cover
Queue itemRemove from queue, play next
PluginEnable, disable, reload, view logs

If a button is missing, ask: is this object remote? Does this page support the action? Is anything actually selected?

Common statuses mean roughly this:

StatusMeaningWhat to do
LoadingThe page or data is still preparingWait; do not hammer clicks
ScanningA library scan is runningLet it finish
QueuedThe task has not startedWait its turn
DownloadingA download task is runningWatch progress and speed
Importing to libraryResults are being written to the libraryCheck Inbox afterward
FailedThe task did not finishOpen the error or check logs
CancelledYou or the system cancelled itRestart it if needed
File unavailableThe file or remote resource is missingCheck path, disk, remote source

Find the entry by goal:

GoalGo to
Import local songsImport Folder
Find a songSongs
Listen by albumAlbums
See new songsInbox
Line up songs temporarilyQueue
Build a long-term playlistPlaylists
Adjust sound outputSettings -> Playback
Adjust EQSettings -> EQ / DSP
Adjust lyricsSettings -> Lyrics or Lyrics
Attach a local videoLyrics guide
Download musicNot provided. See Download And Plugin Source Boundaries
Connect a remote libraryRemote Library
Change the themeSettings -> Appearance
View logsSettings -> About or the diagnostics entries
Do a risky repairSettings -> Danger Zone, after backing up
FeatureWhy be careful
Delete songsMay affect real files or library records
Rebuild databaseAffects the library index, scan state, and local records
Clear cachesCovers and temp files may need regenerating
High-risk plugin permissionsPlugins may change settings, use the network, write the library
Change proxyAffects lyrics, covers, and network metadata
Switch output to exclusive or ASIODevice or driver issues can cause silence or failure
Bulk tag editsMistakes scramble albums, artists, and search all at once
Full remote indexLarge remote libraries can run for a very long time and eat bandwidth

The safe pattern:

  1. Try a small scope first.
  2. Understand what will be affected.
  3. Back up when you can.
  4. When unsure, do not press the dangerous button.
  5. On problems, revert the last step; do not keep changing things.
  1. Songs.
  2. Search the title.
  3. Find the track.
  4. Double-click or press play.
  5. Watch the bottom player.
  6. Sound means done.
  1. Albums.
  2. Search the album title.
  3. Open the album.
  4. Check the track order.
  5. Press play album, or right-click the album and choose play.
  1. Songs.
  2. Select the tracks.
  3. Right-click.
  4. Choose “Play next” or “Add to queue”.
  5. Check the order in Queue.
  1. Songs.
  2. Find the track.
  3. Right-click.
  4. Choose add to playlist.
  5. Pick the playlist.
  6. Check in Playlists.
  1. Songs.
  2. Find the track.
  3. Right-click.
  4. Choose edit tags.
  5. Change the title.
  6. Save.
  7. Search the new title to confirm.
  1. Albums.
  2. Find the split album.
  3. Note which tracks belong together.
  4. Back to Songs.
  5. Find those tracks.
  6. Edit tags.
  7. Unify the album name and album artist.
  8. Save.
  9. Back to Albums to confirm the merge.
  1. Plug in the headphones, speakers, or DAC.
  2. Confirm the system recognizes the device.
  3. Open Settings -> Playback.
  4. Find the output device.
  5. Choose the target device.
  6. Test with System or shared output first.
  7. Play one song.
  8. Only after that consider exclusive output or ASIO.
  1. Open Settings -> Playback.
  2. Find ReplayGain.
  3. Enable loudness processing.
  4. Play tracks from several albums to test.
  5. If you want bit-perfect, turn ReplayGain off instead.
  1. Play the song.
  2. Open Lyrics.
  3. Decide whether the lyrics are early or late.
  4. Open the lyrics settings.
  5. Adjust the time offset.
  6. Nudge a little, then play to check; do not make big jumps.
  7. After saving, listen to a chorus to confirm.

Official platform MV search is not maintained. If you have a local video or your own URL:

  1. Play the corresponding song first.
  2. Attach it following “Video you attach yourself” in the Lyrics guide.
  3. Confirm the video and audio are the same version.
  4. Do not expect millisecond alignment.

ECHO NEXT is not a bare file opener. It is closer to a local music management system, built from a few layers:

ConceptMeaning
Local filesThe real audio files on your disk: FLAC, MP3, WAV, M4A
LibraryThe catalog the app builds from folders; songs stay on their original disk
TagsThe title, artist, album, year, and track number written inside the file
Cover cacheSmall images for lists and the album wall — your originals are not deleted
QueueTonight’s temporary order
PlaylistA set of songs you keep coming back to
Remote sourceYour own NAS, Jellyfin, Navidrome, or similar service
Network metadataCover or info candidates from the internet — for filling gaps only
Audio outputWhich device the sound goes to and how
PluginsSmall local tools whose permissions you review before enabling

ECHO NEXT centers on the local library. Remote libraries, network metadata, and plugins are extensions. They serve the local listening experience; they do not turn the player into a shell for third-party streaming platforms.

Playback stability beats feature count. Scanning, cover generation, remote completion, plugins, and diagnostic windows must not preempt the playback chain.

If EQ or loudness processing is on, the app will not pretend the sound is untouched. Covers and lyrics found online are candidates only; the tags you edited by hand are more trustworthy.

Do not import your full library the first time. The steadier route:

  1. Prepare a small folder with 10 to 50 tracks in common formats.
  2. Open ECHO NEXT.
  3. Import that folder with Import Folder.
  4. Check the new tracks in Inbox.
  5. Search, sort, and play a few songs in Songs.
  6. Check album grouping and covers in Albums.
  7. Open Lyrics and confirm familiar songs roughly line up.
  8. Open Settings -> Playback and confirm the output device.
  9. Only if all of this works, import the full library.

The benefit: if scanning, playback, covers, output, or lyrics is broken, you can see it within a dozen songs, instead of drowning in tens of thousands of tracks and a pile of background tasks.

Not recommendedWhy
Importing a directory with hundreds of thousands of files at onceThe first scan is slow and problems are hard to locate
Enabling remote libraries, plugins, and network completion togetherStacked background chains hide the real cause
Scanning a full library from an unstable external driveProduces missing, inaccessible, and failed-scan states
Declaring the app broken over inaccurate lyricsAutomatic matching depends on tags and online candidates; some error is inherent
Rebuilding the database over playback issuesMost playback problems never involve the database
PageMain purposeMost common actions
Import FolderImport local music foldersPick a directory and start the scan
FoldersManage import rootsCheck scan state, maintain directories
InboxView newly scanned tracksInspect new imports
SongsThe main library listSearch, sort, play, right-click, edit tags
AlbumsAlbum wall and detailsPlay by album, check covers, organize albums
ArtistsBrowse by artistCheck artist grouping
QueueCurrent playback queueAdjust the temporary order
LikedLiked songsQuick access to favorites
HistoryPlayback historyRecover what you just played
PlaylistsPlaylistsManage long-term sets
LyricsImmersive lyrics pageRead lyrics, adjust offset, view helper text
Remote LibraryRemote sourcesAdd WebDAV, Jellyfin, Subsonic, and more
LAN PlaybackLocal-network playbackDiscover and connect DLNA, AirPlay devices
PluginsPlugin managementEnable, disable, review permissions and logs
SettingsGlobal settingsPlayback, lyrics, MV, EQ, appearance, library, danger zone

The local library is the core of ECHO NEXT. The better its quality, the more reliable search, the album wall, lyric matching, MV matching, playlists, and statistics become.

Recommended structure:

Music/
Artist/
2024 - Album Name/
01 - Track.flac
02 - Track.flac
cover.jpg

Not mandatory, but a stable structure cuts future cleanup cost.

Suggestions:

  1. Keep one album per folder where possible.
  2. Keep album name and album artist consistent within an album.
  3. Fill in disc and track numbers for multi-disc albums.
  4. Do not use a temp download folder as your long-term library.
  5. Keep external drive and NAS paths stable.
  6. Filenames help you recognize files, but do not rely on filenames alone.

The project’s file associations cover many formats. Common ones:

TypeExamples
LosslessFLAC, WAV, ALAC, AIFF, APE, WavPack
LossyMP3, AAC, M4A, OGG, Opus, WMA
DSDDSF, DFF
Video or containersMKV, MP4, MOV, WebM, MKA
OtherMPC, TAK, TTA, CAF, DTS, CUE

Whether a file plays smoothly depends on the decoder, the file itself, the container, and the current audio chain.

You can import through:

  1. The sidebar Import Folder.
  2. The add entry on the Folders page.
  3. The folder management area in Settings -> Library.

After importing a folder, ECHO NEXT will:

  1. Record the root directory.
  2. Scan it in the background.
  3. Find the audio files.
  4. Read embedded tags.
  5. Read or extract covers.
  6. Write to the library database.
  7. Group albums and artists.
  8. Refresh Songs, Albums, Artists, Inbox, and other pages.

A scan may pass through these stages:

StageMeaning
QueuedWaiting for the scan task to start
Discovering filesWalking directories to find audio files
Checking incremental cacheDeciding which files are unchanged
Reading metadataReading title, artist, album, duration, and more
Extracting coversReading embedded or folder covers
Organizing albumsGrouping albums and ordering tracks
Writing databaseSaving results
DoneThis round finished
Failed / CancelledThis round did not finish

If your library is large:

  1. Keep the disk online during the first scan.
  2. Do not run mass downloads, remote sync, and plugin batch jobs at the same time.
  3. Browsing during the scan is fine, but avoid rapidly switching wide filters.
  4. If the scan fails, look at the failing path first; do not jump to rebuilding the database.
  5. Later scans reuse unchanged files and are usually faster than the first.

Folders manages import roots.

  1. Seeing which music folders are added.
  2. Adding new roots.
  3. Checking whether a directory is still accessible.
  4. Triggering or watching scans.
  5. Spotting directories that may be failing.
SymptomLikely causeSuggestion
Folder suddenly unavailableExternal drive offline, drive letter changed, permissions changedRestore the path first; do not rush to delete
Slow scanFirst scan, many covers, many lossless filesWait it out; avoid running heavy jobs alongside
New files not appearingNo rescan yet, odd format, path outside the rootRefresh manually or check the directory
Duplicate songsBoth a parent and its subdirectory were addedKeep one root

Inbox is the checkpoint for new content.

  1. Just downloaded a batch of songs.
  2. Just copied in an album.
  3. Just imported a new folder.
  4. Quickly screening whether new tracks are healthy.
CheckLook for
TitleThe real song title, not a garbled filename
ArtistConsistent
AlbumGrouped into the right album
CoverThe right cover shows
DurationNot 0 or obviously wrong
PlaybackPlays normally
FormatMatches what you expected

If new content is low quality, fix the source file tags first, then re-read or rescan.

Songs is the most important daily page. Finding, playing, organizing, and diagnosing mostly run through here.

Search is good for:

  1. Song titles.
  2. Artists.
  3. Albums.
  4. Version keywords.

Suggestions:

  1. In a large library, search first; do not rely on scrolling.
  2. If search misses, check the tags — not just the filename.
  3. Empty artist or album fields degrade search results.
SortGood for
DefaultEveryday browsing
Created time asc / descFinding new or old imports
Title A-Z / Z-AOrganizing by title
Duration short-to-long / long-to-shortFinding oddly short audio, long audio, single-track rips
File modified old-to-new / new-to-oldFinding recently changed files
Quality / sizeFinding high-spec or suspiciously small files
Most playedFinding your frequent plays
RandomShuffled browsing
By artistChecking artist grouping
By albumChecking album fields
Recently updatedSeeing recent scan changes

Switching between local and remote sources

Section titled “Switching between local and remote sources”

The songs page can switch between the local library and remote sources. The difference:

SourceCan doLimits
LocalPlay, edit tags, open folder, copy path, delete, cover actionsDepends on the local file existing
RemoteBrowse, play, queue, like, add to playlistMay not support tag editing or local paths

Missing right-click actions on remote songs are a normal boundary.

Multi-select is good for:

  1. Batch add to queue.
  2. Batch add to playlists.
  3. Batch like.
  4. Batch remove from queue.

Do not run high-risk changes on a huge selection at once. Deleting, tag writing, and tag re-reading are best done in confirmed batches.

The duplicate filter is good for cleaning:

  1. The same file copied multiple times.
  2. The same song at different bitrates.
  3. The same album imported twice.
  4. Downloads folder overlapping the real library.

But these are often not duplicates:

  1. Live versions.
  2. Remasters.
  3. Radio edits.
  4. Instrumentals.
  5. Covers.
  6. Different language versions.
  7. Album and single versions.

Before deleting, compare at least the path, duration, bitrate, album, and file size.

Common actions on local songs:

ActionMeaningRisk
Add to playlistSave to a long-term playlistLow
Play nextInsert after the current trackLow
Add to queueAppend to the queueLow
Like / unlikeToggle favoriteLow
Edit tagsChange library or file tagsMedium
Re-read embedded tagsRefresh the record from file tagsMedium
Open osu! timingView or adjust timingLow to medium
Jump to albumOpen the album detailLow
Show in folderOpen the system folderLow
Copy pathCopy the local pathLow
Open with systemHand to the system default appLow
Copy title and artistFor searching or sharingLow
Copy / save coverExport the coverLow
Delete songDelete or remove the songHigh

Tag edits change library display and, in some cases, write back to file tags.

Suggested field rules:

FieldSuggestion
TitleThe song title only; do not stuff the artist in
ArtistThe performers or main artist
AlbumConsistent across the album
Album artistUnified across the album
YearThe release year; do not mix in date strings
Track numberA number
Disc numberSet for multi-disc albums
GenreRough is fine; do not fragment it
ProblemCheck first
Song not foundFolder imported? Scan finished? Tags empty?
Garbled titleSource tag encoding or filename origin
Split albumAlbum name / album artist consistency
Cover missingFile has a cover? Folder has cover/front image? Cache generated?
Playback failsFile exists? Format decodable? Output device healthy?
Right-click options missingRemote song? Unsupported context?

Albums is the main album browser.

  1. Listening by album.
  2. Checking covers.
  3. Organizing multi-disc albums.
  4. Checking whether same-named albums merged wrongly.
  5. Finding albums with missing covers.
  6. Queuing or playlisting a whole album.

The album page sorts by title, artist, created time, duration, file modified time, recently updated, random, and more. Common uses:

GoalSort
Find recently added albumsCreated desc or recently updated
Check titlesTitle
Check artistsArtist
Pick one at randomRandom
Find odd albumsDuration

Inside an album, check:

  1. Track order.
  2. Disc numbers.
  3. Complete track numbers.
  4. The cover.
  5. Artist and album artist as expected.
ActionPurpose
Play albumPlay the whole album from the start
Add to playlistSave to a long-term playlist
Add to queueAdd to the temporary order
Like albumMark a favorite album
Edit tagsFix album-level info
Copy album infoCopy title, artist, and so on
Copy / save coverHandle the cover
Delete albumHigh risk; be careful
SymptomLikely causeFix
One album split into severalInconsistent album name or album artistUnify tags and re-read
Multiple albums merged into oneSame title, missing album artistFill in the album artist
Wrong track orderMissing track or disc numbersFill them in
Wrong coverOne track embeds a different imageUnify embedded or folder covers
Wrong yearMessy year tagsFix year

Artists is for checking artist grouping.

Common reasons artists split:

  1. Aimer vs aimer.
  2. YOASOBI vs Yoasobi.
  3. Artist feat. B vs Artist / B.
  4. Mixed native and English names.
  5. Leading or trailing spaces.
  6. Different punctuation.

Decide on a naming rule first, then organize tags in bulk.

The queue is the temporary playback order.

  1. Today’s spur-of-the-moment batch.
  2. Temporarily lining up search results.
  3. Testing formats or sample rates.
  4. Quickly inserting the next track.
  1. Long-term collections.
  2. Themed playlists.
  3. Lists that need cross-device or long-term upkeep.

Long-term content belongs in Playlists.

  1. Temporary listening: queue.
  2. Confirmed keepers: playlist.
  3. Testing audio gear: build a dedicated playlist instead of re-queuing every time.

Liked is the quick favorite.

Good for:

  1. Marking frequent plays.
  2. Collecting songs you like on the fly.
  3. Starting playback from favorites quickly.

Not good for:

  1. Complex categorization.
  2. Multi-theme organization.
  3. Album-level structure.

Complex organization belongs in playlists.

History records what you played.

Good for:

  1. Recovering a song you forgot to like.
  2. Reviewing recent playback order.
  3. Checking whether one song keeps failing.
  4. Confirming whether playback really advanced to the next track.

Playlists are for long-term organization.

  1. Daily picks.
  2. Night listening.
  3. Work background.
  4. Headphone test.
  5. Speaker test.
  6. Hi-res test.
  7. New-album candidates.
  8. Car sync.
  9. Local lossless picks.
  10. One artist’s best.
FeatureFor
QueueTemporary playback order
PlaylistLong-term saving and organizing
LikedQuick favorite marking
HistoryRecovering play records

The bottom player is the global control area.

  1. Play / pause.
  2. Previous / next.
  3. Progress bar.
  4. Volume.
  5. Current title, artist, and cover.
  6. Queue entry.
  7. Lyrics entry.
  8. MV entry.
  9. Output or status hints.
SymptomCheck first
Play pressed, no soundSystem volume, app volume, output device
Progress does not moveFile decodable? Audio host started?
Skips to next immediatelyCorrupt file? Early end? Decode error?
Progress jumps aroundOutput mode, device, playback diagnostics
Slow track changesScanning, downloading, remote completion, or plugin jobs running?
Some files will not playFormat, container, corruption, FFmpeg support

Do not rebuild the database at the first playback problem. The playback chain and the database are different things.

The lyrics experience covers display, matching, translation, romanization, kana enhancement, offset, and styling.

Lyrics may come from:

  1. Local LRC files.
  2. Embedded lyrics.
  3. Online candidates.
  4. Manually chosen candidates.
  5. Enhancement sources, such as Japanese kana or reading aids.

Common ones:

SettingPurpose
Lyric sourcesWhere lyrics are searched
Time offsetFix uniform earliness or lateness
FontLyric typeface
Font sizeReading size
Line width limitPrevent long lines from overflowing
TranslationShow helper translation
RomanizationReading aid for Japanese and other languages
Kana enhancementShow kana or reading hints when available
Readability enhancementKeep lyrics readable over busy backgrounds
CaseFix
Everything is late by the same amountAdjust the offset in the matching direction
A few lines are offThe lyric file’s own timeline is weak
Matched a different songPick a candidate manually
A live version will not line upFind live-version lyrics or adjust manually
Translation does not pair with the originalSource data quality issue

Kana and romanization are helper text; they must not replace the main lyric timeline. Good for:

  1. Learning Japanese.
  2. Reading unfamiliar characters.
  3. Singing along.
  4. Comprehension.

If an enhancement source is poor, hide it rather than let it degrade the main lyrics.

The official product does not maintain platform MV search. If an old entry is still visible in the UI, do not treat it as “click here for the official video”.

When you attach a local video or URL:

  1. Confirm the video and the current audio are the same version.
  2. If versions differ, changing the video beats endless sync tuning.
  3. Do not confuse picture problems with silence or a broken library.

Full steps in the Lyrics guide.

Audio output is a focus of ECHO NEXT — and also the part most influenced by your hardware environment.

ModeMeaningGood for
SystemSystem default outputRegular users, quick diagnosis
WASAPI SharedWindows shared outputStable daily playback
WASAPI ExclusiveExclusive device accessMore direct device output
ASIOProfessional sound-card chainSound cards, recording gear, low latency
DirectSoundCompatibility outputOdd devices or diagnosis
  1. Unsure? Start with System.
  2. Stable daily playback: WASAPI Shared.
  3. Testing exclusive output: WASAPI Exclusive next.
  4. Professional sound card: then ASIO.
  5. On any problem, return to System or shared output first.

bit-perfect means the app barely changed the sound in the original file. These usually break it:

  1. EQ.
  2. Preamp gain.
  3. ReplayGain.
  4. Speed change.
  5. Resampling.
  6. System mixing.
  7. Some device driver processing.

Do not force EQ and loudness off just to keep a pretty label on screen. If you want it to sound better or more even, accept that the signal is processed.

Sample rate state may involve:

  1. The file’s sample rate.
  2. The decoder’s output rate.
  3. The requested output rate.
  4. The device’s actual rate.
  5. The shared-mode device rate.

Differences between these values are not automatically bugs. Shared output, system mixing, and device limits all shape the real result.

The equalizer shapes the sound. Once it is on, the sound is processed: bass, vocals, volume, and speed may all change. The app states this clearly instead of pretending the file is still passing through untouched.

The simple rule: with EQ, loudness normalization, speed change, or any other processing on, output is no longer a raw file dump. To verify the raw sound, turn them all off and return to System output — or a WASAPI / ASIO path you already confirmed stable.

  1. Start from a flat or default preset.
  2. Adjust in small steps.
  3. Lower the preamp gain when boosting bands.
  4. Do not boost all bands together.
  5. Save a preset per device.
BandRough effect
LowDrums, bass, body
Low-midWarmth and fullness; also mud
MidVocals, guitar, the core
High-midClarity and sibilance
HighAir and brightness; also harshness
ProblemFix
Sound clips or breaksLower the preamp gain
Bass boomsReduce low or low-mid
Vocals recessedSlightly boost mids
Sound is harshReduce high-mid or high
Verify raw outputTurn off EQ and preamp gain

ReplayGain evens out loudness across songs.

Good for:

  1. Shuffling across albums.
  2. Mixing music from different eras.
  3. Libraries from many sources.
  4. Night listening without loudness jumps.

Not for:

  1. bit-perfect verification.
  2. Preserving an album’s original loudness relationships.
  3. Professional comparison tests.

Playback speed suits special cases: podcasts, practice, Nightcore / Daycore.

Note:

  1. Speed change alters the audio processing chain.
  2. Output at changed speed is not bit-perfect.
  3. On playback problems, restore normal speed before diagnosing.

Remote sources access music that is not on the local disk.

TypeGood for
WebDAV / AListCloud drives, AList, WebDAV-capable services
JellyfinSelf-hosted media server
EmbySelf-hosted media server
NAS / SMBLAN shares
SSHFSSSH file systems
Subsonic / NavidromeMusic servers

The usual flow:

  1. Open Remote Library.
  2. Choose the source type.
  3. Fill in a display name.
  4. Fill in the server URL.
  5. Fill in the account and password or token.
  6. Choose a sync mode.
  7. Test the connection.
  8. Save.
  9. Start indexing when needed.
ModeMeaningSuggestion
Browse onlyNothing written to the library indexTemporary access
Build indexRemote tracks indexed; streams fetched at play timeRecommended
Mirror cacheA future extension; does not copy the library by defaultCareful

Remote sources can spawn background tasks:

  1. Metadata.
  2. Covers.
  3. Lyrics.
  4. MV.
  5. Duration backfill.

These should run at low priority and must not steal resources during playback.

SymptomCheck
Connection failsURL, account, password, certificate, proxy, firewall
Slow scanServer speed, network, file count
Stuttering playbackBandwidth, server response, running background tasks
Covers missingRemote cover permissions, cache, background tasks
Missing filesRemote path changes, server index changes

LAN Playback covers DLNA, AirPlay, and other local-network discovery and playback.

  1. The computer and the target device are on the same LAN.
  2. The router does not isolate devices.
  3. The firewall allows the traffic.
  4. Security software is not blocking it.
  5. On multi-NIC machines, the right network is selected.

Possible causes:

  1. The device is on a different network.
  2. AP isolation is on at the router.
  3. Windows Firewall is blocking.
  4. The device’s service is not running.
  5. Broadcasts went out the wrong interface on a multi-NIC machine.

Fix order:

  1. Restart the casting service on the target device.
  2. Confirm the network.
  3. Check the firewall.
  4. Refresh ECHO NEXT.
  5. Restart the app if needed.

Plugins are a controlled extension capability, not a backdoor for running arbitrary scripts.

Plugins usually live under plugins/ in the user data directory. Each plugin is its own folder with a manifest, scripts, and an optional panel.

Typical structure:

plugins/
echo.example/
echo.plugin.json
plugin.js
panel.html
plugin-storage.json
  1. Open Plugins.
  2. Create the sample plugin or import a plugin package.
  3. Refresh the plugin list.
  4. Review the plugin’s permissions.
  5. Enable only if you trust it.
  6. Check the plugin logs on errors.
  7. Reload after editing plugin files.
TypeMeaning
Playback status panelListens to playback state and shows a small panel
Command toolRegisters manually triggered commands
Library scriptReads library summaries for light organization
Custom sourceReturns search candidates and resolves explicit audio URLs at play time
PermissionCapabilityRisk
playback:readRead playback stateLow
playback:controlPlay, pause, seekMedium
library:readPaginated reads of public library fieldsMedium
library:writeReserved library write capabilityHigh
sources:provideProvide custom source candidates and playback URLsMedium
settings:readRead a settings snapshotMedium
settings:writeWrite settingsHigh
networkExternal network accessHigh
fs:pluginRead and write plugin-directory dataMedium
  1. Do not enable high-permission plugins from unknown sources.
  2. Do not let plugins run heavy synchronous computation.
  3. Do not let plugins scan the whole library.
  4. When a plugin errors, disable first, then read logs.
  5. Settings writes and library writes are high-risk permissions.
  6. Custom sources should only return legal http / https audio URLs — never bypass platform authorization or touch the local file system.

After enabling a custom source plugin, pick that source inside the search entry the plugin declares. ECHO only calls the plugin during search and playback resolution; playback still runs through the host’s own chain once it has an explicit audio URL.

Plugin v2 additionally supports a controlled network API, lyric providers, cover providers, and plugin-owned settings. Network access requires the network permission and only goes through the host-wrapped echo.net.fetchJson/fetchText. Lyrics, covers, and sources return candidates only; ECHO decides whether to apply or play them. Plugin package imports record checksums, and overwriting an existing plugin keeps a backup of the old directory.

The settings page is large; think of it by module. The full per-setting walkthrough is in the Settings guide.

Common content:

  1. Language.
  2. Window behavior.
  3. Tray behavior.
  4. Settings backup.
  5. Automatic backup.

Enable automatic backup, especially if you often adjust settings, plugins, remote sources, or audio output.

Manages:

  1. Output device.
  2. Output mode.
  3. Audio status.
  4. HQPlayer settings.
  5. Playback speed.
  6. ReplayGain.
  7. Current playback diagnostics.

Two kinds:

TypeMeaning
In-app shortcutsActive while ECHO NEXT is focused
Global shortcutsMay work while ECHO NEXT is unfocused

Common actions:

  1. Play / pause.
  2. Previous.
  3. Next.
  4. Stop.
  5. Volume up / down.
  6. Seek back / forward.
  7. Show main window.
  8. Boss key.
  9. Speed adjustment.
  10. Open audio, MV, or lyric settings.

Global shortcuts can conflict with the system or other apps. If recording fails, pick another combination.

Lyric settings manage:

  1. Lyric sources.
  2. Time offset.
  3. Fonts.
  4. Helper text.
  5. Kana enhancement.
  6. Readability.

If picture or legacy MV entries remain in settings, read them as “video you attach yourself”, never as platform search. Details in the Lyrics guide.

Integration capabilities may include:

  1. Last.fm.
  2. Discord Presence.
  3. Network proxy.
  4. Auto update.

Proxy modes are usually:

ModeMeaning
OffNo proxy
System proxyFollow the system setting
Manual proxyA hand-entered proxy address
PACA PAC configuration

The proxy affects online lyrics, covers, and metadata. Playing local files usually needs no proxy.

EQ settings manage:

  1. The on/off switch.
  2. 10-band adjustment.
  3. Preamp gain.
  4. Built-in presets.
  5. User presets.
  6. Save, import, restore.

Appearance settings manage:

  1. Theme.
  2. Custom colors.
  3. Fonts.
  4. Wallpaper.
  5. Video backgrounds.
  6. Motion.
  7. Corner radius, opacity, blur, and other visual parameters.

Suggestions:

  1. Make text readable first.
  2. Then tune decoration.
  3. Video backgrounds must not affect playback stability.
  4. Treat UI fonts and lyric fonts separately.

Library settings manage:

  1. Local folders.
  2. Network metadata.
  3. Library quality.
  4. Duplicate songs.
  5. ReplayGain analysis.
  6. BPM analysis.
  7. Artist image cache.
  8. Database protection.

Be careful with anything touching the database, caches, or scanning.

Usually contains:

  1. App version.
  2. Project links.
  3. Logs.
  4. Diagnostics.
  5. Crash information.

Before reporting a problem, check here for exportable diagnostics.

The danger zone may contain:

  1. Rebuild database.
  2. Repair database.
  3. Delete database.
  4. Clear caches.
  5. Restore default settings.
  6. Database snapshots and restore.

Two kinds of fonts:

TypeFocus
App UI fontReadability, stable layout
Lyric fontLooks, immersion, stage feel

Do not make the whole app UI hard to read for the sake of lyric styling.

Wallpaper and video backgrounds add atmosphere, but:

  1. Video backgrounds consume rendering resources.
  2. Overhead should drop when minimized or hidden.
  3. On playback stutter, turn off the video background first.
  4. Skip heavy video backgrounds on low-end machines.

Network metadata is completion, not truth.

Suggested priority:

  1. Manual edits.
  2. Embedded tags.
  3. Sidecar or folder information.
  4. Network candidates.
  5. Filename fallback matching.

Network metadata is good for:

  1. Missing titles.
  2. Missing artists.
  3. Missing albums.
  4. Missing years.
  5. Missing covers.

Not for:

  1. Overwriting fields you organized by hand.
  2. Overwriting high-confidence embedded tags.
  3. Blindly bulk-applying low-score candidates.

Worth backing up:

  1. Settings.
  2. The library database.
  3. The plugin directory.
  4. Important playlists.
  5. Music-file tags you spent time organizing.

Before any high-risk operation, confirm at least:

  1. What is affected.
  2. Whether files get deleted.
  3. Whether only caches are touched.
  4. Whether it can be undone.
  5. Whether a backup exists.
  1. Check the system volume.
  2. Check ECHO NEXT’s volume.
  3. Check the output device.
  4. Switch back to System output.
  5. Try a known-good MP3 or FLAC.
  6. Turn off EQ, ReplayGain, and speed change.
  7. Check the audio status and logs.
  1. Play the same file in another player.
  2. Check for corruption.
  3. Check for an unusual format.
  4. Check whether only this file fails.
  5. Look for decode errors in the logs.
  6. Re-import or re-read tags if needed.
  1. Check the source file tags.
  2. Check whether the scan finished.
  3. Check for duplicate directories.
  4. Check whether network metadata overwrote expected fields.
  5. Re-read embedded tags.
  6. Do not clear the database as a first step.
  1. Check the file’s embedded cover.
  2. Check the folder cover.
  3. Check that every track in the album embeds the same image.
  4. Confirm the impact before clearing or refreshing the cover cache.
  1. Check for a wrong-version match.
  2. Pick a candidate manually.
  3. Adjust the time offset.
  4. Fix the song title and artist.
  5. Check for live versions, covers, or edits.
  1. Confirm the video and audio are the same version.
  2. Swap the attached video — it beats endless sync tuning.
  3. Do not confuse it with output or library corruption.
  1. Check the URL.
  2. Check the account and password.
  3. Check the certificate.
  4. Check the proxy.
  5. Check the server logs.
  6. Check the firewall.

An effective report contains:

  1. The ECHO NEXT version.
  2. The operating system version.
  3. Installed, portable, or dev mode.
  4. The page where the problem happened.
  5. Reproduction steps.
  6. Expected behavior.
  7. Actual behavior.
  8. Screenshots.
  9. Logs or a diagnostic report.
  10. For playback issues: output mode, device, audio format, and whether only some files are affected.
  11. For scan issues: folder type, local or remote disk, and the failing path.
  12. For network issues: proxy mode, source type, and the server’s response.

“Doesn’t work”, “not great”, or “it froze” alone is hard to fix. The closer your report is to the real chain of actions, the faster the cause is found.