I know this topic has been discussed several times on this forum, but please bear with me for a moment.
Firstly, let me qualify my critique by pointing out that I am actually a music professional coming up on 20 years experience working on soundtracks and audio design projects for television, film, the web, and the videogame industry. Since the late 90’s, I have been using various Steinberg products in my projects, and have generally been very satisfied with their features and performance; these include Virtual Guitar 1 and 2, Groove Agent, WarpVST, Attack, and of course WaveLab 4, 5, 6, and now 7.
With regards to WaveLab, it has always been my preferred audio editor, even DESPITE that fact that I was (at one time) contacted by Sonic Foundry’s Artist Relations team as an unofficial endorser for Sound Forge (back around version 5, as I recall).
Now, the issue at hand: As many are aware (including Phillipe), many plugin GUI displays are not working properly in Wavelab 7. (I’m on a Mac now.) Specifically, I’ve had issues with PSP Audioware, Waldorf D-Pole, and most importantly, Izotope Ozone 4. As I navigate through my files in WaveLab (or if I render processed audio), the Ozone interface randomly disappears, requiring additional clicks to bring it back. I have seen several posts regarding this and similar issues, along with troubleshooting tips that minimize the issue, but PG’s response has generally been the same. To paraphrase: “Not my problem. Contact the plugin manufacturer.”
Based on the responses I’ve read to that sentiment, I’m sure that many of you share with me a certain level of frustration. As a matter of fact, it is beginning to sour me towards Steinberg software as a whole. First and foremost amongst my frustration is the idea that I have to spend what should be production time solving some sort of software development issue (or posting long messages in the WaveLab forum). Regardless of who’s to blame for this particular issue, I am a musician and sound designer, not an application developer. Contacting the plugin manufacturer is meaningless to me, because I don’t even know what questions to ask them or advice to give. “Dear Izotope: Ozone has displayed correctly in every other Mac and Windows host I’ve used over the past 10 years: SONAR, Logic, Sound Forge, Kore 2, DSP-Quattro, GarageBand, Chainer, Live, and WaveLab 5 and 6, but DOES NOT work correctly in WaveLab 7. Please change your plugin!” I’m sure they’ll get right on that.
Now generally, I’m a pretty agreeable fellow, and I hate to pester and nitpick, but frankly, I’m at my wit’s end. I completely understand that any software development is going to involve certain issues and I highly respect what developers and engineers like Phillipe do. But as an end user, I simply expect the software I paid good money to use to do what it needs to in the manner to which I’ve become accustomed. I don’t care what goes on behind the scenes or in the code as long as the application works properly. WaveLab 7 doesn’t do that yet. The stock reply to “contact the plugin manufacturer” puts the end user in the middle of a conversation between developers about things we either don’t understand or hell, need to even care about, truth be told. If this is the official response from Steinberg regarding issues such as these, I have to tell you… it’s cavalier, and frankly, rude. I’ve invested thousands of dollars. You should treat me better.
So how about this instead? YOU draft a short stock message about this mythical plugin framework that developers are using that isn’t fully compatible with WaveLab 7, using language that those developers will understand and pointing them towards the appropriate corrective action and then post it in this thread; i.e. " is currently not working with the current version of WaveLab 7, due to <reason 1>, <reason 2>, <etc.>"
There, I got you started. Now, YOU fill in the s and s and explain the changes their code requires, speaking developer-to-developer. I will do you the courtesy of filling in the with the name of the plugin that requires the corrective action, and sending the message on your behalf to the appropriate technical support contact at each company whose plugins go haywire in WaveLab.
Let’s see where that gets us.