buffer underruns ONLY caused by MIDI!

[TelosHedge]

this is the weirdest thing i have ever encountered in pro tools land.

my current setup consists of two computers. the first comp is:

Core 2 Duo 2.13ghz
P965 chipset
2GB RAM
120GB Harddrive (for PT only)
320GB Drive for audio files
nvidia 7 series vid card 256mb
Digi002Rack Factory
PT7.1

i record all of my audio into this computer. however, i have a separate pentium 4 system that i run
BFD on exclusively to save the first computer some processing/memory power. i record midi via my vdrums into pro tools, and then send it out of pro tools via the digi002 out and into another midi interface for the other computer, which then controls BFD, and sends it back thorugh into the 002's line inputs for a quick stereo mix for monitoring purposes.

my brand new core 2 system runs beautifully - until i try to record or play back any MIDI that gets sent out of the system. it seems that whenever midi is sent out i almost immediately get an underrun error. THIS SUCKS

i have tried the dual core hotfix, but to no avail. i have even tried a different MIDI interface and that yielded the same results. if i bring up my buffer settings i then get a 'the cpu load is too high - TURN DOWN THE BUFFER'

der..... any suggestions? i hope this is not a reduntant question - i tried to search for an answer already.

[bb_aus]

do you have a MIDI interface on the system or are you just using the 002s MIDI i/o

[TelosHedge]

as a matter of fact i've tried both.

i was hoping to use the 002 for simplicity but i also tried the midi interface on my bcontrol fader thing - they both gave me the same issues.

one more thing - i just reinstalled reason (on the same host protools computer) and i am recording midi just fine this way. it seems routing midi internally does not give me this problem (yet), but sending midi data out of the 002 (or any interface) is locking me up.

hope this helps.

[TelosHedge]

no thoughts? really?

bump.

[TelosHedge]

here is my last hurrah.

nobody???