Proper audio engine: Gapless Audio!

[RichardTownsend]

Honestly, what an idiotic post.

[maggot]

It’s not as easy as programming a beat bro.

[Monotremata]

@dylanmixer

Serious question, how big is your team? From posts like these, it makes it sound like Steinberg is a tiny indie studio doing their best to balance fixes and features in their basement, not makers of a major professional DAW and a sub company of Yamaha. I’d really like to understand why development for Cubase is so mind bogglingly slow and that asking for a feature takes years to acknowledge, years to implement, and takes development away from other areas. How many people work on the Cubase team? 4?

Don’t get me wrong, I do appreciate you responding and explaining, but usually your explainations leave me more confused. Why don’t you have enough resources to get any meaningful amount of work done in any sort of reasonable time frame?

Well, if it’s so easy, go write your own DAW and show the world how it’s done! And don’t forget to plan everything 25 years ahead of time, like platform changes, OS updates, user expectation, changes to dev tools, the industry in general, so you can anticipate what the future may bring and you won’t run into any of these silly little annoyances…

[dylanmixer]

Can you explain why? I realize my tone sounded really aggressive, but it wasn’t intended that way. I genuinely don’t know what size team Steinberg operates with. I think that there is a public perception that they are a huge development team, but the language they use on the forums makes them sound much smaller with less resources. I just feel like there is a big gap between community expectations and what seems to actually be practical.

[dylanmixer]

I’m aware, thank you.

[dylanmixer]

Relax, that’s not what I’m saying. I’m actually trying to understand better why development is slow when I feel like it didn’t used to be years ago. It wasn’t intended as an insult.

[skijumptoes]

@dylanmixer

I’m actually trying to understand better why development is slow when I feel like it didn’t used to be years ago.

Is it not like asking why a larger house takes longer to paint? I don’t know what kind of timeframe you’re comparing here.

[dynamaltee]

Dev is surely not slow, when I compare what they add with every update compared to some other DAWs. It is not the number of lines in the release notes, but the complexity of the added ot fixed feature. Developing and maintaining a C++ codebase for a complex real-time-audio processing system for sure is a little different from a “Hello Word” in Python. Also setting the right priorities is crucial.

For me gapless audio would be very nice to have in Cubase, but it is definitely not a must have.

[jjitter]

Definitely need a gapless engine. Huge +1

[Rapollo]

+1
In increasingly fast and intense sessions, this small aspect actually really affects the fluidity of intense mix sessions to the point I’ve had clients asking if the computers okay (since Cubase is in the minority with this, potentially the last one?), and I have to explain its just Cubase, and is actually pushing me to other DAWs like Logic and Pro Tools despite Cubase being my personal first choice . The gapless effects when adding tracks or plugins during playback are clearly felt on both my Windows and Apple machines as of May 2023.

[lucasm]

+1 in 2024

[Italyuser]

My big +1!!!

[mozizo]

same comment Forward in the future ----->>>> +1 in 2032 !

[qaplah1]

Imagine how many users of other DAW software would consider switching to Cubase if this were properly addressed. That should be a strong economic motivator for Steinberg to work this out.

[IVT]

Hi Sir, can we get a 2 year update on this?

I do like some of the features you’ve implemented since you last posted, but few if any would improve workflow as much as gapless audio, something which most other DAWs have had no trouble prioritising.

[UK.SANTS]

+100k

[cbm1]

+1
While it wasn’t high on my list in the past, it has become the main pain point in cubase for me now.

[JoanH]

@Ashkan_Aref

Just imagine how humiliated I’ve got when I inserted a plugin during an orchestral recording session

LOL… why on earth do you want to insert a plugin during an orchestral recording?

[Edited - inappropriate content]

[JoanH]

One note about Logic. Don’t know why some people here refers to Logic as “gapless”, and I don’t know S1 or other DAWs refered in this post (havn’t used protools in last 10 years). Logic is awful in terms of working while playback is running. When you bypass a plugin while playing back it messes out all the delay compensation, same thing as deactivating the plugin without compensating the latency change. So, if you are not aware of this, the result is listening absolutely out of phase tracks. Keep working without stopping the playback and your ears will get very confused if you dont’ know your tools. PDC is a very serious thing to deal with, and Logic only updates the delay compensation when playback is stopped… even with a simple plugin bypass.

Peace and love.

[Trensharo]

@JoanH

PDC is a very serious thing to deal with, and Logic only updates the delay compensation when playback is stopped… even with a simple plugin bypass.

The fact that “PDC is a very serious thing to deal with” is likely why they intentionally only updated it when playback is stopped, because doing it incorrectly while the session is playing (or worse, recording) is a bigger risk and inconvenience than the current design.