Ya something like this is often a real PITA for the end-user because you have to make damn sure you don't need to open up the offending plugin/software 6-months down the road when the client wants to do more work or continue on with the project. Otherwise known as, pissing off the client, because your system is now incompatible with their project.
But the real reason it's a PITA is because one of the companies needs to step up and say they need to fix something. I don't often hear that or read anyone admitting to a bug until the next release has been released and I'm reading it in the readme. Meaning I'm working as if it's not going to be fixed, wasting time and jumping through hoops with work-arounds, all the while the party at 'fault' is busy on a fix that I could potentially just hang out with the older software and wait for till it's ready.
Curious to see if anyone has any experienced suggestions on this one. Have you contacted Waves? They are very very good IME with tech support. I had some show-stopper issues that they helped sort a few weeks back. I still have a nagging issue with their licenses not working with multiple projects open, but haven't had the time to provide them with a super-detailed response. Point is, they do help and do respond often within the day. Far better than most tech support I've run across... ;)