From 44880471bfe3af3903d11944e122b1724f8a7c19 Mon Sep 17 00:00:00 2001 From: "Matthias P. Braendli" Date: Thu, 11 Jul 2019 15:41:26 +0200 Subject: Add a bit of background explanation about FIG0/19 NewFlag --- src/fig/FIG0_19.cpp | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'src/fig') diff --git a/src/fig/FIG0_19.cpp b/src/fig/FIG0_19.cpp index f032bd5..5b6a384 100644 --- a/src/fig/FIG0_19.cpp +++ b/src/fig/FIG0_19.cpp @@ -109,6 +109,19 @@ FillStatus FIG0_19::fill(uint8_t *buf, size_t max_size) else { fig0_19->ASw = 0; } + + /* From the crc-mmbtools google groups, 2019-07-11, L. Cornell: + * + * Long ago, there was a defined use for the New flag - it was intended + * to indicate whether the announcement was new or was a repeated + * announcement. But the problem is that it doesn't really help + * receivers because they might tune to the ensemble at any time, and + * might tune to a service that may be interrupted at any time. So + * some years ago it was decided that the New flag would not longer be + * used in transmissions. The setting was fixed to be 1 because some + * receivers would have never switched to the announcement if the flag + * was set to 0. + */ fig0_19->NewFlag = 1; fig0_19->RegionFlag = 0; fig0_19->SubChId = 0; -- cgit v1.2.3