There is a new branch 'padthread' The details are a bit different from what I proposed, and a fair bit of cleanup is needed. However it does the job and seems to be unconditionally stable :) This is with me jumping around in PadSynth while the instrument is playing in a 12 part project driven by Rosegarden.
Setting a *very* big wavetable while monitoring memory, you can see the changes taking place while listening for the point the sound actually changes. Depending on how dramatic the change made, sometimes you don't even hear a click. One unavoidable 'feature' is that you briefly double the amount of PadSynth memory used Interestingly you can now immediately hear the effect of changing buffer sizes etc. One thing I don't understand yet, is that if you significantly *reduce* either the samples/octaves, or num octaves while padsynth is sounding the sound stops. Loading a part will still silence the instrument, but that's overall as before. However, a very large wavetable doesn't block anything and if you have a multi-engine instrument, and keep playing you actually hear the non-PadSynth engines start immediately, while the wavetable is still being built :) Finally, I've used a C++ thread here instead of posix - much simpler to set up. -- Will J Godfrey https://willgodfrey.bandcamp.com/ http://yoshimi.github.io Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. _______________________________________________ Yoshimi-devel mailing list Yoshimi-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
