Linux / PipeWire timing · Primary-source explanation; no UK IPTV implementation or account test. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Name the computed interval
PipeWire’s pw-top documentation defines the relationship between quantum and rate for a graph scheduling period. This is a particular internal interval, not the entire journey from a source event to a listener hearing a speaker. Keep that scope with a calculation before comparing it with a perceived lip-sync error or a network round-trip measurement.
Work through an original example
For a hypothetical quantum of 512 samples and rate of 48,000 samples per second,512 divided by 48,000 is approximately0.01067 seconds, or10.67 milliseconds. Halving that hypothetical quantum would halve this calculated period at the same rate. It would not establish that the whole playback route’s total delay was halved, because the calculation includes only the interval represented by these two values.
Compare the observed path separately
A viewing arrangement can include decoding, buffering, output hardware and wireless or external-speaker stages. Establish the actual path and measured symptom rather than adding or subtracting unrelated numbers. A subtitle adjustment is another timeline control, not a direct measurement of the audio graph. If a maintainer requests pw-top evidence, provide the real driver and follower context alongside the numerical fields.
Keep tuning claims within evidence
Do not choose the smallest possible quantum purely because the arithmetic number looks attractive. The actual system must meet its processing deadlines and supported configuration. Preserve the original settings and follow the relevant distribution’s guidance if a change is justified. This worked example reports no measured latency improvement and supplies no universal PipeWire or UK IPTV audio-buffer setting.