Just want to add some data on the above in case it helps:

My CPU seems quite low throughout the entire session. Even when the recording automatically stops, I think CPU is below 10%.

I am using a wireless keyboard and mouse, I think for troubleshooting purposes, I will go wired thinking that maybe some key is interrupting this recording process. The only reason I say its not likely is that the process seems to be very consistent at doing 8 measures and stopping.. If it was a random ESC key getting hit, its pretty much got an accurate frequency of 8 bars..

I have 24 gig of ram and enough harddrive to do some damage. So I think thats probably why Disc I/O is very low... Not sure, but tomorrow I will do more troubleshooting.. Just curious if anyone out there ran into this or its just me..

have a great evening..

Hey there,

I am having the same problem with Studio One 3 Pro... it started acting up a couple months ago to when you started a song in the program it would kind of hiccup and re settle itself. That sort of went away and now it's doing the same thing. I will randomly stop recording at different times and I lose my audio take and it has become very frustrating. Is there some factory default setting for all the basic audio options? I really haven't messed with any of them but would like to try some kind of reset and see if that helps. I also have not been able to find any help with this issue but will continue to keep looking and experimenting. Will re post if I find anything helpful

I suggest that you should start by watching this video it is very interesting.

https://www.youtube.com/watch?v=GUsLLEkswzE

This could be a situation where the CPU is being interrupted so much it is causing your computer to stop completely.

Please get the free DPC latency checker and run that and see what sort of figures you are seeing. I bet there may be some very large red spikes in your case.

The wireless keyboard and mouse could be a serious contender for this as he mentions in the video any sort of wireless networking that is going may be a cause. A wireless keyboard and mouse is simply not necessary in a standard DAW setup. I find too the batteries in the mice make them heavier and the batteries will always run out when you dont want them too as well.

But apart from that the fact they are communicating via a network to the computer may be an issue. Then again not, but it might be another hardware device in your system.

Jemusic: Lots of great info in your post and thanks hugely for that! I downloaded the free app and ran it, actually before I even ran that app, I took out all the wireless keyboard/mouse thing and now have wired versions of both. I think it may have helped a little but still doing the interruption thing.

When I ran the app, as you've mentioned, I have some red spikes in there.. Very few actually and the normal average CPU samples on the graph are quite low. When it hits red, its ALL THE WAY UP on the graph.. I want to view the youtube link again, that really makes huge sense. But I think the issue I have is I know something is grabbing and wont let go of the CPU, I don't see a great way to know what exactly it is. I dont think is the keyboard/mouse. I kind of doubt that its the network because I don't have any firewall running on my system and for that reason, I much prefer the ethernet port be disabled in control panel. If I totally run out of ideas, maybe I will do that in BIOS just incase Windows does something crazy with disable devices (and I wouldn't put it past Bill Gates to be doing that). But for lack of any better ideas, I have a few other ideas of what I don't need to be working while running Studio1. So I will experiment. I wish I could see what is actually interrupting that CPU at those red spike moments.. Also too, i will look at the manual for that app..

Have a great one!

I know this sounds tedious but I am sure he says on the video what you have to do is disable things one by one in your Device Manager, check, re-enable etc and and at some point the red spikes will stop. Then you will know what it is. Only do one at a time though!

Yep, you are exactly correct.

Actually, I did this one device at a time of things that are able to be disabled. And unfortunately, the issue still remains no matter what is disabled.

I have a hunch though: I really looked at a SANDRA report on my system. My systems contains 4 drives and 3 of them are I believe to be the best performing from Western Digital (Black). One of my drives is a BLUE and thats my C: bootup drive. I guess I felt that back when I built this system, I had better let the slowest drive be the OS. Based on the fact that I have 24 gig of RAM, I thought that possibly the system wouldn't really need to any paging or MS virtual memory nonsense that would use this lower performing OS drive -- but its about the only idea I have left.. So I am really thinking seriously about a solid state drive for my OS.. I am extremely sure that the guy on your video stated that he did this exact thing and it came down to SSD = no issues and common HD = issues.. So I think tomorrow I am pretty sure I have a game plan.. I might run that app and look for red spikes and see if I can monitor OS Disk activity.. If I see a correlation, I might be on to something...

joe