LittleStudios

Waves got back to me and gave me these instructions: I followed these instructions and restored the deleted registry folders. Cakewalk re-scanned VST's and properly removed the V11 H-Comp plugins. IT WORKED! This seems to be a more sound way of removing the unwanted versions. The registry edit way of removing the plugins worked as well. The one issue with the registry method, other than making a mistake, is if you do a full scan of your VST's it will repopulate the registry with the removed registry folders. Hence restoring the plugins you want removed.

Fixed it... I think. I went into the Registry and navigated to: Computer\HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Cakewalk VST X64\Inventory and removed the following registry folders: WaveShell1-VST3 11.0_x64.vst3*10 H-Comp Mono and WaveShell1-VST3 11.0_x64.vst3*11 H-Comp Stereo and presto, it worked. I of course exported a backup of the registry folders that were removed. Safety first.

Just reached out to Waves. We'll see what they say.

@Teegarden You first need to tell Cakewalk which plugins you want to have the oversampling enabled on, by accessing the "FX" icon in the top left of the plugin editor. Figure 1: Once you enable this plugin to use oversampling, you then have to be sure to globally enable plugin oversampling by clicking this icon: Figure 2: From my tests, if you don't first enable oversampling (upsampling) on a per plugin basis (Figure 1), enabling the global oversampling (Figure 2) will not do anything. To rephrase, plugins must have oversampling enabled for plugin oversampling to take effect. If the plugin has it's own built in oversampling, it will act as another multiplier depending on whatever multiplier the developer coded into the plugin, if you've enabled plugin oversampling on both the per plugin setting and global oversampling bypass/enable button. The default value of Cakewalk's per plugin oversampling is twice the sample rate of the project up to 384,000 Hz. You can manually input the oversampling sample rate in the AUD.INI file or use Scook's tool linked above in Scook's post.

@Starship Krupa You seem to have a very strong opinion about whether or not people should be using oversampling or not. Also you seem to have a very strong opinion on whether or not aliasing is audible. That's fine, everyone is entitled to their opinion. I'm not sure that my feature suggestion of higher oversampling on the plugins (which apparently already exists) warranted this response. Just the same, to answer your question... I typically use oversampling only when I feel it's needed. Mostly on saturation plugins or analog emulations. In a real world situation, I would not oversample a linear noise gate or any plugin that does not produce harmonics, saturation or any type of analog non-linearity. What would be the point? I wasn't originally using a noise gate plugin. I was originally using a channel strip plugin that had a noise gate (Scheps Omni Channel). The Scheps Omni Channel has the ability to produce harmonics and saturation. It also produces audible aliasing. The basic noise gate was used to simplify things. To help illustrate what was happening. The point of my post was to ask whether or not this was the intended behavior. I'm not going to get into a debate on whether high project sample rates make an audible difference. Or whether oversampling plugins is worth it. I thought this area of the forum was for providing feedback and feature requests. I didn't realize that it was a place to also have people tell you that you are wrong for even providing such feedback or feature requests. I've provided feedback and a feature request. That's all I came here for.

I'm not sure if what I've stumbled upon is expected behavior from the software or not. In testing the upsample feature I decided to take a kick drum track and use it to trigger a noise gate on another track. The other track had pink noise on it just for testing purposes. The plugin upsampling was enabled on the noise gate and the upsampling was left on default. When upsampling was disabled everything functioned as expected. As soon as upsampling was enabled the sample rate of the audio being sent to the gate and the resulting audio being let through the gate was very wrong. Here's a link to a video example I put together. You will have to pause the video to read the captions. Here's the link: https://youtu.be/CfMU93SCigU So far, other than this odd behavior, everything is working wonderfully.

Scook.... YOU RULE!!!

I know that there's currently built in 2X upsampling on plugins that can be enabled, and that's awesome. I don't know of any other DAWs that can do that. I say, take that to the next level!! 4X... 8X.... 16X !!! Computers today can handle those types of computations. Aliasing causes some real nasty sounds to come out of the speakers. Having the ability to oversample (upsample) the plugins to these levels would put Cakewalk head and shoulders above the rest (at least to my knowledge). I prefer upsampling my plugins over setting a high sample rate for the project. Upsampling plugins instead of a high sample rate on the project keeps audio file sizes wayyyyyyy down, keep the audio quality as good as digital can get it. C'mon Noel, make it happen!!!!

Noel Borthwick, any ideas?

Unlike Reaper, Cakewalk only lists the plugin once, so I'm unable to exclude the V11 plugin.

Yeah I did that. The problem is the V11 came with the H-Series bundle and Cakewalk for what ever reason is selecting the V11 plugin. Even though the path of the plugin in the plugin manager shows that it should be specifically grabbing the V12 plugin. Reaper doesn't have this issue, it will let you select either one, V11 or V12. Is there some setting that will allow both versions to be listed in the plugin manager?

A while back I bought Waves Hydrid series of effects, which came with H-Comp. This was installed at V11. I later came across a promotion that allowed me to acquire H-Comp V12. I'm unable to specifically uninstall the V11 version of the plugin as it is part of the Hybrid bundle. When I view the plugin properties in the Plugin Manager it shows that it's accessed from Wave Shell V12. The odd thing is when I insert the plugin on a track it accesses Waves Shell V11. Very strange. One thing to note, in Reaper it lists both versions of the plugin (V11 & V12) and I'm able to select the one I want to insert. In Cakewalk it only lists one version of the plugin, and indicates that it's V12, but when I insert it, it's V11. Anyone have any ideas?

I engineered and mastered the song. Here's a link to the lyric video: https://youtu.be/usdT3LKOoE0 Here's a link to the band's website and facebook page: https://www.facebook.com/somestupidband https://www.somestupidband.com/

What about getting the presets? I can't seem to them. Here's the instructions from the site:

Took a couple times. I had to add it to my cart and then remove it. Then it showed that I had it activated. Who knows.

I followed the instructions, but no luck. Can someone explain how to get it?

Have hi plugins been deemed safe to install. I recall about a year ago his original site was attacked.

I've never heard of Babelson, are they legit??

what is the freebie?

Had to uninstall via the control panel. Did the old shutdown and restart. Reinstalled and presto! It worked.

Yeah same. Then again, it's never worked properly.

It's not bad, but it definitely has a long way to go. The control panel for each band gets in the way. You can't reposition it, or if you can, it's not obvious. There are snaps and pops when bypassing the plugin. It's missing that polish that other plugins have. Needs more work, but good ideas.

If I weren't receiving this plugin for free, I would not purchase it. I have plenty of delays and plugins and can very easy route them in the same manor. Ah well, it's free, I'll take it.

Looks like you need Fat Channel XT. I just went through the whole installation process (without having Fat Channel XT) and nothing shows up in my plugin list. Oh well, I didn't really need these.

Do the require having Fat Channel XT? This from the website: