Mythtv windows front end

For digital audio, onboard versus discrete will make no difference. The GT is currently the only card capable of bit-streaming high definition audio codecs, as found on Blu-ray discs. Software decoding of video content is entirely dependent on the CPU, so the content you want to play will determine how much or how little you need.

Standard definition content will all be fairly trivial to handle. All of which can be handled by late model P3s or better. The biggest problem dealing with digital recordings is that MythTV records them, unaltered, as they are broadcast. MythTV has no control over the resolution, quality, or bitrate, so if you are recording digital, you must size your frontend to allow for whatever the broadcaster may send.

Any non-mobile Athlon 64 or Core 2 processor will be sufficiently fast for decoding this content. Higher end Athlon XPs and Pentium 4s can handle this content as well. Atom processors will likely be too slow to manage. Older Core and Pentium M processors were generally only found on slower, mobile systems, and may be too slow as well.

DVB broadcasters are allowed to use H. It allows multi-threaded decoding, allowing multi-core processors to be used more efficiently. Higher bitrate may need faster chips beyond the base model. Unlike DVB broadcasts, the output of this device will be single sliced, meaning only one processor core can be used to decode it, presenting a more difficult challenge.

An Athlon 64 processor of at least 3GHz, or Core 2 of at least 2. There are no known pre-built versions of MythTV for Windows yet. Until then, you'll have to build it yourself by following the instructions. Now, though, setting up a MythTV system is easy. It readily supports most video capture cards, and several MythTV-centric distributions have been created based upon various Linux flavors.

Most MythTV packages install both the back and front ends by default. You can also install a front end by itself on an additional machine.

One front end is all that most users require, but some users want additional front ends scattered throughout the home. Many homes already have a Windows machine, so using one as a MythTV front end may be an obvious choice. ASX files. The stable 0. Version 0. This is not that important to me, as MythWeb really does a good job.

Stensgaard knows about this fairly rare issue and says he is working on a remedy in the next version. Another option for a MythTV front end is an original Xbox. The first 2 tables below configure where that database is located and how to access it. Hence these settings are stored in a separate configuration file config. This selection also appears if MythWelcome or MythFrontend are unable to communicate with the database.

This page will automatically be set up the first time you start the frontend. See the description above Starting the Frontend. In the event that this does not work you may have to manually enter the information here.

The information entered here is stored in Config. This page displays a list of downloadable themes from which to choose. The default theme is Terra and that will be active if you do not select anything here.

This is an optional setting, you can ignore it and continue to use the Terra theme. For some examples of themes see Theme. If the downloadable themes do not show, or to refresh the list of downloadable themes, press M and select the option to refresh downloadable themes. Note that digital output volume can only be controlled by the volume control on your TV or sound system, or by setting up a special configuration in your Linux box. The following options are only displayed if the above option is checked.

If you do not see them, turn off the above setting and turn it on again. This page allows you to customize how video is rendered. It is recommended to use the best setting available for your hardware. MythTV does not automatically determine compatibility. It will accept what you select and try to use it.

If it is not supported you will not see any video played, or it will select a default that is not optimal. Within a Playback Profile are any number of entries. Based on criteria you supply here, a method for playing video will be selected. You can chooses different methods for different types of video. When starting playback, the system scans the list from top to bottom and selects the first entry that matches the video being played. All criteria specified must match for an entry to be selected.

For a sensible setup, place more specific entries first and a generic catch-all last. You can have entries with no conditions that will be always selected. Such an entry should be last because anything after it would not be used. If no entry matches the video, or the selected methods fail because of lack of support for example if a hardware acceleration is selected but your system does not have the correct hardware , the system will select a playback method.

It may not select the best option, so one should always choose entries that will match. Rather than changing one of the default profile, you may want to create a new profile if you want to use different settings, so that the defaults are still available unchanged.

You can re-order entries by selecting M menu and moving them up or down. Order is important. When deciding which rule to use, the rules are scanned from top to bottom and the first one that matches the video is used. For all other conditions, both height and width must satisfy the condition for a match. Standard will always work but will use high amounts of CPU. The others require special hardware or software but will give better results, especially on low powered equipment.

