Compare sequential, repeat and shuffle playback in 调调

Hold three tracks fixed and change only the playback mode, comparing expectation with observation.

1. Fix three tracks and a baseline

Choose three owned tracks whose identities and playback have already been checked, and record A/B/C with their real titles, artists and sounds. Identify all current queue entries. Do not substitute library sorting for queue order or ignore older entries between the three samples. Record current track and upcoming list, then inspect the visible mode state. Complete importing or file preparation first if necessary; the mode control does not repair a file. This comparison covers confirmed items on this device in this round, not the mode currently selected on another device.

2. Identify the actual control meaning

Identify the installed player’s actual mode control and its visible state. Public information names sequential, repeat and shuffle modes, but icon appearance and repeat scope should be read from the actual interface rather than invented. Record any label or indication before changing it. If you cannot determine whether a repeat setting covers one track or the current arrangement, keep that scope unknown. A guessed symbol is insufficient evidence for saying that a particular mode is enabled, and this tutorial does not supply a universal sequence of taps.

3. Observe a sequential control first

Select a state clearly identified as sequential in the installed version. Confirm the queue places B then C after A, and perform one traceable transition. Record manual next-track versus natural ending, checking title and sound instead of only a tap count. If the result is not B, preserve queue and state, then inspect old entries or changed selections. Resolve an unclear baseline before comparing shuffle. This result describes the current arrangement; it proves neither alphabetical title sorting nor a universal default order across all sources.

4. Check repeat at the relevant boundary

Select an identifiable repeat state without changing track or queue. Establish which ending boundary you are testing: hearing the middle of a track does not demonstrate repetition. If the interface states the scope, observe which track follows that ending. If it does not, retain the visible state and before/after identities without pre-filling “must return to A.” A long wait may be deferred, or a short recording used as a separate control. Record a changed sample as another round instead of combining different audio into one purported test.

5. Shuffle is not proof of guaranteed non-repetition

Select an identifiable shuffle state and record several actual track identities, the transition method and total observation count. A small sample happening to produce A/B/C does not prove shuffle was disabled. An adjacent repetition alone does not establish an algorithm defect either; inspect selected mode and duplicate queue entries. The public description promises no particular algorithm, perfectly uniform round or absolute prohibition on replay. Keep the heard sequence separate from your personal goal of hearing each track once, and do not rewrite results to fit the desired statistical pattern.

6. Return by changing only the mode

Save each round before restoring sequential conditions and checking the same queue and current track. Do not also switch servers, rearrange all songs or change the volume: that would obscure the difference. If directly selecting a track changes upcoming entries, copy the new arrangement before continuing instead of assuming the original queue remains. An external row for each state can contain interface state, action, actual next item and unresolved scope. This record does not require 调调 to export playback logs or produce shuffle statistics.

7. Diagnose unclear state and mixed samples

If the icon changes but results look similar, first identify the control and observation boundary. Repeated tapping can leave the final state unclear. If a track disappears, inspect file availability and queue identity rather than assume shuffle deleted music. Separate old and current rounds by date and sample, so an earlier sequential result is not reused as repeat evidence. For unclear scope, retain the visible label and explain its limitation. Do not name a control yourself to manufacture three results, or describe an unavailable option as a completed action.

8. Deliver differences together with conditions

Restore your everyday mode, confirm sound and queue identities remain clear, and save the actual sequential, repeat and shuffle rounds. Acceptance means specifying which state changed, which boundary was observed and which scope remains unchecked, rather than memorising three names. A repeat round without the required ending is incomplete, and an unheard shuffle sequence cannot be copied into the record. Re-identify controls and items after version or queue-size changes. One three-track comparison does not certify algorithms across every playback path or establish unperformed physical-device tests.

Related tutorials and sources

Queue order, Background controls.

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: upcoming queue.