baa30262b8
Session::route_processors_changed accumulates signals emitted in realtime and processing is delegated to a dedicated rt-safe thread. Previously this resulted in any changed to be converted to a `GeneralChange`, which unconditionally triggered a route-reorder. Record-arming a track causes a MeterPointChange (meters change to "in"), and this caused routes to be resorted and a latency-update. While the former is reasonable (Ardour prefers to process rec-armed routes first), the latter certainly is not.
Please see the Ardour web site at https://ardour.org/ for all documentation..
For information on building ardour:
https://ardour.org/development.html