PT10 Takes a Long Time to Close??

[DaveBCC]

This is on Win764 / i7 960 / SSL Madixtreme64+Alphalink AX, and with CPTK.

• Installation was dead simple (aside from the typical fumbling getting the SSL HW to talk)
• Operation is smooth as butter, at least on the small sessions I've run so far, no clicks/pops, no errors, everything perfect, loving the new features
• Comm with Axiom Pro 61 is flawless, hypercontrol working as before

So everything is great, but when I save and exit, the session closes instantly, but then the PT blank screen freezes, and typically takes about a minute before it closes. After it closes all is well, Windows functions normally, and PT can be restarted with no problems.

I'm guessing this has something to do with PT relenquishing memory back to Windows from the disk cache thing, but haven't confirmed that yet (or perhaps this is just a message from the universe telling me I should never stop recording ).

Anyone else seeing this behavior?

[DaveBCC]

Anyone?

[flawlessempire]

Same issue over here when closing PT10.
I never waited long enough to see how long it takes to close.
Now after I close a session, I exit PT10 from task manager.

[jeam25]

I had it ....for me trashing the preferences resolved the issue .

[DaveBCC]

Thanks guys.

Jeam25, I was excited to hear your results, but I trashed preferences and saw no change in the behavior on my rig.

I did verify that it is not related to the disk cache (or at least my RAM meter goes back down immediately, but the background screen still persists for about a minute).

[mrpollack]

I have the same here..I found out that it is closing exactly as long as it starts..

[jeam25]

Originally Posted by DaveBCC

Thanks guys.

Jeam25, I was excited to hear your results, but I trashed preferences and saw no change in the behavior on my rig.

I did verify that it is not related to the disk cache (or at least my RAM meter goes back down immediately, but the background screen still persists for about a minute).

Oh forgot ....I turned off DEP Also try changing the FW driver ...

http://www.fanhow.com/knowhow:Enable...ows_7_27019737

[DaveBCC]

As an update to this one, I find that at this behavior goes away (at least on my machine) if I disable hyperthreading. Odd, but there ya go .