About the next MuLab 9

[pljones]

To get some idea of how the development cycle works, go check what M7-final had in terms of features. Then what M8.0-initial-release had - i.e. what upgraders got. Then compare that with what M8.x has now and see what else has gone into M8. That should give you some idea of the scope for what could go into M9 and why asking for a definitive list isn't sensible -- the initial step from M8-final to M9.0-initial-release may only be the listed features but there's an M9.x future ahead.

[oldguy]

Jo,

Bump on VST 3. Some developers are dropping VST2. For example, I'd like to install Melodyne 5, but it requires VST 3. It would be nice to make this work w/o having to test and find a wrapper plug-in. As someone else mentioned, it could even be klugged in with a transparent wrapper that's stable.

-oldguy

[heks]

Just having VST3 support would be well worth the Mulab V9 upgrade price for me, without any other enhancements .

[Bady89]

Can anyone explain the noob here what a clip Launcher does better than the sampler ?

Or are we targeting for live performances now ?

[syntonica]

VST3 has to be the one most needed upgrade, despite the hot mess that is the VST3 SDK. As previously stated, with Steinberg trying their best to discourage/kill new plugins from using VST2, I am seeing some VST3 only plugins starting to show up. Using a host plugin works, but it kills the immediacy, having to open it up, then open the plugin itself and finally, close the host window since it's always in the way. Maybe an integrated wrapper? I believe the VST3 SDK has one you can use as a model to integrate into MuLab. It should only be a tiny CPU hit for us users, but seamless integration bliss at the same time!

As for the lifetime license, if I hear you are moving to that, I will be worried that your doctor just told you that you have 6 months to live. I think it works for FL since that also get additional revenue streams through their plugins, plus their new entree into the Mac world with FL Studio for a previously untapped market.

Clip launcher? ¯\_(ツ)_/¯ I have no use for one...

Please stay healthy and safe! I know the latest plague Mother Nature has thrown at us has affected all our lives, mostly negatively, but I can wait a few more months delay for the arrival of v9.

Maybe.

[SparkySpark]

VST3 has to be the one most needed upgrade, despite the hot mess that is the VST3 SDK. As previously stated, with Steinberg trying their best to discourage/kill new plugins from using VST2, I am seeing some VST3 only plugins starting to show up. Using a host plugin works, but it kills the immediacy, having to open it up, then open the plugin itself and finally, close the host window since it's always in the way. Maybe an integrated wrapper? I believe the VST3 SDK has one you can use as a model to integrate into MuLab. It should only be a tiny CPU hit for us users, but seamless integration bliss at the same time!

Interesting. I take it you didn't see my post a few pages back, so for your reference, I put it below, and put the most similar parts in bold.

Anyway, I don't think VST3 integration is to be expected atm, but hopefully this will get resolved with time. Personally, I like the idea of an integrated wrapper (obviously). At the same time, I figure things might not be so easy technically speaking, and that the only thing that actually works for every possible situation is proper integration. After all, an SDK and an API are there to help tackle these problems already. So I can understand if Jo and others cannot take this easy route - but it surely looks appealing!

1. VST3/ARA2/WaveShell: Keeping up with standards is obviously troublesome for a one-man company. Moreover, except for connectivity, they don’t bring any extra features in themselves. What I’m thinking is that instead of putting in, say, 18 months’ work on such matters, and then having to redo it as these standards progress and new appear, why not work with one of the wrapper dev’s? I installed Kushview’s Element (freeware) yesterday and suddenly I can run Waves software, AAX and probably more things inside MuLab. It works without a glitch.

I’m thinking that the chosen wrapper wouldn’t have to show up, but instead work behind the scenes. Then, as an option (like a button in the VSTi’s top menu (=MUX) bar), the wrapper itself could be shown, allowing for other intricacies. Maybe this is not ideal, but it can – perhaps – be a great time saver when it comes to development. And more importantly, with the right choice of built-in wrapper, MuLab (and maybe MUX) would be future-proofed as well. Besides, MuLab is rock solid in its current state , and writing code to talk to other standards can maybe mess things up and cause instability under certain circumstances.

Not sure this can work, but if it can, it could be a game-changer.

