Vember Audio Surge is now open-source

[baconpaul]

Hello,

I'm very interested in adapting wavetables for Surge using existing media - started to do this a couple of months ago; but It's a little tedious because the wt info is somewhat cryptic - I'd love to get some clarity.

https://github.com/kurasu/surge/blob/ma ... format.txt

tells you how the flags are used.

the integers are just 2 byte little endian shorts followed by 4 byte little endian size. Line 486 of SurgeStorage shows you where they are read.

[PietW.]

Some (90) wavetables for Surge ( Version from 12.01.2019) Created with Audioterm.

https://www.dropbox.com/s/2sue91au4jxc8 ... 01.7z?dl=0

[Spitfire31]

Thank you Piet! Looking forward to trying them out!

/Joachim

[esaruoho]

Well for a start you bundle Zoozither 1 and 3 so I guess there's a Zoozither 2 out there somewhere but the link in this thread seems dead
viewtopic.php?t=160913
There are some in the KvR database
viewtopic.php?t=160913

hi, just got permission from inigokennedy to bundle inigo_kennedy_03 -pack (another one that went missing) into the pack. that's 31 presets added. thanks. will try to hunt down ZooZither. also found that at least one guy is selling a bunch of Surge presets. will keep yanking at this thread.



so far:
patches:
The ' ReAction ' Soundset by CHE for the Vember Audio - Surge VSTi
http://patcharena.com/downloads/comment.php?dlid=1116
https://rekkerd.org/patches/plug-in/surge/
http://patcharena.com/tag/presets-for-surge/

wavetables:
http://patcharena.com/downloads/comment.php?dlid=1332 - from Arty

[goldenanalog]

[planetearth]

Version 1.6 seems to have fixed the installer routine problems, but the "Sin sequencer 2" patch (in the "Sequence" category) starts to play immediately when it's called up, even if you don't hit a key. And you can't stop it by hitting the "MIDI panic" button in the DAW or having the DAW stop and restart the audio engine.

Also, "Sync acident" [sic] is misspelled in the same category.

Windows 7/x64/Sonar/Surge 1.6/VST2

Steve

[Spitfire31]

… the "Sin sequencer 2" patch (in the "Sequence" category) starts to play immediately when it's called up, even if you don't hit a key. And you can't stop it by hitting the "MIDI panic" button in the DAW or having the DAW stop and restart the audio engine. …
Windows 7/x64/Sonar/Surge 1.6/VST2

Steve

Confirmed on Mac OS 10.12.6, Live 10.0.5, Surge 1.6, Jan 12 build. But I can stop it by just selecting the next or previous patch with the +/– buttons.

/Joachim

[planetearth]

… the "Sin sequencer 2" patch (in the "Sequence" category) starts to play immediately when it's called up, even if you don't hit a key. And you can't stop it by hitting the "MIDI panic" button in the DAW or having the DAW stop and restart the audio engine. …
Windows 7/x64/Sonar/Surge 1.6/VST2

Steve

Confirmed on Mac OS 10.12.6, Live 10.0.5, Surge 1.6, Jan 12 build. But I can stop it by just selecting the next or previous patch with the +/– buttons.

/Joachim

Yes, that works on the Windows side too, but you can't actually stop it to edit the patch or tweak it or play what you want. I thought it had something with the RETRIGGER button being enabled, but I found other patches with that enabled that don't have the same problem.

I also noticed some patches default to SCENE B when you pull them up, where most patches default to SCENE A. I'm not sure if they're all supposed to default to SCENE A, with SCENE B being an "alternate" version of the patch.

Steve

[esaruoho]

Version 1.6 seems to have fixed the installer routine problems, but the "Sin sequencer 2" patch (in the "Sequence" category) starts to play immediately when it's called up, even if you don't hit a key.
Also, "Sync acident" [sic] is misspelled in the same category.

Any preset that is saved with Latch on, will automatically start playing. in fact, almost all my presets are made with Latch on, so i can just load a drone-preset or a FM-drum-percussion-spewforth-preset that just starts spitting out sound.

That's why the Sin Sequencer2 will start playing. just set Latch to Poly or Mono.

i get that the behaviour could feel "a bit" disconcerting if it just starts outputting sound at full blast all of a sudden.

about typos, though, i feel like that if it was renamed to "Sync accident", then any track that uses "Sync acident" would not load the preset because it's not there. therefore preset names, even if they might have typos or broken english, would best stay called what they were called by the artists

[esaruoho]

Yes, that works on the Windows side too, but you can't actually stop it to edit the patch or tweak it or play what you want. I thought it had something with the RETRIGGER button being enabled, but I found other patches with that enabled that don't have the same problem.

The reason the patches play is because they've been saved with the setting Latch.. if you switch that to mono, poly or anything else, the "endless sound" will stop.

now, if Surge 1.5 from years ago, had Latch set up so that

"if Latch is ON, don't start playback until the user inputs note"

then we have a bug

but not sure who to ask about Latch functionality.

[Tj Shredder]

Does anybody know why some presets are pretty out of tune? Flute 2 from wind category is not playing clean octaves (about a quarternote sharp)...
Testing the latest Mac build esaruoho sent me...

[esaruoho]

Testing the latest Mac build esaruoho sent me...

p.s. the same build is available on the #macpackages channel on the SurgeSynth Slack.

(link to invite to slack
https://join.slack.com/t/surgesynth/sha ... mNhYzQ3NTU
)

[layzer]

Some (90) wavetables for Surge ( Version from 12.01.2019) Created with Audioterm.

https://www.dropbox.com/s/2sue91au4jxc8 ... 01.7z?dl=0

nice one!

thank you!

[gazzz]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

hi, i was find some bug (win7 64bit, Reaper 5.967 64 bit, Surge 8/01/2019 64 bit)

Reaper incorrect show (and use) last touched controller (for automatisation and modulation),
when I click button "param". Anybody have same isue?

this is similar to the aMUSEd error, and an error i have been having when binding parameters into DAW from Surge, where twiddling a knob in Surge will result in two automation knob binds in DAW. it is being looked at currently.

in case you or aMUSEd wanna look at the conversation, check this ticket out:
https://github.com/kurasu/surge/issues/247 (https://github.com/kurasu/surge/issues/247)

is this fixed ? in release 12/01/2019 this bug still exist (in Reaper)

[esaruoho]

is this fixed ? in release 12/01/2019 this bug still exist (in Reaper)

Hi, it has been fixed, **EDIT** check the signature. If you are looking for a 64-bit macOS AU/VST2/VST3, please join the Slack and check the channel #macpackages. Otherwise, we'll have to wait for Kzantow to update the site with the newest builds.

Once it reads newer than "12th January 2019" - the fix will be in for windows builds, too.

There's a lot of work going on to make the builds be part of the github repository, and not on a separate URL, and for them to be daily, but that work is not finished yet.