Metadata describing the structure of a (at least partially) encrypted input sample. A buffer's data is considered to be partitioned into "subSamples", each subSample starts with a (potentially empty) run of plain, unencrypted bytes followed by a (also potentially empty) run of encrypted bytes. numBytesOfClearData can be null to indicate that all data is encrypted. This information encapsulates per-sample metadata as outlined in ISO/IEC FDIS 23001-7:2011 "Common encryption in ISO base media file format files".
|iv||A 16-byte initialization vector|
|key||A 16-byte opaque key|
|mode||The type of encryption that has been applied,
|numBytesOfClearData||The number of leading unencrypted bytes in each subSample.|
|numBytesOfEncryptedData||The number of trailing encrypted bytes in each subSample.|
|numSubSamples||The number of subSamples that make up the buffer's contents.|
Returns a string containing a concise, human-readable description of this object.
A 16-byte initialization vector
A 16-byte opaque key
The number of leading unencrypted bytes in each subSample.
The number of trailing encrypted bytes in each subSample.
The number of subSamples that make up the buffer's contents.
Returns a string containing a concise, human-readable description of this object. Subclasses are encouraged to override this method and provide an implementation that takes into account the object's type and data. The default implementation is equivalent to the following expression:
getClass().getName() + '@' + Integer.toHexString(hashCode())
See Writing a useful
if you intend implementing your own