MAutoDynamicEQ automation unreliable in Reaper

[MeldaProduction]

I believe it is fixed in 16.08, please check it out and let me know.

[tingshuo]

Confirmed, quick tests show that it appears to be resolved in 16.08. Thanks Vojtech!

EDIT: please see next post. There's a secondary issue that's still occurring.

[tingshuo]

Ah, unfortunately, there still seems to be an issue with the Band Enable parameter. Perhaps the cause is unrelated, but Enable is not being reliably written to the automation envelope. Please see this short video demo:

[tingshuo]

Ok, I think I've found the cause of the issue with the Band Enable parameters. If I adjust that parameter while in Automation 'Touch' mode, it seems to render the parameter permanently un-writeable. Of course, 'Touch' mode is not a good choice for writing an On/Off parameter, but the permanent disabling (error state?) of the parameter seems to be a bug of some sort. For now, I intend to not automate the Enable parameter at all, and just have all bands enabled at all times - should work, but not ideal due to visual clutter.

Video demonstration:

[_al_]

Found and will be fixed in 16.09. The reason is that currently there's a limitation that if more than 100 parameters are automated at the same time, it's considered "a bug in the host", probably left from the early days of VST3.

I actually had a similar problem recently, with the saturation in MdelayMB causing crazy amounts of feedback, on the first run of a project being open.
Can't remember how I worked around it (if I even did), but I'm hoping this fix will have an effect on all Mvst3

Gotta say though. vst3 kinda sucks. Really buggy in many fx.
Sometimes wish I didn't migrate away from vst2

[Hexspa]

Yeah I think I was having issues with one of the Melda delays. Does anyone else agree that bypassing the plugin should kill the tails? Kind of like a midi panic button.

Reaper is not faultless. XLN Audio has told me that the way reaper buffers things doesn't always work out evenly. I'm not qualified to expound on it but sometimes when I let XO run in sync with reaper, it'll drop 'hits'. In other words, sometimes it won't play something it's supposed to. I reckon it's related to reaper's buffering. They're aware of it afaik but I haven't seen any fix. Again, I can't be sure whose at fault for any of this but I have reason to believe it's not entirely a melda issue.

[_al_]

Yeah I think I was having issues with one of the Melda delays. Does anyone else agree that bypassing the plugin should kill the tails?

Interesting! I never even realised it did this!
Usually I quick cut the feedback by automating hipass on the feedback filter lol
No doubt there's other ways. But yeah, I would kinda expect "Bypass" to cancel all processing, instead of just muting it. Kinda weird, yeah. It's basically the same as muting wet out then

My problem was really weird though, because it seemed to be building up feedback before any sound had even gone into the plugin. So when sound DID go into it, it would sound like saturation had caused the FB to overload, even though it was silent until that point.
Only seemed to happen when automating Sat and/or FB. Not sure exact required combo

But only happened on first load of project. After first run, it behaves as expected

[Held]

Yeah I think I was having issues with one of the Melda delays. Does anyone else agree that bypassing the plugin should kill the tails? Kind of like a midi panic button.

I don't think so. When I unbypass a plugin, I want it to sound like it had never been bypassed in the first place.

Interesting! I never even realised it did this!
Usually I quick cut the feedback by automating hipass on the feedback filter lol
No doubt there's other ways.

Each tap has a "Silence" button that you can automate to silence the feedback path.

[_al_]

Interesting! I never even realised it did this!
Usually I quick cut the feedback by automating hipass on the feedback filter lol
No doubt there's other ways.

Each tap has a "Silence" button that you can automate to silence the feedback path.

Hey, that's awesome! Thank you very much.
And this is why the Melda forum is the only forum I enjoy posting in.
I use 10+ Mdelays in every project, and still I'm able to learn from coming here

[Held]

Each tap has a "Silence" button that you can automate to silence the feedback path.

Hey, that's awesome! Thank you very much.
And this is why the Melda forum is the only forum I enjoy posting in.
I use 10+ Mdelays in every project, and still I'm able to learn from coming here

Happy to help.

[sparella]

I use 10+ Mdelays in every project

If you've made some cool device presets, feel free to share on the exchange!

[MeldaProduction]

Hmmm, I just tested it and it seems just fine with both VST2 & VST3. Hard to say then, I'd need some way to reliably simulate this.

[tingshuo]

Hi Vojtech, thanks for looking into it.


I have just emailed you (info@meldaproduction.com Request 6757) a Reaper project file with an instance of MADEQ that shows the bug I am reporting. The Enable parameter can no longer be written in automation. On my system this is repeatable (MacOS 11.4, Reaper 6.82, MADEQ 16.08)

This 3 minute Youtube clip shows the session I sent you being created and the steps to arrive at the Enable parameter becoming un-automatable.