AIMP CUE Sheet Not Splitting Tracks: How to Fix It

When an AIMP CUE sheet is not splitting tracks, the playlist usually shows one long album file instead of separate song entries. The audio may still play correctly, but track titles, navigation points, and individual durations are missing. In most cases, the cause is a filename mismatch, an incorrect FILE line inside the CUE sheet, the wrong text encoding, insufficient Android folder access, an outdated playlist entry, or confusion between an embedded and sidecar CUE sheet.

The safest troubleshooting method is to test the CUE and audio files as a pair before changing playback output, reinstalling AIMP, or modifying unrelated settings. CUE splitting happens when AIMP reads or imports the source, so audio devices, equalizers, skins, Bluetooth profiles, and most output settings normally do not determine whether one album appears as multiple tracks.

1. Confirm the Symptom With a Small Safe Test

Start by confirming that this is specifically a CUE parsing problem. Create a new temporary playlist in AIMP and add only the affected album. If it appears as one item whose duration equals the entire album, the CUE sheet was not applied. If it appears as several entries with different titles and start times, splitting is already working and the problem is probably limited to an older playlist or Music Library entry.

1.1 Check What AIMP Is Actually Playing

Open the track's file information or properties and inspect its path. Confirm that AIMP is playing the local album file you expected, not another copy from a library location, cloud cache, network share, or previously imported playlist.

This matters when several copies of an album exist. A CUE file stored beside one FLAC cannot split an identical-looking FLAC located in another folder. The sidecar CUE must be accessible beside the exact audio file AIMP adds.

Success means that the displayed path points to the folder containing both the audio file and its CUE sheet. If it does, stop checking duplicate-file locations and move to the filename test.

1.2 Build a Simple FLAC Plus CUE Test

To separate an AIMP configuration problem from a damaged album package, make a test folder containing one ordinary FLAC file and one CUE file. Use simple ASCII filenames without unusual punctuation:

• Test Album.flac
• Test Album.cue

The CUE file can use a minimal structure such as:

FILE "Test Album.flac" WAVE
  TRACK 01 AUDIO
    TITLE "First Test Track"
    INDEX 01 00:00:00
  TRACK 02 AUDIO
    TITLE "Second Test Track"
    INDEX 01 01:00:00

The second index must fall within the duration of the FLAC. Add the CUE itself to a new playlist, or use AIMP's playlist import or open-playlist command. You can also add the audio file and let AIMP detect the matching sidecar CUE.

Success means two entries appear and both play from different positions in the same physical FLAC. Once this works, do not reinstall AIMP. The original album's CUE text, filename, location, encoding, or cached playlist state is the likely cause.

2. Check the CUE Filename and FILE Line

The most common AIMP CUE sheet not splitting tracks fix is correcting how the CUE refers to its audio file. Windows may hide extensions, and Android file managers may make subtle filename differences difficult to see, so verify every character carefully.

2.1 Match the Sidecar CUE to the Audio File

For reliable automatic detection, place the CUE and audio file in the same folder and give them matching base names. For example:

• Artist - Album.flac
• Artist - Album.cue

A name such as Album.cue beside Artist - Album.flac may not be picked up automatically as expected. You can either rename the CUE to match the audio file or explicitly import the CUE into AIMP.

Be careful with hidden extensions. A file displayed as Artist - Album.cue might actually be named Artist - Album.cue.txt. On Windows, enable file-name extensions in File Explorer. On Android, inspect the complete name in the file manager's details view.

After renaming, remove the old unsplit playlist entry and add the album again. Success means AIMP creates separate virtual tracks. Stop changing filenames once the correct track list appears.

2.2 Correct the FILE Line Inside the CUE

Open the CUE with a plain-text editor and find the line beginning with FILE. The quoted filename must identify the real audio file, including its extension. A copied CUE may still point to an old WAV, APE, or differently named FLAC.

For this audio file:

Artist - Album.flac

The relevant line should look like:

FILE "Artist - Album.flac" WAVE

