AIMP Auto Numbering Tracks Wrong: How to Fix It

When AIMP auto numbering tracks wrong results appear, the cause is usually not audio playback, codecs, or the output device. Automatic numbering writes track-number tags according to the files selected and their current order in AIMP's tag editor. If that order is wrong, multiple discs are mixed together, or the disc and track-total fields are inconsistent, AIMP can save technically valid numbers that do not match the album. The safest fix is to test a few copied files, establish the intended order, verify disc boundaries, and only then write new tags.

1. Confirm the Symptom With a Small Safe Test

Begin by separating a real tag-numbering problem from a playlist display or playback-order problem. These symptoms can look similar, but they require different fixes.

• If the Track field inside File Information is wrong, the file's tag was numbered incorrectly.
• If the Track field is correct but the playlist is scrambled, the problem is sorting or cached playlist data.
• If the playlist looks correct but playback jumps around, check shuffle, the playback queue, or device controls.
• If disc 2 begins with the next number after disc 1, the files were probably numbered as one continuous selection.
• If every file shows the same number, a fixed value may have been applied instead of automatic numbering.

1.1 Create a Disposable Test Set

Copy three to five tracks into a temporary folder. Do not test first on the only copy of an album. Choose files whose intended order is obvious, such as filenames beginning with 01, 02, 03, and 04.

Open those copies in AIMP's advanced tag editor. Examine the Filename, Title, Track, Disc, Album, and Artist fields. If available in the selected format, also inspect the total-tracks and total-discs values. Write down or capture a screenshot of the original values before changing anything.

Sort the test files by filename, confirm that the visible rows run from the first track to the last, and then apply automatic numbering. Save the changes and reopen the files rather than trusting only the current editor view.

Success looks like this: the reopened test files contain Track 1, 2, 3, and 4 in the intended order. If that works, stop changing unrelated AIMP settings. The original problem is almost certainly the order or grouping of the larger selection.

2. Put the Selected Files in the Correct Order Before Numbering

AIMP's numbering tool needs an ordered list. It cannot infer the album sequence reliably when the selected rows are sorted by title, date, path, artist, or another field. The first visible selected file normally needs to be the track that should receive the first number.

2.1 Sort by Filename First

If filenames already include reliable prefixes such as 01, 02, and 03, sort the tag editor's file list by Filename before using automatic numbering. Check the entire selection, especially the transition from track 9 to track 10.

Filenames without leading zeroes may appear lexically as 1, 10, 11, 2, and 3 in software that treats the values as text. If you see that pattern, do not number the files in that order. Use another reliable field, manually rearrange the rows if the interface permits it, or temporarily use zero-padded filenames such as 01 through 11.

Do not assume that selecting files in Windows Explorer guarantees the same order after they reach AIMP. The receiving application may obtain the files in a different sequence, particularly when they are dragged from search results, multiple folders, or another application.

Success looks like this: before you press the numbering command, the visible list exactly matches the album booklet, folder listing, or another trusted source. Once that is true, stop adjusting playlist and playback settings because they do not determine the tag editor's current row sequence.

2.2 Check Which Files Are Actually Selected

Automatic numbering should be applied only to the files that belong to the sequence. A hidden extra file, duplicate, bonus track, cover-art audio rip, or unrelated podcast episode changes every following number and may also produce the wrong track total.

Count the selected rows and compare that number with the expected album length. Look for duplicate paths, repeated titles, CUE-defined entries mixed with the source image, and files from bonus or hidden-track folders.

If only part of an album needs correction, select only that part. Do not renumber an entire music collection to repair five files.

3. Handle Disc Numbers and Multi-Disc Albums Correctly

Track number and disc number are separate concepts. A conventional two-disc album usually contains Disc 1 with tracks 1 through its final track, followed by Disc 2 restarting at track 1. A continuous sequence across both discs may be appropriate for some releases, but it should be a deliberate choice based on the source.

3.1 Number Each Disc Separately

The safest procedure for multi-disc albums is to work one disc at a time:

1. Filter or select only the files belonging to disc 1.
2. Sort them into their intended track order.
3. Set the Disc field to 1 and, when supported, the total-disc value to 2.
4. Apply automatic track numbering beginning at 1.
5. Set the track total to the number of tracks on disc 1 if your tagging convention uses per-disc totals.
6. Save and verify the first and last file.
7. Repeat the process for disc 2, setting Disc to 2 and restarting Track at 1.

This prevents disc 2 from receiving numbers that simply continue after disc 1. It also prevents an interleaved selection from becoming Disc 1 Track 1, Disc 2 Track 2, Disc 1 Track 3, and so on.

Success looks like this: each disc starts at Track 1, all files carry the correct Disc value, and the final track on each disc matches the release information. Stop when those values remain correct after reopening the files.

3.2 Decide How Track Totals Should Be Written

Some tag formats and applications display track numbers as a pair such as 3/12, where 3 is the track and 12 is the total. The total may be stored as a related field or encoded according to the format's tagging rules.

For a multi-disc release, choose one consistent convention:

