Target Filename Syntax

LEADTOOLS Multimedia gives some filenames special handling. These filenames follow a syntax similar to an URL (“xxxxx://yyyyyy/zzzz”):

  1. Filenames starting with "ltsf" are assumed to be streamed from a LEAD video streaming server and the LEAD Network Sink filter is used as the sink filter. Such filenames should use ltsf://ip_address[:ltsf_port] as the syntax. These streams require the LEADTOOLS Video Streaming Module. In particular, the LEAD Network Sink Filter, the LEAD Network Multiplexer Filter and the LEAD Network Protocol Manager are used.
  2. Filenames starting with "udp" are assumed to be streamed to a UDP port and the LEAD MPEG-2 Transport UDP Sink filter is used as the sink filter. Such filenames should use udp://ip_address[/network_card][:udp_port] as the syntax. These streams require the LEAD MPEG2 Transport UDP Sink and the LEAD MPEG2 Transport Multiplexer.
  3. Filenames starting with "rtp" are assumed to be streamed to a RTP port and the LEAD MPEG-2 Transport UDP Sink filter is used as the sink filter. Such filenames should use rtp://ip_address[/network_card][:rtp_port] as the syntax. These streams require the LEAD MPEG2 Transport UDP Sink and the LEAD MPEG2 Transport Multiplexer.
  4. Filenames starting with "tcp" are assumed to be streamed to a TCP/IP port and the LEAD MPEG-2 Transport UDP Sink filter is used as the sink filter. Such filenames should use tcp://ip_address[:tcp_port] as the syntax. These streams require the LEAD MPEG2 Transport UDP Sink and the LEAD MPEG2 Transport Multiplexer.
  5. Filenames starting with "mms" are assumed to be pushed to a Windows Media Server and the LEAD MMS Sink is used as the sink filter. Such filenames should use mms://[username[:password]@]ip_address[:port]/publishingpoint as the syntax. These streams require the use of the LEAD Windows Media Compressor or the LEAD Windows Media Multiplexer. See Leadtools.Multimedia.TargetFormatType.WMVMux and Leadtools.Multimedia.TargetFormatType.ASFMux for more details. See Using LEAD MMS Sink for more details on how to use the LEAD MMS Sink Filter.
  6. Filenames starting with "html" are assumed to be pushed to IIS Media Services and the LEAD SSF Writer filter is used as the sink filter. Such filenames should use html://ip_address[:port]/LiveRelativeURL as the syntax. See Using the LEAD SSF Writer for more details on how to use the LEAD SSF Writer Filter.

Anything else is assumed to be a regular file and the regular DirectShow rendering mechanism is used. Syntax for strings prefixed with “ltsf”

ip_address The IP address where the data will be sent from (IP address of the server computer). This can be in the usual Ipv4 format (xx.xx.xx.xx), or it can be a valid host address accepted by the standard inet_addr function. For example, localhost is equivalent to 127.0.0.1. This is the IP address of the sending (server) computer. Note that a computer with multiple network adapters may be able to support multiple addresses.
ltsf_port (Optional) The port on which to listen. The server will listen for connections on this port. The port must be a number from 1 to 65535. Note that you must make sure the port is open if you are running firewall software. The default value is 27015.

Syntax for strings prefixed with “udp”

ip_address The IP address where the data is being sent to (IP address of the client computer). This can be in the usual Ipv4 format (xx.xx.xx.xx), or it can be a valid host address accepted by the standard inet_addr function. For example, localhost is equivalent to 127.0.0.1. This is usually the IP address of the receiving (client) computer. The stream is considered to be multicast if the first number in the Ipv4 address is between 224..239 (0xE0 .. 0xEF). If the first number is not in this range, the stream is unicast.
network_card (Optional) The address of the network card receiving the data. Used only for multicast streams. This is optional - if it is missing, the default network card will be used.
udp_port (Optional) The port on which to listen. The server will listen for connections on this port. The port must be a number from 1 to 65535. Note that you must make sure the port is open if you are running firewall software.

Syntax for strings prefixed with “rtp”

ip_address The IP address where the data is being sent to (IP address of the client computer). This can be in the usual Ipv4 format (xx.xx.xx.xx), or it can be a valid host address accepted by the standard inet_addr function. For example, localhost is equivalent to 127.0.0.1. This is usually the IP address of the receiving (client) computer. The stream is considered to be multicast if the first number in the Ipv4 address is between 224..239 (0xE0 .. 0xEF). If the first number is not in this range, the stream is unicast.
network_card (Optional) The address of the network card receiving the data. Used only for multicast streams. This is optional - if it is missing, the default network card will be used.
rtp_port (Optional) The port on which to listen. The server will listen for connections on this port. The port must be a number from 1 to 65535. Note that you must make sure the port is open if you are running firewall software.

Syntax for strings prefixed with “tcp”

ip_address The IP address where the data will be sent from (IP address of the server computer). This can be in the usual Ipv4 format (xx.xx.xx.xx), or it can be a valid host address accepted by the standard function inet_addr. For example, localhost is equivalent to 127.0.0.1. This is usually the IP address of the sending (server) computer.
TCP streams cannot be multicast. All TCP streams are assumed to be unicast.
tcp_port (Optional) The port on which to listen. The server will listen for connections on this port. The port must be a number from 1 to 65535. Note that you must make sure the port is open if you are running firewall software.

Syntax for strings prefixed with “mms”

ip_address The IP address where the data will be sent(the IP address of the Windows Media server computer). This can be in the usual Ipv4 format (xx.xx.xx.xx), or it can be a valid host address accepted by the standard inet_addr function. For example, localhost is equivalent to 127.0.0.1.
port (Optional) The port to which the data should be sent. The default value is 80 (HTTP port), but the Windows Media server can be customized to listen on a different port. The value used should match the setting in the Windows Media Server's configuration.
publishingpoint The name of the publishing point to create on the Windows Media server. This should be unique and should not match any existing names.
username (Optional) A username that is allowed to push data to the server.
password (Optional) The password for the above username.

Syntax for strings prefixed with “html”

ip_address The IP address where the data will be sent to (IP address of the Media Services server computer). This can be in the usual Ipv4 format (xx.xx.xx.xx), or it can be a valid host address accepted by the standard function inet_addr. For example, localhost is equivalent to 127.0.0.1. This is usually the IP address of the sending (server) computer.
port (Optional) The port to which the data should be sent. The default value is 80 (HTTP port), but you can change it if the Media Services server is customized to listen on a different port. This value should match the setting in the Media Services server's configuration.
LiveRelativeURL The relative URL of the .ISML file that describes the Live Smooth Streaming stream. For example, if the file on the server has an absolute path of C:\inetpub\wwwroot\SSF\LiveSmoothStreaming.isml, LiveRelativeURL would be "SSF/LiveSmoothStreaming.isml".

Help Version 20.0.2019.8.26
Products | Support | Contact Us | Intellectual Property Notices
© 1991-2019 LEAD Technologies, Inc. All Rights Reserved.

LEADTOOLS Multimedia