NetShow Overview

 What's New


 Multimedia Basics


 Illustrated Audio




 Hot Topics

 Glossary & Index

NetShow Encoder Hot Topics

This NetShow Hot Topics section contains tips and techniques on the NetShow Encoder.

A special note for those of you using NetShow Real-Time Encoder that shipped with NetShow v2.0: this component has been renamed NetShow Encoder in NetShow v3.0 . Unless specially noted, all references to procedures are the same, regardless of which version of the Encoder you use.

NetShow Encoder Tips

In order to encode a variety of video motion types, low-motion and high-motion, and at varying frame sizes from QCIF (176 x 144) to CIF (352 x 288), it is recommended that you use a PII-266 at a minimum. A dual-processor Pentium Pro 200 is also an effective encoding machine. The encoding process is much more CPU-intensive than it is dependent on the amount of memory. However, a minimum of 64 MB of RAM is recommended; this requirement is more dependent on the operating system and other applications such as video editing programs that might be used.

A comprehensive study on various computers and CPU utilization is available which provides many details related to encoding machine selection, different types of video encoded, codec selection and configuration, and so on. See CPU Utilization Study Real-time Encoding Study.

Yes there is, with some caveats. For the most part, this document describes the scenario of Webcasting a live event from a location remote to the point of network service, encoding for both video and audio on site and distributed to the Internet at associated bandwidths.The Guide to Live Webcasting Using Microsoft NetShow is now a part of the CCAG. Be forewarned, however: every live event has different and unique implementation issues and challenges. Do not assume that every issue you may potentially confront is discussed in detail in the Guide to Live Webcasting. While we present many specific guidelines, the guide also gives you an idea of the broad range of considerations involved in planning a live Webcast.

The answer to this question may be that either the audio or video input is not properly selected or the encoding settings are overloading the CPU. If you are encoding audio only and have at least a P5-166 encoding machine, it is unlikely that you are overloading the CPU. Therefore, first check the Recording mixer and cable connections to confirm the inputs that are selected and confirm that the audio is playing correctly.

For the video input problem, first check that the video input is assigned to the correct input device--for example, a VCR if appropriate. Then you may need to change the video codec settings under the advanced button on the Wizard page or property page. For example, you may need to reduce your window size, decrease the picture quality, choose an optimal pixel format for your capture device, or reduce the frames per second or alter the IFrame / Second value. One or a combination of these may need to be changed for optimal results.

The NetShow Encoder does not support MJPEG. This card would have to offer a different video format to work with this NetShow component.

Content produced with NetShow Real-Time Encoder as part of NetShow v2.0 normally doesn't create seekable .asf files. ASFChop creates an index on .asf files longer than 10 seconds so that you can seek (similar to fast-forwarding) through the file. To do this, specificy the -in and -out commands without any time, and be sure to give the output .asf file a different name than the input .asf file, for example ASFCHOP -in C:\Test1.asf -out c:\seekable.asf.

Content produced with NetShow Encoder as part of NetShow v3.0, integrates the ASFChop indexing functionality. Indexing of .asf files can be done automatically from within NetShow Encoder. Since this is potentially a CPU-intensive process, this option is in the Local File options property page or in the Custom Configuration wizard. The default setting is on and the procedure is started upon completion of encoding the .asf file.

This is simple and yet complicated. First the ISP needs to talk to their upstream provider in order to get a pipe connection from the MBONE (basically a TCP/IP tunnel) to their network. Then the ISP needs to turn on broadcasting unless they are routing the MBONE tunnel to the client side of their network. (Also note that since the Internet Group Management Protocol is broken in Win95 you can only tune in to one broadcast station at a time over a 28.8-Kbps connection without blowing your whole pipe.) In truth, at this point broadcasting on the World Wide Web is not common, and most any streamed Webcast is served on a one-to-one unicast basis.

The Encoder has an automation interface. You can write a VB application to read the list from a data file. There is an example app in the Encoder SDK that will read a text file and let you "Drop" the URL into the stream with a button click. Clever coders could do all kinds of stuff such as create time-based scripts or other automated sending mechanisms based on events from other software.

You would normally see between 5 and 30 seconds. The length of this delay depends on the advanced settings, the codec choice, and the capabilities of the encoding hardware. You will want to look in the advanced video codec settings to control this. The Data Window is the setting that will have the most effect along with the Quality Setting. The data window set to 5 is optimal for the MPEG-4 video codec.

You can create a batch file or shortcut and set it to start when you boot.(In other words, use the startup group, load line, or some other mechanism.) Use the following command-line syntax: \nsrex.exe /start Such as "C:\Program Files\Microsoft NetShow\Tools\NSRex.exe" /START C:\Drop\CDaudio.asd (note the quotes) The key here is the /Start switch.