MeldaProduction

secretkillerofnames · Mon Feb 27, 2017 10:03 pm

MeldaProduction wrote:
- MEqualizerLinearPhase and MAutoEqualizerLinearPhase removed, only MAutoEqualizer would exist with optional linear-phase mode and latency adjusted depending on the mode. Users of MEqualizerLinearPhase would receive a licence for MAutoEqualizer.

Will the functionality of the originals remain intact? That would be my concern.

Batty · Post by **Batty** » Mon Feb 27, 2017 10:26 pm

Adding to MMultibandDelay (which might be named MDelay)...
Please add a tap field, which can be tapped with the mouse.
The speed of the tapping should make the plugin find out the speed of the delay, which for me is the fastest way to find the delay of taste (like running the song and tapping how one hears the delay in one's head, without the need to think about numbers). Especially, when the need is there for a non synch delay. This could save many many minutes, tweaking.
A tap for each band/delayline. I often feel overwelmed by the many possibilities, if I just need a simple delay...very fast. What do you think?
I used a delay that had this function - but it was 10 years ago and it no longer functions.
Oh, how I miss this one.

All the other changes do sound great indeed.

goldglob · Post by **goldglob** » Tue Feb 28, 2017 2:38 am

I can see the reasoning behind making these changes but I think the backwards compatibility problem could be huge.
I wonder what percentage of Melda users actually follow the Melda news (here, facebook, the Melda site etc)...I guess every Melda user should be contacted by email and made aware of the proposed changes and given the opportunity to react.
Like DarkStar says, we need an MMagicConverter...and I guess each DAW would need it's own version of that... would it have to involve actually re-writing DAW project fies?
I'm all for cleaning thngs up etc but sadly I'm seeing a nightmare...?
But maybe Vojtech can figure this out.

Chandlerhimself · Post by **Chandlerhimself** » Tue Feb 28, 2017 2:52 am

All of the changes sound fine to me. Besides longer delays in MMB there aren't too many problems. The only thing I can really think of is more saturation options in MFilter and maybe a few more filters. Compared to MWobbler and MPS the filter selection looks a bit bare bones. I realize that many of the filters in MW and MPS actually use more than one band, so maybe it's difficult. Perhaps a preset selector that works on multiple bands would work. People could select more complex shapes such as formant filters or LP/HP filters easily. It's a small thing, but more saturation and the ability to quickly mark morphing filters might make for a more useful plugin.

Besides that I can't really think of anything else that needs to be changed.

Chandlerhimself · Post by **Chandlerhimself** » Tue Feb 28, 2017 2:55 am

goldglob wrote:I can see the reasoning behind making these changes but I think the backwards compatibility problem could be huge.
I wonder what percentage of Melda users actually follow the Melda news (here, facebook, the Melda site etc)...I guess every Melda user should be contacted by email and made aware of the proposed changes and given the opportunity to react.
Like DarkStar says, we need an MMagicConverter...and I guess each DAW would need it's own version of that... would it have to involve actually re-writing DAW project fies?
I'm all for cleaning thngs up etc but sadly I'm seeing a nightmare...?
But maybe Vojtech can figure this out.

I don't see how there would be any problem with backwards compatibility. Just use the V11 for new projects and keep V10 on your HD. Old projects will use V10 and you can use the newer versions for new projects. Seems simple to me.

ElevatedBeing · Post by **ElevatedBeing** » Tue Feb 28, 2017 3:38 am

Yeah, draw a line in the sand.

Keep v10 on the site for people to download for older projects. Change the look in the installer, and warn people that this is the future of the Melda plugins. This should clearly signal that this is something entirely new.

So please, tidy up og fix all the small issues and lets take Melda plugins to the next level.

/Jesper

Svama · Post by **Svama** » Tue Feb 28, 2017 5:49 am

@batty, you can already tap the Tempo. I think it was holding alt and left click the delay.

For the Update v11. I think we need a beta version, so the people can see how does the backward compability work. We have two opinions in the forum. The do it and don't do it ones. The problem is people who are making money out of your plugs are afraid about this update and I understand. The fun mixers like me like the idea and hope for a fast release of v11, but a beta version could comfort the skeptical people.

vectorwarrior · Post by **vectorwarrior** » Tue Feb 28, 2017 6:00 am

Yeah svama that's exactly it. If it's trouble free I'm 100% for it. I'm just a little worried currently.

Tagirijus · Post by **Tagirijus** » Tue Feb 28, 2017 8:47 am

Overall I am for tidying up things as well. I am also with vectorwarrior and Svama though. To me all the changes would be not the problem right now, but at the moment I do not have a big ongoing project like vectorwarrior, so I have easy talk on this.

... but I can confirm that it could be some kind of problematic, when you are in a project and the old projects do not work anymore. So first a beta to see if everything will still work, is a good idea.

MeldaProduction · Post by **MeldaProduction** » Tue Feb 28, 2017 9:52 am

Well, I read all your comments and thought a bit more about it, and I'm getting negative about this...

Damn... The problem is that for sake of just changing the names and keeping the automation parameters intact, one would have not 100 Melda plugins there, but 200... That doesn't seem like a good idea... Perhaps the best way would be indeed to create some backward compatibility option for those, who are dependent on the automation and keep the plugins the way they are... Damn... and I so wanted a clean slate

.

valsolim · Post by **valsolim** » Tue Feb 28, 2017 10:06 am

MeldaProduction wrote:Well, I read all your comments and thought a bit more about it, and I'm getting negative about this... Damn... The problem is that for sake of just changing the names and keeping the automation parameters intact, one would have not 100 Melda plugins there, but 200...

But you wrote about the possibility to install V10 alongside V11. So, there would be 100 plugins (V10) for backward compatibility and 100 completely new plugins (V11) for new projects. For the old plugins, add the suffix "V10" to their names and keep their GUIDs. For the new version, do whatever you want and generate completely new GUIDs. I really can't see any problem here...

--
Miloslav

MeldaProduction · Post by **MeldaProduction** » Tue Feb 28, 2017 10:19 am

Unfortunately that doesn't work like that... GUIDs don't work for many hosts, so the names are what we have to count on. Also there's no way to switch between the 2 seemlessly...

Svama · Post by **Svama** » Tue Feb 28, 2017 10:57 am

It's correct, at the beginning you're working with many numbers of plugins, but from time to time you hopefully won't need the version 10 anymore, but people must tell, who are bound on both versions and the great Vojtech for sure, to say what is possible.
A beta v11 isn't possible that easy for checking?!
At the moment it feels like all sides are little bit frustrated, me too, the happy fun mixer, who never earned a penny for hours and hours of work;-)

MeldaProduction · Post by **MeldaProduction** » Tue Feb 28, 2017 11:01 am

A beta would take a lot of development, since this is all in just planning phase. But I'm starting to be against it all... The automation compatibility mode will be a crazy thing to do, but I have it quite figured out. It's just a little sad, that we cannot do an easy transformation... Well, that's technology...

Thavma · Post by **Thavma** » Tue Feb 28, 2017 11:30 am

More presets on MXXX would be awesome!

MeldaProduction

KVR Audio

V11 proposed changes