Vember Audio Surge is now open-source

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS
Surge XT The Sonic Transformation

Post

Given the page specifically discusses using Surge as an effect, I don't think it refers to the VST2 zoom problem. Fortunately VST3 takes care of that complaint.

Post

Haven't tried Surge yet as an effect.

But as an instrument, the VST2 zoom actually works in Cakewalk by BandLab with a workaround. But as you said, not really necessary since the VST3 works without issues that I can tell.

The workaround for VST2 is to go down to the bottom of the zoom menu, and manually "Set default zoom to...". Then re-insert the synth. It will remember the new default zoom level. The other zoom level settings still do not work correctly when scaling the DAW plugin window in the VST2.
Windows 10 and too many plugins

Post

Has anyone successfully used polyphonic aftertouch as a modulation source? I've tried this with a Launchpad Pro, Ableton 10.1 on Mac without any success. Channel aftertouch works flawlessly.

Post

I'm wondering if it's just Live filtering out the messages. Unfortunately I don't have any other VST that supports poly AT to countercheck.

Post

Live doesn't support Poly AT and it filters it out, yes.

Post

I think it's so great how Surge is developing here. In contrast to native instruments that are not willing to support their own wavetables. What has become of Surge is so fantastic that no one needs MassiveX. There is even a wavetable editor for surge. Does not cost anything.

Post

Massive X of course sounds entirely different than Surge. Better filters, better FX, better routing possibilities, and nobody ever said that it won't get user wavetables :P

Saying that "nobody needs MX" is a subjective generalization that is entirely incorrect :)

Post

baconpaul wrote: Mon May 04, 2020 1:50 am And the changelog shows what’s already new in the nightly (and one of us updates it every 2 weeks or so as we march towards a release)

https://surge-synthesizer.github.io/changelog/

The nightlies right now are a wee bit rocky in a couple of spots, but are starting to get some of the new features intact. Always happy to have feedback on features and previews!
Has the parameter names of VST2 been updated to distinct the A-B scene?

Post

kinwie wrote: Sat May 16, 2020 7:26 am
baconpaul wrote: Mon May 04, 2020 1:50 am And the changelog shows what’s already new in the nightly (and one of us updates it every 2 weeks or so as we march towards a release)

https://surge-synthesizer.github.io/changelog/

The nightlies right now are a wee bit rocky in a couple of spots, but are starting to get some of the new features intact. Always happy to have feedback on features and previews!
Has the parameter names of VST2 been updated to distinct the A-B scene?
VST3 also has that problem.

Post

Mac installer still complains that it's an unidentified developer so I have to go into security to allow it

Post

So is it fair to say the VST3 is the version to use now where possible, more stable, less bugs?

If so I'll update my Bitwig device panel for the VST3 instead.

Post

Yes, VST3 is recommended to use, VST2 will likely not going to be provided as a download from version 1.7 onwards.


Automation parameters are still not updated to discern between scene A/B. Will happen in 1.7 I think.

Post

EvilDragon wrote: Sat May 16, 2020 5:32 pm Yes, VST3 is recommended to use, VST2 will likely not going to be provided as a download from version 1.7 onwards.


Automation parameters are still not updated to discern between scene A/B. Will happen in 1.7 I think.
Pleasee...make it happen before the vst2 deprecated

Post

Not my call!

Post

@baconpaul
:help: :help: :hail: :hail:

Post Reply

Return to “Instruments”