i'm a noob... i have sdk since 3 days, but i have just discovered this.
1) you can load modular II/III modules into SDK projects
1 bis) ok, you probably already know this
but what about...
2) in the project tree, if you move "modular view" into the "panel" subtree, you will see (and can use) the modular module surface into the panel once you open it!
this goes directly to
3) you can load the modular II/III modules: SAMPLEPOOL, SAMPLEOSCILLATOR and then, form the surface, you can load samples into the pool, and then move the sample you have loaded into the sampleoscillator module.
in this way you can manage mono waves, and you don't have access to multisampling, but it's better than nothing!
moreover, you can load only the SAMPLEOSCILLATOR module, assign a button to the surface to the "Load sample" button of the module itself, and load the sample from the synth surface without having the modular view on the surface itself...
now, we'd need a stereo modular player, or a way to manage multisamples!
how to use modular to make custom wavetables!
Re: how to use modular to make custom wavetables!
registry is recuiered ...... for the moudular moudules ,,, !!
B were
B were
Re: how to use modular to make custom wavetables!
in vsti instruments they have a sf2 or sfz osc
which is a multisample player it loads the sample containers of sf2 or sfz
there are millions of samples in this format and they are read by emulatorx kontakt
wusicstation
dimentionpro
sfz player
soundfont osc in lots of vsti free and paid
and many others
and with these files you dont have to set anything as all tune and loop info is set in the container files
which is a multisample player it loads the sample containers of sf2 or sfz
there are millions of samples in this format and they are read by emulatorx kontakt
wusicstation
dimentionpro
sfz player
soundfont osc in lots of vsti free and paid
and many others
and with these files you dont have to set anything as all tune and loop info is set in the container files