Ocean Swift - Wavetable Compatibility Converter | use your wavetables with all your synths and modules!

[faxinadu]

After the great response to our Wavetable Creator we have released another wavetable tool, a small but crucially missing piece in the sound design landscape!

Wavetable Compatibility Converter has one job - to convert wavetables files that have one frame size, to another frame size.

This empowers you to use wavetables that you have in one specific format across all your other wavetables, synths, modules and plugins.

It also empowers you to create wavetables in tools other than our Wavetable Creator, such as in Vital (exports 88khz files) or in WaveEdit (exports 256 frame files) and use them anywhere!
The conversion is of very high quality - perfect for professional grade useage.

Ocean Swift - Wavetable Compatibility Converter 1.0.2 - File Loaded Frames Screenshot.png

Key Features:
- Convert wavetables in high quality between frame sizes for full flexibility - use your existing wavetables anywhere.
- Automatically embed loop points for compatibility with Surge XT, VAZ Modular, and more.
- Export multiple formats at once to optimize your workflow.
- Automatically generate Serum-compatible FolderInfo.txt files for batch exports.
The application uses advanced sinc interpolation with a 512-sample kernel and a Hann window, ensuring pristine conversion quality.

Best of all - it's just €10! Simple tool, simple price, does the job!

Has a look here, check out our small trailer video and grab your copy and further enhance your Wavetable tools arsenal! ->
https://oceanswift.net/product/wavetabl ... converter/

Let us know if you find any issues, if you need any additional frame sizes or other particular details in order to make this even more useful for you.

Thanks for the support and happy wavetable-ing!

"You can't stop the waves, but you can learn to surf." - Duke Kahanamoku

Ocean Swift - Wavetable Compatibility Converter 1.0.2 - In Action Screenshot.png

[kääriäinen]

Is there a tool available that shows what is the frame size of the wavetable or is it possible to add automatic frame size detection of the imported wavetable?

[kääriäinen]

Is there a tool available that shows what is the frame size of the wavetable or is it possible to add automatic frame size detection of the imported wavetable?

I´m asking because I have downloaded wavetables all over the internet and I'm not aware what is their frame size

[faxinadu]

Is there a tool available that shows what is the frame size of the wavetable or is it possible to add automatic frame size detection of the imported wavetable?

I´m asking because I have downloaded wavetables all over the internet and I'm not aware what is their frame size

Good question, that is indeed sometimes hard to tell if you don't know it beforehand.

- If you know the number of cycles but do not know the number of frames per cycle, you can open the file in a wave editor e.g. Wavelab and set the timeline to show samples. You will then get the total samples and you can divide by the number of cycles and get the frame size.
- If you know which synth or editor they came from these usually state somewhere what the frame size is.
- If it includes simple wave shapes e.g. sine, tri, saw you can with the same Wave Editor flow try to find by eye what is the number of samples for one cycle. This is totally unreliable though once the shapes are more complex.
- If you're lucky some wavetable files might have a loop point set at the end of the first cycle, then with the same Wave Editor flow you can highlight that loop section and you have your frame size.
- If you're lucky you might have a FolderInfo.txt (Serum generated), playlist file (e.g. Disting) or some other file next to them that indicate the frame size.
- Last resort would be some sort of trial and error. E.g. say you have a wavetable that is an unknown size but you know for a fact it loads correctly in a certain synth (or at least lets say you are happy with how it sounds there and want it to sound the same somewhere else). You could try with the app to set the "original frame size" to various things, export to the new size that you need and then load on the new synth and compare visually and sonically to how it sounds and looks (original wt on original synth, new wt on new synth) until its right.

I have been thinking of ways the app can maybe estimate, but its a bit tricky - even reading out the loop point depends on the wave header being formatted correctly, and if it even exists.

[faxinadu]

Updated to now support Mac ARM, Mac Intel, Linux ARM, Linux Intel, Windows.

1.1.0
ADDED Mac build are now notarized by Apple
ADDED Mac Intel support
ADDED Linux Intel support
ADDED Linux ARM support