Can Someone check me please: MVibrato phasy issues even with Depth = 0.00%

Official support for: meldaproduction.com
RELATED
PRODUCTS

Post

No no it's not latency. It's microdelay, which is not constant. Simply put, if you speed something up, its pitch goes up, right? So the vibrato has a floating delay line, which speeds and slows the audio down repeatedly, so the delay is constantly changing. Hence no compensation can help you, the delay IS the effect.
Vojtech
MeldaProduction MSoundFactory MDrummer MCompleteBundle The best plugins in the world :D

Post

Ok, thx much for the explanation :)

Post

MeldaProduction wrote:No no it's not latency. It's microdelay, which is not constant. Simply put, if you speed something up, its pitch goes up, right? So the vibrato has a floating delay line, which speeds and slows the audio down repeatedly, so the delay is constantly changing. Hence no compensation can help you, the delay IS the effect.
Though thinking about it, and listening - The phasiness is still there with depth set to 0. I was expecting that since Depth = 0 there would be no pitch shift, and therefore no microdelay (and thus no phasiness). What part am I missing there? Thanks! :)

Post

yep, this is what puzzled me, with the chorus, if i remember right. even with the wet at zero, it still sounded phasey.

Post

I forgot, I also wanted to ask what the scaling of "Depth" was in MVibrato: 0-100%, can that be expressed in terms of cents?

Post

Ignore, I was wrong :hihi:

This plug seems to only shift by a few semi, so I guess you could change shape from sine to square, and get exact notes that way

Edit: interesting, changing to square gives no pitch shift.

Ah, just sling it on the verb, and be happy lol

Post

It still phases.

Audio sent to aux bus with verb followed by MVibrato (same aux bus). Audio and aux are then routed to the master out.

Only way the phasiness is inaudible is to turn down the send level, a lot.

Post

ok, so either you have to put the vibrato, BEFORE the verb,or use: http://www.voxengo.com/product/sounddelay/

try something like 12 or 16 ms

Post

...or MUtility...
mba m2 15" | 16gig.ram | 1tb ssd | macOS 26.1 Tahoe
logic 11.2.2  | reaper 7.75 | cubase 14.0.4
focusrite.2i2 | A&H CQ18t

Post

steve2KVR wrote:...or MUtility...
awesome! this plugin has always been a mystery to me. good to know it has some sort of usefulness

Post

...swiss army knif...watch your fingers!... :hihi: .../s~
mba m2 15" | 16gig.ram | 1tb ssd | macOS 26.1 Tahoe
logic 11.2.2  | reaper 7.75 | cubase 14.0.4
focusrite.2i2 | A&H CQ18t

Post

Thank you for all the replies. As it turns out I already have a 250 msec pre-delay on my reverb. Will another 16 or 17 ms really make a difference?

Thank you for any thoughts!

Post

I don't think so, 250ms is so much that 20ms won't be much noticeable (unless you have some kind of temposync in the reverb, so that it won't be in time anymore).
Vojtech
MeldaProduction MSoundFactory MDrummer MCompleteBundle The best plugins in the world :D

Post

MeldaProduction wrote:I don't think so, 250ms is so much that 20ms won't be much noticeable (unless you have some kind of temposync in the reverb, so that it won't be in time anymore).
Thanks for the answer, Mr. Melda.

At this time, with down to 50 msec of pre-delay, there is no phasiness when sending the vocal to a bus that has a reverb followed by MVibrato inserted on it (and both the audio track and the aux bus routed on to the 2-bus). This holds true even with the send up fairly high. Maybe one day I'll see how short I can make the pre-delay before the phasiness sets in ("16-17 msec"?), but for now I'm very happy to be able to experiment with the audible effects of pitch shifting the tail.

Thank you, everyone!

Post Reply

Return to “MeldaProduction”