Setting Up NetShow
Microsoft® NetShow™ is ready to install from the Microsoft NetShow Web site. There are three separate installation programs: one for NetShow Server and NetShow Admininistrator, one for the NetShow content creation tools, and one for NetShow Player.
Hardware and software requirements for each installation differ, so be sure to review the requirements list, available from the Microsoft NetShow Web site at http://www.microsoft.com/netshow.
Setup for each component is straightforward. The information provided in the setup dialog boxes and, for server setup, in online Help will guide you to a successful installation.
NetShow Documentation
Documentation for NetShow Server Administrator and SDK is part of the server installation. Documentation for content creation tools and the NetShow Player SDK is part of the tools installation. Complete documentation is also available at the Microsoft NetShow Web site.
NetShow 2.0 Contains Several New Codecs
NetShow 2.0 tools installation contains several new audio and video codecs. For information on these codecs, please see http://www.microsoft.comhttp://www.microsoft.com/netshow/guide.htm.
General Protection Fault Error Occurs When Watching ASF Content
It is a known issue that passing URL script commands to a client installed on a Windows 95 system with Internet Explorer 2.0 leads to a General Protection Fault in KERNEL32.DLL. This error is caused by limitations of the browser. Microsoft recommends that you upgrade to the latest version of Internet Explorer, which may be downloaded from www.microsoft.com/ie/download.
Using the Duck TrueMotion Codec
The Duck TrueMotion video codec is a high bit rate video codec. The codec works well at 1, 2, and 3 Mb per second, but it does not work well at lower rates such as 28.8, 56, or 112 kbps.
Using the Voxware MetaSound and MetaVoice Codecs
MetaSound and MetaVoice "Bitstream" formats are not supported by NetShow at this time. Even though they can appear in the list of available codecs, do not use these codecs.
Using Component Installations
It is a known issue that for the codec component installations to work when a user is using Internet Explorer 3.0 or 3.01, NetShow Player must already be installed on that computer.
.Asd Files and Using the ASF Real-Time Encoder
As part of the NetShow tools installation, the \Program Files\Microsoft NetShow\Stream Formats directory is created. Inside this directory are nine .asd files, which will help you get started using the ASF Real-Time Encoder (an .asd file is a set of configuration settings that the encoder needs to know before it can encode information). Each of the .asd files has a title that suggests the network scenario for which that .asd file should be used. For example, the name of one .asd file is "Internet Audio Only (FhG Layer-3 )"; when chosen, this .asd file configures the encoder to accept only an audio source and to compress that source small enough to use over the Internet (this means that the output information will fit in the 28.8 kbps bandwidth). The codec used to compress the audio this small is the MPEG Layer-3 audio codec and the format used is the 20-kbps format.
For more information on these template .asd files that accompany the NetShow tools installation, please see the Content Creation Station documents in the Microsoft NetShow program group. An important note about the .asd files is that all .asd files were created for use with the Winnov Videum card. If you use a different video capture card, you may need to adjust some of the settings made by the .asd file.
NetShow Server 1.0 and NetShow Player 2.0
The NetShow 2.0 client's default configuration for unicast connections is to attempt to establish a TCP connection with the server. Previous releases would have first tried for a UDP connection. Since NetShow 1.0 servers supported only UDP connections, the NetShow 2.0 client will fail to connect to a NetShow 1.0 server when that client is running with its default settings. To use a NetShow 2.0 client to access a NetShow 1.0 server, go to the NetShow Player File Properties dialog box, and select the Advanced tab. In the Protocols group, select the UDP check box. Close the client and then try again.
Using NetMeeting and NetShow on the Same Computer
NetMeeting and NetShow use several of the same codecs. Be aware that if you uninstall NetMeeting 2.0, the L&H, Intel G.723.1, and Intel H.263 codecs will also be removed from your computer. To reinstall these codecs, uninstall and then reinstall NetShow.
Using NetShow with File Level Access Checking
When you are using Windows NT security with NetShow and are granting users or groups access to files, always grant the NetShowServices account or the NetShow Administrators group (which includes the NetShowServices account) access to the files. The NetShow Unicast service requires access in order to stream files.
Archiving ASF Streams
If you stop and restart the Real-Time Encoder while archiving a live stream using either the Auto Archive option in Configure Channels or the Save To ASF option in Manage Programs, archiving does not automatically restart. To restart archiving, you must use Manage Programs to stop and restart the program.
Similarly, if you are archiving a stream whose source is a program consisting of multiple streams on another NetShow server, archiving stops when each stream stops and does not restart automatically. To restart archiving, you must use Manage Programs to stop and restart the program.
Simultaneous Editing of NetShow Data
NetShow does not provide concurrency control and does not support the editing of channel, program, and stream information simultaneously by multiple users. If more than one person edits such information at the same time, data may be lost.
Program Manager: Stream Status
When playing a program in which one stream is from a live source and the following stream is from a file saved during the multicast of the live stream, Program Manager may report that "The system cannot open the device or file specified" for the stream that follows. This status message is normal. The second stream will play once the live stream has ended and the file has been completely written.
Configure Channels: Stream Format Changes
If you choose Edit from the Configure Channels and add or delete a stream format, you will not be able to cancel that action.
System Administration Documentation: Script Error Message
When using the online documentation with Internet Explorer, you may occasionally see a message for an Internet Explorer Java Script Error. This may occur when you are clicking a link from a contents page, such as the Overview page. If you click OK, the error message will close, and the page to which you linked will fill the browser's window. To return the frames to the window and continue, do the following:
The frames, including the contents frame, will be restored.
System Administration Documentation: Erratum in Illustration
In the System Administration Guide "Overview," the illustration for the topic "Multicasting File Transfers" contains an incorrect file name. For Clients, the label should read, "Clients receive files using nsfile.ocx."
Installing NetShow Tools
Please uninstall any previous version of the NetShow tools, including beta versions, before you install version 2.0 of the NetShow tools.
Using NoteWorthy Videophone PCMCIA Card with the ASF Real-Time Encoder
If you want to use the Noteworthy Videophone PCMCIA card with the ASF Real-Time Encoder, you must install and use the latest Crystal Sound drivers, and you must use the YVU9 video format. NetShow does not currently support this card using any other formats. To load these drivers, please see the Toshiba Web site at http://www.toshiba.com/tais/csd/support/files/win9drv.htm.
Using the ATI All-in-Wonder Card with the ASF Real-Time Encoder
If you want to use the ATI All-in-Wonder video card with the ASF Real-Time Encoder, you must install and use the latest ATI drivers, and you must use the YVU9 or YV12 video format. NetShow does not currently support this card using any other formats.
ASF Real-Time Encoder: Diagnosing Performance Problems
When you are diagnosing problems while using the ASF Real-Time Encoder, it may be beneficial to have the Task Manager (under Windows NT®) or the System Monitor (under Windows® 95) open to monitor processor loading. Loading of the CPU at 100% is a good indication that too much is being asked of the computer, and you will have to reduce the data rate (frames per second, frame size, etc.).
Problems Using ASF Real-Time Encoder Automation to Record .asf Files
There is a known issue that the ASF Real-Time Encoder incorrectly identifies the send time, play time, and duration time in the header of an .asf file when you record the .asf file after the ASF Real-Time Encoder has been encoding for a while. To see an example of this, start encoding. After an hour, start recording an .asf file. After 10 minutes, stop recording. When you attempt to play the .asf file, it will not play correctly. NetShow Player will incorrectly display the playing time as 01:00:00.0 - 10:00:00.0 instead of as 01:00:00.0 - 01:10:00.0. However, this .asf file can be fixed. To fix the file, use ASFChop to adjust the send, play, and duration times. Just run the following command from a DOS command prompt: ASFChop -in (Input .asf name) -out (output .asf name)
Problems at the End of an ASF Real-Time Encoder Session
There are three known issues where all the information from the Real-Time Encoder doesn't make it to the client or to an .asf file.
Using the Sample .asd Files
All .asd files that are installed with the ASF Real-Time Encoder were created for use with a specific video card and drivers. If you use a different video capture card, you may need to adjust some of the settings made by the .asd file, particularly the Video Source setting. When you select a sample .asd file, the Video Source will usually have "No Video Input" selected. In this case, you will need to select a video source.
When you open .asd files that you created on your computer, the Video Source will have the correct selection because you are using the same video card and drivers as when you created the .asd file.
Creating .Asd Files that Use the L&H 4.8 kbps Codec
There is a known issue that if you create an .asd file that uses the L&H 4.8 kbps codec, and you then attempt to open the file on a machine running a different operating system (for example, Windows NT vs. Windows 95), the Real-Time Encoder will report that the audio codec is unrecognized. To work around this issue, step through the wizard again and select the L&H codec. Save the .Asd file again so that when you open it, the audio codec will be recognized.
ASF Real-Time Encoder: Using the YUY2 Pixel Format
Depending on the video card that you are using, the YUY2 pixel format may not work. Some video cards interpret this pixel format upside down. If your video card is misinterpreting this pixel format, switch pixel formats. A recommended pixel format is RGBH.
Using the Voxware Codecs with the ASF Editor
Use only the Voxware Codecs compression algorithms to compress audio. Using the Voxware Bitstream or Voxware Non-file codecs to compress an audio file will cause an error.
Using the VDO codec with the ASF Editor
You can use the VDO codec to compress images, but if you look at the Codecs property page, in the Installed column, this codec will be listed as No to indicate that it is not installed. This is a known error. The VDO codec is installed.
NetShow Tools and Codecs are Designed Solely for Use on Windows NT 4.0 and Windows 95
NetShow tools and the codecs that are installed with the tools are designed to run solely on Windows NT 4.0 and Windows 95. NetShow Player can run on Windows NT 3.51, and the codecs can be installed on Windows NT 3.51 if you have an older version of NetShow Player installed. You will receive an error if you attempt to install the NetShow tools on a different operating system.
Broken Connection Between NetShow Channel Manager and ASF Real-Time Encoder
If a NetShow Channel Manager uses the stream alias method to identify the ASF stream coming from an ASF Real-Time Encoder, and the Channel Manager stops and then attempts to restart receiving the ASF stream, the connection between the Channel Manager and the ASF Real-Time Encoder is broken. To reestablish the connection between the Channel Manager and the ASF Real-Time Encoder, stop the encoder, step through the configuration wizard again, start the encoder, and then establish the connection between the Channel Manager and the ASF Real-Time Encoder.
Codecs that Do Not Work with the ASF Editor
The following codecs are listed in the ASF Editor's Image and Audio Conversion dialog boxes, but do not work with the editor. Do not use any of these codecs to compress audio or image files in ASF Editor.
Audio- Netscape compatible RT24, Microsoft G.723.1, Vivo Siren, Voxware Bitstream or Non-file codecs, VivoActive G.723.1
Image- MPEG-4 Video High Speed Compressor, Microsoft H.263 Video Codec, Vivo H.263, Duck Truemotion RT 2.0
Antex Card Issue
When using the Antex card, you may hear a periodic clicking noise in the audio track. This noise is an Antex issue and is not restricted to use of any particular codec. The problem was reported when using Windows NT drivers. It is not known if the problems happen on a Windows 95 computer.
Video Capture Cards that Are Compatible with Windows NT and Windows 95
Winnov Videum, Osprey 100, and Osprey 1000
Video Capture Cards That Are Compatible with Windows 95 Only
Intel SmartRecorder III, Video Labs Stinger, Hauppage WinCast/TV, STB TV/VGA Video Card, Noteworthy Videophone PCMCIA
Winnov Videum Issues
The Videum driver version 1.98 for Windows NT and version 1.98a for Windows 95 are the only drivers supported for NetShow 2.0. These drivers are available on the Winnov Web page.
Using UYVY and Y42T color formats with the MPEG-4 codec renders very distorted video.
On Windows 95 driver version 1.98a, the error message for unsupported video formats is truncated. The message reads, "Video Input:" Instead the error message should read, "Video Input: Unsupported video format."
The Winnov Videum card is unable to capture more than 11 frames per second at resolutions greater than 176 x 144.
Osprey 1000 Issues
The Osprey 1000 driver version 2.1 is the only supported driver for Windows NT and Windows 95. Earlier versions of this driver are not supported. You can download this driver from ftp://ftp.mmac.com.
There is a known issue that the first time you use the Osprey 1000 with the ASF Real-Time Encoder, the encoder will report an Access Violation. After you receive this message, it is advised that you reboot the computer. When you restart the computer, you should be able to configure and use the Real-Time Encoder without any problems.
It is a known issue that when running Windows NT and using the Osprey 1000 card as the audio input source for the ASF Real-Time Encoder, the audio will very often be distorted. You can download the patch to fix audio problems under Windows NT from the Osprey FTP site at ftp:// ftp.mmac.com.
General Video Card Issues
The Hauppauge WinCast/TV, Osprey-1000, and Osprey-100 cards vertically invert the video when using the YUY2 color format to output the display. This problem can also occur with other video cards.
Client Setup
Nsplay.exe, which installs NetShow Player, may request you to restart the computer at the end of Setup.
NetShow Plug-in Is Not Supported in the 16-bit Version of Internet Explorer or Netscape 2.0
The NetShow Plug-in does not support embedding in the 16-bit version of Internet Explorer or in Netscape Navigator 2.0.
Problems Playing Back Certain Types of Content
It is a known issue that computers that use a Windows Sound System audio card, have a problem playing back 12 kHz and 24 kHz content that uses the MPEG Layer-3 audio codec. This problem is not related to NetShow.
Blue Screen When Connecting to the ASF Real-Time Encoder
There is a known problem that can occur if you are continually connecting and then reconnecting to an ASF Real-Time Encoder. This problem is more likely to occur if you connect, disconnect, and then reconnect several times within an hour.
Changing NetShow Player Settings
If the settings in NetShow Player conflict with those in Internet Explorer, it may be necessary to change NetShow Player settings. This conflict may be signaled by the error message "The network connection failed." If you need to adjust settings in NetShow Player, after making the changes, click Applyto cause those changes to take effect. The NetShow Player Help file incorrectly states that you must restart the player for changes to take effect.
NetShow Player Identifies Large Number of Recovered Packets
NetShow Server can stream via UDP, TCP, and HTTP. When using UDP, NetShow Server includes an additional packet of information in the stream every 8 to 15 packets to help with error correction (because packets streamed via UDP can be lost). When using TCP, NetShow Server doesn't send the additional packets of information because TCP streaming doesn't lose packets. However, NetShow Player currently doesn't have a way of detecting whether the error correction packets were included in the stream, so the player tries to recover what it interprets as lost packets. The packets were never lost so the player categorizes the large numbers of packets that it is looking for but can't find as Recovered. The number and percentage of Recovered packets is shown on the NetShow Player Properties Statistics page.
File Transfer Control SDK
The packet format used by the File Transfer service has changed from that used in previous releases. Make sure the NetShow server that is sending files and the File Transfer control receiving files are the same release version. The NetShow 2.0 File Transfer control will not work with NetShow Server 1.0 or previously released beta versions of NetShow Server.
Using VBScript to set the value of the Type property exposed by the NetShow File Transfer control requires the following syntax to work with Microsoft Internet Explorer Version 4.0:
Where NSFile1 is the NetShow File Transfer control object.
Earlier versions of Internet Explorer do not require and will not accept the object key word. Use the following syntax to access the Type property with earlier versions of the browser:
Note: This special syntax applies only to the Type property exposed by the control. The object key word is not required to set any of the other properties running any version of Internet Explorer.
Unicast file transfers require a stream-type socket connection. Stream sockets use TCP protocol which insures the reliability of the transmission. Forward error correction (FEC) is provided for multicast file transfers using connectionless protocols, such as UDP, and should not be used with stream sockets. Because of this, the "Receive Unicast" example and the "Total Demo" example (when it is used to receive unicast file transfers), need changes before they will work.
To use these example pages, make the following corrections to their BtnReceiveFile_OnClick subroutines:
The command
Should be changed to
The command
Should be changed to
The "Receive Multicast with Progress" example page has a typographical error in the ButtonReceiveFile_OnClick subroutine.
The command
Should be
Real-Time Encoder SDK
The Real-Time Encoder application sets the duration in minutes, hours, and days, but the automation interface allows only values measured in seconds.
There are a variety of resources available to assist you if you encounter technical problems with NetShow.
There is extensive product documentation installed with NetShow in the form of HTML pages. You should also visit the NetShow website located at http://www.microsoft.com/netshow. View the Technical Support area to view the most up-to-date versions of the FAQ, current support policies, and other free support options such as the list server and newsgroups. Please note that any request that is time sensitive or critical should not be sent to the list server or news groups. These are peer support vehicles, and a response is not guaranteed.
You can contact Microsoft Technical Support to learn about other support options at the following numbers: