MuLab 9.0.59 App + Plugin

[MuTools]

I hope your planning some down time at Christmas Jo, to recharge your "batteries "

Thanks Heks I admit i'm a bit overworked at the very moment, last weeks were very intense with many short nights. So i indeed have to balance and take care about healthy well being.

and I hope you and everyone here has a really good Christmas

I also wish you and everyone here on the MuTools forum a fine & fun Christmas & Newyear season

[carlca]

Working full speed on reaching the point where also MuLab 9 for Mac and MuLab 9 Plug-In can be shared. Still a handful of items on the todo before that point.

No worries, Jo! I remember when I was working in development. When I was asked by my colleagues when the software would be ready, my standard reply would be "Do you want it tomorrow, or do you want it working?"

Can I just echo @heks words and wish you and yours a refreshing and happy and healthy Christmas and new year

[syntonica]

One thing in VST3's favor is that it looks likes all the open source projects, like Surge and Dexed have gone VST3 only, no doubt due to SB's new, possibly nefarious, licensing schemes. VST2 is no longer directly supported. VST2 has been quite "good enough" for ~30 years now. It may not be the most efficient, but it's universal. The King is dead! Long live the King!

CLAP should be a good thing if all the non-SB/PT/Logic people get on board. Then, some good people will just write wrappers for VST/AU/AAX and we'll be done with all this time-wasting foolishness.

Anyway, get back to work! I need a new Mac version by Christmas!

(Oh, and have a wonderful holiday season with your friends and family! We'll still be here after the New Year. )

[Karlatin]

One thing in VST3's favor is that it looks likes all the open source projects, like Surge and Dexed have gone VST3 only

But, SurgeXT (just next version of Surge) has started implementing CLAP already just about a day ago:

" Experimental non-working CLAP commit. (#5644)"

I've been thinking it over and I'd be just fine with the direction of MuLab if Jo skipped VST3 support and just supported VST2 and CLAP - I can think of very few plugins which, for now, don't also drop old VST2 versions. Just in my case, I understand there's a variety of user situations out there.

[syntonica]

One thing in VST3's favor is that it looks likes all the open source projects, like Surge and Dexed have gone VST3 only

But, SurgeXT (just next version of Surge) has started implementing CLAP already just about a day ago:

" Experimental non-working CLAP commit. (#5644)"

I've been thinking it over and I'd be just fine with the direction of MuLab if Jo skipped VST3 support and just supported VST2 and CLAP - I can think of very few plugins which, for now, don't also drop old VST2 versions. Just in my case, I understand there's a variety of user situations out there.

There are scads of new, desirable plugins that are VST3-only since the developers could not license VST2. For better or worse, SB is going to continue pounding the stake into VST2's heart and then nail the coffin shut.

I'm not sure why they keep doubling down on VST3 as it's quite apparent that nobody's using it unless forced to.

[MightyMouse]

vst2 will be gone sooner or later
every host should support vst3 asap

[pljones]

every host should support vst3 asap

Given limited developer time, are you saying that you'd rather drop support for other features in favour of this? Which other features and why would you make that choice?

[heks]

every host should support vst3 asap

Given limited developer time, are you saying that you'd rather drop support for other features in favour of this? Which other features and why would you make that choice?

I know the question wasn't asked of me, but imagine someone comparing DAW's and looking at features wouldn't they expect to find vst3 compatibility as standard ?

[sl23]

But, SurgeXT (just next version of Surge) has started implementing CLAP already just about a day ago:

What is CLAP? I tried to search for it, but I just get clap maker VST 's or similar.

[Karlatin]

But, SurgeXT (just next version of Surge) has started implementing CLAP already just about a day ago:

What is CLAP? I tried to search for it, but I just get clap maker VST 's or similar.

Good question, its new and not at all expected that many know of it. The biggest thread for it is on the u-he subforum:

viewtopic.php?f=31&t=574861

Bique is, btw, a Bitwig employee. Tone2 seems frustrated with VST3, too:

https://www.tone2.org/forum/index.php?topic=2890.0

so if Tone2, u-he and the Surge team were to get on board with the format, there is hope that worthy synths will be using it and that may justify DAWs like MuLab using it.

as a side note, for a while I'd been messing around with Zrythm DAW and it had sort of the opposite problem that MuLab has: it supported VST3 but not at all old VST formats. Correct me if I'm wrong, but one of the reasons people want VST3 supported is that, if a small software developer is just starting up, Steinberg I think won't license them for the VST2 format, therefore more and more VSTs will come out for VST3 or higher only.

[RichardSemper]

vst2 will be gone sooner or later
every host should support vst3 asap

Steinberg's attempt to kill off vst2 is abominable for a variety of reasons:
1. New plugin Devs are forced to use vst3, which I understand is a botched affair, bad for developers, and unfriendly to end users.
2. Existing DAWs (like mulab) pretty much forced to adopt vst3 or be incompatible with newer plugins.
3. SB attempted to terminate existing vst2 licenses for Devs adopting vst3 (which they might yet try again). This would mean DAW developers no longer being allowed to support vst2, killing off a lot of excellent existing vst2 plugins which may not be updated to vst3 for various reasons, including their devs no longer operating. Most unfriendly towards developers, end users and producers. vst2 plugins are far more ubiquitous than vst3 or any other format.
Steinberg must have their own (warped) reasons for doing this, but I don't see how it makes sense for anyone else!
If Vst3 format was any good at all it would sell on its own merit, and naturally supplant the earlier format. Folks would be eager to upgrade to the newer format, and there would be no need at all to try to suppress vst2. Unfortunately, to the end user, like so many so called 'upgrades' these days, it feels like more has been taken away than added.
I sincerely hope the CLAP initiative works out and supplants vst2 and vst3. Bottom line though is I want to be able to continue using my old vst2 plugins while still being able to play with the new stuff from both existing and new developers. I don't want to have to worry about format wars, or policies which exclude me from using either great new plugins or favourite older plugins.

[RichardSemper]

I have been using the m9 pre-beta to attempt a remake of one of my older tracks.
So far I am finding it very stable and usable. The clip launcher is a great addition, improving the workflow and it works great!
Despite using it for several hours each day, and trying many things I really have no issues to report so far, (other than perhaps the number of modules I needed to update from earlier projects to work in m9).
Great work Jo
Have a Great Christmas and a Happy New Year!

[heks]

vst2 will be gone sooner or later
every host should support vst3 asap

I sincerely hope the CLAP initiative works out and supplants vst2 and vst3. Bottom line though is I want to be able to continue using my old vst2 plugins while still being able to play with the new stuff from both existing and new developers. I don't want to have to worry about format wars, or policies which exclude me from using either great new plugins or favourite older plugins.

I completely agree,

[pljones]

Quick question triggered by a problem I saw in M8 -- can someone testing M9 check and report back if it's still an issue, please?
viewtopic.php?p=8301926#p8301926
In the movie in the post, you'll see the start/loop/end sample positions in MuSampla don't correctly display the values -- double-click opens the edit box and they're there but they disappear in the main UI. Hover text is okay, too.

[RichardSemper]

Quick question triggered by a problem I saw in M8 -- can someone testing M9 check and report back if it's still an issue, please?
viewtopic.php?p=8301926#p8301926
In the movie in the post, you'll see the start/loop/end sample positions in MuSampla don't correctly display the values -- double-click opens the edit box and they're there but they disappear in the main UI. Hover text is okay, too.

In m9 the behaviour is the same. The hover text shows the value, as does the edit box. The sample position display in the main ui shows a vertical line which denotes the position in the file rather than a numeric value. This line moves left or right according to the value chosen.