General setup

The general section is where you will set up the major information related to the master backend, job scheduling, and default locale information. It is setup in a sequential design with Back and Next buttons. You can also use the underlined letters with alt to move around. i.e., alt-N is ``Next'', alt-B is ``Back'', alt-C is ``Cancel'', and alt-F is ``Finish''.

Host Address Backend Setup

The first screen of the General configuration deals with IP addresses of the backend system that you're running mythtv-setup on. If you are setting up only one backend/frontend installation, then the default values are fine and you can move to the next page by pressing Enter. If you need to move around the screen, use the arrow keys to move focus between settings.

The default value shown on install will be 127.0.0.1, which is the internal loopback for the local machine. If you plan on deploying multiple backends, running mythweb from another computer, or if your backend is on one system and you're running the frontend on another machine then do not use the ``127.0.0.1'' IP address. Set this to the IP address of the backend as recognised by other machines on your network. If you are using a router on your network that only hands out dynamic addresses, you might consider setting up this machine with a static IP address instead (<ie /etc/network/interfaces >).

NOTE: If you modify the 127.0.0.1 address and use a ``real'' IP address, you must use real IP addresses in both fields, otherwise your frontend machines will generate ``Unexpected response to MYTH_PROTO_VERSION'' errors.

Changing any of the port settings is very strongly discouraged. (If you do accidentally change them, the defaults are 6543 for the master/backend server, and 6544 for the HTTP requests)

Once you're satisfied with the values, move the focus down to Next and hit Enter.

Mythbuntu Host Address Backend Setup

Figure: Mythbuntu Host Address Backend Setup

 

Locale Settings / Global Backend Setup

These screen, on a master backend, will change settings that affect all backends.

TV format:
NTSC, NTSC-JP, PAL, PAL-60, PAL-BG, PAL-DK, PAL-D, PAL-I, PAL-M, PAL-N, PAL-NC, SECAM, SECAM-D, SECAM-DK

Your TV standard should be determined based on your locale. US users should choose NTSC. European users should chose PAL (or try PAL-BG in most of Western Europe except for PAL-I in UK or Ireland).

The Vertical Blanking Interrupt (VBI) Format is used for closed Teletext and Closed Captioning.
PAL Teletext or NTSC Closed Caption

The channel frequency table is also based on your locale. There is a try-all option but using this will slow down channel scanning.

US and Canadian users using Schedules Direct can skip the time offset for xmltv listings. International users will need to set this appropriately so that their data matches up at the correct time.

Mythbuntu Global Backend Setup

Figure: Mythbuntu Global Backend Setup

 

Miscellaneous Settings

File Management Settings
The defaults should be OK except for enable Follow symbolic links when deleting files to prevent recording files left on disk when you want them removed.

WAS: Directory path setup, ie selecting /var/lib/mythtv, but replaced by improved Storage Group management

For Storage Group directories, if you used a non-default location, be sure and set the ownership and permissions to match /var/lib/mythtv (ie mythtv:mythtv).

If for some reason you chose a file system other then XFS or JFS for storage, choose to delete the files slowly. This will avoid some nasty bugs related to using ReiserFS or ext3.

Miscellaneous Settings

Figure: Host-specific Backend Setup 


EIT Scanner Options

The EIT scanner is used to gather data on the fly. If you have a DVB based source or a source providing this data, you will configure it here

EIT Scanner Options

Figure: EIT Scanner Options


Shutdown/Wakeup

The Shutdown/Wakeup options are used for suspending or shutting down the backend server when it has been idle for the set limit. You can configure the master and/or secondary backend(s) to go into a sleep, suspend, or shutdown mode when not in use- depending on the capabilities of your motherboard.

There are different methods you can use to accomplish this. A tutorial on ACPI wakeup/shutdown can be found on the ACPIWake page https://help.ubuntu.com/community/MythTV/Install/WhatNext/ACPIWake. You should complete MythTV installation and ensure the backend is properly functioning before trying to set up this function.

Mythbuntu Shutdown/Wakeup Options

Figure: Mythbuntu Shutdown/Wakeup Options


WakeOnLan

WakeOnLan is another method of configuring secondary backends to wakeup. https://help.ubuntu.com/community/WakeOnLan

Backend Wake-On-LAN

Figure: Backend Wake-On-LAN


Host Specific Job Queue

The Host Specific Job Queue sets up the types of jobs that are allowed to run on this machine. If you have multiple backends, you can configure certain backends to only handle particular types of jobs. This is especially useful if some are much more underpowered then others.

It isn't recommended to have more then 2 simultaneous jobs running on any backend at any given time.

The default job queue frequency of 60 seconds is adequate and typically doesn't need to be changed.

Unless this backend is dedicated to only Transcoding/Commercial flagging jobs, don't change the CPU usage. Anything set higher then ``Low'' may jeopardize the ability to record programs due to being starved for IO/CPU usage.

Host Specific Job Queue

Figure: Host Specific Job Queue


Global Specific Job Queue

The Global Specific Job Queue sets up things affecting any and all backends on a mythtv network.

If you don't check ``Run Jobs only on original recording host'', each of the jobs will be evenly distributed against possible backends. This will lessen the load on each machine.

A decently powered backend with hardware encoding cards (1Ghz+) should be able to flag commercials at the same time as the recording is going. This helps if you ever plan to time shift your recording viewing by 10 or 20 minutes and want to have the commercials flagged as you watch.

Typically you won't want to run your transcode jobs before commercial flagging. The idea should be that you will flag commercials, verify they are right and manually queue them up to be transcoded and removed. If you have a particular reason to transcode first, check this box.

If you set up the backend to save the original files after transcoding, these will not be automatically deleted, but rather fill up your recordings directory with .old files. You will have to manually go in there and delete them to free up recording space as necessary.

Global Specific Job Queue

Figure: Global Specific Job Queue


Job Queue

The Job Queue page provides an area to add your own scripts to perform on recordings.

Some ideas for additional things can range from scp'ing a recording somewhere, transcoding it to fit on an ipod and copying it to a directory, or running it through a denoising filter.

Mythbuntu Job Queue Settings

Figure: Mythbuntu Job Queue Settings

NOTE: Installing package "ttf-mscorefonts-installer" is recommended to ensure that all themes display correctly.