New Release: Wavefield v1.0.0 by Fine Increments - Wavetable-based Spectral Filter (VST3/AU/AAX)

[Tj Shredder]

Congrats to the release. Its a beauty…

I think being able to modulate the window position rather than just the end points would improve wavefield quite a bit.

i am spoiled with modulation possibilities in Bitwig, and thus I simply modulate/automate start and end together…

[TheMaestro]

How is this different from Kiloheart's ShaperTable?

ShaperTable wasn't vibe coded with Google AI Studio.

[fineincrements]

This thing is awesome!

Really interesting effect processor (in a sea of analogue emulations) - I've just been running saw/square waves into it with some hand drawn wavetables, and running the output into amp sims/distortions whilst automating Skew and Pos parameters - so many gnarly basses!

Kinda makes WT synths almost redundant, just turn any sound into a wavetable sounding thingie-majig.

Thanks so much BozzR, glad you're finding Wavefield useful! It does work really well with bass and downstream distortion. Don't go deleting Serum just yet though haha, but yeah any sound could potentially benefit. I think it works the very best on sounds that are rather solid and static, and basses can definitely tend to be that way. but also drums, held synth chords, long vocal notes

[fineincrements]

This plug-in is unique, and it's way more versatile than I expected. It's not a one-trick pony either. Even subtle shifts sound amazing, and it's an effective stereo tool as well. I've spent a few hours with it, and I've noticed that certain settings are downright funky. I'm using it to process drums from Microtonic, and the results are extremely rhythmic and addictive.

I initially started with an ambient type of track, because I wanted to hear how smoothly it morphs through spectral curves. To me it sounds buttery-smooth, and can sound quite beautiful. But it's not limited to mellow music. It's capable of completely twisting percussion loops with Microtonic, while adding exotic harmonics and interesting stereo tricks as well. These features look well thought out, with convenient touches like a Safe Bass setting and more. This thing is cool!

I'm always keeping my eye on new start ups and indie developers. I think there's a big pool of talented people who have really good ideas. It takes some courage to develop plug-ins that actually offer something different, especially in a market that is already so saturated. But so far, Wavefield is proving to be totally worth the price of admission. I'm impressed, and there's still more to explore.

Congratulations to Fine Increments, on a great 1.0 release!

Thanks so much morphex for the glowing review and acknowledgement! I aim to provide value. In magnitude mode, Wavefield preserves the original phase between dry/wet so it can sound clean and buttery like that, and be suitable for everything from vocals and orchestral music to neuro bass.

Glad you noticed the stereo feature - pretty proud of that one. It takes advantage of the unique architecture and offsets the position of spectral shaping between L+R channels. You know how in mixing, stereo width is often created by using eq's in M/S or creating different eq profiles in each channel. Wavefield creates distinct continuously evolving spectral profiles in each channel. I haven't seen anything else that creates stereo width in this way. the tradeoff is you can't expect the same amount of stereo width at a given position with each wavetable. because the width depends on the rate of change frame-to-frame in the wavetable itself.

I think you're absolutely right there are still so many ideas to explore, and I like the idea of creating plugins around a single unique core idea, instead of trying to make them do too many different things. By not allowing a single unique essence to shape the development, I think you end up with a lot of delay plugins in your folder, each one having one feature that's a little different or improved.

Appreciate your support!

[fineincrements]

EDIT - working when I switched browser

love to try it but the download dialog is not giving me access

Thanks for calling out the browser issue, sorry that happened. I think I may have just fixed the problem. Please let me know if the original browser works now! If not, it would really help for other users if I could know what browser is failing, what you're seeing exactly when it happens, and if you have any ad blockers / extensions enabled, incognito window, or anything else unusual like that.

[DCrown]

How is this different from Kiloheart's ShaperTable?

ShaperTable wasn't vibe coded with Google AI Studio.

