What exactly did XVision tell you?

Did you talk with Tom Sailor?

Have you tried ACID on your box? Does the same problem occur when using ASIO with ACID?

You act like we are ignoring you. You have recieved more attention on this than you can imagine. Dave, QA, and I have tried to reproduce this. We cannot reproduce the problem.

Would you be willing to ship your box to us - our expense of course? If not, would you entertain the idea of setting up a remote debugging session?

Peter

the conersation details will be in your email. and yeah I sure have talked with tom

acid 4 ran so clunky when I tried it that I gave up, I hear it is much better now tho, but I havent tried it

I dont mean to act like youre ignoring me...I appreciate all the help

I will see about sending this over..
what would be involved in a " remote debugging station" ??? sounds fun to me

I really would like to know if in fact it DOES mean anything that itll run fine in microsoft sound mapper and not in windows classic wave driver?

on another front in this holy trinity of frustrating hell:

> >> 3) I am on a toally new mobo and CPU, the intel D850EMV2 mobo
and a 533 2.53 P4. The ASUS P4T-E/ 400FSB 2.4 P4 did the EXACT same thing
> >>
> >> 4) Both combos work PERFECT with the following apps: Samplitude,
Sonar, Cubase SX(both asio and MME), Nuendo 1.51 ( both ASIO and MME ), and wavelab
> >
> >I'd conclude from these two that the 9652 is not directly to blame...

> there are posts going way back on the subject, I've been having this trouble for quite a while
>
> remember, when vegas uses " microsoft sound mapper " it works
fine, its when I chooser " windows classic wave driver " that it
gets sticky..hope thats a helpful clue.

Have you asked SF what the difference might be?

Pipeline,

I rarely agree with SF these days....but I do hope you consider sending your system (shipping to/from covered by SF).

This could solve all this for you AND help future clients at the same time....if not AT LEAST show them the problem exists (then they can better place blame/fix on the right parties).

You've re-installed umpteenth amount of times (how well, who knows)...it may be in your best interest to be without the system for a week or two. Just give a specified minimum time for SF to use it (2 weeks should be sufficient).

SF may find a way to make it all gel while it's there.

JoeD

We do have some more PC's that can work for the time being, but the point is, Ive built enough daws not to have any serious trouble...if these RME cards need THAT much tweaking that I gotta send them to someone to work it, I think I would rather just use different hardware.

Ive had trouble with echo and midiman stuff, but nothing like this, and that was a LONG time ago. Soundscape's stuff works fine too. I think I am gonna get rid of the converters and hardware and go for some different converters that wll work with the soundscape cards...but its not my decision alone

" Dave, QA, and I have tried to reproduce this. We cannot reproduce the problem. "

have you tried it on a commercially available P4 setup ? with a workable HD system and config ?

Thanks to fry's 15 day return policy Ill go try whatever working setup you guys have found gladly.

Funny idea... but have you tried running the P4 systems with Vegas 2.0h... that might reveal something...?

Jason