Re: [Linuxsampler-devel] Re: Gigasampler curve types

[<be...@ga...>]

Scrive Simon Jenkins <sje...@bl...>:

> Mark Knecht wrote:
> 
> >   Another 'bug' I notice, or maybe a limitation of the GSt coding, is
> >that the first 2-4mS of a new pulse has the volume of the pulse
> >preceding it, and then the right volume. I want to look at this more
> >later. I'm wondering if this could be some psycho-acoustic thing they're
> >doing? (More likely just a mistake...)
> >
> Maybe they're lowering latency by starting to play a note before they've
> seen the velocity byte? Even after they've seen it - depending on how the
> engine works - they might have some just-in-time fiddling around to do
> before they're ready to make use of it.

that would IMHO be totally silly.
You would save about 300usec (transfer time of 1 MIDI byte) plus
what if you play a loud C1 and then a very soft C4 ? I guess this 5msec
part of loud C4 would be very disturbing (if really present).

Even this velocity curve quantization looks silly to me, it will make
note volumes more static thus I think it will hurt to note dynamics during
playing. Let's do it right (mapping the approximate curve but without
 quantization).

cheers,
Benno



-------------------------------------------------
This mail sent through http://www.gardena.net