Issue forum streamlined

Hi all,

We have decided to reduce the complexity of this dedicated issue forum. We will continue to collect your bug reports, but there will be no managed “collected” or “closed” sub-forums anymore.

The process to align these forums, the beta forum reports, our internal development database and documents like the version history needed to be streamlined in order to ensure an efficient support service to our customers.

From now on bug reports will directly be transferred into our internal developer database (when confirmed) and “solved issues” will only be communicated in the dedicated version history document that we are releasing with the maintenance updates.

Two real-world scenarios:

  1. Prospective buyer doing their pre-purchase due diligence - they review the bug list, and are wondering which bugs are real, vs. (for example) unhinged rantings of users who don’t know they have system-specific difficulties.

  2. Current user with difficulty - they’d like to know if their problem is due to a Steinberg-confirmed bug, or whether it’s worth their time and effort to continue to troubleshoot.

These are common scenarios, the old system helped them come to conclusions. How does this new arrangement help them?

In what situation is this new arrangement better for users?

You never release a list of bug fixes from x.5 to x.0 versions, so we have no way of learning what has been fixed, And have to try the new version or wait for user feedback in this forum.

I think is a bad move…or you could start making that list from x.5 to x.0 …it shouldn’t be too hard isn’t it?

In the old system we had a long list of bug reports, a short list of collected issues and a very short list of closed issues.
Every entry in the bug reports forum had to be approved by one of our team members in order avoid any kind of issues that are not caused by the software. The problem was that the process to go through all the bug reports in order to reproduce and validate them, check if they have already been reported by other users (beta tester, internal, etc), enter them in the developer tool and move them to the collected issues subforum was just to time consuming. As a result the issues forum was just not representing the reality since a lot of the issues in the reported bugs forum were already in the developer database, collected issues were already fixed or some of the collected bugs could just not be fixed at all. The situation was just insufficient for both the customers and Steinberg.

We could have made the decision to emphasise more on this issues forum and have a dedicated support agent and quality assurance engineer constantly work in here. But in this case both of them would not be able to improve the regular support to our customers nor the quality of our products.

We really appreciate your reports and we definitely scan this forum and use your reports to improve our software. The entries are still approved by our team members, but we won’t actively manage this forum anymore since we think that we can use our resources more efficiently if we focus on the direct support via the ticketing system and our quality assurance and testing processes.

Hi Matthias, I still don´t believe that this move is beneficial. The long standing bugs in Cubase lead me to think that there is something deeply flawed about the way Steinberg adresses bug fixing. If you only rely on ticketing system, and the issues forum becomes irrelevant an user may think that is doing something wrong and not report a bug or confirm a reported one.

I can´t use the ticketing system because you refer me to the local distributor in my country, do you think that is streamlined?

Also, I want to point out again, the lack of a list of bugs fixed in the x.0 releases. So, we get a lot of forum members (here and other places online) asking “has the xxxx issue been fixed in x.0 release”? And we wait for other users to test and confirm. Again, do you think that this procedure is streamlined or easy for your customers?

These questions are not an attack (sorry if it looks that way), they are geniune concern about the comunication, or lack of, between Steinberg and its customers. An issue that we have been raising for a long time now.

Now you will be not be managing the best way users have to look if the bugs that hinder they workflow are being looked upon or not. I would dearly welcome a dedicated support agent in the forum, so we can have a conversation about the problems with cubase (for example, disable tracks still keeps forgeting assignments, after a lot of updates).

Thanks

With everything getting thrown into one subforum without much organization, the momentum will tend towards confusion. So, it would be really helpful if when they do, they perhaps:

  1. Don’t lock the thread, so as to allow others to bring more information to the OP.
  2. If the reported possible bug has already been reported in another thread, the Steinberg team member consolidate them, so the discussion isn’t spread across multiple threads.
  3. Delete the bug report when it is fixed in a future update, or instead possibly append a “Solved in update X.Y”.




    Thank you for your consideration.

What exactly is the “ticketing system”?

I was a new user from C8.5 and am very dismayed to see that so many of the bugs have been complained out for years sometimes on this forum. Some of them (I have reported them here) are very significant for a professional piece of software, and I’m getting way more frustrated than I’ve been with the other DAWs I’ve used in the past, as far as that is concerned. I can see how people feel like no one is paying attention because there quite a few very major workflow-inhbiting bugs and issues that just don’t see the light of day as far as a fix.

I don’t mean to sit her and complain, but right now I’m incredibly frustrated. I really want to stay with Cubase as a DAW because it’s the best over what I’ve used in the past, but I haven’t experienced this kind of thing before with this amount of years-long bugs and significant issues (I’m not talking about features – I’m talking about actual bugs/issues) with the other DAWs I’ve used.

