
DTS-HD Master Audio Suite™,
User Guide
v 2.5
Confidential - Do NOT Duplicate 49 DTS Document No.: 9301F55800D
17781 v1
difficult to decipher. (See StreamTools File Info portion of this manual for details) As an aid, the
encoder automatically places a Log file that contains all information used to create the encoded file in the
same
directory as the encode for future reference. A DTSPBR file can also be created in the
same fashion by checking the Auto PBR option from the Options menu.
The log file contains all information that the Encoder used to create the resulting encode plus any other
notable information that arose during the encode process. When an Encode is created, a log file is placed
in the same
directory as the encoded file. The log file will share the same name as the encoded
file with the extension (_log.txt).
Warning: Log files are not protected and can be edited. Thus, information
contained within the LOG FILES SHOULD BE BACKED UP!
7.6.1 Encode Settings
The Encoder Settings portion of the log file contains all of the information the Encoder used to create the
resulting Encode. This includes the full path of the input material and output destination. The
destination type, stream type, sample rate, bit width, constant bit rate, dialog normalization, timecode
parameters, button options, downmix coefficients, and program information. This is a quick way to
determine what settings were used to create the encoded file. The Encode Settings is located at the
beginning of the log file and will makeup most all of the information provided in most log files.
7.6.2 Encode Results
The Encode Results portion begins at the bottom of the log file directly below the downmix information
section. It contains information about events that occurred in the encoder once the encoded file began
processing. There are three type of information that can display here; MD5 Verification, PBR
information, and Saturations Warnings. (See the three sections below for details)
7.6.3 MD5 Validation
MD5 data verification code: This letter/number code allows a user to late validate that the encoded file is
identical to the original encoded file. Data can be lost during file transfers, thus an MD5 check should be
run on any encoded file that has been transferred and the new MD5 letter/number code should be cross
referenced with the original letter/number code to ensure they match. If the codes do not match the
transferred encode should be considered corrupt and the transfer should be done again. (some chip sets
in external hard-drives will cause corrupt data transfer) The MD5 data verification check should be
performed if an encoded file has been transferred from the original encode location.
7.6.4 PBR Data in Log Files
When the option is checked and a Master Audio stream is encoded, a Peak Bit
Rate analysis is performed on the encoded file and a ‘.dtspbr’ file is created in the destination directory.
Comentários a estes Manuais