FR: Requests for TurboFilter

[pelori]

I have been using MTurboFilter recently and have a few feature requests.

- Frequency-Shifter module
I would like to have a module to move the pitch of the signal, you might know how to use it since it is also found in the Insert FX of NI MASSIVE (for the filter routing).

- Delay Tap module
Technically, I was able to achieve Feedback Delay by using FBCOMB, but I would like to have a Delay Tap module that generates Delay only once. Or if there is a way to achieve this, please let me know.

- More variable parameters
Currently, f, q, c, d, fb and #(complexity) are available as variable parameters. I would like to have more variable parameters (for example, adding some generic bipolar parameters).

[dmbaer]

- More variable parameters
Currently, f, q, c, d, fb and #(complexity) are available as variable parameters. I would like to have more variable parameters (for example, adding some generic bipolar parameters).

Yes please! Vojtech doesn't think any more are needed, so I'm glad to see I'm not the only one thinking there should be a few more (at least four to be on the safe side, although two more would cover a lot of situations).

[pelori]

Yes please! Vojtech doesn't think any more are needed, so I'm glad to see I'm not the only one thinking there should be a few more (at least four to be on the safe side, although two more would cover a lot of situations).

I agree with 4 or more.
More and more variable parameters are also welcome!

I'd like to make more complex feedbacking effects with TurboFilter. This module is the feedback beast!

IMHO, I think by the way ... MSF Generator section's feedback support (like FX section) also would be the great option (I know "GenerateCustomMod/Set" module feedbacking hack but I'm not satisfied).

[MeldaProduction]

Huh, what are you doing with that guys? I really want to keep it as simple as possible. Every further parameter will need to be evaluated, take CPU, user would expect it to work everywhere... it's a lot more complicated, than it might seem. Delay & Frequency shifter I'll think about.

[pelori]

Huh, what are you doing with that guys? I really want to keep it as simple as possible. Every further parameter will need to be evaluated, take CPU, user would expect it to work everywhere... it's a lot more complicated, than it might seem. Delay & Frequency shifter I'll think about.

Thank you for reply!
When using multiple modules (Filter, Shaper, Ratio, etc.) and assign their parameters to variable parameters(f,q,c,...), I quickly run out of them.

If I just want to use multiple modules, I can arrange them on MSF.
However, I found that Turbo Filter is quite flexible in building advanced effects, especially including feedback filtering, so I felt that a few more variable parameters would expand the possibilities.

I think the feedback system in the Turbo Filter is amazing!

[MeldaProduction]

Thank you!

Now, I'll think about other parameters too, but only nonmodulatable.

[dmbaer]

... but only nonmodulatable.

No modulation, no problem. What I see as useful (and what I suspect the OP is looking for as well) is a few more top-level controls to set behavior within the filter algorithm. Besides, using, say, cutoff amount to control something totally unrelated is just flat-out confusing. Given that three of the four available parameters are going to be used in many situations, you've little extra to work with in any case. So, no modulation is just fine.

[zuhizuhi]

Vojtech: Huh, what are you doing with that guys?
MeldaUsers: Yes

[jmg8]

Vojtech: Huh, what are you doing with that guys?
MeldaUsers: Yes

[pelori]

Huh, what are you doing with that guys?

I don't think I'm doing anything too complex...
For example, I put individual filters and shapers in the internal feedback routing of the LPF and assign variable parameters to control each of them.
At that time, the variable parameters are used up even with a small number of modules.
ex.) I need parameters of LPF(f1, q1, fb), Notch(f2, q2), SAT(d), ... (already over 6 parameters)

Is what I am trying to do too complex for Turbo Filter?

[jmg8]

Huh, what are you doing with that guys?

I don't think I'm doing anything too complex...
For example, I put individual filters and shapers in the internal feedback routing of the LPF and assign variable parameters to control each of them.
At that time, the variable parameters are used up even with a small number of modules.
ex.) I need parameters of LPF(f1, q1, fb), Notch(f2, q2), SAT(d), ... (already over 6 parameters)

Is what I am trying to do too complex for Turbo Filter?

No, not at all.
The comments were just a playful joke about how Melda power users often push the limits of the software. And so they should! Melda is a creative playground for us all to have fun

[pelori]

The comments were just a playful joke about how Melda power users often push the limits of the software. And so they should! Melda is a creative playground for us all to have fun

Thanks! I agree with that!

[MeldaProduction]

SO, in the next version there should be all the modules you mentioned (I think) and 4 custom params.

[GusGranite]

SO, in the next version there should be all the modules you mentioned (I think) and 4 custom params.

Love it!

[pelori]

SO, in the next version there should be all the modules you mentioned (I think) and 4 custom params.

Thank you so much, I am so glad to hear that!
I am looking forward to the release of the plugins!