The traditional WAVE token is commonly used in CUE sheets that point to lossless audio files. The critical part for this symptom is that the quoted filename is correct. Preserve quotation marks when the filename contains spaces.

Look for small differences such as a missing disc number, a changed apostrophe, doubled spaces, a different extension, or Unicode characters that only look similar. File references can also fail after the audio file is converted from APE or WAV to FLAC without updating the CUE.

If the sheet contains multiple FILE lines, verify each referenced file. In that situation, adding only one physical audio file may not represent the complete album. Import the CUE itself so AIMP can process all referenced files in sequence.

2.3 Confirm That the Index Points Are Valid

Each track normally needs a TRACK declaration and an INDEX 01 time. The times must increase through the album and stay within the source file's duration. Duplicate, reversed, malformed, or out-of-range index values can prevent correct parsing or produce missing tracks.

A normal progression might be:

• INDEX 01 00:00:00
• INDEX 01 04:12:25
• INDEX 01 09:07:60

CUE times use minutes, seconds, and frames rather than decimal milliseconds. Avoid manually converting them unless you know the original boundaries. If the CUE came with the album, first correct filenames and encoding before editing index values.

3. Add the Correct Source to the Playlist

AIMP can use a sidecar CUE automatically when the audio file and sheet satisfy its matching rules. It can also import a CUE as a playlist. Explicitly adding the CUE is often the quickest solution when automatic matching fails or one sheet references multiple files.

3.1 Add or Import the CUE Itself

Create a temporary empty playlist and use the playlist menu's open or import command to select the .cue file. Dragging the CUE into the playlist may also work on Windows. On Android, use the playlist screen and the available open-playlist or import function rather than launching only the audio file from a third-party file manager.

Do not add both the unsplit audio file and its split CUE entries to the same test playlist. Doing so can create one full-album entry alongside the virtual tracks, which makes the result look inconsistent.

Success means the playlist contains one entry for every TRACK section. Selecting the second entry should begin near the second INDEX 01 position without creating a second physical audio file.

3.2 Remove Stale Playlist Entries After Editing

A playlist entry already created from the unsplit audio file may not be rebuilt merely because you corrected the CUE on disk. Similarly, if you change track titles or index points, an existing imported list can continue showing the earlier result.

1. Remove the affected album entries from the playlist without deleting the source files.
2. Save the corrected CUE.
3. Create a new temporary playlist.
4. Import the CUE again.
5. Verify the titles, durations, and starting positions.

If the new playlist works, replace the old album entries. There is no reason to delete every playlist or reset the entire player.

3.3 Refresh the Music Library Deliberately

If the playlist test works but the Music Library still shows one long track, the library is displaying previously indexed information. Remove or rescan only the affected folder where possible. If necessary, exclude the folder from the library and add it again after confirming that the corrected CUE and audio file are together.

Do not begin with a full library deletion. A small playlist test proves whether AIMP can parse the pair without disturbing play counts, ratings, grouping choices, or unrelated folders.

4. Distinguish Embedded CUE From Sidecar CUE

A sidecar CUE is a separate .cue file stored beside the audio file. An embedded CUE is metadata stored inside a compatible audio container. These are different sources, and a CUE that another tag editor displays is not necessarily stored in a form AIMP will interpret as split playlist tracks.

4.1 Test a Sidecar CUE First

If you suspect an embedded CUE problem, export or create a separate UTF-8 CUE file and place it beside the audio file. Match the base filenames and make sure the FILE line names the audio file exactly. Then import the sidecar CUE into a clean playlist.

This is especially useful with MP3 files containing custom metadata labeled as a CUESHEET. A custom MP3 tag may be visible in another program without functioning as a standards-based embedded CUE source in AIMP. A correctly written external CUE avoids that ambiguity.

Success means the sidecar sheet creates separate playlist items. In that case, keep using the sidecar or rebuild the embedded metadata in a format and container known to support it properly. Do not change output devices or install playback plugins, because decoding was not the failure.

4.2 Check Which Metadata Supplies Titles and Artwork

