I have a multitrack audio only project that consists of live recordings of an hour long concert. It contains approximately 6 stereo tracks and about 8 or 9 mono tracks. I started overdubs last night and right off the bat noticed sync jumping. At first I was unsure if it was just bad tempo by the artists, but as it progressed, it was unmistakenly clock issues. While recording one track and playing back the others, sync would not hold and you would hear a slight jump in tempo every now and then. If you play back the newly recorded track, it has pops at precisely the same point on the timeline as you hear the clock jump.
My first thought was, too many tracks at once, or too many plugins, etc. So I rendered the multitrack project to a 2 mix to see if it could handle playing back 1 stereo track while recording a mono track. I got virtually the same results. pops, jumps, etc. After about an hour of killing windows processes and everthing that I could think of, I decided to go back to Vegas 5. (I had not uninstalled thank goodness! ) Vegas 5 rocked as solid as it always had in the past. Even with the entire multitrack .veg playing (16 tracks total) I could record a new track with no pops or jumps in clock.
Any ideas what might be causing this? This sounds like something that Sony should know about don't you think? I have never escalated issues beyond this forum but wonder if I should bring this to their attention?
Thanks,
JAB
My first thought was, too many tracks at once, or too many plugins, etc. So I rendered the multitrack project to a 2 mix to see if it could handle playing back 1 stereo track while recording a mono track. I got virtually the same results. pops, jumps, etc. After about an hour of killing windows processes and everthing that I could think of, I decided to go back to Vegas 5. (I had not uninstalled thank goodness! ) Vegas 5 rocked as solid as it always had in the past. Even with the entire multitrack .veg playing (16 tracks total) I could record a new track with no pops or jumps in clock.
Any ideas what might be causing this? This sounds like something that Sony should know about don't you think? I have never escalated issues beyond this forum but wonder if I should bring this to their attention?
Thanks,
JAB