Hi Ashkan, I apologize for my comment. Seriously. It wasn’t meant to be rude, but it was. I feel very sorry.
I wish you a nice day,
Joan.
(Note for myself: learn more english vocabulary before trying to joke)
1 Like
Exactly, that’s what i meant. Thanks.
Lots of us have learned to stop playback before making routing changes (even to listen a plugin bypass) for that very reason… for years. Not only in cubase. If the technology advanced and nowadays it is possible to do it in a different way, that will be very wellcome obviously. But I’ll keep carefull.
Lots of things cause playback to stutter in Cubendo, not just inserting / removing plugins!
Deleting folder tracks, closing the score window - things that should have absolutely no connection with the audio engine!
It is totally doable - there’s just no will.
Oh, Now I feel bad, I’m so sorry mate 
Have a nice day
2 Likes
Deleting Folder Tracks depends on what’s in those folders and whether or not the contents of the folder are deleted.
Some things are done because of what could possibly happen in that scenario, not what the state of those items are in your specific scenario. There are safeguards built into the implementation.
However, I don’t disagree with the sentiment. It’s clearly possible, as so many other DAWs have accomplished this. There is no reason they shouldn’t be able to get it done.
It doesn’t seem to be a priority, though.
If you search, you will also discover the issues of “gapless” audio including how the other DAWs achieve it.
I agree. Of course I have been using a DAW for many years. Newbies come along, and they want immediacy and no issues.
As far as “theres just no will.” is that a top priority? For myself, I can think of many other issues that are more important. But that is the thing…different user groups that need to be addressed.
Here is what Matthias said over 2 years ago.
It’s all about using financial resources to get the most bang for the buck. I’m pretty sure via a lot of marketing and research, Steinberg knows their market and their different user bases.
As a mater of fact, if enough users were willing to pay say…a 2k initial purchase for Cubase, and $300 annual upgrades, I think we would have gapless…plus a lot more! But the DAW market doesn’t support that. Prosumers are pretty much in the drivers seat…setting the price and feature set.
Others are just along for the ride.
Fwiw, I just made those numbers up out of thin air, but I would pay that plus $300 yearly since I feel that money would be well worth the return. Obviously, there aren’t enough of us that feel that way.
2 Likes
I moved over to Cubase after years on Reaper and Pro Tools. I did notice more hiccups in Cubase if you did stuff while the audio was playing. I responded by pausing the audio before making changes. I haven’t ever felt it was that big of an issue or a dealbreaker. In fact, workflow wise it is probably good for me to pause the track, take stock and then make the change.
2 Likes
I don’t think I’d ever agree with raising the price of something… but yeah.
The teams resources are obviously limited. If I knew we would get double the features and support, I would likely pay double the price.
1 Like
EXACTLY !!
I hate this stupid broken PDC thingy in Logic.
Don´t have a big problem with Cubase´s Audio Gap Engine.
I stop. I insert a plugin. I go on. Since years.
I´m not a EDM loop producer who only can be creative when the cycle runs.
But I understand these big (?) FR - and of course I support it.
5 Likes
I haven’t ready everything in this topic, but it seems the discussion is missing the really cause of this “problem” - ASIO Guard. The way it works in Cubase (and similar systems in other DAWs like S1, Logic or Reaper) is that the tracks which aren’t armed are processed on a much larger buffer, therefore any change in the project that might affect them takes much longer to be reflected or requires flushing of the buffer - in both cases you’re going to get an audible glitch.
Live or Bitwig treat every track as if it was armed, because their clip launchers can change what is being played at any moment, they use devices that randomize MIDI or device parameters, etc. The audio engine therefore cannot predict the future and process it ahead of time, unlike Cubase where most of the project - excepting for armed tracks - can be assumed to be set in stone, so to speak.
This is obviously done for Cubase to be able to handle much bigger projects in terms of track counts and/or number & heaviness of plugins.
Disabling ASIO Guard improves things, but doesn’t solve them because Cubase’s audio engine is simply DESIGNED for different workflow.
4 Likes
The problem comes if they try to ‘keep up’ with rival DAWs where the majority have been adding real-time clip launching features. It then changes the intended workflow of Cubase.
If they ever consider going that route, then they have to build in some kind of ‘live’ mode that the audio engine can engage. It’s an annoyance if you’re using VSTI’s, but it’s a workflow breaker if you’re using external gear.
2 Likes
I’ve no idea how “real-time” are the clip launchers or DP, Logic or ProTools, but I’m looking forward to finding out how it works in Studio One.
From the leaks I’ve seen though, it for example won’t play a new clip you’ve added to currently playing scene until you start the scene again. Which would indicate they didn’t really do it “real-time” and I suspect there’s other concessions made to not have to re-write S1’s Dropout Protection mechanism.
1 Like
Make sure you are using your VOTES.
Adding +1 does nothing except clog up the thread.
USE YOUR VOTES!
This is the 3rd most voted feature/fix/enhancement at this point, that is still pending.
USE YOUR VOTES!
2 Likes
As far as I can guess, the only time when there can be a gap must be :
When you insert a plugin that exceeds the total latency at that time. Because there will be latency added to the sound stream, there will be like a “reset” of audio engine, if you will. Maybe that’s when it’s inevitable.
+10000000000000
Crazy this is still ongoing in 2025
4 Likes
I’ve used pretty much every DAW and never encountered issues with gapless playback.
I get that some feature requests require tradeoffs, but this is just silly. Let the developers worry about tradeoffs, we have decades of posts from Cubase users requesting gapless audio, and zero posts from users of other DAWs complaining about it.
Please, go and search “Ableton PDC” 
There are literally decades of problems with PDC in Live, and these problems often demonstrate themselves as phase issues.
Proper Plugin Delay Compensation and gapless playback when adding/removing plugins to/from signal chain are very hardly achievable at the same time. I dare to say there is no DAW currently at the market which satisfies both those requirements properly. So yes, it is really a choice of trade-offs: Live avoids gaps in playback, Cubase avoids phase issues.
3 Likes
I hear you, but that problem (per Ableton devs themselves) is that Ableton only implements PDC once per track, which can create issues with very long and specifically odered tempo-sync’d plugin chains.
Again, let devs worry about tradeoffs, Ableton is in no way considering removing gapless playback just because of an edge case with a known solution, users would lose their minds if they did because 95% of them never experience any PDC issues.
I have personally had plenty of phase issues in Cubase and I solve them by manually offsetting a track. It’s really not that big of a deal and certainly not a reason to stagnate development.
Year, but it’s “easy” to fix: Just use two independent and simultanous signal pathways when needed. This is also no rocket science. The developers know this for sure.
1 Like
As to phase issues , sure, let it happen while in play mode and better that than break the session vibe with a gap.
The moment stop is pressed, it can be put right automatically as now happens in the dreaded gap..
A much smoother client present workflow.
2 Likes