Why not use SFZ opcodes and import the SFZ format. It would be really easy, since most of it is done for you, and many people have created their own SFZ parsers. You'd be able to see how it was done very easy. Furthermore, this would allow users to import and share a TON of existing samples for the ultimate flexibility.sheaf wrote: Wed Oct 15, 2025 3:15 pm Quick update: I think the next build could be a release candidate for version 1.0, so the code is nearly there. I've made almost 80 presets so far. I'm not 100% decided yet, but my current idea is to make 128 in total for the initial release. Not a lot, but enough to showcase the capabilities I guess. I wonder if this is a good idea though, because factory preset libraries influence my own purchase decision quite a bit. I like making presets as a synth user, but it also takes a lot of time so if I'm going to be dropping money on a synth I want a lot of new sounds out of the box. Especially if it's a synth with a lot of controls, like SWAY. The idea that I would spend more than 4 years on this project and then people aren't buying it simply because I didn't take the time to make enough presets...
Question about custom samples, for in the future: there are several ways I could go about it and I'd like to hear your thoughts. I could make it so you can import audio files on the spot specific to the patch you're working on. It can take quite some time for the user to make an actual multisample with different zones and optimal loop points though. So you'd also want the ability to easily reuse a multisample you've created. I could add some special folder where custom multisamples could be saved for reuse, similar to what the INTERNAL waveform source does on a SY99. Both of these things require me to make a full blown multisample editor within the plugin, and this is going to take a huge amount of time. Many months in my estimate. It would also mean I have to change the patch structure to allow for custom samples that are either linked or embedded, which complicates things a lot.
Another way is this: I just make an external expansion card editor. This way you can only add custom samples by making custom expansion cards. It's less flexible, but it would massively simplify everything. The plugin itself wouldn't even have to be changed, since it already supports expansion cards right now! An external editor means that you could still open it from the plugin, but it launches an external Windows/Mac app in a new window outside of your DAW. When you save changes to your card you refresh them in the plugin and you're good to go. I could probably make this external editor in 4 weeks or so, because I can use web technology which is just easier and faster.
Thoughts about this? Would the second option disappoint you?
