Inaccurate Waveform displays

MixNut wrote on 8/2/2000, 2:17 PM

Forgive me if this has been addressed previously:

When editing on a playlist, fade and edit positions over
waveform displays are innaccurately located (visually) when
zoomed out to a certain level...Once zoomed in
significantly, the fade/edits appear in different position
relative to the waveform display.

i.e. I make cuts when zoomed out to "song level." They
appear to fall at the beginning of track waveforms. Once
zoomed in, however, the cuts are actually .5 [roughly]
seconds into the waveform (thus cutting/fading the intro of
the waveform).

Is this a known bug? If so, when will a fix be available.

Thanks in advance.

Comments

CDM wrote on 8/2/2000, 2:37 PM

I presume you're suing 1.0b. This is a known bug. I don't know if
there's a new update for 1.0. It is fixed in 2.0 and I highly
recommend the update.

David wrote:
>>Forgive me if this has been addressed previously:
>>
>>When editing on a playlist, fade and edit positions over
>>waveform displays are innaccurately located (visually) when
>>zoomed out to a certain level...Once zoomed in
>>significantly, the fade/edits appear in different position
>>relative to the waveform display.
>>
>>i.e. I make cuts when zoomed out to "song level." They
>>appear to fall at the beginning of track waveforms. Once
>>zoomed in, however, the cuts are actually .5 [roughly]
>>seconds into the waveform (thus cutting/fading the intro of
>>the waveform).
>>
>>Is this a known bug? If so, when will a fix be available.
>>
>>Thanks in advance.

PipelineAudio wrote on 8/2/2000, 2:50 PM

David wrote:
>>Forgive me if this has been addressed previously:
>>
>>When editing on a playlist, fade and edit positions over
>>waveform displays are innaccurately located (visually) when
>>zoomed out to a certain level...Once zoomed in
>>significantly, the fade/edits appear in different position
>>relative to the waveform display.
>>

This was probably the MOST frustrating thing I had to deal with so
far in Vegas...I would do quick cleaning between tom parts in
events...then play the file or zoom in only to find that the stick
hits on my toms were GONE.

A zillion calls to tech support, had me buying new video cards and
trying all manner of malarchy...They couldnt seem to duplicate the
problem...Which brings up a VERY ugly thing....I think I know why
they couldnt, they dont actually record anything from the analog
world to test stuff there! thats my theory anyways and you'll see
why...

Any how, the problem comes from the way vegas drwas the waveforms
while you are recording, the fact that this problem does not occur on
internally rendered tracks may shed some light...

The solution is simple, and as a matter of course now, once Im
done recording, prior to any mixes or editing, go to windows
explorer, shut vegas, and DELETE every *.sfk file that has qanything
to do with your current project(s). When you reopen the song in vegas
it will rebuild all the peak files, and life will be somewhat
joyous...'

This may have been fixed in 2.0 and there is some kinda rebuild
peak feature in it, but I dont care....I now religiously delete all
the sfk files before I do anything...Its just piece of mind

User-9871 wrote on 8/2/2000, 8:29 PM

Aaron Carey wrote:

>> A zillion calls to tech support, had me buying new video cards
and
>>trying all manner of malarchy...They couldnt seem to duplicate the
>>problem...Which brings up a VERY ugly thing....I think I know why
>>they couldnt, they dont actually record anything from the analog
>>world to test stuff there! thats my theory anyways and you'll see
>>why...
>>

The policy is very clear: Blame the user's ignorance. Since most of
Vegas users are semi-pro, they get away with it, and at the same time
they can just ignore the professional user like you, Aaron.
Very sad...