MXXX Improvements & Feature Requests

[dmbaer]

... normal users will only save normal presets usually. Active presets are for preset creators, which is kind of "high-class" community and hence we can assume some technical capabilities.

Well, perhaps it's just an issue of documentation. The dual namespace of presets is at this point unfathomable to me. I do not understand, for example, what is meant by the statement "Active presets are for preset creators". I would think that an ordinary MXXX user would do some tweaking now and then and want to save their modified preset, just as many of us do for synth sound presets.

But as I said, maybe when the documentation is available hopefully this will all become clear.

[MeldaProduction]

Basically, an "active preset" is like a plugin withing MXXX. It assumes there will be controls defined etc. Classic Presets (accessible via the normal preset button) are just settings.

[Tagirijus]

Woa ... what a great idea! I am really looking forward to it (or is preset-saving for "active presets" already possible?) !

[DarkStar]

As I understand it ...

In most of the plug-ins "Active presets" are those on the left-hand side of the "Easy" window.

These are different from normal presets as they can actually have a few controls available via knobs or buttons. Click on an preset to load it. Check our video tutorials for information about creating your own active presets. Despite you cannot put your own active presets into this selector, you can still save them as normal presets while these will work the exactly same way.

So, yes it is already there but you need to save them in a folder (perhaps "My Actives" in the Presets window

In MXXXX it is different, the Active Presets are in the top panel of the "Easy" window (it may be collapsed for you). They are tagged with keywords and so the list can be filtered. I am sure that I saw a way to save and tag a new Active Preset but I cannot find that now.

[DarkStar]

- Multiparameter switch buttons - sorry, but cannot be done, for technical reasons, but mainly because you can actually have multiple multiparam windows open at the same time.

Somewhat related: how about adding the name to the Multiparameter title bar to make distinguishing them easier? For example "Multiparameter 1 : Color"

And perhaps the Modulators could have names too? (Apologies if I have requested this in the past). As in this mock-up:

... Big pic: http://i.imgur.com/ps3ORgx.png

And, of course, the modulator names would be displayed on the main window.

(This is not just for MXXX, but for all the plug-ins)

[vectorwarrior]

+1

[dmbaer]

+1

Ditto!

[xNiMiNx]

I'm not geared up to do video (which, for MXXX, could run for hours ), but you might be better to ask a specific question in a separate thread for some guidance.

I only asked because its useful imo. Even a video starting out with a specific goal (ie make a mastering preset for drums) and walking through the steps, or, just messing around with no specific goal. Some devs upload videos of themselves playing with their creation, nothing too planned. I find it very informative, sometimes i look at many things from new angles.

If in the future there is another preset event(? for lack of a better word), a help file and or video(s) (of any type really) would do nothing but better my preset quality, and get me moving along faster. [edit] And of course, either would be appreciated. [/edit] I would go out on a limb and say it would help others, and the quality of their presets as well.

[MeldaProduction]

darkstar: Multiparam names in the title added to the to-do list. But not for modulators, sorry, you asked several times actually , I admire the persistence . Anyway there's just not enough space. I'm counting the mods to be small, so there can be several of them. Otherwise the GUI would get huge or the name gets cropped which considering it now has 4 characters would be almost always...

Video: Yeah, I agree... Sadly, the video should have been done by a new employee of mine, which has already been fired for incompetence... so much wasted potential in him... Anyway I'd like to create several video tutorials myself after it gets released (so it has the final "looks").

[ZentralmassivSound]

It's more a question than a feature request: I wanted to compensate for the latency of the harmonizer plugin, and I see there is the new DelayTap block with a sample rate conversion option, but it does not really make sense to me, how do I use it?

So I assume the latency of plugins, e.g. the harmonizer, is sample rate dependent? And how can I configure a delay compensation that works right at all sample rates?

Sorry if this was answered before.

[MeldaProduction]

Hehe, just check the help for "Scientific delay" panel . Basically you set the number of samples and use the "Convert" feature if needed. If it is Off, the number of samples will stay for all sampling rates. But instead it lets you also convert it to target sampling rate (assuming you are working in 44k or 48k as these are the most common) and it lets you also make it power of 2 (2^n), which is pretty common.

For example with Harmonizer in Vocoder highquality mode it seems 2048 samples and convert "from 48k 2^n round down". The only way is to just test really. There seems some ringing, so I guess it's still +- sample, additional switch is probably needed...oh well...

With MSpectralDynamics and linear-phase crossover the latency is the same for every sampling rate for example.

[ZentralmassivSound]

I checked the scientific delay help, and now I read your post, but still I am not sure I get it

So you mean if I work at 48k and see 2048 samples latency for some plugin, then on a parallel chain I should add a DelayTap with 2048 samples and "from 48k, 2^n" checked, and then the DelayTap will take care for a correct compensation at all rates? Basically the number in the "convert" field states the rate at which the compensation was configured originally?

[MeldaProduction]

Yes, basically the "convert" parameter states how the delay should be adjusted for different sampling rates.

Anyway full automatic latency compensation may be possible after all! Just give me some time to figure it out.

[MeldaProduction]

Ok so MXXX WILL have a full automatic latency compensation.

[ZentralmassivSound]

Ahhhhhh really nice