Re: [tz] CCTF survey on Time and Frequency Metrology - Telecom

Brian.Inglis@SystematicSw.ab.ca said:
My reply suggested they divorce the time scales to allow business systems to use approximate POSIX like common law legal solar time as they ignore leap seconds one way or another; allow scientific systems to use atomic time and ignore legal solar time; and just ignore the ITU as broadcast radio time signals (DCF/JJY/MSF/WWV/B/H) are unavailable most places, may need equipment no longer commonly available, and too low accuracy for modern needs; other commonly available sources are delayed to uselessness by digital processing.
Could you please say more about the "delayed to uselessness"? -- These are my opinions. I hate spam.

On 2021-01-26 13:49, Hal Murray wrote:
Brian Inglis said:
My reply suggested they divorce the time scales to allow business systems to use approximate POSIX like common law legal solar time as they ignore leap seconds one way or another; allow scientific systems to use atomic time and ignore legal solar time; and just ignore the ITU as broadcast radio time signals (DCF/JJY/MSF/WWV/B/H) are unavailable most places, may need equipment no longer commonly available, and too low accuracy for modern needs; other commonly available sources are delayed to uselessness by digital processing.
Could you please say more about the "delayed to uselessness"?
Digital processing mainly compression/decompression delays in the common modern broadcast chain results in time announcements, transitions of minutes, audio "pips", clock tower chimes or bells, varying by eyeball and wristwatch measurable amounts from accurate time sources. Some articles talk about timing broadcast sources to determine which earlier "pip" signals the correct time. Apparently coordinating multiple regional sources in e.g. commentaries, discussions, or now virtual talk shows, requires time code calibration and compensation, so that discussions can appear natural; more so than many remote news reports which can show very pronounced delays, probably due to cellular mobile or wifi sources and internet routes. Satellite links add only up to 250ms each round trip. Many articles lack date stamps so it is difficult to know even if the BBC still transmits legacy analogue AM or FM with accurate "pips" or if stations are mainly DAB in the EU and UK. BBC "pips" history: http://tech-ops.co.uk/next/search_gcse/?q=GTS -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.]

On Jan 26, 2021, at 19:03, Brian Inglis <Brian.Inglis@SystematicSw.ab.ca> wrote:
Digital processing mainly compression/decompression delays in the common modern broadcast chain results in time announcements, transitions of minutes, audio "pips", clock tower chimes or bells, varying by eyeball and wristwatch measurable amounts from accurate time sources. Some articles talk about timing broadcast sources to determine which earlier "pip" signals the correct time. Apparently coordinating multiple regional sources in e.g. commentaries, discussions, or now virtual talk shows, requires time code calibration and compensation, so that discussions can appear natural; more so than many remote news reports which can show very pronounced delays, probably due to cellular mobile or wifi sources and internet routes. Satellite links add only up to 250ms each round trip. Many articles lack date stamps so it is difficult to know even if the BBC still transmits legacy analogue AM or FM with accurate "pips" or if stations are mainly DAB in the EU and UK.
It’s not just in the EU or UK. Digital modulation methods in common use on broadcast air chains in the US (both audio and video) can easily add up to several *seconds* of latency per hop. This can be the case even when the final delivery link to the receiver is ‘analog’ —e.g. amplitude modulation (‘AM’) via medium wave. Effectively, all audience-facing time marks on such broadcasts should be treated as being precise only to the nearest minute. Cheers! |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |---------------------------------------------------------------------| | A room without books is like a body without a soul. | | | | -- Cicero | |---------------------------------------------------------------------|

On 2021-01-27 12:58, Fred Gleason wrote:
On Jan 26, 2021, at 19:03, Brian Inglis <Brian.Inglis@SystematicSw.ab.ca <mailto:Brian.Inglis@SystematicSw.ab.ca>> wrote:
Digital processing mainly compression/decompression delays in the common modern broadcast chain results in time announcements, transitions of minutes, audio "pips", clock tower chimes or bells, varying by eyeball and wristwatch measurable amounts from accurate time sources. Some articles talk about timing broadcast sources to determine which earlier "pip" signals the correct time. Apparently coordinating multiple regional sources in e.g. commentaries, discussions, or now virtual talk shows, requires time code calibration and compensation, so that discussions can appear natural; more so than many remote news reports which can show very pronounced delays, probably due to cellular mobile or wifi sources and internet routes. Satellite links add only up to 250ms each round trip. Many articles lack date stamps so it is difficult to know even if the BBC still transmits legacy analogue AM or FM with accurate "pips" or if stations are mainly DAB in the EU and UK.
It’s not just in the EU or UK. Digital modulation methods in common use on broadcast air chains in the US (both audio and video) can easily add up to several *seconds* of latency per hop. This can be the case even when the final delivery link to the receiver is ‘analog’ —e.g. amplitude modulation (‘AM’) via medium wave. Effectively, all audience-facing time marks on such broadcasts should be treated as being precise only to the nearest minute.
https://en.wikipedia.org/wiki/Greenwich_Time_Signal#Similar_time_signals_els... I'm unaware of broadcast network time signals and their accuracy in NA other than CA CBC Radio One at 13:00 ET, and NR have disclaimers about those and telephone time and talking clocks possibly having one or two ~0.25s satellite hops added, which makes them useless: https://nrc.canada.ca/en/certifications-evaluations-standards/canadas-offici... https://nrc.canada.ca/en/certifications-evaluations-standards/canadas-offici... The telephone and broadcast time data require obsolete Bell 103 modem decoders and suffer from unknown telco or shortwave propagation or ionospheric delays and conditions: https://nrc.canada.ca/en/certifications-evaluations-standards/canadas-offici... https://nrc.canada.ca/en/certifications-evaluations-standards/canadas-offici... -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.]

