Applies to: Apple TV 4K software that actually exposes Continuous Audio; compatible receiver and known references using different output audio paths.
The useful distinctions
- Apple documents Continuous Audio as a continuous Dolby MAT connection.
- Apple describes it as supporting transitions across audio formats.
- Older receiver indications may not distinguish each original signal while it is enabled.
Mark the boundary event
Record whether silence follows starting, stopping or switching references, or happens during continuous sound. These events lead to different comparisons. The feature described in the cited Apple article is version-sensitive, so verify that it exists on the actual device before describing any setting. A general support page is not evidence that older software exposes the same option.
Control the transition reference
Use the same two lawful references and the same order. Record the receiver’s input information where available. If the sources’ original formats are unknown, describe the test as an item-transition comparison and preserve that uncertainty. Do not promise that a feature will eliminate every audible gap or fix interruptions caused elsewhere in the chain.
Keep transition success distinct
A shorter or absent transition gap concerns that boundary. It does not establish that continuous playback is stable. Conversely, a mid-play dropout deserves its own route and item checks even if transitions improve. Report both observations, the actual software version and the feature state. This lets the manufacturer assess a reproducible condition without an invented all-device audio recommendation.
A focused way to proceed
- Record whether the current tvOS version exposes Continuous Audio.
- Observe a repeatable transition between two known references.
- Separately watch an uninterrupted passage for mid-play sound loss.
- Compare the supported alternative feature state without changing the route.
- Restore the preference and record transition and mid-play outcomes separately.
Worked example · synthetic
Hypothetical example: a documented feature state changes a repeated start-between-items gap while a separate mid-program dropout remains. The user records two outcomes and investigates the remaining dropout independently, rather than treating the transition improvement as a complete fix.
When to stop or ask for help
Only use a feature present in the actual software and supported route. No universal absence-of-gaps guarantee or StarShare compatibility is asserted.