Vember Audio Surge is now open-source

[Echoes in the Attic]

I'm using Surge VST3 in Bitwig (Windows 10) and finding that the GUI zoom level is not maintained when I open the plugin again. Even when I save it as default preset after changing the zoom level. Is this a know issue?

Are you using the Menu option "Set default zoom to..."? If not, try that. It seems to work where other zoom options fail.

You won't see the zoom level change when you enter the value; you'll have to close Surge and re-open it before you see a change. But this has worked for me where the other zoom options had problems.

Steve

Crap. I was hoping nobody answered yet so that I could come and edit my post! I just found the default zoom settings. I must have been blind for not seeing it before. All good here now...

[planetearth]

I'm using Surge VST3 in Bitwig (Windows 10) and finding that the GUI zoom level is not maintained when I open the plugin again. Even when I save it as default preset after changing the zoom level. Is this a know issue?

Are you using the Menu option "Set default zoom to..."? If not, try that. It seems to work where other zoom options fail.

You won't see the zoom level change when you enter the value; you'll have to close Surge and re-open it before you see a change. But this has worked for me where the other zoom options had problems.

Steve

Crap. I was hoping nobody answered yet so that I could come and edit my post! I just found the default zoom settings. I must have been blind for not seeing it before. All good here now...

I waited as long as I could to post that, too.

Steve

[baconpaul]

You won't see the zoom level change when you enter the value; you'll have to close Surge and re-open it before you see a change. But this has worked for me where the other zoom options had problems.

we also fixed this in the nightlies so the 1.7 (which we hope will ship this summer sometime) will resize to the default you want when you reset the default!

[onerob]

I hope future versions of Surge can implement more stereo features, e.g. osc pan, unison stereo spread and perhaps even filter pan? I did look at the Github issues page and see that hopefully there will be some work on this for 1.7.

[EvilDragon]

At some point that'll likely happen (if you will see those stereo and unison tickets, they are marked as "currently unscheduled"), but 1.7 has different priorities: new reverb effect, flanger, beginnings of a skin engine (dark skin is WIP), slightly more interactive UI (hover effects over buttons and sliders), moving the build process to cmake instead of premake...

[onerob]

OK, thanks.

[AJYoung]

You can have stereo unison using the "Wide" filter routing, but of course that comes at the sacrifice of using any of the other filter routings.

Ideally, I think all of the filter routings should be stereo by default (and get rid of the redundant ones), but that's a ways off in the future.

[impaler42]

So how exactly does Surge implement transwave synthesis? I saw a post by layzer where he said he ported over the Ensoniq VFX waveforms but my understanding was that transwave synthesis consisted of more than just the wavetables. The ability to move loop points during playback of a note etc. Any further details on this?

Also any plans for adding Vector Phaseshaping Oscillators? Just curious.

[Halonmusic]

Whats transwave synthesis? sounds made up imo.

[EvilDragon]

It's just how Ensoniq used to call wavetables.

[baconpaul]

Short version on how surge does it (with the wavetable oscillator) is that it applies a bunch of transformations to the phase and magnitude traversal over the wavetable and then pumps that into a dac simulation for each voice. Think of things like the formant shift as being Changes in when the per cycle impulses are delivered to the dac. The window oscillator basically convolves with predefined phase waveforms kinda again with transforms. And obviously it interpolates between tables. And does all the antialiasing stuff you would expect. If you play with it it is pretty clear.

The longer version is longer but the code is all on GitHub if you want to dig into the details. The real answer of exactly what it does is all there for anyone to see, which i still think is super cool!

[EvilDragon]

Also, 1.7 milestone is created on github now, so everyone can see roughly what the plan is for that version.

https://github.com/surge-synthesizer/surge/milestone/14

[baconpaul]

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!

[scook]

I noticed in https://github.com/surge-synthesizer/su ... d-vocoder) Cakewalk is listed as "Tested and not working properly" however; it seems to work OK when added to an audio FX rack then following the directions in part 3. Basics of using Surge in compatible software. A MIDI track may be added to send MIDI data to the synth.

What parts do not work properly?

[planetearth]

I noticed in https://github.com/surge-synthesizer/su ... d-vocoder) Cakewalk is listed as "Tested and not working properly" however; it seems to work OK when added to an audio FX rack then following the directions in part 3. Basics of using Surge in compatible software. A MIDI track may be added to send MIDI data to the synth.

What parts do not work properly?

Maybe they're referring to easily changing the zoom setting? It's not as straightforward in Sonar or Cakewalk by Bandlab (CbB). But I've been using it on a few projects in both, and other than the zoom issue (which is easy to work around), I haven't seen any problems outside of the other known issues (that is, the ones that aren't specific to Sonar or CbB).

Steve