latency problem caused by waves pluggins?

what you could try is nudging one of the tracks by the amount of samples that the other track is delayed. To find out the delay, CTRL-click in the grey rectangle above the fader that usually showes the fader-setting in db's. It cycles through fader-setting/peak-level/plugin delay remember that number, set your nudge value to that amount, and nudge the track to the left. or calculate the amount of delay to miliseconds, and put a short delay 100% wet on the other channel... i think you have to calculate like this: lets assume this: -sample delay is 50 -samplerate of the session is 48 Khz the length of one sample is 2.0833 ms so the delay should be 50 * 2.0833 = 104.165 The problem is that you cant dial in such a delay, so you may end up having phasing problems... It would be a nice idea if digidesign introduces a new simple plugin that will allow you to dial in a delay measured in samples instead of miliseconds... (somehow i made a calculation error, but the delay shouldnt be 104 milliseconds, but 10.04 milliseconds) I did a testrun. I took a monotrack, placed an L1 on it, and checked the delay (64 samples). Then on the other channel i placed a short delay and set it to 10.30 milliseconds (If you hold the CTRL-key down while dragging the slider you can dial in more accurate...). I also flipped the phase. The result was silence, so that proves to me it all works...

Thank You Bastian so much. Man I really do learn something new everyday. Wow I have no Idea where I would be with out you guys.

alas no, I was adding in the waves mastering bundle. I was trying out a few tricks that I had read about and trying to apply it to my mastering. I was very amazed at the difference. Woo.