Batches and personal sources

Compare a renamed duplicate and a new recording in 调调

Use an unchanged copy and a genuinely new sample to separate filename changes from duplicate-content handling.

English translation of the Chinese original, translated on . Original publication dates, attribution, code and version notes are retained.

Use an unchanged copy and a genuinely new sample to separate filename changes from duplicate-content handling.

1. Fix the identity of an existing import

Choose an authorised short track already imported and playable, labelled A externally. Preserve original, library title, duration and opening anchor. Replay it to establish identity rather than rely on its name. Record the earlier import path/date while retaining the library and item. This task observes repeated content, not an internal deduplication algorithm or a way to inflate collection counts. The working original A remains the control instead of being deleted to manufacture space for an addition.

2. Create a copy changing only its filename

Copy A using existing file-management tools and give the copy a distinct filename, without editing audio or tags. Keep both locations clear and compare size/provenance. If a tool re-encodes or edits metadata, record that changed condition instead of calling it filename-only. Renaming an extension does not change format, and truncation is not copying. A hash proof is not required, but explain how the copy was made and what changed or remains unchecked. Different names alone do not establish different content.

3. Prepare a genuinely different B

Prepare another owned or authorised small recording B with genuinely different sound, its own audible anchor and no known prior import in this library. B controls ordinary addition; replacing A’s cover is not a new-audio control and would introduce another duplicate-handling question. Record full names, sizes and expected identities for A-copy and B, keeping both within published file conditions. Mark expectations as pending: repeated content may encounter duplicate handling, while B needs normal new-item verification. Do not pre-fill either result as certain success.

4. Submit the copy and retain real feedback

Select A-copy through a supported import flow and submit once after checking identity. If comparing Wi-Fi transfer too, create a separate round instead of changing file and network together. Observe feedback and any new library item. Published duplicate skipping does not promise identical wording or a match report in every version. If nothing new appears, establish whether A remains accessible and playable before diagnosing failure. Do not invent a matched item or internal fingerprint the interface did not reveal.

5. Use B to check the new-item path separately

Save the copy result before importing B through the same path. Check feedback, library identity and opening sound. Keep the copy’s possible nonaddition separate from B’s addition instead of applying one notice to both. If B fails too, inspect readability, size and provider before declaring every new file falsely duplicated. Each submission needs its own observed result. Total library change cannot identify which operation succeeded, especially with same-name items; continue using sound and provenance.

6. Avoid inferring rules for untested metadata changes

This control covers a renamed copy and different audio. It does not establish what happens after artwork edits, artist changes, re-encoding or trimming. The public description mentions duplicate content without specifying its internal test. Keep those rules unknown. A future tag-change comparison needs an external working copy, named tool and separate change record, preserving A. Hundreds of private copies are unnecessary. A few observations do not certify permanent deduplication across the entire collection.

7. Diagnose nonaddition separately from playback failure

If the copy adds nothing while A works, retain duplicate handling as a possible explanation alongside actual feedback. If A cannot be found, inspect identity/source; if B exists but is silent, inspect track/output. These are not all deduplication errors. Do not delete A to force the copy to look new. Preserve unexplained errors and compare one known-readable small sample. Change one condition per round and leave unperformed Wi-Fi checks pending instead of generalising one local result to every transfer path.

8. Deliver distinct outcomes for the two inputs

Confirm that original A still plays and B’s actual state is recorded, retaining originals, copy provenance and both rounds. Explain what filename change established, whether audio changed and how additions/existing items were identified, instead of writing only “deduplication normal.” Internal fingerprints remain unmeasured; accidental selection or editing requires a new round. The method can help later mixed batches, but today’s result does not verify every file or claim completed physical-device testing of a private collection.

Three-file batch reconciliation, Metadata provenance.

Checked on November 16, 2026: Apple’s Russia lookup, cross-checked against China, lists 调调 1.0.1, requiring iOS / iPadOS 17.6 or later. The official store release notes add Home Screen widgets and music themes. Tasks follow published scope; identify controls and available choices in the installed version. Keep expectations separate from actual observations. No completed physical-device or private-server test is claimed.

Official Apple screenshot: local music and file importing.