Sorry if you feel offended in any way because that was not my intention. Of course I encountered issues in the past and had to sort them out but also with other software this happens. But I’m just not sure that you can look into the future and know that it will happen again to me? Anyway, shit happens all the time so it will most probably won’t be the last?
I agree that Cubase is not the most stable software in the world and it’s in a constant state of beta but it always has been and it probably always will be. That’s how Steinberg seems to attend to his business so that’s nothing new. The Extreme/Xeon bug is something they should have detected earlier and frankly I’m surprise it didn’t surface much earlier. You don’t have to run legacy programs. it’s a choice you make and that hardly Steinberg’s responsibility! I know of people that would like to run a 16 bit plugins in Photoshop on 64 bit windows 10 machine because for years they’ve been so very attached to this, but is Adobe to blame if it doesn’t work? Lots of people went haywire when Steinberg announced the Plugin-Sentinel so they couldn’t run their 32 but plugins anymore but that was a choice Steinberg made to enhance the stability. By now most people have solved this by either running something like J-bridge or look for alternatives. You present yourself as a high profile user with a very powerful and complicated setup so why bother with this forum? You’ll have a different route to get support anyway. No need to mingle amongst us simple souls with our pretty modest machines and simple setups?
I believe I already stated that it’s impossible to predict how any given setup will behave with a new update. I do think that most bugs that appear within the boundaries of Steinberg’s own applications should not be as high as they have been in the latest versions. I mean something like instrument panels not working in C9 is something they could have known if they would have tested this. And broken installers and content not being found after an update is at least slobby.
I never said that other people’s problems are by nature due to a lack of knowledge. I just stated that a lot of question asked eventually boil down to this. If you also look on other forums you know what I mean. And it doesn’t matter at all if a question originates from a lack of knowledge. I just think it’s not right if people start to put the blame where it doesn’t belong before they even know what causes the issue.
I fully understand that in a production environment where time is money and you’re dealing with clients you don’t want to take any risk and have to test any change or new update before implementing it in your studio. And I probably didn’t fully appreciate that fact in this context. But I still think this is a ‘general’ forum that tries to provide answers to ‘general’ users. It’s not tailored to or aimed at a specific group of users, be it Joe Average in his little studio on the addict or the big shot producer in his 10 million dollar studio. Everyone can get something out of it. Also remember that registered user here post on a best effort basis and have no commercial benefit in doing so. So I’m only trying to help others with the knowledge I gained over the years but by no means claim to have all the answers.
if you in any way feel that your particular situation is left out of scope then just don’t reply. You can hardly expect me to make an impact analysis for every single type of user that might read posts on this forum. I merely pointed out that most issues mentioned are hardly showstoppers for ‘general’ users. If one thinks some aspects might have more impact on his particular situation then by all means take the necessary actions to test the new update before implementing it in your studio. But please don’t blame me for not fully assessing your particular situation.
