Klanghelm SDRR - flexible saturation plugin released

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
Post Reply New Topic
RELATED
PRODUCTS
SDRR

Post

tonhelm wrote:
J4R1O wrote:Tony,

I'm working on two songs at the moment and they both have SDRR (on Desk Mode) on the master bus.

The thing is that after installing 1.0.1 they both sounded... well, extremely different. Seems like something has changed. I lowered drive knob and it helped but somehow it doesn't sound the same as with previous version of SDRR.
The reason for this is, that there was a bug in the compressor code of DESK mode in the initial version 1.0, which is fixed in 1.0.1. The compressor is pre saturation. Lowering the compression amount will also decrease the saturation amount in most cases.

Tony
Ok! Good to know! Yeah, I fixed the drive amount and levels and everything's back to normal. :)

Have to say that SDRR is one hell of a plug-in. You should be very proud of it. :tu:
Optimal number of audio plugins is one more than you currently have.

Post

i installed SDRR 1.0.1. Had a project where SDRR was already used and now it opens with "default".

is this correct? it sounded better on my track before, iirc. also since i do not remember the preset and tweaking, i can not get it to sound the same now :(

studio one, latest built, 64 bit, windows.
Finally!

Post

cyphersuit wrote:i installed SDRR 1.0.1. Had a project where SDRR was already used and now it opens with "default".

is this correct? it sounded better on my track before, iirc. also since i do not remember the preset and tweaking, i can not get it to sound the same now :(

studio one, latest built, 64 bit, windows.
Are you using the VST3? the project is saved correctly with all the settings and such. But It's possible, that the preset name itself is reset, especially if you've tweaked the settings. I didn't change a thing in the plugin for the update, except for the bug in DESK mode in the compressor part. If in doubt, send me an email, so that I can investigate this further with you.

thanks,

Tony

Post

Yes i am using vst3. If i bypass the plugin, the audio now just sounds the same. So more seems to have changed. I will start a test project to explore the matter tomorrow.
Finally!

Post

I have reported before that the VST3 version does not retain the preset name, it always resets to default. However the settings seem to stay the same. The VST2 version is fine.

Post

Well on my case the settings got reset, too. I was having SDRR on the drum bus for some drastic change. It is now totally gone with the update. When bypassed or on - SDRR isn't affecting the drum sounds anymore.
Finally!

Post

by the way: i decided to delete the vst3 and install vst 2.4. i find it difficult, if the preset name is always reset to default.

is this behaviour the same with dc8c2? then i will change those installations too.
Finally!

Post

with dc8c2 there are no presets showing for me in the VST3 version, again VST 2 is fine

Post

keel wrote:
EvilDragon wrote:
keel wrote:Is the CPU-Usage high as in the free version? If so, I will not even think about this one..
Screw CPU usage, quality counts. Also, bounce/freeze your stuff.

Upgrading the computer is also a valid option ;)
I have i7 @3.5ghz, and that free what I tested, one instance used almost 10%, so this plugin is one of those what you use on every channel, then one instance and 10% is pretty way too much.
Strange.... I have a slower processor and I'm getting less than 1% CPU hit. .7% to be precise. Win 7 x64 bit. Reaper x64. x64 version.

I forget all the specs off the top of my head but it is an i7 core second gen but I am almost sure lower than 3.5ghz

Post

Keith99 wrote:with dc8c2 there are no presets showing for me in the VST3 version, again VST 2 is fine
Ok, thx. I still wonder why i do not have this with other vst3 plugins!?
Finally!

Post

What happened to the stereo sound? Really like SDDR, especially the desk. Unfortunately when placed on a stereo track the sound goes mono on all modes. I selected different xtalk modes and no change. Running Cubase 7.02 32bit. Anyone else experience this? Now this is odd, thought I'd try again before I submitted this post. Some presets are stereo and some are not. Changing the xtalk setting seems to have no effect. Even moveing the mix to all dry it's still mono. For me DR snare pop is clearly mono and DR full toms preset is clearly stereo. And as I said xtalk seems to have no effect. Anyone else?
Thanks......

Post

anabkemeir wrote:What happened to the stereo sound? Really like SDDR, especially the desk. Unfortunately when placed on a stereo track the sound goes mono on all modes. I selected different xtalk modes and no change. Running Cubase 7.02 32bit. Anyone else experience this? Now this is odd, thought I'd try again before I submitted this post. Some presets are stereo and some are not. Changing the xtalk setting seems to have no effect. Even moveing the mix to all dry it's still mono. For me DR snare pop is clearly mono and DR full toms preset is clearly stereo. And as I said xtalk seems to have no effect. Anyone else?
Thanks......
Confirmed here X64 version
Duh

Post

bungle wrote:
anabkemeir wrote:What happened to the stereo sound? Really like SDDR, especially the desk. Unfortunately when placed on a stereo track the sound goes mono on all modes. I selected different xtalk modes and no change. Running Cubase 7.02 32bit. Anyone else experience this? Now this is odd, thought I'd try again before I submitted this post. Some presets are stereo and some are not. Changing the xtalk setting seems to have no effect. Even moveing the mix to all dry it's still mono. For me DR snare pop is clearly mono and DR full toms preset is clearly stereo. And as I said xtalk seems to have no effect. Anyone else?
Thanks......
Confirmed here X64 version
In the lower left corner of the VU meter you can select the channel mode. when set to MONO, the signal becomes mono even on a stereo track. This is intended. Why? Some hosts (Reaper) can't differentiate between mono and stereo tracks. In this case setting SDRR to mono will save CPU and avoids unwanted image widening.

Tony

Post

Thanks, duh... just found it in the manual also. Thanks!

Post

Keith99 wrote:I have reported before that the VST3 version does not retain the preset name, it always resets to default. However the settings seem to stay the same. The VST2 version is fine.
I can confirm the behavior on both WL8 and C7 (VST3 version, 32bit).

Wavelab completely resets the GUI, Cubase only resets the preset name and sporadically one or two parameters.

This is a known issue that came up in RC days. Apparently, there seems to be A LOT wrong with VST3 versions by developers as of late - and they can't track the reasons why.

Quietinthedark wrote:Strange.... I have a slower processor and I'm getting less than 1% CPU hit. .7% to be precise. Win 7 x64 bit. Reaper x64. x64 version.
Reaper shows way lower values due to internal processing hacks to keep the ASIO/CPU power low.

Cubase on the other hand has severe issues with certain drivers and the ASIO Guard. Steinberg is aware(!) of that, but there was no fix so far.

At 256 samples:
VST3 instance - 12,5-15% (at 1024 samples only 8-10%)
VST2 instance - about 10% (at 1024 samples only 8-10%)

Wavelab shows 2% per VST3 instance. And that is on my i7 920 OC'd to 3,6GHz.
[ Mix Challenge ] | [ Studio Page / Twitter ] | [ KVRmarks (see: metering tools) ]

Post Reply

Return to “Effects”