Quote:
# VST3: fix incorrect behavior relating to Waves CLA issue with recent dev builds [p=2110195]
|
I think *maybe* the CLA MH issue is gone. Here's how it went:
- I installed v5.973+dev0319, ran it and loaded the test file. It worked!!!
- Loaded another (real) project containing CLA MH. Worked!
- Closed v5.973+dev0319 to do some tests with other REAPER versions. All OK.
- Then I ran v5.973+dev0319 again, loaded the test file, and ... *POOF* ... REAPER completely – now even without the Runtime Error message – disappears from the face of the screen. Retrying to execute v5.973+dev0319, loading the file ... again: *POOF* ... (AARGH! Not the *POOF*, I hate *POOFs*!)
- So, I re-installed v5.973+dev0319, then restarted Windows. Ran v5.973+dev0319, loaded the test file again. It worked!
- Since, I've tested back and forth, deliberately trying to crash REAPER. But everything reads and loads as expected. Not one *POOF*.
So, hopefully the issue is gone, and the *POOFs* may have had to do with old "rest files" that required a Windows reboot or something. I don't know.
Allow me to add just one more thing (nothing to do with the issue itself):
I’ve been a REAPER-only user since 2008. And it’s times like this when you feel that the developers did this “for me” (OK, not “for me” literally speaking
, rather for all of us) – and within such small time range – that you know that you are dealing with a top, first class company/developer/support/software. Cockos rock!