What are some of the better software Wavetable synths?

[blacktomcat666]

Komplexer WT files have a very simple format: The only include the amplitudes for the harmonics of the additive synth (+/- 4096.0, stored as 32 bit floating point number),nothing else. These values are ordered as follows:

Slice 0 [Harmonic 0 - 63],Slice 1 [Harmonic 0 - 63], .....,Slice 32 [Harmonic 0 -63]. Komlexer has only sinewave - generators in the wavetable oscillator, that's why resynthesis results will look and sound a bit different from the original.

This is very different from Surge WT files. In Surge, a wavetable is stored in "time domain", while in Komplexer it's stored in "frequency domain". And that's the reason why Komlexer is more an additive synth (like a Kawai K5/K5000) than a wavetable synth. And it's the reason for the existence of K - term (now: Audio - Term). You must use FFT analysis or additive synthesis to build Komlexer wavetables.

Isn't that exactly the behaviour of ALL the PPG/Waldorf wavetable synths?

As far as I know PPG/Waldorf wavetables were stored as time domain(until MW1 only the first half of a waveform in a wavetable entry, the other half was mirrored).

[fmr]

I said that because the SoundDiver module for MW and MW II had a wavetable editor where the waves were edited using additive synthesis, and we could even perform analysis and resynthesis, creating an entirely new wavetable.
The fact that only the first half of the wave is stored is because the second half is created by mirroring the first half, which would not collide.

[blacktomcat666]

Komplexer WT files have a very simple format: The only include the amplitudes for the harmonics of the additive synth (+/- 4096.0, stored as 32 bit floating point number),nothing else. These values are ordered as follows:

Thanks for the info!
I'll probably end up supporting that, considering that in Harmor (yes, too an additive synth) I too only need the harmonic amplitudes & not phases (well, they all share the same initial phases, so if I were to read cycles in the time domain, I'd keep the phases of the first one).
(but I see you say it allows negative amplitudes, thus half-phases)

So it's always 64 harmonics?

Komlexer always uses 64x33 harmonics, so the files - written in 32 bit float - are 8448 bytes exactly.

Kterm uses the phase information in a similar way. First it calculates the magnitude spectrum for each slice using sqrt(real^2+imag^2).

Then it scans through each of the 64 harmonic envelopes and sets inital polarity for all following non-zero values in the envelope, using atan2(imag,real). This setting is repeated every time a zero value followed by a non zero value occurs and it's done for each harmonic envelope independently. This avoids "wobbeling" sound also as a too "sawtooth - like" sound.

Sorry for my complicated writing, my english is a bit poor.

[blacktomcat666]

I said that because the SoundDiver module for MW and MW II had a wavetable editor where the waves were edited using additive synthesis, and we could even perform analysis and resynthesis, creating an entirely new wavetable.
The fact that only the first half of the wave is stored is because the second half is created by mirroring the first half, which would not collide.

Hm.. I could imagine the waves where rendered (into a midi/sysex file) and stored as time domain data in the MW's memory. I think MW II has full waves in each wavetable entry, that's why "pulse width modulation" tables were possible.

[gentleclockdivider]

I'd say the audio table module in reaktor

Actually, there is a wavetable synth in the Reaktor factory library, and there is one in the user library that emulates the Microwave XT. This amonge several other wavetable scanning instruments

no really ? just kidding .
I just wanted to say that it's a lot more fun making your own wavetables with the audio table module ..
As far for the waldorf xt emulation , the only thing in common with the hardware is the gui , really don't like that ensemble

[highkoo]

If only they had been defined using a standard wav marker using a new marker ID (like 'wtsc'), then it would be clear when a wav file is a wavetable & each single-cycle would be clearly marked.

I think that is how Massive must work with them because the wavs have markers/regions defined when extracted, and not all the tables contain the same number of wavs.

"I WANT TO BE ABLE TO IMPORT WAVETABLES INTO MASSIVE"

Yeah... +1
Im guessing they play dumb and v2 just has some new fx or something.
What they should do is make it like Zebra and let us load single cycles in slots around the osc knobs, and then add an option to interpolate from end to end if need be, etc....
Fukk itd be perfect.