AIMP CUE Sheet Wrong Encoding: How to Fix It

When AIMP shows garbled track titles, question marks, empty entries, or one unsplit album instead of the tracks described by a CUE sheet, the problem is often the CUE file's text encoding. This is especially common with Cyrillic, Japanese, Chinese, accented European characters, and CUE sheets created on an older Windows installation. The safest fix is usually to test a copy of the CUE file, convert that copy to UTF-8, confirm its FILE line still matches the audio filename, and then re-add it to AIMP. On Android, UTF-8 is the practical requirement to use for CUE text. Stop troubleshooting as soon as the corrected copy displays the expected artist and track names because audio output settings, codec packs, skins, and device controls normally cannot repair incorrectly decoded text.

1. Confirm the Symptom With a Small Safe Test

Before editing your library, determine whether you have an encoding problem or a different CUE problem. Encoding errors affect text interpretation. They do not normally change the sound stored inside the FLAC, WAV, APE, MP3, or other referenced audio file.

1.1 Recognize the Typical Encoding Symptoms

An AIMP CUE sheet wrong encoding problem commonly produces one or more of these results:

• Non-English artist and track titles become strings such as Ã, Ð, À, or other unrelated characters.
• Some titles display correctly while Cyrillic, Asian, or accented characters do not.
• AIMP loads the underlying album image as one long track instead of splitting it.
• Opening the CUE produces empty entries or an error even though the audio file plays independently.
• The same album works on Windows but not on Android.
• English-only CUE sheets work while files containing another language fail.

If playback itself is clean and the error follows the text language, investigate encoding first. An output method, Bluetooth profile, audio device mode, or volume setting cannot turn a correctly decoded title into garbled text.

1.2 Make One Renamed Test Copy

Do not overwrite the original file immediately. Copy the CUE and its referenced audio file into a temporary folder. Give the CUE copy a clear name such as album-utf8-test.cue. If you rename the audio copy, update the CUE's FILE line so it contains the exact new filename.

Open the copied CUE in a plain-text editor. Windows Notepad is sufficient for a basic test. Editors that show the current encoding explicitly can make the diagnosis easier, but they are not required.

Look for lines similar to these:

PERFORMER "Artist Name"
TITLE "Album Name"
FILE "Album.flac" WAVE
TRACK 01 AUDIO
TITLE "Track Name"
INDEX 01 00:00:00

Save the copy as UTF-8, close the editor, and open it again. Confirm that all non-English characters remain readable. Add only this test CUE to a new temporary AIMP playlist.

Success looks like this: AIMP creates the expected track entries, displays readable titles, and plays each entry from the correct position. If that happens, stop changing AIMP settings. You have confirmed that the original CUE encoding was the cause.

2. Fix the CUE Text Encoding and File Reference

The main AIMP CUE sheet wrong encoding fix is to convert the text without altering the CUE structure. A CUE sheet is a text description containing metadata, track indexes, and a reference to the physical audio file. If either the character encoding or the referenced filename is wrong, parsing can fail.

2.1 Convert ANSI CUE Sheets to UTF-8

Older Windows programs often use the word ANSI for a locale-dependent legacy code page. ANSI is not one universal character set. A Russian Windows system may have produced text using Windows-1251, while a Western European system may have expected Windows-1252. Japanese text may use another legacy encoding. Moving the file between systems can therefore cause the same bytes to be interpreted as different characters.

Use this conservative conversion process:

1. Create a backup or work on the renamed copy.
2. Open the CUE in an editor that can choose the source encoding.
3. If the text is already garbled in the editor, reopen it using the likely original code page.
4. Confirm that the artist, album, filenames, and track titles become readable.
5. Choose Save As and select UTF-8.
6. Keep the .cue extension and plain-text format.
7. Close and reopen the saved file to verify the characters survived.

The source encoding must be interpreted correctly before conversion. Saving already garbled text as UTF-8 only preserves the corruption in a newer encoding.

2.2 Try UTF-8 Without BOM When Necessary

A byte order mark, commonly shortened to BOM, is an optional marker at the beginning of some UTF-8 files. Many programs handle it correctly. However, when a CUE parser rejects a UTF-8 file that otherwise looks valid, saving a test copy as UTF-8 without BOM is a reasonable compatibility check.

Do not repeatedly switch formats at random. Test standard UTF-8 first. If AIMP still rejects the sheet, save the same test copy as UTF-8 without BOM, re-add it, and compare the result.

Success looks like this: the first CUE command is recognized, the correct number of tracks appears, and the first title contains no stray symbols. Once this works, keep that encoding and stop modifying the file.

2.3 Verify the FILE Line Character for Character

An encoding conversion can fix titles while leaving a separate filename mismatch. Find the FILE line and compare the quoted value with the audio file's actual name. Check the extension, spaces, punctuation, brackets, apostrophes, and non-English characters.

For example, this reference:

FILE "Álbum Completo.flac" WAVE