Having worked as a software developer, I think it would be more fun to develop new code for new features than work with interpreting standards. Having fun at work is an important theme, especially in the music software industry as we programmers can all get better pay in other places.

[MuTools]

As for the lifetime license, if I hear you are moving to that, I will be worried that your doctor just told you that you have 6 months to live.

Luckily my doctor did not tell me such thing

Please stay healthy and safe! I know the latest plague Mother Nature has thrown at us has affected all our lives, mostly negatively, but I can wait a few more months delay for the arrival of v9.

Best wishes to you too!

[Uchmania]

By any chance are we going to get a razor or split/slice tool for midi notes and clips?

[pquenin]

I have a MUX 7 user key, but I don't see how the new features introduced in M8 and M9 can be incorporated in MUX, or how to use them if they are. They are essentially "standalone" features (Audio sequences with timestreching, launch clips)...
I more tempted to buy a Mulab user key (I have also a M5 user key atm) but well, there is this VST3 thing I have to take into consideration...
For the future, If Mulab and MUX are merged, that sounds great to me...
This is the case of Reason now, it gives you lot of freedom to decide how to make your music...

[syntonica]

Just one wee feature request:

An autosampler to sample any hardware/VST instrument and create a multi-sample out of it. I can do it manually with sample chopping and lots of busywork, but to have the process automated would make me very happy and productive, indeed!

Just a small window to choose a track to sample (so effects may be applied), the number of steps between each sample, sample volumes, and sample length. All the samples properly labeled and tucked away in a folder living amongst the other multi-samples would be perfect. Many of us have little hardware units (or, wall-sized Euroracks) with no preset saving that this would be great for.

If somebody has a simple workflow for this now, I'd love to hear it! Thanks.

[Compyfox]

I don't know if this was mentioned yet, but personally I'd love to see the following in M9 (MUX Modular in my case)

- Event Generator: CC Trigger (just triggering a note) / CC Toggle (first press results in one set MIDI CC, the second sends another set MIDI CC - e.g. toggled/pressed down = MIDI CC #20 Value 12ü, unpressed/button up = MIDI CC #20 Value 0)

- for UI creation: background jpg/png loading, groups where we can remove the "group name" and also use jpg/png loading, removal of Note Pad Trigger Name (so that only the trigger is shown, and/or that the name is in the middle of the trigger pad)

- control over input/output ports/amount of MUX modules (currently limited to stereo in/out

- marking several modules, right mouse click, then "move into container"

- Labels in modular view (see next point)

- a "notepad" module or even an additional UI component for better documentation

- MUX as standalone EXE (I currently use Tone2 NanoHost, but I can't set the input, only MIDI Input/Output and Audio Output)



I am currently creating a custom DSP processor as standalone module, and I highly miss MIDI CC triggers/buttons/switches. I found workarounds, but I needed to utilize custom MIDI processors (InsertPiz) to turn Note Event Pads into buttons (triggers). And I can't really set the audio input here, and the UI is a bit bland.

But once I could wrap my head around it, things work nicely for the time being.

[diasporah7]

I had to log in just to say Sparkysparks idea about exporting MUX to VST(I) would be a awesome way to bring in new users. In fact this idea is gold. Essentially getting a promo to Mulab each time a cool mux is released. Could make exports free for users but in demo for 30 days for users who don’t own Mulab. Sounds like a game changer indeed

[RobKastler]

I am currently creating a custom DSP processor as standalone module, and I highly miss MIDI CC triggers/buttons/switches. I found workarounds, but I needed to utilize custom MIDI processors (InsertPiz) to turn Note Event Pads into buttons (triggers).

The absence of buttons/switches in MUX is beyond me ...

[SparkySpark]

I had to log in just to say Sparkysparks idea about exporting MUX to VST(I) would be a awesome way to bring in new users. In fact this idea is gold. Essentially getting a promo to Mulab each time a cool mux is released. Could make exports free for users but in demo for 30 days for users who don’t own Mulab. Sounds like a game changer indeed

And I had to login just to say thanks.

Seriously though, I agree (obviously) and I also like the way you expanded on the idea.

[pquenin]

maybe you can add transport, mixer, tracks modules and so on, and have a "save as VST DAW" export option ?