Therein lies the problem, and why I created this thread – if the DAW didn’t try to close down the WavesHeadTracker_圆4.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.
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. This worked as I had hoped it would – until I closed the DAW. I realized that I could just launch a dedicated instance of WavesHeadTracker_圆4.exe manually. 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.īeing a User 2, I wanted to come up with a solution to the problem. 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. 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.
There are generally two types of users who would prefer this option: 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.