must point to a file named exactly Álbum Completo.flac in the expected location. If the real file is named Album Completo.flac, correct the CUE or rename the test audio copy.

A useful isolation test is to rename the copied audio file to a short ASCII-only name such as test.flac, then change the copied CUE to:

FILE "test.flac" WAVE

If this works while the original non-English filename does not, encoding or filename interpretation remains involved. If it still fails, inspect the CUE syntax and file accessibility.

3. Refresh AIMP After Correcting the File

AIMP may retain playlist entries or music-library records created before the repair. Correcting the file on disk does not guarantee that an existing entry will be rebuilt immediately. Refresh the smallest relevant area instead of deleting your entire library.

3.1 Re-Add the CUE to a Fresh Playlist

Remove only the affected album entries from the current playlist. Create a temporary playlist and add the corrected CUE directly. Avoid adding the large audio file by itself during this test because doing so may intentionally create one long entry rather than the virtual tracks described by the sheet.

If the old playlist still shows garbled names but the new playlist is correct, the repaired CUE is working. Replace the stale entries with the newly parsed ones. There is no reason to reinstall AIMP.

3.2 Rescan the Relevant Music Library Location

If the playlist is correct but the music library still displays old text, rescan or update the folder containing the repaired album. If available in your setup, remove only the affected item from the library and scan that location again.

Remember that CUE metadata and audio-file tags can provide different values. A playlist generated from a CUE may show the CUE's TITLE and PERFORMER fields, while another library view may favor tags embedded in the FLAC or other audio file. Compare the same track in the playlist and file-information view before concluding that the encoding repair failed.

3.3 Check File Information and Tags Without Rewriting Everything

Use AIMP's file information or tag editor to identify the displayed metadata source. If the embedded tags are garbled too, they are a second issue and must be corrected separately. If embedded tags are readable but only the CUE-created entries are corrupt, keep your attention on the CUE.

Album artwork does not encode track-title text. A wrong cover, embedded image, or external folder image can be corrected independently, but changing artwork will not fix garbled CUE titles.

4. Check Android Storage Access and UTF-8 Compatibility

On Android, use UTF-8 for CUE sheets. Legacy Windows ANSI code pages are not a dependable interchange format for files moved to a phone or tablet. A CUE that happens to work on a Windows computer using a matching regional code page may fail or display incorrectly after transfer to Android.

4.1 Grant Access to the Whole Album Folder

AIMP needs to read both the audio image and its CUE sheet. Android storage restrictions can expose recognized audio files while hiding related text files. In AIMP's file browser, navigate to the album folder and grant full access through Android's folder picker when prompted. Choose the folder containing both files rather than selecting only the FLAC or other audio file.

This is especially relevant for music stored on an SD card, USB storage, a Downloads subfolder, or another location governed by Android's Storage Access Framework.

Success looks like this: AIMP can see the .cue file as well as the audio file, and adding or importing the sheet produces separate tracks. If the titles are then readable, no battery, Bluetooth, or device-control adjustment is needed.

4.2 Confirm That the CUE Survived the Transfer

Some transfer workflows copy audio files but omit small sidecar files. Use a file manager to verify that the destination contains the CUE, that its size is not zero bytes, and that it opens as readable text. Compare it with the working computer copy if possible.

If the file was edited on Windows, copy the corrected UTF-8 version to Android again. Replace the test copy deliberately and check its modification time so you do not keep opening an older duplicate.

4.3 Rule Out Irrelevant Android Settings

Battery restrictions can interrupt background scanning, and network permissions can affect remote sources, but neither setting normally changes the encoding of a local CUE title. Bluetooth profiles and media-button controls affect playback and commands, not CUE text parsing.

If the corrected local test works, stop. Do not change battery optimization, audio routing, output mode, or device-control settings for an encoding-only symptom.

5. Separate Encoding Problems From Other AIMP Issues

The phrase AIMP not working can describe many unrelated failures. Use the exact symptom to avoid spending time on output or network troubleshooting that cannot repair a text file.

5.1 Output Methods and Audio Devices

Investigate AIMP's output method, exclusive device mode, Bluetooth connection, or Windows audio device only when the tracks appear correctly but produce no sound, play at the wrong device, or fail during playback. Those settings operate after the CUE has been parsed.

If titles are garbled before playback begins, output configuration is not the cause. Likewise, installing a codec pack is neither necessary nor appropriate for correcting text encoding.

5.2 Skins and Plugins

A skin can affect how text is drawn, including font availability and available display space. It usually cannot change how the CUE bytes were decoded. Temporarily switch to a standard AIMP skin only if text appears correct in file information but looks missing, clipped, or rendered as empty boxes in one interface.

Temporarily disable a third-party plugin only when it imports, rewrites, or supplies metadata for the affected entries. Do not disable every plugin at once. Native CUE parsing that fails identically in a clean playlist points back to the file.

5.3 Converter Output

