When i completed my masking it looked fine in the preview window frame for frame and then when i rendered it, it came out badly as shown in the photos. The mask is in the top right.
I'm using Vegas Pro 15.
IS there a special reason your project properties are set to interlaced?
Not even sure what that setting is, what should i change it to?
You need to make it match the media you are editing. But first, a little lesson.
Back in the old days of broadcast analog TV, the TVs refreshed the screen 60 times per second (or 50 if you live in Europe), as this corresponds with the number of cycles of alternating current in American/Japanese 60hz AC electricity or European 50hz AC. So, because of how our power works, we had TVs that drew pics at 60 (or 50) frames per second, depending on where you live.
The problem was, broadcasting 60 full frames of video per second over analog airwaves required an enormous amount of bandwidth, more than the stations had to work with, even for old SDTV broadcasts in black and white. So, interlacing was born. The idea was to draw the even rows of pixels (or scan lines back in those days) for one frame, and the odd rows for the next, and when you see these 2 half-frames played back to back 60 times per second, your brain "interlaced" them into a full image. The fact that the TV phosphors retained their brightness after getting scanned for a split second helped to mask the fact that you were only seeing half frames. This is why all modern LCD, etc TVs have to first de-interlace an interlaced signal before displaying it, or it would look like a flickering mess.
Interlacing effectively cuts your resolution in half, and if something in the video moves between one interlaced frame and the next, that can create artifacts in the form of jagged edges on the sides of objects, etc. Interlaced video also struggles to render small text well, the text will appear to crawl with artifacts.
Progressive scan (showing the entire frame, every frame) video became possible when the advent of digital video, as the bandwidth needed for it was far less, and so now we have progressive scan 4k video, which is about 45 times more pixels per frame than an interlaced 480i half-frame would contain, being broadcast over the air in some places. The bandwidth required is so much smaller with digital, that stations are not only able to carry HD broadcasts, but often have enough room left over to carry 2-3 sub-stations in their same bandwidth allocation as well.
In Vegas, for best results, it's always best to look at the type of media you are working with (you can right click on it, select properties, and Vegas will tell you its specs) and make sure your project settings match it. In cases where you use mixed media, I'd use the settings of the highest quality clip and make Vegas scale the others to match, though there are instances (such as there there's only one short high quality clip but the majority of the project is lower quality) where this approach isn't advisable.
"drew pics at 60 (or 50) frames per second, "- fields per second, not frames.
" when the advent of digital video, as the bandwidth needed for it was far less, "- because of video compression capable with digital video.
"pixels per frame than an interlaced 480i half-frame"- analog video did not have pixels, only lines. 525 lines for NTSC.
ODD rows were drawn first.
"struggles to render small text well, the text will appear to crawl with artifacts."- this is a combination of problem with resolution and interlacing. Granted a digital video will hold text better but will also look better on an analog TV interlaced than an analog created Text.
""drew pics at 60 (or 50) frames per second, "- fields per second, not frames."
Semantics... it's drawing 50-60 frames, they're just missing half the rows of pixels.
"ODD rows were drawn first."
Depends, 1080i is even. So is PAL.
"this is a combination of problem with resolution and interlacing. Granted a digital video will hold text better but will also look better on an analog TV interlaced than an analog created Text."
Text on a SD progressive scan image doesn't crawl and flicker like interlaced does, which is what I was referring to. It might be a jumbled, blurry mess of pixels, but it isn't moving unless the text is.
""drew pics at 60 (or 50) frames per second, "- fields per second, not frames."
Semantics... it's drawing 50-60 frames, they're just missing half the rows of pixels"
Not semantics, NTSC is 30fps. There is no 60FPS in analog TV. We need to use a common frame of reference.
"ODD rows were drawn first." Upper field refers to ODD fields. HD doesn't use rows, it uses fields. Rows refer to lines drawn. And you were referencing analog which is odd rows first.
"Not even sure what that setting is, what should i change it to?"
It's possible that someday in the future there will be an Emmy Award winner who has no knowledge of interlaced video, but until that happens you should have a casual knowledge of the concept. Do some reading on Wikipedia.
Follow this post to install and learn to use Mediainfo.
When you get the report for all of your media, look at this field...
... to determine whether your source is interlaced or progressive.
Set your Project Properties to match as follows:
If you happen to have game capture clips that are interlaced, (profoundly unlikely) or some other interlaced source,
set the Field Order to match Upper or Lower as shown in the Scan Order line from the Mediainfo report. For interlaced media, you should also set a Deinterlace method and set the Full resolution rendering quality to Best.
I'd suggest that you create a Project Properties that matches your most common project and check the box to Start all new projects with these settings. Close and restart Vegas Pro and uncheck the box.