diff options
author | Robin Gareus <robin@gareus.org> | 2019-06-09 17:47:21 +0200 |
---|---|---|
committer | Robin Gareus <robin@gareus.org> | 2019-06-09 19:56:15 +0200 |
commit | cd5b0819bf1242240c60d2da4862abc65ce548e6 (patch) | |
tree | 04b77bbe6a7d53a0cb7b1bc2061193ce5a426a37 /libs/ardour/luabindings.cc | |
parent | 1cec6d1250de9e17075c563775aa7fe2c424b596 (diff) |
Consolidate meter-type state and API
In theory different UIs can show different meter-types, so it
can make sense to maintain the type in different places.
MeterType is a bit-set and PeakMeter implementation provides for this.
However, this is not being used, and the current implementation
was rather fragmented, cross-connected signals to keep types in sync,
allowed inconsistent meter-types in GUI and backend.
MeterType is now kept by meter itself, however it is still
saved/restored as part of the Route state.
N.B. This change breaks the API, various methods have been renamed
for consistency.
Diffstat (limited to 'libs/ardour/luabindings.cc')
-rw-r--r-- | libs/ardour/luabindings.cc | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/libs/ardour/luabindings.cc b/libs/ardour/luabindings.cc index 85dc09c5b6..eb6fcf1233 100644 --- a/libs/ardour/luabindings.cc +++ b/libs/ardour/luabindings.cc @@ -1554,7 +1554,8 @@ LuaBindings::common (lua_State* L) .deriveWSPtrClass <PeakMeter, Processor> ("PeakMeter") .addFunction ("meter_level", &PeakMeter::meter_level) - .addFunction ("set_type", &PeakMeter::set_type) + .addFunction ("set_meter_type", &PeakMeter::set_meter_type) + .addFunction ("meter_type", &PeakMeter::meter_type) .addFunction ("reset_max", &PeakMeter::reset_max) .endClass () |