Vember Audio Surge is now open-source

[gentleclockdivider]

So no vst 2 support , but only vst 3 ( even for 32 bit ) ?
Imho I think there are a lot more users running vst 2 in a 64 bit environment , then vst 3 in a 32 bit environment
What I am missing ?

[EvilDragon]

This was explained a few times already in the thread, please look back a few pages. VST2 is still in the codebase and you can build it yourself if you have properly licensed VST2 SDK.

[baconpaul]

By steinberg’s choice to discontinue VST2 (which is totally within their rights), VST2 is not a format where software developers can obtain a license, nor is it a format which is compatible with GPL3. https://surge-synthesizer.github.io/formats

If you are a valid VST2 licensee you can still build the VST2 yourself.

[Guenon]

So, a little trip report on the libxcb-util1 thing and Debian Buster: building Surge on your chosen system, using the included build script, is indeed extremely streamlined and straightfoward like baconpaul noted. Thumbs up for that. The synth functions in a libxcb-util0 equipped environment without any issues. To be sure, I'd recommend this way of installing over any hacky package juggling, on vanilla Debian and related distros.

That being said, I did roll a test box for the latter approach as well ... I noticed there's a certain Steven Pusser who has kindly ported libxcb-util1 for Debian 9 (Stretch) based systems (you can google more on this if so inclined, packages here https://software.opensuse.org//download ... bxcb-util1 ), and rather adventurously I went and installed that single package... yes, on Buster. To be completely sure, this sort of thing is not encouraged, and as a general approach, mixing and matching in this manner is a Bad Idea and will break stuff.

In any case, giving this test system a spin on a wide variety of production software, I didn't encounter any indications of problems at this time, and juggling stuff like this is a potential quick way out when you're really really needing to run something -- as long as you know what you are doing and have reasonably covered your back, for example having an MX Linux style Snapshot of your box with your juggle installed and without it, for quick and convenient rollback.

(Having the actual util1 package around, on an otherwise compatible system, also allows you to run the fresh Kawai K1 emulation Linux VST, for example, which also wants to install on a libxcb-util1 equipped system by default, and so on.)

[Tj Shredder]

I'm getting a warning about the default skin not being installed, although it looks fine to me. I tried to rescan for skins from the menu but I get even more warnings. Plus, I don't see a dark skin installed.

I installed the AU. Should I also install the VST to get the skins working properly?

Screenshot 2020-07-28 at 22.03.56.png

This means your application support/surge data is incorrect. Can you attach a screenshot of "help/about"? And when you ran the installer, did it successfully install /Library/Application Support/Surge and does that directory contain skins?

I should improve that error message too.

Here's the About panel. I've found skins, including the dark skin, installed at /Library/Application Support/Surge.


about.png


Screenshot 2020-07-28 at 23.47.20.png

You seem to have a local copy of the application settings which will indeed blow you up. Remove or rename the directory “/Users/(redacted)/Library/Application Support/Surge” in preference of the one in /Library and it should all work.

Thanks. I trashed it and that's fixed it.

I got the same message, and looked at those two places. Its a bit confusing, as it seems the files in my local library had been installed with the last installer, and those in the global library are the older ones (mainly from 2019). I moved the new ones to the global library and Surge seems happy.
But I interpret this as a bug in the installer, it seems to copy its content to the local library, but the plugin looks for its resources in the global library...

[baconpaul]

@TJ Shredder - I'm super surprised the installer did a local install. https://github.com/surge-synthesizer/su ... ostinstall that's the post install script and it copies to /Library. So not sure how you would have gotten new in the ~/Library. Also, the plugin looks in local first, so if it broke, that means local was wrong not global? I think older installers might have installed locally, and definitely the build scripts install locally when you are doing dev.

But in any case, in the upcoming 1.7.1 release the synth checks for which set of assets is newest and uses those by default if it finds both. This should resolve the various states of peoples machine issues which have popped up here and there. My guess is we do a 1.7.1 point release this weekend. The current nightly has that behavior.

Thanks!

[monkeygenius]

I think it would be cool if LinPlug could be convinced to make (at least some of) their plugins open source too. I've really like Alpha for instance, and it's a shame that it's not possible to get it any more.

Absolutely, but somehow I don't think that'll happen. I still use Spectral and Albino 3...

Yes, that could of course be the case. I don't know enough about LinPlug to say whether they would be interested to release anything as open source, but I mentioned them because they seem to have completely shut down business so it struck me that they might be a more realistic option than some other developers.

[ENV1]

Found some strangeness with the step sequencer.

It sorta mirrors the previous steps after loop end.

Version 1.5.2 does not do that.

See GIF for details.

I assume this is not intentional so i thought id report it...

SurgeSeq1.gif

[grandmasterbird]

I can't believe this synth is freely downloadable, it's amazing! I'm obviously very late to the party but thank you to the team who put the work in to keep it going. Anywhere to make a donation?

[baconpaul]

Found some strangeness with the step sequencer.

It sorta mirrors the previous steps after loop end.

Version 1.5.2 does not do that.

See GIF for details.

I assume this is not intentional so i thought id report it...


SurgeSeq1.gif

That’s actually intentional. And 1.5.2 does do that just the display doesn’t show it. With 1.7.0 we added the white line which shows what the SS will actually output. (Play with deform and you’ll see it). So when you have set end points the wave will loop across the time span rendered on the screen.

Since 1.5.2 (and 1.6.* for that matter) just showed the steps but not the output (Try deform on those and you will see no change) you couldn’t visualize the actually display.

[baconpaul]

I can't believe this synth is freely downloadable, it's amazing! I'm obviously very late to the party but thank you to the team who put the work in to keep it going. Anywhere to make a donation?

Thanks! We don’t take donations. Happy you enjoy the synth!

[Tricky-Loops]

If similar development would be possible with Atlantis by Jeremy Evers, it could be one of the greatest free synths (and filter units). But fiddling around with these tiny envelopes is tedious...

Anyway, a big thanks for the big update of Surge!

[Halonmusic]

I dont think Atlantis is open source though?

[arkmabat]

no, but it has an x64 version now... wow https://jeremyevers.com/atlantis/

[ENV1]

That’s actually intentional. And 1.5.2 does do that just the display doesn’t show it. With 1.7.0 we added the white line which shows what the SS will actually output.

I think i understand.

Its to visualize how the steps are enveloped by the EG.

What made me wonder was the fact that the (active) steps on the left got mirrored on the right (inactive) side, but i think i get the idea now.

Thank you.