summaryrefslogtreecommitdiffstats
path: root/src/DabMod.cpp
diff options
context:
space:
mode:
authorMatthias P. Braendli <matthias.braendli@mpb.li>2016-05-20 16:16:28 +0200
committerMatthias P. Braendli <matthias.braendli@mpb.li>2016-05-20 16:16:28 +0200
commitbb64b314c83843a792103de83ef67cc5b0d1d9be (patch)
tree1538dad1ad322fad67e9f29094c1d87b022cf54c /src/DabMod.cpp
parent5ebfab9364d4315394a136732fd464ffe2229588 (diff)
downloaddabmod-bb64b314c83843a792103de83ef67cc5b0d1d9be.tar.gz
dabmod-bb64b314c83843a792103de83ef67cc5b0d1d9be.tar.bz2
dabmod-bb64b314c83843a792103de83ef67cc5b0d1d9be.zip
Get rid of FCT discontinuity check
The timestamp discontinuity verification takes care of this now
Diffstat (limited to 'src/DabMod.cpp')
-rw-r--r--src/DabMod.cpp8
1 files changed, 1 insertions, 7 deletions
diff --git a/src/DabMod.cpp b/src/DabMod.cpp
index 57ff79b..43550c5 100644
--- a/src/DabMod.cpp
+++ b/src/DabMod.cpp
@@ -108,7 +108,7 @@ struct modulator_data
enum class run_modulator_state_t {
failure, // Corresponds to all failures
normal_end, // Number of frames to modulate was reached
- again, // FCT discontinuity or ZeroMQ overrun
+ again, // ZeroMQ overrun
reconfigure // Some sort of change of configuration we cannot handle happened
};
@@ -887,12 +887,6 @@ run_modulator_state_t run_modulator(modulator_data& m)
running = 0;
ret = run_modulator_state_t::normal_end;
}
-#if defined(HAVE_OUTPUT_UHD)
- } catch (fct_discontinuity_error& e) {
- // The OutputUHD saw a FCT discontinuity
- etiLog.level(warn) << e.what();
- ret = run_modulator_state_t::again;
-#endif
} catch (zmq_input_overflow& e) {
// The ZeroMQ input has overflowed its buffer
etiLog.level(warn) << e.what();