Re: DRM broadcast disrupted by leap seconds

2003-07-21 Thread Peter Bunclark
On Sat, 19 Jul 2003, Markus Kuhn wrote: All modern digital broadcast transmission systems introduce significant delays due to compression and coding. It is therefore common practice today that the studio clocks run a few seconds (say T = 10 s) early, and then the signal is delayed by digital

Re: DRM broadcast disrupted by leap seconds

2003-07-19 Thread Ed Davies
Markus Kuhn wrote: When the scheduled transmission time arrives for a packet, it is handed with high timing accuracy to the analog-to-digital converter, I assume you mean digital-to-analog. ... [In fact, since short-wave transmitters frequently switch between programmes at the full hour,

Re: DRM broadcast disrupted by leap seconds

2003-07-19 Thread Markus Kuhn
Ed Davies wrote on 2003-07-19 09:15 UTC: When the scheduled transmission time arrives for a packet, it is handed with high timing accuracy to the analog-to-digital converter, I assume you mean digital-to-analog. Yes, sorry for the typo. This also raises the point that because the

DRM broadcast disrupted by leap seconds

2003-07-18 Thread Markus Kuhn
A recent visitor gave me a detailed account of a telecoms application where UTC leap seconds can cause havoc, which I would like to share here with you. In this example, the design ended up being vulnerable to UTC leap seconds, in spite off the engineers being fully aware of all the issues