hi,
I'm afraid to say that, under the new internal solution being fostered by the xaudio-bus-aux branch, the (visual) order to the buses will become irrelevant, moot or just kept for UI purposes alone.
though, the Master shall be kept as the first and top of the list, always, no matter what--failing to keep that way is prone to shed some some strange behavior, at best, just because it's a pervasive assumption in way too many internal points (in code) to count, not just in the View/Buses... dialog.
iow., the restrictions you current have in the buses dialog, specially re. Master bus, are there for some old, deep reasons, they aren't there out of a whim ;)
hyu.
hi,
I'm afraid to say that, under the new internal solution being fostered by the xaudio-bus-aux branch, the (visual) order to the buses will become irrelevant, moot or just kept for UI purposes alone.
though, the Master shall be kept as the first and top of the list, always, no matter what--failing to keep that way is prone to shed some some strange behavior, at best, just because it's a pervasive assumption in way too many internal points (in code) to count, not just in the View/Buses... dialog.
iow., the restrictions you current have in the buses dialog, specially re. Master bus, are there for some old, deep reasons, they aren't there out of a whim ;)
hyu.