Vember Audio Surge is now open-source

[EvilDragon]

He's the one who wants to not support VST2 in the first place


Anyways with a bit of tweaking I managed to get the scene A/B into parameter names for host automation:

[Halonmusic]

So you are ditching vst2? Stupid move.

[kinwie]

He's the one who wants to not support VST2 in the first place


Anyways with a bit of tweaking I managed to get the scene A/B into parameter names for host automation:

That's it should be , make it your call ED

[Jorgeelalto]

So you are ditching vst2? Stupid move.

Taking into account Steinberg does not support VST2 any longer and doesn't give VST2 licenses, most of us are not even able legally to compile a VST2 plugin, so it makes sense to go VST3. There are still some DAWs that are still behind on VST3 support, but it has to come sooner or later. New plugin developers that couldn't get a VST2 license can't distribute VST2 plugins, so...

[EvilDragon]

By all means, if there's a plugin developer that is a legitimate owner of VST2 SDK, (s)he will be able to build and distribute Surge VST2.

VST2 code itself in the codebase is not going anywhere, though.

[EvilDragon]

make it your call ED

I can't, baconpaul is the one who calls the shots. All I can do is make a pull request, and if anyone wants this in VST2, needs to build it for themselves (of course, gotta be a legitimate licensee of VST2 SDK).

[kinwie]

[Halonmusic]

So you are ditching vst2? Stupid move.

Taking into account Steinberg does not support VST2 any longer and doesn't give VST2 licenses, most of us are not even able legally to compile a VST2 plugin, so it makes sense to go VST3. There are still some DAWs that are still behind on VST3 support, but it has to come sooner or later. New plugin developers that couldn't get a VST2 license can't distribute VST2 plugins, so...

They dont support vst2 anymore? Oh in that case i apologize.

[AJYoung]

They dont support vst2 anymore? Oh in that case i apologize.

Yup. They technically haven't supported or maintained it since 2013, but they officially killed it off October 2018, when they decided to stop including it as part of the VST3 SDK.

If you didn't have a license for the VST2 SDK before then, you're out of luck.

[Halonmusic]

They dont support vst2 anymore? Oh in that case i apologize.

Yup. They technically haven't supported or maintained it since 2013, but they officially killed it off October 2018, when they decided to stop including it as part of the VST3 SDK.

If you didn't have a license for the VST2 SDK before then, you're out of luck.

I see thanks.

[phazed]

My biggest problem: how do I migrate my projects from VST2 to VST3 without too much pain? I have a good amount of Ableton projects that I'm either still working on or using parts out of it. Since Ableton was very late in supporting VST3, most of my stuff is still using VST2.

It's also not possible to use the VST2 and VST3 version of Surge inside a project (BTW: this works with other plugins from u-he or TAL). That would make a track-by-track migration much easier. Once you instance the VST3 version of Surge, Ableton will refuse to load the VST2 version until you restart the DAW. Vice versa for VST2.

[EvilDragon]

You can continue using VST2 in your current projects for sure, there's no real need to change them to VST3. Current version of VST2 will continue to work.

Live is quite weird in this regard that it doesn't seem to allow VST2 and VST3 of Surge at the same time. There's this issue in Surge github, but no takers on it just yet. I wonder if something on Surge side of things prevents this, it definitely warrants an investigation.


EDIT: I just tried it on my side in Live 10... VST3 loads side by side with VST2 in the same project over here? Not on the same track, of course, but on different tracks, entirely works!

[phazed]

@EvilDragon: are you on Mac? I tried this last week with the latest version of Live without success.

As far as I understand it, the VST2 version will be removed completely from Surge 1.7, and there is no way to keep it from 1.6.6 in parallel with VST3 from 1.7.

[ENV1]

make it your call ED

I can't, baconpaul is the one who calls the shots. All I can do is make a pull request, and if anyone wants this in VST2, needs to build it for themselves (of course, gotta be a legitimate licensee of VST2 SDK).

Thats not correct. You could always use a VSTXML, which allows you to alias the original parameter names as you see fit. Granted it will require some work if the plugin in question has a lot of parameters, (and Surge does have relatively many), but the good thing is that the plugin itself doesnt have to be altered one bit, i.e. no matter what the original parameter names are you can change them to whatever you prefer without the plugin itself requiring any changes at all.

Its always an option where a plugin has suboptimal parameter naming.

[ENV1]

Oh and please dont kill VST2 and/or 32bit.

There are those of us who need those so it would be a shame if we could no longer use the newer builds.

Thank You!