LinuxMCE - User contributions [en]

LinuxMCE System Update

2009-01-25T12:53:50Z

Adamspiers: /* Please Note: you can only force an update if their are updates available */ fix typo

{{NeedsToBeFixed}}
== General Info ==
'''Package:''' pluto-update-system

'''Directory:''' src/PlutoUpdateSystem

== File Details ==

= Please Note: you can only force an update if there are updates available =

LinuxMCE live updating system is taking care of by 4 shell scripts:

;DownloadUpdates.sh: This script is runned by cron and downloads all the needed deb packages for doing an dist-upgrade on the Core and all of it's MDs. Also this script calls the NotifyUpdates.sh script to notify the user that the updates are available and he shoule reboot certain machine so they can be installed. This script runs only on the Core.

;ApplyUpdates.sh: This is a startup script and is runned by the /etc/init.d/fastboot/rcS.d system initialization script before any of the LinuxMCE services get started. It checks if DownloadUpdates has downloaded all the needed packages and if so, it trigers a dist-updagrade. If a new kernel is one of the updated packages he also takes care of rebooting the system after all the updates are installed. This script is run by Core and all the Diskless MDs.

;NotifyUpdates.sh: Notifies the user via orbiters that updates are available and that certain machines should do a reboot so they can update. It takes the ''PK_Device'' of the machine that needs to reboot as a parameter.

;ForceUpdates.sh: Force system update. It kill all instances of already run DownloadUpdates.sh and ForceUpdates.sh, display notification message about reboot on all Orbiters and send a command to the Core to reboot it and start process of system update.
[[Category: LinuxMCEBashScripts]]

== How to upgrade manually ==

--[[User:Totallymaxed|Totallymaxed]] 08:14, 2 March 2008 (PST)
I would suggest the following procedure for forcing the download of updates under 0704;

Go to the /usr/pluto/bin directory

run the following script;

sudo ./LMCEUpdate_DownloadXml.sh background<return>

This will take some time while the update archives are downloaded... so be patient! Once the updates are downloaded you should be asked whether you want to apply the update in the Orbiter - click "Yes" to apply updates and thats it.

