Feature requests :)

[Audiospaceman]

Hello Vojtech and Meldaproduction Team,

Hope you are okay, and everybody here in the forum as well!

I would like to share some thoughts and feature requests that may help improve some plugins. Thanks in advance for listening!

Suggestion for the MAutoDynamicEQ plugin:
Could the Hi-pass and Low-pass filters (the red vertical lines) be present in the Bands panel? So they can be configured in the same manner as the other bands.
A reason for this: to get a visual feedback of the filter frequency value without the need to (mouse) left-click-hold the red flag.

Suggestion for all plugins with modulators and multiparameters:
Could we navigate/scroll between different Modulators & Multiparameters using only 1 window? We could use arrows to quickly scroll between panels.
A reason for this: it avoids cluttering the screen with multiple panels + it avoids the need to constantly open and close multiple panels to access different modulators/multiparameters.

Suggestion for the MLoudnessAnalyzer plugin:
In the information panel results, would it be possibe to display,as well, the actual integrated LUFS value found for each processed file(s)?
Reason for this: to have a quick feedback of the estimated integrated LUFS without the need to open another audio app to get these statistics.

Suggestion for the mighty MDrummer:
The Presets Manager found in the MDrumReplacer (inside the "Drum Editor" panel) is absolutely great and extremely useful! Could we have this "Presets Manager" built into MDrummer? (inside the "Drumset Editor" panel)
Reasons for this: a better way to store and organize our custom drum parts + a better way to save multiple velocity layers and the FX section altogether + a better way to quickly substitute drum parts (layers+fx).

Suggestion for a new plugin OR the enhancement of existing ones :
I have a dream about a better and easier way to deal with panning in multitrack projects.
Would it be possible to develop a Panning plugin that could centralize the panning control for every track in a multitrack project? I mean, this plugin would be a panner to be loaded into every track of the project. Since different instances of the same melda plugin can exchange information between each other (see MMultiAnalyzer for example), my question is if it would be possible to allow multiple instances of this hypothetical panner to communicate and report panning data from every loaded instance, and be able to display it in just 1 single window? From this single window we could modify the panning for each track and have a better visual feedback for the whole mix.
Reasons for this panner: to be an alternative to the actual "scroll and spot" workflow in order to configure panning in a project consisting of 60, 80 or even more than 100 tracks.

Let us know what you think about all this!
Thanks

[Starship Krupa]

Would it be possible to develop a Panning plugin that could centralize the panning control for every track in a multitrack project?

Not only would it possible, it's already been done, but by iZotope, not Meldaproduction. So great for placing backing vocals.

It's free, too: https://www.izotope.com/en/products/visual-mixer.html

It might be a nice feature to include in the "Mix Revolution" that Vojtech has been teasing for years.

[Underoath77]

Mixrevolution needs to be a thing

Would it be possible to develop a Panning plugin that could centralize the panning control for every track in a multitrack project?

Not only would it possible, it's already been done, but by iZotope, not Meldaproduction. So great for placing backing vocals.

It's free, too: https://www.izotope.com/en/products/visual-mixer.html

It might be a nice feature to include in the "Mix Revolution" that Vojtech has been teasing for years.

[Hanz Meyzer]

Let me add my feature requests for MTurboFilter here:

- Being able to write box brackets [] into code/text-box when using MSoundFactory in Bitwig on macos. Does not seem to work.
- Live(?) indicator whether a code is valid or not
- S[] being able to repeat the last filter, e.g. S[peakanalog(f;q);;] would be three times peakanalog, S[peakanalog(f;q);;;LP(f,q);] would be 3x peakanalog and then 2x LP.
- More actual filter algorithms. Not just LP6 and multiples of that. Actual other filter algos. There are really good other algos, often available as public domain. C'mon, please! Have a look at Zebra, those filters sound great.

Some melda filters do not seem to work too nicely, if stacked up, e.g. peak multiple times in MTurboFilter sounds pretty ugly and instable to me. Also I have a hard time to actually peak some freuquency range in a surgical way. It sounds very imprecise.

For all filters:

A frequency analyzer view in all the filter modules could help a lot, which shows the graph relative to the base note / key follow parameter, so the graph stands fixed all the time. I hope you get what I mean.