See Deinterlacing for information on the deinterlacers. You can create playback groups and set a playback group on recording rules or existing recorded programs. This way you can have different settings for playback of different programs. Changes you make here are global across all front ends. To create a special grouping of channels, select " Create new group ", name the new group and continue.

The initial page for this group may be blank, so exit back to the "TV Settings" menu, then re-enter the Channel Groups menu. Enter into your new group, and select the channels that you want to use. If you select a group for editing you will see a list of your channels with check boxes next to each channel.

Select the channels you want included in that group. This is an optional, advanced feature. There are several screens of settings here that can be used to change recording priorities globally across the system.

Recording priorities are only relevant if you are set to record a show, and that episode is showing more than one time or on more than one channel withing the range of days for which you have listings. The system will try to record the instance of an episode that has the highest priority. If a showing of an episode is on the schedule for tonight and again next week, and the next week showing is a higher priority it will record the next week showing.

The selection of which showing to record also takes into account the number of tuners you have and whether other shows that are scheduled will be using the tuners. If they are it will choose the show with the highest priority to record first. This displays a list of all channels on all sources. By default all channels have a priority of 0. To prefer some channels over others in case the same show is on two or more channels, increase their priority.

Here you can use SQL statements to change the priority based on attributes of the program, channel, hardware, etc. There are examples that you can select, but these are examples only, you will need to modify them to make them useful. Videos can be played from the videos storage group on the backend or from local storage on the frontend.

If you are storing videos on the backend you need not fill this in, you can leave the defaults. This is the same setup page that is available in the MythTV backend setup.

Here you can dynamically change the key combinations used for controlling the frontend. Changes made here apply to this frontend only and are effective immediately. If you have a remote control that emulates a keyboard and some buttons do not work correctly you can reassign them here.

See Keybindings for a list of keys and their default assignments. Most of the values are are already set and cannot be changed. Only 1 check box is available for changing. This provides a dynamic and visible way of moving and sizing the screen layout so that it is all visible. This should only be necessary for analog televisions. Digital televisions typically have a setting in the TV set to eliminate overscan if required. This page provides a visible method for adjusting the GUI size and offset.

Jump to: navigation , search. Category : Configuring Frontend. Navigation menu Personal tools Log in. Namespaces Page Discussion.

Views Read View source View history. This page was last modified on 2 January , at Settings Page's Description. Select from one of the audio devices detected on your system. When satisfied, you can test audio before moving on. If you fail to configure audio, video playback may fail as well. There could be a great number of options available, depending on the type of audio devices available.

Select from one of the preconfigured playback profiles. When satisfied, you can test Standard Definition and High Definition playback with the selected profile before moving on. You can further customize the playback profile using Playback Profiles.

In most cases the system will populate this automatically the first time the backend starts. If you are running a single combined backend and frontend, then leave this at its default value of localhost. If you have multiple frontends connecting to this backend enter the ip address or host name of the database server. If you enter a host name it must be resolved using DNS or the hosts file. Test basic host connectivity using the ping command.

This is the name of the database the MythTV backend uses to store information. Normally you should not need to change this. However, you may choose to have different databases for different reasons, for example, a test database so you can check out configurations, and then put this back to mythconverg later, or a different database depending on user so each user can set an independent look and feel.

You should not have to change this from its default. Change this to suit your system. If this frontend's hostname changes often, check this box and provide a network-unique name to identify it.

If unchecked, the frontend machine's local hostname will be used to save preferences in the database. The frontend preferences are stored in the database under this name. If you want those preferences to move to another machine or you change your machine hostname, Check this and enter the old hostname below. If checked, the frontend will use database wakeup parameters to reconnect to the database server Mythbackend.

If checked, the front end will use ACPI to wake the database server if the database server is not running at that time. This way you can save power by not having your database server running all the time. You need to enable ACPI wakeup on the database server for this to work. The following additional options are only displayed if the previous option is checked. The command executed on this frontend to wake up the database server eg.

You can use this command: wakeonlan xx:xx:xx:xx:xx:xx where xx:xx:xx:xx:xx:xx is the MAC address of the database server.