The MPEG-4 Multimedia player can be passed only a single command line
argument and that is a file name or URL referencing a piece of
media content. That media content will be opened and played as soon
as the player has loaded.
In the package that contained the IBM MPEG-4 Multimedia player would have
been an example batch or command script file that invokes the main player class
(M4Play) from the jar provided that contains the code. So using that
example batch the player can be invoked as follows:
Proxies may be defined to the Java Virtual Machine (JVM) on the command line when
launching the player. For example an HTTP proxy can be specified thus:
java -Dhttp.proxyHost=myproxy.here.com -Dhttp.proxyPort=8080
-cp .;IBMToolkitForMpeg4.jar M4Play http://server.outside.com/sample.m4x
-D defines a system property to the JVM and there are system properties documented
for HTTP and SOCKS proxies etc. Please consult the documentation for the VM that
you are using for more information on these system properties.
Note: the Microsoft VM syntax is a little different as it uses /d: instead of -D
The HTTP Proxy settings will also be used for RTSP in HTTP tunnelling mode, and
the SOCKS proxy settings will be used for the RTSP socket
connection where supported by the VM. Thus if using TCP Interleave RTSP mode with a
SOCKS proxy this may be used as an alternative to HTTP tunneling to play via a firewall.
You may wish to change the M4Play batch sample to include any necessary proxy settings.
Here is a brief overview of typical properties which may be set:
- HTTP Proxies:
- SOCKS Proxies:
- socksProxyHost this is the host name for the SOCKS proxy.
- socksProxyPort the port used by the SOCKS proxy. This
usually defaults to a value of 1080 if not supplied.