Antre

Ok, delay is normal in CbB on my notebook. Other DAWs in my notebook - no delay. Dosn't meter how much projects are huge. I will get drop out or audio engine crash or program will say that it can read from disk. That proves my assumptions. Thx

I'm not assuming that. You forgot to quote other pc...And please read again what is my question...Is CbB the only DAW that has playback/stop delay issue ON ANY CONFIGURATION when low on resources? Thats the thing I'm assuming.

OK, so other DAWs are apparently less CPU-HDD-SDD-RAM hungry, but that is not the question I'm asking. Here me, again and thats it from me. Other DAWs plays and stops instantly, eventually after a X tracks with bunch of plugins even on 2048 buf you hit the wall. You get drop outs and audio engine crash but play and stop is instant. So I can freeze tracks or something else...Not frustating at all CbB - I'm working, no delay at beginning of work... continuous work brings increased delay on play and stop which is at some point far more frustrating than hitting the wall. So, this is my experience during the years and my only question from the beginning is - Is CbB in this way different from other DAWs, or I need to check/uncheck some button in pref Everybody can do the test if one wants. You just need CbB and any other DAW. You can do it with old machine with 30 tracks and other DAW, or with super new PC with 1000 tracks and the other DAW. That delay is only thing I'm asking about. I experienced it on diferent configurations, but only in CbB and Sonar. If CbB starts to delay with not enough resources that is, for me, proof that it is different from other DAWs in that behaviour.

My laptop: HP ProBook Intel(R) Core(TM) i5 -3210M CPU @ 2.50GHz RAM 4.00 GB HDD 100 GB Free PC (where I replicate issue with 130 tracks - these 130 tracks are working on MY LAPTOP in OTHER DAWS) AMD Ryzen 7 2700X 8 core RAM 16 GB SSD 80 GB Free I tested both with WASAPI but it is same in my studio with dedicated ASIO

thanks man for your kind words, My test was with 20 unique audio tracks, coppied to 130. and thanks to all suggestions and the people who tested this and prove my point in some degree. During the years on all configurations my work was always like this. This days also. I start to work on a project, say mix a song. I do all the work we enjoy, adding fx, fiddling eq-s and compressors, prochannels modules. I'm all into work and music and at some point something start to bather me. Play/stop delay is here. And please don't tell me that it is my computer, audio card/settings or SSD/HDD because other DAWS are working without this issue. That's the point of my post. I encourage some members with older configuration to test this. People who can replicate this behavior with strong configuration with 160 or more audio tracks are still proving that CbB is only DAW with this issue and can in some scenario with really big projects experience this. I still think that is something unique to CbB. And I would love to maybe find the solution - without changing my hardware setup. Otherwise I will use other DAW as some of you intelligently suggested. Maybe it is prochannel, lets find out. But I tried Harrison Mixbus which have eq/s and compressors on every channel and bus. No issue. Thanks!

Thats nice to see, thanks

Read the post you quoted again - did I mention crying?

And, apparently, my son computer setup...

Maybe, every computer since 2000 and 4 confirugations ago. I remember trying to find same answer on old Sonar forum 10 years ago. It was one guy with same problem but no solution...

Yes, on every configuration, with any driver.

Are you guys understand the TEST i did, because if you UNDERSTAND you will understand the LOGIC in it. I will post both PC specs but that doesn't matter because other DAWS are working. Again: 130 tracks, fresh_first install on other PC Win10 in CbB - delay 130 tracks on MY LAPTOP Win8.1 in OTHER DAWS - no delay both in WASAPI, onboard audio everybody can replicate this, maybe someone will get the same results

Read the test I did with my laptop and w10 gaming Pc

try 130

thats unchecked already