MeldaProduction

sinkmusic · Post by **sinkmusic** » Thu Mar 27, 2014 8:36 am

Darkstart, your skins look good.

Svama · Post by **Svama** » Sat Mar 29, 2014 6:10 am

Hi Vojtech,

3 days left for demoing beta 3. Does that mean next week will come the final release?
MstereoProcessor demo time is over, that's weird.
But to me it looks great and stable.
Go on!
Maybe it is possible to integrate a better workflow for m/s equing with mautodynamiceq. In my opinion it needs too much clicks to switch between mid and side between the different bands(frequincies).

Thanks and greats

Marek

Alphacodex · Post by **Alphacodex** » Sat Mar 29, 2014 10:51 am

@Svama

To do M/S equing with the Melda Plugins you always have to insert two plugins into your chain. Set one to M and the other to S. Do the M equing in the first instance and the other way round.

It may or may not be the best or most intuitive solution, however I do admit that it is more flexible than other approaches (FabFilter did a great job here, however t is still not as flexible as Meldas approach).

I think when you program Plugins you always have to make a decision between making the plugins and gui easy, uncluttered and fastforward and offering the maximum in flexibility, features and options.

The strength of the Melda plugin in my eyes lies in the absolutely amazing galore of options and features. The weakness on the other hand my be, that in order to use all these options you might need one or two clicks more. However I think Vojtech already made a good compomise here.

Cheers,
Codex

Svama · Post by **Svama** » Sat Mar 29, 2014 11:54 am

This is not correct! Mautodynamiceq needs only one instance for m/s, what is great, but it could be smoother in handling, e.g. fabfilter proeq.

Greets

Marek

BasariStudios · Post by **BasariStudios** » Sat Mar 29, 2014 12:16 pm

I still have not seen plugins as flexible as Melda, not even some of the big names and bucks. This is not an advertisement for Vojchek or something, those who have used the plugins know what i am talking about.

Alphacodex · Post by **Alphacodex** » Sat Mar 29, 2014 2:08 pm

@Svama Ok it did not know that!

nicocadiou · Post by **nicocadiou** » Sat Mar 29, 2014 3:52 pm

MeldaProduction wrote:
nicocadiou wrote:Hi Vojtech, hi all,

I think it would be a good thing to add the possibility to modify the green / yellow / red zone values of the meters. Don't you think so ?
Maybe I'm missing it and it's already possible to change it... Let me know

Thanks again for your good work !
What you mean by that???

Considering MLoudnessAnalyser plugin for example, when you change the offset value to -23 (which is the European integrated loudness value that you have to reach), then it would be fine to be able to set the meters colours so that all the values over 23LU are shown in red colour, etc.
Here I take the MLoudnessAnalyser for example but it can be very useful on every plugin I think

MeldaProduction · Post by **MeldaProduction** » Sat Mar 29, 2014 8:27 pm

V-GER wrote: I mean for instance routing the LFO (or the "Normal" part) in modulator 1 to modulate some parameter, the follower in modulator 1 to modulate some second parameter, the envelope to modulate a third parameter and the random to modulate a fourth parameter while the pitch part could modulate a fifth. I can't seem to do it now, as soon as I click "follower" a parameter that was modulated by the "Normal" LFO now becomes modulated by the follower instead. Clearer? Possible? CPU would shoot through the roof?

Huh? So you want 4 modulators in a single modulator

. That really doesn't make much sense, and if implemented, that would be riddiculously overcomplicated, hard to use, have no advantages whatsoever etc... Well, you have to use different modulators of course.

MeldaProduction · Post by **MeldaProduction** » Sat Mar 29, 2014 8:34 pm

nicocadiou wrote:
MeldaProduction wrote:
nicocadiou wrote:Hi Vojtech, hi all,

I think it would be a good thing to add the possibility to modify the green / yellow / red zone values of the meters. Don't you think so ?
Maybe I'm missing it and it's already possible to change it... Let me know

Thanks again for your good work !
What you mean by that???
Considering MLoudnessAnalyser plugin for example, when you change the offset value to -23 (which is the European integrated loudness value that you have to reach), then it would be fine to be able to set the meters colours so that all the values over 23LU are shown in red colour, etc.
Here I take the MLoudnessAnalyser for example but it can be very useful on every plugin I think

Sorry Nicolas, but that's way too over complicated and in 99.999% completely useless. Even in the case of MLoudnessAnalyzer it is completely useless. You just need to set the offset correctly (if you need to show the top part different color). However now I see the 8.00beta3 shows kind of weird green interval

, that's a bug, so thanks for that

.

Gone soft · Post by **Gone soft** » Sat Mar 29, 2014 9:30 pm

MeldaProduction wrote: Huh? So you want 4 modulators in a single modulator . That really doesn't make much sense, and if implemented, that would be riddiculously overcomplicated, hard to use, have no advantages whatsoever etc... Well, you have to use different modulators of course.

Well, I was first and foremost thinking of routing the different parts of a modulator to other parts of that same modulator so for instance the follower in modulator 1 could modulate the rate of the "normal" LFO in modulator 1. If it is limited to one part modulating one other part than it could be an extra slot in for instance the follower to output the resulting rate modulated LFO. Not much more complicated than the current options for "Project unto the LFO shape" and "LFO modulation" within the follower, envelope and random. Does that make any sense to you?

Alphacodex · Post by **Alphacodex** » Sun Mar 30, 2014 8:22 pm

Something else: Would it be a big deal, to add the nice locut and highcut filter from the MDynamicEQ to the standard MEqualizer? I use those filters a lot but I always have to use MDynamicEQ and that's a bit like cracking a nut with a sledgehammer.

Svama · Post by **Svama** » Sun Mar 30, 2014 9:28 pm

Hi Vojtech,

demotime of some plugins is over, what can I do?

Greets

Marek

MeldaProduction · Post by **MeldaProduction** » Mon Mar 31, 2014 10:17 am

V-GER: Nooooo!!!!

That's the same thing, just the more complicated case! Modulating itself... oh come on

...

Alphacodex: Sorry, but now, that's one of the advantages of the dynamic equalizers

. I absolutely don't want to duplicate the features from high end stuff to the free stuff (and all the plugins whatsoever). That way you would end up with a single ultimate plugin, which would be a sledgehammer again

. Personally I always use MAutoDynamicEq, no need for other equalizers whatsoever. There should be a big difference in CPU, unless you use dynamic features of course.

Svama: Free-for-life updates

. So you can buy it already if that's what you are asking

.

Alphacodex · Post by **Alphacodex** » Mon Mar 31, 2014 11:47 am

So if the dynamic setting is set to 0dB it wont take up any resources? If that is the case I can just keep on using the MDynamicEQ. I always feared that the envelope followers of each band i use are eating up a lot of CPU, that's why I asked to put it into the MEqualizer.

Cheers,
Codex

MeldaProduction · Post by **MeldaProduction** » Mon Mar 31, 2014 11:54 am

No

. You can try for yourself - open the eq, check CPU meter, then move vertical nodes of each band a little and check again, then double click on the vertical nodes to reset the dynamic gain again and check once more

.

When the dynamic gain is 0dB, the whole dynamic engine is disabled. So yes, you can use MDynamicEq only

.

MeldaProduction

KVR Audio

8.00 beta 3 for all MeldaProduction effects has been released!