After splitting starts, track titles may come from the CUE while album artwork and other fields come from the audio file, folder images, or AIMP's metadata handling. Incorrect artwork or album grouping does not prove that splitting failed.

Use AIMP's file information or tag editor to compare the physical file's tags with the CUE's TITLE and PERFORMER fields. Fix metadata only after the playlist contains separate tracks. Editing artwork, replay gain, genre, or ordinary tags will not repair a broken FILE reference.

5. Fix Android Encoding and Folder Access

Android adds two important failure categories: text encoding and scoped folder permissions. AIMP may be able to play the audio file while lacking the access needed to discover or read a neighboring CUE file.

5.1 Save the CUE as UTF-8

For the most predictable Android behavior, save the CUE as UTF-8. This is particularly important when artist names, track titles, or filenames contain Cyrillic, accented Latin characters, Japanese characters, or other non-ASCII text.

Use a text editor that lets you choose encoding explicitly. Select UTF-8, save the file without changing its .cue extension, and copy it back into the audio folder. If your editor offers several UTF-8 variants, ordinary UTF-8 is the safest starting point.

Then remove the old entries from the Android playlist and import the CUE again. Success means track names display correctly and the album is divided at its indexes. Once that happens, do not experiment with ANSI or regional encodings.

5.2 Grant AIMP Access to the Exact Album Folder

On recent Android systems, permission to play recognized audio does not always provide unrestricted access to nearby metadata files. In AIMP, open the file-adding interface, navigate to the parent music folder, and grant full folder access when the app offers that option. Select the specific music directory rather than a storage root.

If the album is in Downloads, the root of an SD card, or another restricted location, Android may prevent the desired folder grant. Move the test pair to a normal user-created folder such as Music/CUE Test, grant AIMP access to that folder, and import the CUE from inside AIMP.

Success means the same pair that appeared as one file now appears as several tracks. If so, the original location or permission scope was the cause.

5.3 Test Local Storage Before Network or Cloud Sources

A CUE sheet referring to an audio file on WebDAV, Samba, cloud storage, or another network source requires AIMP to reach both the metadata and the referenced audio path. Credentials, offline files, renamed folders, or provider-specific virtual paths can break that relationship.

Copy the CUE and audio file into one local folder and run the test there. If local splitting works, reconnect the network source, verify its credentials, and add the CUE through AIMP's own storage interface. A radio stream, podcast episode, or changing cloud URL generally cannot be treated like a stable local album image unless the source exposes both files consistently.

Battery optimization can interrupt network playback, but it does not normally explain why a local album initially enters the playlist as one item. Address battery restrictions only if tracks split correctly but playback stops in the background.

6. Rule Out Unrelated Settings and Extensions

It is useful to know which AIMP settings are unlikely to cause this exact symptom. This prevents an AIMP troubleshooting session from becoming a series of risky or irrelevant changes.

6.1 Output Modes and Audio Devices

DirectSound, WASAPI, WASAPI Exclusive, and ASIO affect how Windows sends decoded audio to an output device. Bluetooth profiles and Android audio routing affect where sound plays. These settings may cause silence, exclusive-device errors, stuttering, or unexpected audio quality, but they ordinarily do not control whether a CUE becomes several playlist entries.

If the full album plays as one continuous item, leave the working output mode alone. Only investigate output settings when separate CUE tracks already appear but produce no sound or fail during track transitions.

6.2 Skins, Plugins, and Interface Layouts

A skin can change how playlists and durations are displayed, but it should not rewrite the CUE's FILE reference. Switch temporarily to a standard interface only if you suspect that split entries exist but are grouped, collapsed, or difficult to see.

Temporarily disable third-party playlist, tag, or input plugins if the problem began immediately after installing one. Do not remove built-in components indiscriminately. A clean plugin test is useful only after a known-good FLAC and CUE pair fails in a new playlist.

6.3 Converter Options

AIMP's converter can create a single output file and, depending on the chosen workflow, may generate a CUE sheet. If a converted album does not split, inspect the generated CUE's FILE line and confirm that it references the final output filename rather than the original source.