• Per-disc totals: Disc 1 may use 1/10 through 10/10, while Disc 2 uses 1/8 through 8/8.
• Whole-release totals: Some libraries use the complete album total, although support and interpretation can vary.
• No total: Store only the current track number if total fields cause compatibility problems across devices.

Do not select several albums and write one total based on the number of all selected files. If AIMP's available command does not calculate a separate total for every album or folder in your specific workflow, process each album or disc separately and enter the verified total.

3.3 Sort Multi-Disc Albums by More Than Track Number

A playlist or music library sorted only by Track can interleave discs: Disc 1 Track 1, Disc 2 Track 1, Disc 1 Track 2, Disc 2 Track 2. Use a compound order that considers Album, Disc, and then Track. In views that support multiple column sorting, apply the higher-level album or disc sort before the track sort. A custom sorting template can serve the same purpose where available.

This is a display fix, not a reason to rewrite correct tags. If File Information already shows the right Disc and Track values, change the sorting method and leave the files alone.

4. Separate Tag Errors From Playlist and Library State

AIMP can show old information after files have been edited outside the active playlist or library. A stale display does not necessarily mean the tag write failed.

4.1 Reload the Playlist's File Information

After saving corrected tags, remove the temporary copies from the test playlist and add them again, or use the available command to reread file information. Then open File Information for the first, middle, and final tracks.

If the tags are correct there but the playlist remains in the wrong order, sort the playlist by filename or by a template using Disc and Track. Also confirm that shuffle and the user-defined playback queue are not making the playback sequence differ from the visible list.

Success looks like this: the playlist order agrees with the correct tag fields, and starting playback at the first item proceeds through the album normally. Once it does, do not edit the tags again.

4.2 Rescan or Refresh the Music Library

If the music library still displays the old numbers, refresh or rescan the affected folder so AIMP rereads the files. Limit the operation to the relevant source when practical. A full-library rebuild is rarely the first step for a single incorrectly numbered album.

On Android, a folder-linked smart playlist can refresh its content and reread tag data. Confirm that the playlist is still linked to its source folder and that manual deletions have not changed its synchronization state.

4.3 Check the Skin Without Blaming It for Tag Changes

A skin can move, hide, or visually simplify sorting controls. It normally does not determine what Track value gets written into a file. Temporarily switch to a standard skin only if you cannot locate the sorting, selection, File Information, or tag-editor controls needed for the test.

If the same files contain wrong tags when inspected independently of the skin, continue troubleshooting the selection and numbering operation. If only the displayed order changes with the skin, the issue is interface access or playlist presentation.

5. Check Plugins, Converters, and Metadata Sources

Third-party plugins, online metadata, and conversion tasks can replace or reinterpret tags after you correct them. Test the built-in workflow before concluding that AIMP is not working.

5.1 Disable Only the Relevant Tagging Plugin Temporarily

If the problem began after installing a tagging or library plugin, repeat the copied-file test without that specific plugin. Do not disable security software or remove unrelated audio components. Playback visualizers, DSP effects, and output plugins are generally unrelated to automatic tag numbering.

If the built-in editor numbers the copied files correctly while the plugin-enabled workflow does not, keep the plugin out of the batch process until its mapping and overwrite options are understood.

5.2 Review Online Tag and Artwork Results Before Applying Them

An online metadata result may describe a different edition, reissue, regional release, or disc layout. Artwork alone is not proof that the track list matches your files. Compare the result's track count, durations, disc count, and titles before applying it.

If online tagging changes correct numbers, limit which fields it may replace or apply only the fields you have verified. Do not repeatedly fetch metadata after manual correction unless you intend to overwrite the existing values.

5.3 Check Audio Converter Tag Options

If converted files are numbered differently from their sources, inspect the converter task rather than renumbering the originals. Determine whether the converter copies source metadata, builds tags from filenames, applies a naming template, or writes output files in task-list order.

Run a two-file conversion into a temporary folder. Compare source and output Track and Disc fields using File Information. Review any converter error details or logs available in the interface.

Success looks like this: the converted copies preserve the source Track, Disc, and total fields. When they do, reuse that converter configuration and stop modifying the source tags.

5.4 Treat Radio, Podcast, and Cloud Metadata Differently

Internet radio and many live streams provide temporary metadata rather than editable local-file tags. Podcast episode order may come from the feed's publication data, while cloud and network playlists may depend on remote filenames or cached metadata. Automatic tag numbering is primarily useful for writable local files and supported tag formats.

Before editing, confirm that the item represents a real writable audio file. A stream URL, feed entry, read-only network object, or CUE-defined virtual track may not accept the same tag changes as an ordinary local MP3 or FLAC file.

6. Check Windows and Android Access Only When Saving Fails

Permissions matter when AIMP cannot write the corrected numbers, but they do not normally explain why the proposed numbering order is wrong before saving.

6.1 Windows File Access

Check whether the files are read-only, stored in a protected location, opened by another program, or located on a network share where your account lacks write access. Try saving one copied file in a normal user folder.

If the local copy saves correctly but the original does not, resolve access to the original folder or edit a writable copy. Do not use a registry cleaner, codec pack, or permanent security exclusion. Those actions are unrelated to track-tag sequencing.

