Of course it would be better to make it configurable, but the question is what if the need arises to work with 2 instances at the same time, one with 2 channels and the other with 16 ?cuse wrote: I'm not convinced of that multi-DLL approach. I would simply make it configurable. By default 2 channels and the user could override it either with JSampler / QSampler or a separate app which we could include in the start menu entry. After the user changed the setting, he has to restart the plugin and he would have the desired amount of outputs.
The question is why Kontakt is using this approach (one DLL with 2 output channels, one with 16 outs). Was NI just lazy or are there cases where the user purposely wants to use the two DLLs at the same time ?
or one could implement cuse's suggestion by providing a config file for each DLL.
for example
linuxsampler.dll (2 outs)
linuxsampler.dll.conf is a textfile that contains
outs=2
(amongst other parameters if needed)
linuxsampler_16outs.dll (16 channel version)
linuxsampler_16outs.dll.conf contains
outs=16
that way the user can simply create as many DLLs he wants and using them all at the same time.
just copy the DLL with anothert name, create the config file, set the number of outs. (could be done via editor or by external app)
then at load time the DLL just looks for a file DLLNAME.conf and reads the parameters from that file and sets the numbert of outs.
what do you think cuse ?
ggoodesa: using VST DLLs with many output channels could decrease performance due to more memory copying operations. the DLLs does not get bigger or uses more memory though.
Therefore ideally we should just use as much channels as needed.