O.K., do not ask me how I found this out because I couldn't explain it even if I knew how. But here it comes...
After many a late night and several thousand words used only by Sailors, this is the fix:
First I have a plain old 1.8 and a 450 mhz PC with 1 gig and 512 RAM respectively. I also have a pair of Delta 1010's in the faster PC and an SB audigy in the slower.
Upon firing up VV4 when beginning a session... go to where you set your latency and drivers (Preferances), change the latency to a bit LOWER than what you would usually use (if your at 9.8 ms, then change it to 9.4 or 8.8 or similar).
Apply that setting.
Then close down that window.
Then re-open the widnow and reset the latency to your usual setting and APPLY, again. (Oftentimes I need to close down VV4c, then restart the program, and re-do the settings again, but usually it works within the first time fire-up of the program)
This will work for THAT SESSION ONLY!!!!
If you close down VV4 or choose to bring up a previous session, you will need to reset as described above. This "fix" does not SAVE with the session. It will also only apply to the session you are working on, if you change sessions, you will need to reset as described above.
SoFo might want to address this issue in an forthcoming update. (I hope, I hope, I hope)
I contacted M-Audio after the first week of "no-sleep-nights" and they instructed me to try their latest Beta drivers. After another week of 'BEING SLEEPLESS IN PARK CITY", I stumbled upon this and it has worked ever since... Zero latency problems or issues (other than I wish it would "save").
By the way, the "fix" works for SB Audigy, Live and TB Santa Cruz as well as Echo, or any other card you might choose to use. I recently tried an expensive card - which shall remain nameless - and with their cost and "promise" of no latency problems... I still had problems with VV4 and the card. Once set-up with the fix - no problems existed and it (the audio) didn't sound any better than with my Delta 1010's - so much for the $1400 card???
Hope this works for you.
SoFo could you look into why the latency will not save with the session?
After many a late night and several thousand words used only by Sailors, this is the fix:
First I have a plain old 1.8 and a 450 mhz PC with 1 gig and 512 RAM respectively. I also have a pair of Delta 1010's in the faster PC and an SB audigy in the slower.
Upon firing up VV4 when beginning a session... go to where you set your latency and drivers (Preferances), change the latency to a bit LOWER than what you would usually use (if your at 9.8 ms, then change it to 9.4 or 8.8 or similar).
Apply that setting.
Then close down that window.
Then re-open the widnow and reset the latency to your usual setting and APPLY, again. (Oftentimes I need to close down VV4c, then restart the program, and re-do the settings again, but usually it works within the first time fire-up of the program)
This will work for THAT SESSION ONLY!!!!
If you close down VV4 or choose to bring up a previous session, you will need to reset as described above. This "fix" does not SAVE with the session. It will also only apply to the session you are working on, if you change sessions, you will need to reset as described above.
SoFo might want to address this issue in an forthcoming update. (I hope, I hope, I hope)
I contacted M-Audio after the first week of "no-sleep-nights" and they instructed me to try their latest Beta drivers. After another week of 'BEING SLEEPLESS IN PARK CITY", I stumbled upon this and it has worked ever since... Zero latency problems or issues (other than I wish it would "save").
By the way, the "fix" works for SB Audigy, Live and TB Santa Cruz as well as Echo, or any other card you might choose to use. I recently tried an expensive card - which shall remain nameless - and with their cost and "promise" of no latency problems... I still had problems with VV4 and the card. Once set-up with the fix - no problems existed and it (the audio) didn't sound any better than with my Delta 1010's - so much for the $1400 card???
Hope this works for you.
SoFo could you look into why the latency will not save with the session?