LEADTOOLS Multimedia API Help
| LEADTOOLS Multimedia API Help > LEADTOOLS Multimedia Features > TargetFile Syntax |
LEADTOOLS multimedia gives some filenames special handling. These filenames follow a syntax similar to an URL ("xxxxx://yyyyyy/zzzz":
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.
The filenames should have the syntax ltsf://ip_address[:ltsf_port].
These streams require the LEADTOOLS Video Streaming Module. In particular, the LEAD Network Sink Filter, LEAD Network Mmultiplexer Filter and LEAD Network Protocol Manager are used for this functionality.
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.
These filenames should have the syntax udp://ip_address[:udp_port][/network_card].
These streams require the LEAD MPEG2 Transport UDP Sink and the LEAD MPEG2 Transport Multiplexer.
Filenames starting with "rtp" are assumed to be streamed to a UDP port. The stream is embedded inside RTP packets. The LEAD MPEG-2 Transport UDP Sink filter is used as the sink filter. Important note: the receiving end should read the data using the udp:// prefix, not rtp://, because the LEAD MPEG2 Transport UDP Source filter is able to automatically detect the presence of RTP headers.
These filenames should have the syntax rtp://ip_address[:rtp_port][/network_card].
These streams require the LEAD MPEG2 Transport UDP Sink and the LEAD MPEG2 Transport Multiplexer.
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.
These filenames should have the syntax tcp://ip_address[:tcp_port].
These streams require the LEAD MPEG2 Transport UDP Sink and the LEAD MPEG2 Transport Multiplexer.
Filenames starting with "mms" are assumedto be pushed to a Windows Media Server and the LEAD MMS Sink filter is used as the sink filter.
These filenames use the syntax mms://[username[:password]@]ip_address[:port]/publishingpoint
These streams require the use of the LEAD Windows Media Compressor or LEAD Windows Media Multiplexer. See the ltmmCapture_TargetFormat Constants and ltmmConvert_TargetFormat Constants for more details.
See Using the LEAD MMS Sink Filter for more details on how to use the LEAD MMS Sink filter.
Filenames starting with "html" are assumed to be pushed to a IIS Media Media Services and the LEAD SSF Writer filter is used as the sink filter.
These filenames use the syntax syntax html://ip_address[:port]/LiveRelativeURL
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 function inet_addr. 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 might 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 it 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 function inet_addr. 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 is used. |
|
udp_port |
(Optional) The port on which to listen. 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 function inet_addr. 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 is used. |
|
rtp_port |
(Optional) The port on which to listen. 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 to (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 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 to. The default value is 80 (HTTP port), but the Windows Media server can be customized to listen on a different port. This value 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 an existing name. |
|
username |
(Optional) TA 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 to. 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". |
