This is in the true tradition of Capt. Ed Murphy (the album is supposed to go to the duplicators early next week...) (*)
I have a simple project where tracks are randomly dropping out for very short times. I might not have noticed except that some of the level changes are so abrupt that an audible click is heard. I'll probably open a case support when I get home unless someone has a cure. This is a little long so please bear with me.
The project I'm working on is pretty vanilla with 7 or 8 tracks, V7b, very little fx, no time/pitch correction etc. All 44.1 16 bit. The PC is a vanilla Pentium (no hyper threading, single core).
Using Soundforge the click turned out to be a spot where the volume dropped drastically for a short period of time. After rerendering the click moved to a different spot in the file. Where the volume dropped there was a different looking lower volume audio waveform. It is as though the vocal track dropped out (see below).
Without changing the project I rendered the same project to two different wav files. I then dropped those 2 files into a new Vegas project into separate tracks and inverted the polarity of the second track and rendered that to a third wav file. Normally the resultant file would be all silence.
What I found was 20-30 random spots where the files were different and each of the spots was exactly 129 samples in length. The rest of the resultant file was all zeros as one would expect. Render again and the differences move.
Here's what I've tried so far before having to leave for work this morning:
* Turned off all fx - problem goes away.
* Turned fx back on and removed any non-Sony plugs - problem occurs.
* Bypassing the only master fx, Wave Hammer Surround - problem goes away.
* Replace Wave Hammer with Ozone - problem occurs but the bad spots were all now 707 samples long (weird). (The 707 sample gap is very noticeable)
* Tried changing the number of render threads to 1 - problem occurs.
Though it's hard to tell, one of the 707 sample sections may have been the vocal track which is the only place I'm using the multi-band dynamics for de-essing. Next step is to bypass that fx.
I've been using Vegas since V2 and haven't seen anything like this before. Thanks for listening and any help is really appreciated. The next question is do I need to similarly render each of the remaining 14 tracks twice to check them?
Larry
(*)http://www.edwards.af.mil/history/docs_html/tidbits/murphy's_law.html
I have a simple project where tracks are randomly dropping out for very short times. I might not have noticed except that some of the level changes are so abrupt that an audible click is heard. I'll probably open a case support when I get home unless someone has a cure. This is a little long so please bear with me.
The project I'm working on is pretty vanilla with 7 or 8 tracks, V7b, very little fx, no time/pitch correction etc. All 44.1 16 bit. The PC is a vanilla Pentium (no hyper threading, single core).
Using Soundforge the click turned out to be a spot where the volume dropped drastically for a short period of time. After rerendering the click moved to a different spot in the file. Where the volume dropped there was a different looking lower volume audio waveform. It is as though the vocal track dropped out (see below).
Without changing the project I rendered the same project to two different wav files. I then dropped those 2 files into a new Vegas project into separate tracks and inverted the polarity of the second track and rendered that to a third wav file. Normally the resultant file would be all silence.
What I found was 20-30 random spots where the files were different and each of the spots was exactly 129 samples in length. The rest of the resultant file was all zeros as one would expect. Render again and the differences move.
Here's what I've tried so far before having to leave for work this morning:
* Turned off all fx - problem goes away.
* Turned fx back on and removed any non-Sony plugs - problem occurs.
* Bypassing the only master fx, Wave Hammer Surround - problem goes away.
* Replace Wave Hammer with Ozone - problem occurs but the bad spots were all now 707 samples long (weird). (The 707 sample gap is very noticeable)
* Tried changing the number of render threads to 1 - problem occurs.
Though it's hard to tell, one of the 707 sample sections may have been the vocal track which is the only place I'm using the multi-band dynamics for de-essing. Next step is to bypass that fx.
I've been using Vegas since V2 and haven't seen anything like this before. Thanks for listening and any help is really appreciated. The next question is do I need to similarly render each of the remaining 14 tracks twice to check them?
Larry
(*)http://www.edwards.af.mil/history/docs_html/tidbits/murphy's_law.html