WaveRider Support FAQ
After installing Wave Rider, you will have to set Pro Tools peripherals for Wave Rider operation.
Go to Setup–>Peripherals–>Midi Controllers. Choose HUI as type and select Wave Rider ports for both send to and receive from.
Go to tips section to see a video of it.
Windows users, please make sure to choose port Wave Rider Ch x-x(snd) under “Receive From” and Wave Rider Ch x-x(rcv) under “Send To”.
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.
There is a known iLok issue where if you already have a Cloud session open, the license may activate there, even if the Cloud session is open elsewhere. To prevent this, please close the existing Cloud session within iLok license manager before starting your DAW. (in iLok license manager Menu -> File -> Close Cloud Session)
If you encountered this, and you’re getting “Attempt to start the trial too many times…” error, then please click the “Activate” button instead of “Try”. And on the next window where you are asked to enter an activation code, click “No” and then proceed to enter your iLok credentials and initiate a Cloud session with your Trial license.
If you get this message but WaveRider works as expected, just tick the “Don’t Show this message again” box in the message window. It won’t bother you again, unless you clear PT preferences.
Yes, this is a known little issue. But fortunately very easy to get over. Upon playback, the faders will go to 0.
Also, putting “park on silence” on and setting a slow release will get over this issue and give you better tracking for material that is made of broken regions (checker-boarded).
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.
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.
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.
If you have Icon, Pro Control, or C24), Wave Rider will only control the first 8 tracks that are loaded on the controller. Changing the loaded tracks of this bank will also affect what track WR will control. WR will treat the first track of this bank as channel 1, no matter what the actual track number in Pro Tools is.
If you have a 002, 003 series controller, Wave Rider will control the tracks immediately after the 8 tracks that are loaded on the controller.
If you have a Eucon enabled controller, Wave Rider’s functionality won’t be affected. You can enable all 32 channels in the MIDI controller section, and banking on the Eucon controller will not change WR track numbering.
Command 8 can’t be active concurrently with Wave Rider.
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.
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.
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.
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.