Rendering and mixing to new file un-usable

pvnuk wrote on 2/27/2003, 5:02 PM
When doing any mix downs with multiple tracks, cross fades and or time stretched audio my rendered file has TONS of digital clicks, pops and artifacts.

This never happened in Vegas 3.0

What has changed?

Will this be fixed and addressed immediately?
I have seen others with the same instance.

I develop loop and sound libraries for a living (two of them for Sonic Foundry so far) and I have lost a fair amount of time having to try and re-mix and re-do these tracks.

Help,

Paul

Comments

PipelineAudio wrote on 2/27/2003, 6:25 PM
ALRIGHT!!!! Im not the only nut

if you search back a little bit, you will see a lot of posts from me and some others about rendering glitches. Please contact SF tech support and let them know you have a file they can see also, and maybe theyll have the problem narrowed down better

you made my day
djderricke wrote on 3/6/2003, 9:40 PM
I should've stopped here in the beginning. I'm also having the same issue. Something that cleared it up though was me opening a copy of the file from Vegas in Sound Forge then saving it. The problem then went away.
PipelineAudio wrote on 3/7/2003, 2:06 AM
Im getting the glitches sometimes BY opening copy in sound forge!
SonyEPM wrote on 3/10/2003, 3:17 PM
We need precise repro steps from those of you who are getting pop/clicks/garbage in the rendered files on V4.0.0.

Starting with clean source material, what process will give us a click in the file every time?

We think we have a grip on all this but we want to make sure we are doing the same thing as you are.
PipelineAudio wrote on 3/10/2003, 3:24 PM
shoot! It is only with certain files for me :( On the mix I sent you, it happens at 3:47 every time, Ive got another that does it consistently as well. All I am doing is : tools-render to new track. But theres crossfades roughly near where the glitches show up
JohanAlthoff wrote on 3/10/2003, 8:22 PM
Happens to me too, semi-constantly at a certain time in my project. It's hard to say exactly when, since I get this error when running a modified BatchRender script that exports regions, but the first region to show this error starts at 01:32:18,845. There are no crossfades adjacent to that time.

I'm getting kinda desperate since I need this stuff to work, deadline is tomorrow... =)
Geoff_Wood wrote on 3/10/2003, 10:23 PM
That's why I want a "Save As VV3 veg Project" option. In a pinch I wouldn't mind missing all the extra functionality of the V4-veg, if it got me out of a hole...


geoff
Terpsichore wrote on 2/10/2004, 4:44 PM
Has this issue been resolved? I'm experiencing the same type of thing with Vegas 4.0 or Acid 4.0, latest builds, but NOT with Acid 3.0: rendered files contain random crackles and clicks, low level. Silent tracks render okay. Live playback suffers from the same thing. Happens both WDM and ASIO. What's the latest thinking on this?
SonyEPM wrote on 2/11/2004, 7:16 AM
Terps: You have Vegas 4.0e?

Are the clicks visible in the Waveform?

If so, please give us exact repro steps.
Terpsichore wrote on 2/12/2004, 8:17 AM
It occurs from Vegas 4.0e, from from Acid 4.0f, but not from Vegas 3.0 build 76. Here's how I can reliably reproduce it:

In Sound Forge 6.0, create a new 44.1/16 stereo file. Insert 20-30sec of silence. Then adjust the DC offset to something easily visible like 10000. Save as the test file. Open Vegas 4.0, create a new 44.1/16 project. (not sure if this matters)

Open the test file onto track. I didn't touch or add
any effects. Make sure all levels including master buss are 0dB and render to new file. Open in SF6.0 and playback. Other
than the initial click which is expected, there should be silence. Instead, I see slight crackles on the right channel only.

They appear as single sample depressions below the correct DC level. Barely visible but audible. Same thing happens in Acid when the track is set to beatmap. When set to one-shot, the depressions go all the way to zero, so are much more audible and visible. Again only right channel. I had to run the beatmapped test twice, the first time I didn't get the problem, but the
second render did. But previously I saw depressions all the way to zero from a beatmapped render. In all of my cases so far the beatmap and project tempos are exactly the same.

p.s. the reason I did this with a DC offset (silence) is that inspecting my original problem track which was rendered piano (beatmapped), I heard the crackles but had a hard time finding them. Once I did, they were one sample depressions to zero from either north or south. So the DC makes it much easier to see and hear.

Jim