(I have a thread about this in the Computers forum but am not getting very many views so, I thought I would try it here. I didn't know how to move it here or delete the other one. If double posting is not allowed, please Admin, delete one.)
 
New computer = Dell XPS - i7 8700 6 core - 16 gb 2666 RAM - two 2 Tb 7200 RPM hdd's - Windows 10 - Focusrite Saffire Pro 40 & Octapre
When I hit play, I get the spinning blue thing for about a second. 
The first time I set up looping points it runs to the end of the loop and stops for about a second before returning to the start of the loop. This only happens the first time, after that all looping acts normal.
Some (not all) plugins cause gapping when assigning to a track during playback.
While editing tracks, everything is sluggish acting. I'm stumped.
Is this normal behavior for CbB? I am a LONGTIME Sonar user and these behaviors started showing up near the end of Platinum for me (On my old, much lower powered computer). I do not remember any of this happening in earlier versions of Platinum. (BTW, I also have Studio One and, everything works fine on it but, I really prefer to use Cakewalk)
Any thoughts from anyone?

Can you increase your ram? I use 32 gigs with mine.

what driver-mode are you using?

Hi. Which driver mode do you use?
Any plugins in the project that could be causeing the latency with a lookahead function?
Are you up to date with driver updates on your new machine?
That's all I had for now.
All the best.

I am using ASIO.
No, I cannot afford to add RAM at the moment.
As far as I know, I have updated all drivers, programs, plugins, etc.
I will try loading a project with absolutely no plugins and see what happens. As it is, if I toggle off all plugins, it still does it.
Also, LAtencyMon tells me everything is fine for running audio.
Thanks for the suggestions!
The reason I bought this new computer is because this same thing was happening on my old computer which led me to believe it was failing (It was a six year old i5 with half the RAM of this new one). So, now the same problem is still happening on this new machine. Very frustrating.

One thing that can slow project startup is an excessively large "Prepare using nnn Millisecond Buffers"
 
It could also be something about the audio driver.  Try different driver modes and versions of the driver.

RAM is not the issue. My i7-8700 showed up today and I am in the process of installing a better PSU and moving my drives over. It will be a clean Windows 10 Pro 64 bit environment and I'll need to install a bunch of stuff before I can test audio recording in CbB.
 
ASIO should be fine. What you are describing is NOT NORMAL.
Are you testing with a clean empty project?
Also, pay attention to anything scook says.

Rodreb, when I was reading your post I had the sense of my own "Studio One issue". And then I read you also have Studio One. In my case, I had same Sonar behaviour when I run it after I have used Studio One, it's like Studio One has left "something" behind in the background. If I restart windows and do not use Studio One, only Sonar, then it's all fine.
 
Can't help anything more. But thought to post here, maybe it will help to draw your troubleshooting in the right direction. I just learned to not use one DAW after another.

stickman393 - I always listen to scook! No, I am not testing with a clean, empty project. I am testing with recently recorded tracks. I will try with a clean, empty project.
chris.r - Actually, I have not used Studio One on this new computer yet besides just checking to see if this issue was present in it.
scook - I was under the assumption the MIDI settings only affected MIDI. I do not run MIDI at all. I was also under the assumption that ASIO is always the best driver (That seems to be what we are always told.) Of course, I will try these things, though.

"Prepare using nnn Millisecond Buffers" delays the start of project play by the size of the buffer. As a rule a buffer must be full before the data is sent down stream. The default is 250 but many increase the value by 2 to 5x.
 
Generally ASIO is preferred. My suggestion is to determine if there is a driver issue. May even want to try the internal sound chip if it is available.