needing to rebooting for my audio software

[banjo71]

I've noticed a few things about running my operating system (Windows xp pro) with Pro Tools 8:
(This is a computer thing, not a Pro Tools problem, I believe)

1. There are times I'll be in a session 24bit/44.1kHz and the clock stalls and jumps ahead, and the click track is inconsistent

2. Plugins like Antares Auto Tune, which have always worked for me will stall when I try and put them on a track in the plugin chain.

I notice if I reboot, these problems go away for awhile. I leave my computer on over night, maybe I should shut down it and the firewire Glyph drive for my audio files every night. But I schedule updates and scans during those times. What's the norm solution for this?

 

[RPRecording]

Did this just start or has it always happened? When you talk about the clock stalling then jumping and click being inconsistant, it starts to sound like there's something interrupting the system (distracting the system from focusing on the Pro Tools app).

There's a windows performance setting that allows you to tell windows to give CPU priority to background task's. Most DAW's do much of their stuff as background tasks so you might want to look and see if this option is turned on in windows.

Been awhile since I did XP tweaking so I dont recall exactly where the option is.

Another possibility is the system is see'ing some sudden DPC latency spike.

You could download/install this...
http://www.thesycon.de/deu/latency_check.shtml

Run it while your doing some recording and when you detect the system hiccuping, take a peek at the latency checker and see if you got some sort of spike. This would indicate some driver was doing something and got in the way of the DAW.

A little more difficult to determine exactly WHAT driver but this might put you on to something.

 

[banjo71]

Did this just start or has it always happened? When you talk about the clock stalling then jumping and click being inconsistant, it starts to sound like there's something interrupting the system (distracting the system from focusing on the Pro Tools app).

There's a windows performance setting that allows you to tell windows to give CPU priority to background task's. Most DAW's do much of their stuff as background tasks so you might want to look and see if this option is turned on in windows.

Been awhile since I did XP tweaking so I dont recall exactly where the option is.

Another possibility is the system is see'ing some sudden DPC latency spike.

You could download/install this...
http://www.thesycon.de/deu/latency_check.shtml

Run it while your doing some recording and when you detect the system hiccuping, take a peek at the latency checker and see if you got some sort of spike. This would indicate some driver was doing something and got in the way of the DAW.

A little more difficult to determine exactly WHAT driver but this might put you on to something.

This has happened ever since I've had ProTools 8. Also, sometimes, worse than the cursor going slow and fast and slow... etc.. it will not even play when the play button is engaged. So I save my data, shut down the computer, and start back up and relaunch ProTools, and it works fine.??