comments on Vegas for video post

LarryPeter wrote on 3/7/2000, 10:49 PM
I've been audio engineer and sound designer at a p-
production house in New Orleans for 10 years. I've been
one of those renegades who bucked the ProTools bandwagon
all along because the interface was JUST TOO SLOW. Not
enough time in my day for all those keystrokes and menu
pull-downs. I've used Micro TecnologiesUnlimited
workstations since 1992 and even though there was no
support for real time effects, I could consistently beat
Pro Tools for getting any audio for video job done just
because of the outstanding interface.

Now Vegas comes along and in my eyes has the potential to
be the real deal. I used it on a fairly complex session 3
hrs after registering it and didn't make a fool out of
myself. After another week of use I have some suggestions,
and would like feedback from other video post users.
My first reaction was to throw it out because it's one
frame late on sync on the record side locked to MTC. Never
had that problem before. The rest of the prog is good
enough to be patient, optimistic and press for a fix.

Next, please look at the MTU interface for two of it's
excellent features and see is something similar could be
implemeted: Amp zones and skip zones. Dig this: select a
region, click a button, type -20,1,1,(enter) and you have
an exact -20db attenuation with 1 frame fades on each side.
How long does it take a good artist to draw this with
volume envelopes? Also, allow the setting to be saved as
default. Next time you just select and hit enter!

The fade handles on the ASR curves should be easier to
grab, too. Don't like trying more than once.

I'm looking for a prog that is as quick, accurate and
repeatable as riding an automated fader. If you can
implement these few changes, you'll be closer than anyone
else has come.

Overall, great job.

Comments

pwppch wrote on 3/8/2000, 9:13 AM
Hi Larry:

>>My first reaction was to throw it out because it's one
>>frame late on sync on the record side locked to MTC. Never
>>had that problem before. The rest of the prog is good
>>enough to be patient, optimistic and press for a fix.
>>

Could you decribe a scenario to reproduce this problem?

Thanks
Peter

PSPattison wrote on 3/8/2000, 9:28 AM


Larry Peter wrote:. . .
>>Overall, great job.

I agree. The one-frame-late problem is, of course, related more to
the shortcomings of MTC than VP itself. One effective workaround I
have used with a TimeLine Micro Lynx synchronizer is to feed code
from the synchronizer's TCG output, locked to the group and offset
one frame. Sync sticks like glue. I am also looking into using the
Antex StudioCard 2000. I once used an earlier version of their card
and recall that besides MTC it could read/write real SMPTE in all its
flavors, and would map into a system as though it were MTC.

Good Luck
PSPattison--another PT avoidance kinda guy
LarryPeter wrote on 3/8/2000, 7:35 PM


Peter Haller wrote:
>>Hi Larry:
>>
>>>>My first reaction was to throw it out because it's one
>>>>frame late on sync on the record side locked to MTC. Never
>>>>had that problem before. The rest of the prog is good
>>>>enough to be patient, optimistic and press for a fix.
>>>>
>>
>>Could you decribe a scenario to reproduce this problem?
>>
>>Thanks
>>Peter
>>
>>
LarryPeter wrote on 3/8/2000, 8:02 PM


Peter Haller wrote:
>>Hi Larry:
>>
>>>>My first reaction was to throw it out because it's one
>>>>frame late on sync on the record side locked to MTC. Never
>>>>had that problem before. The rest of the prog is good
>>>>enough to be patient, optimistic and press for a fix.
>>>>
>>
>>Could you decribe a scenario to reproduce this problem?
>>
>>Thanks
>>Peter
>>
>>

Dear Peter:

Thanks for the quick response. First of all, I am aware of the
limitations of MTC sync. My previous MTU workstations had a SMPTE
daugtherboard that handled sync flawlessly; cost a couple grand
though. Don't want to go down that "proprietary" road again. Here's
exactly what I was experiencing: I'm feeding VP 24 bit AES/EBU from a
Sony Digibeta machine converted to SPDIF through a CO3. I record arm
a track, set to chase MTC, and roll a tape that has a series of 1
frame pop tones at frames 0:00, 0:10, 0:20 and 1:00. When I examine
the time line, the tones are at frames 1, 11, 21 and 1:01. I then
layed the track from VP back to videotape in chase to MTC mode. the
video tape now had tones at frames 1, 11, 21 and 1:01. So sync is
fine on the playout side. Then I eliminated the CO3 converter and
fed VP analog audio from the videotape. Same thing; comes in 1 frame
late. Lays back fine.
Didn't mean to sound like an ass on my previous post, but in my field
1 frame off means lost clients. Fixing it means lost time. Neither
one is good. The one frame deal seems very consistent. I've
repeated it dozens of time from various sources. Also saw several
posts on the forum that looked similar. So regardless of where the
blame lies, hardware, drivers, etc., be good guys and give us an
"invisible" fix for things like this. i.e., all of our video editing
programs allow us to set sync offsets in the .ini files for both
record and play sides. Some of these progs are sloppy as you get,
but neither you or the client sees the sync slop; the .ini settings
have corrected the 10 frame sync offset and you don't have to fix it.
I will say , every day I use this I like it more. Couple of tweaks
for us video guys and I'll be pushing this prog on all the guys in my
field. Love the forum also.
pwppch wrote on 3/10/2000, 1:14 PM
Thanks for the details. I will let you know what I discover..

Peter