I've been a long-time user of Waves plugins (mainly the Gold bundle plugins) but having just recently bought a new Macbook Pro, I've realised that I can't reactivate my license on it and I have to pay for the yearly upgrade plan (have any of those plugins actually been upgraded in the past few years??) or commit to the Waves subscription model, which I'd rather not do.

Waves H-Delay is one of my favourite plugins, and probably the only Waves plugin which I'd bother paying for to own outright. However, in my annoyance at Waves, and realising that there is surely a better, more modern alternative delay out there, I would really appreciate some direction on where to look!


Download H-delay Plugin Free


Download Zip 🔥 https://urlgoal.com/2y4QpJ 🔥



A sine wave or pink noise passed through a plugin with a detailed spectrum view can help you better understand those subtleties so they can be applied across your entire mix to add up to significant character.

EchoBoy is an amazing delay plugin with vintage vibe. SoundToys studied some of the most popular hardware delays of all time and modeled them for EchoBoy. Classic sounds include the EchoPlex, Space Echo, Memory Man, DM-2, and the TelRay oil can delay.

Waves is great at producing quality plugins which are easy to use, and the Manny Marroquin Delay is no exception. One thing great mixers do all the time is add extra effects to their delays to spice them up. This might include sending the delay to a reverb, adding a bit of saturation, or even modulating it with a phaser or flanger.

Roland launched the Space Echo hardware unit in 1973, and it can be heard on recordings by Pink Floyd, David Bowie, and countless others. It was a tape delay and spring reverb unit capable of virtually any style of analog echo. As is the case with most delay plugins or hardware, it could sound quite reasonable and subtle, or it could go into complete chaos at the twist of a knob. UAD painstakingly captured all the magic of the original hardware in this phenomenal delay plugin!

I've tried maybe 10 or so plugins from Platinum - and all is well, except for H-Delay. I inserted it on a guitar track, and initially it was fine (first play through). Then all of a sudden I started getting some extreme latency - or what I assume is latency. When I playback the track, the audio doesn't start playing until about 1/2 a second in. Same goes with having a guitar plugged in and playing real time - if the H-delay is inserted and active on the track - and I hit a note - it doesn't play back until about 1/2 a second later. I tried different buffer settings in Logic to no avail - and this shouldn't be an issue anyway - this is a powerful new iMac and no other plugs were on - just 1 track, 1 instance of H-delay. I tried some other delays and all of them are fine.

I have a mono track, acoustic guitar. I send it out to an aux track. The aux track is stereo. To no surprise, if I place the mono version of a Waves plugin (H-Delay) on the aux track, the result is mono, yay. If I instead place the stereo version of the same plugin, in this case H-Delay and set it to "ping-pong", I get the nice left and right back and forth action in stereo, once again yay.

Here's where things get weird. If I place the mono/stereo version of the same plugin on the track, H-Delay, and set it to ping-pong, the result is not stereo, it's mono. If that's not weird enough, as an experiment I first added the stereo version of H-Delay to the aux track, set it to ping-pong, it worked great. I then also inserted the mono version of H-Delay to the aux track, but I disabled it. So now I have both the mono and stereo versions of H-Delay on my aux track, but the mono version is disabled. I was expecting to get a stereo ping-pong delay effect, NOPE. It resulted in a mono signal, even though the mono version was disabled.

I'm left to the conclusion that it's probably best to use Waves stereo version of their plugins, this way if the effect is a stereo effect, then the result will be stereo and likewise if the effect is mono the result will be mono or dual mono and closer to the user's expectations.

My next question is, if this behavior is true for Waves plugins, is this true for other developers? This could be very annoying. Imagine you have a series of plugins that you want to use. If any of those plugins forces a mono result regardless of the plugins on the track being stereo or not, you would have to create a series of effects tracks (aux tracks) for each plugin as a work around to create a chain of plugins in sequence to get a result that is stereo.

In my opinion, Cakewalk should use the interleave (mono or stereo) setting of the track to determine if the resulting output is mono or stereo, not let the plugins determine that outcome. This way if a plugin on a track happens to be coded as a mono plugin, the way Waves mono plugins seem to be, it won't override a following plugin that may be stereo.

And no, not all plugins work the same way when mixing mono and stereo. Some are smarter than others. Some get downright flaky when you send the "wrong" interleave to them. When in doubt, if the vendor offers both mono and stereo versions, use whichever is appropriate for the track.

Check this thread. Waves Mono work in Mono, Stereo versions work in Stereo, and currently Mono/Stereo versions ONLY work in Mono. When trying Mono/Stereo versions on a track, those can get stuck in Mono. Normally when changing from mono interleave to Stereo interleave uou may have to Press E twice (or bypass plugin or bin then re-enable) to force Stereo interleave.

I'm not sure if this is related or not? But, if I place a mono plugin on a stereo track, then remove the plugin and replace it with the stereo version, the sound is still mono (or not quite right). I have found by clicking the track Interleave Button, from stereo to mono, and back to stereo again, this corrects the audio sound.

I just did some messing around in Reaper and the plugin behavior is as expected. I first inserted the Waves H-Delay (stereo) on the track and set it to a ping-pong delay and it ping-ponged as expected. The next test was inserting just the Waves H-Delay (mono/stereo) on the track and set it to ping-pong and got a ping-pong delay, too as expected, back and forth in stereo. I did another test with first inserting the Waves H-Delay (mono) followed by Waves H-Delay (stereo) set to a ping-pong delay. In Cakewalk this would produce a mono signal without the left to right ping-pong effect. I was expecting the same result in Reaper, but this was not the case. Instead I got the result that you would want, the mono version sent its result to the stereo ping-pong and output the ping-pong effect. The order in which the plugins are placed in the insert list is important and intuitive. If the stereo effect comes after the mono effect, the result is stereo. If the mono effect comes after the stereo effect, the result is mono. This makes complete sense.

What is Reaper doing differently than Cakewalk under the hood to produce the intuitive behavior? Is Cakewalk's handling of mono/stereo plugins by design or is it legacy code that hasn't been updated?

I'm not planning on switching to Reaper, no way. I just happen to prefer the way it handles mono/stereo plugins. Would be nice if Cakewalk could change its ways. What is the benefit of Cakewalk's approach to mono/stereo plugins, because I can't think of one?

That's not to say there isn't an issue in CbB's handling of mono (I think there is - some mono plugins (eg. UAD?) perform better on mono tracks in other DAWs, but all CbB's tracks are, as far as I understand, stereo behind the scenes so this advantage is never gained - but it's not totally broken in this instance). e24fc04721

wget http stedolan.github.io jq download linux64 jq

al green simply beautiful mp3 download

download suara toa polisi

download de pop playtime captulo 2 mobile

download spy mouse 1.0.6 for android