If you renamed the converted file afterward, rename the CUE to match and update the FILE line. Review any converter messages for incomplete output or write errors. The conversion itself succeeded only if the destination audio file plays for its expected duration and the associated CUE references it correctly.

7. Run a Clean Temporary Test Before Reinstalling

Reinstallation is rarely the first solution because it does not repair a misspelled filename, inaccessible sidecar file, malformed index, or stale imported playlist. Instead, isolate the issue with a temporary playlist and a simple local folder.

1. Create a new folder outside restricted or synchronized locations.
2. Copy one known-good FLAC into it.
3. Create a matching UTF-8 CUE with two valid tracks.
4. Use matching base filenames.
5. Confirm the FILE line names the FLAC exactly.
6. Create an empty AIMP playlist.
7. Import the CUE itself.
8. Play both resulting entries and verify their start positions.

If this test works, AIMP's core CUE support is functioning. Compare the working pair with the failed pair one difference at a time. Check location, filename, extension, FILE line, encoding, index order, and whether the original sheet references multiple files.

If even the minimal pair fails, try AIMP's standard skin and temporarily disable relevant third-party input or playlist plugins. On Windows, a portable or temporary clean profile can provide a controlled comparison without deleting the normal profile. On Android, test in a newly created local folder with explicit folder access.

Reinstall only after preserving playlists and settings, confirming that a valid local pair fails, and ruling out permissions and plugins. Do not delete source music during this process.

8. Quick Fix Checklist

• Put the CUE and album audio file in the same folder.
• Match their base filenames for automatic sidecar detection.
• Make sure the CUE is not really a hidden .cue.txt file.
• Correct the quoted filename on every FILE line.
• Confirm that the referenced extension matches the real audio file.
• Save the CUE as UTF-8, especially on Android.
• Add or import the CUE itself into a new playlist.
• Remove stale unsplit entries before importing a corrected sheet.
• Verify that INDEX 01 times increase and fit within the audio duration.
• Grant Android access to the specific folder containing both files.
• Test locally before troubleshooting WebDAV, Samba, or cloud paths.
• Use an external sidecar CUE when embedded metadata is uncertain.
• Do not change output devices if the audio already plays correctly.
• Stop troubleshooting as soon as separate entries play from the correct positions.

9. Frequently Asked Questions

9.1 Should I Add the FLAC or the CUE to AIMP?

With a correctly named sidecar CUE in the same folder, adding the FLAC can allow AIMP to detect the sheet automatically. For troubleshooting, importing the CUE itself is clearer because it directly tests whether AIMP can parse the sheet and resolve its FILE line.

9.2 Why Does AIMP Still Show One Track After I Fixed the CUE?

The playlist may contain an entry created before the correction. Remove that entry without deleting the physical file, create a new playlist, and import the corrected CUE again. Rescan the affected Music Library folder only after the new playlist works.

9.3 Does the CUE Filename Have to Match the Audio Filename?

Matching base names are important for reliable automatic detection of a one-file album. If the names cannot match, such as when one CUE references two physical files, explicitly import the CUE rather than relying on automatic pickup.

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

The likely causes are non-UTF-8 text, Android folder-access restrictions, or opening the audio through a file manager that does not give AIMP access to the sidecar CUE. Save the sheet as UTF-8, grant access to the album folder, and import the CUE from AIMP's playlist interface.

9.5 Can an Embedded CUE Replace a Separate CUE File?

It can in compatible formats and metadata structures, but not every field called CUESHEET is interpreted identically. If embedded metadata does not create tracks, test a matching external UTF-8 CUE. A working sidecar confirms that the audio and index information are usable.

9.6 Will Changing WASAPI, ASIO, Bluetooth, or the Skin Fix Splitting?

Usually not. Those settings affect playback output or presentation, while CUE splitting is determined when AIMP reads the CUE and adds the source to a playlist or library. Investigate them only if separate tracks already exist and the remaining symptom concerns sound, transitions, or display.