UMP (Unified Media Platform)

13.1 Status Overview

 

The Web Interface provides an intuitive, versatile means of configuring and managing the UMP and the media stored on it. Its functionality ranges from configuration options for the OSD over power management, file management, executing tasks on the device remotely and even controlling the device with the WebRemote.

 

When accessing the Web Interface, the initial page displays a brief summary of the device’s current status, including available disk space, future scheduled recordings, EPG availability and the current date and time. Below is an overview of the information and options presented on this page:

 

-         UMP Web Status as of […]: This displays the current date and time that the device is set to. Although the UMP devices automatically synchronize the by default, it is recommended to check that the time and date shown here match your timezone and are correctly adjusted. The EPG and scheduled recordings rely entirely on the date and time function, not on any time or ShowView information provided in the TV signal.

 

-         UMP Recording server is […]: This indicates whether the UMP recording server is running. If this is not the case, no recordings can take place.

 

-         The EPG listings […]: This indicates the availability of the EPG for the next 24 hours. If less than 24 hours of EPG data is loaded, a warning will be displayed in red, informing you roughly how many hours are still in the EPG cache.

 

-         […] programs scheduled to record: Here you can see how many recordings are scheduled. Note that favorites are only listed if they occur in the EPG data currently loaded.

 

-         […] of […] MB free in /mnt/data/Recordings: This indicates the amount of free space on the disk in which the TV_RECORD_DIR resides.

 

Below the status overview is a link to the WebRemote, which is discussed later in this chapter and a search entry field for the EPG, explained in section 3.

13.10 Network Settings

 

Network

 

This page allows you to configure the basic networking properties of the device, such as its IP address, subnet mask, gateway address, DNS servers, hostname and connection protocol (DHCP or static). It is recommended to use DHCP, though the device can be configured entirely statically. An overview of the parameters is presented below:

 

 

Hostname

Here you can specify a hostname for the device to use. Unless you have more than one UMP, it is recommended to keep the default name 'UMP'.

IP Address Settings

Here you can specify whether the device should retrieve an IP from a DHCP server or use static details.

IP Address

Here you can see the device's current IP address and specify a new one.

Subnet Mask

Here you can see the device's current subnet mask and specify a new one.

Gateway

Here you can see the device's current default gateway and specify a new one.

DNS Server #1

Here you can see the device's current primary DNS server and specify a new one.

DNS Server #2

Here you can see the device's current secondary DNS server and specify a new one.

DNS Domain

Here you can see the device's current DNS domain name and specify a new one.

 

 

When you select static IP addressing, the entry fields for the various required parameters should be enabled. Note that this function does not work in all browsers that do not fully support JavaScript. It is recommended to use the device’s Web Browser in case of any problems.

 

Once the required changes have been made, select the Apply Settings button below the input fields. A popup will appear, asking for confirmation whether the changes should be applied. If you answer yes, the device will attempt to restart the networking subsystem, which may take up to 3 minutes.

13.11 Using the Web Remote

 

As well as the remote control, game controller and HID input support, you can use any web browser or web capable device to control the UMP with the Web Remote.

 

The Web Remote of the device features the same basic features as the common remote control (UMP-R-1XX), though it only communicates with the OSD, and thus cannot be used to start it or operate Desktop Mode applications. When in the OSD, most common functions can be used. A small diagram of the Web Remote and its controls is presented below:

 

 

Up

 

Left

Enter

Right

 

Down

 

 

 

 

Exit

A. Select

Help

Menu

Record

Eject

 

 

 

 

Play

 

Rewind

Pause

F.Forward

 

Stop

 

 

 

 

Vol+

Mute

Ch+

Vol-

 

Ch-

 

Color buttons, labeled as R, G, Y and B:

 

Red

Green

Yellow

Blue

 

All controls listed in the Web Remote correspond to the identical buttons on the remote control (UMP-R-1XX) or their equivalent on the other remote types (UMP-R-2XX, UMP-R-3XX), except for the fact that they only operate the OSD.

 

Note that you may need to disable your popup blocker or allows popups from the Web Interface to open the Web Remote.

13.2 Viewing Log Files

 

Many devices which provide partially similar functionality do not provide facilities to monitor or debug the individual functions of the device. The UMP devices are almost unique in the sense that they provide full detailed logging for practically all the device’s functions and, if desired, can produce highly verbose debug output.

 

The device’s log files are listed in the Logs section of the Web Interface. By default the ‘ump.log’ file will be loaded in the log viewer with a 22 line output, though you can select any one of the log files from the Log File drop down menu on the left side above the main textbox.

 

Below is a brief overview of the available log files. Please note that these logs will display extremely verbose output, if configured, about the Python scripts that are responsible for most of the device’s functionality. Python is a very flexible, well known programming language and its entire functionality goes beyond the scope of this document. Although no Python knowledge or experience is required to use this device, it can help while trying to understand the logfile’s output. For more information on Python, visit the official documentation at http://python.org.

 

