Hi everybody ... breaking the silence... :) Benno was stressing me for a while to make the option for max. voices and disk streams a runtime option, rather than a compile time one, as its currently the case. I guess I'm going to implement that soon.
The reason why I postponed this for a while was, because I was unsure whether I should implement a simple solution, like setting the max. voices / streams globally for the whole sampler..... or making it an option on a per engine instance basis. The simple solution (globally) would make it an "untrue" value, at least if more than one audio output device is used in the sampler. Because, as you might know, for each audio output device, a separate sampler engine is created and each engine has its own counter for limiting the amount of voices and streams. On the other hand, making it a per engine option would probably mean a lot of overhead work, both on backend as well as on frontend side. Since e.g. on frontend side one would have to implement something like an engine instance parameter browser. Not sure if its worth it ATM. What do you guys think? CU Christian ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