El ene. 27, 2021, a las 3:56 p. m., Brian Inglis <Brian.Inglis@SystematicSw.ab.ca> escribió:
The telephone and broadcast time data require obsolete Bell 103 modem decoders and suffer from unknown telco or shortwave propagation or ionospheric delays and conditions:
https://nrc.canada.ca/en/certifications-evaluations-standards/canadas-offici...
https://nrc.canada.ca/en/certifications-evaluations-standards/canadas-offici...
Just a note on the word “obsolete” here, FSK modulation remains widely used and implemented. Modern software such as direwolf <https://github.com/wb2osz/direwolf#decoded-information-from-radio-emissions-...> can decode more reliably than prior hardware implementations of Bell 103 compatible demodulators. Regards, -s

On 1/27/21 11:58 AM, Fred Gleason wrote:
all audience-facing time marks on such broadcasts should be treated as being precise only to the nearest minute.
This topic came up during the famous trial of OJ Simpson in the 1990s, when they were trying to establish a timeline of events. Here's a section from the 1995-07-11 trial transcript: MR. DARDEN: Miss Harman, the times that you've given us today, those--the accuracy of those times depend on the accuracy of someone else's kitchen clock; is that correct? MS. HARMAN: And-- MR. SHAPIRO: Objection. THE COURT: Overruled. MS. HARMAN: And desk clock. Yes, it would. MR. DARDEN: Okay. And as well as the accuracy of the digital clock in your vehicle; is that correct? MS. HARMAN: Yes, it would. MR. DARDEN: And so if those clocks are one or two or more or less minutes off, then your time would be off, wouldn't it? MS. HARMAN: It would, except I usually set the clock to KFWB. So I feel confident that the clock in my car was accurate. Afterwards, I remember reports that KFWB's time signal was more accurate than that of KNX, their main news rival, and that KFWB's marketing tried to make hay of this. In the long run it was all for naught, though: KFWB's corporate owner bought the much more powerful KNX and then eventually sold KFWB, which is now airs classic regional Mexican music. And as far as I know, KNX's audio time signal is no more accurate now than it was in the 1990s.

On Jan 27, 2021, at 18:02, Paul Eggert <eggert@cs.ucla.edu> wrote:
MS. HARMAN: It would, except I usually set the clock to KFWB. So I feel confident that the clock in my car was accurate.
Back in the day when analog phone loops were the primary means used to backhaul audio/video content, the latency was quite low, and many stations did pride themselves on providing accurate and precise time checks. Things started to change with the introduction of satellite backhaul in the late 70s/early 80s. By the mid/late 90s, the introduction of digital encoding made the whole concept of precise-to-the-second time checks on broadcast channels moot (especially the introduction of systems like “HDRadio” in the US, that introduced around a half-dozen seconds of latency). Sports broadcasters kicked up a fuss (because of the time-honored habit of fans bringing portable radios to the game to follow the play-by-play), but no-one else seemed to care. Cheers! |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |---------------------------------------------------------------------| | The more things change, the more they stay insane. | | | | -- Anonymous | |---------------------------------------------------------------------|

<<On Wed, 27 Jan 2021 15:02:30 -0800, Paul Eggert <eggert@cs.ucla.edu> said:
And as far as I know, KNX's audio time signal is no more accurate now than it was in the 1990s.
Most CBS owned-and-operated radio stations installed "HD Radio", which requires an eight-second delay in the analog audio to match the compression delays on the digital side. (CBS Radio's then national VP of engineering, Glynn Walden, was heavily involved in the creation and promotion of the "HD Radio" system.) Receivers may add additional decoding delays so long as they delay analog audio an equal amount. (This allows for "seamless" cross-fading between the analog and digital signals at the fringes of the digital coverage area.) The encoding delay for "HD2" and other low-bandwidth subchannels is even longer, about 30 seconds (there's no blend-to-analog issue there, just the encoder). Even before HD Radio, CBS affiliates that carried the network news at the top of the hour would normally take the "bong" from the network feed, via satellite. However, CBS stations running a talk format would not normally dump the profanity delay for the news, so the network "bong" would be delayed another seven to fifteen seconds. Some talk stations chose to insert their own top-hour tone after the profanity delay, often at the transmitter. (Aside: When Westinghouse bought CBS, this combined Westinghouse's all-news stations with CBS's all-news stations in several major markets, including Los Angeles; other than New York, the weaker of the two stations ended up changing formats. But after Westinghouse changed its corporate name to "CBS", this had the effect that "CBS" owned a number of radio stations that were not affiliates of the CBS Radio Network -- the former Group W stations were primarily ABC Information Network affiliates if they had any network at all. ABC-I didn't broadcast a top-hour time signal, so those stations, like WBZ in Boston, already had their own local top-hour beeps if they wanted. WTIC in Hartford, which wasn't a Westinghouse station but did later become part of CBS Radio, famously kept its V-for-Victory Morse code interval signal from World War II. A few years back, CBS spun off its radio unit to Entercom, but kept the CBS Radio News network under the new name "CBS News Radio".) -GAWollman

