Read the precision of the source field
Apple's Compressor documentation lists23.976 and24 as separate frame-rate choices. That distinction matters when identifying a source or a conversion requirement.
A user-facing player label can round a value. Preserve an inspector's actual field and units instead of assuming every displayed24 means exactly24/1.
Use arithmetic without inventing a measurement
A small rate difference accumulates over time when timelines are treated differently. That general calculation is not a diagnosis of a particular subtitle or audio drift.
A file can also have edits, variable timing or player errors. Do not claim fractional rate is the cause merely because a mismatch grows.
Keep display matching separate
Apple TV's matching guidance concerns supported source cadence and display modes. A display output value is another stage from the encoded source.
A brief blank while switching modes differs from a timing gap growing during playback. Record the exact event rather than treating both as one frame-rate fault.
Compare the same timeline
Use a permitted exact edition and note several positions when investigating sync. If a subtitle aligns early and changes abruptly after one scene, an edit difference may fit better than a uniform rate mismatch.
Do not change global output, audio delay and subtitle delay together. Their effects can conceal which relationship is wrong.
Ask for a precise specification
Provide the actual source rate where known, player/device versions and the observed timing pattern. Do not infer rate from a subscription tier or sports category.
No frame timing or drift was measured here. The article explains documented rate distinction and a proposed evidence method, not a universal conversion instruction or service claim.
Retain the original rate when sharing diagnostics
If a support form accepts only an integer, include the more precise rate in a note rather than silently rounding it away. Likewise, distinguish nominal metadata from an observed average if the tool exposes both. A convenient label can be sufficient for ordinary browsing while still being inadequate for technical timing work. The report should state what the tool actually measured or declared, leaving unknown fields unknown instead of deriving a complete cadence from one rounded number. A label rounded for browsing can still be useful; the problem begins when its missing precision is treated as a measured technical fact.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- Apple Compressor frame-rate and duration — Official versioned current search excerpt lists23.976 and24fps as distinct choices. Arithmetic example is original explanation, not measured video drift.
- Apple TV content matching — Official support excerpt: frame-rate matching, source cadence and transitions; no app/TV combination certified.
