|
 |
 |
Command Line
The IBM MPEG-4 XMT Batch Converter Tool supports a Command
Line interface. Command line options can be specified which
pre-populate window interface especially the input and output
file fields. Secondly, The input and output files can be specified
along with the quiet (-noGui) option on the command line
to allow a batch generation of MPEG-4 files.
Command line format:
XmtBatch <input>
[-m <MPEG-4.mp4>]
[-o <XMT-O.xml>]
[-a <XMT-A.xml>]
[-h <Hinter.mp4>
[-v <M4Mvr.mv4>]
[-t <M4Mux.m4x>]
[-p <XMT-O.xsd>]
[-u <schemas/o/>]
[-[no]ValidateXmto]
[-s <XMT-A.xsd>]
[-w <schemas/a/>]
[-[no]ValidateXmta]
[-[no]convert]
[-[no]Gui]
[-l <logfile.txt>]
[-e (4|3|2|1|0) [class list]]
[-?] [-??]
[-meter|-pixel]
[-r (size|%)]
[-[no]bmp]
[-c <imgDir>]
[-d <imgDirOff>]
[-xmtaMediaPrefix <url prefix>]
[-q <test1[=<true|false>] test2[=<true|false>] ...>]
[-systemAudioDesc <on|off>]
[-systemBitrate <bitrate>]
[-systemCPU <CPU>]
[-systemCaptions <on|off>]
[-systemComponent <URI URI ...>]
[-systemLanguage <la-co la-co ...>]
[-systemOperatingSystem <OS>]
[-systemOverdubOrSubtitle <overdub|subtitle>]
[-systemRequired <Req Req ...>]
[-systemScreenDepth <screen depth>]
[-systemScreenSize <widthXheight>]
[-standard|-av|-isma|-3gpp]
[-b <pktSize>]
[-f <bitRate>]
[-g minBuffer|maxBuffer|time <t>|size <k>|min <t> <k>|max <t> <k>]]
[-y <bitRate>]
[-z minBuffer|maxBuffer|time <t>|size <k>|min <t> <k>|max <t> <k>]]
An explanation of the various command line options follows.
<input> |
input file name. Valid input files are:
WMF file |
If no other parameter is provided then the extension
will be changed from .wmf to .mp4. |
XMT-O file |
If no other parameter is provided then the extension
will be changed from .xml to .mp4. |
XMT-A file |
If no other parameter is provided then the extension
will be changed from .xml to .mp4. |
MPEG-4 binary file |
If no other parameter is provided then the extension
will be changed from .mp4 to .xml. |
|
<MPEG-4.mp4> |
MPEG-4 binary file name. |
<XMT-O.xml> |
optional XMT-O file name. If one is not provided then
the XMT-O file will not be generated. If an XMT-O file is
the input then this parameter is ignored. |
<XMT-A.xml> |
optional XMT-A file name. If one is not provided then
the XMT-A file will not be generated. If an XMT-A file is
the input then this parameter is ignored. |
<Hinter.mp4> |
optional MPEG-4 Hinter file name. Hinted MPEG-4 is file
for a server like VideoCharger for unicast/multicast over
RTP. |
<M4Mvr.mv4> |
optional MPEG-4 MVR file name. MPEG-4
MVR file for streaming over an HTTP server. |
<M4Mux.m4x> |
optional MPEG-4 Multiplex file name. MPEG-4 Multiplex
file for streaming over an HTTP server. |
<XMT-O.xsd> |
optional XMT-O schema file. The name to be used for the
XMT-O output file. If an XMT-O file is not output then this
parameter is ignored. NOTE: the schema file name should
be in the format of a URL name. For example: 'xmt-o.xsd',
'http://www.ibm.com/xmt-o.xsd' or 'file:///c:/xmt-o.xsd'.
If one is not specified then the default is 'xmt-o.xsd'. |
<schemas/o/> |
optional path to an xmt-o schema file. This path will
be used before the default one while looking for the schema.
The default is 'schemas/xmt-o/'. |
-[no]ValidateXmto |
optional flag for validation of the XMT-O file. Default
is to validate the XMT-O file. |
<XMT-A.xsd> |
optional XMT-A schema file. The name to be used for the
XMT-A output file. If an XMT-A file is not output then this
parameter is ignored. NOTE: the schema file name should
be in the format of a URL name. For example: 'xmt-a.xsd',
'http://www.ibm.com/xmt-a.xsd' or 'file:///c:/xmt-a.xsd'.
If one is not specified then the default is 'xmt-a.xsd'. |
<schemas/a/> |
optional path to an xmt-a schema file. This path will
be used before the default one while looking for the schema.
The default is 'schemas/xmt-a/'. |
-[no]ValidateXmta |
optional flag for validation of the XMT-A file. Default
is to validate the XMT-A file. |
-[no]convert |
optional flag to perform validation only. The input file
will be validated but not converted. Default is to perform
the conversion. |
-[no]Gui |
flag to display the window user interface or run in command
line batch mode. Default is to run in the command line batch
mode. If there are no arguments then the default is to run
the window user interface. |
<logfile.txt> |
optional file name where messages will be logged. If one
is not provided then any message will be printed on the
console. |
-e (4|3|2|1|0) |
level for error messages.
4 |
only fatal error messages will appear. |
3 |
error and fatal error messages will appear, default. |
2 |
warning, error and fatal error messages will appear. |
1 |
trace, warning, error and fatal error messages will
appear. |
0 |
OK, trace, warning, error and fatal error messages
will appear. |
|
[class list] |
optional list of classes to trace. Only works if trace
level for messages is supported. |
-? |
short help information. |
-?? |
long help information. |
-meter|-pixel |
optional flag to indicate that the XMT-O generated from
the WMF (Windows Metafile Format) file should be in meter metrics
or pixel metrics. Default is meter 'meter'. |
(size|%) |
optional scaling factor to be used in the XMT-O file from
the WMF file. It can be specified as a raw size or as a
percentage of the original. To indicate a percentage of
the original suffix the numeric value with a percent sign
(%). Default is '100%'.
size |
the XMT-O layout size is scaled to the width provided
in the size value. The scene is sized to fit the presentation
window. |
% |
the XMT-O layout size is obtained from the WMF file.
The scene size is scaled to the percentage of the
size value found in the WMF file. |
|
-bmp|-nobmp |
optional flag to indicate whether external bitmap files
should be generated in addition to the JPEG files generated
from images found in the WMF files. The name and location
of the BMP files is the same as for the JPEG files with
the .bmp extension. Default is to not generate the BMP files. |
<imgDir> |
directory where the image files will be created. This
is either an absolute path location or relative to the current
execution directory. E.g. 'c:\XMT-O Source Dir\multimedia\'
or '..\XMT-O Source Dir\multimedia\'. Default is to place
the image files in the current execution directory. |
<imgDirOff> |
directory offset from the location of the
in the XMT-O file. This is the prefix used file location
of the source attribute on the image element. E.g. <img
src="multimedia\image.jpg">. Default is to not use a
prefix. |
-q
<test1[=<true|false>]
test2[=<true|false>]
...> |
optional. Use this flag to manually set defaultState
attributes of customTest elements. The custom test element
has a value of true or false, default is true. |
-xmtaMediaPrefix <url prefix> |
Prefix added to the XMT-A StreamSource url attribute. The
url is constructed from the XMT-O media src attribute. This
allows prefixing the url attribute to indicate a different
location for the XMT-A document. This only applies to
relative paths src attributes. By default the path of the
XMT-O document is used. |
-systemAudioDesc <on|off> |
Whether or not audio descriptions should be
rendered. Valid values are 'on' or 'off'. Default value is
off. |
-systemBitrate <bitrate> |
Indicate the bandwith in bits per seconds, available to the
system. Valid values are integers greater than 0. Default
value is 5000000. |
-systemCaptions <on|off> |
Specify whether a text equivalent of the audio portion of
the presentation is displayed. Valid values are 'on' or
'off'. Default value is off. |
-systemComponent <URI URI ...> |
Indicate a URI that identifies a component of the playback
system, e.g. user agent component/feature, number of audio
channels, codec, HW MPEG decoder, etc. Valid values are
strings containing one or more whitespace separated URI's. |
-systemCPU <cpu> |
Specify the CPU on which the user agent may be running.
Valid value names come from the _PR_SI_ARCHITECTURE constants
defined by the mozilla project. Default is system specific.
Valid CPU values are: |
alpha, arm, arm32, hppa1.1, m68k, mips, ppc, rs6000, vax, x86, or unknown. |
|
-systemLanguage <la[-co] la[-co] ...> |
Specify the language-country codes. This implementation uses
two letter codes. Where la represents the language code and
co represents the country code. e.g. en specifies the
english language. en-gb specifies the english language (en)
with Great Britian (gb) as the country. Valid values are a
defined in [RFC1766]. Default is system specific.
The valid language codes are: |
aa, ab, af, am, ar, as, ay, az, ba, be, bg, bh, bi, bn, bo,
br, ca, co, cs, cy, da, de, dz, el, en, eo, es, et, eu, fa,
fi, fj, fo, fr, fy, ga, gd, gl, gn, gu, ha, he, hi, hr, hu,
hy, ia, id, ie, ik, is, it, iu, ja, jw, ka, kk, kl, km, kn,
ko, ks, ku, ky, la, ln, lo, lt, lv, mg, mi, mk, ml, mn, mo,
mr, ms, mt, my, na, ne, nl, no, oc, om, or, pa, pl, ps, pt,
qu, rm, rn, ro, ru, rw, sa, sd, sg, sh, si, sk, sl, sm, sn,
so, sq, sr, ss, st, su, sv, sw, ta, te, tg, th, ti, tk, tl,
tn, to, tr, ts, tt, tw, ug, uk, ur, uz, vi, vo, wo, xh, yi,
yo, za, zh, or zu. |
The valid country codes are: |
AF, AL, DZ, AS, AD, AO, AI, AQ, AG, AR, AM, AW, AU, AT, AZ,
BS, BH, BD, BB, BY, BE, BZ, BJ, BM, BT, BO, BA, BW, BV, BR,
IO, BN, BG, BF, BI, KH, CM, CA, CV, KY, CF, TD, CL, CN, CX,
CC, CO, KM, CD, CG, CK, CR, CI, HR, CU, CY, CZ, DK, DJ, DM,
DO, TL, EC, EG, SV, GQ, ER, EE, ET, FK, FO, FJ, FI, FR, FX,
GF, PF, TF, GA, GM, GE, DE, GH, GI, GR, GL, GD, GP, GU, GT,
GN, GW, GY, HT, HM, HN, HK, HU, IS, IN, ID, IR, IQ, IE, IL,
IT, JM, JP, JO, KZ, KE, KI, KP, KR, KW, KG, LA, LV, LB, LS,
LR, LY, LI, LT, LU, MO, MK, MG, MW, MY, MV, ML, MT, MH, MQ,
MR, MU, YT, MX, FM, MD, MC, MN, MS, MA, MZ, MM, NA, NR, NP,
NL, AN, NC, NZ, NI, NE, NG, NU, NF, MP, NO, OM, PK, PW, PS,
PA, PG, PY, PE, PH, PN, PL, PT, PR, QA, RE, RO, RU, RW, KN,
LC, VC, WS, SM, ST, SA, SN, SC, SL, SG, SK, SI, SB, SO, ZA,
GS, ES, LK, SH, PM, SD, SR, SJ, SZ, SE, CH, SY, TW, TJ, TZ,
TH, TG, TK, TO, TT, TN, TR, TM, TC, TV, UG, UA, AE, GB, US,
UM, UY, UZ, VU, VA, VE, VN, VG, VI, WF, EH, YE, YU, ZM, or
ZW. |
|
-systemOperatingSystem <os>
| Specify operating the user agent may be running.
Valid os value names come from the _PR_SI_ARCHITECTURE
constants defined by the mozilla project. Default is system
specific. Default is system specific.
Valid Operating System value names are: |
aix, beos, bsdi, dgux, freebsd, hpux, irix, linux, macos,
ncr, nec, netbsd, nextstep, nto, openbsd, openvms, os2,
osf, palmos, qnx, sinix, rhapsody, sco, solaris, sonly,
sunos, unixware, win16, win32, win9x, winnt, wince, or
unknown. |
|
-systemOverdubOrSubtitle <overdub|subtitle> |
Specify whether subtitles or overdub is rendered.
Overdub selects for substitution of one voice track for
another, and subtitle means that the user prefers the display
of text in language other than which is being used in the
audio track. Valid values are 'overdub' or 'subtitle'.
Default value is overdub. |
-systemRequired <Req Req ...> |
Provides an extension mechanism for new elements or
attributes. Valid values are a list of white-spaced,
separated namespace prefix language extensions. |
-systemScreenDepth <depth> |
Specify the depth of the screen color palette in bits
required for displaying the element. Valid values are
integers greater than 0. Default is system specific. |
-systemScreenSize <widthXheight> |
Specify the screen screen size on which the user agent may
be running. The x separator is case insensitive. Valid
values are widthXheight. eg. 1024X768 or 176x144. NOTE:
xml document has the width and height reversed, i.e.
heightXwidth. Default is system specific. |
-standard | -av | -isma | -3gpp |
optional flag for determining the hinting format. The
default is "standard". The various options are:
standard |
hint the entire file. |
av | only hint the audio and video tracks. |
isma |
hint the audio and video tracks in ISMA format. |
3gpp |
hint the audio and video tracks in 3GPP format. |
|
-b <pktSize> |
Maximum RTP packet size. The default is 1024 bytes. |
-f <bitRate> |
Anticipated client connection speed for MPEG-4 MVR
file. This parameter is optional. The default is 104857600
bit/sec. |
-g (minBuffer | maxBuffer | time <t> |
size <s> | min <t> <s> | max <t>
<s>) |
Set constraints for the download buffering. A minimum
amount of buffering offers a just-in-time delivery of
content. A maximum amount of buffering provides the earliest
possible delivery of media content. This would fill up
a buffer to the extent of the maximum possible bandwidth.
This will help mask network glitches which would not be
possible in the just-in-time delivery, but could create
extremely large buffers in networks with large bandwidth.
Within these minimum and maximum buffer sizes, limits
can be set on the amount of buffer space used. Buffer
size can be limited based on a size limit value or an
estimated playback time limit value. Both of these buffer
size limiting values are constrained by the minimum and
maximum buffer amount values.
minBuffer |
minimum buffer size |
maxBuffer |
maximum buffer size |
time <t> |
buffer size limit based on an estimated playback
time. The default with a 5 second buffer (time 5.0). |
size <k> |
buffer size limit based on a maximum size value. |
min <t> <s> |
buffer size limit based on the lesser of an estimated
playback time and maximum size value. |
max <t> <s> |
buffer size limit based on the greater of an estimated
playback time and maximum size value. |
The time and size values are in the form:
<t> |
Time in seconds as a decimal value. e.g. "time 5.3" |
<s> |
Size in bytes as a integer value. e.g. "size 10000" |
|
-y <bitRate> |
Anticipated client connection speed for MPEG-4 Multiplex
file. This parameter is optional. The default is 104857600
bit/sec. |
-z (minBuffer |
maxBuffer | time <t> |
size <s> | min <t> <s> | max <t>
<s>) |
Set constraints for the download buffering. A minimum
amount of buffering offers a just-in-time delivery of
content. A maximum amount of buffering provides the earliest
possible delivery of media content. This would fill up
a buffer to the extent of the maximum possible bandwidth.
This will help mask network glitches which would not be
possible in the just-in-time delivery, but could create
extremely large buffers in networks with large bandwidth.
Within these minimum and maximum buffer sizes, limits
can be set on the amount of buffer space used. Buffer
size can be limited based on a size limit value or an
estimated playback time limit value. Both of these buffer
size limiting values are constrained by the minimum and
maximum buffer amount values.
minBuffer |
minimum buffer size |
maxBuffer |
maximum buffer size |
time <t> |
buffer size limit based on an estimated playback
time. The default with a 5 second buffer (time 5.0). |
size <k> |
buffer size limit based on a maximum size value. |
min <t> <s> |
buffer size limit based on the lesser of an estimated
playback time and maximum size value. |
max <t> <s> |
buffer size limit based on the greater of an estimated
playback time and maximum size value. |
The time and size values are in the form:
<t> |
Time in seconds as a decimal value. e.g. "time 5.3" |
<s> |
Size in bytes as a integer value. e.g. "size 10000" |
|
For example:
XmtBatch sample.xml
XmtBatch sample.xml -a sampleA.xml -m sample.mp4 -noGui
|
|
 |