Workflow for VOB Files

jbellomy wrote on 5/31/2010, 11:05 AM
I'm working on football highlight DVD for a friend. He gave me the clips on a DVD where each individual play is a VOB file.

I've copied the files and renamed to .mpg. After editing, I rendered out to .avi with the Field Order being Upper Field first (it defaults to Lower, but I read that VOB files are Upper). I do this for each song.

In a separate project, I open each song clip (.avi), populate timeline and render as Architect - Widescreen - Video Only and Audio as .wav.

When I create the DVD in Architect and view on television, the action is all jittery.

Any suggestions are much appreciated.

Comments

Former user wrote on 5/31/2010, 12:54 PM
a VOB file can be either upper or lower. There is no standard.

Try rendering with lower and see if that fixes the jitter.

Dave T2
jbellomy wrote on 5/31/2010, 1:33 PM
Thanks Dave.

I tried Lower field, but it did not work. However, I've done so many renders that using Lower from the beginning may have worked.

I ended up rendering it as Progressive and Blend as the De-interlacing option. This worked, though I don't know if the quality suffered. The original footage is not that great.
MSmart wrote on 5/31/2010, 4:33 PM
In a separate project, I open each song clip (.avi), populate timeline and render as Architect - Widescreen - Video Only and Audio as .wav.

Why not just render as .avi and bring that into DVDA? It should be easier than the two step process.
Former user wrote on 5/31/2010, 7:27 PM
Yes, buy going to progressive, you have thrown out about half of the video information.

If you are not sure of the field order, it is best to run a test before rendering too many times. The computer screen usually only shows one field or a progressive scan so you can't tell field order by that.

As I said, a DVD can be either upper or lower depending upon the original source.

Dave T2
david_f_knight wrote on 6/1/2010, 2:06 PM
When trying to figure out field order issues, it is quickest if you set your preview window to full size and the preview quality to good or best. If you don't have it set to full size and good or best quality, then as DaveT2 suggested, only one of the fields may be shown in the preview window, making it impossible to tell whether you have the field order set correctly in the project properties.

Also, by rendering to progressive frames you do not necessarily throw out half your video information. That depends on how you de-interlace your source video. Vegas Movie Studio Platinum 9 provides three de-interlacing options: none, blend fields, and interpolate fields. Which works best depends on the nature of your source video.

Interpolating fields actually is a misnomer; it throws out one field from each frame (so half the video data is thrown away) and interpolates between rows of the retained field; best for high-motion video.

Blending fields takes both fields of a frame and merges them into a single frame (so all the video data from both frames is used); best for low-motion video.

[VMSP9 has no adaptive de-interlacing option. (There may be a free third-party plug-in that provides that capability, but not all adaptive de-interlacers are equally effective.)]

I'm not sure what the de-interlacing option of none does when rendering interlaced footage to progressive frames; it is intended to be used when rendering progressive to progressive or interlaced to interlaced. However, interlaced footage has issues that may require it to be de-interlaced even when the project will be rendered interlaced. For example, if interlaced footage is rotated, zoomed, panned, resized (like from 1080i to 720i) or stabilized then it needs to be de-interlaced first, so choosing none would in general not be the best selection in those cases.