WaveRider v3 will not work on Catalina. We have released v4, which does. This is a paid upgrade from v3.
Even though WaveRider is a 64 bit plugin, the MIDI driver which makes the HUI connection possible was a 32 bit driver. Catalina doesn’t support any 32 bit applications.
In order to fix this, we had to rewrite the MIDI driver and associated plugin components, hence the paid upgrade.
Group: WaveRider Support FAQ
WaveRider controls wrong channel (systems with Eucon)
On some systems with Eucon enabled controllers, WaveRider might control the channels other than the ones assigned (up or down one).
This happens with later versions of Mac OS and Pro Tools with Eucon.
Dragging the affected tracks to a different position in the layout and then putting them back to where they were seems to fix this.
I have a range of compressors and limiters, and their plugin versions. What can WaveRider do better?
Compressors and limiters do one thing: attenuate the signal. For levels below their threshold they simply don’t do anything. You need to squash your signal over the board and use make up gain to achieve an even output level. This colors the sound, and once it’s there it’s there forever. WaveRider rides the faders for gain as well as attenuation so the output level stays consistent without degrading the dynamics of your signal. The best part is you can alter these moves after the fact. Of course WaveRider could be used along with your favorite dynamics processors to achieve ultimate results.
Isn’t this like AGC (Automatic Gain Control)?
Well, you are kind of right. However it doesn’t suck as most AGC circuits do.
WaveRider’s intelligent algorithm maintains the natural dynamic of the signal, keeping quiet parts comparatively quieter than loud parts. AGC circuits have a common characteristic: They will push gain as default and then brick-wall limit the hell out of the signal, creating a pumping artefact. WaveRider won’t do that, it will glide the signal gently to where it needs to go.
What’s WaveRider algorithm based on?
To put it simply, it’s based on Leq (A) weighting. But it gets complicated. Alpha version WaveRider’s algorithm was designed by a genius engineer with a PhD.
But in the studio, it didn’t work that well. It needed some human feel. So we went back to the drawing board and lessened the logic, and put some magic in it.
Ultimately, it evolved into an organic beast that is hard to classify as anything. We like that.
Does WaveRider do LKFS or LUFS ?
No. WaveRider does not utilize the ITU-R BS. 1770 specification, because its algorithm is designed for mixing, not metering. However, WaveRider does make it extremely easy to meet requirements like EBU R-128, ATSC A/85, OP-59, and TR-B32.
I have installed and set up everything right, but I don’t see any automation written on the track.
There could be a few reasons.
1-Make sure you have selected the proper channel number for the track you want to control. Wave Rider requires manual selection of the channel number, it will default to channel “off” when inserted.
2-Make sure you have not suspended automation in Pro Tools, and you have auto enabled Volume controls, and put the track on LATCH mode.
3-Please check out the following question to see the difference in HUI behaviour along with other types of external controllers.
My faders are going nuts, zig-zagging uncontrollably.
Please use the Latch automation mode, and not touch. And make sure no other instant of WR is trying to control the same track number.
I installed WaveRider v4 but I don’t see the MIDI ports
In ProTools menu check Setup > MIDI > Input Devices and make sure all WaveRider ports are checked.
We also found that if you have M-Audio USB Support.plugin or any other 32 bit driver in your MacHD/Library/Audio/MIDI Drivers folder this can be the cause. Simply remove this driver & restart and all is good.
Alternatively, please run the WaveRider installer and tick the box next to WaveRider_32BitDriver when presented. This will install the 32 bit driver that will load the MIDI ports.
It does not look like the automation written by Wave Rider is bang on, it looks like it is a little late.
There are a few of things to watch out for:
- Set your playback engine so that H/W buffer size is 512-1024 samples.
- Make sure there are no DSP plugins before WaveRider.
- Delay compensation should be on if your system supports it.
- WaveRider should be last plugin the chain.