VEP5 isn't nulling with Pro Tools, why?

[meech]

I noticed that when I use Vienna Ensemble Pro to host my VIs (or send audio to VEP and then back), it doesn't result in a perfect null when I do the equivelent plugins in Pro Tools.

I tried using a single sample in Kontakt, and when I bounced the RTAS version to one track, VEP to another, and inverted the phase of one, they don't completely cancel each other out. The very first time I did that test today, it actually DID cancel, but when I tried again now they won't.

What could be causing this? I've tried different buffer settings (for PT and VEP), different bit depths, disabling delay comp, etc, but I can't get it to null again. Does this mean that Vienna actually sounds different than Pro Tools or it just something funny going on? I'm wondering if I should stick to Pro Tools to avoid a change in sound quality. The strange thing is that the null test did work the very first time, but not since.

Does anyone know the reason for this? At what settings do they null perfectly, and should I be concerned about that at all?

Thanks so much for the input

[Stig Eliassen]

I can't say what's going on, nor can I test this myself, but VEP occasionally needs to be "re-calibrated" by toggling the ADC engine off/on. I mainly work with a buffer of 512 samples.

If the test did work earlier, it's pretty safe to say that VI's in VEP doesn't sound any different than VI's in PT. I've also found that the timing seems very tight and solid over network, but I haven't tried any null tests.

[browniespeaks]

are you using a VI with reverb built in? Those ones wont null usually.

[Bill Denton]

Uhhhh...dude? Gearslutz is over there...

But in all seriousness, are you really working on something where it would actually make a difference?

[John_Toolbox]

I've heard people say that vepro sounded slightly muffled in the high end compared to other hosts, but haven't ever noticed it myself so I've never bothered to do the test.