From bb64b314c83843a792103de83ef67cc5b0d1d9be Mon Sep 17 00:00:00 2001 From: "Matthias P. Braendli" Date: Fri, 20 May 2016 16:16:28 +0200 Subject: Get rid of FCT discontinuity check The timestamp discontinuity verification takes care of this now --- src/DabMod.cpp | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) (limited to 'src/DabMod.cpp') 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(); -- cgit v1.2.3