How much longer do we have to wait for the Cubase 14 update to be released??? It’s very annoying to work with 2 versions. I guess they are waiting to release Nuendo 14, which when the problems appear again, they will tell you that they are in the middle of a release, and that their priority is the new product…
1 Like
Hi,
No one is allowed to say the release date before the official announcement.
1 Like
My guess is that it will come out around the same time as Nuendo 14, which means sometime this month.
Well ,they could have been released already, or it comes loaded with improvements (which I don’t think, because it doesn’t usually happen)
1 Like
Maybe the person at Steinberg who counts down the countdown could do a livestream to keep us up to date on when the countdown is approaching ZERO. 
what problems?
One of them is the Midi remote. For me the most serious one is cleaning the pool sometimes crashes Cubase.
Steinberg SKI remote sometimes crashes Cubase, and several have been reported.
2 Likes
Sounds to me then that you’re not really asking in your original post when the “next” CB maintenance is slated…
…what you’re really asking is if/when there will be fixes for the bugs you experience (which not everyone experiences)…
Lemme find the crystal ball to check 
I’ve had nothing but problems with MIDI remote and my Yamaha Montage in plugin control mode: it filters SysEx in weird, unexpected ways, often rendering the 8 knobs on the Montage unusable.
I find it obnoxiously fiddly and cumbersome. I don’t want to be designing UIs full of virtual knobs. I don’t care about that at all! All in the world I want is to be able to reliably, instantly bind MIDI CCs to virtual instruments and effects (that support MIDI learn).
I also really don’t understand why 8 is the number that has been chosen, no more, no less. 8 shall be the number of the quick controls, not 6, not 7, unless thou then proceed to 8. 9 is right out.
It’s stupid: if I want to bind cutoff, resonance, filter EG amount, and two envelopes worth of ADSR, I can’t do it. Because 8 shall be the number.
I will never, ever understand why these companies think they can arbitrarily come up with conventions and try to enforce them globally that are just inadequate for certain, valid workflows. I spend so much time and energy trying to work around them just so I have a comfortable creative environment against which I can develop muscle memory. It’s a travesty.
I haven’t had any such annoying problems until now (v14) and I had to install previous versions to be able to continue and solve the problem (because in the previous one I don’t have such problems, or I can live with them)
I love Cubase, and it’s the only software I’ve bothered to learn how to use.
As a customer who updates it with each release I hope that the problems are solved as soon as possible, and I don’t like that the forum is more full of problems and feature requests that don’t arrive, than of the benefits that this great DAW has (because I really believe that it is the best)
1 Like
I had asked a clear question about MIDI Remote problems, which was about projects from Cubase 13 causing problems with MIDI Remote in Cubase 14. Unfortunately, I didn’t get an answer. I therefore assume that these problems will not be solved with a new Cubase update.
It’s what always happens… sadly. It’s easier to say nothing than to say what you don’t want to hear. As time goes by I’ve noticed that the Cubase forum has less activity from those responsible (hopefully Martin Jirsak appears, at least) and I also know that support tickets seem to go unanswered… so I don’t know what to think…
Yes.
I actually could live with the designing a virtual representation of my controller if it would stay active and unchanged when I power down.
But it doesn’t, and recreating that every time is not for me.
Nevermind.
8 is the number for historical and technical reasons and because it’s 2³.
In the old analog days, consoles were being made by buckets of 8 channels because it was the optimal number for summing. So buckets of 8 were summed together and then theses signals were summed together again.
Most controllers will have 8 encoders or 8 faders because
1- people are used to multiples of 8.
2- electronic chips allow for 8 faders/encoders/pots. Having less would be a waste of resources, more would be more expensive.
So, when the VAST majority of controllers have sets of 8 knobs, it makes sense to have 8 QC. De
1 Like
My point is that we shouldn’t be bound to history here. They finally relaxed the number of inserts for obviously good reasons, but even then there was pushback which absolutely blew my mind.
I know the history, but it’s no longer relevant, or shouldn’t be. Companies like Ableton and Bitwig increasingly have the right idea with the Modulators without limits, etc. This is the future: arbitrary, conventional restrictions are the past and are no longer necessary for any technical reason.
I believe the industry should move forward and embrace novel, futuristic ways of doing things. I even believe ML should be embraced and used to get deep insight into individual systems. Much like gene therapy is the wave of the future in medicine, it should eventually be possible to automate bespoke solutions for bespoke systems, reliably. In other words, agents that can see deep into your PC and find out exactly what threads are competing and whether some have been given priority that they should never have had and automatically trace this to a specific service or device, name it, catalog it, perhaps even automatically reduce its priority or even disable it.
In 5-10 years, this will be the norm: self-healing operating systems that fight digital entropy all on their own, just as living things fight analog entropy in the biological world via exercise, play, and any number of activities. We’re rapidly moving into a new world and it’s time for the audio industry to start keeping up: the whole goal should be to make musicmaking fun again for the largest number of individuals possible, and this means getting the technical stuff out of our way so we can achieve and sustain flow states. So we can play again. It’s been a long time since I’ve felt that way, because my experience of the current state of the industry is that it’s prioritizing the wrong things and sacrificing stability and performance. I know not everyone shares this experience and I’m happy for them, but I’m far from the only one.
Hi,
14.0.20 has been released.
2 Likes