Are you sure? How do you know?
I had to google
"Vibe coding" in Google AI Studio allows users to build functional, full-stack applications by describing ideas in plain English, powered by Gemini 3 Pro and agentic workflows. It turns prompts into apps, including database and authentication integration, without requiring deep coding skills"

If that's true, well, I am not going to support or pay for no skills for sure".

Btw Kvr made a forum for AI stuff to keep this forum clean.

[fineincrements]

ok, on demo. Just running a WT synth sequenzed from HW.

Sounds great. Even on the sequenzed WT Synth ( Waldorf MW1)

Key to make it work for me is in this case to deal with WT start and end points. Make it shorter!

Looks like a quite useful -and definitly funny- plugin for me.

- - - - - - - - - - - - - - - - - -

already a feature request:
- Instead of having WT Start/End and Trim parameters would i turn these three into just: WT start/lenght
- as is is jamming around fiddly.
- probably as a a 2nd mode option. But i don`t see what somebody could lose with such a parameter arrangement ?
- that mode would allow for much quicker handling. And: better jamings

Hey Funky40, I do see your point on how it could be implemented to behave similarly with two parameters. I'll add this to the tracker and see what I can do.

[fineincrements]

i`ve checked it re. live play and Piano:


Now comes the caveat re. live playing:
- it has a reported 90ms Latency (48khz)
- i can bring it down to 30ms by hosting it in "Patchwork", at 4x oversampling. 30ms
- i can bring it further down at 8x oversampling. 18ms (leave out CPU usage)


Now the next caveat:
- it is not really working hosted within "Patchwork"
- the waveform display does not work when set to "db" visual mode
- several parameters stop working also- WT start/stop/Trim continue to work. Others don`t !
- maybe patchwork is clamping those off. Not checked further.....Not donne any CC mapping within PW

Soundwise ? can be fun with Piano....and some manual "Dry-Wet" jam wiggling for example. Sounds good.


Nice plugin. Not exactly made for live play uses ( i see the context). And it seems in an quite early stage.
Definitly fun on sequenzed instruments. I really like it.

Thanks for the detailed report, and I'm glad you like it overall! A few notes:

Latency: The roughly 90ms at 48kHz is correct and inherent to the spectral processing architecture - Wavefield uses a 2048-point STFT with 50% overlap, so the pipeline needs 4096 samples buffered before output begins, plus a 5ms limiter lookahead. That's just the physics of frequency-domain processing at that resolution. Reducing the FFT size would lower latency but also degrade the spectral resolution that makes Wavefield sound the way it does. I originally tried it at 1024, and liked the transient handling better but couldn't stand the low resolution in the bass frequencies.

Parameters/display issues in Patchwork: This sounds like a Patchwork hosting issue rather than a Wavefield bug. Patchwork's parameter bridging may not be forwarding all automation correctly - the fact that some parameters (WT start/stop/trim) work while others don't points to something on Patchwork's end. The dB display relies on real-time data from the processor, which may also be disrupted by how Patchwork manages the editor/processor relationship. It sounds exactly like what happens in DAWs like Logic that don't call the processor block when transport is stopped, or if there's no underlying audio file to process at a given moment. Patchwork may stop calling the processor and that would explain most of what you're seeing.

Wavefield wasn't designed with live performance latency in mind, but I appreciate you pushing the boundaries with it!

[fineincrements]

there is this wavetable filter as well https://expdsp.com/exp-filtertable but wavefield brings its own thing to the table so one could easily use both without feeling overly luxurious

I think being able to modulate the window position rather than just the end points would improve wavefield quite a bit.

Thank you! One hundred percent, the convolution-only wavetable filters absolutely bring their own thing too. Wavefield's straight gain mapping approach is useful for different things. When you say modulate the window position, could you elaborate? I'm not sure I fully understand the request. If you mean the trim bar, you actually can do that. Just grab the bar itself (under the wavetable visualization display) and drag it around. the parameter you'd automate is called "trim offset"

[Funky40]

Latency: The roughly 90ms at 48kHz is correct and inherent to the spectral processing architecture - Wavefield uses a 2048-point STFT with 50% overlap, so the pipeline needs 4096 samples buffered before output begins, plus a 5ms limiter lookahead. That's just the physics of frequency-domain processing at that resolution. Reducing the FFT size would lower latency but also degrade the spectral resolution that makes Wavefield sound the way it does. I originally tried it at 1024, and liked the transient handling better but couldn't stand the low resolution in the bass frequencies.

Yeah, i understand that FFT based FX have some latency. Also that div. FFT sizes do create different sounds. IIRC, there was no mention vs. latency. ( nearly all devs leave that info out)

Parameters/display issues in Patchwork: This sounds like a Patchwork hosting issue rather than a Wavefield bug.

Could be. But i`ve never run with Patchwork into any similar problem bevore. So, PW definitly works well under normal conditions. I don`t use "Patchwork" too much, though. (Only if i have to oversample a FX plugin that has no internal oversampling).

the fact that some parameters (WT start/stop/trim) work while others don't points to something on Patchwork's end.

I`m not sure if that sentence was still meant towards patchwork. I don`t think so.
As i remember was in PW *nothing* running. No access to parameters. And that sentence is true vs. GP, where some things were running, but others not
I need to check again.

Wavefield wasn't designed with live performance latency in mind, it!

yeah, looks like.

vs. life play operations:
Your plugin is very great for that. I really liked it. I have that other thing from minimal audio, which was never as inspiring to me as yours is. Yours has some great usages.

Such FX can definitly be used furher down in some FXing pathes where latency starts to lose its haevy weight. It`s definitly adding something to the table for us.


