Don't make the same mistake I made

Briody wrote on 5/24/2003, 1:32 PM
I writing this in case it will save someone else the 7 hours I spent debugging the stupid issue.

I had pristine video shot in great lighting with a pair of Panasonic AG-DVX100 cameras.

But every time I rendered my project little problems would pop up in the video. Certain sections would be wavy. Camera flashes that took up a single frame on the original video now looked like venetian blinds on the rendered frame.

It didn't look horrible, but the problems were there.

I tried different codecs. I tried frameserving. Nothing solved the problem.

I brought the same clips into a new project and they looked great.

Finally it hit me. It was my own stupid fault.

Near the end of the video there is a still. I had imported the still and there was someone's head at the bottom of the frame. So I had clicked on track motion and resized the frame to eliminate the person's head. The source frame was much larger then video size, so I figured I was downsampling anyway.

Not only was that still resized, but I had just resized the entire main video track. Duh! That was my problem.

I cropped the still in Photoshop and reset the track size to normal.

All is well now.

Mark

Comments

TorS wrote on 5/24/2003, 1:50 PM
We're all human, Mark. I didn't think we were all THAT human though.
Tor
BillyBoy wrote on 5/24/2003, 2:01 PM
It pays to read the manual. Being human, we all make mistakes, sometimes as you said, stupid mistakes that can take hours, days to realize we done something pretty dumb. Vegas is based on what is called events. Understanding the concept and the many ways you can alter events is key to nearly everything else you do. Vegas being flexable gives you many choices... sometimes more than you can grasp right away if you're new to the application. Some are obvious, others aren't.

If you're new to Vegas, go to the online Help System, search for Event and read the numerous articles. The twenty minutes or so spent doing this will in the long run save you many hours of frustration as you learn the basics and some of the finer points in using Vegas more effectively.
Briody wrote on 5/24/2003, 2:07 PM
You're totally right. And I'm usually real good about reading manuals. I remember spending weeks pouring over every detail of the After Effects manual before I tackled that program.

Vegas is so intuitive (especially for someone with an audio engineering background). I gave the manual a quick once-over and got to work.

But tonight is going to be manual reading time!

Mark
BillyBoy wrote on 5/24/2003, 2:47 PM
Just a quick heads up. There are two manuals. The one that comes with the boxed version is more a overview. The full manual is in PDF format you can download off the SoFo web site. The first section contains an EXCELLENT tutorial that shows the basics well. Worth doing. Also pick up the white paper on the new version 4 features, also on their web site.

Also the build-in help system is also excellent and well done with many detailed explinations and graphics many not part of the full manual. So it pays to look at that too! <wink>

If that isn't enough SPOT wrote a book, should be out early next month and he also has a 4 DVD set running I think 6 hours or so.
Briody wrote on 5/24/2003, 3:11 PM
Thanks for the tips! Much appreciated.

I have the pdf manual printed down, but I was unaware of the others.

Once again, thanks!

Mark
XOG wrote on 5/24/2003, 4:23 PM
Hi Briody,

If I'm not mistaken, there are actually THREE versions of the Vegas manual.

1. The online help
2. The Vegas 4 Manual and
3. The New Features in Vegas 4 manual

Perpahs Nos. 2 and 3 have been combined into one manual by now?

Cheers,

XOG (Pronounced ZOG . . . if anyone's wondering . . . )

Chienworks wrote on 5/25/2003, 7:49 AM
This does make me wish for a couple of things though. Since both Pan/Crop and Track Motion are so incredibly useful, it seems a shame to limit Pan/Crop to events and Motion to tracks. I'd love to see a Pan/Crop track feature and an Event Motion feature.