'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.
'Vember Audio'
/Library or ~/LibraryaMUSEd wrote: ↑Wed Jan 02, 2019 9:47 am'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.
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.aMUSEd wrote: ↑Wed Jan 02, 2019 10:17 am 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.
Hi,esaruoho wrote: ↑Wed Jan 02, 2019 7:18 amhi 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.
any chance you could fill in this data to https://github.com/kurasu/surge/issues/193aMUSEd wrote: ↑Thu Jan 03, 2019 12:07 am 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.
Hi StudioDave, the discussion at https://github.com/kurasu/surge/issues/19 about Linux building might be of interest to you!StudioDave wrote: ↑Fri Dec 14, 2018 3:54 pm 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 Jorgeelalto - the automated builds of 64bit VST2/VST3 seem to be at the kzantow url. but what's really missing is the linux stuff.Jorgeelalto wrote: ↑Fri Dec 21, 2018 1:16 pm Is there someone working on the Windows build? It works perfectly fine (the building process) on VS2017 Community, Windows 10 x64, VST3 x64.
Yep, checked them a few days ago - works perfectly, thanks a lot!esaruoho wrote: ↑Thu Jan 03, 2019 1:12 pmhi Jorgeelalto - the automated builds of 64bit VST2/VST3 seem to be at the kzantow url. but what's really missing is the linux stuff.Jorgeelalto wrote: ↑Fri Dec 21, 2018 1:16 pm Is there someone working on the Windows build? It works perfectly fine (the building process) on VS2017 Community, Windows 10 x64, VST3 x64.
nice to hear! There's still talk going on about trying to get 32-bit builds for Windows + macOS going on, they're at
this is being looked at currently.aMUSEd wrote: ↑Thu Jan 03, 2019 12:07 am 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.
even newer and more up-to-date builds at https://kzantow.github.io/surge/ (11th January 2019 right now)discoDSP wrote: ↑Tue Sep 25, 2018 9:10 am Cool! I can't find any binaries but it's stated there are available at GitHub.
Edit: Woops https://github.com/kurasu/surge/releases
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement