Beta LFO-filter plugin

async · Post by **async** » Thu May 15, 2008 5:49 am

Nope, sorry. This is an Audio Unit for Mac OSX only.

Keagan · Post by **Keagan** » Thu May 15, 2008 8:22 am

cool. sounds great quite a bit of cpu though in logic 7 and live. Like 10% with analog on.

Jack Rock · Post by **Jack Rock** » Thu May 15, 2008 5:36 pm

Nice work! It sounds amazing in analogue mode!!!

It would be nice with interpolation when moving the sliders, though - at least on the cutoff slider.
If the steps are audible, as they are now, then the plugin will not be as useful as it could be.

Audio Dependent · Post by **Audio Dependent** » Thu May 15, 2008 5:38 pm

nice work man! sounds great! tested it in ableton and no cpu issues here. i vote for keeping an analogue and digital bit. you could make the analogue setting the default as its a bit safer and have a little warning somewhere about the digital. its just nice to have a bit of headroom spare with these things imo.

thanks for sharing

unsaturated · Post by **unsaturated** » Thu May 15, 2008 7:56 pm

Jack Rock: luckily I think it's pretty simple to add high-res to the cutoff value (purely for automation's sake). I couldn't hear the steps myself, but I can understand perhaps doing a bit of interpolation on the params. Were you using a MIDI controller? I could see this being a big issue with only 8 bits of resolution on the cutoff...

Keagan: What are your machine's specs and what's your IO buffer size?

My next tasks are UI and optimization, roughly in that order. In particular, the envelope detector could be much more optimal (I'm currently doing like 5000 adds, a divide and a float32 square root per output sample... this is obviously not very optimal). I also add a tanh before every stage of the moog-ladder in the analog mode, when this isn't strictly necessary (though I found that it makes the sound noticably more smooth, whatever that means).

Jack Rock · Post by **Jack Rock** » Thu May 15, 2008 10:08 pm

unsaturated wrote:Jack Rock: luckily I think it's pretty simple to add high-res to the cutoff value (purely for automation's sake). I couldn't hear the steps myself, but I can understand perhaps doing a bit of interpolation on the params. Were you using a MIDI controller? I could see this being a big issue with only 8 bits of resolution on the cutoff...

I was actually just using the mouse. But the problem is more obvious when using automation - at least in Logic.
It seems the slider in the interface is logaritmic but the interpretation of the automation is linear.

Here's a screenshot to demonstrate:

Notice how the cutoff slider in the interface is almost halfway through while the automation line has barely left the bottom.
(Also notice how the automation states 387 Hz while the interface says 438. But that's a minor problem).

Here's how this sounds:
http://www.mobilseddel.dk/Filterizer.mp3
Pretty noticable!

So maybe it's not just a matter of interpolation but also interpretation of controller data. I dunno ...

But I hope you can fix it, cuz the sound of this filter is quite unique for any plugin I've tried.

unsaturated · Post by **unsaturated** » Thu May 15, 2008 10:57 pm

Woah! 1000 thanks for that VERY clear and concise description (and sample) of what you were hearing. I'll make the param high-resolution and see if that changes anything.

The funny part is that I don't actually control what the display shows, I just read the parameter once per render callback. This is a weird bug in Logic Pro (or audio units).

unsaturated · Post by **unsaturated** » Fri May 16, 2008 12:42 am

I've flipped the high-resolution bit on the filter cutoff and the q, could someone try again? The link is the same, the AU has been updated.