Cubase 8 Pro was not ready for public release

Cubase
61

I disagree completely. Cubase8 is far from “SOLID” The documentation is in the "Issues, collected issues, and solved issues forums. The sad thing is there are a lot of issues that should be moved to “collected” but they have not done it for some unknown reason. The following has nothing to do with anyones computer build or components.

  1. MCU doesn’t work. Period. It didn’t work with the introduction of C7 either. Can you attribute that to “Newish, few teething problems?” I attribute that to rushing out a product before Christmas. I doubt many professional users with external hardware using multiple monitors would agree with you.

  2. History window doesn’t work any longer with up/down arrows anymore. The function has been broken. How difficult is it to confirm this? It takes just seconds to open the window and press either the up or down arrow. Unfortunately the usual reply to this will be:

  3. I don’t use the history window (implies if you don’t use it it’s not important)
    2 use a work-around (you could end up going back to a prior release or even different DAW with that concept)

  4. why did you buy 8.0 and not wait until 8.5 you should know better. (see prior post)

Did I miss any other excuses?

Those are just a couple “bug or two” as you say, that personally effect me. I could list dozens more but that’s not the point.

62

Exactly my sentiment. And the best way to get something done about it is to discuss it, and then come to an agreement on how to do something about it. I for one have no issue taking consolidated feedback and give Steinberg a call. (i.e. turning this discussion into action), and I’m sure another bunch of folks would gladly help with this.

Same here, there’s some really sweet stuff in 8, and if it would work great, then this release wouldn’t feel hurried. But the tagged-on menu bar (Windows), the way the VCA faders were implemented, issues like MCU, plugin menus for some very widely used 3rd party plugins not showing… all these could have been avoided through better QA and/or UAT (and probably also with an improved feedback cycle in general). And then it would indeed have made that great dot zero release.

I for one can’t wait until it works as it should! In the areas I love Cubase for, it’s so far ahead of the rest that I’d gladly wait a bit. However, for the benefit of Yamaha/Steinberg, it would be good if we as customers could provide them with solid feedback on how this unofficial paying beta-testing program doesn’t work well (for some). If the majority of customers is fine with a release being stable only after 6 months, and Steinberg decides that’s good enough then so be it, I’m just not part of that majority, and would prefer to work towards a better situation.

Regards,

characterstudios

63

Great intentions, but that won’t work, trust me. You have to know Steinberg and their history.

Also, you have to be very careful about threads like this so they don’t deteriorate between the resurrected Cubase fan-boys and obnoxious or irrational complainers…which will contain everyone elses comments in the middle. These threads often get locked, moved to the “lounge” or deleted, and the users get banned then go to Cubase8 gearslutz and carry on… :mrgreen:

It seems to happen with every new Cubase release.

64

Understood, and aware, but still wouldn’t mind trying. The best customer is the one that’s critical with the goal to move forward.

So true. Forums are not for serious business. Anyway, my offer stands, so if anyone feels like discussing this in a different way, send me a PM, and I’m sure we’ll be able to organize something.

Regards,

characterstudios

65

I wonder how anyone gets anything done at all. Must be hell. Good luck.

66

Pstssssssssssssssssssssssssssssss
That’s the air escaping from my balloon.

67

Was wondering the same about you too, after all it’s you that takes the time to troll a discussion that you clearly have no intention to add any value to.

Nonetheless, good luck to you too!

Regards,

characterstudios

68

Perhaps,

but I first started hearing/reading that: ‘people will start voting with their wallet’
thang when SX1 was released and now seven versions later, here we are at C8.

When is this voting gonna start?

{‘-’}

69

The golden question!

I guess because for many there is no better alternative? In other words Cubase is the best tool compared to the competition?

70

I disagree completely. I’ve been using Cubase on mac since the mid 90s. Cubase Pro 8 is absolutely the most stable, mature and welcome update yet. I work in tv full time with crazy deadlines and am lovin’ C8. No issues here at all. Great work on this one Steinberg!

71

The people having all the problems are the ones who don’t use a mac.

72

Not true, there are plenty happy PC users as well. (Myself included) I’ve seen issues posted by some from both sets of users though.

73

It is a fact that the MAC has less model and component variety and thus it is easier to get software to work there. It is also my own experience after having 10 years with different PCs and now 4 years with MAC. I currently work on both platforms as Microsoft office is best on PC and Cubase behaves best on MAC. I know there are opposite experiences (confirmed in this forum many times), but all the feedback from professionals I have from both music business and design business report of less trouble with software on MAC than PC. The total environment counts. OS, discs and which software you place on which discs also seem important. The more complex it gets, the more the advantage of a more unified component world of the MAC seems to come into play.

74

Let me help you there:

Be assured that our opinion on the quality of this release will not be adjusted by the fact that it works fine for you

Sounds pretty irritated to me.

