[FR] MXXX a very cool feature to have

[Frankie.T]

Probably some of you know https://www.stltones.com/products/controlhub-plugin

Long story short this plugin try to recreate a chain (both hardware and software) with their internal processors.

Since MXXX is way more capable with lots of more plugins inside, would be very cool to have that feature to!

I know what it creates will never be an 100% copy, but at least a good starting point where you can tweak all the parameters to bring something different you like inside the Melda ecosystem.

This is something i've done just using my ears with few compressors, but it's a real pain to go through that process, and nearly impossible if there is a chain with more complicated stuff.

So a feature like that on MXXX would be really nice to have

[vectorwarrior]

Capture an IR and/or EQ match with melda stuff, then use NAM modelling to capture the non-linearities which you can then use in the MGuitarArchitect NAM module and you've pretty much got a lot of the characteristics. So it's already possible, but not a simple 'click to capture' process right now.

[Frankie.T]

Thanks for the suggestion, but if my understanding is correct you won't have i.e. an eq, compressor, saturator or whatever chain it is, to shape accordingly to your taste like it is with the other plugin i linked before. And so i think a tool made with this purspose to "understand" what's going on, and then load the relatives Melda plugins with the closest setup to match the source may be the ideal solution, and ofc as you wrote a simple on click

[MeldaProduction]

Frankie, even if this works, it will be quite useless... Every track is different. Copying processing from one to another will pretty much never work.

[Frankie.T]

Frankie, even if this works, it will be quite useless... Every track is different. Copying processing from one to another will pretty much never work.

I agree with you, the request is not to copy paste settings, but a single machine or a chain, let me make you an example.


You have 1 compressor (hardware or plugin) let's say it's an 1176 you use on vocals. You are used to use the samish settings for attack and release and ratio.

The original unit (hw or sw) under the hood change the attack, release and ratio accordingly to the ammount of signal it's feeded with. So when the sample is at 2db of GR the attack is 0.2ms release 80ms, ratio 4, but when hit 9db of GR every value is different (and ofc values are different in between)

I'm doing lots of tests, using my hears and every analyzing tool that can help, and i see some software acting like that, with variable internal settings.

This is very cool, and if settled up properly it makes a huge difference.

I love MTurboComp cause you can do lots of stuff, but trying to replicate something with a costant changes, it's freaking hard if not impossible.

So having a tool designed for that, can test and replicate the original machine would be awesome. Is not about IR, but understanding how something behave then translate with actual settings on your plugins (like the new IR import on FabFilter Pro-R2)

I tried with different sounds that comes with different waveform to understand the behavior, a very short transient driven sound like a snap, then a clap with an higher peak at the beginning, then a compressed kick with an higher peak at the beginning, a dip later and an increased tails that is at the same level of the beginning peak, vocals, and instruments.

But it's an insane job to do manually, while if automated i think it's pretty fast. It's all about to feed the tool with proper sounds with different caratteristics to understand how it behave at different levels.

I see different plugins to behave differently accordingly to the kind of sound that it's feeded and the ammount.
Let's take i.e. a very short vocal, where we have an high peak at the beginning, that it's very short then a quieter part that last 1 second, then a longer part like 2 second but at the same level of the higher peak we have at the beginning.

You may want an internal fast attack and release to deal with the peak, but this create distortion when the longer part comes, in that case you want a more gentle attack, with a sustained release to avoid any unnatural compression.

These behaviour are what makes different compressors different, along harmonic distortion, and having something able to replicate that behaviors is game changer.


If we talk about chain, things don't change too much, will be just matter of having more plugins inside MXXX.

I understand not everything is made for that purpose, so it's even possible that MAIComp may be needed to store and recreate certain behaviours, here we comes into your territory, i'm not a dev and i don't know how certain stuff works.

Eq's are very easy, i replicated everything i was interested for with MADEQ, but when it comes with compression al limiting, everything is way more complicated, and even if i was able to do awesome compressors with MTurboComp, there are some stuff that it's just not possible for a human, and so i made this post :p

[MeldaProduction]

I understand, but what you want is kinda the holy grail of analog emulation and quite honestly I don't see a reason for that. The AI can partly do that and we will look in that quite soon I suppose, but it will consume like 1000x more CPU than MTurboComp approach.

What you can do however is to exploit the "Machine learning" feature in MTurboComp (and most other Melda plugins) - it lets you select input signal and output signal and tries to make the settings, so that the compressor gets from A to B. But it's a very heavy job - you'll need to make the computer run like overnight etc . At least that's what I was doing when making the MTurboComp devices

[Frankie.T]

I understand, but what you want is kinda the holy grail of analog emulation and quite honestly I don't see a reason for that. The AI can partly do that and we will look in that quite soon I suppose, but it will consume like 1000x more CPU than MTurboComp approach.

What you can do however is to exploit the "Machine learning" feature in MTurboComp (and most other Melda plugins) - it lets you select input signal and output signal and tries to make the settings, so that the compressor gets from A to B. But it's a very heavy job - you'll need to make the computer run like overnight etc . At least that's what I was doing when making the MTurboComp devices

If it will consume lots more CPU is not a problem (till the consuption is during the analyze and not while running).

How can i use that MTurboComp machine learning feature? And how to setup to recreate the behaviour of another compressor?
I was not aware of it and it sounds like i could spend weeks into that

[mccy]

I was not aware of it and it sounds like i could spend weeks into that

Wow, wasn't aware of that too...

[Frankie.T]

I was not aware of it and it sounds like i could spend weeks into that

Wow, wasn't aware of that too...

But i wasn't able to find it. Is it another dedicated tool or where can i find it?

[al808]

What you can do however is to exploit the "Machine learning" feature in MTurboComp (and most other Melda plugins) - it lets you select input signal and output signal and tries to make the settings, so that the compressor gets from A to B. But it's a very heavy job - you'll need to make the computer run like overnight etc . At least that's what I was doing when making the MTurboComp devices

What the hell are you talking about?

[mccy]

Yeah, what the hell? Still haven't found it!

[Frankie.T]

Probably it's a tool they have internally but not available in the plugin, let's wait for an answer.

Anyway if so, would be nice to have that plugin-tool in a user friendly form ofc

[sparella]

Version 16.11b
" Added “Machine learning” feature to most plugins (in the Utilities panel). Note: Not for beginners. "

[Frankie.T]

Version 16.11b
" Added “Machine learning” feature to most plugins (in the Utilities panel). Note: Not for beginners. "

Thanks for the info!!

I will give it a try when will be out, this may be my next addiction