Well that's what the code says :) This is the mechanism used by the 'stop' button (and currently only this button) to stop all sound. However it tries to do so fairly gently by making a graduated fade out. But this is articulated over the time of one buffer, so if you are running at 44.1k with a (total) buffersize of 2048 frames, that will be 46.4mS, but with 96k and 128 frames it will be 1.33 mS.
I don't know how important this is, but I can think of a relatively easy (and computationally benign) way to make the fade work over a fixed time. The question is what sort of time should we head for? 1.33mS is likely to result in quite a loud click, and even 46.4 isn't ideal if we are interrupting a strong bass note. So, do we head for something like 100-200mS? Or do we not bother at all? As usual I have an ulterior motive for asking :p If this works, there are a number of other situations I can think of where such smoothing could possibly be applied. -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Yoshimi-devel mailing list Yoshimi-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