Please, if I may … this thread was started to describe a new method Steinberg has implemented to list bug reports, confirmed bugs, etc.

If it starts expanding to other things, such as “Cubase has too many bugs …” and the like, then it’s going to be very hard to have a discussion on the actual topic, such as how people feel about the new bug listing system, requests for change etc.

.
.
.

I’d like to say that after a few days of working with this system, where anything to do with bugs is listed in one thread - I find it so difficult and frustrating to locate anything to do with a specific bug that I am ready to give up ever looking for info about bugs again.

It’s like everything that is loose in the house is thrown into one closet - after several months it’s so cluttered no one ever looks in there any more.

Ann I the only one who feels this way?

They did not implement a new method to list bug reports, confirmed bugs etc in the forum. It’s the opposite, that they would no longer do so. Debating the point is an absurd way to pass your time.

If you want to report a bug in the forum, just do it. If you really want your report to count, use your my steinberg account to file a support request with a real repro. There have always been many, many items in the dev’s bug list that did not appear on the forum.

One thing that’s been unclear about the forum is that it’s a user to user forum. But, since Steinberg staff participate, voluntarily, I might add, the expectation that the forum is an official technical support venue has grown.

imo, it’s just as well they got rid of the former structure, since it added to the false expectations, and was never up-to-date. Now support staff has more time to devote to support, and clearly, they are in great need of that.

I’m pretty close to speechless, though I know I shouldn’t be.

What an aggressive-sounding post from moderator to customer!

“Streamlined” (the word used by Steinberg in the title to this post) wouldn’t usually make one think of “not listing reports or confirming bugs”, please excuse my confusion.

Trying to stay on topic - you’re saying that bug reports should be filed as “support requests” via mysteinberg, “if we really want the report to count”.

I’m wondering if I missed that instruction somewhere else, or whether this is the first time Steinberg is telling us to use mysteinberg support requests to report bugs. I’m wondering when did customer filing reports in the bug list become something that “doesn’t count” …

Thank you -

I don’t know if you missed any information, but requests made through the support system that reveal a bug are formally documented and tracked. That’s why they work.

An issue posted here is good, but better yet would be a support ticket with a link to that issue report.

I presume he means the ticket that’s created when you make a support request through the my steinberg website.

I’m trying to figure out the best way to identify and review the Steinberg-confirmed bugs.

Suggestions for how to do that with the streamlined forum?

You could follow the forum posts, and when you see a bug report, do the repro on your system, then report back. That would take care of part of what you’re asking, identifying, and also help the dev team to see that the issue is happening on multiple systems.

The next part doesn’t involve the forum, I’m afraid: You would apply for a job with Steinberg Media Technologies GMBH in Hamburg Germany, as a Quality Assurance engineer. Once you are hired, you will have access to the database they use to track development, and all the intimate knowledge available therein about bugs, reports, future features, and development progress. :wink:

What a great and helpful answer, thank you!

Please forgive me, I didn’t post quite what I wanted to. I’m asking about the old bugs that were identified by Steinberg in the past. The ones that had things like [BON-] , etc. in front of them.

@SteveInChicago
Where to find that Support tickets? In my profile it says
“Individual support for you is provided by one of our Steinberg distributors. Please find a list of distributors on this page”
What the hell, am I have to contact my local store?!!??
Please explain and provide proper instructions for bug reports.

If you’re not in a country where Steinberg or Yamaha provide direct support, you would have to post here or send email to info(at)steinberg.de.

I’m not a Steinberg employee, so please don’t shoot the messenger. Steinberg employees’ names are in blue or red on the forum. I’m green. :slight_smile:

sorry @SteveInChicago
So I’m redirecting my question to @Matthias Quellmann:
Where to find that Support tickets? In my profile it says
“Individual support for you is provided by one of our Steinberg distributors. Please find a list of distributors on this page”
What the hell, am I have to contact my local store?!!??
Please explain and provide proper instructions for bug reports.

I’m Steinberg loyal customer for more than 14 years who pay for each upgrade I believe I deserve to have right to send support tickets.
You sell your product in my country so you have to accept my requests and bug reports.

Wow this is terrible news…
I keep trying to find things to keep me from moving to studio one…
Currently Steinbergs ignorance on console 1 support and now this rubbish! Seems like 9.x was my final upgrade.

This is a bad move if… bugs are not solved but, a really good move on steinberg if it gives them more time to focus and fix the old/current bugs. I better see that long list of fixed bugs when the next update comes along :smiley: