Vember Audio Surge is now open-source

[aMUSEd]

Doesn't help that the company name has been changed to VmbA - it means if I save as AUpreset patches get saved to the wrong location now.

can you tell us more about this?
how did Surge1.5 save them, and where? what did Surge1.5 say?

'Vember Audio'

And (as I have pointed out several times) the default preset location on Mac for Factory presets was:

/Library/Application Support/Vember Audio/SURGE

It's become a bit confused now as I seem to have 3 different locations for presets.

[esaruoho]

Doesn't help that the company name has been changed to VmbA - it means if I save as AUpreset patches get saved to the wrong location now.

can you tell us more about this?
how did Surge1.5 save them, and where? what did Surge1.5 say?

'Vember Audio'

And (as I have pointed out several times) the default preset location on Mac for Factory presets was:

/Library/Application Support/Vember Audio/SURGE

It's become a bit confused now as I seem to have 3 different locations for presets.

/Library or ~/Library

[aMUSEd]

For Factory it's /Library (you can confirm using the 1.5 installer, it literally asks you to drag and drop the presets and wavetables into that location). For user I'm less clear as there's a folder in mine called 'patches_user' but I notice when I save patches they are going in ~Documents/Surge so that's also confusing.

[esaruoho]

For Factory it's /Library (you can confirm using the 1.5 installer, it literally asks you to drag and drop the presets and wavetables into that location). For user I'm less clear as there's a folder in mine called 'patches_user' but I notice when I save patches they are going in ~Documents/Surge so that's also confusing.

yeah.. i get it. not a big fan of some stuff being on ~/Library and some at /Library and then some other stuff being in ~/Documents - too confusing.
i'll try and write a ticket about it https://github.com/kurasu/surge/issues/192

[PietW.]

In version 1.7 my own wavetables do not appear. Everything works in version 1.5.

hi PietW., I've identified the issue: the current (2nd January 2019) build of Surge does not accept wavetables with the file-extension .WT or .Wt - if you rename the wavetables to .wt they will work fine.

This seems like a minor thing to fix for a future build, however, so I've logged a ticket for it at
https://github.com/kurasu/surge/issues/191

Also, have posted screenshots of what it looks like on macOS AU, Renoise3.1.1 VST2, Live10 VST2, Live10 AU - so this should help figuring it out.

Do you have a lot of wavetables out there? Does anyone have an archive? Would be cool to test them out further.

Hi,
it works perfectly. The current version of Surge recognizes my wavetables. Thank you very much for this information.
I have thousands of wavetables for serum, icarus ... They can be easily converted into the format for Surge with Audioterm.

[aMUSEd]

There is something odd going on with host automation assignments for Scene B. If I try and 'learn' params from the filters in scene B in Bitwig for example (in order to create a device panel map), by clicking learn then selecting the filter cutoff, res etc, what gets learnt is LFO params, not filter params. The only way to map filter params (or any params from Scene B) is via the drop-down selector but that is an endless list and very disorganised.

[esaruoho]

There is something odd going on with host automation assignments for Scene B. If I try and 'learn' params from the filters in scene B in Bitwig for example (in order to create a device panel map), by clicking learn then selecting the filter cutoff, res etc, what gets learnt is LFO params, not filter params. The only way to map filter params (or any params from Scene B) is via the drop-down selector but that is an endless list and very disorganised.

any chance you could fill in this data to https://github.com/kurasu/surge/issues/193
we're missing at least which operating system, and which version you're running, and which plugin (vst2,vst3,audiounit) and all kinds of other info. please help.

[aMUSEd]

MacOs Sierra, VST2, Bitwig 2.4

[esaruoho]

I'll get back on the Linux build asap. We're just settling into a new place, after another few days I can start looking into resolving the load error. Yes, I've already built it for Linux but it won't load into any DAW here (Ardour, Bitwig, Qtractor). I may already have a clue to the resolution, if I'm right it should be a simple fix. Wish me luck.

Hi StudioDave, the discussion at https://github.com/kurasu/surge/issues/19 about Linux building might be of interest to you!

[esaruoho]

Is there someone working on the Windows build? It works perfectly fine (the building process) on VS2017 Community, Windows 10 x64, VST3 x64.

hi Jorgeelalto - the automated builds of 64bit VST2/VST3 seem to be at the kzantow url. but what's really missing is the linux stuff.

[esaruoho]

and some help with the 32bit building.

[Jorgeelalto]

Is there someone working on the Windows build? It works perfectly fine (the building process) on VS2017 Community, Windows 10 x64, VST3 x64.

hi Jorgeelalto - the automated builds of 64bit VST2/VST3 seem to be at the kzantow url. but what's really missing is the linux stuff.

Yep, checked them a few days ago - works perfectly, thanks a lot!

[esaruoho]

works perfectly, thanks a lot!

nice to hear! There's still talk going on about trying to get 32-bit builds for Windows + macOS going on, they're at

https://github.com/kurasu/surge/issues/115

p.s. if anyone reading this thread feels like jumping in and assisting with either bugreports or helping with the builds etc, here's a slack invitation link

https://join.slack.com/t/surgesynth/sha ... mNhYzQ3NTU

[esaruoho]

There is something odd going on with host automation assignments for Scene B. If I try and 'learn' params from the filters in scene B in Bitwig for example (in order to create a device panel map), by clicking learn then selecting the filter cutoff, res etc, what gets learnt is LFO params, not filter params. The only way to map filter params (or any params from Scene B) is via the drop-down selector but that is an endless list and very disorganised.

this is being looked at currently.
EDIT:
fix is in, but not yet baked to the automated kzantow builds.

[esaruoho]

Cool! I can't find any binaries but it's stated there are available at GitHub.

Edit: Woops https://github.com/kurasu/surge/releases

even newer and more up-to-date builds at https://kzantow.github.io/surge/ (11th January 2019 right now)
enjoy!
and don't forget to log bugs in or describe them on the forum here if you come across any issues!