D. Michael McIntyre wrote:
> On 03/05/2013 03:04 PM, Ted Felix wrote:
>
>> > Work up the math, add a config variable (audioPanLaw?), and hook it
>> > into the config dialog ("Audio Pan Law"). Default to -3. Shouldn't be
>> > too hard.
> I agree this is a good candidate for a config variable that defaults to
> the current -3 behavior. We have the math for two out of three. I
> wouldn't begin to even try to get my head around working out how to do
> the -6 dB option, being basically bereft of math skills, but I'm good
> for knocking together the GUI side of things if anybody would like help
> with that.
> -- D. Michael McIntyre
I agree that any change to Rosegarden's panning should be switchable and
should default to the current behavior.
Currently Rosegarden appears to be using a form of the so-called 0dB Pan Law
that results in a monaural channel being considerably louder when panned to the
center than when panned to either side. When I first read the code, I assumed
it was a mistake, but I guess people actually do this sort of thing
intentionally.
From what I've read, I'm not sure that OdB, -3dB, or -6dB setups would be
useful for what I need to do. But because there seems to be little
standardization concerning how these laws are implemented, I might be able to
configure a -3dB panning law to provide constant power (constant sum of the
squares of the channel levels). I have found that a constant-power scheme
delivers exactly what I need, as I no longer have to readjust a fader every
time I move something.
I have found Rosegarden's existing behavior extremely awkward, since I use the
panning controls to position monaural sound sources on an imaginary stage.
Every time I would move something, I would disturb the tonal balance of the
composition. Some organ compositions that I worked on a while ago illustrate
the point:
Polyphonic organ music will typically have several independent voices played on
the same manual at the same time. With Rosegarden this means assigning each of
these voices a to a different segment, even though they originate from the same
keyboard.
I could easily have assigned the same instrument (representing a certain stop
combination) to each of these segments but chose, instead, to assign a
completely different instance of the same instrument to each. That way I could
pan the individual identical instruments, thereby hinting at the spacial
diversity that would be evident in an actual pipe organ installation. (This is
a lot easier than reworking a sound font to specify the position of each
individual pipe!)
In this case maintaining the balance between the various voices was absolutely
critical to the structure of the pieces but nearly impossible to pull off using
Rosegarden's original configuration. That's what finally drove me to do
something about it.
I hope that someone else might actually find such a feature useful, and that it
wouldn't serve only to add more clutter and confusion to an already complicated
project.
Tim Munro
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
