Just gone up on github for those of you as impatient as me 
8 Likes
Just had a play with this. I think I’m in love.
2 Likes
How do I download it? Please!
For now, you’ll need to grab the source from github and compile it yourself. It will appear in the library soon.
1 Like
thanks sounds hard, i’ll wait but thanks.
1 Like
genio
It’s just turned up in the normal library for me. Now to dig in.
3 Likes
Am I right in understanding that the wavetables are at most 256 samples per wave and at most 64 waves?
my first try with terrorform:
I’m streaming it right now here: https://www.twitch.tv/dag2099
So far I’m finding to be very 80’s but it’s a super complicated module. I’m trying to read the manual while streaming, which seems to be a bad idea.
edit: stream over
If I’m not mistaken it is 64 waves per bank (x 64 banks).
There was a recent change to the module which should allow it to load 2048 cycles waves. This might not have been changed in the manual yet.
Check with @valley.audio
Hmmm… I tried making a simple two wave table with 2048 length waves as well as trying to load a Serum table with six waves and couldn’t get it to see the full lengths, and the limits I got by reading the constant definitions in the source. (i.e. TFORM_MAX_WAVELENGTH and TFORM_MAX_NUM_WAVES) Maybe this is on a branch or something in the works.
That is possible!
I really love this new module, so many waves! And I connected it to transit for some jumps (faded) between different sounds. Thanks Valley!
1 Like
Already discussed this in a PM, but yeah I am working on adding Serum compatibility where tables can be compressed / downsampled during loading. It’ll be limited to integer downsampling, e.g. 2048 -> 256 is 8:1, and this compresses nicely.
4 Likes
To no-one in particular, but is there a way to find out what kind of wavetable is “inside” the wav file ?
4 of these I know how to find out the rest ?
How do you mean? Like what the cycle length is?
Yes, the cycle length inside the wav if its a 2048samples or something else ?
I’d use an audio editor like Audacity to visually inspect the WAV file, switch to show “selection length” as samples (numbers at the bottom), zoom in and see if the cycles line up nicely to either 256, 512, 1024, or 2048, assuming the table actually used a power of 2 as it’s cycle length (Adventure Kid waves for example don’t line up!).
It is then fair to assume that the entire lot of wavs from that same collection is consistent, but always worth a check.
In Terrorfom you’ll be able to see straight away in the Viewer if the table did not line up correctly.
1 Like
Thank you so much, so it’s basically a visual activity 