An idea would be that you would implement the oversampling directly into Wavefiled. *
And you could even add a FFT size switch. *
* i understand that this is not how you see your plugin right now. I just mention it ( with no further understanding how much work it would take a Dev)


It`s definitly a fun Tool in my context.

Thanks for coming back to me

[Funky40]

already a feature request:
- Instead of having WT Start/End and Trim parameters would i turn these three into just: WT start/lenght

Hey Funky40, I do see your point on how it could be implemented to behave similarly with two parameters. I'll add this to the tracker and see what I can do.

Glad you like the idea. That would be super great to have that.


(I`ll check vs. CC mapping again. I think it was not running flawlessly in GP, which is then a deal breaker for me. I`ll try to give that information again, but with more clarity)

[billinder33]

I tested this last night, comparing it against Filterverse and Filtertable on an acid lead. It won the comparison pretty easily because in addition to the synched motion of wavetable, the novel parameters - especially the stereo, floor, and safe bass settings - helped reduce the typical 'thinning' effect you commonly get with filtering.

Really like this plugin ("this plug in is amazing"). Another new release I'm probably going to add to the arsenal.

[TheMaestro]

How is this different from Kiloheart's ShaperTable?

ShaperTable wasn't vibe coded with Google AI Studio.

Are you sure? How do you know?
I had to google
"Vibe coding" in Google AI Studio allows users to build functional, full-stack applications by describing ideas in plain English, powered by Gemini 3 Pro and agentic workflows. It turns prompts into apps, including database and authentication integration, without requiring deep coding skills"

If that's true, well, I am not going to support or pay for no skills for sure".

Btw Kvr made a forum for AI stuff to keep this forum clean.

Because I have made my own synth that way.

[fineincrements]

How is this different from Kiloheart's ShaperTable?

ShaperTable wasn't vibe coded with Google AI Studio.

Hi TheMaestro, I'm a developer with formal college training, a ton of online training after that, and years of experience. I also use AI to assist me. My question to you is why are you throwing shade at people for something you do yourself? BTW Claude Code is what the pros use

Wavefield took 9 months to build, and went through extensive beta testing for months to make sure this was suitable for professional release.

[noahrbc]

Collaboration and creation isn't about competition. People use their own skills with the assistance of AI to help build tools. I don't know why so many people have an issue with this. Enough with the vibe coding blah blah blah...