One Synth Challenge #159: Surge XT (j5v Wins!)

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

Post

Alright, here's my entry for OSC 159. It uses Renoise 3.4.1 and 11 instances of Surge using Surge FX only. I will tweak it and reupload it within the next 4 days.
https://soundcloud.com/jack-cimino/korg ... al_sharing

Post

Hi all,

Here is my submission for OSC159 - Surge XT.

https://soundcloud.com/neverbeeninariot/dissolution

Enjoy, or not! :D


Big props to the Surge Synth Team for their work updating this fantastic synth, and to Claes for releasing it into the wild. Surge is a beast!

Bitwig
Surge XT x 13

Mix Plugins - Bitwig
Compressor, Delay-2, Dynamics, EQ+, EQ-5, Peak Limiter, Pitch Shifter, Reverb, Saturator, Tool

Mix Plugins - Other
Rough Rider, TDR Nova

Master Track
Tool, Peak Limiter, TDR Nova, TDR Kotelnikov, Voxengo Span, Youlean Loudness Meter
-12.0 LUFS Int

Post

ZioMau wrote: Fri May 27, 2022 8:48 pm Well i have some things to say:
Really gelled with everything you said. And I love the jazz quote!

Good luck with the contest! Glad you're enjoying it. I'm enjoying it too.
Captain Silverpants

Post

baconpaul wrote: Thu May 19, 2022 11:50 am
FrogsInPants wrote: Thu May 19, 2022 11:02 am
] Peter:H [ wrote: Thu May 19, 2022 8:02 am @EvilDragon / @BaconPaul
Probably I missed the section in the manual ... but is there a way to link lfo speed to the notes played, at least in lower registers?
I know the lfos can go up to a few 100 hz... can I map them in a easy way that for any A key coming in they use 220 Hz and for other keys the respective frequency "around" 220hz? So for A3, A4, A5,... the Lfo uses 220 hz? For B3, B4, B5 the frequenzy of the B above 220 Hz...
You can keytrack the rate, but as far as I've been able to find there isn't a straight-forward way to modify the response curve. However, your question did give me an idea: Perhaps we can use a formula LFO to determine the response curve. The formula can access its control parameters like rate or deform to calculate its output. Keytrack one of those values, use that to determine the note number [...]
In current surge yeah that's how you would do it. Tutorial 06 shows how to use the key number to generate an output modulator signal.

In a future version of surge, we really hope to have more intuitive modulation manipulators (basically functions in the edges of the modulation graph). but it's not the future yet
BTW: I think I found it following the description above. I subscribed to "voice" in the init code and get the key number in the processing function. I use the note number then to compute the lfo sine fade with a start/end frequency related to the incoming note...only thing you have to take into consideration is that the LFO frequency has to be set to 1hz to get the intended AM frequency ...
Here's the fragment of the init code.

Code: Select all

function init(modstate)
    modstate["notefreq"] = {8.176, 8.662, 9.177, 9.723,10.301, 10.913, 11.562,12.250, 12.978,13.750,14.568,15.434,16.352}
    modstate["subscriptions"]["voice"] = true
That LUA stuff is really hilarious. I went through all the tuts and get the impression you should a.) add all that into the manuals asap. It's such a unique feature! And on top of that ...
b.) ... make LUA avaiable as a oscillator. There's actually a PR on github which didn't make it to the 1.1 ... I hope it will be in the 1.2

Post

baconpaul wrote: Sun May 15, 2022 6:33 pm
FrogsInPants wrote: Sun May 15, 2022 6:30 pm
baconpaul wrote: Sun May 15, 2022 3:06 pm
ElVincente wrote: Sun May 15, 2022 2:18 pm 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.
Hi Baconpaul.
Wanted to say thank you about the quick update you did last time.
After reverting to the stable build I think I did encountered the same bug (but not 100% sure about when the reverting to init happened though...)
But it seems to be rock solid now with the last nightly...
And I'm finishing my track now :wink:
You rock !
Last edited by ElVincente on Sat May 28, 2022 3:38 pm, edited 1 time in total.

Post

https://soundcloud.com/madmcman/figments-of-tomorrow

Here's my OSC for Surge XT. Had lots of fun with the modulation on this synth as well as the great FX options.

All sounds made by Surge XT
Made in Reaper with....

55 x Surge XT

VST:
CHOP
STFU
TDR Nova
TDR Kotelnikov
SPAN
Pancake 2
Wider

AirWindows:
Console 7 buss
Console 7 Cascade
Console 7 Crunch
Monitoring 2 (for mixing)
I also used AirWindows FX within surge itself.

JSFX:
ReaComp
ReaGate
Midi Tool 2
Dynamic Poly/mono MIDI Router
ReEQ
Midi Delay
Event Horizon Limter/Clipper
Last edited by MadMcMan on Sat May 28, 2022 3:24 pm, edited 1 time in total.

Post

ElVincente wrote: Sat May 28, 2022 1:42 pm
baconpaul wrote: Sun May 15, 2022 6:33 pm
FrogsInPants wrote: Sun May 15, 2022 6:30 pm
baconpaul wrote: Sun May 15, 2022 3:06 pm
ElVincente wrote: Sun May 15, 2022 2:18 pm 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.
Hi Baconpaul.
Wanted to say thank you about the quick update you did last time.
After reverting to the stable build I think I did encountered the same bug (but not 100% sure about when the reverting to init happened though...)
But it seems to be rock solid now with the last nightly...
And I'm finishing track now :wink:
You rock !
I also experienced this bug on one of the nightly builds on my windows 10 reaper machine. I had a track muted and at some point closing / reopening the project over the days that muted track lost its settings and was back to init mode. luckily i only noticed during cleanup as it was a track i was no longer using. I immediately saved all my surge instance sounds to presets after that.

