|
Logs
Record Log: The R5000-HD
incorporates two logging functions. The first one is a basic
"Record Log" which is accessible from the "Utilities"
menu. This log basically contains an entry for each recording made along
with a dump of the statistics associated with it. The entries are: 1)
Complete filename and path where the recording was made, 2) The total
length of the recording in "hhmmss" format, 3) Number of
failed transfers, 4) Ending time.
This
log will also flag other major problems encountered while recording (more on this in the
"Troubleshooting" section). For instance, if there is lost or
corrupted data this will be notated. A "Disk Full" notification is also provided.
Menu: Utilities->"View Record Log" launches Windows Notepad for convenient viewing of
the log contents. This is useful if you have made a lot of unattended
recordings, for example, with the PVR and need to know where
they were recorded to as well as whether or not they were completed
properly. Use the "Purge Record Log" option to clear all log
entries.
The Record Log file is "log.txt" and is stored in the
installation
directory of the R5000-HD.
Remuxer Log: This log is of a much more technical nature and
contains information relating to the re-multiplexing process. This is a
complicated process of reformatting and encapsulating the MPEG2 audio
and video data into useable streams. There are a lot of factors that can
introduce errors or other problems into this process, the most common of
which are reception drop-outs and glitches. In the event that something
causes the process to go wrong, the remuxer will output its own messages
to this log file.
The messages in this log will be of a
cryptic nature to most people. Its main purpose is to provide detailed
feedback to Nextcom for troubleshooting analysis. The log file is named
"remuxer.log" and is also stored in the installation directory.
This logging feature is enabled and disabled from the
"Utilities" menu under "Remuxer Log". It is
recommended that if enabling this feature that you make your recordings
to a different physical drive if disk fragmentation is of concern. Since two
files are being simultaneously created (the log and the program), there
is the possibility of causing non-contiguous files. Whereas the stream
data will still get recorded properly, this can affect playback since
the drive may cause a latency in presenting data as the head as to skip
over unrelated blocks of data. It is usually not a problem with today's
fast drives with ample caching. Also, the remuxer log data is only
flushed out occassionaly, minimizing how often the file is written to.
|