Some love for MXXX

[MeldaProduction]

dmbaer & Nspace: I got your point, but the value in MXXX is highly because of its modularity, but it's far from that. Yes, other developers are cloning our features for years and don't blame them , I get inspired too , that's progress. But there's so much more in MXXX. For instance, modulators - we have them for years and nobody even tried to get close, because it's such a complex unit. Now with the V9 improvements, it will take a long time before someone dares. And we have a complete set of pretty much the most advanced and best sounding units. Yes, everyone has a flanger even in the host. But for some reason even such a basic thing as custom shapes in flanger...only Melda has it from what I know, even in a free plugin . And there are plugins such as MSpectralDynamics, which don't have even a close competition at all. I'm not really afraid there would be a clone that soon, it will take years for most developers (if they would dare). And even in that case it's just not enough to devaluate the whole thing and Melda plugins in general.

farfadetfarfelu: External VST's are denied, period. That's where BlueCat has it's area and I'll let them have it . But since 50% of you are complaining about the reverb, I'll personally check it out when possible, just not so much time right now...
"buy modules as you go" - exactly, that's one of the big problems.

I personally consider MXXX as the Ferrari between effects. It's just expensive, because it is worth it. Could cannot want Ferrari for 150$ based on an argument that someone can make Ferrari clone . It will still be Ferrari, or MXXX...

Quite frankly originally I wasn't even thinking about different pricing models. I'd like to make this technology accessible by people, but more and more we discuss that, I see the classic patterns of people wanting something for cheap/free, which I understand, but makes me think that maybe we should make it simple and keep the normal licencing model...

[Scotty]

What about 3 options? One for Mtotal, one for Mcreative and one for the free bundle.

Option 1: Those that are Mcreative users would have a version at a reasonable price and you wouldn't be giving away your products. It the user was close to owning the suite an incentive bundle that would scale in price to completing the suite along with the MXXXX could be purchased. This might tip the purchasing decision. They could at the same time authorize the Free bundle which would be integrated and available once purchased.

Option 2: The same situation would apply to the MTotal suite.

Option 3: A third option would be offer the MXXX with only the Free bundle at a cost that makes it worth your while. The user might also be incentivised to purchase the free plugins if they were integrated into an MXXX environment as an option. You could monetize this bundle and continue to introduce people to your amazing creations. There is a lot of power in your free bundle... take it from there.

[MeldaProduction]

Scotty, I'm afraid that's a very overcomplicated approach that would immediatelly return to me as a bumerang...

[Nspace]

dmbaer & Nspace: I got your point, but the value in MXXX is highly because of its modularity, but it's far from that. (...) I'm not really afraid there would be a clone that soon, it will take years for most developers (if they would dare). And even in that case it's just not enough to devaluate the whole thing and Melda plugins in general.

I personally consider MXXX as the Ferrari between effects. It's just expensive, because it is worth it. Could cannot want Ferrari for 150$ based on an argument that someone can make Ferrari clone . It will still be Ferrari, or MXXX...

Quite frankly originally I wasn't even thinking about different pricing models. I'd like to make this technology accessible by people, but more and more we discuss that, I see the classic patterns of people wanting something for cheap/free, which I understand, but makes me think that maybe we should make it simple and keep the normal licencing model...

(italic + brown coloring is mine)

Well, the idea of MXXX base to be split in LEGO modules was mentioned to ease access by way of allowing separate partial payments, that could even get to a higher total payment at the end. As said in a previous post:

keep Mxxx valuable base, but "separated" in LEGO functional modules by grouping its basic functions (modulation, multichannel band splitting, copying/leveling/comparing, etc., etc.) and sell them in blocks. This way potential buyers with moderate expense limit, will have a way to acquire MaXX, then MbXX and lastly McXXX for.. EUR70 each, forming MXXX in stages to which we will add our existing Melda plugin licenses.
Such modular growth would also set the path for future developments and new functionality to be add later, providing a way for us to pay for each new module.

The results with such option could be;
-1, more budget limited customers -we- may buy MXXX by sequential payments, totaling EUR210 in the above example, which is not the case of wanting it for cheap/free...just the availability of smaller partial payments related to partial functions.
-2 It would define a payment-functionality connection for MXXX where future functional additions can get charged.

