Play/Pause issue driving me nuts...

[mano111]

Originally Posted by rogga_bogga

I have the exact same problem, and I have NVidia graphics too. (GeForce FX 5200)
I don't know if it's a coincidence or not but all the trouble started after installing drumkit from hell superior 2.

Have you tried deleting pref and databses? often needed after installing new plugins.

Another thing to try is moving the newly installed plugin to the 'unused plugins' folder, just to see if it makes a diffrance.

Originally Posted by mano111

Have you tried deleting pref and databses? often needed after installing new plugins.

Another thing to try is moving the newly installed plugin to the 'unused plugins' folder, just to see if it makes a diffrance.

Deleting prefs and databases helped a lot, I didn't know that. It's still there but it doesn't happen even half the times it used to. I tried moving the plugins but it didn't make a difference at all.

Thanks.

[mano111]

Originally Posted by DigiTechSupt

Try emptying the contents of your Windows>"Prefetch" folder.

This (mentioned on first page of this thread) may also help.

Originally Posted by rogga_bogga

I tried moving the plugins but it didn't make a difference at all.

So it probably has noting to do with the new plugins.

[Teolin]

Originally Posted by mano111

This (mentioned on first page of this thread) may also help.


So it probably has noting to do with the new plugins.

Just did some testing.

I have Superior Drummer 2.01 and EZ Player in a session that's been very troublesome. At 64 buffer size, it can take several hits to the keyboard or clicks to the transport for play or record to begin. As buffer size is increased the behavior decreases (usually), but never goes completely away, on my machine. Just like others are seeing.

Things tried that did not correct the problem:

1) Remove instances of Superior and EZ from session tracks.

2) Remove instances of Superior and EZ from session, close PT, run remove database and pref utility, and restart PT.

3) Remove instances of Superior and EZ from session, close PT, remove Sup. and EZ from PT plugins folder, run remove database and pref utility, and restart PT.

What did work (on my computer):

Remove instances of Superior and EZ from session
Save session and close PT
Remove Sup. and EZ from PT plugins folder
Shut down and restart computer
Run remove database and pref utility
Restart PT
Open session

The only way I can get rid of the problem is not to use Superior (for which I recently paid $300). I get zero instances of unresponsive trasport at any buffer setting when SD2 and EZ are banished from Digi-world. I didn't test removing just one or the other of SD2 and EZ.

What would be helpful is if someone who has SD2 and is running it on something other than a Q6600 could chime in. Also whether anyone who does have a Q6600 and SD2, but does not run a Nvidea video card is seeing the same symptoms. I don't have another video card to test with.

What a fun Saturday morning...

[Teolin]

Oh, one other thing about the test. Removing SD2 reduced the RAM usage drastically (which I thought might be related to the transport unresponsiveness). So I added 18 instances of Xpand! to get the RAM usage up to a similar level, after deleting the instance of SD2.

[HeySchlitz]

fwiw Teolin, I was able to reproduce the problem on an empty project....just hitting play. I have yet to see the issue even once on the Mbox 2 mini I picked up (same computer, everything the same except USB interface). This leads me to believe (based on other information in this thead) that it's firewire, 64ms buffer or the nvidia drivers (or some combination of these). It also only occurred for me after opening and closing a few sessions.

[Teolin]

HeySchlitz,

The Mbox 2 mini I bought last week is used only with my laptop so far. Also using 7.4 with it and SD2, and am not seeing the play/rec problem at all. I've been moving the same session back between both computers--works fine on one and not on the other.

So, SD2 and the Mbox 2 mini running on an old Dell 8600 (Pentium M 1700--a qualified computer with prior versions of PT) doesn't display the problem. Except the old Dell will barely run SD2 and Xpand together because of cpu load.

But Schlitz, you have the problem with one interface and not the other on the same computer, without SD2! I guess I should test that tonight. I'll unhook the 002 from the desktop and plug in the Mbox and reactivate SD2 and see what happens. If sessions with SD2 work okay, then on my machine it's down to "interaction between a software program and firewire/002?" Maybe... Maybe not...

Did you try Digi supports suggestion of disabling the NVIDIA drivers and using the stock XP video drivers?

I'm running XP Home SP2 on the desktop and SP3 on the laptop. Both computers have NVIDEA GeForce cards.

002R on the desktop on an approved ADS Pyro card--no sharing of IRQ.

[HeySchlitz]

Thanks for the info. No I haven't tried disabling the drivers yet...I've been too lazy. I'll try hooking up the 003 again and give it a whirl this week.

[Teolin]

Loaded Mbox 2 Mini drivers on desktop (specs in signature) and tested the same session alternately switching between Mbox and 002r. Ran delete databases and prefs between restarting PT and changing interfaces. Did not reboot between restarts of PTLE 7.4.

48k Session was newly created with 3 instances of SD2 on 3 stereo instrument tracks. 26 dverbs on six mono audio tracks. Cpu load at about 15-18%, Ram usage at 2.15 Gb. Just wanted to get the session under somewhat of a load--in my experience more problems occur in PT under load.

I have a Nvidea 7300 video card, but it is running on the Windows plug n play drivers rather than NV software.

Mbox buffer will only go to 128 so first ran a test at 128 on both interfaces. Ran tests with Play only, but used both the mouse and spacebar. Ran 20 tries each (below, 1 represents a successful play start and 0 unsuccessful)

002r at 128 spacebar: 10110010000010010101 (8 successful, 40%)

002r at 128 mouse: 00011000010011010011 (8 successful, 40%)

Mbox at 128 spacebar: 19 out of 20 success

Mbox at 128 mouse: 100% successful

002r at 64 spacebar: 10000110000111010101 (9 successful)

002r at 64 mouse: 00011000010011010011 (8 successful)

[DigiTechSupt]

Teolin - which Firewire card are you using, or what are the specs of the firewire port the 002 is connected to?