Update: the developers can reproduce this as well now. We are working on it.
However, for the sake of transparency, it may not make it into the next maintenance update, which is scheduled to be released in December, but rather into the one after that.
But this is all subject to change. Thank you for your patience in advance!
Will this be fixed in a final Cubase 15 patch as well, hopefully?
And if so, is the timeline the same for a 15 patch as a 16, or sooner, or later?
Getting a rush on a 15 patch would be much appreciated.
I don’t have any info on a Cubase 15 patch that might address this issue at this point.
Well, it better soon be, because things like this have an impact on how users perceive Steinberg.
Leaving last version with a feature that is broken, just because the new version was released just several days ago? This doesn’t look good. Some users will may take a note and remember Cubase as a software that cannot be trusted with new features.
While I’m staying with Cubase, because I can’t find equivalent alternative, my perception of Steinberg is already not that great.
I paid for Cubase 14 and 15 updates for Modulators - one of the highlighted features. Those features are not working as advertised. When this will be fixed in C16, that fix should go to previous versions too.
My trust in the new features in the next Cubase updates is really low. Now I’m cautiously taking into a consideration that every new feature introduced in Cubase, will be fully working a few versions later.
I hope that Steinberg can bring back my trust.
Thanks Ed,
I’m hoping as soon as the problem/solution is found, a public hotfix “beta”/test can be released for 15 asap, as I’m assuming, upcoming 16 updates are going to be compiled with more unrelated fixes that will take more time. This would allow 15 users to both test the fix prior to 16 update, and allow 15 users to, if all goes well, complete and start projects as many 15 users aren’t updating to 16 yet and will want to finish their 15 projects before upgrading to 16 (which could be many months down the road).
Thanks again
I’m sure while Cubase 15 is in support the final patch should include this fix. Or am I wrong?
Actually, by the time the patch is released, I will certainly have already switched to C16, like most Steinberg users ![]()
Ugh… It would be an absolutely fantastic winter season if a hotfix was released for 15 in the coming weeks…
Like roll out a ‘Modulator’ only hotfix, and then recompile it with the other 15 fixes in the final patch.
Not to quote myself.
I just feel like there is such a mismatch of user vs developer needs and intent.
Like Steinbergs development agenda doesn’t align with with users needs and users reality. Steinberg seems to stick to very strict timeline and what will be worked on and released and when.
There’s probably good reason for that, like thoroughly testing before compiling and public distribution… But I’m not sure that it’s always to the benefit of Steinberg themselves.
For the user, my logic of releasing 15 first actually makes more sense.
1.) Most people who are using Cubase 16 were users of previous versions in which if working modulators are a dire need they can go back to a modulator hotfixed 15 version while 16 is updated, and then bring their 15 modulator projects forward to 16.
2.) Many people are not updating to 16 yet and or have 15 projects they need to finish. 3.) The users who desperately need this fixed have most of their modulator projects in version 15 project files.
4.) There’s a strong ethics case to be made about fixing things for the users who have already paid for two version updates for modulators, some of whom might not want to update to 16 until they get what they paid for, for them, seeing this get fixed in 16 only forcing them to update is a punch to the gut.
5.) There’s a risk that after waiting so much time and getting a patch, the patch itself creates other problems or doesn’t fix all the problems… Then we wait an indefinite amount of time or it never gets fixed in that version.
I just think Steinberg is so stern on their development itinerary, they don’t see this customer relations perspective. And the moral creative angle - we have projects, artwork, that is dependent on these fixes. Our train with precious goods is stopped with a break in the railway, we’ve paid our dues to use the rail line, but the rail company is building a new line not fixing ours. We’re just sitting in the middle of nowhere, our precious cargo spoiling.
Sorry for the deep analogy.
I think as other users have pointed out, this is a good opportunity to 1.) develop a quick distribution protocol to release public hot fix betas (at user risk), even if just for one fix. 2.) Build rapport and trust with existing users.
I can only speak for myself, but when a developer releases hotfixes, it gives the impression to the user that the developer cares, understands the urgency, and isn’t so overly committed to an internal itinerary over the users creative and professional needs.
@Ed_Doll The software is so good and the people at Steinberg are obviously so talented, but the costumer relations could use some work. I would rather get a early broken hotfix public beta, than no hotfix… Because it shows us that something is happening, you’re trying. Rather than being in indefinite darkness.
I have an entire album of Modulator based creative work i’ve done in Cubase. I hope to finish it and release it soon - besides, I need to in order to make money to buy Steinberg upgrades.
Have you ever considered that this might be a faulty assumption? That the folks at Steinberg actually aren’t talented enough to be able to meet all customer’s demands?
That is funny (the topic of the thread being modulators)! ![]()
No, the folks at Steinberg are talented.
Being a producer and engineer, I work with talented people - but talent is only part of the equation. Many of them are financially inept, mismanage time, and so on. Hence, the need for producers and managers (which sometimes still isn’t enough).
What I’m saying is, the talent is there, but the parameters of exploiting that talent perhaps aren’t optimized. That could be the result of available resources, limited staff numbers, and so on.
I’m not talking about them meeting all customers demands… just mine ![]()
I think some sort of change in development and release/patch structure could, overall benefit everyone - all users and Steinberg.
“oh, there’s a bug there? try this hotfix”. That type of rapid deployment is what I’m talking about. Report a bug, and it’s fixed the week after. Even if this came in the form of a separate install, ie there current version of Cubase is 15.0.4. They would release Cubase 15.0.45b which would install as a completely separate version on the users computer. Thus, it won’t break their working version of 15, and thus there is no need for the user to have to figure out how to rollback if there are problems - they just uninstall, and likewise, do so when 15.0.5 releases.
It would be glorious to have that kind of turn around. I would have no problem installing an entire additional version if it meant I could use modulators next week.
Having to wait months for a fix for something so vital is just not groovy. There’s no groove.