6.2 Android Storage and Network Access

On Android, verify that AIMP has access to music and audio files and to the folder containing the album. Depending on the Android release and storage location, the app may need explicit media or shared-storage access. Remote SMB, FTP, or WebDAV sources also require valid network access and credentials.

Some remote sources permit playback but not tag writing. Copy one affected track to writable local storage and test it there. If local editing works, the limitation belongs to the remote source, its credentials, or its write support rather than automatic numbering itself.

Battery restrictions can interrupt lengthy scans or cloud access, but they do not usually alter the numeric sequence produced from an already visible selection. Adjust battery behavior only if refreshes or saves are being interrupted.

7. Use a Clean Temporary Test Before Reinstalling

Reinstallation is rarely the right first response because the wrong order may remain in the filenames, tags, playlist, or library database. A clean test gives you more useful evidence without risking playlists or settings.

1. Back up the affected files and export important playlists.
2. Create a new empty playlist or temporary AIMP profile where supported.
3. Add only three copied files from one folder.
4. Use the default skin and built-in tag editor.
5. Sort the files by their verified filenames.
6. Apply automatic numbering and save.
7. Close and reopen the editor to verify the stored values.

If the clean test succeeds, the installation is functional. Return to the original setup and add one variable at a time, such as the full album, custom sorting template, plugin, remote source, or library view. Stop as soon as the failure returns because the last added variable is the best lead.

If the clean test fails even with writable local copies, record the exact steps, file formats, original tags, expected result, and actual result. Check AIMP's error details or debug facilities if available, then use that reproducible case when seeking support. Avoid deleting playlists or resetting the entire library until the copies and exports are safe.

8. Undo Incorrect Numbering Safely

The safest undo method is restoring the original files from a backup. Recent AIMP tag-editor workflows may also provide an undo function, but its availability and retained history depend on the session and settings. Do not assume that undo will remain available after closing the editor or application.

If no backup or undo is available, stop editing the files and reconstruct the order from reliable evidence:

• Original filenames and folder structure
• A verified album booklet or release track list
• CUE sheets belonging to the audio files
• Existing Disc, Title, and Album fields
• A previously exported playlist
• Another synchronized device that still has the correct metadata

Correct one album and one disc at a time. Save, reopen, and verify each group before continuing. This limits the effect of another mistaken selection.

9. Quick Fix Checklist

• Work on copied files until the procedure is proven.
• Confirm that the problem is the stored Track tag, not only playlist order.
• Sort selected files by reliable zero-padded filenames before numbering.
• Inspect the first, ninth, tenth, and final rows for lexical sorting mistakes.
• Remove duplicates, bonus files, CUE entries, and unrelated selections.
• Number each disc separately and restart each disc at Track 1 when appropriate.
• Write the correct Disc value and total-disc value for every disc.
• Set track totals per album or per disc according to one consistent convention.
• Save and reopen several files to confirm the values were written.
• Refresh the playlist or rescan the affected library folder.
• Use Album, Disc, and Track together when sorting multi-disc releases.
• Test without the relevant tagging plugin if values are overwritten.
• Verify converter metadata settings when only converted copies are wrong.
• Test remote files from writable local storage.
• Stop changing settings as soon as stored tags and playback order are correct.

10. Frequently Asked Questions

10.1 Why Does AIMP Number Track 10 Before Track 2?

The visible files may be sorted as text rather than as numeric values, producing 1, 10, 11, 2. Sort using zero-padded filenames such as 01 and 02, or establish the correct row order manually before automatic numbering. Verify the list before saving because numbering follows the selected sequence.

10.2 Why Does Disc 2 Start at Track 11?

Both discs were probably selected and numbered as one continuous batch. Restore or correct the affected copies, select disc 2 by itself, set Disc to 2, and apply automatic numbering beginning at Track 1. Confirm whether the release truly uses restarted or continuous numbering before changing it.

10.3 Should I Write Track Totals Such as 3/12?

Track totals are optional for many libraries, but they can help identify complete albums. Use a consistent convention and verify compatibility with your other devices. For multi-disc albums, per-disc totals are often clearer. Do not use the number of every file in a multi-album selection as one shared total.

10.4 Why Are the Tags Correct but AIMP Still Plays the Wrong Track Next?

Check playlist sorting, shuffle, repeat behavior, and the user-defined playback queue. A queue can override the visible playlist order without changing the tags. On Android, also check headset, notification, volume-button, Bluetooth, and car controls if external commands are skipping or selecting tracks.

10.5 Can a Skin Cause Wrong Automatic Track Numbers?

A skin may hide or relocate the controls used to sort and select files, which can lead to numbering the wrong visible order. It should not independently rewrite Track fields. Use a standard skin for the test if you cannot find the necessary controls, then inspect the saved tags directly.

10.6 Do I Need to Reinstall AIMP?

Usually not. First test copied local files in a new playlist with the default skin, built-in editor, and no relevant third-party tagging plugin. If that test works, reinstalling is unlikely to solve the underlying selection, sorting, cache, or metadata-source problem.