KVR Audio

Kees49 · Post by **Kees49** » Sun Mar 29, 2026 11:20 pm

I just want to say THANK YOU to the developers of this great synth. I played many VA VSTi's and while some are great (Diva, Repro, DUNE 3), this synth really surprised me! Somehow it reminds me of my Nord Lead 2 in a way, like they are family. The high resonance sounds sound just gorgeous. I must give this synth a 10/10, period!

Danilo Villanova · Post by **Danilo Villanova** » Mon Mar 30, 2026 3:51 am

Yeah, incredibly good ploysynth. Oscillators and filters are top notch, especially w/ oversampling, and the modulation options are not bad.

teilo · Post by **teilo** » Mon Mar 30, 2026 1:09 pm

Weasel-Boy wrote: Fri Mar 27, 2026 5:21 pm
teilo wrote: Fri Mar 27, 2026 1:42 pm
baconpaul wrote: Fri Mar 27, 2026 1:18 pm That's exactly it. If I modify the VST3 to not support edge programs at all in Cubase, it all works. It is definitely calling setProgram again after setState and thats just .... ugh. wrong.

It will take me a bit of time today to get it merged and cubase-only but I'll get it done and push a 1.0.3 today or tomorrow.
But it's Steinberg, and they obviously will use VST3s properly, right?

Right?
Yes, Steinberg treats VST3's correctly in Cubase. It all works incredibly well.

That's incredibly naïve.

D-Fusion · Post by **D-Fusion** » Mon Mar 30, 2026 2:04 pm

Kees49 wrote: Sun Mar 29, 2026 11:20 pm I just want to say THANK YOU to the developers of this great synth. I played many VA VSTi's and while some are great (Diva, Repro, DUNE 3), this synth really surprised me! Somehow it reminds me of my Nord Lead 2 in a way, like they are family. The high resonance sounds sound just gorgeous. I must give this synth a 10/10, period!

+1
I would like to thank the original creator for making it and the Surge Team for continuing the work on this fat sounding synth

baconpaul · Post by **baconpaul** » Mon Mar 30, 2026 2:48 pm

4_the masses wrote: Sun Mar 29, 2026 6:21 pm
baconpaul wrote: Thu Mar 26, 2026 8:01 pm
4_the masses wrote: Thu Mar 26, 2026 6:27 pm Is there a PDF of the user manual ? The machine I use it on is not online.
Just put together a script which generates it and its now linked from the manual online.

The script doesn't run automatically when we update the manual yet. That's a next step. But at least current manual pdf is there.
How would I do that please ?

The first thing - linked from the manual online - is to open the manual online and click the link to the pdf then save it

The second thing - write a GitHub action in the web repository to run this script and repush the pdf if the manual content changes

whassup · Post by **whassup** » Mon Mar 30, 2026 8:40 pm

D-Fusion wrote: Mon Mar 30, 2026 2:04 pm
Kees49 wrote: Sun Mar 29, 2026 11:20 pm I just want to say THANK YOU to the developers of this great synth. I played many VA VSTi's and while some are great (Diva, Repro, DUNE 3), this synth really surprised me! Somehow it reminds me of my Nord Lead 2 in a way, like they are family. The high resonance sounds sound just gorgeous. I must give this synth a 10/10, period!
+1
I would like to thank the original creator for making it and the Surge Team for continuing the work on this fat sounding synth

+1
Me likes this very muchos!

ampetrosillo · Post by **ampetrosillo** » Tue Mar 31, 2026 5:08 pm

On my system (Win 11, FHD screen) any zoom setting other than 125% is very fuzzy with the default non-vector theme.

satYatunes · Post by **satYatunes** » Tue Mar 31, 2026 5:29 pm

^^^ I have the same setup and have no issues with the default theme. It can go up to 150% max on my monitor and looks clear no fuzziness. I have "Use software renderer" on. See if that makes any difference.

ampetrosillo · Post by **ampetrosillo** » Tue Mar 31, 2026 5:51 pm

