Vember Audio Surge is now open-source

[EvilDragon]

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

Nope, Windows here.

[Halonmusic]

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!

This!

[aMUSEd]

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.

Anyone using Bitwig I've uploaded a revised device panel mapping for the VST3 with each scene clearly differentiated

https://www.dropbox.com/s/xkxmf1pyfwzen ... 4.zip?dl=0

[EvilDragon]

32-bit won't be killed but VST2 is already removed from the Azure pipeline. Not even nightlies are getting VST2 now.

[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).

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.

Cool, that's interesting.

Either way, Surge 1.7 will have things as in my screenshot there, pull request that I made was merged into the master branch.

[Halonmusic]

Well if vst2 is really being removed for whatever reason i wont bother with Surge in the future.

[phazed]

@EvilDragon: ok, I'm on Mac, so it seems that Live on Windows will allow to use VST2 and VST3 at the same time.

Personally, I can live with the fact that Surge 1.7 will be VST3 only as long as I can use the 1.6.6 VST2 on my Mac simultaneously.

Otherwise I will have to stick with 1.6.6 or invest a lot of time to do a manual migration. Basically it would mean to locate each single instance of Surge in ongoing projects, the library (also clips etc.), old projects export it's settings using the patch browser, remove the plugin from the track, restart Live, insert the VST3 and reload the exported settings again.

[ENV1]

32-bit won't be killed but VST2 is already removed from the Azure pipeline. Not even nightlies are getting VST2 now.

Thats unfortunate.

Maybe it can be brought back then, because some hosts just dont support VST3.

I know i would appreciate it a lot, as would probably others who still use hosts that dont know VST3.

(Phrazor for instance has no idea what VST3 is, and im pretty sure EnergyXT hasnt either.)

[baconpaul]

@EvilDragon: ok, I'm on Mac, so it seems that Live on Windows will allow to use VST2 and VST3 at the same time.

Personally, I can live with the fact that Surge 1.7 will be VST3 only as long as I can use the 1.6.6 VST2 on my Mac simultaneously.

So I just installed 1.6.6 from the website installing only the VST2 and of course I have the 1.7 on my box as a VST3. In Reaper 6 macOS catalina I was able to load both. Reaper uses process isolation of course and I think Live doesn't, but it is very reasonable to ask that installing 1.7 VST3 doesn't break 1.6.6 VST2 so you can at least keep both on one machine and use either-or. We'll do our best to make sure we meet that constraint at release points and will keep the 1.6.6 VST2 installed on my box to test that.

https://github.com/surge-synthesizer/surge/issues/1904 is the issue to make sure we engineer accordingly.

[EvilDragon]

32-bit won't be killed but VST2 is already removed from the Azure pipeline. Not even nightlies are getting VST2 now.

Thats unfortunate.

Maybe it can be brought back then, because some hosts just dont support VST3.

I know i would appreciate it a lot, as would probably others who still use hosts that dont know VST3.

(Phrazor for instance has no idea what VST3 is, and im pretty sure EnergyXT hasnt either.)

It's unfortunate but it's a clean cut licensing-wise. VST3 is truly free and open source software, VST2 is not. The current Surge synth team would like to steer away from legal ambiguities and gray areas that VST2 is full of now after Steinberg did what they did to VST2.

I can periodically build VST2, but only 64-bit and only Windows. I won't do it for nightlies, only official releases. Any other active developer that holds a VST2 SDK license is free to build from the current Surge repository and distribute them. The current Surge synth team does not want to spend their available time and energy into supporting VST2, when VST3 actually works better (especially regarding GUI scalability across various hosts, etc.).

[Kott]

Hi,
I thought that we can use alternatives for vst2 https://github.com/sadko4u/lsp-plugins/ ... /steinberg https://github.com/osxmidi/LinVst/blob/master/vestige.h https://git.iem.at/zmoelnig/FST
But as I can see Surge vst2 part uses headers from public.sdk/source/vst2.x/ which be not fully reimplemented. Is it?

[Halonmusic]

32-bit won't be killed but VST2 is already removed from the Azure pipeline. Not even nightlies are getting VST2 now.

Thats unfortunate.

Maybe it can be brought back then, because some hosts just dont support VST3.

I know i would appreciate it a lot, as would probably others who still use hosts that dont know VST3.

(Phrazor for instance has no idea what VST3 is, and im pretty sure EnergyXT hasnt either.)

Energyxt dosent support vst3

[EvilDragon]

IIRC Surge VST2 doesn't even work in eXT as is (UI doesn't show). The issue regarding this was closed and never fixed, if you want to read:

https://github.com/surge-synthesizer/surge/issues/190

[EvilDragon]

Hi,
I thought that we can use alternatives for vst2 https://github.com/sadko4u/lsp-plugins/ ... /steinberg https://github.com/osxmidi/LinVst/blob/master/vestige.h https://git.iem.at/zmoelnig/FST
But as I can see Surge vst2 part uses headers from public.sdk/source/vst2.x/ which be not fully reimplemented. Is it?

Yeah I don't think that'll work.

[Halonmusic]

Yes i know about the issue about the gui problem of the vst2 version. Why that never got fixed is beyond me. Maybe it'll work in IL Minihost Modular or Element though.