(Same old) new problems in V 1.150
Posted: Wed May 06, 2020 8:50 am
V 1.150
"Sample data spill over into other again (similar like in V 0.990)".
Especially if I use short unlooped samples (like drums) it spills with other samples, after saving a soundfont.
As far as I can tell the problem appears, if you have mono and stereo-samples (like drums) combined together in an instrument.
Either you only use mono or only stereo samples to fix the problem (I recommend stereo samples).
Viena 1.150 and Plogue Sforzando_x64
Sforzando can`t read/convert soundfonts into sfz anymore, created with Viena V 1.150.
No matter if you use a simple single instrument or a complex soundfont-kit.
Remedy here is the use of an earlier Viena version only.
(For some reason, Sforzando deactivates "loop points" arbitrary where are none. Especially on mono-samples/one-shot sample without loop points.
I think this is a Sforzando-problem `cause such a problematic soundfont runs flawlessly inside a VST3 compiler, but the "spill problems" can also be found here.)
V 1.150 caused serious problems for me, so I preferred to go to an earlier version to be full VST3 compatible when programming VSTi`s.
"Sample data spill over into other again (similar like in V 0.990)".
Especially if I use short unlooped samples (like drums) it spills with other samples, after saving a soundfont.
As far as I can tell the problem appears, if you have mono and stereo-samples (like drums) combined together in an instrument.
Either you only use mono or only stereo samples to fix the problem (I recommend stereo samples).
Viena 1.150 and Plogue Sforzando_x64
Sforzando can`t read/convert soundfonts into sfz anymore, created with Viena V 1.150.
No matter if you use a simple single instrument or a complex soundfont-kit.
Remedy here is the use of an earlier Viena version only.
(For some reason, Sforzando deactivates "loop points" arbitrary where are none. Especially on mono-samples/one-shot sample without loop points.
I think this is a Sforzando-problem `cause such a problematic soundfont runs flawlessly inside a VST3 compiler, but the "spill problems" can also be found here.)
V 1.150 caused serious problems for me, so I preferred to go to an earlier version to be full VST3 compatible when programming VSTi`s.