Nope.

100%.
https://postimg.cc/ZWXJwBzc/1a75f73e

125%.
https://postimg.cc/tnn5tM3h/91204d8b

(I don't know if you can appreciate the difference).

Oh, maybe it's my failing eyesight... but the vector version appears far clearer.

EvilDragon · Post by **EvilDragon** » Tue Mar 31, 2026 11:42 pm

You seem to have some OS level DPI scaling enabled, though? 100% size is 1150x576, both your screenshots are larger than that.

ampetrosillo · Post by **ampetrosillo** » Wed Apr 01, 2026 11:31 am

125% OS scaling, but that's the recommended scaling. I presume this is quite common.

EvilDragon · Post by **EvilDragon** » Wed Apr 01, 2026 7:23 pm

On a non-HiDPI display (1920x1080, 1920x1200), 100% is the most common scaling actually. That's how I have it set up.

ampetrosillo · Post by **ampetrosillo** » Wed Apr 01, 2026 7:54 pm

Ok, but still. It's not a big issue, hey? But I presume a lot of people use fractional scaling and having the UI look a bit blurry for them is detrimental to the synth. Some shallower user than me (and I can be very shallow. I buy bass guitars just for their looks) might just go "ick! I'm not using it!".

4_the masses · Post by **4_the masses** » Wed Apr 01, 2026 8:02 pm

baconpaul wrote: Mon Mar 30, 2026 2:48 pm
4_the masses wrote: Sun Mar 29, 2026 6:21 pm
baconpaul wrote: Thu Mar 26, 2026 8:01 pm
4_the masses wrote: Thu Mar 26, 2026 6:27 pm Is there a PDF of the user manual ? The machine I use it on is not online.
Just put together a script which generates it and its now linked from the manual online.

The script doesn't run automatically when we update the manual yet. That's a next step. But at least current manual pdf is there.
How would I do that please ?
The first thing - linked from the manual online - is to open the manual online and click the link to the pdf then save it

The second thing - write a GitHub action in the web repository to run this script and repush the pdf if the manual content changes

Many thanks

EvilDragon · Post by **EvilDragon** » Wed May 06, 2026 11:18 am

Hey all!

I just wanted to let you know that, as of latest nightly build of OB-Xf, we now have support for reading OB-Xd patches!

Simply drop your OB-Xd FXPs in a subfolder of your user data folder (basically, where your own user patches get saved), and they will load up as if they were an OB-Xf patch!

One small caveat, though. Since OB-Xd had an incorrect middle C reference frequency which we have fixed in OB-Xf (it was an octave higher than supposed to), OB-Xd patches will compensate for this by setting the Transpose knob up an octave, in order to remain as close to the original patch as possible. Of course, this will result in an edge case where an OB-Xd patch which already had its Transpose set to max, that patch will sound an octave lower in OB-Xf. This can be improved slightly by then setting both oscillator pitch knobs up an octave, if they are also not maxed out (but that would realistically be a very rare situation, I would suspect). This improvement will come next week likely (when I'm back from Superbooth).

Actually there is another small note. The Step parameter in OB-Xd does not exist in OB-Xf, in OB-Xf you hold Ctrl to quantize oscillator pitch to semitones. However, in OB-Xd this change was done in the DSP core itself. So the oscillator pitch knob could say 7.38 semitones, but this would be rounded to 7. OB-Xf will do this quantization on import, so the pitch knob will say 7.00 instead of 7.38 semitones.

Importing of OB-Xd FXB files is also upcoming, next week. This will be a literal import procedure, either via option in the patch browser menu or by drag and dropping an FXB onto OB-Xf interface. The FXB will be scanned for patches and they will be individually written out in your user data folder as a new Project (using the same name as the FXB's filename).

Lastly, all these patches of course won't contain any metadata like Author, Category, License. Just so you know.

There we go, hope this brings some happiness to y'all!

OB-Xf by Surge Synth Team