Windows 10 - please do not upgrade! Discussion

Might have summarised some of the opinions expressed in the thread, but does not necessarily reflect the facts, of which we know few.

Here is some perspective: These DAWs do not list Windows 10 as being compatible/supported on their websites

Pro Tools Pro Tools 11 System Requirements

MOTU Digital Performer http://www.motu.com/products/software/dp/body.html/specs.html

Reaper http://www.reaper.fm/technical.php

I can guarantee that Reaper works on Windows 10. A friend of mine is on Windows 10 also and using Reaper and working flawless for him.

What? Are you trying to ruin the rants? :open_mouth: :open_mouth: :open_mouth: :wink:

Who’d have thought that W10 would be the new object of rabid desire? If this is any portent of things to come, maybe MS should ramp up production of whatever phones they are making, just to placate the rampant hordes.

But just like with Cubase, that it is ‘working’ for some does not mean that it is ‘certified for use’ with W10, which usually requires more thorough systematic testing, and hence a substantive delay while that goes on with the stable release version, regardless of how many pre-release versions have appeared.

The irony of this thread is that Cubase is actually working on Windows 10, according to many of the thread’s respondents, which corresponds to my own experience.

What actually is happening here is that SB alerted their users not to upgrade yet, and many users did so anyway, found that Cubase works, and reported that.

Users who upgraded and stuck with Win 10 are early adopters who can tolerate the issues which have been discussed in this rambling thread. For others, the advice in the original post is good- upgrade when Cubase is ready, according to the engineers.

If I get a moment I’ll clean up the thread, since there is pertinent info in here, but it’s hard to find among 7 pages and counting…

Which is to be expected when some issues are found with a product upon which they know a large % of users rely for livelihood.

I love this thread… it’s like the old wild wild west days… :wink:

I get your point that we are not the only ones certified but, I don’t have Pro Tools, Motu Digital Performer, or Reaper so I could care less. I do have Cubase and deal a lot with Studio One 2. SO is certified and CB is not. So I won’t upgrade until CB is certified. I just don’t want to deal with the possible issues that may come up as stated in Steinberg’s original post and various replies.

Just an observation/opinion…
Based of the title of this thread it is a “discussion” about the Windows 10 - Please do not upgrade post. Not specific to one topic like “I have upgraded and it works good” or the opposite of that. So if the “rant opinions” and the other back/forth “techno opinions” are not part of that discussion then you should delete them all and move all the “I upgraded and it is working or not” posts to the linked topic. That would probably only leave the original OPs post and maybe a few others.

However, the “Replies” to “Views” ratio is pretty high for this topic. I would think the “powers” are learning something from these rants and disagreements. Could prove valuable for future concerns.

Regards :sunglasses:

I fought with several issues (video, vst loading) running cubase on windows 10 and solved them all by running Cubase as an administrator :open_mouth: . In case anybody has an issue, try it.

I tried to run Cubase as administrator, but then I couldn’t drag/drop samples from explorer. Did you try that?

Just a thought.

When Cubase is certified for Windows 10 and there’s still issues, then what? Certification doesn’t mean ‘from this day on, no problems, and even if there are it’s not our fault’. It means ‘we can put a little logo on our box’.

Who’s going to guarantee that new drivers, new Cubase update etc. isn’t going to break your rig? No-one. Never could.

I was a software company Quality Manager. I’ve been there.

Do Steinberg have consultants that will come to your studio and fit Cubase to your situation? Not to my knowledge. And if they did, don’t you think that they would have ‘little requests’ made to them - ‘oh, while you’re here, could you make Cubase do this or that’, which of course wouldn’t be documented anywhere, making future support requests expensive in time and money.

In other words, there isn’t going to be a Nirvana point with Cubase and Windows 10. It’s a moving target. Best you can do is test it on your rig and roll back if it doesn’t work the way you want.

Now, please for the sake of humanity go and make some classy music - if the admins would lock this thread I wouldn’t cry.

Another reason to not jump into W10…

I used to preach the “keep your DAW offline” mantra, then 8 years or so ago, I changed camps. But after reading more about some of these issues, I am chanting once again, DAW offline. When I finally take the 10 challenge, it will be staying offline as much as possible…

The critical thing is not to use W10 Home. With W10 Pro you can hold the updates for a long line - I think a year, is it? Then you can update when ready and not mid-job.

Awesome - thanks for that. Just tried it and it does indeed seem to get rid of the dropouts! Not ideal, but it’ll do until Steinberg update. Own stupid fault for upgrading early - just couldn’t resist being able to play xbox while the wife hogged the TV…

I guess that’s the lesser of two evils. I go to File->Import now to do this. But at least I have video and all my VST’s with no other issues

I am a huge Reaper fan however I had major problems using it on Windows 10. I re-installed my Windows 7 as a direct result of that. So I would be extremely careful about giving out guarantees that something will work. Also worth remembering it is not just the DAW as there are so many other factors as for instance in my case NVidia graphics cards etc.

Which is why extensive regression testing is required to have any level of confidence in making such a claim.

Regression testing involves checking that each possible usage scenario (sequence of actions) can be completed without incident, which, for software as complex as Cubase, can be thousands of person-hours of meticulous and laborious keystrokes and recording of results, though a lot can be done by test-robot software. Of course, any major issues can just bog down the whole process. Also, it is obvious that BOTH the software under test AND the target environment MUST not change for the duration of the whole cycle of testing, otherwise parts must be repeated. But if the changed parts cannot be identified clearly, then it is best to wait until all changes are done before doing any of it at all.

I doubt that ANY person on this forum has spent the time to do anywhere near the level of testing required to make any sort of valid endorsement of a product’s compatibility with W10.

While I understand the issues here, I have been quite scathing about their handling of the Android version of iC Pro. So I would expect that no-one in SB would second such a proposal! :wink:

More like: :laughing: :laughing: :laughing: :laughing:. You have go to be joking! :laughing: :laughing: :laughing: :laughing::laughing: :laughing::laughing:

As a survivor of Windows 95, 98, Me, XP, and to a lesser extent, Windows 7, I have to wonder why Steinberg is getting dumped on for its not being ready on Day One of the launch of Windows 10.

On the positive side, sure it’s great that Microsoft is giving it away - yay! Does that mean that the new version is going to be free of bugs and glitches? Are you serious? Every version of Windows has its share of problems, for reasons I am not qualified to explain. Win10 is obviously no exception; however, as with previous editions, fixes will be available that will make it right as time goes on.

Naturally, with the giveaway, everyone wants to experience what they’ve been teased with over the past several months. I will not claim to be an exception here; however, having finally gotten C8 working, I don’t feel like being a beta tester for either Microsoft OR Steinberg. No money in it. There are quite a few other programs that are currently not compatible with Win10 which have nothing to do with music creation, so I’m content to wait until it all shakes out.

That’s my bit regarding Microsoft. Now, Steinberg, it’s your turn.

I understand that until you have an actual release version of Win10, you can’t do the necessary testing to certify C8’s compatibility. I get that. However, all we have seen so far is a message dated July 28, 2015. No follow-up messages as to what’s going on. C’mon, Steinberg - the reason we use this software is we are geeks - we are all about getting into the details of what makes it all tick. With no news updates, that’s the kind of treatment you give to Grandpa, who’s still convinced that the Internet is just a bunch of tubes. You’ve got to provide better information than “Performance and timing issues.” Why not just say, “Right now, the software sucks.” That’s equally informative, and it might amuse one or two people out there.

I’m willing to enjoy my C8 with Win7 while waiting for a fix. But I sure feel sorry for the poor suckers who threw down $1,700 for Nuendo 7! Let us pray.