The
org_params parameter class records attributes which control aspects
of the code-stream organization (hence the name, "ORG").
None of these attributes are actually preserved in
code-stream marker segments, but they may be established
during compression in the same manner as any other
code-stream parameter attributes, most of which do
wind up in marker segments. Tile-specific forms of
the ORG parameters exist, but component-specific forms
do not.
The cluster name is "ORG", but you are recommended
to use the macro
ORG_params, in functions which take a cluster name like
kdu_params::access_cluster.
The following attributes are defined. For an explanation
of pattern strings, consult the comments appearing
with
kdu_params::parse_string.
-
Macro =
ORGtparts; Pattern = "[R=1|L=2|C=4]" — Controls the division
of each tile's packets into tile-parts. The attribute
consists of one or more of the flags,
R,
L and
C, separated by the vertical bar character,
|. If the
R flag is supplied, tile-parts will be introduced as
necessary to ensure that each tile-part consists of
packets from only one resolution level. If
L is supplied, tile-parts are introduced as necessary
to ensure that each tile-part consists of packets from
only one quality layer. Similarly, if the
C flag is supplied, each tile-part will consist of packets
from only one component. Note that the cost of extra
tile-part headers will not be taken into account during
rate control, so that the code-stream may end up being
a little larger than you expect. By default, tile-part
boundaries are introduced only as required by the presence
of multiple
Porder attribute specifications (see
poc_params).
-
Macro =
ORGgen_plt; Pattern = "B" — Requests the insertion of packet
length information in the header of all tile-parts
associated with tiles for which this attribute is true.
The PLT marker segments written into the relevant tile-part
headers will hold the lengths of those packets which
belong to the same tile-part. Note that the cost of
any PLT marker segments generated as a result of this
attribute being enabled will not be taken into account
during rate allocation. This means that the resulting
code-streams will generally be a little larger than
one might expect; however, this is probably a reasonable
policy, since the PLT marker segments may be removed
without losing any information.
org_params {Java: Org_params}