Differences in how Windows 2000 and Windows XP handle Serial Digital Interface signals

Support for Windows XP has ended

Microsoft ended support for Windows XP on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article has been archived. It is offered "as is" and will no longer be updated.
This article discusses the differences in how Microsoft Windows 2000 and Microsoft Windows XP handle Serial Digital Interface (SDI) signals like digital video (DV) streams.
SDI (or SMPTE 259M) is a standard for serial transmission of digital video. The SDI standard transmits plain video data and provides space for ancillary data, including time-code data, user-specific control data, and digitized audio. The SMPTE 291M standard defines the generic format and location of ancillary data. Audio embedding is specified in the SMPTE 272M standard. A data rate of 270 megabits per second (Mbps) is standard for conventional TV formats (4:2:2 video). This rate is equal for 525-line systems (29.97 Hertz (Hz)) and for 625-line systems (25 Hz). New standards with higher data rates have been developed after the introduction of new image formats and of HDTV.

The Microsoft Digital Video (MSDV) camcorder driver (Msdv.sys) uses a fixed mechanism for timing DV streams. A problem may occur in how the correct stream rate is maintained. The Msdv.sys driver will insert empty common isochronous packet (CIP) header packets every nth isochronous packet. For example, this pattern might be an alternating pattern like 15, 15, 15, 15, 16, repeat. This pattern would cause correct DV transmission, but the timing would be imprecise.

In Windows XP, the Msdv.sys driver sits on top of the IEC-61883 protocol driver (61883.sys). 61883.sys, not Msdv.sys, specifies a time value that tells how long it should take to send one data block. The time value is specified in terms of 1394 ticks. For more information, see the following formula:
1394 ticks = 8000 cycles/second * 3072 ticks/cycles = 24,576,000		  ticks/second 

This time information and the number of ticks that have actually occurred are tracked to derive the correct time to insert empty CIP packets. The result is a much more accurate data stream rate in the Windows XP Msdv.sys driver than the data stream rate in the Windows 2000 Msdv.sys driver may provide.

Article ID: 834727 - Last Review: 01/06/2015 13:44:47 - Revision: 1.0

Microsoft Windows 2000 Professional Edition, Microsoft Windows 2000 Service Pack 1, Microsoft Windows 2000 Service Pack 2, Microsoft Windows 2000 Service Pack 3, Microsoft Windows XP Professional, Microsoft Windows XP Professional SP1

  • kbnosurvey kbarchive kbinfo KB834727
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)