On 01/27/2013 08:15 PM, David Henningsson wrote:
On 01/27/2013 09:35 PM, Aere Greenway wrote:
David and all:
One more thing I need to know, to try different values for the
"synth.overflow.volume" parameter, is what range of numbers are produced
from the "volume_score" and "attenuation" calculat
On 01/27/2013 09:35 PM, Aere Greenway wrote:
David and all:
One more thing I need to know, to try different values for the
"synth.overflow.volume" parameter, is what range of numbers are produced
from the "volume_score" and "attenuation" calculations. Is tho
"volume_score" just the value from t
On 01/27/2013 12:37 PM, Element Green wrote:
On Sun, Jan 27, 2013 at 11:07 AM, Aere Greenway
mailto:a...@dvorak-keyboards.com>> wrote:
If you could please explain more precisely what you mean by 'per
voice', it would help me a lot.
A voice represents a single audio sample being play
On 01/27/2013 12:37 PM, Element Green wrote:
On Sun, Jan 27, 2013 at 11:07 AM, Aere Greenway
mailto:a...@dvorak-keyboards.com>> wrote:
If you could please explain more precisely what you mean by 'per
voice', it would help me a lot.
A voice represents a single audio sample being play
On Sun, Jan 27, 2013 at 11:07 AM, Aere Greenway
wrote:
>
> If you could please explain more precisely what you mean by 'per voice',
> it would help me a lot.
>
>
A voice represents a single audio sample being played back. A single
note-on event may trigger several voices, if an instrument has la
David:
I am starting to test the "synth.overflow" parameters, but find I still
have a point of confusion.
I have always been thinking on a per-note basis, in which case, the
situation is easier to understand.
But where the algorithm is "per voice", I am having problems
understanding how it
