mxxx-reloading an active Preset???

[Arrested Developer]

Hi, if i want to do some further editing on a saved active preset, how can i do this?
It's not possible to load it.

[MeldaProduction]

Hi,

what do you mean it's not possible to load it??

[Arrested Developer]

I'm on MacOS 10.6.8

I can save Active Presets to:
Users/username/Library/Application Support/MeldaProduction/MeldaProductionMXXX/Active Presets

I can load Presets from:
Root (not defined where this is, no possibility to find it) /


Edit:

i see, i can load my active presets when the edit window is closed.

However, in that case i have to retype the information and all the tags, since they are not recalled
when i open a saved Active Preset.
Lost hours with that ...& it's destroying my nerves.
Maybe you could find i way that tags & info is recalled.

[MeldaProduction]

Aaaaaha... actually you can temporarily save it as normal presets via the "Presets" window. But I agree that the tags should get recalled and I'd like to have a tree view so that the presets are easier to find.

[Arrested Developer]

Aaaaaha... actually you can temporarily save it as normal presets via the "Presets" window. But I agree that the tags should get recalled and I'd like to have a tree view so that the presets are easier to find.

I do this. but it keeps the name, the tags and the information of the last active preset.
So the only thing is to do a screenshot when saving for the first time.

[MeldaProduction]

True, that needs to be improved.

[Tomgu]

I'm looking forward to this improvement as well.

Also, any chance you'll disable the demo noise for the rest of the month? I installed MXXX two weeks ago but unfortunately I could start with the presets only a few days ago. I'm sure most people would enjoy working with MXXX more without the noises, leading to better presets!

[MeldaProduction]

Today / tomorrow .

But sorry no extension, I could extend it to 31 days like MPowerSynth, but it seems a little too much... after all it works fine with the noise, it's like once a minute, not such a big deal. It will at least make you work harder, so you can get a licence earlier .

[Arrested Developer]

The update is here, so i have a final question:

Two of the plug ins can't be validated in Logic (MAnalyser and MLimiter).
Does this affect mxxx?

Second question:

In some presets that use reverb i made a transformation shape that bypasses the reverb when the
mix is 0% (but only then!). Is this useful in terms of cpu usage, or is it better to leave this option away?

[MeldaProduction]

Aaaaah, Logic validation... Please restart OSX, install the plugins again and try to revalidate. If it won't work (which I believe it will), send me the AU validation logs to info@meldaproduction.com please.
And no, it doesn't affect MXXX at all.

2nd question - it's fine to bypass MReverb to save CPU, it's there for it after all, but note that when the users then enable the dry/wet it will take some time before the reverb adjusts. You may hear echoes from the previous time it was enabled etc.

[Arrested Developer]

Thanks for your answers!

I will send you the logs, asap.

For the reverb: I can write a short note in the information window about that.
I think, if somebody will play with the amount of Reverb, he still has the range from 1-99% (1% is almost the same as no reverb).
So it's an opportunity rather to skip the reverb.

[MeldaProduction]

Sure , no problem