Plugin state not saving with Reaper project.

Question

Hi, I am using Waverazor with the current version of Reaper (6.63), and when I save a project with one or more instances of Waverazor and subsequently load it, all of the current plugin state is lost, and it loads the last factory patch I had open instead (in whatever the last project is I was working on).  The plugin shows that it's registered with version 2.6.0.

Answer 1

Yikes, that does sound like a bug and thanks for reporting it!   I am working on a new build for beta (a week or two away) that should fix this issue, and will post here when that is available for testing.   In the meantime I will investigate further, but at this point, this does appear to be a bug...  the issue is that some DAWs will send a Program Number 0 after they send the State Information, which Waverazor is interpreting as a "please load the last patch".   I didn't catch this earlier, because not all DAWs do this.

Cheers!  - Rob

Comments

Hi Rob,
any news on that issue?
Thank you, horst

p.s.: it's affecting not only reaper but Live and Waveform too!

---

Oh, yes, thank you for reminding me to post here.   Yes, this should now be fixed in the latest Beta build.   I haven't had a chance to get everything finished for a release, but this bug does seem to be fixed in v2.6.2 Beta

I have turned on Waverazor Beta access in your MOK account.   For anyone else reading this, if you would like Beta access, just let me know.    The release builds come from Tracktion, but you can download the Beta builds from your My MOK Account ( https://mok.com/account.php )

---

Good morning Rob,
thank you, but the download isn't running. The browser (firefox & edge) is idling and nothing happens.
horst

---

downloads are working, we just tested on several systems.   Please email me offline at info [a] mok.com and we'll go from there

---

Now I have it! I have been a bit too impatient as it took some minutes to get a response from your server.
Everything is fine! Thank you, horst

---

Glad to hear!   Hopefully this problem is now fixed in the beta (my testing indicates it is fixed).   We also have a Discord for discussion, it's pretty quiet at the moment, as it is still in the getting-started phase, but feel free to join if you have further questions about Beta builds:   https://discord.gg/5qjhgmfTcP