Thanks for consideration.

[nonplussed_]

Could we navigate/scroll between different Modulators & Multiparameters using only 1 window?

This would be particularly valuable for usability of the FM module in MSoundFactory; if you're trying to line up the timing of N envelopes, you need N+1 windows open. One of the best things about NI's FM8 is the view of all the envelopes stacked vertically.

[Mrs_Midi]

Would be nice to process M/S, L/R etc without having to load multiple plugins.

[Hexspa]

Besides the EQ filters being available as bands, perhaps the red flags could update with their frequency cutoff. Doesn't need to be accurate to the decimal. 63Hz on the low end and 5.5k on the top would suffice.

Viva La Revolucion!

[Audiospaceman]

Not only would it possible, it's already been done, but by iZotope, not Meldaproduction. So great for placing backing vocals.

It's free, too: https://www.izotope.com/en/products/visual-mixer.html

It might be a nice feature to include in the "Mix Revolution" that Vojtech has been teasing for years.

Thank you very much for this great tip!
This is an excelent tool and very clever the way those guys at izotope achieved it!
Aaaand, i´m starting to get a little more curious about this mysterious "Mix Revolución"...

[Polluxmdq]

Suggestion for MDrumReplacer:
add a parameter for the retrigger delay/cooldown. When working with fast drums (for example a double kick drum playing straight 16s and every now and then will play a triplet or a couple of 32s) the plugin will only trigger the first hit and ignore the following 2-3 hits.

[MeldaProduction]

Thanks for the feedback folks, no time to reply, but I took some advices and ignored other, hope you don't mind.

[Hexspa]

I don't mind as long as it was my advice that you took

[Starship Krupa]

Would be nice to process M/S, L/R etc without having to load multiple plugins.

This would be my #1 feature request at the moment. I use different compressor release times for M/S in order to work the stereo field and at present, the only compressors I have that will do that in a single instance are the IK Multimedia Opto and 670, and Soundspot Cyclone.

If I'm loading a Soundspot plug-in instead of a Meldaproduction one, something is wrong.

[Held]

Would be nice to process M/S, L/R etc without having to load multiple plugins.

This would be my #1 feature request at the moment. I use different compressor release times for M/S in order to work the stereo field and at present, the only compressors I have that will do that in a single instance are the IK Multimedia Opto and 670, and Soundspot Cyclone.

If I'm loading a Soundspot plug-in instead of a Meldaproduction one, something is wrong.

I'm not sure if that's exactly what you want, but you can split mid/side in a single multi-band plugins.

[Starship Krupa]

I'm not sure if that's exactly what you want, but you can split mid/side in a single multi-band plugins.

I don't own any of the MB plug-ins except for MReverbMB, which I got in a smokin' deal at PluginBoutique. Truth: I have a hard time understanding how to use the "MB" part, and with my issues with Meldaproduction's sparse documentation, I have been afraid to spend any more money on them. It may be just me, but I find it difficult to impossible to apply the concepts from a video tutorial on reverb to a compressor. The way I learn is to start with a specific recipe for the tool that I'm using and then expand my knowledge from there. "Top down" I think is the term.

What I want to be able to do is use a compressor as I do my T-Racks Fairchild 670 emulation and Cyclone.

These let the user adjust all the compressor parameters independently for mid and side (or even left and right in the case of the T-Racks). The Meldaproduction compressors I have (and I have heavy hitters like MDynamics), when operated in M/S mode, work the way that these others do in linked mode, where the parameters for mid and side are the same.

To have independent settings for mid and side with the Meldaproduction compressors I have, I must set one instance to mid and then insert a second instance set to side (which suddenly gives me the idea to try two different compressors for mid and side, must do that). It's a pain in the dupa to have to switch back and forth and keep straight which is mid and which is side.

[Held]

I'm pretty sure the MB plugins will give you what you want. Set the mode to mid/side (or panorama for left/right) and the number of bands to 2. You can link the parameters to adjust them for all bands at once, and then unlink them to adjust them independently for mid and side.

Why not get the Demo of MDynamicsMB and try it yourself?