Hello,
Sure, it makes sense.
As for manually putting the files in a given folder, this would be more like a developer feature, right? We could say that if there is a new stable sample package, this would come with a plugin update and the user only needs to upgrade it.
Thanks for the patch, I will have a look and merge it accordingly. From what I saw from the surface, it was basically some path adaption for the MOD and one bug fix.
We do not have such thing in place though, and the amount of data needed for the full plugin is bigger than what some devices are even able to install anyway so we cannot tie the 2 together.
So the installation of sfz/wav files needs to be optional.
Main question is how to make this as simple as possible…
I’m working on an original soundfont and at the moment is playing well in Sfizz. I didn’t make intensive tests to see if it dies badly with a lot of poliphony etc. I kept the soundfont size not too big (160MB) so that I can use ARIA sfz opcode hint_ram_based=1 (that is recognized by Sfizz) to load all the files in ram. For a decent electric piano (better than the ones already existing in the mod store) that’s enough. If anyone is interested I can share the soundfont for helping in testing Sfizz. Pre-requisite is that you’re able to copy files on your Mod and you can install Sfizz from beta.
@falkTX sfz opcodes can map to CC some features. For example on my custom sfz file I have
<global>
// Lfo modulated pan & pitch
lfo01_wave=1 // Sine waveform on lfo 1
lfo01_freq=0.5 lfo01_freq_oncc14=20 // Lfo 1 min, max frequency [Hz] controlled by cc14
lfo01_pan=0 lfo01_pan_oncc15=100 // Pan min, max depth [%] when modulated by lfo 1 and controlled by cc15
lfo01_pitch=0 lfo01_pitch_oncc16=50 // Pitch min, max variation [%] when modulated by lfo 1 and controlled by cc16
I cannot hear them working. The same controls work with linuxsampler with the very same soundfont. I need to recall from the mod-host features if CC messages are “captured” and not sent to plugins. If not the case I will open an issue to Sfizz on github!
NOTE: sfizz prints by default when there are some unrecognized opcodes, that’s not the case
Thx
the sfizz plugin in the beta section of the store is old now, you should try if the same works if you install the official binaries.
they recently released the plugin as v1.0, so they consider things to be stable enough for initial version.
mod-host does not intercept any CCs. it will intercept the midi tempo stuff, but not anything else.
Thanks, I’m running Sfizz on my custom board and I’m using version 0.5.1. I have seen now the 1.0. I’ll try it and get back
So I’m using now Sfizz 1.0. I’ve seen lfos are still unsupported Add support for LFOs · Issue #150 · sfztools/sfizz · GitHub. However I was able to cascade a few plugins in Mod to obtain the same effects.
An audio demo of the soundfont here SoundfontTestSuitcaseMarkI by Massimo Pennazio | Free Listening on SoundCloud
It’s sounding really cool man!
Is this something you would like to have integrated into SimSam? Are the samples available somewhere?
Sorry but I never tried SimSam, can you tell me differences or improvements over Sfizz? Why I would need to encapsulate a sample in a plugin shouldn’t they remain in a separate folder?
This is what I do on current Aida DSP OS builds: I keep the samples in a path that can be mounted on usb with mass storage upon request for file transfers. So I have all the sfz files together. Since at the moment I don’t have integrated the latest version of mod-ui which supports file explorer, I have a bash script that creates the lv2 presets for Sfizz so that all the samples on board are selectable. Problem of course is if a user add another sample of his own. For this reason I will work on integrating latest mod-ui version.
As of now SimSam simply follows a different approach than sfizz. It comes from a time before official file handling support. I just thought you might be interested in having this integrated to SimSam as you posted in here 
Of course, if you share your samples they could be added in a modular approach to sfizz as you described above.
Any updates on stability of these plugins?