Vember Audio Surge is now open-source

[audiot]

Like EvilDragon said, if you have any questions, feel free to join the Discord server

Thanks Nerdy Music Guy! I always wanted to check out Discord. Finally i'll have the chance to see what all these cool Minecraft kids are talking about If i dont like it, i'll see you at git.

[crickey13]

However the main trait of Surge - to have everything important on one page - is still paramount.

Thank you for that, it's one of Surge's strongest points. I've never found the GUI to be confusing, I actually think it's unusually intuitive.

[EvilDragon]

Indeed. My pet-peeves with status quo of Surge's UI are mostly concerning the layout of sections. For example, filter keytracks have nothing to do in their own frame, they should be in F1/F2 sections. Then, highpass right next to keytracks, when it's applied at the very END of the signal chain? It should be in the Amp section. Stuff like that.

[The Nerdy Music Guy]

Some more Surge craziness:
https://soundcloud.com/user-589036812-2 ... -1-x-surge

[The Nerdy Music Guy]

Some more crazy stuff. This is just one held note with some macro automation. It goes quite crazy towards the end:
https://soundcloud.com/user-589036812-2 ... -1-x-surge

[EvilDragon]

Alrighty people!

Today we're officially starting the beta cycle for Surge version 1.8!

More information: https://surge-synthesizer.github.io/beta18

Everyone is welcome to try the beta out and of course, any bugs you might stumble upon, let us know either here or (preferably) on GitHub. We are now in feature freeze phase, so only bug reports will be taken under consideration.


Thank you!

[subterfuge]

Thanks for the new beta.

When opening the beta 1.8 version and changing the skin to Surge Dark,I get two nag screens;
"Defaults not saved.
Unable to load defaults file c:\Program Files\Common Files\VST3\Surge Synth Team\SurgeUserData/SurgeUserDefaults.xml."

Checking into that folder, there is indeed no such file in there. So apparently the install doesn't set any basic user default file in there, and the portable zip doesn't have one either. Problem with this in this specific case is that the dark skin does load, but whenever I close and re-open the Surge GUI, it's back to the classic skin.

-----
update:
After uninstalling Surge and deleting everything related in Common Files/VST3/SurgeSynthTeam folder, a fresh install of beta 1.8 got this back to normal. Good news is that I didn't lose two days worth of earlier preset level adjustments and few custom presets either.

[baconpaul]

Did you install from the full installer or the portable zip?

We certainly shouldn't create SurgeUserData by default. If we do that's a bug because it is created somewhere non-writable (which is what you saw). The InnoSetup installer doesn't seem to. ahh but I see now that the portable zip does.

So I should stop the portable zip from having that file by default. Then it will use %DOcuments%

Thanks!

[baconpaul]

OK I modified the pipelines so that the dev zip doesn't include the portable UserSettings and also took the zip off the download page until we can document the gotchas of using a portable install with user documents. The installer does the right thing.

And yeah we never delete user settings. What happened was Surge detected that as your user area and assumed you had set up properly (but how would you know that - we have no documentation for the zip). The standard installer makes the factory junction but not the user area so is fine.

Thanks!

[subterfuge]

OK I modified the pipelines so that the dev zip doesn't include the portable UserSettings and also took the zip off the download page until we can document the gotchas of using a portable install with user documents. The installer does the right thing.

You got it. I had an earlier regular install already and in a bold move, decided to simply drop the new beta portable files on top of that, updating all the old files. That's where things went sideways. After uninstall and a new regular install things went back to normal.

Yes, I tried to look for readmes about the portable package, but couldn't find any, so good idea to document all that. Thanks, and now back to usual...

[Markin]

Thanks to everyone who has helped keep this project alive.
I only just got around to trying Surge and imo it sounds very cool.
Many years have passed and many new Synths have arrived all promising to be better and offering more features than the last when in reality there has been a trend of decline in new ideas and features with the emphasis on clever marketing and better interfaces.

Can't say I really like the quirky interface of Surge but that is only because I have become seduced with modern Gui's.
In the sound department Surge can easily hold its own against many modern day Synths and in many real world cases easily surpass them.
The extra's that have been coded since are appreciated.

[baconpaul]

... decided to simply drop the new beta portable files on top of that, updating all the old files. That's where things went sideways...

that *would* have worked if I hadn't made a UserSettings empty dir in the zip. And if we had documented it at all. And so on. Sorry bout that! Thanks for your patience, glad it is working, and look forward to hearing how you enjoy 18!

[Andywanders]

This is indeed a fine synth

However, I can't set up LFO to Pitch modulation via Mod Wheel, so that the Mod Wheel controls the amount of modulation. I have looked in the manual but there are no answers there.

Does anyone have a clue

[The Nerdy Music Guy]

This is indeed a fine synth

However, I can't set up LFO to Pitch modulation via Mod Wheel, so that the Mod Wheel controls the amount of modulation. I have looked in the manual but there are no answers there.

Does anyone have a clue

Assign the LFO to the pitch and then assign the modwheel to the amplitude of the LFO

[Andywanders]

Assign the LFO to the pitch and then assign the modwheel to the amplitude of the LFO

Thank you sir