This information may appear complicated, and is only provided for advanced users or when you need to contact UMP support.

 

cache-103.log

This logfile displays the Media Cache helper’s activities and the resulting effects. It should always be present in this list. Check this logfile if rebuilding the cache fails or misses items.

commdetectserver-103.log

This logfile displays the Commercial Detection server’s progress and output. It should always be present in this list. Check this logfile if commercial detection fails.

encodingserver-103.log

This logfile displays the Encoding server’s progress and output. It should always be present in this list. Check this logfile if re-encoded videos contain faults or when there are problems with re-encoding.

main-103.log

This logfile displays the OSD’s progress and output. It should always be present in this list. Check this logfile in case of anomalies in the OSD. Even if the error relates to another service, it’s recommended to look here first.

recordserver-103.log

This logfile displays the Recording server’s progress and output. It should always be present in this list. Check this logfile if recordings don’t take place, or recorded videos contain faults.

 


 

13.2 Viewing Log Files (continued)

 

Below is a continuation of the logfile overview presented on the previous page.

 

 

schedulefavorites-103.log

This logfile displays the ‘schedule_favorites’ helper’s progress and output. It should always be present in this list. Check this logfile if recordings don’t take place.

tv_grab-103.log

This logfile displays the ‘tv_grab’ helper’s progress and output. It should always be present in this list once the EPG has been updated. Check this logfile if there are problems with the EPG functionality.

ump.log

This logfile represents a filtered but comprehensive overview of the device’s startup sequence and regular tasks such as updating the EPG or synchronizing the time with an NTP server on the Internet.

webconfig-103.log

This logfile displays a changelog of the device’s main configuration file. It should always be present in this list once any configuration has been performed in the web interface. It can be helpful when trying to trace back a setting that caused an error or other unexpected behavior. Simultaneously, it can also provide a reference as to when which settings were changed in a multi-user environment.

webserver-103.log

This logfile displays the progress and output of the device’s web service. It should always be present in this list. Check this file in case of errors in the web interface.

 

Additionally, there are a number of logfiles which are generated when specific tasks or applications are executed. If debugging is enabled, every MPlayer instance, game emulator and even some of the Helpers and Commands will produce logfiles, allowing you to examine their progress and output. A few examples of these logfiles are listed on the next page.

 

Some of these include a long number, indicated as ‘[…]’ in the examples, which is the UNIX time notation of the time and date when the process was initiated. The UNIX timestamp is a unified way of expressing time and date by a number of seconds elapsed since an arbitrary event, the beginning of the UNIX epoch, which corresponds to the 1st of January, 1970, according to the Gregorian calendar. The UMP’s Linux operating system also uses the UNIX timestamp.

 

For more information on the UNIX timestamp, see its Wikipedia article at: http://en.wikipedia.org/wiki/Unix_timestamp.

 

13.2 Viewing Log Files (continued)

 

Another common UNIX convention is the use of the file descriptors STDERR and STDOUT. You may have also heard of STDIN, though it is not relevant for the output of an application or command. If you are already acquainted with these conventions you can skip this section. For the purpose of this explanation, you can consider STDERR and STDOUT as ‘channels’, where an application can ‘send’ its output. Generally, STDERR is used for errors and STDOUT is used for regular logging and output. When a command or application is launched it will almost always create both a STDERR and STDOUT logfile. If there are no (serious or critical) errors, the STDERR file should remain empty.

 

Below is a list of other logfiles that are not necessarily present in all configurations.

 

command-stderr-103-[...].log

These logfiles indicate a command’s errors when launched from the Commands menu in the OSD.

command-stdout-103-[...].log

These logfiles indicate a command’s output and progress when launched from the Commands menu in the OSD.

dosbox-stderr-103-[...].log

These logfiles indicate DOSbox’s errors when launched from the Games menu in the OSD.

dosbox-stdout-103-[...].log

These logfiles indicate DOSbox’s output and progress when launched from the Games menu in the OSD.

recorderstderr.log

This logfile indicates any anomalies or messages during a recording. Note that the recording server log should list these events, and this logfile should remain empty.

recorderstdout.log

This logfile indicates any errors which occurred during a recording. Note that the recording server log should list these events, and this logfile should remain empty.

mame-stderr-103-[…].log

These logfiles indicate a MAME’s errors when launched from the Games menu in the OSD.

mame-stdout-103-[…].log

These logfiles indicate a MAME’s output when launched from the Games menu in the OSD.

makelogos-103.log

This logfile indicates the progress and result of the ‘makelogos’ Helper script which retrieves the logos for the selected channels in the EPG.

makestationlist-103.log

This logfile indicates the progress and result of the ‘makestationlist’ Helper script which builds a list of TV channels for the TvTime application

 


 

13.2 Viewing Log Files (continued)

 

Below is the continuation of logfile listing mentioned on the previous page.

 

mplayer-stderr-103-[…].log

These logfiles indicate MPlayer’s errors when launched from the OSD.

