Comments

Control_Z wrote on 1/9/2002, 10:12 PM
I've seen plenty of bugs in VV3 but sync in a playback track isn't one of them.

Is this some sort of audio problem? If so, then no, no progress has been made toward separating VV3 video users from VV3 audio users forums and it does lead to great confusion.
stakeoutstudios wrote on 1/10/2002, 5:33 AM
The problem still exists, but it is solely a tracking or audio recording problem for me, not playback. Sometimes the tracks just don't line up right, which is very irritating.
dlogix wrote on 1/15/2002, 11:18 AM
Exactly. Lets say I have a drum track, but bass comes in later in the song. I cue up to that point and record. In the mix (in real time as I record) it sounds like everything is fine. But when played back after recording, the sync of the two tracks is off (by a lot sometimes). My other recording software (not to name names...cough...Pro Tools) does not ever do this. I was hoping Vegas would be a nice home solution since I do not have access to the studio all day and night, but this BUG is annoying..
SHTUNOT wrote on 1/15/2002, 2:12 PM
Which version of Vegas are you all speaking of? Is there still a problem like this with VV3? I haven't run into anything like this at all. What OS are you guys running...win98se,win2k,XP? Does turning vegas on/off help? Need to reboot sometimes to staighten this out? Did you guys write to sofo support and describe what has happened? What was their response? Later.
RobSoul wrote on 1/15/2002, 9:26 PM
What sound card and other hardware are you using? This is not a known software bug, as far as I'm aware. I suspect hardware issues.

Rob

Arnar wrote on 1/21/2002, 10:16 AM
This is a known bug as you will find out if you search the forum.

What you need to do is set up a pulse/click track on one track and record on another and then measure the delay between them and set that as the latency offset

Preferences /Audio/advanced/record latency.

you can set it to automatically compensate for recording latency but that is not going to work.

Obviously this is a bug but that how i got around it while im waiting a couple of years for SF to fix it.
klyon wrote on 1/21/2002, 12:22 PM
I agree that this is almost certainly a hardware problem. Are you using internal hardware? Soundblaster and other similar and compatible cards have a bug; I experienced the same thing a long time ago. They won't sync correctly at 44.1. If you're using an internal card try 48. Buying better hardware (in my case an Echo Mona) solved the problem completely.
stakeoutstudios wrote on 1/22/2002, 7:45 AM
OK, when I record using my delta 1010, I don't have the problem (but oh the problems I had getting that working! M-audio's fault though, not SF's!) But when I record using the Gadget Labs Wave 8*24 I have the latency problem. There aren't any problems with either card in Vegas 2.0h, so... it is a software bug, but only affects certain hardware.

Can everyone post what hardware this bug is affecting? that might help SF?!

Jason
cputnam wrote on 1/22/2002, 8:23 AM
I've experienced this, with the Delta 1010 and Vegas 2.0h under WinXP. Seems to happen when the track count hits around 32 tracks of 24-bit/48kHz.

e.g. yesterday I recorded a guitar part for a song, played the entire length of the song, and about halfway through, the guitar was suddenly out of sync.
I had already muted a bunch of tracks after Vegas had been choking, but this still happened. I tried recording this part a couple of times, but each time something got out of sync. These problems are usually followed by an audible dropout.

After muting just about every track, I could record.
Eventually I deleted a few unused tracks, saved the project under a new name, restarted vegas, and things worked. SF support please note.

FWIW, my CPU and disk did not appear to be anywhere near stressed when this happened.
klyon wrote on 1/29/2002, 5:22 PM
I've just set up my music machine to dual boot Win 98SE and Win 2000 and bingo: Your problem has surfaced. With only three tracks, nonetheless, I had a track record completely out of sync. I suppose that VV3 is simply broken as far as Win2000 and XP are concerned. Back to 98Se. It's a shame, as under 2000 the CD burning finally works.
ramallo wrote on 1/29/2002, 5:47 PM
Hello,

I don't have any latency issues, I believe that the problem is your sound card. I work with 40 tracks or more and all are fine.

I use a RME Hamerfall (3,5 ms of latency with Vegas).

Bye
klyon wrote on 1/29/2002, 7:16 PM
3.5ms with MME drivers? Amazing. Well, the thing is my Echo Mona has been working faultlessly with all previous versions of Vegas in 98SE. The problem arrived with Win 2000. I'll check with Echo.
ramallo wrote on 1/29/2002, 8:06 PM
Hello,

Yes MME drivers, (No WMD yet)

I tried with play with Vegas a fast and percussive shot, and record this signal, from the output of my converter to the input, and measure the time difference between to shots of the tracks.

This card works with 2,5 ms in Sonar (MME) and 1,5 ms under Asio.

Playback buffer 0,040 s (40 tracks, no drops)

Bye
stateofgracie wrote on 1/31/2002, 12:26 AM
I asked about this problem on this forum last year. I saw it while using a USB audio input device. Finally, it was acknowledged by SF: this is a problem of Window's Kmixer with WDM drivers. It should appear with audio applications other than Vegas as well. You don't see this issue with MME drivers, and there's nothing wrong with using MME drivers on Win2K. In fact, as long as the principal problems with WDM are not sorted, it's probably best to stick with MME for professional audio.