One Synth Challenge #159: Surge XT

VST, AU, AAX, etc. plug-in Virtual Instruments discussion
RELATED
PRODUCTS
Surge XT
User avatar
FrogsInPants
KVRist
284 posts since 4 Nov, 2019

Post Sat May 14, 2022 4:57 am

EvilDragon wrote: Sat May 14, 2022 4:06 am The Surge Synth Team considers formula modulator as an integral part of it, and encourages its usage! Considering you cannot pipe the output of the LFO in Surge to an audio output (plus, you're strictly limited by LFO rate being a maximum of 512 Hz, which means at 250-something Hz it actually starts aliasing), I would say it's entirely fair game to use it to create wild modulation paths not otherwise possible.
The 'process' function is called once per block. What determines the block size? I was thinking this meant per block as specified by the DAW, but your comment about when it starts aliasing suggests it is hard coded within Surge.

User avatar
EvilDragon
KVRAF
22424 posts since 7 Jan, 2009 from Croatia

Post Sat May 14, 2022 5:11 am

Surge processes things in chunks of 32 samples regardless of your audio buffer size. This basically determines the control rate for modulation, too.

empphryio
KVRist
388 posts since 14 Apr, 2019

Post Sat May 14, 2022 1:05 pm

1. We should probably sticky this thread.
2. Is there a way to keep an FX on while scrolling through presets?

User avatar
Boy Wonder
KVRist
108 posts since 30 Jan, 2021

Post Sat May 14, 2022 5:50 pm

Some of the OSC rules are confusing and contradictory. That said, I'd like to build a riser in SurgeXT. Any pointers?

3lu5iv3
KVRist
434 posts since 24 Sep, 2016

Post Sat May 14, 2022 6:10 pm

Boy Wonder wrote: Sat May 14, 2022 5:50 pm Some of the OSC rules are confusing and contradictory. That said, I'd like to build a riser in SurgeXT. Any pointers?
Maybe modulate the pitch of an oscillator by using an LFO?
SoundCloud
"I believe every music producer inherently has something unique about the way they make music. They just have to identify what makes them different, and develop it" - Max Martin

User avatar
Boy Wonder
KVRist
108 posts since 30 Jan, 2021

Post Sat May 14, 2022 6:26 pm

@3lu5iv3 - Good idea. I'll try that now as well as with the MSEG's.

User avatar
Boy Wonder
KVRist
108 posts since 30 Jan, 2021

Post Sat May 14, 2022 7:03 pm

Update - Yeah! I did it! [Pats self on back]. It's as I suspected - route the oscillators to MSEG pitch. Works like a charm. I made five risers so far. The thing is, I was spoiled rotten by the convenience of AIR Music's TheRiser.

BrainBeatMusic
KVRer
24 posts since 19 Apr, 2022

Post Sat May 14, 2022 11:27 pm

Hi Guys Here is I hope my last version of my track unless someone can hear an issue that is likely not in the rules or an idea to help improve it. I will post the info about the track later in an update.
https://soundcloud.com/user-783020495/e ... al_sharing

ElVincente
KVRist
239 posts since 22 Jun, 2019

Post Sun May 15, 2022 6:18 am

Hi,

I had several times settings going back to saw init with this build : surge-xt-win64-NIGHTLY-2022-05-04-7253035
I'm using reaper 6.57 win10
Won't have time to beta test any more if I want to finish my track, so I'm reverting to last stable build.

baconpaul
KVRist
497 posts since 25 Dec, 2018

Post Sun May 15, 2022 7:06 am

ElVincente wrote: Sun May 15, 2022 6:18 am Hi,

I had several times settings going back to saw init with this build : surge-xt-win64-NIGHTLY-2022-05-04-7253035
I'm using reaper 6.57 win10
Won't have time to beta test any more if I want to finish my track, so I'm reverting to last stable build.
Oh that's the first report we have of that happening outside of Logic / M1. Can you give me an idea roughly what you were doing when it reset?

I don't think i've changed the load / setup order but if this is on project-reopen then i'm very interested in hearing more about the bug.

Sorry you had this experience.

User avatar
FrogsInPants
KVRist
284 posts since 4 Nov, 2019

Post Sun May 15, 2022 10:30 am

baconpaul wrote: Sun May 15, 2022 7:06 am
ElVincente wrote: Sun May 15, 2022 6:18 am Hi,

I had several times settings going back to saw init with this build : surge-xt-win64-NIGHTLY-2022-05-04-7253035
I'm using reaper 6.57 win10
Won't have time to beta test any more if I want to finish my track, so I'm reverting to last stable build.
Oh that's the first report we have of that happening outside of Logic / M1. Can you give me an idea roughly what you were doing when it reset?

I don't think i've changed the load / setup order but if this is on project-reopen then i'm very interested in hearing more about the bug.

Sorry you had this experience.
I had the same happen with the 05-06 nightly, in Reaper on M1. I'm afraid I can't help you with what I was doing when it reset. I just found it had reset at some point when I went to check something in the patch on an otherwise empty track I hadn't touched in a while. It was just the one track.

baconpaul
KVRist
497 posts since 25 Dec, 2018

Post Sun May 15, 2022 10:33 am

FrogsInPants wrote: Sun May 15, 2022 10:30 am
baconpaul wrote: Sun May 15, 2022 7:06 am
ElVincente wrote: Sun May 15, 2022 6:18 am Hi,

I had several times settings going back to saw init with this build : surge-xt-win64-NIGHTLY-2022-05-04-7253035
I'm using reaper 6.57 win10
Won't have time to beta test any more if I want to finish my track, so I'm reverting to last stable build.
Oh that's the first report we have of that happening outside of Logic / M1. Can you give me an idea roughly what you were doing when it reset?

I don't think i've changed the load / setup order but if this is on project-reopen then i'm very interested in hearing more about the bug.

Sorry you had this experience.
I had the same happen with the 05-06 nightly, in Reaper on M1. I'm afraid I can't help you with what I was doing when it reset. I just found it had reset at some point when I went to check something in the patch on an otherwise empty track I hadn't touched in a while. It was just the one track.
I think I know what is causing this and I have a PR ready. I think there's a race condition between initialization and DAW restore and could, occasionally, reproduce it with a particular logic gesture (which is why I thought it was a logic problem).

May be a new nightly in an hour or two with a potential fix.

Appreciate all the reports.

ElVincente
KVRist
239 posts since 22 Jun, 2019

Post Sun May 15, 2022 11:44 am

baconpaul wrote: Sun May 15, 2022 7:06 am
ElVincente wrote: Sun May 15, 2022 6:18 am Hi,

I had several times settings going back to saw init with this build : surge-xt-win64-NIGHTLY-2022-05-04-7253035
I'm using reaper 6.57 win10
Won't have time to beta test any more if I want to finish my track, so I'm reverting to last stable build.
Oh that's the first report we have of that happening outside of Logic / M1. Can you give me an idea roughly what you were doing when it reset?

I don't think i've changed the load / setup order but if this is on project-reopen then i'm very interested in hearing more about the bug.

Sorry you had this experience.
Not a big deal, and with reaper's nice auto save feature I almost lost nothing.

Just as froginpants said, tracks I did not touch for some time were reverted to init setting. I did all my sounds from init too if it is of any help for you...

The Sound Of Merlin
KVRist
49 posts since 29 Jan, 2022

Post Sun May 15, 2022 10:51 pm

Dear friends,

Here's my track for this OSC #159: 33 instances of Surge XT.

DAW: Cubase 11 Pro
Native Cubase plugins: Frequency, GEQ-30, Stereo Delay, Revelation, Tube Compressor, AutoPan and Maximizer.
Free 3rd party plugs: Panagement 2 by Auburn, Baby Come Back by Baby Audio, MCharmverb by Melda Production, Wider by Polyverse Music and Supermassive by Valhalla.

The Alien Voice has been created using the Vowel/Speech wavetable in Surge's TWIST engine.

https://soundcloud.com/thesoundofmerlin ... conscience

User avatar
diaseis
KVRist
90 posts since 16 Jul, 2019

Post Wed May 18, 2022 12:25 am

Hi !

I noticed that, when chosing a preset (top left menu button, above "LFO"/"name of selected modulator") from the modulation section, the "LFO EG" gets greyed out and I can't find to get back the control on it. I think it's a bug but I might be wrong. Do you guys have the similar behavior ? If so, I'll file a bug report on Github :) .

Return to “Instruments”