On 2021-01-28, at 12:15:21, Garrett Wollman wrote:
Most CBS owned-and-operated radio stations installed "HD Radio", which requires an eight-second delay in the analog audio to match the compression delays on the digital side. ...
How do stations and networks deal with that latency between a news anchor in the home office and a reporter in the field? Perhaps a low-latency side channel? Eight seconds of dead air is expensive. I'm changing my stance on Leap Seconds: yes, it's a means of keeping UTC synchronized with the earth's rotation. But I see no need. Fix UTC forever at TAI - 42(?) s and make desired adjustments in civil time. At some future date when the drift accumulates to several minutes, change my timezone from MST7MDT to MST7:15MDT. This can be coordinated with the Spring clock reset: every few centuries that can be +45 minutes instead of +60. -- gil

Paul Gilmartin via tz said:
I'm changing my stance on Leap Seconds: yes, it's a means of keeping UTC synchronized with the earth's rotation. But I see no need. Fix UTC forever at TAI - 42(?) s and make desired adjustments in civil time. At some future date when the drift accumulates to several minutes, change my timezone from MST7MDT to MST7:15MDT. This can be coordinated with the Spring clock reset: every few centuries that can be +45 minutes instead of +60.
That's the leap hour proposal. I don't understand why so many people were against it. -- Clive D.W. Feather | If you lie to the compiler, Email: clive@davros.org | it will get its revenge. Web: http://www.davros.org | - Henry Spencer Mobile: +44 7973 377646

On Fri 2021-01-29T17:38:52+0000 Clive D.W. Feather hath writ:
That's the leap hour proposal. I don't understand why so many people were against it.
The document given to ITU-R which proposed the leap hour came from the United States. At that date the US Code explicitly specified that legal time was mean solar time, so representatives from the US groups were legally bound to include some mechanism for retaining a connection between UTC and mean solar days. The objection to the leap hour came from other countries. The US Code has since been changed, but not even pressure from US Department of State during talks about foreign aid could convince some of the countries that objected in 2015. -- Steve Allen <sla@ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 https://www.ucolick.org/~sla/ Hgt +250 m

On Fri 2021-01-29T10:33:35-0700 Paul Gilmartin via tz hath writ:
I'm changing my stance on Leap Seconds: yes, it's a means of keeping UTC synchronized with the earth's rotation. But I see no need. Fix UTC forever at TAI - 42(?) s and make desired adjustments in civil time. At some future date when the drift accumulates to several minutes, change my timezone from MST7MDT to MST7:15MDT. This can be coordinated with the Spring clock reset: every few centuries that can be +45 minutes instead of +60.
The problem that originally brought us leap seconds was that the legal definition of a calendar day in most countries is one mean solar day, which means actually measuring the rotation of the earth. Representatives from countries with such laws could not approve the use of radio broadcast time signals deviating from that definition. Because UTC by that name has become the basis of legal time in most places it will be necessary to get consensus to change the definition of the calendar day. At the ITU-R WRC in 2015 the same issue arose when a number of countries objected to changing UTC in a way that redefined the calendar day. -- Steve Allen <sla@ucolick.org> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 https://www.ucolick.org/~sla/ Hgt +250 m

On Jan 29, 2021, at 12:33, Paul Gilmartin via tz <tz@iana.org> wrote:
How do stations and networks deal with that latency between a news anchor in the home office and a reporter in the field? Perhaps a low-latency side channel? Eight seconds of dead air is expensive.
Few stations take the news feed ‘live’ off of the satellite demod any more. Instead, it’s usually pre-recorded and then played when needed to sync to the station’s other programming. (Many stations have software that is capable of playing out the recording while the audio capture is still ongoing; basically a FIFO queue). In the early 90s, I worked for a news network (SRN News in Washington DC) that actually broadcast the live ‘top of the hour’ news at ten minutes before the top of the hour [XX:50:00], with the actual feed at the top of the hour [XX+1:00:00] simply being a replay of the recorded audio. This was explicitly to allow affiliate stations to easily delay broadcast the news. This practice has since become standard industry practice (most networks now also offer news bulletins via FTP download, which saves the need for an expensive and cumbersome C-band satellite downlink). Cheers! |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |---------------------------------------------------------------------| | The more things change, the more they stay insane. | | | | -- Anonymous | |---------------------------------------------------------------------|
participants (9)
-
Brian Inglis
-
Clive D.W. Feather
-
Fred Gleason
-
Garrett Wollman
-
Hal Murray
-
Paul Eggert
-
Paul Gilmartin
-
Steve Allen
-
Steven R. Loomis