So to be clear. A thread is started boldly stating (not questioning) that C8 was not ready for public release. Some loudly agree. However, when it is pointed out that many are getting on with it fine - yes, very much including those of us who use it for a living - this is of no relevance whatsoever. Indeed, we are to “be assured” of its irrelvance. Ditto when you compare with competitors at 10x the price yet far worse performance, this is also brushed aside as irrelevant.

It’s the definitive point at which this thread demonstrates it has no value. Regardless of what facts and opinions are considered, it will not matter. Some folks here want a jolly good rant, and they’re going to have it, inconvenient facts be dammned, and shame on us for spoiling that particular ranty party. As for the idea that now the thread should about turn and become more cerebral and analytical - perhaps starting with a less infantile subject header might be a thought.

I would love nothing more than to spend 2 hours going through everything else point by point (as we all know there’s nothing more intellectually stimulating that reading forum arguments that spiral into ever decreasing circles of petulance after all), but I really must be off to earn that living.

75

Indeed, but that doesn’t mean Mac users have no issues. The fact is some clearly are. Some users from both platforms are having issues.

76

Yes Indeed! And the fact it being fewer that reported problems with MAC as opposed to Win on this forum cannot be taken into credit either as there are fewer MACs around. However the fact still remains that due to lesser component variety software companies have less problems adapting to MAC. And to me it was going from hell to heaven when I bought MAC for Cubase. But as mentioned I have kept my PCs for Office as the GUI is better on PC for those programs.

77

Interesting topic. I disagree that this release is too early for public release based on the following:

I make a difference between two releases in terms of what can be expected from it.

FIrst thing is that before they release a new version with new functionalities, they finish (to a certain level, but quite high) the previous release. That is 7.5, and that version is under any condition available on the system since licenses are working top-down. The mature version should imho be the version to be used in live or in pro surroundings.

At the same time there is an anual pressure to release new functionalities on time. (look back on how many questions there were for a new release at the end of 2014) And what follows is an x.0 release on schedule. It has been tested since august 2014 by a team of beta testers. (not me)

Debugging this completely with use cases like is being done in a professional environment is virtually impossible, since documenting this would take up thousands and thousands of use cases. No single company has that kind of resources available. And releasing it to a bunch of normal users as beta testers without having the proper feedback line setup is also not an option since the guys who do the programming are most of the times not end-users themselves and beta testing without a proper schedule and documentation is very inefficient.

It could be an option if improving the testcycle would be a requirement, to do a release to a “wider” user base before doing the final public release for some months. But that is on the other hand a killer for the release schedule that in fact is quite strict nowadays. (every year something new) So they do a release, imho, that is functional, based on a certain amount of use cases, and then it’s release time.

A release is premature if there are still critical malfunctions. If that is still present in a release, that is a bad. Generic things like crashes, blue screens, startup problems, and other unwanted severe bugs may not be present in an x.0 release. I think with version 8.0 there were no real critical bugs. The biggest i was aware of were the incompabilities on windows systems with Always on top and the new GUI. That was quite severe in my opinion, but that was also fixed quite fast in a 8.05 release. (but they were windows only (and tells something about what kind of machines the beta-testers are using))

Bugs that are critical under user-specific conditions are not crititcal in a generic way, and if they are traced before the release date is thus heavily dependend on the fact that the guys who design the use cases for beta-testing are aware of them and if they were listed as a possible use case.

Best thing to do with those bugs that are still there is to get them documented as quick as possible, so that the program can be finetuned.

So for me: version 7.5 does its job and everything i need is recorded and present in 7.5 and needs no change. That’s fine.
At the same time i am working a lot in the new version 8, bugs included, and i’m using this “free” time to adapting myself to the new workflow that has been introduced. For me it will take several months before everything is fully setup, but hey: i give version 8 a big 10 in terms of new workflow and new functionalities. I will be able to do a lot more with just the same equipment, and that’s a good thing.
Once this release is going to it’s mature state (probably before the end of this year), i’m going to have one hell of a good DAW with excellent workflow.

Meanwhile, 7.5 will do “the job”.

FWIW,
kind regards,
R.

78

Maybe this is the public beta for Nuendo 7 :slight_smile:

79

:mrgreen: :mrgreen:

80

I like Cubase PRO 8 overall but some bugs are way to simple not to been found by a simple BETA test team.
It took me less then 10-20 minutes to recognized some basic major problems that were wrong in Cubase PRO 8.0.0.

Example of problems.

  1. Cubase PRO 8 lock up the taskbar completely.

  2. Can’t minimize the project window.

  3. VCA faders don’t save state. (Still don’t).

  4. Select one channel that belongs to a VCA fader-group, highlight and select all channels in mixer view. (Still haven’t been addressed)

  5. VCA and “link” “key commands” are broken. (Still broken)

  6. Rec button doesn’t work working with VCA fader-group. It set record-mode on all channels that belong to same VCA-group.


    So the question is, either Steinberg hasn’t BETA test the new product at all or the BETA Testers are to incompetent to discover or recognize basic problems? Hire me as a BETA tester in the future are one of the solutions.

Best Regards
Freddie