Comments

Chienworks wrote on 5/18/2004, 8:47 PM
This is a vast oversimplification, so keep in mind that the actual process is probably a lot more complex.

Imagine, if you will, that the video frame is a checkerboard of red & black squares. It's also 8x8 squares. If, for whatever reason, you now need a 4x4 board, you would have to resize it. The simplistic and fast way to do this would be to skip every other square in both directions and keep only the ones you don't skip. So, for example, you might keep squares 1, 3, 5, and 7 in rows 1, 3, 5, and 7. Now, if you look at these squares specifically you might that they are all black. This means that your resulting 4x4 checkerboard is all black. It's very fast to do this, but the result isn't really what you wanted. This is fast resizing. In actual practice it's not as bad as this horrid example, but you can see the point. Information is simply thrown away in order to get the result as quickly as possible.

Instead of chucking stuff out, you could combine adjacent squares that will end up occupying the same new square. In the new checkerboard, square 1 of row 1 is made up of squares 1 & 2 from both rows 1 & 2 of the original. This means that you'll blend two black squares and two red squares together to get a single maroon square. It takes time to do this averaging so it's not as fast. However, the result might be more faithful to the original.

Of course, this checkerboard scenario isn't very realistic. Video is 720x480 pixels or so. It's very seldom you will have a video frame that consists of regular alternating pixels of high contrast colors. The details of the image tend to cover larger groups so using either method may or may not produce better results. Fast resizing may be sharper but look blocky. Averaging my look smoother but may also look blurry. It really depends on what the original image looks like. There are also different methods of averaging that take into account more surrounding pixels, giving them less weight in the average. This can improve smoothness at the cost of losing more sharpness.

The less averaging that is done, the faster the process will go. That will hold true whether the end result would benefit and look better from averaging or not. So, Fast Video Resizing will always render faster than not using it. Whether it looks better or not depends.
hbwerner wrote on 5/19/2004, 10:28 AM
Hey, Chienworks,
Very interesting. I was thinking of fast rendering more like it is done in VideoWave. There if a section of clip has no special effects or crossfades, it can copy those frames quickly and faithfully. Where there are effects, it analyzes frame by frame and takes longer. They claim on loss of quality in the video with their version of fast rendering.
I appreciate your pointing out that MS fast rendering actually blocks pixels so that there is a reduction of the final resolution from the original 720x480 (if I understand your explanation correctly).
Bryan
Chienworks wrote on 5/19/2004, 11:38 AM
Yep. Both Movie Studio/VideoFactory and Vegas will do this. If you have any unmodified DV or uncompressed material on the timeline, you can render those sections to matching DV or uncompressed files without it going through the rendering process. This happens because those frames can simply be copied. This doesn't have anything to do with the fast resizing switch. In fact, in any cases where the video is being resized, it's being modified. So this wouldn't apply to these situations anyway.
hbwerner wrote on 5/20/2004, 7:33 AM
I thought I had noticed MS moving quickly throug unaltered frames when using fast resizing, and going frame by frame when not using fast resizing. Maybe I'm wrong there, but now I'm confused as to just what resizing is doing. Is it just the conversion of frames altered with FX applications to fit the standard raster?