This is KILLING me!

[DigiTechSupt]

PS. wow that's a lot of drift with x-form. I consolidated the files AFTER editing and everything was way off. It takes an hour to render x-form, so I'll just record each track to a new one.

Again, covered in the manual. Don't use X-Form or Monophonic if you want to maintain tight accuracy.

Did you read through this thread?

http://duc.digidesign.com/showthread...=230034&page=2

[DigiTechSupt]

Any ideas about the other problems?

I thought you indicated earlier that these were no longer a problem (click and playback start) - is that not the case?

[audiogeekzine]

I still don't know the cause. I'd like to prevent it from ever happening again.

I had a session to finish and I didn't dick around with the playback engine again after the playback bug stopped. I just did what I had to get through it.

Why would the click plugin stop working after running the tech support utility option 2?

Why do I get different results from using the tech support utility, and deleting prefs and databases manually according to the troubleshooting faq?

When is database and preference trashing recommended?
-after installing new/different hardware?
-after installing new plugins?
-after a version update?
-after a cs update?
-only when erratic behavior occurs?

[DigiTechSupt]

Why would the click plugin stop working after running the tech support utility option 2?

I don't know - there's a function to move 3rd party plug-ins, but why that would move the click plug-in, I'm not sure. And I'm not even sure that it did, since you said it started working again.

Why do I get different results from using the tech support utility, and deleting prefs and databases manually according to the troubleshooting faq?

What 'different results' are you getting, exactly?

When is database and preference trashing recommended?
-only when erratic behavior occurs?

Typically that's the only time it's 'recommended'. There are other reasons to do it - like when you remove incompatible plug-ins, so that Pro Tools can re-cache all plug-in data.

[audiogeekzine]

By different results, I mean running the tech support then reopening a session has all the same preferences as before. It doesn't appear to do anything most of the time.
I run it from desktop/downloads/techsupport utility should it be in the Digidesign folder?

If I manually delete the files I see a change closer to as if I had just opened PT for the first time.

the play/stop thing happened again last night in a new session.

[audiogeekzine]

The play/stop bug is still happening.

I will trash prefs again and delete prefetch

[audiogeekzine]

Play/stop thing doesn't seem to be happening now, at least at max buffer settings.

Now I'm getting -9129 and -9093 errors if I open a plugin during playback, which makes mixing impossible.

I've tried setting processor scheduling to Background services
I've set windows appearance to classic
no change.
I've changed it back because I can't have it looking like [bleep][bleep][bleep][bleep] for no reason.

what other options do I have?
-I think RAID is disabled in BIOS
-I need my internal soundcard for music and skype.
-adjusting the paging file? Currently min=2046 max=4092 on C drive only.

[Bill_Urick]

Originally Posted by audiogeekzine

I do have Avast! antivirus and Spybot running at all times.

When did this start being a good idea?

[original_min]

This combo seemed to fix 99% of my playback troubles.
Although every now and then have to delete prefs, annoying....

If you have an NVidia graphics card use the Avid certified driver for it here: http://www.nvidia.com/object/avid_cert_drivers.html

At the same time trash Pro Tools preferences.
Restart, cross fingers and toes.

[audiogeekzine]

Originally Posted by Bill_Urick

When did this start being a good idea?

Well maybe it's not, but I would think a quadcore pc with 4GB RAM should be able to handle a few programs running in the background.
I'm not looking to get every last drop of performance here, I'm just trying to get a stable system that doesn't give me errors every 2 seconds.

I'll try disabling some stuff in msconfig and see if it helps any.