Hi ,I would like to know what is the procedure to import waveforms to use as oscillators in Z3TA+. I read the manual and it didnt go into how to import waveforms to use as osciallators...  Any help or info would be much appreciated.  Thanks

Right-click on the program button, and select 'Load User Wavetable (.wav)' from the dropdown list.
 

 
It must be a mono .wav file, of any sample rate, up to 64,000 samples in length.  The information can be found in the compiled Release Notes 1.1~1.4.rtf, under z3ta+'s Documentation subfolder.  For more techniques, and a process for transforming waveshapes using z3ta+ alone, see Steal This Waveshape (Part I).

 Thankyou very much for this info b.rock

b rock
The information can be found in the compiled Release Notes 1.1~1.4.rtf, under z3ta+'s Documentation subfolder.  For more techniques, and a process for transforming waveshapes using z3ta+ alone, see Steal This Waveshape (Part I).

This article is since long gone also from the internet archive, but I assume it's the same one that is available in pdf format here and that contains both part 1 and part 2. Get it now before it's removed, as it seems to be in a subdomain part of the site that isn't really up.

 
This article (and this thread) refers to z3ta+ and not z3ta+2.  In case someone wants to do similar things with z3ta+2, you should be aware that there is what might be considered a bug in the way z3ta+2 exports and imports wavetables (and perhaps in z3ta+ as well ?).  I don't know if this is still the case in the latest release of z3ta+2.  Quoting myself from a previous thread :
 
The waveshaper wants its wavetables normalized to -6db or it won't shape properly.  However, the waveshaper exports the wavetables at 0db.  So, after exporting a waveform, you have to use a wave editor to normalize it to -6db and then it will behave properly once reloaded.
 

Paul P
 
This article (and this thread) refers to z3ta+ and not z3ta+2.  In case someone wants to do similar things with z3ta+2, you should be aware that there is what might be considered a bug in the way z3ta+2 exports and imports wavetables (and perhaps in z3ta+ as well ?).  I don't know if this is still the case in the latest release of z3ta+2.  Quoting myself from a previous thread :
 
The waveshaper wants its wavetables normalized to -6db or it won't shape properly.  However, the waveshaper exports the wavetables at 0db.  So, after exporting a waveform, you have to use a wave editor to normalize it to -6db and then it will behave properly once reloaded.

Thanks for the reminder and for the solution for Z3TA+ 2. I just assumed it was very similar. I did have odd results from my first waveform import and wondered what the prerequisites were for waveforms.