Constantly being prompted to update MOK Waverazor
-
GuitarPlayerinNYC GuitarPlayerinNYC https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=453621
- KVRist
- 207 posts since 23 Dec, 2019
Pretty much, in the title.
For over a month, I've been prompted to update Waverazor. I have my setting in the Download Manager to autoinstall, but I've also manually installed as well.
I just noticed that I still have WF versions 10 and 11 still installed - should I uninstall them? I vaguely recall keeping them, because I had some projects in them. At this point, I don't care about them. I am concerned about the tracktion.settings file. I learned that this file is pretty important, and what moved me to join this forum 5 years ago. I'm reluctant to delete those files right now, as I'm dealing with midi controller issues (but unlikely they have an effect on the new controller I had a thread on).
WF Pro 13.5- all other WF instruments are up to date.
Win 11 OS
TIA!
For over a month, I've been prompted to update Waverazor. I have my setting in the Download Manager to autoinstall, but I've also manually installed as well.
I just noticed that I still have WF versions 10 and 11 still installed - should I uninstall them? I vaguely recall keeping them, because I had some projects in them. At this point, I don't care about them. I am concerned about the tracktion.settings file. I learned that this file is pretty important, and what moved me to join this forum 5 years ago. I'm reluctant to delete those files right now, as I'm dealing with midi controller issues (but unlikely they have an effect on the new controller I had a thread on).
WF Pro 13.5- all other WF instruments are up to date.
Win 11 OS
TIA!
- KVRAF
- 4891 posts since 3 Jan, 2003 from Vancouver
I think maybe you've left out some pretty important details, like if you own Waverazor and if the installed version is the latest version. Like, why is what's happening happening and/or why should it not be happening?
You can poke the eye and hide a product, but I don't know if that's what you want to do. I had to do that for Kult because it was just a demo and I decided not to buy it. It kept telling me about updates so I had to hide it.
There is an XML file that keeps track of the downloads. It has a format that's kinda hard to read but if your situation is that you have the latest version installed and the downloader doesn't seem to know about it, you can probably edit the XML file directly. I would be careful with that. The format for software and version number is NAME [pipe] NUMBER, eg. "DownloadManager|1.5.3".
I have lots of old versions of Waveform installed. The only issue I have had with that is WF11 seems to stomp all over the edit previews in WF12 so I never run it. I should probably uninstall it, I guess. But it doesn't harm anything to keep it around. If you're worried about the settings when you uninstall, back up your settings folder first.
You can poke the eye and hide a product, but I don't know if that's what you want to do. I had to do that for Kult because it was just a demo and I decided not to buy it. It kept telling me about updates so I had to hide it.
There is an XML file that keeps track of the downloads. It has a format that's kinda hard to read but if your situation is that you have the latest version installed and the downloader doesn't seem to know about it, you can probably edit the XML file directly. I would be careful with that. The format for software and version number is NAME [pipe] NUMBER, eg. "DownloadManager|1.5.3".
I have lots of old versions of Waveform installed. The only issue I have had with that is WF11 seems to stomp all over the edit previews in WF12 so I never run it. I should probably uninstall it, I guess. But it doesn't harm anything to keep it around. If you're worried about the settings when you uninstall, back up your settings folder first.
Surely there must be consensus by now...
-
- KVRist
- 374 posts since 18 Nov, 2023
In the Download Manager place a right-mouse-button click on the version number for the particular plugin in question. In the appearing pop-up menu you can select to not become informed anymore about that particular plugin to be available in a newer version.
Concerning your old versions of WF, I never tested it myself, but remember to have collected here in the forum the following information:
you can keep the old versions of WF installed, and you can also use them. BUT, be careful which WF version opens which project! If you open your "ProjectMadeWithWF11" with a newer version of WF (WF 12 or WF13), then some configuration in that "ProjectMadeWithWF11" will be updated. You afterwards can not open it with old WF11 no more, because old WF11 does not know how to deal with that changed (updated) configuration.
So, use for "ProjectMadeWithWF11" your old WF11, then export an Archive of it in order to have a copy of it, and then only work with that copy in newer WF12 or WF13.
Concerning your old versions of WF, I never tested it myself, but remember to have collected here in the forum the following information:
you can keep the old versions of WF installed, and you can also use them. BUT, be careful which WF version opens which project! If you open your "ProjectMadeWithWF11" with a newer version of WF (WF 12 or WF13), then some configuration in that "ProjectMadeWithWF11" will be updated. You afterwards can not open it with old WF11 no more, because old WF11 does not know how to deal with that changed (updated) configuration.
So, use for "ProjectMadeWithWF11" your old WF11, then export an Archive of it in order to have a copy of it, and then only work with that copy in newer WF12 or WF13.
Classical guitar --> Line Audio CM4 @ SSL12 --> KDE-Plasma @ Debian-Linux --> Waveform PRO 13.5
-
GuitarPlayerinNYC GuitarPlayerinNYC https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=453621
- KVRist
- Topic Starter
- 207 posts since 23 Dec, 2019
You're right. Sorry.pough wrote: Fri Aug 22, 2025 5:42 pm I think maybe you've left out some pretty important details, like if you own Waverazor and if the installed version is the latest version. Like, why is what's happening happening and/or why should it not be happening?
You can poke the eye and hide a product, but I don't know if that's what you want to do. I had to do that for Kult because it was just a demo and I decided not to buy it. It kept telling me about updates so I had to hide it.
There is an XML file that keeps track of the downloads. It has a format that's kinda hard to read but if your situation is that you have the latest version installed and the downloader doesn't seem to know about it, you can probably edit the XML file directly. I would be careful with that. The format for software and version number is NAME [pipe] NUMBER, eg. "DownloadManager|1.5.3".
I have lots of old versions of Waveform installed. The only issue I have had with that is WF11 seems to stomp all over the edit previews in WF12 so I never run it. I should probably uninstall it, I guess. But it doesn't harm anything to keep it around. If you're worried about the settings when you uninstall, back up your settings folder first.
The version # is 2.8.2 and the vst3 version is the same. It's the LE edition of Waverazor, so I'm guessing it came free/preloaded, when I bought the Pro version of WF.
I don't want to mess around with editing any xml files right now. Things can go south pretty quickly, when you don't know what you're doing.
I've learned that keeping old versions or Tracktion/Waveform can cause problems because of the .settings file. Apparently, that file holds all the info, globally, of EVERYTHING regarding T/WF. It's not really disastrous if you delete it. You just have to re-authrorize WF, and possibly rescan for all your plugins. An uninstall doesn't get rid of the .settings file from all versions you may have- I learned this from my very first thread post, and shoutout to @PeterWiddombe (sp?) for nailing that down for me, 5 years ago. Just giving you a heads up, if you want to drill down to those files. If on Windows, the path is: C:\Users\PWidd\AppData\Roaming\Tracktion 4\Tracktion.settings
I don't absolutely need Waverazor. I'm thinking it's possibly a symptom of other things. I've had some incremental updates to WF13 this year, along with other WF instruments. Since, things can be sluggish. But, it could be anything. I've bought loads of plugins since June, including some Tracktion stuff- I try to support them, since I started with T4 years ago (mostly for recording audio). Now I'm getting deeper into music production/mixing/mastering.
Appreciate your input.
You do not have the required permissions to view the files attached to this post.
-
GuitarPlayerinNYC GuitarPlayerinNYC https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=453621
- KVRist
- Topic Starter
- 207 posts since 23 Dec, 2019
Great tip! I just did that now (after yet another update, and, for the first time, WF informed me a new vst3).talby wrote: Fri Aug 22, 2025 6:54 pm In the Download Manager place a right-mouse-button click on the version number for the particular plugin in question. In the appearing pop-up menu you can select to not become informed anymore about that particular plugin to be available in a newer version.
Concerning your old versions of WF, I never tested it myself, but remember to have collected here in the forum the following information:
you can keep the old versions of WF installed, and you can also use them. BUT, be careful which WF version opens which project! If you open your "ProjectMadeWithWF11" with a newer version of WF (WF 12 or WF13), then some configuration in that "ProjectMadeWithWF11" will be updated. You afterwards can not open it with old WF11 no more, because old WF11 does not know how to deal with that changed (updated) configuration.
So, use for "ProjectMadeWithWF11" your old WF11, then export an Archive of it in order to have a copy of it, and then only work with that copy in newer WF12 or WF13.
And thanks for the additional tip. I made a shortcut for WF13 pinned to my taskbar. I used to get a popup from WF 13 about having a creating a project with older editions.
In my other comment, I gave the path to the .settings file you may be interested in. An uninstall doesn't get rid of that file, necessarily.
Thanks for your insights.
