MUX Vst : What do you need?

[AndreasD]

@bmrzycki:
i can only answer to a few of your questions:

2: Osc fatness is indeed a stack of detuned osc voices. At the moment there is no modulation possible for fatness and the related parameters. But a work around might be to use mutiple osc each with fatness=2 (=3 voices, center/up/down pitch), different detune and osc pitch modulated. As the number od osc is not restricted, you can even build the Roland supersaw by 15 seperate osc

3: I have no idea about Jo's plans about scripting, but i am already impressed by what is achievable with the current means! And don't forget, you can use any VST in a Mux.

5: PWM is a straight saw wave with the AIPS modulated. Results in an exact PWM

[fluffy_little_something]

15 oscillators I wonder if it is worth wasting so much CPU power on one sound, especially as long as there is no multi-core support.

Sometimes one is tempted to put too much emphasize on the technical aspects of sounds and recording in general. But usually the music does not get any better just because one uses, say, a super saw instead of a normal saw sound. If a song does not appeal when done with simple tools, it is probably not a good song to begin with.

Sometimes I find myself spending too much time on that modular approach, adding this module, removing that module etc. Since I am not physicist, it is not always easy for me to understand which modules to use and how to use them in order to achieve a certain sound. It would be easier if I had some sort of analyzer for sounds I like in some song I like. Based on the analysis I could decide which modules are necessary to emulate the sound. Currently it is more like try and error and I find myself using more and more external VSTs to get what I want

With complicated sounds what might be helpful is module categories being color-coded by default (I know one can color-code individual modules manually). For instance oscillators in red instead of the standard gray.

[liquidsound]

That's why I'm a preset-coholic

[AndreasD]

That's why i'm a MUX deep editor - coholic

[fluffy_little_something]

That's why I'm a preset-coholic

Really? Well, I never use presets in songs, simply to avoid the wearing the same dress situation, should anyone ever hear my crap
But as a basis for my own patches, yes of course. I don't want to spend more than 15 to 30 minutes on one sound, so modifying a good preset is way faster than building a patch from scratch. Unfortunately, DAWs/VSTs usually come with few good presets, at least for my music. Younger people might like those patches, though, dunno.

(What is that script running on this site?! Chrome sometimes tells me there is a script running on this site and slowing down all things Flash, eventually making Chrome crash. I have disabled Scripts for this site now, so the smilies don't work anymore.)

[MuTools]

"MIDI Clocks" is a standard term. It's 1/24th of a beat = quarter note. It's independent from the PPQN resolution.

Anyway, i understand the "x/24th" notation is confusing because it's referring to 1/24th of a beat while eg 1/16th refers to 1/16th of a measure. In the next version the 1/xth of a measure notation is always used. That's a quick short term solution. Further improvements may come lateron.

The next MuLab version M4.2.1 will be released soon.

Unfortunately i struggled some more with this one.
I only see one immediate solution at this point:
The "x/24" notation should be replaced by "x MIDI Clocks", which is more correct.
But as "x MIDI Clocks" is too long for the current UI fields, "x MClocks" is used. This is implemented in M4.2.2 which is available at http://www.mutools.com/mulab/cedar/

What's changed in M4.2.2:

• Tempo synced echo now uses the more correct "MClocks" units instead of "/24" units.
• Parameter Event Generator now shows the effective parameter value instead of a generic "x %".
• MIDI Controller Generator did not yet apply the correct MIDI channel.
• Finetuned skin.

[MuTools]

Is the MUX VST going to be a single .dll file? Id prefer it to be as I don't want to have to install it as that causes problem if using on usb drive.

It will be a zip package like MuLab.

[MuTools]

1. I noticed MuLab uses a serial key -- will MUX use the same or similar (key file, serial) form of copy protection?

MUX Vst 1 will use the same copy protection as MuLab 4.

2. In the oscillator youtube tutorial I saw a "fatness" parameter. I assume that does some sort of voice stacking and detuning? If so is it possible to send non-linear event input to the value? I ask because a big part of the JP6000 super-saw sound was how the non-linear detune and respective saw balances were adjusted with respect to each other. I'd like to have this level of control when shaping sounds and I hope it's there.

Not yet, but it's planned.

3. Are there any plans for a script-able language (Lua, Javascript, Jesusonic, etc) to build MUX modules? I think I can use ReaJS inside MUX to get most of what I want but was curious as to your take on the idea.

Not yet.

4. How does MUX handle PDC? Let's say MUX loads a VST with X PDC and Y PDC where X < Y. Does MUX report X+Y to the DAW or does it analyze the signal path to determine the longest chain and report that? In the example above if X and Y were in parallel then the logical thing to do is report Y to the DAW.

No automatic PDC yet. But you can do it manually using the "Pure Delay".

5. How does the internal OSC do PWM? Does it have a concept of wavetables or some sort of osc start <-> end osc and intelligent morphing? I liked what I saw in the OSC video but it left me with a lot of questions that I could probably answer/discover after playing a bit.

Andreas is right: Use a Straight Saw and AIPS.

6. Any ETA on pricing/availability?

Price will be announced on release. Release is planned for July. A first test version will be available very soon.

[MuTools]

A first time-limited test version of the MUX Vst for Windows is available here:

http://www.mutools.com/mux/cedar

Known issues:

• In some setups, the MUX Play Editor window is not resized when changing patches.
• Using MUX Vst in Reaper 64 bit using the 64 bit bridge is not stable.

Looking forward to your feedback.

[bmrzycki]

Price will be announced on release. Release is planned for July. A first test version will be available very soon.

Thank you very much for answering my questions. One last one: will MUX be available as a 64-bit VST?

[Juan Mendoza]

A first time-limited test version of the MUX Vst for Windows is available here:

http://www.mutools.com/mux/cedar

The party has started

[MuTools]

Price will be announced on release. Release is planned for July. A first test version will be available very soon.

Thank you very much for answering my questions. One last one: will MUX be available as a 64-bit VST?

Yes, at some point in time.
But i cannot yet answer the question when exactly that will be.
Step by step i'm taking the steps to be able to build the 64 bit versions of MuLab and MUX Vst.

[MuTools]

A first time-limited test version of the MUX Vst for Windows is available here:

http://www.mutools.com/mux/cedar

Known issues:

• In some setups, the MUX Play Editor window is not resized when changing patches.
• Using MUX Vst in Reaper 64 bit using the 64 bit bridge is not stable.

Looking forward to your feedback.

About the editor resize problem: Up to now i noticed it in these 2 situations:

1) In Cubase.
2) In Reaper x64 when using the x64 bridge.

Wrt Cubase: I've researched the Cubase editor resize problem and i can only conclude it's a Cubase problem. I'm not going to R&D special trickery to make it work for based on the info i found this would not make much sense. So i'll list this in the docs as a known Cubase issue. Workaround = In Cubase when the MUX Vst editor is not properly sized, close and reopen the MUX Vst editor. Then the size will be ok. Normally this is only needed after having changed the preset.

Wrt Reaper x64: I assume it's a Reaper x64 bridge issue. Solution will be to have a proper x64 version of MUX Vst so that the Reaper x64 bridge is not needed anymore. In Reaper x32 MUX Vst works fine.

[bmrzycki]

Wrt Reaper x64: I assume it's a Reaper x64 bridge issue. Solution will be to have a proper x64 version of MUX Vst so that the Reaper x64 bridge is not needed anymore. In Reaper x32 MUX Vst works fine.

This is precisely why I asked about 64-bit VST. Thank you for the responses and honest feedback.

[MuTools]

Yes i agree on the importance of a 64 bit version of the MUX Vst. Working on it.