aboutsummaryrefslogtreecommitdiffstats
path: root/m4/ax_cxx_compile_stdcxx_11.m4
diff options
context:
space:
mode:
authorMatthias P. Braendli <matthias.braendli@mpb.li>2019-11-15 12:31:54 +0100
committerMatthias P. Braendli <matthias.braendli@mpb.li>2019-11-15 12:36:25 +0100
commit5b1dea7f85749d14bf85114accd01677caae7530 (patch)
tree9b5b11711cc79881876f50d5b400e49755a1cf37 /m4/ax_cxx_compile_stdcxx_11.m4
parenta59cb62793534117512666215549d99f9bebd98c (diff)
downloaddabmux-5b1dea7f85749d14bf85114accd01677caae7530.tar.gz
dabmux-5b1dea7f85749d14bf85114accd01677caae7530.tar.bz2
dabmux-5b1dea7f85749d14bf85114accd01677caae7530.zip
Initialise TIST with consistent system time at startup
The change introduced in fd33dd4 (v2.4.0) had the consequence of generating different timestamp offsets depending on when exactly the mux was started. The intended goal to avoid having the NULL symbol output at a fixed offset to avoid receiver synchronisation is however not so important, because most commercial receivers will cut transmission for several seconds before resuming, and the majority of the receivers will then start resynchronising. However, the different timestamp offsets upsets some modulator input modules, which so not necessarily have enough buffering capacity. This change reverts back to the previous behaviour, where the timestamp is set to current system time, rounded to 24ms.
Diffstat (limited to 'm4/ax_cxx_compile_stdcxx_11.m4')
0 files changed, 0 insertions, 0 deletions