Sure, but there are various ways of handling that, if it's a direction the designer chooses to go in.pdxindy wrote:It is nice for people sharing presets that any Diva or Zebra preset can be shared with any user of that synth... with a bunch of paid modules, you would never know what preset might work.
For example, it's possible to share sysex patches of hardware synths, which refer to PCM waveforms on cards/cartridges that the user may not have. In this the simplest case, the patches just don't sound right.
Better that patch has some indication, note or filename reference where a particular optional resource is necessary. Better still the synth itself knows that a patch requires a resource a user doesn't have installed, and either visually shows a notification of this (eg, the patch is shown in a different colour, or makes the patch not loadable, or whatever.).
Other ways too, it's not insurmoutable, like I say *if* Urs wants to go down that avenue (I'm not sure he does, but these decisions can get complex when they affect multiple products, existing and new users etc)
