Lyrics And MV Matching
Lyrics and MV lookup are candidate-matching features. ECHO NEXT uses the current track title, artist, album, duration, tags, and online sources to find likely results, then tries to pick a good candidate.
The goal is convenience, not perfect certainty. When lyrics or MV results are wrong, out of sync, or unavailable, inspect the candidate and diagnostics first. Do not treat every mismatch as a broken library, audio output, or player.
Why Matching Cannot Be 100%
Section titled “Why Matching Cannot Be 100%”There is no universal source of truth for every track version. The same song may exist as:
| Case | Result |
|---|---|
| Original, live, edit, remix, instrumental | The timeline and MV may differ completely |
| Single version and album version | Lyrics may drift over time |
| Titles with feat., with, translated names, romanization, aliases | Search can return mixed candidates |
| Non-standard video titles | MV results can include fan edits, stages, clips, or reuploads |
| Recompressed or trimmed uploads | Video and local audio will not naturally align |
| Changing platform result order | Today’s first candidate may not stay the same |
Automatic matching can save time, but it cannot replace judging the exact version.
Lyrics Matching
Section titled “Lyrics Matching”Recommended confidence order:
- Local LRC or lyrics you saved yourself.
- Embedded lyrics.
- Online lyrics candidates.
- Manually selected candidates.
- Per-track offset or manual correction.
When lyrics are wrong, classify the problem first:
| Symptom | Likely Cause | First Step |
|---|---|---|
| Completely different song | Wrong candidate | Pick another candidate |
| Whole song is early or late | Candidate has a global offset | Adjust per-track offset |
| Starts right, drifts later | Different version or duration | Use lyrics for the same version |
| Only a few lines are wrong | Poor lyric timeline quality | Pick another candidate or edit manually |
| Translation does not align | Translation and main lyrics differ | Disable translation or pick another candidate |
Do not use the global offset to fix one song. Global offset is only for cases where every song is consistently early or late on your setup.
Why MV Matching Is Harder
Section titled “Why MV Matching Is Harder”MV matching is even less likely to be perfect, especially when the MV source is Bilibili.
Bilibili is a video platform, not a one-to-one official MV database for your local audio files. A result may be an official MV, live stage, subtitled upload, fan edit, clip, reupload, interpolated version, recompressed version, concert segment, or regional version. The video title, description, tags, uploader, and view count are clues, not proof that the video is the exact MV for the audio file you are playing.
Also, the audio inside a Bilibili video is usually not the same file ECHO is playing locally. Even if it is the same song, it can contain:
- Intro cards, outro cards, black frames, or subtitles.
- Trimmed intros or endings.
- Recompressed audio.
- Live audio instead of studio audio.
- MV and album versions with different durations.
- Display delay from frame rate, browser decoding, or buffering.
For that reason, MV cannot promise exact audio sync. ECHO NEXT can find candidates, try alignment, restart audio when requested, and accept custom URLs, but it cannot turn a third-party video source into an official millisecond-synced asset for your local audio.
When The MV Is Wrong
Section titled “When The MV Is Wrong”Use this order:
- Check candidate title, uploader, duration, and visible content.
- Prefer the official MV or the closest official-looking version.
- If the automatic result is wrong, pick another candidate manually.
- If you already know the correct video, use a custom URL.
- If the audio and video are different versions, changing video is better than tuning sync.
- If the issue is a small whole-video offset, try sync settings.
- If mismatches are frequent, raise the auto-match threshold.
Do not treat MV mismatch as an audio-output problem. If audio playback is fine and lyrics work, focus on candidates, source, version, and video state.
When MV Will Not Open
Section titled “When MV Will Not Open”MV playback depends on network access, platform availability, account or cookie state, stream parsing, browser decoding, and rendering. Any of those can cause black video, failed loading, no visible frame, or external-player-only behavior.
Check:
- Whether your network can access the platform.
- Whether proxy settings affect Bilibili, YouTube, or other sources.
- Whether account login or cookies expired.
- Whether the video requires login, region access, paid access, or passes platform risk checks.
- Whether the chosen quality is too demanding, such as HEVC, HDR, Dolby Vision, or 4K 60fps.
- Whether immersive MV background, video wallpaper, or real-time effects are too heavy.
- Whether an external player can open the same URL.
If MV does not open, stays black, fails to load, plays audio without visible video, or has candidates but cannot play them, enable MV diagnostics report. It generates a copyable local Markdown report with MV state, candidates, source information, error clues, and page visibility details.
When reporting the issue, include the MV diagnostics report, a screenshot, ECHO NEXT version, operating system version, current track, and the video URL or candidate title. Saying only “MV does not open” is usually not enough to tell whether the cause is network, platform, login, encoding, candidate selection, or rendering.
Suggested Settings
Section titled “Suggested Settings”| Goal | Suggestion |
|---|---|
| Reduce wrong matches | Raise the MV auto-match threshold |
| Slow network or UI lag | Disable MV auto-preload and lower max quality |
| Video stutters | Disable 60fps and test 720p or 1080p first |
| Lyrics are hard to read over video | Enable MV lyrics readability or darken the background |
| Candidates are often not official MVs | Pick candidates manually or use a custom URL |
| Debug video not opening | Enable MV diagnostics report and copy the report |
What Not To Do First
Section titled “What Not To Do First”These usually do not fix lyrics or MV issues and can make debugging harder:
- Do not delete the database first.
- Do not clear the whole library.
- Do not keep switching audio output modes.
- Do not change proxy, account, quality, source order, and sync mode all at once.
- Do not send only a black-screen screenshot without the diagnostics report.
Keep the current track, candidate, settings, and diagnostics report available. That gives enough context to see where the chain failed.