Hello abaymajr,
abaymajr wrote:mdyde wrote: I've logged it as an enhancement request. (When the output perspective mix adjustments were added for v5 I did actually strongly consider making front-rear, up-down output perspective mix adjustments, instead of individual level adjustments for the perspectives, but felt in the end that the individual levels provided the maximum flexibility in the simplest way. I've noted in the enhancement request that you'd also like additional convenience/'shortcut' adjustments which vary the ratios of pairs of the existing level adjustments accordingly.)
IMHO, I think three knobs panning/balancing between front 1 and front 2, rear 1 and rear 2, and between front and rear pairs, would be the easiest way to make real perspective adjustments, while maintaining the same overall output level and so avoiding audio clipping or low output. This would not exclude the existing individual input level settings, on the contrary. Such adjustments would be useful for leveling these perspective inputs when their sound levels are not originally leveled each other.
If using the four output perspectives as 'perspectives' (front, rear, up, down) then yes -- balance/pan-type adjustments would be quicker. However, some people (including, I think, Mark) use them for other things (e.g. for feeding to a parallel reverb mix, or to monitor speakers, or to a recording mix), for which balance/pan adjustments could be awkward. It was implemented the way it is to allow both uses. Hence I think we would definitely not want to sacrifice the existing adjustments, but I wrote in the enhancement request that you'd appreciate some additional ones for maximum convenience for balance/pan-type use.
abaymajr wrote:For a few days now, I've been trying to use the intermed mix entries for this purpose, outputting to them eight different balance combinations between 3 (primary) perspectives, and connecting to the master mix only the intermed mix corresponding to the desired combination at a giving moment. I still have to mute the other 7 intermed outputs, but, although it's more limiting, this is better and faster than remembering/changing each perspective level combination. I ask: are the primary and intermed mixes which do not result in an effective sound output still processed, generating CPU overhead?
- If a mixer send is muted it will consume no CPU overheads.
- If no non-silent audio is being routed to any given mixer bus then the bus will will consume no CPU overheads.
- If non-silent audio *is* being routed to a given mixer bus and its sends are non-muted then its non-muted sends will add some overhead, but it will be so tiny that you really shouldn't need to worry about it (unless you're using hundreds of buses simultaneously).
abaymajr wrote:Also, I would like to take the opportunity to make a small suggestion. Since the number of mix presets has been dramatically increased, with the benefit of a possible use of each of them for different samplesets, it would be interesting to be able to rename the mix preset in order to avoid inadvertently changes to a mix preset which is not intended by the user to be shared among two or more samplesets. To avoid this, I've been renaming the first master mix entry, adding to it a convenient keyword, but it would be even better if the preset mix itself could be renamed.
Yes -- adding the ability to name mixer presets is logged as an enhancement request.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.