Prepare audio for 调调: check format, size and permission separately

Prepare one recognisable, traceable small audio file before importing.

1. Establish the first file’s provenance

Choose audio you recorded yourself, a purchased usable file, or material you have permission to use. Record its source and whether you may use it on this device. This exercise handles a file you already possess; it does not require an unknown music-download site. Preserve the original and create a clearly named working copy. A short piece with a recognisable beginning and ending is enough for comparison. Do not begin with hundreds of unfamiliar files from a whole album collection: if the first attempt fails, locating the problematic file will be much harder.

2. Retain actual extension and size

Check the full filename and size in the system’s file information. If the current view hides extensions, use an information view instead of guessing the format from artwork. The dot and suffix are clues, not proof that the contained audio track is readable. Record the size together with its units. Start with a small sample well below the published 512 MB per-file limit to reduce the first transfer’s burden. Renaming an unsupported file to mp3 does not convert its encoding; it can also hide the original type during later diagnosis.

3. Compare the published format list

The current public description lists MP3, M4A, AAC, WAV, AIFF, CAF and FLAC, a maximum of 512 MB per file, and the condition that the system can read the audio track. Compare your extension with this list, then record format-list membership separately from actual readability. The list does not certify every encoding in all seven containers. Two files with the same suffix can still differ in track encoding or integrity. Without an inspection tool, leave sample rate, bit depth and losslessness unknown rather than inventing those conclusions.

4. Identify protected content separately

The public description explicitly excludes DRM-protected imports. If a source only permits listening within a subscription service, first establish whether you actually obtained an importable audio file. An item marked downloaded in that service is not automatically a general-purpose file. This exercise does not remove protection or change permissions. Keep an unreadable protected item in its original service and choose another authorised readable sample. If protection has not been checked, record that uncertainty: a failed import does not prove DRM, and the ability to copy a file does not prove its absence.

5. Confirm the provider supplies readable content

For iCloud Drive or another file provider, wait until the content is readable on this device, then check its name, size and provenance. A row in the picker may only locate a file; it does not replace a reading check. Do not delete cloud originals to test independence, or clear another app’s data during preparation. You may use an existing system opening method to compare the content with your record. A successful system opening is only a control, however: a separate import and playback check inside 调调 is still required.

6. Record an audible identity, not just a name

Write down an audible opening anchor, such as your own spoken count or a recognisable musical passage, and an approximate duration. The teaching example is not something you have already heard; fill the observation from your own attempt. Identically named editions may have different lengths, while differently named files may duplicate the same content. Record at least provenance, full filename, size, format clue and audible anchor. These will help determine whether the title, artist or artwork read by 调调 belongs to the same track, instead of using a similar cover as identity verification.

7. Diagnose preparation with one-variable controls

If a file exceeds the limit, choose another smaller authorised sample; do not cut bytes from its ending merely to reduce the size. For an unlisted extension, preserve the original and ask whether the source supplies a supported format. Conversion is separate external preparation, with quality that needs its own check. If neither system nor app can read a file, inspect integrity and provenance first. If only one import path fails, record that path and its error. Change only the file or provider per comparison; one failure does not classify every file with that extension.

8. Deliver a preparation card ready for importing

Close the information view and locate the sample again, checking that its name, size and original location remain clear. Pass this preparation record to the import step. Acceptance means identifying this particular file, its permitted use, size conditions and unresolved track readability, rather than writing only “MP3 supported.” Leave unchecked conditions for the import task instead of inventing an answer. Preparation is not a completed playback pass. Repeat these checks for another track, provider or edition instead of applying today’s result permanently to an entire music collection.

Related tutorials and sources

File import, Offline verification.

Checked on November 15, 2026 against Apple public lookup and the official App Store information and screenshots it lists: version 1.0, requiring iOS / iPadOS 17.6 or later, with identity and version cross-checked against China lookup. Tasks use published capabilities; identify actual controls in your installed version. External records are acceptable. Keep expectations separate from observations; no physical-device, private-server or universal input-environment test is claimed.

Official Apple screenshot: local importing.