Sorry Fabio I don’t understand. Can you please clarify?
The VST Instruments Development Team is a separate one. But how do they get paid if it’s not from Steinberg? If it is from Steinberg, then aren’t resources i.e money/budgets, being shifted from the team developing Cubase, Nuendo or Wavelab to the VST Development Team?
I realize it could be more complicated than what it looks like on the surface. Maybe Steinberg gets some type of royalties or Halion profits subsidize all the VST’s in Cubase?
Hello Fabio, thanks for the response, don’t take this as a bashing towards you or steinberg, I deeply love cubase and I am making my living out of it. I also like steinberg vsti, even though I don’t use them as much as third party ones.
I don’t know of you have been reading the open plea threads, now it has become somewhat circular, but I wanted to ask you:
-Can you give us a reason as not to engage in some kind of comunication with your customers? A lot of people in that threads is asking for old bugs fixing, but also some kind of info or timeframe…so,
-Is too much to ask for a simple "we think we will have VCA record arm issue, disabled tracks loosing settings, etc. fixed by this or that update"
so we can know you are working in those items (or others) in particular? In case you don’t make it for that update, at least we have some comunication. We are thankful that you are pushing the envelope with new features in every version, but, two flagship features like VCA and disabling tracks have been broken for a year.
We need some dialog Fabio, a little conversation between steinberg an its users, not surveys.
I appreciate the point Fabio, but when I filled out the survey (before reading this thread) I was clear in my comments that I would prefer Steinberg devote more resources to DAWs and less to VSTi’s. While they may be different teams, if we go far enough up the corporate food-chain someone is deciding to invest X resources in Team A, and Y resources in Team B, Since there is no mechanism that allows us to provide feedback to those decision makers, we end up using whatever channels become available. And I’d encourage others to do the same.
That said, it might be unrealistic to expect the VSTi team to recommend that they be downsized based on their own survey results. Reallocated is a better word.
It’s only a guess but I’d say that for various reasons (technical/financial/marketing/whatever), it’s hard to be sure what can be delivered and how long it will take so too much communication can get you into trouble. Look at Avid, talking about the ‘Pro Tools Cloud’ for nearly two years yet it hasn’t been delivered. Then people are crying out ‘Where’s the Cloud you promised us???’.
Steinberg said nothing, but then VST Transit appears. I prefer that than 2 years of talking about it.
Hmm… I don’t know, but I think Steinberg got the message about bug hunting by now.
No need to start the same routine with every survey in my opinion…
And I also think that an DAW is a whole other design/development concept and environment than a VST instrument.
I do not think it is as easy as some people seem to believe here, to pull people from the VST design group out to the DAW design/bug hunting group. That is a whole different discipline, and I guess it takes months -if not years- to get so comfortable with all ins and outs of the DAW to even remotely start on some comfortable level of effective bug hunting. Anybody that has ever worked in a software design environment knows what I am talking about.
So - I get what Fabio is telling here. I really think that this survey is not connected to Cubase itself, and resources will not be “shifted” to (or from) VST instrument design.
I can’t delve into financial stuff, not my duty and happy that way, sorry.
I’ll just say that like in every company, a different product made by a different team generate its own revenues and belongs to a different cost center.
About the communication, that can certainly be improved - I’ll be very straight and realistic.
Yes, I’ve been reading the ‘plea thread(s)’, everyone did. The people in charge replied there, but to address all of the points raised would take a few more people… It has been asked, for example, to be be updated and to communicate about bug fixing and such, sort of a confirmation that Steinberg works on that.
Of course Steinberg does, based on the Forum, mails, phone calls, beta testers, internal testing, QA.
To communicate what’s going on in detail against what is being discussed on the forum is, honestly, not possible. We’re talking about thousands of tasks which you cannot just review reading the title.
Besides that, there is what can be communicated in a responsible manner. To promise a specific fix giving a timeframe is often difficult, as you never know what can happen - i.e. I’m telling you today the ‘silence on automated tracks’ and ‘flickering when using slice/pencil/line tools’ issues are fixed in 8.5.10 (real-world examples ), what if another task breaks it and I promised something not coming?
Rest assured there is a LOT in the works which goes unseen at the moment.
Thanks for the response Fabio, I would like to point out that even though the people in charge responded, they did with a survey that had anything to do with what we were asking. If steinberg is aware that comunication could be improved, why don’t ask the customers what sort of comunication they need…I think is the best approach possible. Then you can decide if it is doable or not.
are the fixes you mentioned coming to cubase 8.0? Or do we have to upgrade to 8.5?
I would like to point that what you are doing here IS comunication, and even if sometimes we can get answers we don’t necessarily like, I appreciate your feedback and responses!.
Similarly, a “Yes, in 8.5.10” … or a “No, but in a later version” … or a “Not quite sure yet” … or even an “Engineers can’t reliably reproduce, but are looking at it” would go a long way towards happiness!
Thanks again for the great communication in this post!!
… what if another task breaks it and I promised something not coming?
I can only speak for myself with certainty, but I suspect many others might agree:
If that situation did come to pass, and then you came back and said something like, “Hey, we were really hoping to get that done like we discussed, but this other task broke it, and it set us back … I’ll let you know when we have a better idea when it will get fixed again.” …
That would be absolutely, completely, totally, and without question … NOT a problem in the least!
There is no perfection expected, I may not be a computer expert but am smart enough to know that “flower” happens in any situation.
So, please don’t feel that if Steinberg found itself in that situation that they would have made things worse! The communication that went on before it would make things so much better!
Those are my bigest issues, if you fix them I would be very happy.
Regarding closing folders I have somewhat found what could be happening, but I am not in the computer now to make a repro report.
In my case It seems that if you have a multi out instrument track in a folder and you unfold the outs of that instruments and then hide all automation it closes the folder.
The weird thing is…if you fold again the outputs of that track it continues closing the folder with the hide automation command.
If you have a template saved in previous versions, and you have 8.5 you should take the tracks of the folders and then put them in new folders and resave, maybe that helps.
No, as Fabio already mentioned the HALion Team has a different cost center, they get paid like every one else these days with an electronic bank transfer, nobody uses checks anymore at least not in Germany.
It is more or less like the team in London that is developing the new scoring software, just a little bit smaller and in Germany.
Even though they are a separate cost center, they still would have an operating budget. In most corporations that budget would be determined by a negotiation between that team’s management and Steinberg corporate managment. At some point Steinberg is making a decision about how much of Steinberg’s operating budget is being allocated to Team HALion vs. Team Cubase etc. Steinberg must allocate its limited resources to different teams based on a set of corporate priorities. It is those priorities, which drive budget decisions, which are being questioned. Being a cost center is not very relevant to the actuall issue. A cost center is only an accounting mechanism used to facilitate achieving a set of corporate goals. It is these goals and priorities which are being questioned.
Been very busy, I see this has gone a long way in the meanwhile.
I wanted to reply to a couple questions for a few days now.
‘Collected Issues’ means the issue is reported in our internal tracking system, it is known and being worked on / on schedule / being discussed or planned.
There are many more collected tasks than those listed in the forum. Also, not all threads are moved to ‘collected’, even if actually collected (reasons may vary).
About the specific issues you asked for above:
The first one (BON-14128) should fit in 8.5.20. There is no ‘fix version’ set for the other two, but both are active tasks.
Yes, some fixes coming with 8.5.10 will also apply to 8.0.40 (automation, VCA, performance, etc.)
There are some important tasks related to the consistency of the performance across systems (starting from the next release already). This should benefit in particular the users having performance problems and those who witness a lesser performance compared to the previous version(s). All users should see an improvement, though.
That’s it, pick the one you were waiting for, if any
2&3 are big bugs, I would add fix visibility presets so that adding new tracks in visibility A , don’t show up across all saved visibilities making this feature useless for big projects. And improve performance efficiency.
True, we didn’t ask for a vst survey, 3rd party vst’s are most of the time superior, I would support a modular approach to buying cubase.
And I don’t think it’s a resource issue, it’s not our place to know that , I think it’s engineering design flaw starting with the mixer redesign whereby the bugs slowly took over, and efficiency decreased, the engine simply can’t efficiently run the interface and support the tools the new features offer. Just look at the performance issue threads.
Finally lets go easy on the moderators, I doubt they set policy nor are software engineers by day.