FR: MMultibandDelay, Tapping Tempo by Mouse

[Svama]

Hi Vojtech,

what about a knob for tapping the tempo by mouse or shortcut key?

Thanks and greets

Marek

[MeldaProduction]

Hi Marek,

well, I'm afraid it would be quite complex, GUIwise. Sorry.

[Svama]

Okay, but what about tapping the tempo with the left mouse with a keyboard shortcut like alt on the tempo value. So you don't need another knob or something like this.

[MeldaProduction]

Hmmm, hard to say, I'll check. Wait a sec - where on earth is "tempo" in the delay?? You mean time?

[Svama]

Yeah Mr. Melda, you called it delay parameter in ms:-)! Would be great!!

[Grizzellda]

Hey guys, in MMultibandDelay, what if I want every band to cover the same frequency range - is that what the minimum frequency & maximum frequency parameters are for, in each band?

And what does "Runs all bands as parallel processors" mean? Is this about the crossover slopes?

[vectorwarrior]

Yes, the frequency controls in each band's settings are filters on the input of each band. If you have feedback on the delay, each time it gets delayed and fed back, it will go through the filters... so it will gets slightly progressively more filtered (only slightly because the filter frequencies aren't changing, just the severity).

Secondly, I presume you're talking about the crossover right-click? Yes, that was a feature someone asked for, it allows you to essentially run the plugin as a parallel effect, where the crossover filters dont actual filter, they just send the full signal. This way you can set up up to six totally different effects (one in each of the 6 bands) and it'll be the same as if you put 6 instances of the plugins in your DAW.

Hope that helps.

[Grizzellda]

Secondly, I presume you're talking about the crossover right-click?

That's correct...thanks for the reply by the way. I've read several of your posts - you seem to be a heavy Melda user!

About the first question, does this "input filtering" basically enable each of the six bands to simply cover the full range of the audio spectrum, so it acts more like a regular multi-tap delay...if that makes any sense?

Because most multi-tap delays aren't multi-band, yet they still have all those delay options, etcetera.

And concerning "crossovers", how would you define them?

[vectorwarrior]

Okay, you need to mentally separate the crossover bands from the stuff inside the bands... if that makes sense.

The effects are designed with single-band in mind... so the filtering in the band is just applied to the input it receives, it's not aware of if it's being used in a multiband/crossover context.

Example: If you set up the effect to only have 1 band, and you set up the delay filtering on the band to be 500Hz min and 1000Hz max, the delay's output will only be between the 500-1000Hz range (obviously).
Then, if you set up a two band version with the crossover at say 700Hz, with the filtering in each band to be exactly the same as above for both bands (500-1000), the first band will receive audio at 0Hz to 700hz (sort of, depending on the crossover filter), and will then filter that so it only keeps 500-1000hz... meaning it'll only receive 500-700Hz. The second band will do the same, but it's only receiving an input of 700Hz and up... so it's output will be 700-1000hz.

Does that sort of make sense? I feel i may not be helping. But essentially, the crossovers happen first, then the output of the crossovers are sent to the bands where the respective effect is applied.

If you want more info, honestly the best thing to do is to click on the little '?' on the relevent section of the UI. The help is very useful, if a little 'generic' at times as it's reused across all effects that share that feature, so the help can sometimes need a little deciphering on your part.

As for me, yeah, I absolutely love Melda effects. I jumped ship from Waves, which I used for many years. Honestly it was a bit of a gamble for me as I'd switched studios and ditched everything I'd used, I found the learning curve very steep so I kept reading the manuals over and over whilst fiddling with them until I 'got it'. The promise of the plugins was so great but it took me a long time to really understand how they functioned as they are not built for ease of use like Waves stuff (which now come across as exceptionally simplified/restrictive to me now). The great thing is, once you 'get' how one Melda plugin works, you 'get' all of them to a degree, as they share common functions.

[steve2KVR]

...well there ya go......vector just about nailed it for me...waves/etc all seem like the "simple" interface on the melda equivalent plug...which i actually use on mplugs that i have configured as one of my "standards"....../s~

[Grizzellda]

If you want more info, honestly the best thing to do is to click on the little '?' on the relevent section of the UI. The help is very useful,

Oh, I know all about that! He could put better info there, for sure...

The effects are designed with single-band in mind... so the filtering in the band is just applied to the input it receives, it's not aware of if it's being used in a multiband/crossover context.

Got it. Good answer, it really is making things clearer. I think I have basically understood the concept for awhile, but it is the whole slope stuff, how the bands interact that I'm wondering about. That's why I asked about the "parallel processing" option.

The great thing is, once you 'get' how one Melda plugin works, you 'get' all of them to a degree, as they share common functions.

Agreed! Well it's the GUI, isn't it? I have invested some effort here as well. But it's worth it.

Thanks man! I'll reflect on all this...

[Svama]

This post takes a interesting way, but what about tap delay? Is itc possible?

[MeldaProduction]

Not sure yet... I fear this could be a totally hidden -> useless feature.