cd5b0819bf1242240c60d2da4862abc65ce548e6
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.
Please see the Ardour web site at http://ardour.org/ for all documentation..
For information on building ardour:
http://ardour.org/development.html
Description
Languages
C++
56.5%
C
39.6%
JavaScript
1.3%
Lua
0.9%
Python
0.6%
Other
0.9%