Horizontal Distortion when rendering

Atomic K wrote on 10/3/2002, 4:50 PM
I am experiencing horizontal distortions similar to a motion blur of some sort when I render a final .avi or .mpg file from vegas 3.0c. Tech support is working on it, but I was wondering if anyone else has experienced this with Vegas. It causes a "flutter" when played back in any media player. The still frames have an actual distortion as if lines were drawn in across the subject matter. It happens especially when using the pan/crop.

I am open to any suggestions.

Thanks!

Comments

Chienworks wrote on 10/3/2002, 4:57 PM
Are these lines typically just a pixel or two thick? Could they be interlacing artifacts? You might want to try the "reduce interlace flicker" filter.
Atomic K wrote on 10/3/2002, 6:01 PM
The distortions are larger than just a pixel or two thick. where is the "Reduce interlace flicker" filter?
SonyEPM wrote on 10/4/2002, 8:39 AM
KMD: I believe you sent an MPEG copy of this psa to SF tech support? Excellent job! email me your phone # and I'll help you polish it off: drdropout@sonicfoundry.com
SonyDennis wrote on 10/7/2002, 11:28 PM
If the source video is interlaced, but Vegas thinks it's progressive, it won't deinterlace before scaling, and the interlaced lines will moire into larger artifacts (due to the scaling, and different sizes depending on the amount of scaling). Check the source media properties and/or proejct properties to make sure they are interlaced. Then, when you render to a non-interlaced format (such as MPEG-1, WMV, QuickTime), you won't get the artifacts you're referring to (the ones on the basketball at the end, right?)
///d@
P.S. Nice spot!
sqblz wrote on 10/9/2002, 10:23 AM
A very nice piece of advice. Perfect example of pristine Customer Support.
Kudos to Dennis.
Control_Z wrote on 10/9/2002, 1:13 PM
Oh please. *Good* customer support would be to release a patch immediately that either fixes VV3's propensity to misinterpret field order, or at least allows us to force it to always interpret field order a specific way in the interim.

I can no longer capture with scene detection since I must always remember to check each clip's properties and set the correct field order myself. What a pain.
SonyEPM wrote on 10/9/2002, 2:03 PM
ctrlZ: are files you have captured with sf video capture being interpretted incorrectly (not progressive)? I thought (and could be wrong) you were using another app to capture with.
Control_Z wrote on 10/9/2002, 7:10 PM
No, you're right. Since VV3 discards DV audio channels 3&4 I must use SCLive to capture - which captures all 4 channels in a single pass.

I posted an example small type-2 DV file last week. Looks normal and acts normal in Premiere and Storm edit, but drop it on the VV3 timeline and it shows up as 'progressive' instead of 'lower field first'. Renders terribly jittery.

A few topics up someone mentions SCLive is actually altering slightly it's method of capture so the problem may be fixed _for_ you. I can't wait.
SonyDennis wrote on 10/10/2002, 2:07 PM
Vegas reads the DV headers and interprets progressive DV as progressive and interlaced DV as interlaced. If your capture app is messing up the headers, how are we supposed to fix that?
///d@
Control_Z wrote on 10/10/2002, 6:17 PM
As far as I know SCLive creates standard type 2 DV files. The 'bad' ones work fine in my other two NLEs (Premiere and Stormedit). But by all means - if you're aware of some header info that's incorrectly set in these files please give me a quote that I can forward to the author.

The sample file is at ftp://videx.serveftp.com/sclive_ohci_0001.avi and is as small as I could capture it - about 4 megs. Try dropping it on the VV3 timeline and it shows as 'progressive', thus rendering jittery. Playback from timeline is good on all 3 NLEs.

Of course, I can change the FO in properties, but that's really not practical with scene detection on and hundreds of clips.
SonyDennis wrote on 10/11/2002, 2:33 PM
Control_Z:

I downloaded that clip and looked at it. Although it's hard to tell because there is hardly any motion, it definately is progressive. Actually, it's pretty bad progressive, generated from odd numbered rows on one frame, and even on the next, so small details bob up and down every other frame! No wonder you're not happy with how it looks.

Vegas is doing the right thing. If other software is bringing this clip is as interlaced, then they are not looking at the DV headers properly.

///d@
sqblz wrote on 10/15/2002, 9:53 AM
I repeat: "A very nice piece of advice. Perfect example of pristine Customer Support.
Kudos to Dennis."
Maybe Control_Z has reassessed by now. *Immediate* release of a patch to correct a non-existant bug would be quite an achievement <G>
Control_Z wrote on 10/15/2002, 7:36 PM
I dunno how much more proof I can offer of a bug somewhere. Dennis can claim VV3 handles it correctly when the other NLEs don't, but he hasn't told me what to look for in the header that indicates this. I own a disk editor too and would like to know.

In the meantime, I'll write SCLive and tell them Dennis at Sofo says some of their type2 DV files are incorrect.
SonyDennis wrote on 10/18/2002, 11:17 PM
Feel free to upload a clip that actually shows a problem, I'm happy to look at it. I'll the first to admit if the problem is ours, my record and reputation will back that up.
///d@