If the problem began after converting or splitting an album, inspect the converter's output folder and log. Confirm that the generated audio filenames match the CUE FILE line. Also check whether the converter copied an old CUE unchanged, generated a new one in a legacy code page, or embedded CUE data inside the output file.

Test the external CUE separately from any embedded CUESHEET metadata. They are different sources and may contain different text. Success means the generated files play at the correct indexes and the selected metadata source shows readable names.

5.4 Radio, Podcasts, Cloud Storage, and Network Shares

A CUE encoding repair applies to local or remotely stored CUE text. It does not repair malformed metadata sent by an internet radio station or podcast feed. If only live streams show garbled names, test a local UTF-8 CUE and treat the stream metadata as a separate issue.

For WebDAV, Samba, NAS, or cloud storage, copy one affected album to local storage. If the local UTF-8 copy works, verify remote credentials, offline availability, filename preservation, and whether the provider exposes the CUE alongside the audio file. Network access problems often make a sheet unavailable; they do not usually convert readable local text into another code page.

6. Run a Clean Temporary Test Before Reinstalling

Reinstalling AIMP rarely repairs a CUE saved in the wrong encoding. A controlled test is faster and protects playlists, library data, settings, skins, and plugins.

1. Create a temporary folder outside the main library.
2. Copy one affected audio file and its CUE into it.
3. Rename the audio copy to test.flac or keep its correct extension.
4. Update the CUE's FILE line to match.
5. Confirm all TITLE and PERFORMER text is readable in the editor.
6. Save the sheet as UTF-8, using UTF-8 without BOM if the first attempt fails.
7. Grant AIMP access to the folder on Android.
8. Create a new empty playlist and add or import the CUE.
9. Compare the number of entries, titles, and start positions with the sheet.

If the clean copy works, apply the same encoding conversion to the original CUE after backing it up. Re-add that album and refresh its library location. Do not delete every playlist or reset the entire application.

If the clean copy fails, check the CUE syntax, FILE line, track numbering, INDEX lines, and source audio readability. Try opening the audio file alone. If the audio file itself cannot be decoded, you have a format or damaged-source problem in addition to the CUE issue.

7. Quick Fix Checklist

• Back up the original CUE before editing it.
• Test one renamed copy instead of changing the whole library.
• Reopen legacy text using its original ANSI code page when known.
• Convert readable text to UTF-8 for Windows and Android portability.
• Try UTF-8 without BOM if standard UTF-8 is still rejected.
• Verify non-English PERFORMER and TITLE fields after saving.
• Match the FILE line exactly to the real audio filename.
• Keep the CUE and referenced audio file accessible in the same expected location.
• On Android, grant full folder access so AIMP can read sidecar CUE files.
• Remove stale album entries and re-add the corrected CUE.
• Rescan only the affected music-library folder if old text remains.
• Do not install codec packs or change audio output settings for garbled titles.
• Stop changing settings as soon as the clean UTF-8 test works.

8. Frequently Asked Questions

8.1 What Encoding Should an AIMP CUE Sheet Use on Android?

Use UTF-8. Android does not provide a dependable match for every legacy Windows ANSI code page, especially when a library contains multiple languages. UTF-8 preserves Cyrillic, Asian scripts, accented characters, and mixed-language metadata in one portable format.

8.2 Why Does the CUE Work on Windows but Not Android?

The Windows computer may be interpreting an ANSI CUE through the same regional code page that created it. Android may interpret those bytes differently. Android may also have access to the audio file but not the CUE sidecar until you grant full access to the folder. Convert a copy to UTF-8 and verify folder permission.

8.3 Should I Save the CUE With or Without a BOM?

Start with ordinary UTF-8. If AIMP still rejects an otherwise valid sheet, test UTF-8 without BOM. Keep whichever version parses correctly. The important checks are that the first command is recognized, all international characters remain readable, and the expected virtual tracks appear.

8.4 Why Are Titles Still Wrong After I Fixed the File?

The playlist or music library may still contain entries created from the old CUE. Remove the affected entries, add the corrected CUE again, and rescan the relevant library folder. Also check whether the current view is displaying embedded audio tags instead of CUE metadata.

8.5 Can an AIMP Skin or Plugin Cause Garbled CUE Text?

A skin may cause a font-display problem, and a metadata plugin may alter imported information, but neither is the first suspect when non-English CUE text consistently becomes mojibake. Test the corrected CUE in a fresh playlist with a standard skin. If file information is correct but one skin shows empty boxes, investigate that skin's font support.

8.6 What If AIMP Shows One Long Track Instead of the CUE Tracks?

Confirm that you added the CUE rather than only the audio image. Then verify the CUE is readable UTF-8 text, its FILE line names the correct audio file, and its TRACK and INDEX lines are intact. On Android, confirm that AIMP has folder access and that the CUE was actually copied to the device. Once the expected separate tracks appear with readable names and correct start positions, the repair is complete.