Background: Waves NX plugins are powered by WavesHeadTracker (see image), which runs as a separate process outside of your DAW.
The WavesHeadTracker is, by default, launched upon the initialization of an NX plugin instance (be it loading an existing project or adding it to an existing project.) The good news is that Waves 13 gave users the option to choose whether or not the WavesHeadTracker would be launched in that fashion.
There are generally two types of users who would prefer this option:
- Those who won’t use a Bluetooth or Camera tracker – thus have zero reason to use the WavesHeadTracker.
- Those who wish to manually control the launch and shutdown of the WavesHeadTracker_x64.exe process, as opposed to having the plugin close the instance upon switching projects or exiting the DAW.
The bad news for User 2 is that there is currently no way to tell the plugin to not also close the WavesHeadTracker instance upon exiting. If you’re switching from one project session to another, you will have to reconnect your Bluetooth connection to the NX Tracker, which in theory shouldn’t be a hassle – although it has sadly proven to be for myself and at least one other user. Whether it be having to turn off Bluetooth entirely on the computer, reset the NX Tracker, reconnecting is not the “simple button press” that it ought to be.
Being a User 2, I wanted to come up with a solution to the problem. I realized that I could just launch a dedicated instance of WavesHeadTracker_x64.exe manually. This worked as I had hoped it would – until I closed the DAW. Because there is no option to maintain the active instance of WavesHeadTracker, the DAW automatically assumes that you intended to close it – and with it, your Bluetooth connection.
Therein lies the problem, and why I created this thread – if the DAW didn’t try to close down the WavesHeadTracker_x64.exe process upon exiting, then I would still have an active Bluetooth connection to the tracker, and I could immediately continue my Bluetooth connection into another project. I would simply go to the dropdown box (see point 2 in the bottom image) and select the active instance of the WavesHeadTracker from the dropdown.
The solution I am proposing: Allow the user to choose whether or not they want to automatically close the running instance of WavesHeadTracker_x64.exe upon removing the plugin, switching projects, or exiting the DAW. (see point 3 in the bottom image) This would effectively allow the WavesHeadTracker to run in the background as if it were a service, and not as something that can just be terminated at the beck and call of the DAW.
The workflow for the user would look like
- Start up computer.
- Start up WavesHeadTracker (outside of DAW)
- Start up DAW
- Load project containing an NX plugin or create a new project and add an NX plugin
- In the NX GUI, connect to the WavesHeadTracker instance.
I can’t even begin to explain how much this would help people use NX more efficiently. It is seriously the one thing that has made using NX feel a little clunky for me, as I like to switch between a lot of different projects in my DAW, yet I have to keep juggling the Bluetooth connection upon each switch.
Having the ability to launch a dedicated instance of the WavesHeadTracker outside of the control of the DAW would be a dream come true for usability!
EDIT: Added a clearer demonstration image for what I am proposing
EDIT: Clarified my initial proposal