A-H presets now send automation when changed

[kylen]

Hello Melda - I have MAutoDynamicEQ 7.04 installed and wanted to find out more about this useful feature I found in the release notes [MAutoEqualizer 6.00 changes].

I'm experimenting trying to set it up but haven't gotten it yet.

Where in the manual do I look? Or if you can note a couple of steps here I'd appreciate it. I'm using Reaper4.261 on Win7. Thanks!

[MeldaProduction]

Hi, well, all you need is to enable automation write in your host and then change the A-H presets. But note that only automatable parameters can be recorded. Or you can use MIDI program change to switch between the presets. Note that it can take some time to reload the presets so it is possible you will get some glitches.

[kylen]

Thanks Vojtech.

I sent MAutoDynamicEq this midi msg (captured by ReaControlMIDI activity log):
C1 00 00 [Program Change] chan 2 val 0
B1 00 00 [CC0 Bank Select MSB] chan 2 val 0
B1 20 00 [CC32 Bank Select LSB] chan 2 val 0

That made MAutoDynamicEQ jump to preset 'D'.
After that MAutoDynamicEq didn't respond to any more program change requests until I removed the plugin from the Reaper FX rack and added it in again.

I tested this with ReaEQ and was able to change presets successfully, just to have a control test.

Looking for some ideas when you get a minute. I'll try some more things this week but need a break in the meantime. Setting up a new automation environment is a bit tricky sometimes - I must've missed something basic somewhere.

[kylen]

I turned off 'Settings' 'Automation compatibility mode' and now (using Reaper - show last touched FX Parameter only) gives me 'Preset trigger - next' for presets A-H, which seems closer to 'LFO 4' which is what I got with 'Automation compatiblity mode' on.

Next I'll try to select a user preset (not A-H preset) using a midi message.

[kylen]

The manaul that comes with MAutoDynamicEQ describes the Midi Controllers Editor from some previous version like v5.

I'm looking at the MStereoGenerator manual which has a midi controllers section more closely resembling MAutoDynamicEQ version 7.04.

Under the "Controllers" bar is the unnamed 'parameter button', continuing on...

[kylen]

...Or you can use MIDI program change to switch between the presets...

I think I'd rather do that than use the A-H preset and automation write.

What MIDI program change message do I send to select MAutoDynamicEQ v7.04
preset named 'Vitalizer bass' for example?

[MeldaProduction]

...Or you can use MIDI program change to switch between the presets...

I think I'd rather do that than use the A-H preset and automation write.

What MIDI program change message do I send to select MAutoDynamicEQ v7.04
preset named 'Vitalizer bass' for example?

By presets I meant the A-H presets. But in MIDI controllers you can now create a controller which changes preset to the next/previous one in the list.

Manual will be modified in next major version, or maybe it will actually be removed as you will be able to create it from inside the plugin.

The "unnamed button" is the selected controller, no idea what you mean by that.

I'll check the Reaper, but since it is extremely unfriendly, could you send me a simple project which generates the message, so that I can check the freeze?

[kylen]

"I'll check the Reaper, but since it is extremely unfriendly, could you send me a simple project which generates the message, so that I can check the freeze?"

Interesting. What are a couple of examples of friendly daw's?
Maybe I should be looking around.

[MeldaProduction]

Well quite frankly I'm surprised you are complaining about that. Reaper knows lots of things you cannot do in other DAWs, but to do them you have to go through thousands of menus with weird names, settings with gazillions of checkboxes etc. But the biggest problem for me was always routing and editing of audio & MIDI... For example using a simple stereo sidechain in Cubase takes 2 clicks, in Reaper I don't know, 20 ? ...

Nevermind this is just my opinion, so please ignore it if you want. I'm personal fan of Cubase, which has always been simple and still powerful, that's why other hosts (such as Studio One or Logic) copy the way it works. It depends on everyone's way of using it of course...

You have to understand that I'm dealing with literally dozens of hosts, so I need to do things quickly without spending hours by searching for features, which normal hosts would be willing to take, but I just cannot.

[kylen]

By presets I meant the A-H presets. But in MIDI controllers you can now create a controller which changes preset to the next/previous one in the list.

OK yes I can do that now. I'm able to walk thru a list of presets [relative to the currently selected preset] using midi messages sent to MAutoDynamicEQ after changing the "MIDI Settings" preset switch trigger.

What I think I'll do in Reaper is to create some EQ setting(s) that I like in MAutoDynamicEQ, save it as a Reaper preset (click the Reaper FX + sign and save preset). That is so I can see the preset name in the Reaper FX host as they switch, I can't see the preset name without getting into the Melda preset area.

But now, since the presets are managed by Reaper I can just send a 'real' program change MIDI message via ReaControlMIDI or the piano scroll midi item inserted on a midi track:
624: B0 00 00 [CC0 Bank Select MSB] chan 1 val 0
625: B0 20 00 [CC32 Bank Select LSB] chan 1 val 0
626: C0 02 00 [Program Change] chan 1 val 2

That selects Program 2 (preset 2). This is manageable for me. I'm remastering stereo tracks that have 3 or 4 sections that require pretty different settings.

BTW Vojtech - MAutoDynamicEQ is a really fine dynamic EQ that's why I'm trying to keep a single instance and use it to to change to a different preset when needed - I only have 2-core and can't afford multi-instances (along with the other plugs in the FX rack), track freezing doesn't help in my workflow either.

Anyway - I hope the presets will load properly this way on an off-line render so I'm still kind of testing this all out.

[MeldaProduction]

Uuuuu, really? This way??? That seems awfully complicated... Ok, and it works this way or not? Of not, please send me the project, because I don't think I will be able to do such hacking in Reaper . Anyway the switching of presets works, but you're just stuck with the preset name?