- On the "buy modules as you go", (...) things can get really complicated. For example people will load presets just to realise they can't use them because they are missing this or that module.

farfadetfarleu. Yes, and the inability to use certain presets/functions could be made explicit in the modules promotion, hence constituting another incentive to buy the remaining modules; Sinergeticly when you complete the puzzle, you get extra powers.
///If technically modular MXXX is feasible, I just see advantages for both developer and users.

[id4kvr]

I deemed it just like something about ableton's effect rock previously,but,absolutely it's more flexible and powerful!

[MeldaProduction]

I'm thinking about the "lego" idea . It will take some time, now the major update is the main task.

[gentleclockdivider]

Anyone else having problems when certain modules are used ...slow gui refresh rate/unresponsive etc..?

[gentleclockdivider]

I personally consider MXXX as the Ferrari between effects. It's just expensive, because it is worth it. Could cannot want Ferrari for 150$ based on an argument that someone can make Ferrari clone . It will still be Ferrari, or MXXX...

Yes , great quality efffects , but very poor execution in almost everything .
Bring up the analyzer , and everything start to slow down ...and I have noticed this in numerous melda plugins
Sluggish gui , non intuitive evelopes etc.
This is not the only 'out of the box 'modular effect , have you tried 'psp N2o ?
It's a beast
http://www.pspaudioware.com/plugins/mul ... s/psp_n2o/
I am aware of the fact that a lot of work has been done for the framework etc..but as a modular effect plugin it doesn't invite you to experiment ( muy opinion )
A nice clear gui :audiomulch approach , and not a billion pop up windows would make things much easier .

Other than that , I think you have a winner here , and maybe I should ust upgrade to a faster computer

[MeldaProduction]

So again - what kind of computer do you have? Btw. if you have a laptop with Intel HD, please switch to the main GPU (I suppose all reasonable laptops have NVidia or AMD onboard). And ensure the GPU acceleration is enabled - click Settings / GPU acceleration. Also I assume you are using 9.00b3, if you are still on 8.10 please update (though the official 9.00 release should be probably tomorrow).

[gentleclockdivider]

Ohh I hve avery slow laptop , dual core ( about 6 years old )
BUt altough the audio cycles remain moderate , it's the gui that get sluggish , when certain modules are activated.
But yes, I definately should upgrade my pc.

[MeldaProduction]

The graphics generally depend on your GPU and speed of one core, so it's not surprising in your case. Though I'd suggest forcing the dedicated GPU if you have one.

[gentleclockdivider]

Hi Mr.melda , me again ..
I love the modular effect, more so then the synth ..
Anyway , been playing with the delay line , nice sound ..interpolated ..meaning no glitches when moving the time slider ..nice ...EXCEPT ....when modulating the time by an lfo, envelope follower . ...cpu boost .;
This happens when the modulation range is big , I know that interpolated delay lines require more cpu resources , but
what's the meaning of an interpolated delay line when there is only a limited modulation range before cpu problems occur , these are the same problems that occur in the synth .
PLease understand that I don't want to nag about anything , just making something clear here

[plexuss]

Also Zebra 2 does this kind of thing with almost the same UI as MXXX. I installed and opened MXXX but didn't try it as it doesn't suit my workflow. I typically mix and match plugins from different manufactures when I am working on music. I wouldn't have much use for a melda-only tool like this. but my first impressions were "oh. like the way Zebra does it..." good idea for a effects tool especially from melda. bundling together a bunch of melda plugins in MXXX would be interesting but for me not something I'd use really.

[gentleclockdivider]

Sure , there are some similarities , but does zebrify has unlimited x-over filters for the input signal? , I don't think so.
Zebra has no interpolated delay line etc...
I really like this plugin , Its a quick substitute for reaktor , when I don't feel like patching .
But I think areas need some improvements .

[plexuss]

Sure , there are some similarities , but does zebrify has unlimited x-over filters for the input signal? , I don't think so.
Zebra has no interpolated delay line etc...
I really like this plugin , Its a quick substitute for reaktor , when I don't feel like patching .
But I think areas need some improvements .

What I meant was the concept. Zebra uses the same concept in the context of it's feature set.