MFreeEffectsBundle- assorted ideas & suggestions

[.jon]

While I think this (upgraded) bundle represents some of the best value in the industry, offering a very nice selection for creative processing and mixing, you know how it is- always some things could be improved

All plugins:

- button to collapse the A/B, AGC and MIDI etc section. I emjoy all the features in there, but honestly don't need them visible all the time or on all plugins. Being able to fold it would save some screen estate and reduce clutter.

- keep window size when changing style / colours. Currently it resets to factory default, not the user chosen default size- would be cool if it didn't reset at all. This could almost be a bug, but an annoyance at least.

- short chapter in the Information window about the plugin itself, what does it do and how it's features work?

- when I open the MIDI window, the list is pre-populated by a few dozen entries for dry/wet. What's their purpose?

MBitFun
- this one lacks the limiter, a feature I've learnt to love on all the other distortion plugins.

MBitFun, MWaveFolder, MWaveShaper (+MFreqShifter)
- what do you think about adding modulators to these? Signal-following distortion could be sweet, for example

MComb
- the panorama handles on band nodes have reversed response, when I drag right it pans left. Not sure if this is intentional.


That's the stuff I've remembered to write down, maybe more will follow. Regardless of this list, thanks for the awesome plugins, I use them on everything. On a side note, MLimiter + MOscilloscope+MAnalyzer was a combo that changed my understanding of saturation.

[MeldaProduction]

Thanks for the feedback, but I'm not going to make you happy really :

1) The toolbar needs to stay there, people hate things than appear and disappear, kills the support etc. So only things that really need to be hidden/shown can be collapsed. And this is waaaaay too small and almost always useful.

2) That's intentional! Think of people with small resolutions.

3) It is there whenever it is necessary. But let's face it, everyone knows what an autopan is .

4) These are just defaults, you are assumed to set the target parameters somehow.

5) That's because it is limiting by nature. Think of what bit mangling does - it can never exceed the bitrate.

6) Sorry, no. That's one of the advantages of the multiband versions.

7) Yes! Fixed! Please wait for the update.

And thank you!

[castcircle]

I have a sillier question. Has the FreeEffectsBundle upgrade ever been in the Eternal Madness sale? I keep looking and hoping, but I don't think I've ever seen it. (And I'll get around to it eventually either way, I promise, because it is wonderful.)

[ElevatedBeing]

I have a sillier question. Has the FreeEffectsBundle upgrade ever been in the Eternal Madness sale? I keep looking and hoping, but I don't think I've ever seen it. (And I'll get around to it eventually either way, I promise, because it is wonderful.)

I think if you wait a couple of days you will be able to buy it at a discount.

[.jon]

Thanks for the detailed reply, Vojtech!

1) not sure how it's that different from other UI elements, and people probably don't hate them appearing and disappearing

2) sorry, how is resolution relevant? User sets a good size for the window, saves it as default, then decides he wants to change the colours- size is reset. Resolution?

3) True, Autopan is pretty obvious. Wavefolding is not that common in plugins, and MLimiter isn't a typical limiter for example These could be helpful to many, and not bother anyone

4) Ok, but why is "Gain" as a default there 32 times? What is the benefit of this to the user?

5) The limiter in other plugins is a safety limiter, and MBitFun, just like any bit mangler, can and often will alter the signal level so it goes above 0dB. It does have AGC, but it doesn't react instantly like a brickwall safety limiter, thus offering less protection. EDIT: the multiband version actually has the limiter.

6) Fair enough!

7) Awesome, thanks!

...and one more thing:

vertical meters option for MLoudnessAnalyzer? Those horizontals seem to take a while to get really used to.

[castcircle]

Yay and thank you!

[steve2KVR]

...and maybe the option to "colaps" the meters entirely...would relieve cpu use and open up "way more" screen space as well...all I need are the numbers and the time graph...btjm.../s~

[MeldaProduction]

1) This is because this particular toolbar takes just a little place and is almost always handy.

2) Try a 13" laptop with 1280x800, you'll see after you won't be able to reach the title of the window... not mentioning problematic hosts... not mentioning it is generally good to know how by each style is...

3) Yeah, these exceptions could use some info . On the other hand, wavefolder is just a specific kind of distortion and there's not much to write about it, certainly not how it works!

4) I don't follow. It's just some value, you are expected it to set it to something useful for you.

5) Actually it shouldn't unless you do that manually using output gain. Multiband version needs it for cases with phase shifting.

Vertical meters - sorry, won't happen, I denied it several times.

Collapsing meters - it's already there! But it cannot save CPU in MLoudnessAnalyzer much, because both the time graphs and meters are using the same subsystems, so the measurements are always necessary. But it doesn't take almost anything, so it should be fine

[.jon]

2) Try a 13" laptop with 1280x800, you'll see after you won't be able to reach the title of the window... not mentioning problematic hosts... not mentioning it is generally good to know how by each style is...

Ok, I tried it on 1280*800 and it works just like on 1920*1200, changing colours resizes the main plugin window for no good reason?

4) I don't follow. It's just some value, you are expected it to set it to something useful for you.

User is expected? Surely no Every function in a program is expected to be there only for some benefit to the user. Why else would you put something in the code? I just don't see any use case for 32 entries of Gain in the MIDI controls, that's why I asked what's their point.

5) Actually it shouldn't unless you do that manually using output gain. Multiband version needs it for cases with phase shifting.

It can easily do that even with signals as low as -12dB.

Vertical meters - sorry, won't happen, I denied it several times.

They'd be great tho

[MeldaProduction]

2) Aaaahaa, when changing colors ... Why didn't you say so . There's no benefit indeed, but it's technically complicated to differ in what one has changed and personally I don't consider it relevant at all. I mean, you do that once...

4) There are 32 slots, because it was done like that. Technical reasons. And each needs some value... that's all...

5) Could you send me some settings? I tried just about every preset, no luck, it was always below/equal 0dB. There perhaps may be some slight overload like 1dB, which is irrelevant. Safety limiter is for preventing big jumps, that could hurt you/monitors, not to make everything below 0dB. We are fortunately not in analog domain anymore .

[.jon]

Right. Enjoy the holiday season and good luck!

[MeldaProduction]

You too!