Post

Hi all,

I have not been here for a long time.
Since I was sick and couldn't hear much, I couldn't participate in the OSC for the last few months.
But now I feel better and so I will try to participate again this month :)
At the last Surge OSC Challenge my entry was called "Sleepless in Germany in Germany" my next entry will be either "Sleepless in Germany Part 2" or "Part 3" or maybe "Part 4" :)

Here is already Sleepless in Germany in Germany Part 2

https://soundcloud.com/user-221952934-5 ... al_sharing

Greetings Jürgen

Post

] Peter:H [ wrote: Sat May 28, 2022 11:51 am That LUA stuff is really hilarious. I went through all the tuts and get the impression you should a.) add all that into the manuals asap. It's such a unique feature! And on top of that ...
b.) ... make LUA avaiable as a oscillator. There's actually a PR on github which didn't make it to the 1.1 ... I hope it will be in the 1.2
Tutorial patches = manual for formula modulator. Other than that we can just defer to Lua's own documentation.

As far as using Lua for oscillators, Lua is not fast enough for this purpose. Something like Faust would be far more appropriate, but it comes with a hefty set of dependencies if it were to be JIT compiled in realtime.

There likely won't be 1.2, but 2.0 (and a whooooole bunch of changes as a consequence).

Post

EvilDragon wrote: Sat May 28, 2022 6:01 pm
] Peter:H [ wrote: Sat May 28, 2022 11:51 am That LUA stuff is really hilarious. I went through all the tuts and get the impression you should a.) add all that into the manuals asap. It's such a unique feature! And on top of that ...
b.) ... make LUA avaiable as a oscillator. There's actually a PR on github which didn't make it to the 1.1 ... I hope it will be in the 1.2
Tutorial patches = manual for formula modulator. Other than that we can just defer to Lua's own documentation.

As far as using Lua for oscillators, Lua is not fast enough for this purpose. Something like Faust would be far more appropriate, but it comes with a hefty set of dependencies if it were to be JIT compiled in realtime.

There likely won't be 1.2, but 2.0 (and a whooooole bunch of changes as a consequence).
My comment about the manual refers more to the specific integration into Surge XT rather than learning lua itself.
As I'm writing this here I'm working again on refactoring my Catmul-Rom Spline based Amplitude Modulation hobby project which I implement with protoplug / lua ... so I know Lua very well, I'd say. Not fifth grad black belt, but brown belt.
To be more specific - I'm not sure that for instance all "subscription" options and all possible subscribeable values are covered in the tutorials... Anyways, you guys do some much good stuff, please take my comments not as a complaint but a suggestion.

Post

] Peter:H [ wrote: Sat May 28, 2022 6:19 pm
EvilDragon wrote: Sat May 28, 2022 6:01 pm
] Peter:H [ wrote: Sat May 28, 2022 11:51 am That LUA stuff is really hilarious. I went through all the tuts and get the impression you should a.) add all that into the manuals asap. It's such a unique feature! And on top of that ...
b.) ... make LUA avaiable as a oscillator. There's actually a PR on github which didn't make it to the 1.1 ... I hope it will be in the 1.2
Tutorial patches = manual for formula modulator. Other than that we can just defer to Lua's own documentation.

As far as using Lua for oscillators, Lua is not fast enough for this purpose. Something like Faust would be far more appropriate, but it comes with a hefty set of dependencies if it were to be JIT compiled in realtime.

There likely won't be 1.2, but 2.0 (and a whooooole bunch of changes as a consequence).
My comment about the manual refers more to the specific integration into Surge XT rather than learning lua itself.
As I'm writing this here I'm working again on refactoring my Catmul-Rom Spline based Amplitude Modulation hobby project which I implement with protoplug / lua ... so I know Lua very well, I'd say. Not fifth grad black belt, but brown belt.
To be more specific - I'm not sure that for instance all "subscription" options and all possible subscribeable values are covered in the tutorials... Anyways, you guys do some much good stuff, please take my comments not as a complaint but a suggestion.
Will def rescan manual for 11

Did you see the debugger also? That shows you the actual runtime subscribable events. May also be helpful

Post

So here's my submission !
https://soundcloud.com/user-637213504/s ... al_sharing
Made in reaper 6.
20 surge xt instances
Reacomp Reaeq Realimit Reagate (yeah, some of my patches were noisy and needed that lol)
Mequalizer Mcompressor
Geraintluf smooth limiter
MSED Tdr limiter n6 (free version) Sanford reverb

Made everything from scratch as I like to do. I had the impression I could have made 5 distinct tracks but that distorded sound I found out put me on rails for kind of a RATM tribute. So it got out pretty despaired and harsh, but I hope you enjoy listening to it nonetheless.
Man, what a synth! Thanks you for this gift all of you that contributed to this huge one !
Last edited by ElVincente on Sun May 29, 2022 12:11 pm, edited 2 times in total.

Post

Can we use wavetables from a commercial synths?
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

Post

here's mine.

https://soundcloud.com/3lu5iv3/zrelton

DAW = Reaper v6.58

Instruments = 5 X Surge XT

Effects = GTune, StereoTool, 4U+ ProjectTime,
SPAN, ReaLimit, ReaEQ

Wavetables = Sine
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

Post

https://soundcloud.com/user-87727874/loris-rolling

Reaper
30 instances of SurgeXT
ReaComp
ReaEQ
MEq
OrilRiver
ReaLimiter
StereoWidener
OTT
DDUtility
DDAutofilter

Post Reply

Return to “Instruments”