TSPlayer
TSBroadcaster
SoftOC
TSMux
OCAP ATE Host
OCAP SFG
OCAP
Strategy and Technology

TSPlayer is an MPEG-2 transport stream player which is particularly suitable for streaming MHP and OCAP content, encoded and created by the TSBroadcaster and SoftOC products. [View TSPlayer screen shot].

TSPlayer consists of:

  • A suitable Unix-based server, typically a SunFire 240 running Solaris or an HP Proliant 380 G3 running RedHat 7.3.
  • An ASI input/output card from Video Propulsion, Inc. GigE support is currently under test and will be available shortly.
  • TSMux, real-time software multiplexor.
  • TSPlayer client software for monitoring and handling transport stream play-outs.

TSPlayer is suitable for a laboratory environment or live broadcast. It can be configured to ensure continuous service through two modes of resilency:

  1. First level is intended to protect against failure of the interface receiving data from TSPlayer. In this instance, TSPlayer may either be installed with two ASI cards or have its ASI output split, thus playing transport streams to multiple broadcast interfaces simultaneously. Ensuring delivery to more than one point in the broadcast multiplex.

  2. Second level requires dual servers, having two TSPlayers configured as partners. In this mode each TSPlayer monitors the health of its partner and takes over play out if a problem occurs.
TSPlayer can play out single file transport streams or kit files at user-defined data rates. 'Kit files' consist of transport packets and DSM-CC modules plus an XML kit-control file. The control file describes how to multiplex these parts at the section level in order to achieve user defined MPEG / DVB / DSM-CC table repetition rates.

TSPlayer has three levels of access allow administrators, users and staff with simple monitoring privileges to be created.



ASI output specification

  • ASI output to 50 Mb/s

  • Upgrade to 100 Mb/s or 200 Mb/s available

  • Clock rate accuracy 1 ppm

  • Ageing < 1.0 ppm/year

  • TSMux takes multiple simultaneous file and socket inputs

TSMux

  • Auto 'rewind' of AV files when end is reached making TSMux AV play out suitable for:

    • Broadcast barker channels.
    • Development systems such as TSDeveloper

  • TCP/IP socket inputs are ideal for dynamically updating data such as MHP/OCAP Object Carousels played from TSPlayer.

  • Processing of transport stream components on entry to TSMux. Processes include:

    • PID filtering
    • PID re-mapping
    • PCR restamping - essential for AV re-multiplexing.

Last Updated: September 23, 2007; Copyright © 2003-2007 UniSoft Corporation.
Copyright © 2003 Strategy and Technology Limited