summaryrefslogtreecommitdiffstats
path: root/src/fig
diff options
context:
space:
mode:
authorMatthias P. Braendli <matthias.braendli@mpb.li>2019-07-11 15:41:26 +0200
committerMatthias P. Braendli <matthias.braendli@mpb.li>2019-07-11 15:41:26 +0200
commit44880471bfe3af3903d11944e122b1724f8a7c19 (patch)
tree63e943d2b67be581079e05890a9feb004dd2f5cb /src/fig
parent0a5b562102db25f28f4759bd17cf6864a3386514 (diff)
downloaddabmux-44880471bfe3af3903d11944e122b1724f8a7c19.tar.gz
dabmux-44880471bfe3af3903d11944e122b1724f8a7c19.tar.bz2
dabmux-44880471bfe3af3903d11944e122b1724f8a7c19.zip
Add a bit of background explanation about FIG0/19 NewFlag
Diffstat (limited to 'src/fig')
-rw-r--r--src/fig/FIG0_19.cpp13
1 files changed, 13 insertions, 0 deletions
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;