Reading thought threads here most issues with sfizz were resolved otherwise already. Otherwise I found this:
- 2109 Sfizz vs LinuxSampler Audio : Don’t know if the user resolved that behavoiur somehow.
- Then there is this thread mentioning Salamander Piano being linuxsampler optimized. In the same thread finally users reported that it worked good meanwhile, and the repo now states that the piano is now Sforzando optimized. There is also this NoctSalamander which I can say works great on sfizz.
- Reading through the (un)supported opcodes in sfizz: Regarding only opcodes which are widely used in real world examples, unsupported are mostly modifiers (CC/random → parameter, like filters, effects, veltrack and so on) and curve shapes. In most cases the instrument would be usable anyway. I did not find that in real world, but a problematic case would be eg. if someone would use the cutoff2 filter (set_cc74=127 cutoff2=100 cutoff2_cc74=9600), so the cutoff will be fixed to an unusable value. But: cutoff2_onccN works, cutoff works with all opcodes, and the most common cc modifiers (–> ADSR/filter ADSR/filter/LFO/pitch/volume/offset etc.) work.
But I’d be really interested in practical problems with sfizz.
Yet another pro for sfizz would be, if it would support DecentSampler presets by default. I’ll test that. SFZ sharing thread - #26 by hannesmenzel