Quoting [http://plutohome.com/wiki/index.php/User:Nite_man nite_man] from forum :

You can do upgrade manually. Go to the /usr/pluto/bin and run one by one two scripts:

./DownloadUpdates.sh

and

./ApplyUpdates.sh

The first one will download all updated packages and the second one will apply changes to the LinuxMCE installation.

Note: you should wain until DownloadUpdates.sh finish. Also, you can ignore some warnings which may be generated by this script (you can see the log /var/log/pluto/DownloadUpdates.log)

Another way to perform system update is use the Orbiter:

More --> Advanced Options --> Force Upgrade Now

It forces reboot your core and starts upgrade.

LinuxMCE System Update

2009-01-24T17:34:56Z

Adamspiers: /* How to upgrade manually */ LMCEUpdate_DownloadXml.sh is now daemonized by default

{{NeedsToBeFixed}}
== General Info ==
'''Package:''' pluto-update-system

'''Directory:''' src/PlutoUpdateSystem

== File Details ==

= Please Note: you can only force an update if their are updates available =

LinuxMCE live updating system is taking care of by 4 shell scripts:

;DownloadUpdates.sh: This script is runned by cron and downloads all the needed deb packages for doing an dist-upgrade on the Core and all of it's MDs. Also this script calls the NotifyUpdates.sh script to notify the user that the updates are available and he shoule reboot certain machine so they can be installed. This script runs only on the Core.

;ApplyUpdates.sh: This is a startup script and is runned by the /etc/init.d/fastboot/rcS.d system initialization script before any of the LinuxMCE services get started. It checks if DownloadUpdates has downloaded all the needed packages and if so, it trigers a dist-updagrade. If a new kernel is one of the updated packages he also takes care of rebooting the system after all the updates are installed. This script is run by Core and all the Diskless MDs.

;NotifyUpdates.sh: Notifies the user via orbiters that updates are available and that certain machines should do a reboot so they can update. It takes the ''PK_Device'' of the machine that needs to reboot as a parameter.

;ForceUpdates.sh: Force system update. It kill all instances of already run DownloadUpdates.sh and ForceUpdates.sh, display notification message about reboot on all Orbiters and send a command to the Core to reboot it and start process of system update.
[[Category: LinuxMCEBashScripts]]

== How to upgrade manually ==

--[[User:Totallymaxed|Totallymaxed]] 08:14, 2 March 2008 (PST)
I would suggest the following procedure for forcing the download of updates under 0704;

Go to the /usr/pluto/bin directory

run the following script;

sudo ./LMCEUpdate_DownloadXml.sh background<return>

This will take some time while the update archives are downloaded... so be patient! Once the updates are downloaded you should be asked whether you want to apply the update in the Orbiter - click "Yes" to apply updates and thats it.

Quoting [http://plutohome.com/wiki/index.php/User:Nite_man nite_man] from forum :

You can do upgrade manually. Go to the /usr/pluto/bin and run one by one two scripts:

./DownloadUpdates.sh

and

./ApplyUpdates.sh

The first one will download all updated packages and the second one will apply changes to the LinuxMCE installation.

Note: you should wain until DownloadUpdates.sh finish. Also, you can ignore some warnings which may be generated by this script (you can see the log /var/log/pluto/DownloadUpdates.log)

Another way to perform system update is use the Orbiter:

More --> Advanced Options --> Force Upgrade Now

It forces reboot your core and starts upgrade.

VDR

2009-01-23T20:02:42Z

Adamspiers: add Perl script to sort by LCN

{| align="right"
| __TOC__
|}
[[Category:Software components]]
[[Category:Video]]
[[Category:Tutorials]]
= The Video Disk Recorder =
VDR is a [[personal video recorder]] system aimed at the DVB market. It supports DVB-S, DVB-C and DVB-T tuner cards. More details can be found at the [http://www.cadsoftusa.com/vdr/ VDR homepage].

It is the second PVR system integrated into LinuxMCE. The main aim is for a seamless integration into LinuxMCE. The UI should not change between VDR and the other LinuxMCE pieces. The first version of this integration wass scheduled for January 2008, and is mainly sponsored by [http://www.dianemo.co.uk Convergent Home Technologies Ltd].

== Configuration ==

Recently I managed to setup VDR under LinuxMCE successfully. This brief howto is a result of my personal experience. Don't hesitate to improve it.

===Installation===

VDR can be chosen by two ways. The first one is initial configuration after installation. During setup the media center property you should choose VDR and not MythTV. The second way is to tick VDR and tick off MythTV on the Software modules page - Wizard --> Media Directors. In both cases VDR will be installed automatically and will start after installation.

[[Image:LMCE-software-modules.jpg|thumb|550px|left|LinuxMCE Software Modules]]
 
To make VDR configuration and manage easier its web interface - VDRAdmin can be used. It should be installed manually:

sudo apt-get install vdradmin-am

and then enabled to be able run by replacing ENABLED="0" by ENABLED="1" in the /etc/default/vdradmin-am. Also don't forget to add a new firewall rule for the port 8001 - Advanced -->> Network --> Firewall Rules.

=== Scanning for Channels ===

To enable scanning for channels the DVB utilities package should also installed manually:

sudo apt-get update

then do

sudo apt-get install dvb-utils

==== Scanning for DVB-T Channels ====

Firstly we need to stop VDR before we scan for channels;

sudo /etc/init.d/vdr stop

Above we installed the dvb-utils package and this will have installed the scan utility and tuning files for many DVB transmitters in various regions. Look for a transmitter in your region by looking in the following directory;

ls /usr/share/doc/dvb-utils/examples/scan/dvb-t

You should now see something like this on your console;

au-Adelaide fi-Ahtari fi-Taivalkoski se-Borlange se-Uddevalla
au-Brisbane fi-Ala-Vuokki fi-Tammela se-Emmaboda se-Uppsala
au-canberra fi-Ammansaari fi-Tampere se-Falun se-Vannas
au-Darwin fi-Anjalankoski fi-Tervola se-Gallivare se-Varberg
au-GoldCoast fi-Espoo fi-Turku se-Gavle se-Vasteras
au-Hobart fi-Eurajoki fi-Utsjoki se-Goteborg_Brudaremossen se-Vastervik
au-Mackay fi-Fiskars fi-Vaasa se-Goteborg_Slattadamm se-Visby
au-Melbourne fi-Haapavesi fi-Vuokatti se-Halmstad se-Vislanda
au-Melbourne-Upwey fi-Hetta fi-Vuotso se-Harnosand se-Ystad
au-Perth fi-Iisalmi fi-Yllas se-Helsingborg tw-Taipei
au-Sydney_Kings_Cross fi-Inari fr-Bordeaux se-Horby uk-Angus
au-sydney_north_shore fi-Joutseno fr-Brest se-Hudiksvall uk-Bilsdale
au-Townsville fi-Juntusranta fr-LeMans se-Jonkoping uk-BlackHill
au-unknown fi-Jyvaskyla fr-Lyon-Fourviere se-Kalix uk-BluebellHill
cz-Praha fi-Kaihuanvaara fr-Lyon-Pilat se-Karlshamn uk-Caradon
de-Berlin fi-Karigasniemi fr-Marseille se-Karlskrona uk-CaradonHill
de-Braunschweig fi-Kaunispaa fr-Nantes se-Karlstad uk-Craigkelly
de-Bremen fi-Kerimaki fr-Niort se-Kiruna uk-CrystalPalace
de-Erfurt-Weimar fi-Kiihtelysvaara fr-Orleans se-Kisa uk-Dover
de-Frankfurt fi-Kilpisjarvi fr-Paris se-Kramfors uk-DoverB
de-Hamburg fi-Koli fr-Rennes se-Linkoping_Vattentorn uk-Durris
de-Hannover fi-Kruunupyy fr-Rouen se-Malmo uk-EmleyMoor
de-Kiel fi-Kuopio fr-Toulouse se-Malmo_Kronprinsen uk-Hannington
de-Koeln-Bonn fi-Kuttanen fr-Vannes se-Molndal_Vasterberget uk-Heathfield
de-Leipzig fi-Lahti hr-Zagreb se-Mora uk-Llanddona
de-Luebeck fi-Lapua is-Reykjavik se-Motala uk-Mendip
de-Muenchen fi-Mikkeli it-Bologna se-Nassjo uk-Oxford
de-Nuernberg fi-Oulu it-Bolzano se-Norrkoping uk-PontopPike
de-Rostock fi-Pello it-Catania se-Norrtalje_Sodra_Bergen uk-Redruth
de-Ruhrgebiet fi-Pernaja it-Conero se-Orebro uk-Reigate
de-Schwerin fi-Pihtipudas it-Genova se-Ornskoldsvik uk-Rowridge
dk-Copenhagen fi-Posio it-Milano se-Ostersund uk-SandyHeath
es-Alfabia fi-Pudasjarvi it-Torino se-Osthammar uk-Storeton
es-Alpicat fi-Puolanka it-Varese se-Skelleftea uk-SudburyB
es-Collserola fi-Pyhatunturi nl-AlphenaandenRijn se-Skovde uk-SuttonColdfield
es-Lugo fi-Pyhavuori nl-Randstad se-Sodertalje_Ragnhildsborg uk-TheWrekin
es-Madrid fi-Ranua se-Alvsbyn se-Stockholm_Marieberg uk-TheWrekinB
es-Mussara fi-Rovaniemi se-Angelholm se-Stockholm_Nacka uk-Waltham
es-Rocacorba fi-Ruka se-Bollnas se-Sundsvall uk-WhitehawkHill
es-Sevilla fi-Salla se-Boras se-Trollhattan uk-WinterHill

Once you have found the DVB-T transmitter for your region then use the line below to generate the VDR compatible channels.conf for that specific transmitter using the line below substituting 'uk-CrystalPalace' with the name of your closest transmitter;

cd /home
sudo scan -o vdr -p -u /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-CrystalPalace > channels.conf

This will write the channels.conf file and also output data on all the found and tuned channels to the console. The scan process usually takes less than a minute but can take longer if you have a low quality signal in your area. Below is an example of the output for 'uk-CrystalPalace' my local transmitter here in the UK showing the channels broadcast on all 6 MUX's;

scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-CrystalPalace
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 505833333 0 3 9 1 0 0 0
>>> tune to: 505833:I999B8C34D999M16T2G32Y0:T:27500:
0x0000 0x1044: pmt_pid 0x1044 BBC -- BBC ONE (running)
0x0000 0x1084: pmt_pid 0x1084 BBC -- BBC TWO (running)
0x0000 0x10ff: pmt_pid 0x10ff BBC -- BBC THREE (running)
0x0000 0x113f: pmt_pid 0x113f BBC -- BBC NEWS 24 (running)
0x0000 0x117f: pmt_pid 0x117f BBC -- BBCi (running)
0x0000 0x123f: pmt_pid 0x123f BBC -- CBBC Channel (running)
Network Name 'Crystal Palace'
>>> tune to: 481833:I999B8C23D12M64T2G32Y0:T:27500:
Network Name 'Crystal Palace'
0x2005 0x2045: pmt_pid 0x0100 ITV -- ITV1 (running)
0x2005 0x2066: pmt_pid 0x0104 ITV -- ITV3 (running)
0x2005 0x2085: pmt_pid 0x0102 ITV -- ITV2 (running)
0x2005 0x20a1: pmt_pid 0x0116 ITV -- ITV4 (running)
0x2005 0x20c0: pmt_pid 0x0108 Channel 4 TV -- Channel 4 (running)
0x2005 0x20fa: pmt_pid 0x010e Channel 4 TV -- More 4 (running)
0x2005 0x2100: pmt_pid 0x010b Channel 4 TV -- E4 (running)
0x2005 0x2104: pmt_pid 0x010c Channel 4 TV -- Channel 4+1 (running)
0x2005 0x2145: pmt_pid 0x0110 Teletext Limited -- Teletext (running)
0x2005 0x21c3: pmt_pid 0x0112 Teletext Limited -- Teletext Cars (running)
0x2005 0x2240: pmt_pid 0x0114 Channel 4 TV -- Teletext on 4 (running)
0x2005 0x2244: pmt_pid 0x011c Global Radio -- Heart (running)
>>> tune to: 561833:I999B8C23D12M64T2G32Y0:T:27500:
0x3002 0x3242: pmt_pid 0x0101 five -- Five (running)
0x3002 0x3280: pmt_pid 0x0113 five -- Five Life (running)
0x3002 0x32c0: pmt_pid 0x0117 five -- Five US (running)
0x3002 0x3340: pmt_pid 0x0103 QVC -- QVC (running)
0x3002 0x37c0: pmt_pid 0x0105 Sit-Up Ltd -- bid tv (running)
0x3002 0x3900: pmt_pid 0x010a EMAP -- Smash Hits! (running)
0x3002 0x3940: pmt_pid 0x010b EMAP -- MOJO (running)
0x3002 0x39c0: pmt_pid 0x010c Teletext Limited -- Ttext Holidays (running)
0x3002 0x3a80: pmt_pid 0x010e five -- UKTV Style (running, scrambled)
0x3002 0x3b80: pmt_pid 0x0112 five -- TVX / RED HOT (running)
0x3002 0x3cc0: pmt_pid 0x0114 five -- UKTV Gold (running, scrambled)
0x3002 0x3d00: pmt_pid 0x0115 Sit-Up Ltd -- price-drop tv (running)
0x3002 0x3dc0: pmt_pid 0x0118 five -- Teachers TV (running)
0x3002 0x3e20: pmt_pid 0x0124 Turner Broadcasting System Europe Limited -- Nuts TV (running)
0x3002 0x3e80: pmt_pid 0x011d five -- Eurosport UK (running, scrambled)
0x3002 0x3ea0: pmt_pid 0x0104 ITV -- CITV (running)
0x3002 0x3ee0: pmt_pid 0x011c ITV -- SETANTA SPORTS (running)
0x3002 0x3f00: pmt_pid 0x011b Teletext Limited -- Teletext Games (running)
0x3002 0x3f20: pmt_pid 0x0125 The Jewellery Channel -- Jewellery Chan (running)
0x3002 0x3f60: pmt_pid 0x0120 TopUp TV Ltd -- TopUp Anytime1 (running, scrambled)
0x3002 0x3f80: pmt_pid 0x0121 TopUp TV Ltd -- TopUp Anytime2 (running, scrambled)
0x3002 0x3fa0: pmt_pid 0x0122 TopUp TV Ltd -- TopUp Anytime3 (running, scrambled)
WARNING: filter timeout pid 0x0010
>>> tune to: 529833:I999B8C34D34M16T2G32Y0:T:27500:
0x4000 0x4280: pmt_pid 0x02ca BBC -- BBC Parliament (running)
0x4000 0x41c0: pmt_pid 0x02be BBC -- BBC FOUR (running)
0x4000 0x4240: pmt_pid 0x02bf BBC -- CBeebies (running)
0x4000 0x4600: pmt_pid 0x02c0 BBC -- BBC R5 Live (running)
0x4000 0x4640: pmt_pid 0x02c1 BBC -- BBC 5L SportsX (running)
0x4000 0x4680: pmt_pid 0x02c2 BBC -- BBC 6 Music (running)
0x4000 0x46c0: pmt_pid 0x02c3 BBC -- BBC 7 (running)
0x4000 0x4700: pmt_pid 0x02c4 BBC -- 1Xtra BBC (running)
0x4000 0x4740: pmt_pid 0x02c5 BBC -- BBC Asian Net. (running)
0x4000 0x4c00: pmt_pid 0x02c6 BBC -- 301 (running)
0x4000 0x4c40: pmt_pid 0x02c7 BBC -- 302 (running)
0x4000 0x4c80: pmt_pid 0x02c8 BBC -- 303 (running)
0x4000 0x4180: pmt_pid 0x02bd BBC -- 305 (running)
0x4000 0x4e00: pmt_pid 0x02c9 BBC -- Community (running)
0x4000 0x4840: pmt_pid 0x02cb BBC -- BBC Radio 1 (running)
0x4000 0x4880: pmt_pid 0x02cc BBC -- BBC Radio 2 (running)
0x4000 0x48c0: pmt_pid 0x02cd BBC -- BBC Radio 3 (running)
0x4000 0x4900: pmt_pid 0x02ce BBC -- BBC Radio 4 (running)
Network Name 'Crystal Palace'
>>> tune to: 578166:I999B8C34D34M16T2G32Y0:T:27500:
0x5000 0x5740: pmt_pid 0x02c1 Channel 4 TV -- E4+1 (running)
0x5000 0x5640: pmt_pid 0x02bd Sky -- Sky News (running)
0x5000 0x5680: pmt_pid 0x02be Sky -- Sky Spts News (running)
0x5000 0x56c0: pmt_pid 0x02bf Sky -- SKY THREE (running)
0x5000 0x5840: pmt_pid 0x02c2 talkSPORT -- talkSPORT (running)
0x5000 0x5c80: pmt_pid 0x02cd Sky -- Sky Text (running)
0x5000 0x5a40: pmt_pid 0x02ca Virgin Radio -- Virgin Radio (running)
0x5000 0x5cc0: pmt_pid 0x02cf yoomedia -- tvtv DIGITAL (running)
0x5000 0x5700: pmt_pid 0x02c0 UKTV -- Dave (running)
0x5000 0x5780: pmt_pid 0x02cc Square1 Management Ltd -- smileTV (running)
0x5000 0x59c0: pmt_pid 0x02c8 London Christian Radio Ltd -- Premier Radio (running)
0x5000 0x5a00: pmt_pid 0x02c9 Score Digital -- Clyde 1 (running)
Network Name 'Crystal Palace'
>>> tune to: 537833:I999B8C34D34M16T2G32Y0:T:27500:
0x6000 0x6440: pmt_pid 0x03e9 EMAP -- The HITS (running)
0x6000 0x6480: pmt_pid 0x03ea MTV Europe -- TMF (running)
0x6000 0x64c0: pmt_pid 0x03eb UKTV -- UKTV History (running)
0x6000 0x6500: pmt_pid 0x03ec Flextech -- Virgin1 (running)
0x6000 0x6540: pmt_pid 0x03ed CCI -- Ideal World (running)
0x6000 0x6640: pmt_pid 0x03fd EMAP -- Kiss (running)
0x6000 0x66c0: pmt_pid 0x03ff EMAP -- Kerrang! (running)
0x6000 0x6700: pmt_pid 0x0400 GMG -- SMOOTH RADIO (running)
0x6000 0x67c0: pmt_pid 0x0403 EMAP -- The Hits Radio (running)
0x6000 0x6800: pmt_pid 0x0404 EMAP -- Magic (running)
0x6000 0x6840: pmt_pid 0x0405 EMAP -- Q (running)
0x6000 0x6980: pmt_pid 0x0407 4TV Ltd -- 4TVinteractive (running)
0x6000 0x69c0: pmt_pid 0x03ee ITV -- ITV2 +1 (running)
0x6000 0x6a00: pmt_pid 0x03f0 Channel 4 TV -- Film4 (running)
0x6000 0x6780: pmt_pid 0x0402 BBC -- BBC World Sv. (running)
0x6000 0x6680: pmt_pid 0x03fe EMAP -- heat (running)
0x6000 0x6a40: pmt_pid 0x03f1 Channel 4 -- Gems TV (running)
0x6000 0x6a80: pmt_pid 0x03f2 Camelot Group plc -- Lottery Xtra (running)
Network Name 'Crystal Palace'
dumping lists (90 services)
Done.

Below is an example of the first few lines of the 'channels.conf' that was produced by the example above. Notice that the channels are grouped by MUX and not by their UK LCN (Logical Channel Number) which are the numbers with the '@' in front on alternate lines.

:@1
BBC - BBC ONE:505833:I999B8C34D34M16T2G32Y0:T:27500:600:601,602:0:0:4164:0:0:0
:@2
BBC - BBC TWO:505833:I999B8C34D34M16T2G32Y0:T:27500:610:611,612:0:0:4228:0:0:0
:@80
BBC - BBC NEWS 24:505833:I999B8C34D34M16T2G32Y0:T:27500:640:641:0:0:4415:0:0:0
:@70
BBC - CBBC Channel:505833:I999B8C34D34M16T2G32Y0:T:27500:620:621,622:0:0:4671:0:0:0
:@3
ITV - ITV1:481833:I999B8C23D12M64T2G32Y0:T:27500:520:521,522:0:0:8261:0:0:0
:@6
ITV - ITV2:481833:I999B8C23D12M64T2G32Y0:T:27500:530:531,532:0:0:8325:0:0:0
:@10
ITV - ITV3:481833:I999B8C23D12M64T2G32Y0:T:27500:540:541,542:0:0:8294:0:0:0
:@102
Teletext Limited - Teletext Cars:481833:I999B8C23D12M64T2G32Y0:T:27500:0:789:0:0:8643:0:0:0
:@4
Channel 4 TV - Channel 4:481833:I999B8C23D12M64T2G32Y0:T:27500:560+8190:561,562:0:0:8384:0:0:0
:@13
Channel 4 TV - Channel 4+1:481833:I999B8C23D12M64T2G32Y0:T:27500:580+8190:581,582:0:0:8452:0:0:0
:@29
Channel 4 TV - E4:481833:I999B8C23D12M64T2G32Y0:T:27500:570+8190:571,572:0:0:8448:0:0:0
:@14
Channel 4 TV - More 4:481833:I999B8C23D12M64T2G32Y0:T:27500:590+8190:591,592:0:0:8442:0:0:0
:@28
ITV - ITV4:481833:I999B8C23D12M64T2G32Y0:T:27500:600:601:0:0:8353:0:0:0
(null) - [2243]:481833:I999B8C23D12M64T2G32Y0:T:27500:0:621:0:0:8771:0:0:0
:@728
Global Radio - Heart:481833:I999B8C23D12M64T2G32Y0:T:27500:0:631:0:0:8772:0:0:0

VDR will load the channels into the EPG in the order that they are listed in the 'channels.conf'. So for example in the UK you might want to 'sort' the lines in the 'channels.conf' based on their LCN before loading them into VDR... although the 'channels.conf' will work fine without this. Here is a command which will create a new 'channels-sorted.conf' file from the original, sorted by LCN:

perl -0777ne 'print for sort{($a=~/^:@(\d+)/)[0]<=>($b=~/^:@(\d+)/)[0]}split/(?=^:@)/m' channels.conf > channels-sorted.conf
mv channels-sorted.conf channels.conf

Now that you have a good 'channels.conf' for your local DVB-T transmitter you need to load it into VDR. So just upload the new 'channels.conf' file using LinuxMCE's Web Admin site - go to Advanced –> Configuration –> VDR and use the 'Browse' button next to 'Upload custom file' to find where you created your 'channels.conf' file and click 'Upload'. Now restart vdr from the console;
sudo /etc/init.d/vdr restart
Now use the following command to check that vdr is running;
/etc/init.d/vdr status
You should see the line below;
Getting status of Linux Video Disk Recorder -= LMCE VERSION 0710-10 =- : vdr - is running.
Now the acid test...go to your LinuxMCE Orbiter and select 'TV' from the 'Media' menu to see a live picture and your all done.
==== Scanning for DVB-S Channels ====
Configuration
To configure VDR we should get the list of all available channels for desire satellite. You can find it somewhere or create using DVB utility scan. To do that we need the list of transponders stored as INI file. Get it from the [http://joshyfun.peque.org/transponders/index.html JoshyFun's site]. Store it somewhere on your LinuxMCE core. In my case I use the INI file for [http://joshyfun.peque.org/transponders/0130.ini Hotbird].

Before scanning stop VDR:
sudo /etc/init.d/vdr stop
and start scanning procedure:
scan -o vdr -p -x 0 0130.ini > channels.conf
It might take about 10-20 minutes depends on the number of available channels on your satellite. When scanning is finished just upload the created channels.conf file via Admin site - Advanced --> Configuration --> VDR. And then pickup your satellite from the list (see picture above).
[[Image:LMCE-VDR-config.jpg|thumb|550px|left|LinuxMCE VDR Configuration Screen]]
 
Quick reload router (most probably is not needed) and press button TV on the on-screen Orbiter. You should be able to watch live TV. To navigate on that screen use F6, F7 and F8 buttons on your keyboard, Gyration mouse or Fiire remote. Additionally you can switch channels, see EPG and schedule recording from VDRAdmin web interface.
===Troubleshooting===
If VDR works not as you expect you can do following:

<ol>
<li>Check VDR log - /var/log/pluto/<ID_VDR_IN_YOUR_SYSTEM>_VDR.log</li>
<li>Check if everything ok with your DVB card:
<ul>
<li>lspci - you should see your card in the list of PCI devices</li>
<li>dmesg|grep -i dvb - if driver if your DVB card is loaded correctly you will see it here. Note that in some cases you should place a firmware for your card into /lib/firmware!</li>
</ul>
</li>
</ol>
=== MCE Remote Functions ===
The MCE Remote button functions listed below are for lmcevdr-v10.
==== What do the buttons do? ====
[[Image:MCE-Remote-2.jpg|frame|50px|left|MCE IR Remote]]
==== TV Off ====
Not implemented currently
==== PC Off ====
When the menu bar is displayed or the screen saver is displaying images this button will power off the Core or any Media Directors that have IR remote control features. In VDR this button stops the Live TV picture (any scheduled recordings will be unaffected).
==== Record ====
Pressing this button when watching Live TV will start an 'Instant Recording'.
==== Stop ====
Pressing this button will stop the playback of a recording and return you to the Live TV picture on the channel you were watching previously.
==== Pause ====
When you have a Live TV picture on the screen pressing this button will 'Pause Live TV' and start recording - pressing this button again will un-pause the picture and start playing the recording while continuing to record the live transmission. If you are watching a recording and you press this button the playback of the recording will stop and the picture will 'freeze' on the screen. Pressing this button again will continue the playback of the recording again.
==== Rew ====
Rewinds a recording. There are 3 Rew speeds - pressing this button once gives you speed 1, press it again for speed 2 and a third time for speed 3. This button does nothing when watching Live TV.
==== Play ====
Pressing this button in 'Pause' mode plays the paused recording and pressing it again will 'Pause' the playback again.
==== Fwd ====
Fast Forwards a recording. There are 3 Fwd speeds - pressing this button once gives you speed 1, press it again for speed 2 and a third time for speed 3. This button does nothing when watching Live TV.
==== Replay ====
Press to jump back 1 min in a recording. Press repeatedly to jump back quickly through a recording.
==== Skip ====
Press to Skip forward 1 min in a recording. Press repeatedly to jump forward quickly through a recording.
==== Back ====
Takes you back to the last VDR on-screen menu if watching Live TV or a Recording and back to previous on-screen menu if an a VDR on-screen menu is already displayed.
==== More Info ====
Press once to display 'Info screen' for a Live Channel or a Recording. Press again to cancel 'Info screen'.
==== Up Arrow ====
While watching Live TV does a Channel Up. In on-screen menu moves to the menu option above.
==== Left Arrow ====
When watching a recording is equivalent to pressing 'Rewind'. In on-screen Schedule menu moves backwards in time.
==== OK ====
Pressing this button when Live TV displays the mini on-screen guide for 5 secs at the bottom of the screen. When playing a recording pressing this button displays the playback progress panel at the bottom of the screen. Press again to hide the playback progress panel.
==== Right Arrow ====
When watching a recording is equivalent to pressing 'Fwd'. In on-screen Schedule menu pressing this button moves forwards in time.
==== Down Arrow ====
While watching Live TV pressing this button does a Channel Down. In VDR on-screen menu moves pressing this button moves you to the menu option below. When watching a recording is equivalent to pressing 'Pause'.
==== Vol - (+) (-) ====
Increase or Decrease volume.
==== Green Start Button ====
Displays LinuxMCE Menu Bar.
==== Channel - (+) (-) ====
Increases or Decreases the Channel number and then changes to that Live TV channel
==== Mute ====
Pressing this button repeatedly toggles between Muted sound, on-screen subtitles and un-muted sound.
==== Recorded TV ====
Displays the VDR TV Recordings screen. Use Back repeatedly to back out of on-screen menus and get back to Live TV.
==== Guide ====
Displays the on-screen EPG Guide for the currently tuned channel. Use Colour buttons to Record, View Progs, Now & Next, Schedule & Next.
==== Live TV ====
Turns on Live TV or if already watching Live TV displays the on-screen EPG.
==== DVD Menu ====
When watching Live TV displays Channel List.
==== 1,2,3,4,5,6,7,8,9,*,0,# ====
Use to choose channel number directly in Live TV or to jump to on-screen menu items directly when an on-screen menu is displayed.
==== Clear ====
Currently unused
==== Enter ====
Equivalent to pressing 'OK'
==== Text ====
Currently unused
==== Red ====
In Live TV displays Recordings menu. In VDR menus does the 'Red' labeled function.
==== Green ====
In Live TV displays Channels on-screen menu. In on-screen menus does the 'Green' labeled function.
==== Yellow ====
In Live TV displays Info on-screen menu. In on-screen menus does the 'Yellow' labeled function.
==== Blue ====
In Live TV displays Timers on-screen menu. In on-screen menus does the 'Yellow' labeled function.
== Adding your own plugins to vdr ==
===Installing vdr-dev===
If you want to build and add plugins to vdr you need to install the vdr-dev package. Open a console session at your core or ssh in from another machine and do;
apt-get install vdr-dev
Now follow the instructions for building the plugin you are interested in.
== Manual Installation ==
For details on manually installing VDR please look in [[VDR Manual Install]].
== See also ==
* [http://www.linuxtv.org/vdrwiki/index.php/Main_Page VDR Wiki (English)]
* [http://www.free-x.de/wiki/index.php VDR Wiki (Russian)]
* [http://allrussian.info/board.php?boardid=61 VDR Forum (Russian)]
* [http://www.vdr-portal.de VDR Portal (German)]

Custom Display Resolutions

2008-07-15T22:23:37Z

Adamspiers: /* Step 2: Adding new resolutions to the A/V Wizard */ document AVWizard-Common.sh bug

If you have a display designed for use with a computer rather than as a regular TV, such as a plasma display, it is possible that the native resolution of the display is not one of the options presented by the [[AVWizard]]. In this case, with a small amount of tweaking it is possible to get the media director to drive the display at its native resolution, which will give you optimum picture quality.

'''Please note:''' the following has only been tested with a [[Hybrid]]. If someone knows how to do it with a diskless [[Media Director]], please update this page.

=Step 1: EDID=

By default, LinuxMCE disables EDID - please see the [[EDID]] page for the details. However in this case you are probably better off re-enabling it. This should be done by editing <code>/usr/pluto/templates/xorg.conf.in</code>, which is the template from which the [[AVWizard]] automatically creates new Xorg configurations. You will find a line in this file like:

Option "UseEDID" "false"

Simply change <code>false</code> to <code>true</code> and save the file. Now we need to regenerate the Xorg config, but first we need to ensure that the right resolution is visible in the [[AVWizard]].

=Step 2: Adding new resolutions to the A/V Wizard=

The resolutions visible in the wizard are set in the file <code>/usr/pluto/share/Resolutions.conf</code>. The resolution you need may well already be in there, but with visibility disabled. For instance, 1360x768 is already in there, and only requires the visibility flag to be toggled to make it appear in the wizard.

If your required resolution is not in there, copy a block from one of the other resolutions and modify it accordingly.

'''FIXME:''' someone please document the syntax of this file!

'''Furthermore''', unfortunately these resolutions are also hardcoded in <code>/usr/pluto/bin/AVWizard-Common.sh</code> - look for the line starting <code>Resolutions_HDTV</code> and add your custom resolution to the shell array. This is arguably a bug where the code does not gracefully handle resolutions which are listed in <code>/usr/pluto/share/Resolutions.conf</code> but not listed in <code>/usr/pluto/bin/AVWizard-Common.sh</code>.

=Step 3: Run the A/V Wizard to regenerate the correct Xorg configuration=

[[AVWizard Step by Step|Proceed through the wizard]], selecting the resolution which you have just made appear, and make sure the display is happy with the setting. If not, switch to the tty1 virtual console via Control-Alt-F1, log in, and check the most recently modified Xorg logfile written by the wizard's test (this is probably <code>/var/log/Xorg.1.log</code>) to find out why it didn't work.

=Step 4: Prevent LinuxMCE from changing the Xorg config=

This is a bit of an ugly hack, and if the above is done correctly I'm not sure if it's even needed. Nevertheless, if you want to get really creative and write your own xorg.conf, this is the way to protect it from being overwritten:

Edit <code>/usr/pluto/bin/Xconfigure.sh</code> and add the following lines immediately below the <code>#!/bin/bash</code>:

echo "$0 neutered to preserve custom xorg.conf"
exit 0

Migrating from Topfield PVR

2008-07-05T21:36:42Z

Adamspiers: add category and stub

[[Category: Tutorials]]
{{stub}}

== Importing video files ==

=== Background ===

The [http://en.wikipedia.org/wiki/Topfield Topfield] TF5800 PVR records video files in MPEG format with an [http://forum.toppy.org.uk/forum/viewtopic.php?t=381 extended header].

=== Transferring the files ===

Use one of the [http://toppy.org.uk/downloads/linux.php available Linux utilities] for transferring .rec files from your Topfield to <code>/home/public/data/videos</code> or one of your other media storage areas. <code>ftpd-topfield</code> is a good one because you can then use any decent ftp client to (recursively, if necessary) mirror the files across.

=== File extensions ===

==== xine ====

<code>xine</code> does not currently recognise the format unless you change the extension to something else appropriate like <code>.ts</code>. This can be done en masse with a simple Perl script:

$ cd /home/public/data/videos/topfield # for example
$ perl -MFile::Find -we 'find(sub { my $new = $_; if ($new =~ s/\.rec$/.ts/) { rename $_, $new or warn "failed to rename $_ to $new: $!\n" } }, ".")'

==== mplayer ====

mplayer does recognise the format regardless of extension, but [http://forum.linuxmce.org/index.php?topic=5583.0 mplayer is currently only used for a few hardcoded formats] such as HD-DVD and Blu-Ray. If that changes in the future so that mplayer can be used to play .rec files directly, the above renaming trick should be not necessary. However, the .rec file extension is not automatically recognised by LinuxMCE - see the [[Add video file extensions]] page for how to fix this. Once the extension has been added, LinuxMCE should automatically spot the new media via [http://en.wikipedia.org/wiki/Inotify inotify], but you can check/enforce this by visiting the [[LinuxMCE Admin Website]] and going to Files & Media > Media Files Sync.

Migrating from Topfield PVR

2008-07-05T21:30:24Z

Adamspiers: /* File extensions */ mplayer is kind of irrelevant right now

== Importing video files ==

=== Background ===

The [http://en.wikipedia.org/wiki/Topfield Topfield] TF5800 PVR records video files in MPEG format with an [http://forum.toppy.org.uk/forum/viewtopic.php?t=381 extended header].

=== Transferring the files ===

Use one of the [http://toppy.org.uk/downloads/linux.php available Linux utilities] for transferring .rec files from your Topfield to <code>/home/public/data/videos</code> or one of your other media storage areas. <code>ftpd-topfield</code> is a good one because you can then use any decent ftp client to (recursively, if necessary) mirror the files across.

=== File extensions ===

==== xine ====

<code>xine</code> does not currently recognise the format unless you change the extension to something else appropriate like <code>.ts</code>. This can be done en masse with a simple Perl script:

$ cd /home/public/data/videos/topfield # for example
$ perl -MFile::Find -we 'find(sub { my $new = $_; if ($new =~ s/\.rec$/.ts/) { rename $_, $new or warn "failed to rename $_ to $new: $!\n" } }, ".")'

==== mplayer ====

mplayer does recognise the format regardless of extension, but [http://forum.linuxmce.org/index.php?topic=5583.0 mplayer is currently only used for a few hardcoded formats] such as HD-DVD and Blu-Ray. If that changes in the future so that mplayer can be used to play .rec files directly, the above renaming trick should be not necessary. However, the .rec file extension is not automatically recognised by LinuxMCE - see the [[Add video file extensions]] page for how to fix this. Once the extension has been added, LinuxMCE should automatically spot the new media via [http://en.wikipedia.org/wiki/Inotify inotify], but you can check/enforce this by visiting the [[LinuxMCE Admin Website]] and going to Files & Media > Media Files Sync.

Migrating from Topfield PVR

2008-07-05T21:23:44Z

Adamspiers: /* File extensions */ add link

== Importing video files ==

=== Background ===

The [http://en.wikipedia.org/wiki/Topfield Topfield] TF5800 PVR records video files in MPEG format with an [http://forum.toppy.org.uk/forum/viewtopic.php?t=381 extended header].

=== Transferring the files ===

Use one of the [http://toppy.org.uk/downloads/linux.php available Linux utilities] for transferring .rec files from your Topfield to <code>/home/public/data/videos</code> or one of your other media storage areas. <code>ftpd-topfield</code> is a good one because you can then use any decent ftp client to (recursively, if necessary) mirror the files across.

=== File extensions ===

The .rec file extension is not automatically recognised by LinuxMCE - see the [[Add video file extensions]] page for how to fix this. Once the extension has been added, LinuxMCE should automatically spot the new media via inotify, but you can check/enforce this by visiting the [[LinuxMCE Admin Website]] and going to Files & Media > Media Files Sync.

However, xine does not currently recognise the format unless you change the extension to something else appropriate like <code>.ts</code>. This can be done en masse with a simple Perl script:

$ cd /home/public/data/videos/topfield # for example
$ perl -MFile::Find -we 'find(sub { my $new = $_; if ($new =~ s/\.rec$/.ts/) { rename $_, $new or warn "failed to rename $_ to $new: $!\n" } }, ".")'

mplayer does recognise the format regardless of extension, but [http://forum.linuxmce.org/index.php?topic=5583.0 mplayer is currently only used for a few hardcoded formats] such as HD-DVD and Blu-Ray.

Migrating from Topfield PVR

2008-07-05T21:21:48Z

Adamspiers: /* File extensions */ add Perl script

== Importing video files ==

=== Background ===

The [http://en.wikipedia.org/wiki/Topfield Topfield] TF5800 PVR records video files in MPEG format with an [http://forum.toppy.org.uk/forum/viewtopic.php?t=381 extended header].

=== Transferring the files ===

Use one of the [http://toppy.org.uk/downloads/linux.php available Linux utilities] for transferring .rec files from your Topfield to <code>/home/public/data/videos</code> or one of your other media storage areas. <code>ftpd-topfield</code> is a good one because you can then use any decent ftp client to (recursively, if necessary) mirror the files across.

=== File extensions ===

The .rec file extension is not automatically recognised by LinuxMCE - see the [[Add video file extensions]] page for how to fix this. Once the extension has been added, LinuxMCE should automatically spot the new media via inotify, but you can check/enforce this by visiting the Admin web interface and going to Files & Media > Media Files Sync.

However, xine does not currently recognise the format unless you change the extension to something else appropriate like <code>.ts</code>. This can be done en masse with a simple Perl script:

$ cd /home/public/data/videos/topfield # for example
$ perl -MFile::Find -we 'find(sub { my $new = $_; if ($new =~ s/\.rec$/.ts/) { rename $_, $new or warn "failed to rename $_ to $new: $!\n" } }, ".")'

mplayer does recognise the format regardless of extension, but [http://forum.linuxmce.org/index.php?topic=5583.0 mplayer is currently only used for a few hardcoded formats] such as HD-DVD and Blu-Ray.

Migrating from Topfield PVR

2008-07-05T21:12:41Z

Adamspiers: /* File extensions */ mention mplayer

== Importing video files ==

=== Background ===

The [http://en.wikipedia.org/wiki/Topfield Topfield] TF5800 PVR records video files in MPEG format with an [http://forum.toppy.org.uk/forum/viewtopic.php?t=381 extended header].

=== Transferring the files ===

Use one of the [http://toppy.org.uk/downloads/linux.php available Linux utilities] for transferring .rec files from your Topfield to <code>/home/public/data/videos</code> or one of your other media storage areas. <code>ftpd-topfield</code> is a good one because you can then use any decent ftp client to (recursively, if necessary) mirror the files across.

=== File extensions ===

The .rec file extension is not automatically recognised by LinuxMCE - see the [[Add video file extensions]] page for how to fix this. Once the extension has been added, LinuxMCE should automatically spot the new media via inotify, but you can check/enforce this by visiting the Admin web interface and going to Files & Media > Media Files Sync.

However, xine does not currently recognise the format unless you change the extension to something else appropriate like <code>.ts</code>. This can be done en masse with a simple Perl script.

mplayer does recognise the format regardless of extension, but [http://forum.linuxmce.org/index.php?topic=5583.0 mplayer is currently only used for a few hardcoded formats] such as HD-DVD and Blu-Ray.

Migrating from Topfield PVR

2008-07-05T21:07:57Z

Adamspiers: more info on file extensions

Migrating from Topfield PVR

2008-07-05T20:56:57Z

Adamspiers: new Topfield migration page

The [http://en.wikipedia.org/wiki/Topfield Topfield] TF5800 PVR records files in MPEG format with an extended header.

Use one of the [http://toppy.org.uk/downloads/linux.php available Linux utilities] for transferring .rec files from your Topfield to <code>/home/public/data/videos</code> or one of your other media storage areas. <code>ftpd-topfield</code> is a good one because you can then use any decent ftp client to (recursively, if necessary) mirror the files across.

Gyration Go 2.4 air mouse

2008-06-28T16:46:12Z

Adamspiers: qualify mentioning bug

[[Category: Hardware]]
[[Category: Input]]

This device works, and is supported (plug and play) under LinuxMCE, sometimes with one or two minor issues, e.g. the jog shuttle does not always work in absolute mode, only relative (this may be NVidia-related - check the forums and bug database).

[[Image:GC1005M-large.jpg|right]]

'''Features'''

*GO 2.4 Optical Air Mouse with 30' Range
*2.4 Ghz RF Receiver with USB connector with no line-of-site limitations
*Rechargeable NiMH Battery w/Desktop cradle
*Easy to get started with the Quick Start reference guide
*2-Year limited warranty

'''Where to Buy'''
*"[https://www.8774e4voip.com/ProductDetails.asp?ProductCode=Gyration+GC1005M+%2D+LinuxMCE/ .e4 Tech]" VoIP Phones, Service, and Telephony Hardware for the Asterisk Element of your LinuxMCE.
*"[http://www.gyration.com/en-US/ProductDetail.html?modelnum=GC1005M&accshow=3/ Gyration.com]" Manufacturers Web Site
*"[http://www.newegg.com/Product/Product.asp?Item=N82E16826139003/ NewEgg.com] - online Computer Hardware retailer

Gyration Go 2.4 air mouse

2008-06-28T16:21:12Z

Adamspiers: mention bug

[[Category: Hardware]]
[[Category: Input]]

This device works, and is supported (plug and play) under LinuxMCE, with one or two minor issues, e.g. the jog shuttle does not work in absolute mode, only relative.

[[Image:GC1005M-large.jpg|right]]

'''Features'''

*GO 2.4 Optical Air Mouse with 30' Range
*2.4 Ghz RF Receiver with USB connector with no line-of-site limitations
*Rechargeable NiMH Battery w/Desktop cradle
*Easy to get started with the Quick Start reference guide
*2-Year limited warranty

'''Where to Buy'''
*"[https://www.8774e4voip.com/ProductDetails.asp?ProductCode=Gyration+GC1005M+%2D+LinuxMCE/ .e4 Tech]" VoIP Phones, Service, and Telephony Hardware for the Asterisk Element of your LinuxMCE.
*"[http://www.gyration.com/en-US/ProductDetail.html?modelnum=GC1005M&accshow=3/ Gyration.com]" Manufacturers Web Site
*"[http://www.newegg.com/Product/Product.asp?Item=N82E16826139003/ NewEgg.com] - online Computer Hardware retailer

Custom Display Resolutions

2008-06-28T16:07:58Z

Adamspiers: add link to step by step page

If you have a display designed for use with a computer rather than as a regular TV, such as a plasma display, it is possible that the native resolution of the display is not one of the options presented by the [[AVWizard]]. In this case, with a small amount of tweaking it is possible to get the media director to drive the display at its native resolution, which will give you optimum picture quality.

'''Please note:''' the following has only been tested with a [[Hybrid]]. If someone knows how to do it with a diskless [[Media Director]], please update this page.

=Step 1: EDID=

By default, LinuxMCE disables EDID - please see the [[EDID]] page for the details. However in this case you are probably better off re-enabling it. This should be done by editing <code>/usr/pluto/templates/xorg.conf.in</code>, which is the template from which the [[AVWizard]] automatically creates new Xorg configurations. You will find a line in this file like:

Option "UseEDID" "false"

Simply change <code>false</code> to <code>true</code> and save the file. Now we need to regenerate the Xorg config, but first we need to ensure that the right resolution is visible in the [[AVWizard]].

=Step 2: Adding new resolutions to the A/V Wizard=

The resolutions visible in the wizard are set in the file <code>/usr/pluto/share/Resolutions.conf</code>. The resolution you need may well already be in there, but with visibility disabled. For instance, 1360x768 is already in there, and only requires the visibility flag to be toggled to make it appear in the wizard.

If your required resolution is not in there, copy a block from one of the other resolutions and modify it accordingly.

'''FIXME:''' someone please document the syntax of this file!

=Step 3: Run the A/V Wizard to regenerate the correct Xorg configuration=

[[AVWizard Step by Step|Proceed through the wizard]], selecting the resolution which you have just made appear, and make sure the display is happy with the setting. If not, switch to the tty1 virtual console via Control-Alt-F1, log in, and check the most recently modified Xorg logfile written by the wizard's test (this is probably <code>/var/log/Xorg.1.log</code>) to find out why it didn't work.

=Step 4: Prevent LinuxMCE from changing the Xorg config=

This is a bit of an ugly hack, and if the above is done correctly I'm not sure if it's even needed. Nevertheless, if you want to get really creative and write your own xorg.conf, this is the way to protect it from being overwritten:

Edit <code>/usr/pluto/bin/Xconfigure.sh</code> and add the following lines immediately below the <code>#!/bin/bash</code>:

echo "$0 neutered to preserve custom xorg.conf"
exit 0

AVWizard Step by Step

2008-06-28T16:06:46Z

Adamspiers: add link to custom resolutions page

[[category: AV Wizard]]
{| align="right"
| __TOC__
|}
AV Wizard can be accessed by pressing the Shift key when the Kubuntu with LMCE boots up. In the process of booting, at a time, you'll hear a series of beeps. You must be prepared before these beeps to press the Shift key. When you'll hear them, press Shift key and keep it pressed. Then you'll enter in AV Wizard. If instead of AV Wizard you see black screen or "no signal" message on display, try to switch the connector type as it is described in section '''II'''.

==Section I==

===Resolution Settings===
Here, you can choose the desired output from your video card to TV or monitor. If you’ll choose '''VGA''', there are many available resolutions and refresh rates. If you have a LCD TV or LCD monitor there is no need to choose a refresh rate. This is helpful only if you have a CRT monitor. If the optimum resolution for your display is not listed, please see [[Custom Display Resolutions]].
====VGA====
[[Image:Avw1.jpg|thumb|500px|left|Resolution Settings]]
 
====DVI/HDMI====
[[Image:Avw2.jpg|thumb|500px|left|DVI/HDMI Resolutions]]
[[Image:300px-DVI Connector.jpg|thumb|200px|left|'''DVI/HDMI''' means that you can use a special cable from the
DVI/HDMI output of your video card to DVI/HDMI input of LCD TV/monitor. ]]
 
You have the same range of resolutions like at VGA. Choose one that is suitable for your display device.
====Component====
[[Image:Avw3.jpg|thumb|500px|left|Component Resolution Options]]
[[Image:180px-Component video RCA.jpg|thumb|200px|left|'''''Component''''' uses another special cable which is consisting at every extremity of three jacks (red, blue and green). The display and the video card must have these three jacks. ]]
 

The resolutions for component are made for using with wide screen monitors and TV’s. Choose the one that is best suited to your display device.
====Composite====
[[Image:Avw4.jpg|thumb|500px|left|Composite Resolution Options]]
[[Image:300px-Composite.jpg|thumb|200px|left|'''''Composite''''' is something like a TV out from your video card to the monitor/LCD TV. It uses another special cable with a yellow jack. Like at component, the video card and the display must have this kind of input connector.]]

 
If you are choosing Composite, you can also choose one TV standard from the list, supported by your display.

====S-Video====
[[Image:Avw5.jpg|thumb|500px|left|S-Video Resolution Options]]
[[Image:300px-SVideoConnector.jpg|thumb|200px|left|'''''S-Video''''' is another way to send the signal from the video card to monitor/TV. The jack for the cable looks like in the image below.]]

 
As you can see in the picture above, you will choose one of the TV standards in the list.

===Confirmation of Resolution===
After choosing a resolution, a counter will appear on your screen which will stay 15 seconds. In this time, you can decide if the resolution is good for your monitor or not. If you like it, press Continue. If not, press Back.

[[Image:Avw6.jpg|thumb|500px|left|Confirmation of Resolution]]
 
===Select Graphical User Interface===
The next step of the A/V wizard refers to the graphical aspect of user experience. Here, you have three options:
::Please look a [[Selecting the Right UI]] for more information regarding the best option to choose.
• Static images, no overlay (lightweight) – It uses only static images and works on nearly all graphics platforms.

• OpenGL with overlay (medium)

• OpenGL with alpha blending (high-end) - '''Requires very specific Graphics Cards'''
::In this case your media is always first and foremost, and the media is always full-screen. If you're not watching any media, Pluto downloads the 'most interesting' photos from flickr.com and presents smooth sliding, cross-fading gallery art as your media.

[[Image:Avw8.jpg|thumb|500px|left|Selection of Graphical User Interface]]
 
===Adjust Image Size===
The wizard will guide you to the adjustment of the image size. If your TV doesn't overscan, meaning crop off the edges, you will see all 4 yellow arrows completely on this step. If your TV does overscan, be sure to hit the - key to reduce the image until all 4 arrows are fully visible. Use the arrow keys to shift the image. The goal is that all 4 arrows are centered and as close to the edges of your screen as possible, but without being cropped off. Once you made the correct setup press OK and go the next screen.

This is where LinuxMCE will display the user interface. Your movies and media themselves are always full-screen and are not effected by this.

[[Image:Avw9.jpg|thumb|500px|left|Adjust Image Size]]
 

===Audio Output Connector===
Next set up the audio system. Again, you have to look at the sound card to see where is connected the cable which goes to the sound system. If you connected the cable to the correct output you have only to click the choice on the screen. If you will hear a melody, then everything is ok, you made the correct setup.

[[Image:Avw10.jpg|thumb|500px|left|Audio Output Connector]]

[[Image:Avw11.jpg|thumb|500px|left|Volume Adjustment]]
 
===Dolby Audio Test===
If your audio has Dolby, then you will have an additional screen, if not then you will bypass these two screen.
[[Image:AVWizardStep7.jpg|thumb|500px|left|Dolby Audio Test]]
 
===DTS Audio Test===
If you audio has Digital Theater Sound(DTS) then you will have an additional screen, if not then you will bypass this screen.
[[Image:AVWizardStep8.jpg|thumb|500px|left|Dolby Audio Test]]
 

===Final Confirmation===
The final screen of the AV Wizard will show you the settings that you’ve chosen for the LinuxMCE system. If agree these setting press ''I agree'', if not, press ''I do not agree'' and you’ll be able to make the settings again.

[[Image:Avw12.jpg|thumb|500px|left|Final Confirmation]]
 

==Section II==

Another method to choose the resolutions and the connector is by pressing some keyboard keys. By default, the AV Wizard has the resolution 640x480 on VGA. To choose the connector you have to press the keys from 1 to 5 (1=DVI, 2=VGA, 3=Component, 4=Composite, 5=S-Video). To choose a resolution you have to press the keys from 6 to 0 (6=640x480, 7=1024x768, 8=720p, 9=1080i, 0=1080p). For choosing the resolution and connector you have to be in the initial screen of AV Wizard.

[[Image:Avw13.jpg|thumb|500px|left|Welcome]]
 

When you are in this screen press the key the desired connector. The screen will flicker and will return to this initial screen. Then, press the key for the desired resolution. Again, the screen will flicker and will return to the initial screen, using the resolution that you chose. After you made the setup, you can continue with the next settings.

==Troubleshooting==
===Driver Issues===
*''1080i and 1080p are not fully supported because of some factory issues of NVidia drivers''.
===The AVWizard does not start===
*I hear the beeps but I only have a black screen.
::Please refer to Section II above as it will tell you how to start the AVWizard with a connection other than VGA.

Custom Display Resolutions

2008-06-28T16:04:02Z

Adamspiers:

If you have a display designed for use with a computer rather than as a regular TV, such as a plasma display, it is possible that the native resolution of the display is not one of the options presented by the [[AVWizard]]. In this case, with a small amount of tweaking it is possible to get the media director to drive the display at its native resolution, which will give you optimum picture quality.

'''Please note:''' the following has only been tested with a [[Hybrid]]. If someone knows how to do it with a diskless [[Media Director]], please update this page.

=Step 1: EDID=

By default, LinuxMCE disables EDID - please see the [[EDID]] page for the details. However in this case you are probably better off re-enabling it. This should be done by editing <code>/usr/pluto/templates/xorg.conf.in</code>, which is the template from which the [[AVWizard]] automatically creates new Xorg configurations. You will find a line in this file like:

Option "UseEDID" "false"

Simply change <code>false</code> to <code>true</code> and save the file. Now we need to regenerate the Xorg config, but first we need to ensure that the right resolution is visible in the [[AVWizard]].

=Step 2: Adding new resolutions to the A/V Wizard=

The resolutions visible in the wizard are set in the file <code>/usr/pluto/share/Resolutions.conf</code>. The resolution you need may well already be in there, but with visibility disabled. For instance, 1360x768 is already in there, and only requires the visibility flag to be toggled to make it appear in the wizard.

If your required resolution is not in there, copy a block from one of the other resolutions and modify it accordingly.

'''FIXME:''' someone please document the syntax of this file!

=Step 3: Run the A/V Wizard to regenerate the correct Xorg configuration=

Proceed through the wizard, selecting the resolution which you have just made appear, and make sure the display is happy with the setting. If not, switch to the tty1 virtual console via Control-Alt-F1, log in, and check the most recently modified Xorg logfile written by the wizard's test (this is probably <code>/var/log/Xorg.1.log</code>) to find out why it didn't work.

=Step 4: Prevent LinuxMCE from changing the Xorg config=

This is a bit of an ugly hack, and if the above is done correctly I'm not sure if it's even needed. Nevertheless, if you want to get really creative and write your own xorg.conf, this is the way to protect it from being overwritten:

Edit <code>/usr/pluto/bin/Xconfigure.sh</code> and add the following lines immediately below the <code>#!/bin/bash</code>:

echo "$0 neutered to preserve custom xorg.conf"
exit 0

AVWizard

2008-06-28T16:02:49Z

Adamspiers: refactor into separate EDID page

This page covers the aspects of the AVWizard that the end user will be interested in. If you want to customise the AVWizard for your needs, like writing a separate backend, see [[AVWizard for developers]].

==Background==

LinuxMCE is intended to act like a normal consumer A/V device, even though it is PC based. As a result, the process for configuring displays is substantially different from configuring X11 on a normal Linux machine, and the A/V Wizard has been designed to make this process as easy as possible. Please see the [[EDID]] page for more details on the reasons behind the way it has been designed.

==Starting A/V Wizard==
===Initially===
This wizard is started automatically the very first time the system boots; it does not automatically start after that.

===Starting A/V Wizard from the LinuxMCE menu===
The A/V wizard can be restarted at any time from the LinuxMCE menu by choosing Advanced--> Advanced--> A/V Wizard.

===Restarting the AVWizard during bootup===
Alternatively, the AV Wizard can be started during bootup. Either hold down the Shift key on the keyboard, or press the "A/V Menu" button on the remote to make the A/V wizard start. During bootup you should hear a series of escalating beeps to tell you when LinuxMCE is monitoring the Shift (and "A/V Menu") keys.

When you hear the descending beeps it means that you're too late; the bootup has already gone past the AV Wizard check and LinuxMCE has already started.

==How A/V Wizard Starts==
When A/V Wizard starts it always outputs 640x480 on the VGA connector. If you are ''not'' using a VGA connector, you will likely see a black screen when the A/V Wizard starts (even if you previously saw the Kubuntu boot splash). You will know that the A/V Wizard is running, however, because you will hear a series of beeps. If you then have video after hearing the beeps, proceed to [[AVWizard_Step_by_Step| complete the A/V Wizard]]. If not, see the next section.

==What to do if A/V Wizard does not start==
Press the number 1 through 5 on the keyboard (or the remote control) to switch to the active connector. Wait 15 seconds, and you will hear that same sequence of beeps telling you that A/V Wizard has now restarted. If you don't hear the beeps after 15 seconds, press the number for your connector again.

<pre> Keys for choosing a connector:

1: DVI
2: VGA
3: Component
4: Composite
5: S-Video</pre>

If you hear the beeps but still don't see a picture, it's possible that the display you're using cannot handle 640x480. Press the number 6-9, or 0, as shown below, to select your resolution. Again, 15 seconds later, you should hear the beeps when the A/V Wizard is restarted. If you again need to choose a connector (other than the default VGA), press the 1-5 key (as above) and wait until you hear the beeps again. Repeat as often as needed.

<pre>
Keys for choosing a resolution:

6: 640x480
7: 1024x768
8: 720p
9: 1080i
0: 1080p</pre>

(''Note: Due to a bug in the 0704 release, the numeric keys 0-9 on the Windows XP I/R remote may not be able to set your output connector & resolution. Use the 0-9 keys on the keyboard instead, or use another remote.'')

Once you have a picture you can proceed to complete the A/V Wizard. You can then resize your user interface to fit your screen, choose your audio outputs, and so on. Follow the [[AVWizard Step by Step]] instructions.

==AVWizard steps==
:''See [[AVWizard Step by Step]] for detailed screen-by-screen instructions.''

AVWizard is an easy 10 step configuration wizard:

*AV Welcome screen
*AV Resolution and Refresh screen
*AV Video Resolution counter
*AV UI Switcher
*AV Video Output
*AV Audio Connector
*AV Audio Volume
*AV Dolby Test
*AV DTS Test
*AV Final Selections

After that an [[Orbiter Generator]] will be launched, to create an [[Orbiter]] (remote control) for that tool.

==Running A/V Wizard from the Commandline==
If you are having difficulty running the AVWizard normally (by selecting the option in the Orbiter) it can be run manually by typing in the command line. <pre>/usr/pluto/bin/AVWizard_Run.sh</pre>
Note that you should kill X and any process trying to reload it before running the wizard. You should only do this if your attempt to run it normally fails for whatever reason.
Note: I had to use <pre>sudo -s /usr/pluto/bin/AVWizard_Run.sh</pre> to get my AVWizard to restart.
[[Category: Tutorials]]

Custom Display Resolutions

2008-06-28T16:02:28Z

Adamspiers:

If you have a display designed for use with a computer rather than as a regular TV, such as a plasma display, it is possible that the native resolution of the display is not one of the options presented by the [[AVWizard]]. In this case, with a small amount of tweaking it is possible to get the media director to drive the display at its native resolution, which will give you optimum picture quality.

'''Please note:''' the following has only been tested with a [[Hybrid]]. If someone knows how to do it with a diskless [[Media Director]], please update this page.

=Step 1: EDID=

By default, LinuxMCE disables EDID - please see the [[EDID]] page for the details. However in this case you are probably better off re-enabling it. This should be done by editing <code>/usr/pluto/templates/xorg.conf.in</code>, which is the template from which the [[AVWizard]] automatically creates new Xorg configurations. You will find a line in this file like:

Option "UseEDID" "false"

Simply change 'false' to 'true' and save the file. Now we need to regenerate the Xorg config, but first we need to ensure that the right resolution is visible in the [[AVWizard]].

=Step 2: Adding new resolutions to the A/V Wizard=

The resolutions visible in the wizard are set in the file <code>/usr/pluto/share/Resolutions.conf</code>. The resolution you need may well already be in there, but with visibility disabled. For instance, 1360x768 is already in there, and only requires the visibility flag to be toggled to make it appear in the wizard.

If your required resolution is not in there, copy a block from one of the other resolutions and modify it accordingly.

'''FIXME:''' someone please document the syntax of this file!

=Step 3: Run the A/V Wizard to regenerate the correct Xorg configuration=

Proceed through the wizard, selecting the resolution which you have just made appear, and make sure the display is happy with the setting. If not, switch to the tty1 virtual console via Control-Alt-F1, log in, and check the most recently modified Xorg logfile written by the wizard's test (this is probably <code>/var/log/Xorg.1.log</code>) to find out why it didn't work.

=Step 4: Prevent LinuxMCE from changing the Xorg config=

This is a bit of an ugly hack, and if the above is done correctly I'm not sure if it's even needed. Nevertheless, if you want to get really creative and write your own xorg.conf, this is the way to protect it from being overwritten:

Edit <code>/usr/pluto/bin/Xconfigure.sh</code> and add the following lines immediately below the <code>#!/bin/bash</code>:

echo "$0 neutered to preserve custom xorg.conf"
exit 0

Custom Display Resolutions

2008-06-28T16:01:39Z

Adamspiers: New page: =Setting up custom display resolutions= If you have a display designed for use with a computer rather than as a regular TV, such as a plasma display, it is possible that the native resolu...

=Setting up custom display resolutions=

If you have a display designed for use with a computer rather than as a regular TV, such as a plasma display, it is possible that the native resolution of the display is not one of the options presented by the [[AVWizard]]. In this case, with a small amount of tweaking it is possible to get the media director to drive the display at its native resolution, which will give you optimum picture quality.

'''Please note:''' the following has only been tested with a [[Hybrid]]. If someone knows how to do it with a diskless [[Media Director]], please update this page.

==Step 1: EDID==

By default, LinuxMCE disables EDID - please see the [[EDID]] page for the details. However in this case you are probably better off re-enabling it. This should be done by editing <code>/usr/pluto/templates/xorg.conf.in</code>, which is the template from which the [[AVWizard]] automatically creates new Xorg configurations. You will find a line in this file like:

Option "UseEDID" "false"

Simply change 'false' to 'true' and save the file. Now we need to regenerate the Xorg config, but first we need to ensure that the right resolution is visible in the [[AVWizard]].

==Step 2: Adding new resolutions to the A/V Wizard==

The resolutions visible in the wizard are set in the file <code>/usr/pluto/share/Resolutions.conf</code>. The resolution you need may well already be in there, but with visibility disabled. For instance, 1360x768 is already in there, and only requires the visibility flag to be toggled to make it appear in the wizard.

If your required resolution is not in there, copy a block from one of the other resolutions and modify it accordingly.

'''FIXME:''' someone please document the syntax of this file!

==Step 3: Run the A/V Wizard to regenerate the correct Xorg configuration==

Proceed through the wizard, selecting the resolution which you have just made appear, and make sure the display is happy with the setting. If not, switch to the tty1 virtual console via Control-Alt-F1, log in, and check the most recently modified Xorg logfile written by the wizard's test (this is probably <code>/var/log/Xorg.1.log</code>) to find out why it didn't work.

==Step 4: Prevent LinuxMCE from changing the Xorg config==

This is a bit of an ugly hack, and if the above is done correctly I'm not sure if it's even needed. Nevertheless, if you want to get really creative and write your own xorg.conf, this is the way to protect it from being overwritten:

Edit <code>/usr/pluto/bin/Xconfigure.sh</code> and add the following lines immediately below the <code>#!/bin/bash</code>:

echo "$0 neutered to preserve custom xorg.conf"
exit 0

AVWizard for developers

2008-06-28T15:49:32Z

Adamspiers: split off developer's page

(See also the [[AVWizard|AVWizard users' page]].)

AVWizard is written in C++ using the libraries:
*SDL (SDL_image, SDL_rotozoom, etc.)
*libXML2
*network code

AVWizard executes these two steps:
*[[Generating screens of the AVWizard]] (in the /tmp folder as XML files)
*load modules one by one, depending of the needs of the ([[Main AVWizard]]).

Those two steps may be split in the future into two separate applications, making it more customisable. "Redundant code" may also then be reduced, such as defining object, save/load operations, and restore objects
.
The XML files keep only the display representations of the data. The factory creates the coresponding objects in a WizardWidget class which contains a tree of WizardWidgets that has as many child processes as are used.

EDID

2008-06-28T15:38:50Z

Adamspiers: new EDID page

=LinuxMCE and Extended Display Identification Data (EDID)=

==Background==
Consumer A/V gear, like DVDs, cable boxes and TVs, handle video differently than PCs and PC monitors. PCs and PC monitors exchange information about the resolution and capabilities of the monitors using [http://en.wikipedia.org/wiki/Extended_display_identification_data EDID]. With EDID, the PC figures out automatically what type of monitor and what type of video connector (VGA, DVI) is used. However, consumer A/V gear generally does not work like this. Instead the output resolution is generally set by a switch. The video signal is then output to all connectors at the same time.

==LinuxMCE with TVs==
This often leads to frustration when using a home theater PC. When you connect the PC to a TV, the PC usually expects EDID information from the TV. But since most consumer TV's do not report EDID information (or report it improperly), the PC often incorrectly detects the active connector, or outputs the wrong resolution.

Therefore LinuxMCE does not use EDID to communicate to the TV or monitor. Instead, the user must manually specify the connector type and the resolution in the [[AVWizard|A/V Wizard]] (unless you are using the default 640 x 480 VGA).

==LinuxMCE with PC monitors, plasma displays etc.==
The [[AVWizard|A/V Wizard]] makes the process a bit more complicated for PC users who may actually be using a PC monitor (instead of a TV) for video output. They are used to having EDID automatically detect and configure their monitor's output connector and resolution. Because EDID is turned off in LinuxMCE, however, these users will also have to manually set the output connector and resolution settings, as above.

==Trade-off: disable EDID==
We decided that to use a consumer TV with a home theater PC (and still have HD video) it would be simpler to use manual output type/resolution configuration for all video output, no matter whether a TV or a PC monitor is used.

==Hiding the complexity of modelines==
In the past, most Linux users using a TV as a monitor have determined the correct settings for their TV using a [http://www.bohne-lang.de/spec/linux/modeline/ modeline tool].
They then manually edit the [http://en.wikipedia.org/wiki/Modeline modeline] of the [http://en.wikipedia.org/wiki/XFree86 Xfree86] module in Linux. While this only has to be done once for each TV, it takes some effort and tweaking of Linux configuration files. Requiring a user to edit the Xfree86 modeline by hand is likely too complex for many users, so instead, we decided to use a simpler manual configuration method for all video output devices, no matter whether a TV or a PC monitor.

==Custom display resolutions==
Those with displays with unusual resolutions are most affected by this - however see [[Custom Display Resolutions]] for a workaround.

X Configuration Scripts

2008-06-25T23:33:22Z

Adamspiers: add Resolutions.conf

== General info ==

'''Package:''' pluto-x-scripts

'''Directory:''' src/X-Resolution

These scripts are used to configure X and change resolutions.

== File details ==

;/usr/pluto/share/Resolutions.conf: Configuration file which determines the resolutions available for selection in the AV Wizard
;/usr/pluto/share/resolutions.png: Reference picture for resolution change screen
;Xconfigure.sh: Generates a XF86Config-4 file (defaults to /etc/X11/XF86Config-4). It can use a set of defaults on request. Autodetects the video card driver as part of the defaults. Updates configuration sections according to requested screen resolution, refresh rate. Updates just the video driver when requested.

Xconfigure.sh [--defaults] [--resolution <ResX>x<ResY>[@<Refresh>]] [--scantype {progressive|interlace|doublescan}] [--force] [--update-video-driver] [--conffile <config_file>] [--force-vesa]
--defaults - use the defaults as a starting point
--resolution <ResX>x<ResY>[@<Refresh>] - set the screen mode and corresponding modeline in the config file; Refresh defaults to 60
--scantype {progressive|interlace|doublescan} - select a scan type; has effect only when used with the --resolution parameter; when not specified, defaults to progressive
--force - The default horizontal sync range is 28-90; with this option, it is set to 28-500
--update-video-driver - redetects the video driver and updates the config file; does nothing when the --defaults parameter is specified as --defaults implies this parameter
--conffile - specify which config file to use instead of the default /etc/X11/XF86Config-4
--force-vesa - use vesa, skip driver autodetection; useful only with --defaults and --update-video-driver; used by the fallback mechanism in case the detected driver fails X probeonly test.

;Xres_config.sh and Xres_config_end.sh: These scripts are used by the LinuxMCE Admin "Set resolution and refresh" pages.

Xres_config.sh: <ResX> <ResY> <Refresh> [<Scan Type>] - generates a X config file for this resolution and starts a X server on display :1, sets the background to the resolutions.png file and displays the current settings on screen and at the console.
X_res_config_end.sh {y/n} - confirms or infirms if the settings specified to the previous script should be kept and transfered to the running system (y parameter) or should be discarded (n parameter).

;xtiming.pl:xtiming.pl <ResX> <ResY> <Refresh> [<Scan Type>] - generates a X Modeline for the specified resolution

;XF86Config-4.in: Defaults used when the --defaults parameter is used with the Xconfigure.sh script

;X-ChangeDisplayDriver.awk: Used for updating the display driver in a X config file

;X-ChangeResolution.awk: Used for updating the screen mode, vertical refresh rate, horizontal sync frequency, and resolution modeline in a X config file.

[[Category: LinuxMCEBashScripts]]
[[Category: Programmer's Guide]]