j9k,
I really am quite a fan of your modular matrix, along with other dev's you use to bring us before I became a member. Your Mod matrix is a great tool in Morpheus Vers. II. So many options. This is a perfect tool for tweaking synth parameters, and routings. Afterall most of us can never return to generic hardware after experiencing SFP. Hope you have returned to bless us with your well designed workarounds, and modifiers.
On 2006-09-18 17:47, j9k wrote:
the only wavetable player is the waldorf one. you can open them in wavelab and edit them. they are labled wt**.dsp in the dsp folder of your install.
i don't know what format they are but still fun to play with.
j9k
<font size=-1>[ This Message was edited by: j9k on 2006-09-18 18:06 ]</font>
The wt**.dsp files are just modules with an integer array of 2048 entrys. You can create them quite easy. Also you can copy all data from an wt** module to your own module by connecting both arrays.
But what exactly do you mean by edit them in wavelab?
<font size=-1>[ This Message was edited by: olase on 2006-09-19 06:17 ]</font>
if these were raw wavetables in one form or the other, then someone would have come up with an editor long time ago
To me they look as random as any other encrypted module
Maybe an sdk user only tool/module would be the way to go with this? To go down that line would require the module to be as close to perfect as possible, but it could maybe even be open to a certain extent. Any thoughts?
now do you talk about the wav oscillator or a wav-2array converter.... that really converts a wav file into a .dsp file?
it looks like easter time. we search the eggs....
would say the probl. is not to fill an array with data whatever;
probl. is to fill it with data that makes sense in realtime!
for ex.
if blowing the audioIn into an array;
where to start where to stop recording?
without an editor for manual selection its sort of random
