Tracks and time ledgers

Compare fixed-duration PCM WAV files in 调调

Audit channels, sample rate, container bits and payload for two thirty-second PCM samples, then check importing, duration and audible playback separately.

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

Audit channels, sample rate, container bits and payload for two thirty-second PCM samples, then check importing, duration and audible playback separately.

1. Fix the same thirty-second source passage

Use an authorised thirty-second recording with a short opening identifier and a different near-end cue verified externally. Prepare two still-thirty-second PCM WAV exports in a familiar tool and retain actual settings/reports. This lesson does not reinterpret sample rates or convert audio inside 调调. Both contain the same passage but can have different bytes; shared content is not byte identity. Preserve source and exports. The extension helps locate files while real format information establishes the encoding.

2. Write all four data conditions

A uses 44100 sample frames per second, two channels, sixteen stored bits per channel sample and thirty seconds. B uses 48000 frames per second, two channels, twenty-four stored bits with twenty-four valid bits for this example, again thirty seconds. A frame contains simultaneous samples across channels; stereo does not double duration. If twenty valid bits occupy a twenty-four-bit container, record precision separately while using container bytes for payload. Compressed WAV or floating-point formats need their own model rather than this integer-PCM ledger.

3. Calculate A’s four bytes per frame and payload

Sixteen bits divided by eight gives two bytes per channel sample; two channels give four bytes per frame. Multiply by 44100 for 176400 bytes per second, then by thirty for 5292000 payload bytes. Keep frame, second and whole-passage rows to avoid treating sixteen bits as sixteen bytes. With decimal MB=1000000 bytes, payload is 5.292 MB. This is audio data, not guaranteed whole-file size: headers and extra chunks add overhead, and a universal forty-four-byte header is not assumed. An independent A check multiplies 1323000 frames by four bytes to obtain the same 5292000. If an external report exposes nBlockAlign and nAvgBytesPerSec, they correspond here to four and 176400. These are format-report fields, not promised player labels.

4. Calculate B’s six-byte frames without changing duration

For B, twenty-four bits gives three bytes per channel sample and six bytes per stereo frame. At 48000 frames per second that is 288000 bytes/second, hence 8640000 bytes or 8.64 decimal MB for thirty seconds. A has 1323000 frames and B 1440000; divided by their respective rates both last thirty seconds. Larger payload does not imply longer duration, new source information, better sound or automatic system compatibility. Those are separate questions requiring their own evidence. B also checks as 1440000 frames times six bytes. A mathematical mono variant of A, with other conditions unchanged, has 2646000 payload bytes for the same thirty seconds. This third row is a calculation only; do not mark an uncreated file as successfully imported.

5. Retain both actual import outcomes

Submit each sample through the file flow and retain identity/feedback separately. Published WAV support does not certify every depth or internal encoding. If B fails, preserve its report/error and use known-playable A as a control rather than rename an extension to imitate compatibility. Both are far below the per-file limit; no boundary-sized file is needed. If content already exists, verify the existing item and separate additions from selections. Import failure does not invalidate the correctly scoped payload calculation.

6. Verify duration and two audible cues

Open each successfully playable item, verify its opening identifier and near-end cue, and record displayed duration and the range actually heard. A rounded 0:30 does not inspect every sample frame. If one shows a minute or differs markedly in speed/pitch, inspect external preparation before explaining duration from file size alone. Use the same output and ordinary volume. Listening verifies identity/duration, not an uncontrolled vote on sound quality.

7. Separate whole-file size from payload differences

Inspect actual whole-file byte counts externally against 5292000/8640000. A somewhat larger file can contain legitimate chunks; a difference of a few dozen bytes alone does not establish corruption. A much smaller result calls for checking compression, duration or copied parameters, stopping precise attribution when reports are unknown. Player duration does not replace file inspection, and total app storage is not one track’s payload. Label bytes and decimal MB; do not silently mix MB with binary MiB values. Check whether size is exact bytes or rounded MB. A display near 5.3 MB does not establish exactly 5300000 bytes and therefore cannot prove an 8000-byte header. Use a real byte-count report for that claim, or retain the uncertainty imposed by rounded display.

8. Reopen and deliver format and playback ledgers

Reopen the usable items, verify title/cues and deliver two rows of parameters, frame bytes, byte rate, thirty-second payload and actual playback state. Explain why B can carry more data yet last equally long, why container/valid bits are distinct and why visibility is not playability. Preserve failed samples/errors instead of reinstalling or deleting the library as a diagnosis. Changed channels, duration or compression need an appropriate new model; these observations do not certify all WAV files or device decoders.

Preparing audio formats; Passage position cards.

Checked on 17 November 2026: Apple’s Russia lookup and China lookup both list 调调 1.0.1, requiring iOS / iPadOS 17.6 or later. The official store release notes include music themes and Home Screen widgets. Users supply audio and servers; identify controls actually present in the installed version. These are repeatable instructions with paper expectations separate from observations, not claimed completed device or private-server tests.

Method references: Microsoft WAVEFORMATEX data rate and frame alignment; Microsoft WAVEFORMATEXTENSIBLE container and valid bits.