mplayer-stdout-103-[…].log

These logfiles indicate MPlayer’s output and progress when launched from the OSD.

psX-stderr-103-[….].log

These logfiles indicate psX’s output and progress when launched from the Games menu in the OSD.

psX-stdout-103-[….].log

These logfiles indicate psX’s errors when launched from the Games menu in the OSD.

videothumb-103.log

This logfile is created if the ‘video_thumbnail’ Helper is started. It indicates the progress and results of the thumbnail creation process.

zsnes-stderr-103-[…].log

These logfiles indicate zSNES’s errors when launched from the Games or Commands menu in the OSD.

zsnes-stdout-103-[…].log

These logfiles indicate zSNES’s output and progress when launched from the Games or Commands menu in the OSD.

 

To view any one of these logfiles, select it from the Log File drop down menu. Note that logfiles containing a timestamp are logs that will only be used for the output of that particular instance of the application. If it is launched again afterwards, it will create a new log file with a new timestamp.

 

Above the main textbox with the logging information there are a number of controls which are explained below.

 

-         Refresh: This refreshes the currently selected logfile without reloading the entire page.

-         Refresh Delay: This allows you to specify after how many seconds a logfile should be refreshed automatically.

-         Rows: Here you can specify how many rows should be displayed.

 

Because logfiles tend to accumulate after a while of usage, you can clear out all the temporary log files, while leaving the main logs intact by selecting ‘log_cleaner’ under Plugins -> Helpers in the Web Interface.

 

It is recommended to make a copy of the relevant logfile output if an error is determined. Please note that UMP support may ask for a copy of the device’s log files to assess the cause or nature of the problem.

13.3 EPG and Recording Functions

 

Both navigating through the EPG and scheduling recordings can be achieved in the Web Interface as well as the OSD.

 

The EPG and recording functions in the Web Interface are distributed over 4 or 5 pages, where the last page, ‘Search’, is disabled by default. To enable the Search page, activate it by modifying the WWW_PAGES variable in the Web Interface under Settings -> Www. Alternatively, you can enable it as a personal page under

WWW_PERSONAL_PAGE. The other 4 pages are EPG, Scheduled Rec, Manual Rec and Favorites.

 

 

EPG

 

The EPG page provides a similar layout to the TV Guide overview in the TV Menu of the OSD, showing a timeline moving from left to right and a vertical list of the configured channels. Navigating through the EPG can be performed in a number of ways which are explained below:

 

-         Select a time and day in the top left hand corner above the EPG and press the View button.

-         Select the ‘<<’ or ‘>>’ symbols on the left and right hand side of the timeline to navigate backward and forward through the EPG.

-         Select a category from the Category drop down menu above the EPG.

-         Select a channel in the EPG to see all remaining data for it.

-         Enter a search term in the Search box below the EPG. This function searches through the entire EPG for occurrences of the desired term(s). Optionally, you can place a tick in Movies only, though not all movies are labeled as such in the XMLTV data.

 

Note that the Category function relies on the presence of category information in the EPG data, though not all XMLTV sources provide this.

 

 The same information that is made available for individual TV programs can also be displayed in the Web Interface by clicking on the desired item. An info dialog including the program’s start time, stop time, length and description should be displayed. Just below the start and stop times there are three buttons which allow you to close the dialog or add the item to the Scheduled Recordings or Favorites. Any changes made here are directly visible in the OSD and vice versa.


 

13.3 EPG and Recording Functions (continued)

 

Recording Functions

 

As mentioned on the previous page, you can schedule an item for recording or add it to the favorites simply by clicking on it and selecting the corresponding option. The Web Interface offers the same functionality for manual recordings as the OSD.

 

To schedule a recording, access the Web Interface and navigate to Manual Rec.  Here you can see the same parameters as in the OSD within the Manual Recording menu entry. Below is a brief list of the individual controls and their functions:

 

-         Channel: Here you can select the desired channel to record from.

-         Start Time: Here you can specify the date and time to start recording.

-         Stop Time: Here you can specify the date and time to stop recording.

-         Title: Here you can specify a title for the file in the OSD.

-         Program Description. Here you can specify a description which can be displayed in the OSD.

 

To add the recording job, select Add to Recording Schedule at the bottom of the page. Note that the Start Time may be in the past, though the Stop Time must be at least 3 – 5 minutes in the future. If you add a recording schedule with a start time in the past, the recording should start within approximately five seconds.

 

To view all scheduled recordings or cancel a currently recording program, navigate to Scheduled Rec in the Web Interface. The Scheduled Rec page displays a list of scheduled recordings, including the start and stop time details, where future recordings are listed in black and the currently recording program (if any) is listed in red. You can cancel the current recording by selecting Remove on the right hand side of the recording item.

 

 

Favorites

 

To manage favorites in the Web Interface, navigate to Favorites. Here you should see list of configured favorites (if any are configured). Here you can configure duplicate detection, priority, episode handling or the item’s name (displayed both in the Web Interface and the OSD).