Either one of my Reaper settings is off, or Slate Plugins have a major issue...

[NickScottProducer]

Hey guys. I've been battling this for a while now. Have always noticed this! In my audio example you'll hear a few cymbal hits.. Pay close attention to the tail en of the last one. It sounds as if there is a noise gate on the audio, just juggling between the threshold. A distinct crackle/tearing of the audio.

https://www.dropbox.com/s/oy4o3fzgi7...e_why.mp3?dl=0


So what you're hearing is literally just some compression on the way in (cla76) and then an instance of slate VMS. There is nothing in the VMS modules. When I bypass Slate -- the crackling is gone. This happens also with slate VBC and Slate VTM. Either something is going on with Reaper's communication with the Slate plugins, or I have NO clue what's going on.. But it's bugging me a lot and it will until it's figured out. I'm running VST3 instances of the slate plugins. Super open to sharing my Reaper preferences if that's of any help!

[Neutronic]

Originally Posted by NickScottProducer

I'm running VST3 instances of the slate plugins.

Hi Nick,
does it mean you haven't tried VST2 versions yet? I would check that first at least to confirm/rule out the compatibility issue.
I have dealt with plug-ins that misbehaved when run as VST3.

[NickScottProducer]

Originally Posted by Neutronic

Hi Nick,
does it mean you haven't tried VST2 versions yet? I would check that first at least to confirm/rule out the compatibility issue.
I have dealt with plug-ins that misbehaved when run as VST3.

Yeah it unfortunately still happens with vst2

[RobertP]

https://forum.cockos.com/showthread....20#post2138520

[NickScottProducer]

SUPER dope news -- it's an actual issue. Here's what I got back from slate bois:

"

Hi there,

Thank you for contacting Slate customer support. This is an issue specific with Reaper and our VST3 plugins. The issue has been logged for fixing and will be resolved in an update. For the time being please use the VST2 versions of the plugins or make sure plenty of signal is being sent through the VST3 plugin format (considering the issue only happens at really low volumes)."

[poetnprophet]

I knew it!
I contacted them about that noise months ago, they told me to uninstall/reinstall, which seemed to fix it but then it returned. It was driving me nuts!

I sure hope they fix it for good.

[Stella645]

Originally Posted by NickScottProducer

Yeah it unfortunately still happens with vst2

Originally Posted by NickScottProducer

For the time being please use the VST2 versions of the plugins "

So their vst3 doesn't work and they advise to use vst2...but the vst2 also doesn't work?

[ivansc]

Slate & I have a history of them failing to find and fix bugs properly. I currently own a fair bit of their software but the only ones that work reliably are the originial Kontant based drums and their tape machine sim.

Maybe they need to hire a bug-fixer? Have to say though that their support guys are more than willing but sadly in my case they never did resolve my issues with Steven Slate Drums 4 Platinum... Money & a lot of my time down the drain.

[daxliniere]

It's not just you. I have a bunch of slate licences from beta testing for them YEARS ago and the other day I thought I'd give them another shot. Nothing but crashes and problems where VMR hangs on to the iLok suffice too long, causing the following iLok-secured plugins to fail authorisation.
Tried VST3 first, then VST2: same deal. My friend at Sonnox tested in REAPER on Mac: he gets a crash after a few seconds just by inserting VMR into a blank session...

I left the Slate beta team because their bug hunting/solving capabilities are some of the worst I've ever encountered. The plugins sound okay, but not even slightly reliable. On a recent sort call, they asked why I was using an outdated version of VTM and I told them it's stable so I don't want to risk 'upgrading' myself into more headaches.
With one big fix they introduce another bug.

What finally broke my patience was a bug (they eventually fixed) which showed the deeper problem.
It was a bug where the left VU meter, but only the left, would get STUCK when signal went too high. (Yes, as if it was a physical meter.)
Which lead me to ask WHY THE HELL IS THE CODE FOR THE LEFT CHANNEL DIFFERENT TO THE RIGHT CHANNEL?!? What programmer does that?!??? You write one block of code for the meter and you call it each time you need a meter. That is coding 101 and I'm not even a coder! It's just plain logic.

[MRMJP]

Slate is all about quantity and hype, not quality and stability.

I gave up years ago and also dropped off the beta team. Too much crap.