maybe useful tip for users

CDM wrote on 1/5/2001, 4:23 PM
I'm not sure how many people know this but you can reduce
overhead on your project by cutting out any blank or silent
spaces in events. Even though they are "silent" Vegas still
has to play those silent areas, as long as they are part of
an event. So, say you are rendering out tracks to reimport
into a new project, be sure to trim out the sections that
did not contain any audio.

At least this was the case in 1.0...

am I wrong SF?

Comments

Rednroll wrote on 1/5/2001, 6:24 PM
You're correct as far as I know Charles. All audio
programs actually work this way. That's because there is
no hard drive seek action when there is no event present.
Even when there is silence and the event is present, Vegas
must read the hard drive and playback the silence. Most
audio programs have a "Remove or Strip Silence" function
because of this, which automatically seeks through an event
and cuts out all audio below a set threshold value. Sound
Forge has this type of feature, but I haven't learned how
to use it quite correctly with Vegas to be able to
automatically do this.You can actually have a 1000 track
song using Vegas, the limit is the speed of your computer
of how many of these 100 tracks can actually play
SIMULTANEOUSLY. Working with an 8 Track Neve audiophile you
always ran into this problem where tracks would not play,
because there where 8 simultaneous events playing at the
same time, so you had to trim the silence out and this
cured the problem. How's that for a $60,000 digital 8 track
editor, that actually couldn't even playback 8 sounds at
one time? With the use of hard disk recording I always
wondered why it's even necessary for a Gate anymore....I
never used the gates with Vegas and really wordered why SF
even developed them, you have much more control by just
trimming an event and adding a nice fade at the end. Lots
of times I even trim between snare and kick drum hits to
cut down on my computer overhead.

Charles de Montebello wrote:
>>I'm not sure how many people know this but you can reduce
>>overhead on your project by cutting out any blank or
silent
>>spaces in events. Even though they are "silent" Vegas
still
>>has to play those silent areas, as long as they are part
of
>>an event. So, say you are rendering out tracks to
reimport
>>into a new project, be sure to trim out the sections that
>>did not contain any audio.
>>
>>At least this was the case in 1.0...
>>
>>am I wrong SF?
CDM wrote on 1/5/2001, 8:04 PM
It would be really great to have a strip silence feature in
Vegas.....

Brian Franz wrote:
>>You're correct as far as I know Charles. All audio
>>programs actually work this way. That's because there is
>>no hard drive seek action when there is no event
present.
>>Even when there is silence and the event is present,
Vegas
>>must read the hard drive and playback the silence. Most
>>audio programs have a "Remove or Strip Silence" function
>>because of this, which automatically seeks through an
event
>>and cuts out all audio below a set threshold value. Sound
>>Forge has this type of feature, but I haven't learned how
>>to use it quite correctly with Vegas to be able to
>>automatically do this.You can actually have a 1000 track
>>song using Vegas, the limit is the speed of your computer
>>of how many of these 100 tracks can actually play
>>SIMULTANEOUSLY. Working with an 8 Track Neve audiophile
you
>>always ran into this problem where tracks would not play,
>>because there where 8 simultaneous events playing at the
>>same time, so you had to trim the silence out and this
>>cured the problem. How's that for a $60,000 digital 8
track
>>editor, that actually couldn't even playback 8 sounds at
>>one time? With the use of hard disk recording I always
>>wondered why it's even necessary for a Gate anymore....I
>>never used the gates with Vegas and really wordered why
SF
>>even developed them, you have much more control by just
>>trimming an event and adding a nice fade at the end.
Lots
>>of times I even trim between snare and kick drum hits to
>>cut down on my computer overhead.
>>
>>Charles de Montebello wrote:
>>>>I'm not sure how many people know this but you can
reduce
>>>>overhead on your project by cutting out any blank or
>>silent
>>>>spaces in events. Even though they are "silent" Vegas
>>still
>>>>has to play those silent areas, as long as they are
part
>>of
>>>>an event. So, say you are rendering out tracks to
>>reimport
>>>>into a new project, be sure to trim out the sections
that
>>>>did not contain any audio.
>>>>
>>>>At least this was the case in 1.0...
>>>>
>>>>am I wrong SF?