Consolidate meter-type state and API
authorRobin Gareus <robin@gareus.org>
Sun, 9 Jun 2019 15:47:21 +0000 (17:47 +0200)
committerRobin Gareus <robin@gareus.org>
Sun, 9 Jun 2019 17:56:15 +0000 (19:56 +0200)
commitcd5b0819bf1242240c60d2da4862abc65ce548e6
tree04b77bbe6a7d53a0cb7b1bc2061193ce5a426a37
parent1cec6d1250de9e17075c563775aa7fe2c424b596
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.
libs/ardour/ardour/meter.h
libs/ardour/ardour/route.h
libs/ardour/luabindings.cc
libs/ardour/meter.cc
libs/ardour/route.cc