Naming & folders · How we test and maintain this guide
The list, folder and player may sort differently
A playlist has a source order. A folder browser may sort alphabetically by filename. A music player may sort by embedded track number, album or title. Those are separate choices. A tidy numbered filename can still appear in a different sequence when the player is using tags, and importing a playlist does not create a universal playback-order instruction.
The TuneBundle importer lists the metadata it reads and lets you choose entries to add to the batch. The archive contains selected ready files and records; it does not include a newly generated M3U playlist or rewrite embedded track tags. Decide which ordering mechanism your destination uses before renaming a collection to solve the wrong problem.
Numbers identify positions among ready results
| Input in the executed naming example | Number + title output |
|---|---|
| Same title | 01 - Same title.mp3 |
| same title | 02 - same title.mp3 |
| A/B: take? | 03 - A B take.mp3 |
| CON | 04 - _CON.mp3 |
The current naming function assigns numbers across ready items. Unchecking a ready item does not renumber every remaining name. In the controlled partial-batch example, the third and seventh ready rows were unchecked. The selected set therefore can retain gaps in its numbered filenames. That is expected bookkeeping, not proof that the ZIP lost a file.
Failed rows are not ready files and are handled differently from unchecked ready rows. Use the current CSV to connect each selected filename to its source ID and inclusion flag. The sequence shown in a text input, the ready-file numbering and the final delivery order should not be assumed identical when failures, duplicates or selections intervene.
Create a deliberate delivery sequence
For an ordered project, make a small mapping before you rename copies. Include intended position, exported filename, source ID and any destination track tag. This preserves the relationship if you want a consecutive delivery set while keeping the source export untouched. The example below is a proposed handoff map, not a newly implemented drag-to-reorder feature.
| Delivery position | Exported position | Action on a working copy |
|---|---|---|
| 01 | 01 | Keep first chosen track |
| 02 | 02 | Keep second chosen track |
| 03 | 04 | Use the next selected take; preserve source ID in the map |
- Save and verify the original selected archive with its records.
- Choose the final sequence by listening and project purpose, rather than by title alone.
- Write the source-to-delivery mapping and review it for missing or repeated items.
- Rename working copies if filename sorting is the destination's method. Keep extensions accurate.
- If the player sorts by tags, write appropriate track numbers on copies using a metadata editor and verify the stored values.
Use a consistent number width for the size of the collection, such as 01 through 20 for a small batch. This makes ordinary lexical filename sorting easier to interpret. It does not force every application to use that order. A player with shuffle enabled, a different sort field or a cached library view can still present another sequence.
Test from the destination, not just the workspace
Open the delivered folder or imported album in the actual target application. Check the first, middle and last positions, then inspect any skipped or duplicated item. Confirm that the player is using the delivery copies rather than old paths. A playlist referencing files that were later renamed may need its own paths updated.
Compare the intended total duration with the selected collection, remembering that the interface rounds display values. Duration is a useful cross-check but cannot distinguish every same-length take. Keep source identity and listening decisions in the mapping so a later revision does not accidentally replace one artistic version with another.
When sharing a collection, include only the records a recipient needs. A clean track list can explain order without exposing every private source note. Retain the fuller map in your own project records. If the order changes after delivery, give the revision a distinct name and describe which positions changed rather than silently replacing files under familiar names.