I'm hoping someone out there can help me out with a really weird issue I'm having. There are 3 points in my project where a "hiccup glitch" is consistently reoccurring. I see two CPU cores spike on the CPU meter, and there is an annoyingly noticeable musical mistime when it happens - same place every time guaranteed, even when just one track - any track (midi or audio) - is solo'd. It almost sounds like a scratched CD skipping. I've been racking my brain for three days straight without success. I moved the entire project to a different disk, no change. Saved as a different project, no change. I disabled all effects in all bins (and there aren't that many yet as I'm still tracking audio) - no change! It is most noticeable on my Addictive Drums 2 tracks (whether frozen, or in midi), but it definitely happens on all tracks - vocals, guitars, etc.
 
I'm running SPlat build 2016.03 x64. 88.2 Sampling rate, 4096 buffer size. Machine is an i7-975 running at 3.33 Ghz, 28GB RAM. Project disk is an SSD, as are the Audio and VST disks as well. I did try to move the entire project to a spinner to see if it would make a difference, and it didn't. I have several much larger projects that run without issue, so I know my system is not the problem.
 
Any ideas, anybody?

Solo/mute will not free up CPU. As it happens in the same place each time, do any tracks start at those points? Soft synths or audio tracks with high CPU/look ahead would be something to check.

Freezing synths will free up CPU some, but archiving a track would release it completely. If you go this route, save the project with a new name first.

I would also check the event list for possible accidental events which are not visible.

Possible causes that I can think of:
 

• A volume/mute envelope dropping rapidly to -INF
• A snippet of a clip which could (should) be deleted - enable all your layers and have a look

You say it's happening on all tracks - is this true even when you solo individual tracks?
Hopefully this is just a glitch on one track and soloing each one in turn will reveal the culprit

mettelus
Solo/mute will not free up CPU. As it happens in the same place each time, do any tracks start at those points? Soft synths or audio tracks with high CPU/look ahead would be something to check.

Freezing synths will free up CPU some, but archiving a track would release it completely. If you go this route, save the project with a new name first.

I'll give archiving a try and let you know what happens. Only one of the three glitch areas has a new segment starting. I also tried deleting that section and there was no change.
 
Overall CPU usage is actually quite low, which is what makes the spike noticeable when it occurs right at the glitch.

Kalle Rantaaho
I would also check the event list for possible accidental events which are not visible.

Hmmm. That's a good idea. Let me check that out too.

If you say that it happens on all tracks, no matter if they are midi/audio, solo'd or not, then I would say take all the audio out of the project, see if it happens. if it still does it, put all audio back and take out all midi. If it still happens copy one trk at a time to a new project and see if that cures it.
 
I am like others, there must be some small little bit of clips in the project that your not seeing.