Thanks Steiny it’s really is nice to know that you are trying to do better .I must say I could not do the job of updating Cubase for fear of a backlash from the customers of Cubase even though you are trying to improve the program for us , thanks again .
Call me sensitive, but that remark upset me. Perhaps you need to realise that your sense of humour isn’t everyone’s, especially if they have suffered personal tragedy. You could have expressed your frustration differently.
I didn’t mean to hurt you. I’m sorry.
But this is the internet, man, and this is the forum where many upset and angry guys come to complain. You should be prepared to see all sorts of comments here and not to take everything so personal.
Update went smoothly here although AA’s Nebula4 VST3 still doesn’t show up (it was fine in C 9.5.35) at all although N4 VST2 is fine and I get by with that, no big deal really.
Both versions do show up in WaveLab 9.5.35.
For the people who say loading FX chain presets works are these being made in new songs or old ones created in 9.5.4? I’m still having issues loading presets that I have saved there. I’m loading the old project, saving the preset, and then trying to open in a new project. So the presets are being made in 9.5.41 but the original project was made in 9.5.4.
I have a couple suggestions that might help. I work on code that gets rolled out to millions of users on a regular basis, it never goes off without a hitch, we have to support Win XP through Win 10.
Institute an alpha/beta program, even for maintenance releases. This will help you find the stuff that QA can’t. You have a lot of loyal customers who would love to have a chance to help you make Cubase better. We all like to play with shiny new things before everyone else does, so there’s that.
Allow for parallel installs/updates. If an update breaks a customers system, they’re not stuck trying to figure out how to undo it and they won’t have downtime trying to do so. The stuff you would need to copy from the base is not that big, so it should be doable. Parallel updates also allow you to validate the updater, can you roll it back?
I have a FrankenDAW and almost every commonly used plugin, I would have no problem with testing releases as long as my main production environment remains untouched and stable.
These are pretty cheap solutions and they should allow you to crowdsource some of your QA, we all want you to succeed.