summaryrefslogtreecommitdiff
path: root/libs/ardour/ardour/route.h
diff options
context:
space:
mode:
authorRobin Gareus <robin@gareus.org>2015-05-02 02:36:53 +0200
committerRobin Gareus <robin@gareus.org>2015-05-02 03:46:49 +0200
commitce259edbcdd4c9a2cd8f2a5daa8b158dd9afc928 (patch)
tree03bfcd5b12a088b1ea941fadd1b4879699b81a07 /libs/ardour/ardour/route.h
parent2f432c3be779eb2e8b1915703746853781e0e8a2 (diff)
professionalize peak-meters
The peak meter needs to withstand various test-signals without visual jitter (in particular 1kHz sine) regardless of settings (period-size, sample-rate, custom fall-off). This needs to be done in sync (and not by a random non-rt ‘smoothing’ thread). On the downside this voids the ‘visual smoothing’ particularly with large buffersizes - but then again exactly this “always fall-off no matter what [the next real data will be]” is the problem. One the upside, there’s one less high-frequency (100Hz) thread (Yay!) PS. it probably never worked on windows, anyway. Only peak-meters are affected by his change. K-meters, IEC I/II and VU were never visually smoothed.
Diffstat (limited to 'libs/ardour/ardour/route.h')
-rw-r--r--libs/ardour/ardour/route.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/libs/ardour/ardour/route.h b/libs/ardour/ardour/route.h
index 2d35211f47..fbce3fd3f3 100644
--- a/libs/ardour/ardour/route.h
+++ b/libs/ardour/ardour/route.h
@@ -185,7 +185,6 @@ class LIBARDOUR_API Route : public SessionObject, public Automatable, public Rou
bool apply_processor_changes_rt ();
void emit_pending_signals ();
MeterPoint meter_point() const { return _pending_meter_point; }
- void meter ();
void set_meter_type (MeterType t) { _meter_type = t; }
MeterType meter_type() const { return _meter_type; }