diff options
Diffstat (limited to 'abs/core-testing/local-website')
141 files changed, 49017 insertions, 0 deletions
diff --git a/abs/core-testing/local-website/PKGBUILD b/abs/core-testing/local-website/PKGBUILD new file mode 100644 index 0000000..fd5f2f6 --- /dev/null +++ b/abs/core-testing/local-website/PKGBUILD @@ -0,0 +1,21 @@ +pkgname=local-website +pkgver=2 +pkgrel=1 +pkgdesc="Contents of http://localhost" +arch=(i686 x86_64) +license=('GPL') +url="http://localhost" +#install=filesystem.install +depends=('lighttpd') +source=() + +build() +{ + cd $startdir/pkg + mkdir -p srv/http + cp -rp $startdir/htdocs/* $startdir/pkg/srv/http + chown -R http:users $startdir/pkg/srv/http + chmod -R 655 $startdir/pkg/srv/http + +} + diff --git a/abs/core-testing/local-website/htdocs/KnoppMyth.css b/abs/core-testing/local-website/htdocs/KnoppMyth.css new file mode 100644 index 0000000..7c5c8cf --- /dev/null +++ b/abs/core-testing/local-website/htdocs/KnoppMyth.css @@ -0,0 +1,24 @@ +/* KnoppMyth Style Sheet */ + .headerimage { + border: thin solid #000000; + font-size: 18px; + background-color: #000080; + color: #FFFFFF; + } + table { + width: 725px; + text-align: left; + margin-left: auto; + margin-right: auto; + } + td { + font-family: Verdana, Arial, Helvetica, sans-serif; + font-size: 13px; + border: thin solid #000000; + background-color: #CCCCCC; + color: #000000; + } + a, a:link, a:active, a:visited, a:hover { + font-size: 16px; + } +/* End of KnoppMyth Style Sheet */ diff --git a/abs/core-testing/local-website/htdocs/favicon.ico b/abs/core-testing/local-website/htdocs/favicon.ico Binary files differnew file mode 100644 index 0000000..6a99443 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/favicon.ico diff --git a/abs/core-testing/local-website/htdocs/header.png b/abs/core-testing/local-website/htdocs/header.png Binary files differnew file mode 100644 index 0000000..55beba6 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/header.png diff --git a/abs/core-testing/local-website/htdocs/index.html b/abs/core-testing/local-website/htdocs/index.html new file mode 100644 index 0000000..0184380 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/index.html @@ -0,0 +1,159 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> +<head> + + + <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"> + + + <meta content="Cecil Watson" name="author"> + + + + + <title>KnoppMyth R5.5</title> + <link href="KnoppMyth.css" rel="stylesheet" type="text/css"> +</head> + + +<body> +<p align="center"><a href="http://www.mysettopbox.tv"> + <img src="header.png" alt="Tux with a Remote" align="middle" border="0"></a> + </p> + + + +<table align="center" border="0" cellpadding="5"> + + <tbody> + + <tr> + + <td style="vertical-align: top;"> + + <p class="headerimage" align="center"><b>KnoppMyth R5.5</b></p> + + + <p><a href="mythweb/mythweb.php"><b>MythWeb</b></a>: <br> + + The MythWeb allows you to use a web page to control + aspects of your MythTV system. MythWeb is a separate application, + but it is dependent upon MythTV being installed and operational." + </p> + + + <p><a href="remote/index.html"><b>MythTV Web Virtual Remote</b></a>: <br> + + A web based virtual remote control for MythTV. + In order for this to work, you must enable + "Network Remote Control interface". See: + <b>Utilities/Setup -> Setup -> General -> Fourth Page</b>. + </p> + + + <p><a href="mythtv-doc/mythtv-HOWTO.html"><b>MythTV Documentation</b></a>: <br> + + The MythTV Installation / User's Guide. + </p> + + + <p><a href="mythtv-doc/keys.txt"><b>MythTV Keybindings</b></a>: <br> + + The keybindings for the normal MythTV interface. + </p> + + + <p><a href="linhes.html"><b>LinHES</b></a>: <br> + + Describes how "The Project Leader" setup multiple systems + to form a <b>Lin</b>ux <b>H</b>ome <b>E</b>ntertainment <b>S</b>ystem. + </p> + + + <p><a href="folding@home/"><b>My Folding Status</b></a>: <br> + + Status of the folding@home work for the local user. + </p> + + + <p><a href="http://fah-web.stanford.edu/cgi-bin/main.py?qtype=teampage&teamnum=50975"><b>Folding@home</b></a>: <br> + + KnoppMyth Team status for the folding@home effort. + </p> + + + <p><a href="ipodfeed/"><b>iPod Feeds</b></a> <br> + + Transcodes ready for the ipod (if any).</p> +<a href="archive"><b>XviD Feed dir</b></a> <br> + Any programs you transcodes to XviD.</p> + <p><a style="font-weight: bold;" href="fuppes.php"><span style="text-decoration: underline;">FUPPES</span></a><br> + FUPPES - Free UPnP Entertainment Service. A +UPnP to be used inplace of the UPnP server that comes with MythTV. + If the UPnP that comes with MythTV doesn't work for you, you can +try FUPPES. Edit /etc/init.d/mythtv-backend, comment +EXTRA_ARGS="" and uncomment #EXTRA_ARGS="--noupnp". Then restart +the backend and start FUPPES.</p> + <p style="font-weight: bold;">/etc/init.d/mythtv-backend restart<br> +/etc/init.d/fuppes start</p> + <p>If you want FUPPES to start on boot:</p> + <p><b>update-rc.d fuppes defaults 80</b></p> + <p></p> + + + <p><a href="motion/index.html"><b>Motion</b></a>: <br> + + Motion is a software motion detector. The configuration file for + motion is <i>/etc/motion/motion.conf</i>. All you should have to do is edit + "videodevice" to point to your webcam or capture device. You'll also + need to change the IP in <i>/var/www/motion/index.html</i> to the IP of your + backend. + <br> + + For further detail on configuring Motion, please read the + <a href="http://www.lavrsen.dk/twiki/bin/view/Motion/MotionGuide">Motion Guide</a>. + <br> + + As root: <b>/etc/init.d/motion start</b> will start motion. + To have it start automatically, <b>update-rc.d motion defaults 80</b>. + Images and video are stored in <i>/myth/motion</i>. + Symlinks to <i>/myth/gallery</i> and <i>/myth/video</i> exist. <br> + + Hover on the left side of the video feed in your web browser. + </p> + + + <p><a href="rrd/index.html"><b>RRDTool</b></a>: <br> + + Hardware status graphs. + </p> + + + <p><a href="vlc_control.php"><b>VLC HTTP Interface</b></a>: <br> + + Web interface for VideoLan Client. + </p> + + <b>Tip:</b> + If you seem to be stuck in a + loop when trying to select a video to stream from MythWeb + (MythStreamTV), go back to the main + <a href="mythweb/">MythWeb</a> page and select "StreamTV" again. + + <p><a href="javascript:void(0)"onclick="window.open('mythweb/data/mp3player.html','linkname','height=100, width=260,scrollbars=no')"><b>KnoppMyth Radio</b></a>: <br> + + Your music must be encoded as MP3 in MythMusic for this to work.</p> + + </td> + + </tr> + + <tr> + <td style="vertical-align: top;"></td> + </tr> + </tbody> + +</table> + +</body> +</html> diff --git a/abs/core-testing/local-website/htdocs/layout.css b/abs/core-testing/local-website/htdocs/layout.css new file mode 100644 index 0000000..a91a651 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/layout.css @@ -0,0 +1,29 @@ +/* Layout Stylesheet - Colors taken from MythWeb - arranged by md10md*/ + +.style2 {color: #FFFFFF} +.style3 {color: #FFFFFF} +.header { + font-family: Verdana, Arial, Helvetica, sans-serif; + font-size: 10px; + background-color: #CCCCCC; + border: solid thin #000000; +} +a, a:link { color: #E0E0FF; text-decoration: none; font-size: 14px; } +a:active { color: #990033; text-decoration: none; font-size: 14px; } +a:visited { color: #E0E0FF; text-decoration: none; font-size: 14px; } +a:hover { color: #F0F000; text-decoration: underline; font-size: 14px; } +body,td,th { + font-family: Verdana, Arial, Helvetica, sans-serif; + font-size: 10px; + background-color: #002650; +} +td,th { + border: thin solid #000000; + background-color: #265990; +} +.headerimage { + background-color: #335555; + border: solid thin #000000; + font-size: 18px; + color: #FFFFFF; +} diff --git a/abs/core-testing/local-website/htdocs/linhes.html b/abs/core-testing/local-website/htdocs/linhes.html new file mode 100644 index 0000000..6cfebeb --- /dev/null +++ b/abs/core-testing/local-website/htdocs/linhes.html @@ -0,0 +1,392 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> +<head> + + + + + + + <title>My Settop Box</title> + <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> +</head> + + +<body> + + +<div align="center"> +<table border="0" cellpadding="1" cellspacing="1" width="600"> + + + <tbody> + + + <tr align="center"> + + + <td colspan="1" valign="top"></td> + + + </tr> + + + <tr> + + + + + <td style="text-align: center;" valign="top"><big><big><big><big><big>LinHES<br> + + + <small><small><small><small><small><small>Linux Home +Entertainment System<br> + + + <br> + + + </small></small></small></small></small></small></big></big></big></big></big> + + + <div style="text-align: left;"><span style="font-style: italic;">Introduction:</span><br> + + + <br> + + + LinHES is what I called my home entertainment +system. LinHES is of course based on KnoppMyth, but the setup I +describe can be accomplished with any Linux distro and MythTV. My +setup consists of a master and slave backend. My master backend is +in my bedroom and it is used to store all recorded programs. My +slave backend is in my living room. It's primary function is to +entertainment visitors. Both backends are hooked up to a TV via, +TV out(SVIDEO). SBE is also hooked to a Kenwood receiver w/ +surround(works w/o additional tweaking!). NFS is used to share the files +between the systems.<br> + + + <br> + + +MBE hardware:<br> + + +Chaintech 7NIF2 w/ Athlon XP 2400+<br> + + +512 megabytes of RAM<br> + + +120 gigabyte hard drive<br> + + + <a href="http://hauppauge.com/pages/products/data_350.html">Hauppauge +PVR 350</a><br> + + + <a href="http://hauppauge.com/pages/products/data_250.html">Hauppauge +PVR 250</a><br> + + +DVD-ROM drive<br> + + + <br> + + +SBE hardware:<br> + + +Asus A7N266 w/ Athlon XP 1800+<br> + + +512 megabytes of RAM<br> + + +160 gigabyte hard drive<br> + + +nVidia Geforce 4-440mx w/ TV out<br> + + +Hauppauge WinTV model 401<br> + + +AverMedia M179<br> + + +DVD-ROM drive<br> + + +2 Logitech Wingman Wireless rumblepad<br> + + + <a href="http://wilsonet.com/mythtv/remotes.php">RadioShack +15-2116 universal remote</a><br> + + + <br> + + + <span style="font-style: italic;">Installation</span>:<br> + + + <br> + + + I performed an auto install on MBE, while SBE +was installed manual (I wanted /cache no larger than 5 gigs). Both +systems installed w/o issue all hardware was seen and worked w/o +additional configuration. MBE was recently changed to R5 +Alpha(auto upgrade and <span style="font-style: italic;">not ready</span> +for the average user), while SBE is running R4V3. Both are of +course running MythTV 0.15.1.<br> + + + <br> + + + <span style="font-style: italic;">Customization</span>:<br> + + + <br> + + +MBE:<br> + + +/etc/hosts:<br> + + +127.0.0.1 mbe.mysettopbox.tv +localhost<br> + + +192.168.1.91 sbe<br> + + + <br> + + +Added the following to /etc/fstab:<br> + + + <small>sbe:/myth /mnt/sbe nfs rsize=8192,wsize=8192,soft,nfsvers=3</small><br> + + + <br> + + +/etc/exports:<br> + + +/myth *(rw)<br> + + +update-rc.d nfs-kernel-server defaults<br> + + + <br> + + +Made a directory under /mnt called sbe and symlinked music and video to +sbe/music and sbe/video.<br> + + +mkdir /mnt/sbe<br> + + +cd /mnt<br> + + +ln -s sbe/music music(Setup-Music Settings-General Settings, change the +directory to hold music to /mnt/music)<br> + + +ln -s sbe/video video(Setup-Video Settings-General Settings change +directory to hold videos to /mnt/video)<br> + + + <br> + + +Ran mythtv-setup and change both IPs from 127.0.0.1 to my actual +IP. Modified /etc/mysql/my.cnf, commented bind-address and +restarted mysql. Finally as the user mythtv:<br> + + +cd ~/.mythtv<br> + + +rm -fr MythVideo<br> + + +ln -s /mnt/sbe/image_cache/MythVideo/ MythVideo<br> + + + <br> + + + <br> + + +SBE:<br> + + +/etc/hosts<br> + + +127.0.0.1 localhost<br> + + +192.168.1.91 sbe.mysettopbox.tv sbe<br> + + +192.168.1.92 mbe.mysettopbox.tv mbe<br> + + + <br> + + +Added the following to /etc/fstab:<br> + + + <small>mbe:/myth /mnt/mbe nfs rsize=8192,wsize=8192,soft,nfsvers=3<br> + + + <br> + + + </small>/etc/exports:<br> + + +/myth *(rw)<br> + + +update-rc.d nfs-kernel-server defaults<br> + + +update-rc.d -f mysql remove<br> + + +update-rc.d -f apache remove<br> + + +rm -fr /etc/cron.daily/mythtv-backend<br> + + + <br> + + +Made a directory under /mnt called mbe and symlinked tv to mbe/tv, +music is symlinked to /myth/music and video is symlinked to /myth/video.<br> + + +mkdir /mnt/mbe<br> + + +cd /mnt<br> + + +ln -s mbe/tv tv(mythtv-setup 2nd screen, directory to hold +recordings, change to /mnt/tv)<br> + + + <br> + + +Run mythtv-setup and change the first IP to the IP for SBE and the +second to MBE's IP. Configure capture cards and bind input to +source(configured during MBE setup). Finally as the user mythtv:<br> + + +cd ~/.mythtv<br> + + +rm -fr MythVideo<br> + + +ln -s /myth/image_cache/MythVideo/ MythVideo<br> + + +vi mysql.txt<br> + + + <br> + + +DBHostName=mbe<br> + + +DBUserName=mythtv<br> + + +DBPassword=mythtv<br> + + +DBName=mythconverg<br> + + +LocalHostName=sbe<br> + + + <br> + + +At this point, one can reboot boot systems or:<br> + + +MBE:/etc/init.d/nfs-kernel-server start<br> + + +SBE:/etc/init.d/nfs-kernel-server start<br> + + +MBE:mount /mnt/sbe<br> + + +SBE:mount /mnt/mbe<br> + + +M/SBE:/etc/init.d/mythtv-backend restart<br> + + + <br> + +Tips :<br> + + + <br> + + + In Setup-TV Settings-Playback-2nd screen, +"Action on playback exit", set this to "Save position on exit". +This way you can migrate watching a recorded show from one system to the +next.<br> + + + </div> + + + </td> + + + </tr> + + + + + </tbody> +</table> + + +</div> + + +<br> + + +</body> +</html> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/BlockDiagramofavideocapturedevice.eps b/abs/core-testing/local-website/htdocs/mythtv-doc/BlockDiagramofavideocapturedevice.eps new file mode 100644 index 0000000..ce5d92d --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/BlockDiagramofavideocapturedevice.eps @@ -0,0 +1,331 @@ +%!PS-Adobe-3.0 EPSF-3.0 +%%Creator: jpeg2ps V1.9 by Thomas Merz +%%Title: Block Diagram of a video capture device.jpg +%%CreationDate: Fri Jan 5 11:03:30 2007 +%%BoundingBox: 20 20 336 229 +%%DocumentData: Clean7Bit +%%LanguageLevel: 2 +%%EndComments +%%BeginProlog +%%EndProlog +%%Page: 1 1 +/languagelevel where {pop languagelevel 2 lt}{true} ifelse { + (JPEG file 'Block Diagram of a video capture device.jpg' needs PostScript Level 2!\n) dup print flush + /Helvetica findfont 20 scalefont setfont 100 100 moveto show showpage stop +} if +save +/RawData currentfile /ASCII85Decode filter def +/Data RawData << >> /DCTDecode filter def +20 20 translate +315.75 208.50 scale +/DeviceRGB setcolorspace +{ << /ImageType 1 + /Width 421 + /Height 278 + /ImageMatrix [ 421 0 0 -278 0 278 ] + /DataSource Data + /BitsPerComponent 8 + /Decode [0 1 0 1 0 1] + >> image + Data closefile + RawData flushfile + showpage + restore +} exec +s4IA0!"_al8O`[\!<E1.!+5d,s4[N@!!ic5#6k>;#6tJ?#m^kH'FbHY$Odmc'+Yc +t)BU"@)B9_>,VCGe+tOrY*%3`p/2/e81c-:%3B]>W4>&EH1B6)/6NIK"#n.1M(_$ +ok1*IV\1,:U?1,:U?1,:U?1,:U?1,:U?1,:U?1,:U?1,:U?1,:U?1,:U?1,:U?1, +:U?1,AmF!"fJ;('166!?qLF&HMtG!WU(<*rl9A"T\W)!<E3$z!!!!"!WrQ/"pYD? +$4HmP!4<@<!W`B*!X&T/"U"r.!!.KK!WrE*&Hrdj0gQ!W;.0\RE>10ZOeE%*6F"? +A;UOtZ1LbBV#mqFa(`=5<-7:2j.Ps"@2`NfY6UX@47n?3D;cHat='/U/@q9._B4u +!oF*)PJGBeCZK7nr5LPUeEP*;,qQC!u,R\HRQV5C/hWN*81['d?O\@K2f_o0O6a2 +lBFdaQ^rf%8R-g>V&OjQ5OekiqC&o(2MHp@n@XqZ"J6*ru?D!<E3%!<E3%!<<*"! +!!!"!WrQ/"pYD?$4HmP!4<C=!W`?*"9Sc3"U"r.!<RHF!<N?8"9fr'"qj4!#@VTc ++u4]T'LIqUZ,$_k1K*]W@WKj'(*k`q-1Mcg)&ahL-n-W'2E*TU3^Z;(7Rp!@8lJ\ +h<``C+>%;)SAnPdkC3+K>G'A1VH@gd&KnbA=M2II[Pa.Q$R$jD;USO``Vl6SpZEp +pG[^WcW]#)A'`Q#s>ai`&\eCE.%f\,!<j5f=akNM0qo(2MHp@n@XqZ#7L$j-M1!Y +GMH!'^JXqC&(g$7MX!$Kq(h(.4qa6V1!*;nop@3o$sGM-MMGAJrZ$l>*&r5LsX.H +iF)';PoSYrr?V$\g0`%m"mprkK1^\N)0aVU%jYs?@01kK'q4Tc'</uY2M+W*oWAD +kX!&$"HG!A]SGlURWjPb@m/)ucho)nZk6ZjWh>8X^au^D;2"Mnc>eq3cQ]H+_ESK +E;3(jbBl5bsg$W:#F!tmfK+t*oIVn6K\t%fL!;1*iXZU0mh:si!hY%57kLa1PRN+ +h=0P=9.+HeuE[RgI=mp))X\i$&AK^LreGk9a+P3fg8FOD,OG(km9+O;;EVfrt**V +!9QBUUb=+,=_]Kd0__8N\c?b.qg+>_!.+#Mi^7Vut\NY9:M::#PD[`&AL<8)h^=X ++Z=hb6];ZALeHC\]3&!%Cj:[5..).Dkc.ThD0Ql?Sk[6X>38Bl(]$)[R+Mc#DV"p +O7&'85Wq<9U@CF<2i?beij>=qL*&F4>Ts!?W&`siFZ@E/;.s.(`*NPpoj)C$k=mr +h0$=Y76t)IFldi`08)cU+%bZ*4D&*;<)s5`>-'%W)`X)hj5;14?&J-\,rQ5-68u? +`80s(m0c2Rc=2Wj>Kg3AZt>j&"`d_,;:9X+%6V;l?\M.X8T#iV)gP'79?2QFV^!. +YpUF6l'U4r07TVUJU4k3EZT1gIi?8M])]N"5"kZ1q-#Y>JUliQ//H\F@51D0;[DF ++#5=kDrK3id:>H9T(0F?8i?h8\u'uMEEtt6iR,l=,&h+k1ot:CE6.eRcN6aArWsP +7PY:ic)2EChlQm)r>"B,l&abHDoUMTZJ>H[B^*+1gK@:\%Lp.hXo]$i%-K`n%P$( +gNLm&Lpl197;otn@`iV.oWB:K'`]`7r)CZr%K=I&-^cYEuWmOrj'V9*D#O%Kj&i? +pf@0=UrS<dY'P"G(5Xa0sqU5Aq!U5Aq!U5Aq!U5Aq!U5Aq!U5Aq!U5Aq!U5Aq!U5 +Aq!U5Aq!U5Aq!U5Aq!U5Aq!U5Aq!U5Aq!U5Aq!U5Aq!U5Aq#5I8-X:!]"Fg'W+;? +))CEkAGV+,b.hu:]r,nf\IL1D\9K6q*n87GtdC=HK.-ITs2s%h(R"OcdT!Ir6q&t +cO._*qqqn5as[=VVN7TV>g%2$VchbM2u;39JPi&0r59#8I;./ERXN/QfdF&5QJ6\ +7-/hm!`0*mD0q=DJl>#,h!D6'.9UAU^6;9Mgmun].=p6YlULQ0L%tq=i!;K)B4^. +OeCY-1e.:QG^Q&W=FeNR"ojR!0s(!onrMfSMM$YJqLFCS_eaLd^E+"8GEc6r_f(@ +^-Fn6A=#d)\,XE[YL-kX".T]MZcY6Lh*EbI*Ie<0!=jd^e\9&^((hZILP%&PY.MV +6nW@11Fn,NYt[n!49A.I77MRe0f/H=m:+!:>":_nX*s">cK4EApfa.)c-^ZFR'lZ +jGjTuG`kK$lB*QN:qJt8%R;!7l,=gpC^dc#Rk&D4eTT]VPduHW(dj@K@u`%h'ELh +\7agYlA\GM#CuDmk5%O1KWpcOi?nuIrYd95@4)""(80_O,'#k!R"1SmsJ90"aH)h +WU"b3aZLhDM0OEjn9bqaQSCk]Hd)!%:aW2J&8];t/aXu+lnD^-)lM',i]IZ-`b?( +uioJd?4$81ih](h4L_37KFVoDih[8gp>6MC>,!MC>,!MC>,!MC>,!MC>,!MC>,!M +C>,!MC>,!MC>,!MC>,!MC>,!MC>,!MC>,!MC>,!MC>,!MC>,!MC>,!MC>,!MC>,! +MC>,!MC>,!MC>,.3q9o-4rTd4\8`:PW9Q8W"jc"^Gj_7Yrr@I:]=tP\mp0:Tm:I, +tC3PfIGM88ZU-rn(-8?Kin.YjEp5:!b=3!5gguoODcOrjBg:D7Wl]KHQ+T@%T`k" +bB.&)S!.&)S!.&)S!.&)S!.&)S!.&)S!.&)S!.&)S!.&)S!.&)S!.&)S!.&)S!.& +)S!.&)S!.&)S!.&)S!.&)S!.&)S!.&)S!.&)S!.&)S!.&)S!.&)S!.&)S!.&)S!. +&)S!kPSpYkZ6c+!7c2N8cJdofP@.YDQRdED4]JLhCFC-(jMlBlGMBu%:]>;_CV"& +2MnBhBmAkL5FZT`nt.'qZ>H6EJr8ajhr64LMsW,;8g437/bIZIrr>t+LQB:(qc0[ +-''VHBa4Xn5&`."Edbu)^JG&Kg#04G45T8-L70"$!70"$!70"$!70"$!70"$!70" +$!70"$!70"$!70"$!70"$!70"$!70"$!70"$!70"$!70"$!70"$!70"$!70"$!70 +"$!70"$!70"$!70"$!<9D_ImI+*$8P$@.Qp?UO]Wb^p+2I'l.6Rh7>b\R-2;L%>> +-u]?]2[94eXdV$P#q]U3Q;:keFS<Md@^PuJnrPFH]*5rB1/3MMSgATRR.^n_!cd[ +WTX>VMC8J)\,'ZjX)I][6I+HU*9Ul&LB.10oKMq_ZLs7il$<Vol;nE#O]dp)S]2H +b^?@PriRcu6cilZ/7kUlgd5@Do:c_h:'6OQ@kBJ&ji-S?"Z)m3fC:YWc&F4D6^RR +% +Dd2Y.B0)Fc[TFC3H?IH6)FKrQ;=]>90,jgm^pQ4@#nH-(4L8CX/R_k`I/7>t:riP +"*GgED!<Bf>ucMk`3FT-BAEaosND5etp:VlTI+&^AUTFQR2kPkP@+MY/@=jZSG;: +amFS%-3Z!^ZhdHsh9OVOac%g:Sb<3qhFp']G!K#24J2m!Xin>b[*(!2>?!!2>?!! +2>?!!2>?!!2>?!!2>?!!2>?!!2>?!!2>?!!2>?!!2>?!!2>?!!2>?!!2>?!!2>?! +!2>?!!2>?!!2>?!!3GM"#>;e\@FQp2UR(<\L,iHu?%eL@M`9g&1le9WOgBcZ3&mQ +A*n7(;p!hRj8#L$eQVSXgEbSU;aUgjteVH1cE9'%NZ3'S:Ffp7$rrBo?j*N2Voiq +35Mld"5eiQNjLpIt<#qBs$#FljQ4Y^6uQ'JeKAIY3#.1Np>&ie6G-l#NQnEuF7bo +F/-&R2neQk6-D=Nd$\4gu&;"4++:jj^L3$ubU<-_;jE6JTj=*]A!SS>o?43?\AM^ +H&CjooBdDBp8=H.'KDU9@j5ZF_IMUN%CefQ\;RC?u71e`16"eH@=+ooP;WP/Zpqo +A;1JH\VWlSP-JUM4UE[sSO3;enGJ`ceQYYT2hjUQHlOtqUQs-QgjS0<mm%jugff^ +"Q/d9hCV$#ll$%=UaWe6+N\<"1O92u1!_s"])!D2O[%k"?nK3]IgKF3/9%M](4%G +#U9886JOt5Y(3TFf5U$`F.li-sio`"ot?X*Jo4Ic%f\k[5oAI?BS5Q[d7:UIRCT' +dF--_4*\ERfYO./YiM3WSbuD,U7;[a8Dr[<q5sltEQ)/bJq*ZsD#Kq6EZ,8]ana) +=D:6n3W0IGUH7ue]6Ds!4[QlXh:qGR;bqka@-7+_9Z%`QTboKp"J+Ng0>n,6m7<g +Xs5%(E.2Bu!+b.kSVE\JV:pi3)gLc;__VRn(f`+Y3$#OWJNsuaU5Aq!U5Aq$1K!Z +0PH)hS]!G2>W5@?.9N*Um6m7?DCJK`ekPkOg2=3Jr2cs;:LJ*%m14G-:!5n*Ek)] +:/T$*+38\EOBeoY9+>Q&cC8rn0rY(DN2Y@W,pW7roKNRSau2r0c;"0)2g'k4H:Hn +V;PgpQ%mNOA(p]!INlPl4_j/3TIIg8k19`4BkF\+\O_,Q:hQVire4rJYSX6Qb>R* +<d2(rrBo=D.n+Y<gS,"GEV1kKBq\D-jTXf+)9VdBWbc8TTpg[``:E=.h>HH=o`sb +;*Y]L>c!^MpJM2E$uI3ml9H6InuN49IpTapL?:,t'-,*!/oTbT"Cu\X?$lQ>m8*_ +p-3!tl%2ocTMqVhBH:@i6TF(\Frn$ZVr<iQ)q*,tr;>m]X0DZF`!:kS'n?.A#!9a +@^[JWJn!(+I":WNGKIr"h;re5k"T9&n#TV?rsrrDG9&V&02rrA8Qrr@`pgAW;r!2 +3d"!%6h,!".p<TFQJK?c6=D/,oV1r.!Zqp:lEukZ@caanYl9_R^(&"/#SEnJD-2r +rDjZ+8A_3YMq53(&n:)IR!>)Jr0QkrrBJ)7K3?S^]%$LrY0itpl#-*J,Gq"r%"G7 +J3!W0m=,^td'*HLPO\YQKcf%J,6%Y:?iL*Rj8T)dkU<)6J,<Tk?h>lK!9F'-iCEU +VLqi.TrrC19rrBpI$7H"Krn$ZVr<iQ)q*,tr;>m]X0DZF`!:kS'n?.A#!9WIrFo- +N2-^2FQA85DTIigp2HWK6^g1hOK[HqYNQOtLCXjdOTN;dr@XoAADC[_,oPQ(VK2. ++7.ng`lGp#Q_`J1(LtMC>,!MC>,!MC>,!MC>,!MC>,!MC>,!MC>,!MC>,!MC>,!M +C>,!MC>,!MC>,!MC>,!MC>,"W55Pq]HsDBT&R_#ddEXnBsd[uS]B9FI#`^5;d5J_ +#=#]9qJY2:4_=`JrrCHL1%cDS5Cs5aIP0)ZO^ZbjI3Nho$)jbfV"tAu0sUFQ-F]t +[7Ztd=aGT3!"^#:ImO/1*]^\IPX'>@_8@,s#0=:Uh'?-P^A'X&u3Pcr6r$u8CrrA +1.9`G*r8AFct?;R6s/bCJFp%7bplJ='j8k#O)!Z\0c2Z2GUjC?WO?U=\lOaBe%!3 +\r.oDq2pqM1'C5GdXDC"HFh[r;L+`g5&pZZ+"-<?mW(Nu.!b_t*-:WP\LB/[AO+( +>.Anm4&=uE^ptm29,pk6@;5lMg0(qQQ^1hWIA@]O-4[?/,89keWf@N57BY?XEj)R +9h/06mbqhQ95?R_$@,'!'?8F`S@3M'5TTQ^j3J0MRZ)QAS#L]-;?Bi\M&/,h4L0O +b=%?Bh9)+KR5PE=49AAh/7@\BKm`=_)LrM7I<lG%Q;+1I!;+1I!;+1I!;+1I!;+1 +I!;+1I!;+1I`e\C/SIK':RnpfjMX8$K079q/;]V5?*cimP%^Z5iPrr?BrJ*85[ph +Tjt>pK?]U&P,>"TW:772,`!72,`!72,`!72,`!72,`!72,`!72,`!72,`!72,`!7 +2,`!72,`!72,`!72,`!72,`!72,`!72,cpYCFX,WW)tMUqca,UI"n[OaBe%!3\r. +oDqFprr=8:VuHa'P5bOG#)rle7I;o1]d!IVcijDBDl-[kl5,fV^_5r(BA+WQq=Y4 +M*<lbF;k(ZC2".A*Q7>Y&nO[kY?mTL-.)Z4<7L(0@3R)5C?<Z!sB"Y[/hB6h#9]6 +dP;c:X[9cD+eX2`%,b&Rd\#(R^_'Mng!'Mng!'\Oa&PVeE!UkQu3E_ZW4:D<fo.& +)5!.&)5!.&)5!.&)5!.&)5@lJM.:^Ae2:GsCp7<W"`S!$\S.rr?A%rrD6aXD6Y`# +/:*;YB`A)'34rfrr=7GOoGDf;#^OZ!e<-VU5Aq!U5Aq!U5Aq!U5Aq!U5Aq!U5Aq! +U5Aq!U5Aq!U5Aq!U5Aq!U5Aq!U5Aq!U5Aq!U5Aq!U5Aq!U5Arsf>$BQeGfO7dU2q +Qd@gL>aM"I#f;)dM!2Em#!0MV,rrB5oJ+Nh4KDtoqp6kp\?BKa$!e<:X%6DhR5!8 +?clSb('LJMS8XWY,>,/Y?f*3`<p$SriMr4&Q:P0:[\>[$oG8:K0hl;mWCAL)i#ZB +ANQ"C=qr<dhNp4Y`D[eU0"jp80]?/OoJ-e-ZKBRaIH8-oh=UeWmD'K8bc^W0b>(= +OM(<?;%h@\=IN5^3Od=Al8t,*uG0#0EAljV^ET,rjCaH&9q5=<mpD_4[S9O2!Pjc +!Wr_f77KdDa8<Z(&$BZj?$O/0UhC!6dfHt`2koDM=I9H*;Mr*c?qW.(F2?n.1bLl +sB;e7trr?cu>(u@ooshDVR2RqriXNM7.\Ke`!2#U@.quA;G4>uefm/%pQAoPo,A+ +r<EcI'$.QdVD!Q\AfPJgYL^P;.CjKc5)e02I$A]L$?7UU@5aJF[K,k,l7g#j?_Hs +NjIW5ISIQHX+kr`_rI9J,@^j+V+:"FIlY=&HGM1S3B$pV%'-*Flu`l$#(pp9k9Rc +$59eGhuIj!/;=u:>q21O3Y.gJufU1,`;$`44p^)nT=jVREWl5ZQ--r$N-`DmD&f< +!K2$Y:D-dalWRtV48hZEP1qp=p;H)"Z^Eq;fk*LOnqQ=gHDN!Gk.1!RY:\n%XGD! +l(f\2D`?K5g!A["!Fb.Y8#Fp-B8tH?qq_d9#J#H"iFZaj\l39ZjDia='_X%WBiHF +7F_9F.m7@`As9De&0bI`V5VO$@3)R8iTHti_]:nZu2)*'h+#:45jl@'\\nNGZo&D +TDI+o<5d/L51r1;l,5XBCc@n:@/lo3EGlHpajhl]^S";Fu:S/c>D4NghVl(bc.P< +u<<H5okO$?(\r:IDOG9?!f./K^3a-Ul(lQf5;mjmG+i7%chtGXm'.6)LeA<TlI$f +C)=1o+nKSD%?Z65<E)sqaiQNaTFI><U4<S!U4<S!U4<S!U4=]XhspucrrB6J5P,U +hr&+KS,-I(.!+&M%!9aKcC>\Rd^Ae2:GsCp7<W"`S!$\S.rr?A%rrD6aJ2JaLM?# +'!M?#'!M?#'!M?#'!M?#'!M?#'!M?#'!M?#'!M?#'!M?#'!M?#'!M?#'!M?#'!M? +#'!M?#'!W,$^d)@hOLX'DH]"e7/$M\lVTW6*%M)5%,a^Z8_NrrDB5?i9uPT`5#5] +r$;2UgNruX;cX,pj^9^'\)9mFVq7u=it%`G0:uKIe"OMf;H<#BKu&@BqP(_(]Jq5 +"%%m]nOJKgHmo5p\$=1#\XUbM#R$lP91V?5F[4'h27s2>+QOF@.&*s74A--lV0-2 +MS^$97(/&rhgaVh0SWdgLou`^'gnKq%<u[M8S.)!ed[#Cj.lTiHXnD&cf2mME-nZ +b9!m?*nHf3qlBS%*h.0L6E7sY/=.&)5!.&)5!.&)5!.&)5!.&)5@lJM.:^Ae2:Gs +Cp7<W"`S!$\S.rr?A%rrD6aXD6Y`#/:*;YB`A)'34rfrr=7GOoGDf;#^OZ!e<-VU +5As1Ho'`p5??,_n*c_A>FCpLOoGEg-X<50fJj!&X`*u$oM=m^J)JK4rrA'Vi/d[J +/:[&bretU@eMV+O(<G=s=&I^;(as#]H&k2q;LO<W!L`rf#[WAdbO>?H>lOfob!4h +md6G0irr@[%TDgiOZu6WArZGp=9t_1_#R3hf)EAKQKVO(M5.JRI:^95b!!lnfrQF +[-)-m1An]F)T$dh2LIK';"/"cf$>.S=DB<5h;?g70=m:FSb!$aHK*Y1D"U;p3=eG +dqj3Q/[ESZSd),@l^lbKm%S!+gYs(SZD"qu6X#=$QV'O8)'6:[VS>i6(6_!01,H> +dgEt+2W=mr74s'Y_M-Ro%a]eS2[<3i;ODkBDrIU'Dn-RpbKD[!99;n_AAqrEr5k: +#$4%eEi%0r?_M^rE<_h[-]k)o'ZB7$;?8"]*=ED'[%C1&O&:g2BntF(NMT0r,j\D +0A*>\`F4W5LOoGCe?A\X(n,+&.rrDT35N*!t5Il4B!.ueor]+#eT+^Ae+#'joGTi +5X9Q;O=No4Cm.KXQE3QHHPV/#jU[ph!IgSD?0Z!GQ'=EO`f62!Ff#&!iWH7/G?^[ +PfUrrC(frr@^*7/l<BrX>rZpuQD<1fj+f1t!Xh7]"qsJ5oE$8LL/G"jWlWBr4J$9 +e[?&`TK(N()nuun]Bh>J22W5$dh2LIK';"/"cf$8,ONV-hf:/n7?\@!66TMIO]Ro +T4$6$DE.MMg#o:&=(=K8rrDs?H7/G?^[PfUrrC(frr@^*7/l<BrX>rZpuQT3:^95 +b!!lnfrQF[-)-m1An]F)T$dh2LIK';"/"cf$<G_X\GWu,l4*WWmI*!3LH',aS8N6 +fn-leg>f2Y'UrrDs?H7/G?^[PfUrrC(frr@^*7/l<BrX>rZpuQT3:^7H1G[F.Rf5 +qCFNV^V8E@OYsg,C*5&A%u;rBNT$D#XLP(SZD"qu6X#=$QV'NH>(g?OVG9gu%s(- +$0h%ci4!^(SZD"qu6X#=$QV'O8)'6:[VS>i6(6_!01,H70%E/!:Y^+TA70\!5XrH +rr=%6rXcaVqj6481:dDbj-@tg5TKe(r#pA6pFj;NATRkOa"&CR4ohn'n?/a)VT!Z +/dp"ju,h-HW]T+`baN)lDH7/m5Hp@*Ee&/aseuc&h10nWKgIUkRC@*!<YXA=U%,[ +`N#/,p\rrA1.9`G*r8AFct7_Sg%,5.r7!+(ig!9aWH#Q@0Z1]G'3rrCCL!-&hFCA +o[PNise!#+]b3C%gqi'toa[9TfD)(##RU'LI'.HM5OieXk@0_KPe#b!e4>XYu`"4 +H:-\/`^$hPE$J:GUF@U]kL>B4&cWYS.;IJR.*Hm8<QB$Z4&^(">KTCTFW<tn"A2` +r(hBLE0hIoR`:l/KX%d3etP!(#[u8(!$l^s<4ko9!o/%0rXnV)I@L*<0/-PhaUdP +V]=6l,(sY>eCYG(27G=]6EJsq<3`@93Jge:1i/Ju$2C\\]l&Wi74S&8lEVrbpDtm +$JbS=6o`V.<k/W<%D*:pedo.j77j4_)Z"hji*$IRa01)n,GL-m?F4E8!j(s[E/R; +LoNUM4.s7ZFl#AH]"**epJ`%jCH1T4t:ZHo\XKJL@ob2ltBI167JIJA\&u_85OCG +$Y<&/E#,r?j1DL[>Epq0B%`pUMWl\AWIo*eHjQGi=p,G>RlD?PQ3Li##7oTciVT` +'ED!!'ED!!'ED!!'ED!!'EM!1rrA-<p\fH\rrA^\YMl\\'m,N5nq[5F5S[d0rrA- +<p\fH\rrA^\YMl\\'m,N5nq[5F5SO6u72/Q'5N%Uu'J+b$VuDWiTr`,2!/6p$caF +Sc5M7['aq%:TId]L]c.N$rJQ;^M"FnLdA,cOG5P/GdQE?qHqW3jGeEpbVK5be3OB +% +'*;E7\D%XF]Um99*KYh#-"k#gTmUTg=XRq"I=h/HW/?f;4mB;l"DCQ$X64]:$An@ +Zq.]^T[B1ipj>b7KQh(gZ]oWtQR)UiaE1k.A;__R_(U[j'8:1N^5VH'tOD=.bbGa +X)3pB,oHK56Q4S`d:j]YWcp!LUME:Oj#'P0SPn]>S8rT&#U*BkM@/<mmQqjUNhC> +=hJGam3DKEQjaV'QR4L"69b.f:3tuI;e"8L.smc102>0aC-F)\=dmUqN`)hnD2Ra +H;GK7<J8r]76aH2OLG\=q/hM1q7^m7).@&QurrBbEZ!H8S@m9QJrY3`ICp%V$YXX +B0kh\ihY\uYsO]WU(ERdUQ%'Ki\WscUF:XhhKK%Zl6@=*,*pF%%RATJe31'(;.OP +TG)GjkVpF>*M$=b#Y_>?XdYVeC%m(8#I*$"(oARG$Fdl'?K=R,A"eWNUF09grGo\ +4!%tP2\/e)e;=$DESF/F5AcA@bOV7&<M!lXO#LfBn(=[*naWp!.[uBBg9!f7BQ?A +nkl4^cEemkL(Zk=5)h"@qrCgMF__HRSG&:(M'/BJN^Q#J=C@32dkq"ef1ONMYd&m +j[=JBL)Y?o%np[qHb\K*lh"]DPZoqk+?$bC(gEiuX]1E^fm3Y-WW?3me<1_bXc!P +^Z;q()UHRSO-D#?QPSXm1\qJ1gW4Q%q<)))e_%DOhg5pY'1Xa"2AnI*/[WFE2,#( +3CMg,T]cTK81e5+/4!_R^c%Ma!1CRh+.(11lC6raA%0bXj+j*0ZM9ks-3tnCD*tH +r$Tp*DROXd3cG)e1]aKiFH3lh2GR]@?>QN"9LAcKAiamc/FX;0/csQCkmD?\[`Tt +I0OXRJ>fPs-_b>EhF.U.iHZN/E77GN4H\Q]Kq+@9"S&"'=7j`qdmql\Yd'#'CBu+ +@0$Ua9:KAb8TFQ0ArrA4aY5\LS.a.hl7Sd,F=#uWH!/GqjicWlAD!pr=Mm^%'7Ss +;(!tZ)9cOO/t,kLVd@uBmqo]o&U3OKQS$b>7fA="YpLfgUr:('#D=dNG)cnBMH^: +;XWk)n4d=3PY(Y.Y_5#@j>1/.Y$3*6ji)]MIN-I;UpsrAklgXX/]0Bsr9r,U&()+ +#(bu*]iA.FZpDf/iCBLBf_g5JN_8`8E:0`,^nY<HN#d^h?($unRfD6C=+<r?\fI3 +NbK*6U2=J'.05['E,mJ5MC@G?,)I'pd6aQU^ed&l3skuXH[%YC-c(&]Bf)1'UU9W +hKEmOriC;VF,UB$l!Q!MrF:WHPrEibngNnmH%=s3b@^gK=VYF1f2F5Xf?Pl!\b%j +`oLHZB%`OAB>8=OWi/Fl@L5OL<Br@7fGiB7iW]/NgB>NTH.aQY4qk+Lccm3?l:nC +\eM!8o^V)J`BF(\$S%"kjp?:<B6?[V4?h5SnFP#b[7m).CmH"4FkE98CU:X^_0;h +JJ+!dTs="\GOr!F4Z;04VLPInZL<c+YgD@SN]mV3=$Fo?XPnl.U=u.[*gep/1b9$ +X^GG>8%?"XoE:=skW<mZ$kF*/9kUU'C1o/90;KD*@LI@<4+F$Id)aADr0jtl!!u: +GqYpO+CQSPrgSg>9!(F4kY(+O9iK*j4S,WI[jK=)b3WB*S9_=VM!*pYFDL;3U<QY +@;R.,QtifEk0Hn<%uFo)PrqY?LGrrAbP\dBhf3o=;lY0JW,HO5^Pqn&)1Ifij]b3 +Bj8.Rl]/Jguc"LSWab>j6E1$tK$tkhLV2ZeN:p'eEL84f60YjLdCo)\_P&!9`3h2 +sS*TotHil?!lF%bA14OBjVb3M?tXP5\hJ@&A8s2eI=k&g>>l?Lk"HJ$H)D#KW^f\ +]"C()UTN<VbA-RfCtFD=.:K[jIX!",aS[FgTXiU[rGTO(p\JI^2g2K19=@rlE;PE +OA*eKARLf=Sg1UA17K3@\$Lk5'r$Cm"L9*&942#WUW/\0=CD[SPAcY]MrrBhuUN% +<Z?L+9a!6DjNJ(LK'q>d/qR_OdQ/ILiJl5/D3$3r:U'?\Iq3+`F&;8M>RV.nT>>3 +]-c?<LN'EG[2nN`b$c_RU!>Dqi7"etM%s@`Vo=$sJ@>Tl0!Ub*e6AW=6=<*B+)HH +=%-VK?DSR>AjpTM;c4Z\%K3!RQ$3R<X%/LZ@&`X,EB>45W[(?9%-UPV6u[]f!?<@ +L=-E"!$lSJ#j8*C?i,=Gqf&kXC1fIiAD.cSo6,D51Q5it-_<AAY%(>Y@do_BDY8p +QGjMhT36`^b7cA?)V![K,ZtC@"9Qa7a4\*DUSe-IKFhH5s.;..p$lNT=)5Un/7bS ++EU4>>+h+#jg=;pU9&>!FAN0$g!*8st[;c]s@c+V])iQho,Nq6MgRca3BZBe^/,[ +Vf4R""E6&!WtcK:eCk1maZ/M)>h2buWa!<Z*GAB85*fo%GTRQ6sB[UU\ThQ7'"Yc +qjtKd9IY5DXh&:XfVBDp65HD@?)1A,ukP`6F%IKng#)h%/dV6>mH"i>FfiOg.nPj +([W"sb468a%"Gnp@!_f/!P(W5:]X!!:]X!!:]X!!:]X!!:^'!dr]o)mp$X:-Jni& +T^Z8DC5O6H6r;]iW>Q-n>ht?Fcrdnn"L;2eLdQd'?+8l19#,N#25TKe(Jj8<mZ2X +g4TDC:CTWWQf'r/bU_^;Po(+^\c=hK_.PEU]'5Q`C,(o@64KJuR(!2$B7rr<;5^\ +iD.3XRC0rr@^29E,!aX`OLB#IhJGHB7hgFMIYJf0AbOHiF)dVur]e\c2[)6Zg*=q +U[t$H[Gbma/K"<KJuR(!2$B7rr<;5^\iD.3XRC0rr@^29E,!aX`OLB#IhJGHB7hg +FMIYJf0AbOHiF)dVur]e\c2[)6Zg*=qU[t$H[Gbma/K"<KJuR(!2$B7rr<;5^\iD +.3XRC0rr@^29E,!aX`OLB#IhJGHB7hgFMIYJf0AbOHiF)dVur]e\c2[)6Zg*=qU[ +t$H[Gbma/K"<KJuR(!2$B7rr<;5^\iD.3XRC0rr@^29E,!aX`OLB#IhJGHB7hgFM +IYJf0AbOHiF)dVur]e\c2[)6Zg*=qU[t$H[Gbma/K"<KJuR(!2$B7rr<;5^\iD.3 +XRC0rr@^29E,!aX`OLB#IhJGHB7hgFMIYJf0AbOHiF)dVur]e\c2[)6Zg*=qU[t$ +H[Gbma/K"<KJuR(!2$B7rr<;5^\iD.%<MM<?OVG9gu%s(-$0l[BAlQ;b5N@0D*hs +pggW3GS^#$F+K6MpObRgGc9'V-!#/:!!#/:!!#/:!!,(WTnh4a-p$"./J8!;ZjBg +;"ld@Hb!)]qLaM"SQ!8"$]q>m?WrrA1.9`G*r8AFct5SUVU#A>%;o%r9giU55SH1 +=Ms3F>+o^le;l4ZcEFdVNBuYdTSKg*)-00n;D_\L3PeeZ(#!L9%(`g>"ALWEQ.BE +(mUXYFGi&i:5Eui:5&bFf/DLgfdKn#a/CP9[GL>CiZ@nq(WlceZ(#"!-g$3bBtrI +R\EfP>bD]n`0;rmlC$A-8BDt_o:4mihKUiop\KQ0f/drbd^m*/b]+WH^N@+rluFd +Dn3&:JM?(WG4=?k=2eM@ObC%Nc3?9Djr6u^?IACd$Sf8o<>4G$$&>V#"Z,IW86pZ +?rDu^!5VpRa5'N%+!'N%+!'N%+!'N%+!'N%+0ol'X.?[p\?TDAkorYke:O]P*R!3 +[f#oDquMDtsKBJ(M?*q?a2$)ZKf"=%N>kY:+nm!C.Qf;+1I!;+1I!;+1I!;+1I!; ++1I?8YUuYRjocFL"sISi1<.5:Z-!$eu>S"g+D.:rN3c>j)!/fW/[B<(n=T3G<iV, +"h\g0c#XMjOCeaO89iiD%gTG5`!YZaXZkW?pk,cIV\7jW0&G%5cg<2(@Q\4i\`7` +hEdIYj!SQ44_0Kpb(:2%D%Pj28iK]2'*#_uCMV8<,Gu?&#;U6VI'iY[=PL*AYHQJ +[8>7Gn,(B2J!iSH"qL1W"HZSiVEM$?=$aTM=*$KJOt&F*=X:Q"d;S*BCDS&=gR76 +T4nCuc%gKEWN>U_%U.`6\anDI'l`%Cj])`[R!F(!HtH&u;bQToqt!19`nI,H.asD +Y;g$rr>`seFa)#U"*P=2Fdb.m*[.Jr`00i63@^Ck]>IgSI<A^KO,_h`eS%]je=)U +DfmYNVO7+<`NlM:!()a3M*1J6'ERL.HB!o=hmQiqgM[4uSLUL%`c7415;?2SNmfi +b!;K7[.s_%_@k;hCM631PfYSn3^_mk,DG\KNl''m(3uS)IU5Aq!U5Aq!U5Aq!U5A +q!U5Aq!U5Aq!U5AqeOef7hE[nX[.a#XOK@CgU*X2&;!"B.J!RM++F;.OV5Q:]h2h +f$1"(V?2IYAm5K6UW"J2TXdkZ:&=!-A/?n:PsirdZmkpZPKS!!kN;^ZYc0rr@M%F +;0C^;TqB+A<Y_t0L+M#n@/>rCk(p#U](gC$\-M-a8Z#EkB),Z<&!!0kjVcaUTOKi +=-d(AD32P<#l[icNn0%PaQQ?.l$b4onC=,,"lZ_=;q*ouFW.[;j_`rW("nLf/'n= +54,6E.m_@]bn@/>rCk(p#U](gC$\-M-a8Z#EkH01WaSL&Gc7CUJ!4+<Fde;\C6I; +3I:-@%P+K<ZJ3P\S>25dPNRd<?"=R;a^=@XC6]Yfp,P)KPcb$Ha?]r2#,r#ji3rr +A]$O8\nhJ&2ZRDu'IdrrCrM=f^Nbn@kBnBp1d^d-T^L@m&Pb;e19%q2/#/gX`\AM +<30nc#th<g]%7i9/`>S0ft&WH"/hiSF'>P\dXZ`H(YY6rX`uUJ'\D?rr!0gi<Je\ +r;^Y`n'J40j'U<K3TA;%<Ugc(XnF=N3>_%"6;@@?^]FH!,_b<Na4dY0T+TRfESG5 +0H8X2n_)0<g<:(nq@m]Ob%o?4`(h8iN3R%PGJ+/)8>Q0.25POA=rr<<`KtlgRA,c +OXKk/n^Y?b7PI8a%JZ&_N-jb>1XL/r$UbeNGdPOc1Z%P`q:`H+T^4p6MYS*"R4h5 +oaLS^-;3NJ8Ec"Z@C5H=V?K#C$1J#WIIPkQ>>p!.KVDn:PsirdZmkpZP[E70%E/! +:YVc>Q0.25POA=rr<<`KtlgRA,cOXKle#*#<mMEiF4K_)\PC$OKI00NX1drO]"#4 +W/<8C%KHR&70"$!70"$!70"$!70"$!70"$!70"'XX8#lM<n(R-P4JKG^PY6+m5?a +'B9,(*^k/XDcQe>&U4>7di,'k=*d\Zcn`HEb\WZogc-&e6'Rfc7N!o\?#'f4YF*I +pb]6i4LYOsEVmqc?,SlqpqZqNd$!C0O;`W5:FP?h0&!RKEn6H[UD/nDT.]Qdn!/O +e1*`NhE*-NfM3)k/F1N786nCBuN!f^(9!)[WnK;.gWg[&PBr7n%jK<Oq:j#Gs#LU +4=ZUqF.9:VF=p*+3KWi[#SGJM'\RWod#\reuqq>!#/:!!#/:!!#/:!!#/:!!#/:! +!#/:!!#/:!!#/:!!#/:!!#8./Z$fP?]s*OWm-Sj%_rh3Y;fKPqA93B)BV5bS:W&5 +N`J*H:Ge.bRN(jFk@ImuB>8`Ea+H_pe0Lc>LR!]&h]s3kdDI;dBe7@'<^1\5JGn; +3o9]2T^i":u'GiuH.J2")f5<Dt^G5BL`/u73W.4Es4`>TKG[PZ+[0p5:',j)(?Sd +J1V8(.&(e0MR$/be#&ApD+,\NXK7\`4)pp\TJB<CHn/g=M#Forep@3inY\6u5tn, +!j2h$lp(DU:Q)Zf=hNFpJKKpNV&@ZI4_Pi3^toB/-?0q3=VS<NgUs]ePSROK6SSG +7d!X<?Ib&*^TePLYhOt72%3S$q3qL#So`5e'l)48HCN38>O_ibNNud$!noUrKTnI +4BlM+<`rhtP-Pb(W5TGcmK.`Ab0%0>rH^uZ[R3f8Lq_Ft#a8W/3+?qPd3\':p3M^ +!aa9l%!CHq_Al#n]2:CmN\KDC',RH?[4!&cau[VN(@J-m^!J-m^!J-m^!J-m^!J- +m^!J-m^!J-m^!J-m^!J-m^!J-m^!J-m^!J-m^!J-m^!J-m^!J-m^!J-m^!J-m^!J +-m^!J-q<^$s)r?\B5t'T4(Vs=";O31+:=$0E^2H!Ts+42Xrn9(=TohH?:%l/qaXL +Xi-'8I+D+/$"=8Oh(d2:=%s3_dN*\Qf(tTbgM-LFgG6un$1e_5h9RH.!!1ssRe*Q +j$cW,G#Z[1]A`-eI0,-on)CDC+NXmUY#%]QFh10NlAG#=pg:rDcWI.:?C,"@53^n +OphBHpRCIh9Y'm%AaEWPS3!-ZpW.a^*ZmbSo@T4:YPj_c;f)C-GebcUsSJ9f-o23 +"^4qSGH+C:DnRkr%k!\@>(I@$3[q8-+=H;TmBdj/4bkiXI,3nX[[rI:oD&CDuGHe +i<-J7+X1#dSd\uOLRWfC^e&uACZ_UbGb3:5h2O5nC?;Gp'6OPFUFqa6KggWN1@$O +,kT.uBEPf+;mVrmT1t2^pNGc+9T#YA@D;0iMun<U:3"Q6>i)`fG_NeFRKeWIQQ#l +(B772K]o#<?o*SlB@I6tf>>)Wuk,5.km]tX4d]pKo^2OIG@u1h!r[6#8]7Z-o93. +5M9)+X>_W^iUop]Xp!+ju!)S$K+`NXC#Yl-uj4F"&/Z&;kkejc-CWbL$np+(jg)V +S:gi#JrX)d,^?P'UW?CZ"p%7FJ"D?JZbe@M;?V\!Bl0TAj^FFq296**4GgB\L4Wl +o\4K5*\",f/b^%\p]g%VIs8(fpjK@$SbH^F7SqRS#b7YP3RA$Rp'Rk*Q>[*A2MBd +=QfY0"OAeAJIR`n7MKj4cj+-3ilr!.q_5Oo"PgoX`$(-&-852Y63Do(mi2jaK&al +m)n)uX^6_boZebpFm'4/?FtctN!$pKbgY\[,>Jn>X!5j#Hd^G9ZIk:FBNO4f%R/H +8Q,?J0RXM\d-,jso^2$\_LDJikO:&<RQ$[D=h,9Y.I?9tr2hZjhrf\C`+_q(/-"P +<"B)_+DY!,%D6'/hNb_X0_3iJ>L!V:<.niU%iWin!j#o&d@]VcAIAns"Yl2Uslj" +EJb]Xp;mkGDJ+.42b<D=R.&DQJtuT[^1u2m+s>I=(_LL@\Y1^\@3<XJpek?P>M%. +1>0j[;6bg,8RM.l/_rr=i1,6Q!Rb(pY=-nu1T/p`XLC8072m'pMPgW?Lt^c#eOce +[[_&GNM$n&7"uA&OMDU<gP!dad6j8T4i,N#YT;>m`H/N=^=VP!&P/VH4rr?$<."D +Qm;u'FqH7Q*Z`S,6d'2Q-f/Rl)UdR`be4HL@i@3VmQ%aCmkngFRSLqIeI#D_\"F? +>;UHeYs9N`WZT<J9c@bG'OAQhuGf:ZYk-\s,6nLq!5Wb]0Fu.nq[_aLdH;$?F$0i +% +HI>3An`%NN1c(-2Ue=!57nS[JF(82oQ,[e@U6M$.r@?g#ngg4DFbk1aG+^]1jd26 +IM7\8L9B>i3UG,ns:@dIh$H`(Nc8^Bj0?2p@^ETf+8+"@@@KGO]A`?[F?09*c[(I +QhI_"1?n*Qqcm""Y7UmXN(=@?7T>C2.uEblNhF*I]@<a2=_g%i`/ZpM:o<qp.hXb +=)[FX'+<IEqDoWc.Y&5gK57bV;r^`j6Ah/C4.7Y!ako501M4b:sD\ZD\lGq#rClX +l>k.E"*ej(!;N@%1(jbt:/o?sX)j-r2)`Hk"=V96*[G6IM2AV*J."UIthE#DT?k6 +)cDCS(&<K!0&Fm^2@&foj`F1:C6/_uq]V#$B"A<PeO^leh(_'_m_`BXD&49nFl7a +<eC.NE!qDLnFd#EX!%;%rCi&*A*V9oGp:q9,h+*,gmH1O-JWa9)[\2&[h.]pIXU> +r$E<geAe-ZTKMg)fu&)2jV`R2T:(\.]5>i7a'.DC%0KIKiVbh2e&8tLSNJPd>[0b +,;#*KI7_qZ88E!&u4H\3mD(et/!QEu(m#/9d=]RGp<?GfY-P,BYcT)(hIeHQ0!;/ +B$U4<S!U4<S!U4<S!U4<S!U4<S!U4<S!U4<S!U4<S!U4<S!U4<S!U4<S!U4<S!U4 +<S!U4<S!U4<S!U4<S!U4<S!U4<S$QgmMheCs&;TgO)WS/R;\e'.u3P_de-7;O!T- +R=^kVZsDK);`2HoG$gBWMn&8Z64b<:u6"j_g-)R?l*_B@`JmE!Ui8pKi$T2>M.ZO +Fa#re5n`U2,[dXIe<=3;%^W:,B%%\s^9TKgRN4P%\<SA2+a=)'B,O`3R,IS]1RqD +AA@E=87uFYam46r789F'6Of+[rOY]PN@qP"*m0j#g%n"lp1Seef$ZUT0?=f)7k!p +rA`<ji<:lMQ(*/`.P[XufY4)8M-(a;e]`u9Y3"/#Wq25K$__;i4-8WrdmXY$p'=X ++S6A%A1=bYP2F^Q>Tk_t30m-_&#>QQ#juD%sQ<Q^8.u+BOjtR8daR38jDoN)0b[d +9]<iYMsoPD,X_k2+Zo>]p_$2f@J@&7$5Pe,`'_V+EGMm[RY*#]P"3Ll/!)BimLbB +4H`&BSi4'>,`trrSj#uhrY,C;FW3WH/sp5mChQPYM[(R__+SF=;?u5_X3EL--LdX +bmr*(9$b]#34?%J(**8;[*Ecp3p#,3b\$<uM8#/f;'Y_tkQ;(UQW=LWKYB:4O*20 +,THj[#Z=:pXp3bK[p!;-,gVeS,Y[\"$-N5B@5QZR6J7cEu%f+Xin\rNn@U1eT&Ye +JSTG1G7P"oOSGTK^d[/,Oj3LPN)+:D6t-DbRdnY98jB.U24qXlS.lmNkh4hp_W4- +QRH)%o8q4a&1>DGr<be%9mQcNiR(4(D=tVSMW7raN5i!NSU+FJDmrpPCc;.lF[dQ +WSD2(;/2qr>?f2lM56RhAMK,Y&t$dHj!@Jgo&PgE"/MZK-ig!!-ig!!-ig!!-ig! +!-ig!!-ig!!-ig!!-ig!!-ig!!-ig!!-ig!!-ig!!-ig!!-ig!!-ig!!-ig!!-ig +!!-ig!!-ig!!-j#F.UY'?_bAVk8RY]rk+k[_MFCf#,Pk')&Ffb?,B8>QRK$`.e80 +quFOX?2:%`8_3BOKn`e<A/^H3u'n%#o2ak*pX3B5=Bu>MI!mW<M\S42*%@;Q&.0+ +HC[lN0B^cK>O''^6s>GXb+7"n07'h,=qD-1%RI>a,Z\[gD!LM&C'.:&)8b@QGBu_ +U@JlkncE=HFtqg>>iakL3NJGe*n%F+D<8(0=C0k>g;H?5gC[i4Gs7l>.%gpRpbTh +^3fKEsC!+mt.a9@S30$KG__bcfA&./X>5+>+g4c'JQZ,GX[)c-9Ug0t"l3O,A!6i +o>.ACN8/TYW;M:s;1V3Y2JN+An999MpFUB@1VeC-8##A>#=m!!V6G`GmkQ6"DcX< +G02eVOU)p-@Yq.%h"WD'm9O;SCRsm?TiGh4JAF':C`e/q/H$W(Z(i%UD-@^tEOUb +<KSn9_#bul4qj%!.0[r72,_ti>i9c:U@?D4]34C>1ge=`pj`:LijlOc;-Qo\Z>R= +QXcdmV3[`iQM0N6#eB#[P"@d!:F)N+'MntU.&)5!.&)5!.&)5Vs4I~> +%%EOF diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/BlockDiagramofavideocapturedevice.png b/abs/core-testing/local-website/htdocs/mythtv-doc/BlockDiagramofavideocapturedevice.png Binary files differnew file mode 100644 index 0000000..a01ae3d --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/BlockDiagramofavideocapturedevice.png diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/Card1 HDTV Card2 Cable.png b/abs/core-testing/local-website/htdocs/mythtv-doc/Card1 HDTV Card2 Cable.png Binary files differnew file mode 100644 index 0000000..013856e --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/Card1 HDTV Card2 Cable.png diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/Card1 Pri 0 Card2 Pri -1-TDS.png b/abs/core-testing/local-website/htdocs/mythtv-doc/Card1 Pri 0 Card2 Pri -1-TDS.png Binary files differnew file mode 100644 index 0000000..344095a --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/Card1 Pri 0 Card2 Pri -1-TDS.png diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/Card1 Pri 0 Card2 Pri -1.png b/abs/core-testing/local-website/htdocs/mythtv-doc/Card1 Pri 0 Card2 Pri -1.png Binary files differnew file mode 100644 index 0000000..3dfb909 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/Card1 Pri 0 Card2 Pri -1.png diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/Card1 Pri 0 Card2 Pri 0.png b/abs/core-testing/local-website/htdocs/mythtv-doc/Card1 Pri 0 Card2 Pri 0.png Binary files differnew file mode 100644 index 0000000..7eb25aa --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/Card1 Pri 0 Card2 Pri 0.png diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/Makefile b/abs/core-testing/local-website/htdocs/mythtv-doc/Makefile new file mode 100644 index 0000000..0368fd2 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/Makefile @@ -0,0 +1,42 @@ +# To build this stuff, you need the linuxdoc tools and htmldoc. On Debian, +# this means: linuxdoc-tools linuxdoc-tools-text htmldoc +# +# - mdz + +TARGETS = mythtv-HOWTO.txt mythtv-HOWTO.html mythtv-HOWTO-singlehtml.html mythtv-HOWTO.pdf index.html +LINUXDOC_HTML_SPLIT := 1 + +all: $(TARGETS) +clean: + rm -f $(TARGETS) $(patsubst %.html,%-[0-9]*.html,$(filter %.html,$(TARGETS))) + rm -Rf doxygen-dev-docs doxygen-warnings.txt + +distclean: clean + +validate: mythtv-HOWTO.sgml + linuxdoc -B check $< + +%.txt: %.sgml + linuxdoc -B txt $< + +# Generate PDF via LaTeX using linuxdoc +#%.pdf: %.sgml +# linuxdoc -B latex -o pdf $< + +# Generate PDF via HTML using htmldoc +%.pdf: %-singlehtml.html + # htmldoc exits unsuccessfully for no good reason -mdz + htmldoc --book --quiet --outfile $@ $< || true + +%.html: %.sgml + linuxdoc -B html --split=$(LINUXDOC_HTML_SPLIT) --toc=2 $< + +%-singlehtml.html: LINUXDOC_HTML_SPLIT=0 +%-singlehtml.sgml: %.sgml + cp $< $@ + +index.html: mythtv-HOWTO.html + cp $< $@ + +devdocs: + doxygen doxygen-create-developer-docs.cfg diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/add.eps b/abs/core-testing/local-website/htdocs/mythtv-doc/add.eps new file mode 100644 index 0000000..5a6bfb7 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/add.eps @@ -0,0 +1,27 @@ +%!PS-Adobe-2.0 EPSF-2.0 +%%BoundingBox: 0 0 16 16 +% +% created by bmeps 1.2.7 (SCCS=1.78) +% +/pstr + 16 string +def +/inputf + currentfile + /ASCII85Decode filter + /RunLengthDecode filter +def +gsave +0 16 translate +16 16 scale +16 16 8 [16 0 0 -16 0 0] +{ inputf pstr readstring pop } +image +mJdF^dB'"3UWN!$rs@Ya]@u6"bb(3Qr;R/`V9S;S_naFJWJB%'s"j5Gb3-LGZ+7BO +cCTm[s8UHNjM8:-s8T6tVp'V$s8T.Cb-.n=s8S.NR^fMRs8S\=\ubf/$(%F'EW?'- +b-A#Es"g"7_/95PU:%M-SrE^LQ^=,IVgACCaGnB:S=T][Q^*rZDQs0@n!'EcSXPn1 +Q'fUPEU!K&$eL*#ag@\2[)e8?b5D8Ge:i1K]tC4YDp%qV#OK!PEGg',kjAB +~> +grestore +currentdict /inputf undef +currentdict /pstr undef diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/add.png b/abs/core-testing/local-website/htdocs/mythtv-doc/add.png Binary files differnew file mode 100644 index 0000000..6332fef --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/add.png diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/doxygen-architecture-document.cpp b/abs/core-testing/local-website/htdocs/mythtv-doc/doxygen-architecture-document.cpp new file mode 100644 index 0000000..16ad56d --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/doxygen-architecture-document.cpp @@ -0,0 +1,787 @@ +/** +\mainpage MythTV Architecture + +\section intro Introduction + +Over the last couple years %MythTV has grown into a rather large +application. The purpose of these pages is to provide a portal +into the code for developers to get their heads around it. +This is intended for both those new to %MythTV and experienced +with it to get familiar with different aspects of the code base. + +If you are just looking for the code formatting standards, +see the official %MythTV wiki article +<a href="http://www.mythtv.org/wiki/index.php/Coding_Standards"> +coding standards</a>. If you are looking for the +<a href="http://svn.mythtv.org/trac/wiki/TicketHowTo">bug tracker</a>, +it can be found on the official pages. +If you haven't already, you should subscribe to +the <a href="http://www.mythtv.org/mailman/listinfo/mythtv-dev/"> +developer mailing list</a> and the <a href="http://www.mythtv.org/mailman/listinfo/mythtv-commits/">SVN commits mailing list</a> + +If you just stumbled onto the developer pages +by accident, maybe you want to go to the official +<a href="http://www.mythtv.org/modules.php?name=MythInstall">%MythTV +Installation page</a>. There is also a good unofficial +<a href="http://wilsonet.com/mythtv/fcmyth.php">Fedora %MythTV installation</a> page, +and a +<a href="http://dev.gentoo.org/~cardoe/mythtv/">Gentoo %MythTV installation</a> page. + +If you are new to Qt programming it is essential that you keep in mind +that almost all Qt objects are not thread-safe, including QString. +Almost all Qt container objects, including QString, make shallow copies +on assignment, the two copies of the object must only be used in one +thread unless you use a lock on the object. You can use the +<a href="http://doc.trolltech.com/3.1/qdeepcopy.html">QDeepCopy</a> +template on most Qt containers to make a copy you can use in another +thread. + +There are also special dangers when +\ref qobject_dangers "using QObject" outside the Qt event thread. + +The is also short HOWTO on \ref profiling_mythtv available in addition +to documentation on the code itself. + +\section libs Libraries + +%MythTV is divided up into eleven libraries: +<dl> + <dt>libmyth <dd>Core %MythTV library. Used by the Plugins. + The \ref database_subsystem "database", + \ref audio_subsystem "audio", + \ref lcd_subsystem "LCD", + \ref osd_subsystem "OSD", + \ref lirc_subsystem "LIRC", and the + \ref myth_network_protocol "myth network protocol" are supported by libmyth. + <dt>libmythtv <dd>%MythTV %TV functionality library. + The + \ref recorder_subsystem "recorders", \ref video_subsystem "video" and + \ref av_player_subsystem "A/V players" are supported by libmythtv. + <dt>libmythui <dd>Main user interface rendering library + <dt>libavcodec/libavformat/libavutil + <dd>This is the ffmpeg A/V decoding library (aka avlib). + <a href="http://ffmpeg.mplayerhq.hu/documentation.html">Documented Externally</a>. + <dt>libmythmpeg2 <dd>Alternate MPEG-1/2 A/V decoding library. + <a href="http://libmpeg2.sourceforge.net/">External Website</a>. + <dt>libmythsamplerate <dd>Audio resampling library + <a href="http://www.mega-nerd.com/SRC/api.html">Documented Externally</a>. + We use this to support a different output sample rates than the sample + rate used in the audio streams we play. + <dt>libmythsoundtouch <dd>Pitch preserving audio resampling library. + <a href="http://www.surina.net/soundtouch/">External Website</a>. + We use this for the time-stretch feature. + <dt>libmythdvdnav + <dd>Used for navigating DVD menus when using the internal player + <dt>libmythfreemheg <dd>UK interactive %TV viewer + <dt>libmythlivemedia <dd>Support for the FreeBox recorder device + <dt>libmythupnp <dd>Initial uPnP (universal Plug and Play) support +</dl> +Two libraries libmythmpeg2 and libmythsamplerate appear redundant, but +libmpeg2 decodes MPEG-2 more quickly than ffmpeg on some systems, and +libmythsamplerate resamples audio with better quality when we only need +to match the hardware sample rate to the A/V streams audio sample rate. + +\section db Database Schema +The database schema is documented here \ref db_schema. + +\section apps Applications +%MythTV contains 14 applications: + +<dl> + <dt>mythbackend <dd>This is the backend which runs the recorders. + <dt>mythfrontend + <dd>This is the frontend which is the main application + for viewing programs and using the %MythTV plugins. + <dt>mythtv-setup <dd>This is the program which sets up the database + to use a machine as a backend server. + <dt>mythtv <dd>This was an "External Player" used to play videos + from within mythfrontend. Setting the player command + to "internal" does the same thing now. This is handy + for testing the audio and videoout code, though. + <dt>mythtvosd + <dd>This is used externally by programs that want to pop-up an + <i>on screen display</i> in %MythTV while one is watching a recording. + <dt>mythfilldatabase + <dd>This is used both internally and externally to fetch program listings. + <a href="http://tms.tribune.com/">Tribune Media</a> provides + listings in exchange for demographic information in the USA, + and Australia uses a + <a href="http://minnie.tuhs.org/twiki/bin/view/TVGuide"> + community-driven TV guide</a> originally developed for OzTiVo. + Other markets are served by the + <a href="http://membled.com/work/apps/xmltv/xmltv">XMLTV</a> + web spiders. + <dt>mythtranscode <dd>This is used both internally and externally to + transcode videos from one format to another. + This is used to shrink HDTV programs to lower + quality recordings that match the hardware the + user has. + <dt>mythjobqueue <dd>This is used internally by mythfrontend to schedule + jobs such as commercial flagging and transcoding. + <dt>mythcommflag <dd>This is used internally by mythfrontend to flag + commercials. + <dt>mythepg <dd>This is used internally by mythfrontend to find + upcoming programs to record based on the channel + and time. + <dt>mythprogfind <dd>This is used internally by mythfrontend to find + programs to record based on the first letter of + the program name. + <dt>mythuitest <dd>This is a test program for libmythui development. + <dt>mythlcdserver <dd>This is an interface between a number of Myth + clients and a small text display (LCDProc server). + <dt>mythwelcome/mythshutdown + <dd>These programs manage Power Saving (shutdown/wakeup) on your Myth PCs. +</dl> + +\section fe_plugins Frontend Plugins +<dl> + <dt>mytharchive <dd>Creates themed Video DVDs from recordings + (and other video files). + <dt>mythbrowser <dd>Provides a simple web browser. + <dt>mythcontrols<dd>Editor for Myth Key bindings, \e et \e c. + <dt>mythflix <dd> + <dt>mythgallery <dd>A simple picture viewer for your %TV. + <dt>mythgame <dd>Launches the xmame classic game system emulator. + <dt>mythmovies <dd> + <dt>mythmusic <dd>A simple music player for your %TV. + <dt>mythnews <dd>Browses RSS news feeds. + <dt>mythphone <dd>SIP based video phone. + <dt>mythvideo <dd>Launch DVD players, and a Video Browser for other files + (non-%MythTV recordings). + <dt>mythweather <dd>Presents your local weather report. + <dt>mythzoneminder<dd> +</dl> + +\section be_plugins Backend Plugins +<dl> + <dt>mythweb <dd>Provides a PHP based web pages to control mythbackend. +</dl> + +\section spt_scripts Support Scripts +These tools are in the contrib directory of the source tree: +<dl> + <dt>osx-packager.pl <dd>Downloads and builds all dependencies, then the + source, of %MythTV and all the official plugins, + on Mac OS 10.3 thru 10.5 + <dt>win32-packager.pl <dd>Similar tool for Windows XP +</dl> + */ + +/** \defgroup database_subsystem Database Subsystem + \todo No one is working on documenting the database subsystem. + +There are a few classes that deal directly with the database: +MythContext, MSqlDatabase, DBStorage, MDBManager, SimpleDBStorage. + +And one function UpgradeTVDatabaseSchema() located in dbcheck.cpp. + +MythTV's Configurable widgets also do save and restore their values +from the database automagically when used in %MythTV's window classes. + */ + +/** \defgroup audio_subsystem Audio Subsystem + \todo Ed W will be documenting the audio subsystem. + */ + +/** \defgroup lcd_subsystem LCD Subsystem + \todo No one is working on documenting the LCD Subsystem + */ + +/** \defgroup osd_subsystem OSD Subsystem + \todo No one is working on documenting the OSD Subsystem + */ + +/** \defgroup lirc_subsystem LIRC Subsystem + \todo No one is working on documenting the LIRC Subsystem + */ + +/** \defgroup video_subsystem Video Subsystem + \todo No one is working on documenting the video subsystem + */ + +/** \defgroup recorder_subsystem Recorder Subsystem +This line is filler that is ignored by Doxygen. + +TVRec is the main class for handling recording. +It is passed a ProgramInfo for the current and next recordings, +and in turn creates three main worker classes: +<dl> + <dt>RecorderBase <dd>Recordings from device into RingBuffer. + <dt>ChannelBase <dd>Changes the channel and other recording device attributes. Optional. + <dt>RingBuffer <dd>Handles A/V file I/O, including streaming. +</dl> + +%TVRec also presents the public face of a recordings to the +\ref myth_network_protocol, and hence the rest of %MythTV. This +means that any call to the %RecorderBase, %RingBuffer, or +%ChannelBase is marshalled via methods in the %TVRec. + +RecorderBase contains classes for recording %MythTV's +specialized Nuppel Video files, as well as classes for +handling various hardware encoding devices such as MPEG2, +HDTV, DVB and Firewire recorders. +ChannelBase meanwhile only contains three subclasses, %Channel +for handling v4l and v4l2 devices, and %DVBChannel and +%FirewireChannel, for handling DVB and Firewire respectively. +Other channel changing hardware use ChannelBase's external +channel changing program support. +Finally, RingBuffer does all reading and writing of A/V files +for both TV (playback) and %TVRec, including streaming +over network connections to the frontend's %RingBuffer. + +%TVRec has four active states, the first three of which +correspond to the same states in %TV: kState_WatchingLiveTV, +kState_WatchingPreRecorded, kState_WatchingRecording, and +kState_RecordingOnly. +When watching "Live TV" the recorder records whatever the +frontend requests and streams it out using the %RingBuffer, +this may be to disk or over the network. +When watching pre-recorded programs %TVRec simply streams a +file on disk out using the %RingBuffer. +When just watching a recording, %TVRec continues a recording +started as recording-only while simultaneously streaming out +using the %RingBuffer. +Finally, when in the recording-only mode the recording +is only saved to disk using %RingBuffer and no streaming +to the frontend is performed. + +%TVRec also has three additional states: kState_Error, +kState_None, kState_ChangingState. The error state allows +%MythTV to know when something has gone wrong. The null or +none state means the recorder is not doing anything and +is ready for commands. Finally, the "ChangingState" state +tells us that a state change request is pending, so other +state changing commands should not be issued. + +\todo Check if the TVRec is actually still passed a ProgramInfo for the current and next recordings + +\todo Document the massive changes Daniel has made in the Vid and MultiRec branches + */ + +/** \defgroup av_player_subsystem A/V Player Subsystem +This line is filler that is ignored by Doxygen. + +TV is the main class for handling playback. +It instantiates several important classes: +<dl> +<dt>NuppelVideoPlayer <dd>Decodes audio and video from the RingBuffer, then plays and displays them, resp. +<dt>RemoteEncoder <dd>Communicates with TVRec on the backend. +<dt>OSD <dd>Creates on-screen-display for NuppelVideoPlayer to display. +<dt>RingBuffer <dd>Handles A/V file I/O, including streaming. +</dl> + +NuppelVideoPlayer is a bit of a misnomer. This class plays all video formats +that %MythTV can handle. It creates AudioOutput to handle the audio, a FilterChain +to perform post-processing on the video, a DecoderBase class to do the actual +video decoding, and a VideoOutput class to do the actual video output. See +that class for more on what it does. + +%TV has three active states that correspond to the same states in TVRec: +kState_WatchingLiveTV, kState_WatchingPreRecorded, kState_WatchingRecording. +When watching "LiveTV" the %TVRec via RemoteEncoder responds to channel +changing and other commands from %TV while streaming the recording to +%TV's %RingBuffer. +When watching a pre-recorded stream, a recording is streamed from TVRec's +%RingBuffer to %TV's %RingBuffer, but no channel changing commands can be +sent to TVRec. +When watching an 'in-progress' recording things work pretty much as when +watching a pre-recorded stream, except %TV must be prevented from seeking +too far ahead in the program, and keyframe and commercial flags must be +synced from the recorder periodically. + +%TV also has three additional states: kState_Error, +kState_None, kState_ChangingState. The error state allows +%MythTV to know when something has gone wrong. The null or +none state means the player is not doing anything and +is ready for commands. Finally, the "ChangingState" state +tells us that a state change request is pending, so other +state changing commands should not be issued. + + */ + +/** \defgroup plugin_arch Plugin Architecture +This line is filler that is ignored by Doxygen. + +MythPlugins are shared object files (<I>i.e.</I> libraries) which are loaded +from a specific directory (<I>%e.g.</I> /usr/local/lib/mythtv/plugins). +Currently, all plugins are written in the C++ language, but there is nothing +preventing other languages being used (the functions are in the C name space). + +int mythplugin_init(const char *libversion); is invoked whenever mythfrontend +is started. This typically handles upgrading any database records - it will be +the first method called after a new version of the plugin has been installed. + +int mythplugin_run(); is invoked when the action attribute of a menu item +requests it via the PLUGIN directive. This is when the user chooses to enter +the plugin from the main menu or the appropriate submenu. + +int mythplugin_config(); is invoked when the action attribute of a menu item +requests it via the CONFIGPLUGIN directive. This should be when the users +wishes to change the plugin's settings (in the main Setup menu). + +Other plugin functions are listed in the file \link mythpluginapi.h \endlink +(see also the \link MythPlugin \endlink + and \link MythPluginManager \endlink classes.) + +*/ + +/** \defgroup mtd MTD (the Myth Transcoding Daemon) +This line is filler that is ignored by Doxygen. + +The %MTD is a simple program that is used by the MythVideo plugin. + +It currently \b only transcodes tracks from DVDs, but could in the +future also rip CD/VCD tracks, transcode %TV recordings, \e et \e cetera. + +The DVD Rip screen will offer to start %MTD if it is not running. +It does \b not currently shut it down afterwards, though. + +By default, the %MTD listens on port 2442, for commands of this format: + +\verbatim +halt +quit +shutdown +\endverbatim +- Tells the %MTD to wait for all jobs to finish, stop listening, and exit. + +\verbatim +hello +\endverbatim +- Send a trivial response if the %MTD is listening. + +\verbatim +status +\endverbatim +<B>\verbatim +status dvd summary 1 +status dvd job 0 overall 0.0262568 ISO copy of UNTITLED +status dvd job 0 subjob 0.0262568 Ripping to file ~ 00:08/05:04 +status dvd complete +\endverbatim</B> +- Sends a response listing the status of all jobs. + +\verbatim +media +\endverbatim +<B>\verbatim +media dvd summary 1 UNTITLED +media dvd title 1 1 1 0 5 27 8 +media dvd title-audio 1 1 2 nl ac3 2Ch +media dvd complete +\endverbatim</B> +- Sends a detailed list of titles/tracks on the current disk. + +\verbatim +job dvd TITLE AUDIOTRK QUALITY AC3 SUBTITLETRK DESTPATH +\endverbatim +\verbatim +e.g. job dvd 1 1 -1 0 -1 /myth/video/UNTITLED +\endverbatim +- Starts a transcoding job. TITLE, AUDIOTRK and SUBTITLETRK are integers + to select the track details. AC3 is 0 or 1. DESTPATH is the output file. + QUALITY is one of enum \ref RIP_QUALITIES (-1, 0 or 1). + +\verbatim +abort dvd job NNNN +\endverbatim +- Stops the job identified by the job number NNNN. + +\verbatim +use dvd PATH +\endverbatim +- Check dvd PATH is usable, and if so set the current drive to it. + +\verbatim +no dvd +\endverbatim +- Forget about the current dvd path, ending any jobs that are trying to read it. + +\verbatim +no dvd PATH +\endverbatim +- End any jobs that are reading from dvd PATH, and if it is the current drive, + forget about it. + */ + +/** \defgroup myth_media Myth Media Manager +This line is filler that is ignored by Doxygen. + +The Myth Media Manager is a thread in the frontend which looks for any +changes to removable media, and sends events to any Frontend Plugins +which are interested in that media. + +At startup, it creates a list of MythMediaDevice objects (currently +MythHDD or MythCDROM and its subclasses) for each removable device +configured on the system. A runtime loop then monitors each of these +via its checkMedia() method. + +When any of these devices change status, a MediaEvent object is created. +If the device has a status which is usable, the window jumps to the main menu +(to allow the registered jump to work correctly), and the event is dispatched +to the relevant plugin's registered media handler. If the device status is +unusable (<I>%e.g.</I> ejected), the plugin's media handler is called directly +(so it can "forget" about this device). + +The following tables show +typical status transitions for CD/DVD and USB flash drive devices: + +\verbatim + CD/DVD USB/FireWire HDD +State Action State Action +-------------------------------------------------- +NODISK NODISK + eject attach +OPEN USEABLE + insert disk, close detach +USEABLE UNPLUGGED + mount +MOUNTED + unmount +NOTMOUNTED +-------------------------------------------------- +\endverbatim + */ + +/** \defgroup myth_network_protocol Myth Network Protocol +This line is filler that is ignored by Doxygen. + +The MythTV backend process currently opens sockets for three different types +of commands; a custom protocol (by default at port 6543), +an HTML server (by default <A HREF="http://127.0.0.1:6544"> +http://127.0.0.1:6544 +</A> for the status, and other services under that, like +< HREF="http://127.0.0.1:6544/Myth/GetMusic?Id=1"> +http://127.0.0.1:6544/Myth/GetMusic?Id=1 +</A>), and a UPnP media server (several ports that I cannot +remember right now that throw around lots of little bits of XML :-) + +The custom protocol is an ASCII encoded length and command string. +Command sequences can be easily sent to the backend using telnet. +<I>%e.g.</I> \verbatim telnet 127.0.0.1 5432 +Trying 127.0.0.1... +Connected to localhost. +Escape character is '^]'.\endverbatim +<B>\verbatim21 MYTH_PROTO_VERSION 36 23 ANN Playback hostname 1 10 QUERY_LOAD 4DONE\endverbatim</B> +\verbatim13 ACCEPT[]:[]362 OK34 0.919922[]:[]0.908203[]:[]0.856445Connection closed by foreign host.\endverbatim +The command string is prefixed by 8 characters, containing the length +of the forthcoming command. This can be justified in any way +(as the above example shows) + +The backend responds with a length, and the response to the command. +This can be numbers (up to 32 bit, represented in ASCII), +a single string, or an ASCII encoding of a QStringList. +The 5 byte sequence "[]:[]" seperates items in the stringlist. +Any 64 bit numbers are represented as a stringlist of two 32bit words +(MSB first). + +\section commands Commands + +There are three main types of networking interactions in MythTV; +identification commands (which tell the backend about this client), +query commands that are sent to the master backend +(<I>%e.g.</I> listing recordings or viewing guide data), and +file streaming commands (when a frontend is watching or editing a recording). + +Until a client is identified to the backend (via the ANN commands), +any of the query or file streaming commands will silently fail. + +The following summarises some of these commands. +For a full understanding of all the commands, either read the source code +(programs/mythbackend/mainserver.cpp), or look on the Wiki +(http://www.mythtv.org/wiki/index.php/Myth_Protocol_Command_List). + + */ + +/** \defgroup qobject_dangers QObject is dangerous for your health +This line is filler that is ignored by Doxygen. + +QObject derived classes can be quite useful, they can send and receive +signals, get keyboard events, translate strings into another language +and use QTimers. + +But they also can't be \ref qobject_delete "deleted" easily, they +are not \ref qobject_threadsafe "thread-safe", can't participate +as equals in multiple \ref qobject_inheritence "inheritence", can +not be used at all in virtual \ref qobject_inheritence "inheritence". + +\section qobject_delete Deleting QObjects + +The problem with deleting QObjects has to do with signals, and events. +These can arrive from any thread, and often arrive from the Qt event +thread even if you have not explicitly requested them. + +If you have not explicitly connected any signals or slots, and the +only events you might get are dispatched with qApp->postEvent(), +not qApp->sendEvent(), then it is safe to delete the QObject in the +Qt event thread. If your QObject is a GUI object you've passed +given to Qt for it to delete all is good. If your object is only +deleted in response to a posted event or a signal from the Qt event +thread (say from a QTimer()) then you are OK as well. + +If your class may be deleted outside a Qt thread, but it does not +explicitly connect any signals or slots, and the only events it +might get are dispatched with qApp->postEvent(), then you can +safely use deleteLater() to queue your object up for deletion +in the event thread. + +%MythTV is a very much a multithreaded program so you may need to have +a QObject that may get events from another thread if you send signals +but do not get any signals and or events from outside the Qt event +thread, then you can use deleteLater() or delete depending on whether +you are deleteing the QObject in the event thread, see above. But +if you are not in the Qt event thread then you need to call disconnect() +in the thread that is sending the signals, before calling deleteLater(). +This prevents your object from sending events after you consider it +deleted (and begin to delete other QObjects that may still be getting +signals from your object.) + +What about if you are getting events via qApp->sendEvent() or a signal +from another thread? In this case things get complicated, so we highly +discourage this in %MythTV and prefer that you use callbacks if at all +possible. But in say you need to do this, then you need to disconnect +all the signals being sent to your QObject. But disconnect() itself +is not atomic. That is you may still get a signal after you disconnect +it. What you need to is disconnect the signal from your slot in the +thread that is sending the signal. This prevents the signal from +being emitted while you are disconnecting. Doing this gracefully is +left as an excersize for the reader. + +Ok, so the above is not entirely complete, for instance you could wrap +every signal emit in an instance lock and reimplement a disconnect +that uses that instance lock. But if you've figured this or another +solution out already all you need to know is that almost all Qt +objects are reenterant but not thread-safe, and that QObjects recieve +events and signals from the Qt event thread and from other threads +if you use qApp->sendEvent() or send signals to it from another thread. + +\section qobject_threadsafe QObject thread-safety + +The only thread-safe classes in Qt are QThread and the mutex classes. +when you call any non-static QObject method you must have a lock on +it or make sure only thread ever calls that function. + +QObject itself is pretty safe because when you assign one QObject to +another you make a copy. Qt's container classes, including QString +do not make a copy but rather pass a reference counted pointer to +the data when you assign one to another. This reference counter is +not protected by a mutex so you can not use regular assignment when +passing a QString or other Qt container from one thread to another. + +In order to use these classes safely you must use +<a href="http://doc.trolltech.com/3.1/qdeepcopy.html">QDeepCopy</a> +when passing them from one thread to another. This is thankfully quite +easy to use. + +\code + QString original = "hello world"; + QString unsafe = original; + QString safe = QDeepCopy<QString>(original); +\endcode + +In this case safe and original can be used by two seperate +threads, while unsafe can only be used in the same thread +as originalStr. + +The QDeepCopy template will work on the most popular Qt containers, +for the ones it doesn't support you will have to copy manually. + +\section qobject_inheritence QObject inheritence + +You can not inherit more than one QObject derived class. +This is because of how signals and slots are implemented. What +happens is that each slot is transformed into an integer that +is used to find the right function pointer quickly when a signal +is sent. But if you have more than one QObject in the inheritence +tree the integers will alias so that signals intended for the +second slot in parent class B might get sent to the second slot +in parent class A instead. Badness ensues. + +For the similar reason you can not inherit a QObject derived +class virtually, in this case the badness is a little more +complicated. The result is the same however, signals arrive +at the wrong slot. Usually, what happens is that the developer +tries to inherit two QObject derived classes but gets linking +errors, so they make one or more of the classes virtual, or +inherit a QObject non-virtually but then also inherit one +or more QObject derived classes virtually. The linker doesn't +complain, but strange unexplainable behaviour ensues when +the application is run and signals start showing up on the +wrong slots. + +*/ + +/** \defgroup profiling_mythtv Profiling MythTV +This line is filler that is ignored by Doxygen. + +You can use any sampling profiler to profile %MythTV, the most +popular GPL one is OProfile and this section tells you how to +use it to profile %MythTV. For Intel also makes VTune, AMD +makes CodeAnalyst, and Apple makes Shark. These all work +similarly to oprofile, so the %MythTV portions are the same. + +This do not describe how to install oprofile. There are a +few cotchas on installation: You must have APIC enabled to +use performance counters. This is usually the default, but +you may want to check this in your kernel configuration. You +also need the oprofile module, this is part of the kernel +config in Linux 2.6+, but must be compiled seperately for +earlier kernels. Finally, some RedHat kernels does not work +with the standard oprofile, so you must use the RedHat +version of oprofile, or compile your own kernel. + + +\section prof_compile Compiling MythTV for profiling + +The first thing you need to do is compile with profiling in +mind. %MythTV has three compile types "release", "debug" and +"profile". The "release" type enables optimizations that +make debugging practically impossible, while "debug" has so +few optimizations that profiling it usually won't tell you +where the real performance problems are. The "profile" compile +type enables the all the optimizations in "release" but also +enables debugging symbols, so that you know which functions +are the CPU hogs. + +So we configure thusly: +\code + make distclean + ./configure --compile-type=profile --enable-proc-opt [+your normal opts] +\endcode + +The "make distclean" clears out all your old binaries and the the configure +sets the compile type approriately. You may not want the "--enable-proc-opt" +if you plan on making a package for other CPUs. This only makes about a +10% difference in playback speed because MMX and CMOV are enabled for +CPUs that support them regardless of this option. + +Next, you compile and install %MythTV as you normally would. +\code + qmake; make -j2 -k + su + make install +\endcode + + +\section prof_init Initializing profiler + +Most sampling profilers, OProfile included, require a kernel module so +this module must be loaded. In oprofile's case the module gets confused +when it has been loaded a long time, so it is best to begin each session +by shutting down the OProfile server and reloading the module: + +\code + opcontrol --deinit + opcontrol --init +\endcode + +You also will want to tell the profiler whether to profile the +kernel as well, if you want the kernel profiled, and assuming +your compiled kernel is in /usr/src/linux, issue this command: +\code + opcontrol --vmlinux=/usr/src/linux/vmlinux +\endcode +If you don't want it in your profile report, use this command: +\code + opcontrol --no-vmlinux +\endcode +Normally, you don't need it when profiling %MythTV, but there are +times when the kernel is a bottleneck. For example when writing +streams to disk is taking too long. + +Now all CPU's are not profiled the same way. In the days of olde, +a sampling profiler would hook into the clock interupt and record +the instuction pointer's location at the instant the interrupt was +triggered. But the wall clock timer still ticks as often as it did +when CPU's ran at 5 Mhz, and now they run almost a thousand times +faster. Such a profile would now take a thousand times longer than +it did in 1985. + +So modern processors include explicit support for profiling. For, +example the Pentium Pro has the INST_RETIRED counter, the Pentium 4 +has the INSTR_RETIRED counter, the AMD64 has the RETIRED_INSNS +counter, etc. For a full list see the +<a href="http://oprofile.sourceforge.net/docs/">OProfile documentation</a>. +You need to find a performance counter you can use for your CPU, +after you've run "opcontrol --init" you can run the following command: +\code + opcontrol --list-events +\endcode +And it will list all the performance counters available with your +CPU. You need to pick the best one for what you want to measure, +for overall performance you want something line INSTR_RETIRED. + +For an Intel Pentium 4, the following will work +\code + opcontrol -e INSTR_RETIRED:6000:0x0f:0:1 +\endcode + +This tells OProfile to schedule an interrupt on every 6000th +instruction that finishes and matches the flag 0x0f. You +could also count cycles when not in idle for the same type of +measurements. The last two numbers tell OProfile it should not +profile the kernel and should profile userspace, if you want +to profile the kernel as well you need to replace the zero with +a one. + +It is possible to profile in oprofile the old fashioned way, by +using the real-time-clock. But you must compile your Linux kernel +WITHOUT RTC support, and run %MythTV significantly longer to get +enough samples for a good report. + + +\section prof_run Running Profiler + +Normally, oprofile will tell you about everything running in +its reports. You can limit what information is collected by +running a opcontrol command such as: +\code + opcontrol --image=/usr/local/bin/mythfrontend +\endcode +This tells OProfile to only profile the frontend. + +Now you want to start %MythTV as usual: + +Then begin doing whatever you want to profile, then issue these +commands: +\code + opcontrol --reset ; opcontrol --start +\endcode + +After a few seconds/minutes your should have collected enough data. +Then you want to issue the following commands: +\code + opcontrol --shutdown + opreport --merge tgid -l --image-path=/usr/local/bin > report.txt +\endcode + +Now you can peruse the report at your pleasure. + +This should be enough to get you started with finding and fixing +performance problems in %MythTV, but there is more information +available from the +<a href=http://oprofile.sourceforge.net/doc/index.html>OProfile manual</a>. +This includes information on constructing callgraphs, producing +an annotated versions of the code, and saving results. + +*/ + +// The file ac3.h in ffmpeg contains no Doxygen markup, +// but for some reason generates the following modules: +// * Coded elements +// * Derived values +// +// They add nothing useful to this programmer doco, so I camouflage these +// by manually defining the block here. Same thing for the few modules +// in ffmpeg that are documented; Macroblock and VC9 bitplanes from vc1.c, +// Monkey Audio from apedec.c, multithreaded slicing from h264.h, + +/** + @defgroup coded . + @defgroup derived . + @defgroup block . + @defgroup std_mb . + @defgroup rangecoder . + @defgroup multithreading . + @defgroup bitplane . + */ diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/doxygen-create-developer-docs.cfg b/abs/core-testing/local-website/htdocs/mythtv-doc/doxygen-create-developer-docs.cfg new file mode 100644 index 0000000..c00b3cf --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/doxygen-create-developer-docs.cfg @@ -0,0 +1,1142 @@ +# Doxyfile 1.3.7 + +# This file describes the settings to be used by the documentation system +# doxygen (www.doxygen.org) for a project +# +# All text after a hash (#) is considered a comment and will be ignored +# The format is: +# TAG = value [value, ...] +# For lists items can also be appended using: +# TAG += value [value, ...] +# Values that contain spaces should be placed between quotes (" ") + +#--------------------------------------------------------------------------- +# Project related configuration options +#--------------------------------------------------------------------------- + +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded +# by quotes) that should identify the project. + +PROJECT_NAME = MythTV + +# The PROJECT_NUMBER tag can be used to enter a project or revision number. +# This could be handy for archiving the generated documentation or +# if some version control system is used. + +PROJECT_NUMBER = 0.21 + +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) +# base path where the generated documentation will be put. +# If a relative path is entered, it will be relative to the location +# where doxygen was started. If left blank the current directory will be used. + +OUTPUT_DIRECTORY = doxygen-dev-docs + +# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create +# 2 levels of 10 sub-directories under the output directory of each output +# format and will distribute the generated files over these directories. +# Enabling this option can be useful when feeding doxygen a huge amount of source +# files, where putting all generated files in the same directory would otherwise +# cause performance problems for the file system. + +CREATE_SUBDIRS = NO + +# The OUTPUT_LANGUAGE tag is used to specify the language in which all +# documentation generated by doxygen is written. Doxygen will use this +# information to generate all constant output in the proper language. +# The default language is English, other supported languages are: +# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, +# Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en +# (Japanese with English messages), Korean, Korean-en, Norwegian, Polish, Portuguese, +# Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian. + +OUTPUT_LANGUAGE = English + +# This tag can be used to specify the encoding used in the generated output. +# The encoding is not always determined by the language that is chosen, +# but also whether or not the output is meant for Windows or non-Windows users. +# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES +# forces the Windows encoding (this is the default for the Windows binary), +# whereas setting the tag to NO uses a Unix-style encoding (the default for +# all platforms other than Windows). + +USE_WINDOWS_ENCODING = NO + +# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will +# include brief member descriptions after the members that are listed in +# the file and class documentation (similar to JavaDoc). +# Set to NO to disable this. + +BRIEF_MEMBER_DESC = YES + +# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend +# the brief description of a member or function before the detailed description. +# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the +# brief descriptions will be completely suppressed. + +REPEAT_BRIEF = YES + +# This tag implements a quasi-intelligent brief description abbreviator +# that is used to form the text in various listings. Each string +# in this list, if found as the leading text of the brief description, will be +# stripped from the text and the result after processing the whole list, is used +# as the annotated text. Otherwise, the brief description is used as-is. If left +# blank, the following values are used ("$name" is automatically replaced with the +# name of the entity): "The $name class" "The $name widget" "The $name file" +# "is" "provides" "specifies" "contains" "represents" "a" "an" "the" + +ABBREVIATE_BRIEF = + +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then +# Doxygen will generate a detailed section even if there is only a brief +# description. + +ALWAYS_DETAILED_SEC = YES + +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited +# members of a class in the documentation of that class as if those members were +# ordinary class members. Constructors, destructors and assignment operators of +# the base classes will not be shown. + +INLINE_INHERITED_MEMB = NO + +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full +# path before files name in the file list and in the header files. If set +# to NO the shortest path that makes the file name unique will be used. + +FULL_PATH_NAMES = NO + +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag +# can be used to strip a user-defined part of the path. Stripping is +# only done if one of the specified strings matches the left-hand part of +# the path. The tag can be used to show relative paths in the file list. +# If left blank the directory from which doxygen is run is used as the +# path to strip. + +STRIP_FROM_PATH = + +# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of +# the path mentioned in the documentation of a class, which tells +# the reader which header file to include in order to use a class. +# If left blank only the name of the header file containing the class +# definition is used. Otherwise one should specify the include paths that +# are normally passed to the compiler using the -I flag. + +STRIP_FROM_INC_PATH = + +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter +# (but less readable) file names. This can be useful is your file systems +# doesn't support long names like on DOS, Mac, or CD-ROM. + +SHORT_NAMES = NO + +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen +# will interpret the first line (until the first dot) of a JavaDoc-style +# comment as the brief description. If set to NO, the JavaDoc +# comments will behave just like the Qt-style comments (thus requiring an +# explicit @brief command for a brief description. + +JAVADOC_AUTOBRIEF = YES + +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen +# treat a multi-line C++ special comment block (i.e. a block of //! or /// +# comments) as a brief description. This used to be the default behaviour. +# The new default is to treat a multi-line C++ comment block as a detailed +# description. Set this tag to YES if you prefer the old behaviour instead. + +MULTILINE_CPP_IS_BRIEF = NO + +# If the DETAILS_AT_TOP tag is set to YES then Doxygen +# will output the detailed description near the top, like JavaDoc. +# If set to NO, the detailed description appears after the member +# documentation. + +DETAILS_AT_TOP = YES + +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented +# member inherits the documentation from any documented member that it +# re-implements. + +INHERIT_DOCS = YES + +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC +# tag is set to YES, then doxygen will reuse the documentation of the first +# member in the group (if any) for the other members of the group. By default +# all members of a group must be documented explicitly. + +DISTRIBUTE_GROUP_DOC = NO + +# The TAB_SIZE tag can be used to set the number of spaces in a tab. +# Doxygen uses this value to replace tabs by spaces in code fragments. + +TAB_SIZE = 8 + +# This tag can be used to specify a number of aliases that acts +# as commands in the documentation. An alias has the form "name=value". +# For example adding "sideeffect=\par Side Effects:\n" will allow you to +# put the command \sideeffect (or @sideeffect) in the documentation, which +# will result in a user-defined paragraph with heading "Side Effects:". +# You can put \n's in the value part of an alias to insert newlines. + +ALIASES = "sideeffect=\par Side Effects:\n" + +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources +# only. Doxygen will then generate output that is more tailored for C. +# For instance, some of the names that are used will be different. The list +# of all members will be omitted, etc. + +OPTIMIZE_OUTPUT_FOR_C = NO + +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources +# only. Doxygen will then generate output that is more tailored for Java. +# For instance, namespaces will be presented as packages, qualified scopes +# will look different, etc. + +OPTIMIZE_OUTPUT_JAVA = NO + +# Set the SUBGROUPING tag to YES (the default) to allow class member groups of +# the same type (for instance a group of public functions) to be put as a +# subgroup of that type (e.g. under the Public Functions section). Set it to +# NO to prevent subgrouping. Alternatively, this can be done per class using +# the \nosubgrouping command. + +SUBGROUPING = YES + +#--------------------------------------------------------------------------- +# Build related configuration options +#--------------------------------------------------------------------------- + +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in +# documentation are documented, even if no documentation was available. +# Private class members and static file members will be hidden unless +# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES + +EXTRACT_ALL = YES + +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class +# will be included in the documentation. + +EXTRACT_PRIVATE = YES + +# If the EXTRACT_STATIC tag is set to YES all static members of a file +# will be included in the documentation. + +EXTRACT_STATIC = YES + +# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) +# defined locally in source files will be included in the documentation. +# If set to NO only classes defined in header files are included. + +EXTRACT_LOCAL_CLASSES = YES + +# This flag is only useful for Objective-C code. When set to YES local +# methods, which are defined in the implementation section but not in +# the interface are included in the documentation. +# If set to NO (the default) only methods in the interface are included. + +EXTRACT_LOCAL_METHODS = NO + +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all +# undocumented members of documented classes, files or namespaces. +# If set to NO (the default) these members will be included in the +# various overviews, but no documentation section is generated. +# This option has no effect if EXTRACT_ALL is enabled. + +HIDE_UNDOC_MEMBERS = NO + +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all +# undocumented classes that are normally visible in the class hierarchy. +# If set to NO (the default) these classes will be included in the various +# overviews. This option has no effect if EXTRACT_ALL is enabled. + +HIDE_UNDOC_CLASSES = NO + +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all +# friend (class|struct|union) declarations. +# If set to NO (the default) these declarations will be included in the +# documentation. + +HIDE_FRIEND_COMPOUNDS = NO + +# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any +# documentation blocks found inside the body of a function. +# If set to NO (the default) these blocks will be appended to the +# function's detailed documentation block. + +HIDE_IN_BODY_DOCS = YES + +# The INTERNAL_DOCS tag determines if documentation +# that is typed after a \internal command is included. If the tag is set +# to NO (the default) then the documentation will be excluded. +# Set it to YES to include the internal documentation. + +INTERNAL_DOCS = NO + +# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate +# file names in lower-case letters. If set to YES upper-case letters are also +# allowed. This is useful if you have classes or files whose names only differ +# in case and if your file system supports case sensitive file names. Windows +# users are advised to set this option to NO. + +CASE_SENSE_NAMES = YES + +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen +# will show members with their full class and namespace scopes in the +# documentation. If set to YES the scope will be hidden. + +HIDE_SCOPE_NAMES = NO + +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen +# will put a list of the files that are included by a file in the documentation +# of that file. + +SHOW_INCLUDE_FILES = YES + +# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] +# is inserted in the documentation for inline members. + +INLINE_INFO = YES + +# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen +# will sort the (detailed) documentation of file and class members +# alphabetically by member name. If set to NO the members will appear in +# declaration order. + +SORT_MEMBER_DOCS = NO + +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the +# brief documentation of file, namespace and class members alphabetically +# by member name. If set to NO (the default) the members will appear in +# declaration order. + +SORT_BRIEF_DOCS = NO + +# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be +# sorted by fully-qualified names, including namespaces. If set to +# NO (the default), the class list will be sorted only by class name, +# not including the namespace part. +# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. +# Note: This option applies only to the class list, not to the +# alphabetical list. + +SORT_BY_SCOPE_NAME = NO + +# The GENERATE_TODOLIST tag can be used to enable (YES) or +# disable (NO) the todo list. This list is created by putting \todo +# commands in the documentation. + +GENERATE_TODOLIST = YES + +# The GENERATE_TESTLIST tag can be used to enable (YES) or +# disable (NO) the test list. This list is created by putting \test +# commands in the documentation. + +GENERATE_TESTLIST = YES + +# The GENERATE_BUGLIST tag can be used to enable (YES) or +# disable (NO) the bug list. This list is created by putting \bug +# commands in the documentation. + +GENERATE_BUGLIST = YES + +# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or +# disable (NO) the deprecated list. This list is created by putting +# \deprecated commands in the documentation. + +GENERATE_DEPRECATEDLIST= YES + +# The ENABLED_SECTIONS tag can be used to enable conditional +# documentation sections, marked by \if sectionname ... \endif. + +ENABLED_SECTIONS = + +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines +# the initial value of a variable or define consists of for it to appear in +# the documentation. If the initializer consists of more lines than specified +# here it will be hidden. Use a value of 0 to hide initializers completely. +# The appearance of the initializer of individual variables and defines in the +# documentation can be controlled using \showinitializer or \hideinitializer +# command in the documentation regardless of this setting. + +MAX_INITIALIZER_LINES = 30 + +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated +# at the bottom of the documentation of classes and structs. If set to YES the +# list will mention the files that were used to generate the documentation. + +SHOW_USED_FILES = YES + +#--------------------------------------------------------------------------- +# configuration options related to warning and progress messages +#--------------------------------------------------------------------------- + +# The QUIET tag can be used to turn on/off the messages that are generated +# by doxygen. Possible values are YES and NO. If left blank NO is used. + +QUIET = NO + +# The WARNINGS tag can be used to turn on/off the warning messages that are +# generated by doxygen. Possible values are YES and NO. If left blank +# NO is used. + +WARNINGS = YES + +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will +# automatically be disabled. + +WARN_IF_UNDOCUMENTED = YES + +# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for +# potential errors in the documentation, such as not documenting some +# parameters in a documented function, or documenting parameters that +# don't exist or using markup commands wrongly. + +WARN_IF_DOC_ERROR = YES + +# The WARN_FORMAT tag determines the format of the warning messages that +# doxygen can produce. The string should contain the $file, $line, and $text +# tags, which will be replaced by the file and line number from which the +# warning originated and the warning text. + +WARN_FORMAT = "$file:$line: $text" + +# The WARN_LOGFILE tag can be used to specify a file to which warning +# and error messages should be written. If left blank the output is written +# to stderr. + +WARN_LOGFILE = doxygen-warnings.txt + +#--------------------------------------------------------------------------- +# configuration options related to the input files +#--------------------------------------------------------------------------- + +# The INPUT tag can be used to specify the files and/or directories that contain +# documented source files. You may enter file names like "myfile.cpp" or +# directories like "/usr/src/myproject". Separate the files or directories +# with spaces. + +INPUT = doxygen-architecture-document.cpp ../contrib ../filters ../libs ../programs ../../mythplugins + +# If the value of the INPUT tag contains directories, you can use the +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +# and *.h) to filter out the source-files in the directories. If left +# blank the following patterns are tested: +# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp +# *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm + +FILE_PATTERNS = *.cpp *.c *.h *.mm *.pl *.pm *.sh *.py *.php *.css + +# The RECURSIVE tag can be used to turn specify whether or not subdirectories +# should be searched for input files as well. Possible values are YES and NO. +# If left blank NO is used. + +RECURSIVE = YES + +# The EXCLUDE tag can be used to specify files and/or directories that should +# excluded from the INPUT source files. This way you can easily exclude a +# subdirectory from a directory tree whose root is specified with the INPUT tag. + +EXCLUDE = ../libs/libmythsamplerate + +# The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories +# that are symbolic links (a Unix filesystem feature) are excluded from the input. + +EXCLUDE_SYMLINKS = NO + +# If the value of the INPUT tag contains directories, you can use the +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude +# certain files from those directories. + +EXCLUDE_PATTERNS = moc_*.cpp moc_*.h + +# The EXAMPLE_PATH tag can be used to specify one or more files or +# directories that contain example code fragments that are included (see +# the \include command). + +EXAMPLE_PATH = + +# If the value of the EXAMPLE_PATH tag contains directories, you can use the +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +# and *.h) to filter out the source-files in the directories. If left +# blank all files are included. + +EXAMPLE_PATTERNS = + +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be +# searched for input files to be used with the \include or \dontinclude +# commands irrespective of the value of the RECURSIVE tag. +# Possible values are YES and NO. If left blank NO is used. + +EXAMPLE_RECURSIVE = NO + +# The IMAGE_PATH tag can be used to specify one or more files or +# directories that contain image that are included in the documentation (see +# the \image command). + +IMAGE_PATH = + +# The INPUT_FILTER tag can be used to specify a program that doxygen should +# invoke to filter for each input file. Doxygen will invoke the filter program +# by executing (via popen()) the command <filter> <input-file>, where <filter> +# is the value of the INPUT_FILTER tag, and <input-file> is the name of an +# input file. Doxygen will then use the output that the filter program writes +# to standard output. + +INPUT_FILTER = + +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using +# INPUT_FILTER) will be used to filter the input files when producing source +# files to browse (i.e. when SOURCE_BROWSER is set to YES). + +FILTER_SOURCE_FILES = NO + +#--------------------------------------------------------------------------- +# configuration options related to source browsing +#--------------------------------------------------------------------------- + +# If the SOURCE_BROWSER tag is set to YES then a list of source files will +# be generated. Documented entities will be cross-referenced with these sources. +# Note: To get rid of all source code in the generated output, make sure also +# VERBATIM_HEADERS is set to NO. + +SOURCE_BROWSER = YES + +# Setting the INLINE_SOURCES tag to YES will include the body +# of functions and classes directly in the documentation. + +INLINE_SOURCES = NO + +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct +# doxygen to hide any special comment blocks from generated source code +# fragments. Normal C and C++ comments will always remain visible. + +STRIP_CODE_COMMENTS = YES + +# If the REFERENCED_BY_RELATION tag is set to YES (the default) +# then for each documented function all documented +# functions referencing it will be listed. + +REFERENCED_BY_RELATION = YES + +# If the REFERENCES_RELATION tag is set to YES (the default) +# then for each documented function all documented entities +# called/used by that function will be listed. + +REFERENCES_RELATION = NO + +# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen +# will generate a verbatim copy of the header file for each class for +# which an include is specified. Set to NO to disable this. + +VERBATIM_HEADERS = YES + +#--------------------------------------------------------------------------- +# configuration options related to the alphabetical class index +#--------------------------------------------------------------------------- + +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index +# of all compounds will be generated. Enable this if the project +# contains a lot of classes, structs, unions or interfaces. + +ALPHABETICAL_INDEX = YES + +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns +# in which this list will be split (can be a number in the range [1..20]) + +COLS_IN_ALPHA_INDEX = 3 + +# In case all classes in a project start with a common prefix, all +# classes will be put under the same header in the alphabetical index. +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that +# should be ignored while generating the index headers. + +IGNORE_PREFIX = + +#--------------------------------------------------------------------------- +# configuration options related to the HTML output +#--------------------------------------------------------------------------- + +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will +# generate HTML output. + +GENERATE_HTML = YES + +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `html' will be used as the default path. + +HTML_OUTPUT = html + +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for +# each generated HTML page (for example: .htm,.php,.asp). If it is left blank +# doxygen will generate files with .html extension. + +HTML_FILE_EXTENSION = .html + +# The HTML_HEADER tag can be used to specify a personal HTML header for +# each generated HTML page. If it is left blank doxygen will generate a +# standard header. + +HTML_HEADER = + +# The HTML_FOOTER tag can be used to specify a personal HTML footer for +# each generated HTML page. If it is left blank doxygen will generate a +# standard footer. + +HTML_FOOTER = + +# The HTML_STYLESHEET tag can be used to specify a user-defined cascading +# style sheet that is used by each HTML page. It can be used to +# fine-tune the look of the HTML output. If the tag is left blank doxygen +# will generate a default style sheet. Note that doxygen will try to copy +# the style sheet file to the HTML output directory, so don't put your own +# stylesheet in the HTML output directory as well, or it will be erased! + +HTML_STYLESHEET = + +# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, +# files or namespaces will be aligned in HTML using tables. If set to +# NO a bullet list will be used. + +HTML_ALIGN_MEMBERS = YES + +# If the GENERATE_HTMLHELP tag is set to YES, additional index files +# will be generated that can be used as input for tools like the +# Microsoft HTML help workshop to generate a compressed HTML help file (.chm) +# of the generated HTML documentation. + +GENERATE_HTMLHELP = NO + +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can +# be used to specify the file name of the resulting .chm file. You +# can add a path in front of the file if the result should not be +# written to the html output directory. + +CHM_FILE = + +# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can +# be used to specify the location (absolute path including file name) of +# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run +# the HTML help compiler on the generated index.hhp. + +HHC_LOCATION = + +# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag +# controls if a separate .chi index file is generated (YES) or that +# it should be included in the master .chm file (NO). + +GENERATE_CHI = NO + +# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag +# controls whether a binary table of contents is generated (YES) or a +# normal table of contents (NO) in the .chm file. + +BINARY_TOC = NO + +# The TOC_EXPAND flag can be set to YES to add extra items for group members +# to the contents of the HTML help documentation and to the tree view. + +TOC_EXPAND = NO + +# The DISABLE_INDEX tag can be used to turn on/off the condensed index at +# top of each HTML page. The value NO (the default) enables the index and +# the value YES disables it. + +DISABLE_INDEX = NO + +# This tag can be used to set the number of enum values (range [1..20]) +# that doxygen will group on one line in the generated HTML documentation. + +ENUM_VALUES_PER_LINE = 4 + +# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be +# generated containing a tree-like index structure (just like the one that +# is generated for HTML Help). For this to work a browser that supports +# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, +# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are +# probably better off using the HTML help feature. + +GENERATE_TREEVIEW = NO + +# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be +# used to set the initial width (in pixels) of the frame in which the tree +# is shown. + +TREEVIEW_WIDTH = 250 + +#--------------------------------------------------------------------------- +# configuration options related to the LaTeX output +#--------------------------------------------------------------------------- + +# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will +# generate Latex output. + +GENERATE_LATEX = NO + +# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `latex' will be used as the default path. + +LATEX_OUTPUT = latex + +# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be +# invoked. If left blank `latex' will be used as the default command name. + +LATEX_CMD_NAME = latex + +# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to +# generate index for LaTeX. If left blank `makeindex' will be used as the +# default command name. + +MAKEINDEX_CMD_NAME = makeindex + +# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact +# LaTeX documents. This may be useful for small projects and may help to +# save some trees in general. + +COMPACT_LATEX = NO + +# The PAPER_TYPE tag can be used to set the paper type that is used +# by the printer. Possible values are: a4, a4wide, letter, legal and +# executive. If left blank a4wide will be used. + +PAPER_TYPE = a4wide + +# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX +# packages that should be included in the LaTeX output. + +EXTRA_PACKAGES = + +# The LATEX_HEADER tag can be used to specify a personal LaTeX header for +# the generated latex document. The header should contain everything until +# the first chapter. If it is left blank doxygen will generate a +# standard header. Notice: only use this tag if you know what you are doing! + +LATEX_HEADER = + +# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated +# is prepared for conversion to pdf (using ps2pdf). The pdf file will +# contain links (just like the HTML output) instead of page references +# This makes the output suitable for online browsing using a pdf viewer. + +PDF_HYPERLINKS = NO + +# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of +# plain latex in the generated Makefile. Set this option to YES to get a +# higher quality PDF documentation. + +USE_PDFLATEX = NO + +# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. +# command to the generated LaTeX files. This will instruct LaTeX to keep +# running if errors occur, instead of asking the user for help. +# This option is also used when generating formulas in HTML. + +LATEX_BATCHMODE = NO + +# If LATEX_HIDE_INDICES is set to YES then doxygen will not +# include the index chapters (such as File Index, Compound Index, etc.) +# in the output. + +LATEX_HIDE_INDICES = NO + +#--------------------------------------------------------------------------- +# configuration options related to the RTF output +#--------------------------------------------------------------------------- + +# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output +# The RTF output is optimized for Word 97 and may not look very pretty with +# other RTF readers or editors. + +GENERATE_RTF = NO + +# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `rtf' will be used as the default path. + +RTF_OUTPUT = rtf + +# If the COMPACT_RTF tag is set to YES Doxygen generates more compact +# RTF documents. This may be useful for small projects and may help to +# save some trees in general. + +COMPACT_RTF = NO + +# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated +# will contain hyperlink fields. The RTF file will +# contain links (just like the HTML output) instead of page references. +# This makes the output suitable for online browsing using WORD or other +# programs which support those fields. +# Note: wordpad (write) and others do not support links. + +RTF_HYPERLINKS = NO + +# Load stylesheet definitions from file. Syntax is similar to doxygen's +# config file, i.e. a series of assignments. You only have to provide +# replacements, missing definitions are set to their default value. + +RTF_STYLESHEET_FILE = + +# Set optional variables used in the generation of an rtf document. +# Syntax is similar to doxygen's config file. + +RTF_EXTENSIONS_FILE = + +#--------------------------------------------------------------------------- +# configuration options related to the man page output +#--------------------------------------------------------------------------- + +# If the GENERATE_MAN tag is set to YES (the default) Doxygen will +# generate man pages + +GENERATE_MAN = NO + +# The MAN_OUTPUT tag is used to specify where the man pages will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `man' will be used as the default path. + +MAN_OUTPUT = man + +# The MAN_EXTENSION tag determines the extension that is added to +# the generated man pages (default is the subroutine's section .3) + +MAN_EXTENSION = .3 + +# If the MAN_LINKS tag is set to YES and Doxygen generates man output, +# then it will generate one additional man file for each entity +# documented in the real man page(s). These additional files +# only source the real man page, but without them the man command +# would be unable to find the correct page. The default is NO. + +MAN_LINKS = NO + +#--------------------------------------------------------------------------- +# configuration options related to the XML output +#--------------------------------------------------------------------------- + +# If the GENERATE_XML tag is set to YES Doxygen will +# generate an XML file that captures the structure of +# the code including all documentation. + +GENERATE_XML = NO + +# The XML_OUTPUT tag is used to specify where the XML pages will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# put in front of it. If left blank `xml' will be used as the default path. + +XML_OUTPUT = xml + +# The XML_SCHEMA tag can be used to specify an XML schema, +# which can be used by a validating XML parser to check the +# syntax of the XML files. + +XML_SCHEMA = + +# The XML_DTD tag can be used to specify an XML DTD, +# which can be used by a validating XML parser to check the +# syntax of the XML files. + +XML_DTD = + +# If the XML_PROGRAMLISTING tag is set to YES Doxygen will +# dump the program listings (including syntax highlighting +# and cross-referencing information) to the XML output. Note that +# enabling this will significantly increase the size of the XML output. + +XML_PROGRAMLISTING = YES + +#--------------------------------------------------------------------------- +# configuration options for the AutoGen Definitions output +#--------------------------------------------------------------------------- + +# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will +# generate an AutoGen Definitions (see autogen.sf.net) file +# that captures the structure of the code including all +# documentation. Note that this feature is still experimental +# and incomplete at the moment. + +GENERATE_AUTOGEN_DEF = NO + +#--------------------------------------------------------------------------- +# configuration options related to the Perl module output +#--------------------------------------------------------------------------- + +# If the GENERATE_PERLMOD tag is set to YES Doxygen will +# generate a Perl module file that captures the structure of +# the code including all documentation. Note that this +# feature is still experimental and incomplete at the +# moment. + +GENERATE_PERLMOD = NO + +# If the PERLMOD_LATEX tag is set to YES Doxygen will generate +# the necessary Makefile rules, Perl scripts and LaTeX code to be able +# to generate PDF and DVI output from the Perl module output. + +PERLMOD_LATEX = NO + +# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be +# nicely formatted so it can be parsed by a human reader. This is useful +# if you want to understand what is going on. On the other hand, if this +# tag is set to NO the size of the Perl module output will be much smaller +# and Perl will parse it just the same. + +PERLMOD_PRETTY = YES + +# The names of the make variables in the generated doxyrules.make file +# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. +# This is useful so different doxyrules.make files included by the same +# Makefile don't overwrite each other's variables. + +PERLMOD_MAKEVAR_PREFIX = + +#--------------------------------------------------------------------------- +# Configuration options related to the preprocessor +#--------------------------------------------------------------------------- + +# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will +# evaluate all C-preprocessor directives found in the sources and include +# files. + +ENABLE_PREPROCESSING = NO + +# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro +# names in the source code. If set to NO (the default) only conditional +# compilation will be performed. Macro expansion can be done in a controlled +# way by setting EXPAND_ONLY_PREDEF to YES. + +MACRO_EXPANSION = NO + +# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES +# then the macro expansion is limited to the macros specified with the +# PREDEFINED and EXPAND_AS_PREDEFINED tags. + +EXPAND_ONLY_PREDEF = NO + +# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files +# in the INCLUDE_PATH (see below) will be search if a #include is found. + +SEARCH_INCLUDES = YES + +# The INCLUDE_PATH tag can be used to specify one or more directories that +# contain include files that are not input files but should be processed by +# the preprocessor. + +INCLUDE_PATH = + +# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard +# patterns (like *.h and *.hpp) to filter out the header-files in the +# directories. If left blank, the patterns specified with FILE_PATTERNS will +# be used. + +INCLUDE_FILE_PATTERNS = + +# The PREDEFINED tag can be used to specify one or more macro names that +# are defined before the preprocessor is started (similar to the -D option of +# gcc). The argument of the tag is a list of macros of the form: name +# or name=definition (no spaces). If the definition and the = are +# omitted =1 is assumed. + +PREDEFINED = USING_XVMC_VLD USING_XVMCW USING_XVMC USING_XV USING_IVTV MMX USING_FIREWIRE USING_DVB USING_DVB_EIT USING_XRANDR USING_DIRECTX USING_DIRECTFB USING_OPENGL_VSYNC Q_OS_MACX + +# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then +# this tag can be used to specify a list of macro names that should be expanded. +# The macro definition that is found in the sources will be used. +# Use the PREDEFINED tag if you want to use a different macro definition. + +EXPAND_AS_DEFINED = + +# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then +# doxygen's preprocessor will remove all function-like macros that are alone +# on a line, have an all uppercase name, and do not end with a semicolon. Such +# function macros are typically used for boiler-plate code, and will confuse the +# parser if not removed. + +SKIP_FUNCTION_MACROS = YES + +#--------------------------------------------------------------------------- +# Configuration::additions related to external references +#--------------------------------------------------------------------------- + +# The TAGFILES option can be used to specify one or more tagfiles. +# Optionally an initial location of the external documentation +# can be added for each tagfile. The format of a tag file without +# this location is as follows: +# TAGFILES = file1 file2 ... +# Adding location for the tag files is done as follows: +# TAGFILES = file1=loc1 "file2 = loc2" ... +# where "loc1" and "loc2" can be relative or absolute paths or +# URLs. If a location is present for each tag, the installdox tool +# does not have to be run to correct the links. +# Note that each tag file must have a unique name +# (where the name does NOT include the path) +# If a tag file is not located in the directory in which doxygen +# is run, you must also specify the path to the tagfile here. + +TAGFILES = + +# When a file name is specified after GENERATE_TAGFILE, doxygen will create +# a tag file that is based on the input files it reads. + +GENERATE_TAGFILE = + +# If the ALLEXTERNALS tag is set to YES all external classes will be listed +# in the class index. If set to NO only the inherited external classes +# will be listed. + +ALLEXTERNALS = NO + +# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed +# in the modules index. If set to NO, only the current project's groups will +# be listed. + +EXTERNAL_GROUPS = YES + +# The PERL_PATH should be the absolute path and name of the perl script +# interpreter (i.e. the result of `which perl'). + +PERL_PATH = /usr/bin/perl + +#--------------------------------------------------------------------------- +# Configuration options related to the dot tool +#--------------------------------------------------------------------------- + +# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will +# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or +# super classes. Setting the tag to NO turns the diagrams off. Note that this +# option is superseded by the HAVE_DOT option below. This is only a fallback. It is +# recommended to install and use dot, since it yields more powerful graphs. + +CLASS_DIAGRAMS = YES + +# If set to YES, the inheritance and collaboration graphs will hide +# inheritance and usage relations if the target is undocumented +# or is not a class. + +HIDE_UNDOC_RELATIONS = YES + +# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is +# available from the path. This tool is part of Graphviz, a graph visualization +# toolkit from AT&T and Lucent Bell Labs. The other options in this section +# have no effect if this option is set to NO (the default) + +HAVE_DOT = NO + +# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for each documented class showing the direct and +# indirect inheritance relations. Setting this tag to YES will force the +# the CLASS_DIAGRAMS tag to NO. + +CLASS_GRAPH = YES + +# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen +# will generate a graph for each documented class showing the direct and +# indirect implementation dependencies (inheritance, containment, and +# class references variables) of the class with other documented classes. + +COLLABORATION_GRAPH = YES + +# If the UML_LOOK tag is set to YES doxygen will generate inheritance and +# collaboration diagrams in a style similar to the OMG's Unified Modeling +# Language. + +UML_LOOK = NO + +# If set to YES, the inheritance and collaboration graphs will show the +# relations between templates and their instances. + +TEMPLATE_RELATIONS = NO + +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT +# tags are set to YES then doxygen will generate a graph for each documented +# file showing the direct and indirect include dependencies of the file with +# other documented files. + +INCLUDE_GRAPH = YES + +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and +# HAVE_DOT tags are set to YES then doxygen will generate a graph for each +# documented header file showing the documented files that directly or +# indirectly include this file. + +INCLUDED_BY_GRAPH = YES + +# If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will +# generate a call dependency graph for every global function or class method. +# Note that enabling this option will significantly increase the time of a run. +# So in most cases it will be better to enable call graphs for selected +# functions only using the \callgraph command. + +CALL_GRAPH = NO + +# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen +# will graphical hierarchy of all classes instead of a textual one. + +GRAPHICAL_HIERARCHY = YES + +# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images +# generated by dot. Possible values are png, jpg, or gif +# If left blank png will be used. + +DOT_IMAGE_FORMAT = png + +# The tag DOT_PATH can be used to specify the path where the dot tool can be +# found. If left blank, it is assumed the dot tool can be found on the path. + +DOT_PATH = + +# The DOTFILE_DIRS tag can be used to specify one or more directories that +# contain dot files that are included in the documentation (see the +# \dotfile command). + +DOTFILE_DIRS = + +# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width +# (in pixels) of the graphs generated by dot. If a graph becomes larger than +# this value, doxygen will try to truncate the graph, so that it fits within +# the specified constraint. Beware that most browsers cannot cope with very +# large images. + +MAX_DOT_GRAPH_WIDTH = 1024 + +# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height +# (in pixels) of the graphs generated by dot. If a graph becomes larger than +# this value, doxygen will try to truncate the graph, so that it fits within +# the specified constraint. Beware that most browsers cannot cope with very +# large images. + +MAX_DOT_GRAPH_HEIGHT = 1024 + +# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the +# graphs generated by dot. A depth value of 3 means that only nodes reachable +# from the root by following a path via at most 3 edges will be shown. Nodes that +# lay further from the root node will be omitted. Note that setting this option to +# 1 or 2 may greatly reduce the computation time needed for large code bases. Also +# note that a graph may be further truncated if the graph's image dimensions are +# not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT). +# If 0 is used for the depth value (the default), the graph is not depth-constrained. + +MAX_DOT_GRAPH_DEPTH = 0 + +# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will +# generate a legend page explaining the meaning of the various boxes and +# arrows in the dot generated graphs. + +GENERATE_LEGEND = YES + +# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will +# remove the intermediate dot files that are used to generate +# the various graphs. + +DOT_CLEANUP = YES + +#--------------------------------------------------------------------------- +# Configuration::additions related to the search engine +#--------------------------------------------------------------------------- + +# The SEARCHENGINE tag specifies whether or not a search engine should be +# used. If set to NO the values of all tags below this one will be ignored. + +SEARCHENGINE = YES diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/doxygen.perl.patch b/abs/core-testing/local-website/htdocs/mythtv-doc/doxygen.perl.patch new file mode 100644 index 0000000..c7288b6 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/doxygen.perl.patch @@ -0,0 +1,141 @@ +diff -ru doxygen-1.5.4.orig/src/scanner.l doxygen-1.5.4/src/scanner.l +--- doxygen-1.5.4.orig/src/scanner.l 2007-10-26 21:52:35.000000000 +1000 ++++ doxygen-1.5.4/src/scanner.l 2008-01-09 13:19:14.000000000 +1100 +@@ -115,6 +115,7 @@ + static bool insideObjC = FALSE; //!< processing Objective C code? + static bool insideCli = FALSE; //!< processing C++/CLI code? + static bool insideJS = FALSE; //!< processing JavaScript code? ++static bool insidePerl = FALSE; //!< processing Perl code? + + static bool insideCppQuote = FALSE; + static bool insideProtocolList = FALSE; +@@ -332,13 +333,15 @@ + insidePHP = langExt==SrcLangExt_PHP; + insideObjC = langExt==SrcLangExt_ObjC; + insideJS = langExt==SrcLangExt_JS; ++ insidePerl = langExt==SrcLangExt_Perl; + if ( insidePHP ) + { + useOverrideCommands = TRUE; + } + //printf("setContext(%s) insideIDL=%d insideJava=%d insideCS=%d " +- // "insideD=%d insidePHP=%d insideObjC=%d\n", +- // yyFileName.data(),insideIDL,insideJava,insideCS,insideD,insidePHP,insideObjC ++ // "insideD=%d insidePHP=%d insideObjC=%d insidePerl=%d\n", ++ // yyFileName.data(),insideIDL,insideJava,insideCS,insideD, ++ // insidePHP,insideObjC,insidePerl + // ); + } + +@@ -591,6 +594,7 @@ + %x Define + %x DefineEnd + %x CompoundName ++%x PerlSubName + %x ClassVar + %x CSConstraintName + %x CSConstraintType +@@ -604,6 +608,7 @@ + %x BitFields + %x FindMembers + %x FindMembersPHP ++%x FindMembersPerl + %x FindMemberName + %x FindFields + %x FindFieldArg +@@ -920,6 +925,29 @@ + REJECT; + } + } ++<FindMembersPerl>{B}*"sub"{B}+ { ++ BEGIN( PerlSubName ); ++ } ++<PerlSubName>{LABELID} { ++ //printf("### Perl SUB name = %s\n", yytext); ++ isTypedef=FALSE; ++ current->name = yytext; ++ current->section ++ = Entry::FUNCTION_SEC; ++ current->type = "sub" ; ++ current->fileName = yyFileName; ++ current->startLine = yyLineNr; ++ current->bodyLine = yyLineNr; ++ lineCount(); ++ curlyCount = 0; ++ current_root->addSubEntry(current); ++ //current_root = current ; ++ current = new Entry ; ++ initEntry(); ++ lastCurlyContext = FindMembersPerl; ++ BEGIN( SkipCurly ); ++ BEGIN( FindMembersPerl ); ++ } + <CliPropertyType>{ID} { + addType( current ); + current->name = yytext; +@@ -3431,6 +3459,13 @@ + BEGIN( CopyArgComment ); + } + } ++ /* Same in Perl or Sh */ ++<FindMembersPerl>"###" { ++ fullArgString+=yytext; ++ lastCopyArgChar=0; ++ lastCommentInArgContext=YY_START; ++ BEGIN( CopyArgCommentLine ); ++ } + /* a non-special comment */ + <ReadFuncArgType,ReadTempArgs>"/*" { + lastCContext = YY_START; +@@ -5434,6 +5469,10 @@ + { + BEGIN( FindMembersPHP ); + } ++ else if ( insidePerl ) ++ { ++ BEGIN( FindMembersPerl ); ++ } + else + { + BEGIN( FindMembers ); +diff -ru doxygen-1.5.4.orig/src/util.cpp doxygen-1.5.4/src/util.cpp +--- doxygen-1.5.4.orig/src/util.cpp 2007-10-26 21:33:49.000000000 +1000 ++++ doxygen-1.5.4/src/util.cpp 2008-01-09 09:27:43.000000000 +1100 +@@ -6158,6 +6158,9 @@ + extLookup.insert(".m", new int(SrcLangExt_ObjC)); + extLookup.insert(".M", new int(SrcLangExt_ObjC)); + extLookup.insert(".mm", new int(SrcLangExt_ObjC)); ++ extLookup.insert(".pl", new int(SrcLangExt_Perl)); ++ extLookup.insert(".pm", new int(SrcLangExt_Perl)); ++ extLookup.insert(".sh", new int(SrcLangExt_Shell)); + init=TRUE; + } + if (i!=-1) // name has an extension +diff -ru doxygen-1.5.4.orig/src/util.h doxygen-1.5.4/src/util.h +--- doxygen-1.5.4.orig/src/util.h 2007-08-12 05:45:51.000000000 +1000 ++++ doxygen-1.5.4/src/util.h 2008-01-09 09:28:43.000000000 +1100 +@@ -85,14 +85,16 @@ + + enum SrcLangExt + { +- SrcLangExt_IDL = 0x008, +- SrcLangExt_Java = 0x010, +- SrcLangExt_CSharp = 0x020, +- SrcLangExt_D = 0x040, +- SrcLangExt_PHP = 0x080, +- SrcLangExt_ObjC = 0x100, +- SrcLangExt_Cpp = 0x200, +- SrcLangExt_JS = 0x400, ++ SrcLangExt_IDL = 0x0008, ++ SrcLangExt_Java = 0x0010, ++ SrcLangExt_CSharp = 0x0020, ++ SrcLangExt_D = 0x0040, ++ SrcLangExt_PHP = 0x0080, ++ SrcLangExt_ObjC = 0x0100, ++ SrcLangExt_Cpp = 0x0200, ++ SrcLangExt_JS = 0x0400, ++ SrcLangExt_Perl = 0x0800, ++ SrcLangExt_Shell = 0x1000, + }; + + //-------------------------------------------------------------------- diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/i18n/.svn/all-wcprops b/abs/core-testing/local-website/htdocs/mythtv-doc/i18n/.svn/all-wcprops new file mode 100644 index 0000000..e7b0699 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/i18n/.svn/all-wcprops @@ -0,0 +1,11 @@ +K 25 +svn:wc:ra_dav:version-url +V 64 +/svn/!svn/ver/15931/branches/release-0-21-fixes/mythtv/docs/i18n +END +keys_de.txt +K 25 +svn:wc:ra_dav:version-url +V 76 +/svn/!svn/ver/15931/branches/release-0-21-fixes/mythtv/docs/i18n/keys_de.txt +END diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/i18n/.svn/entries b/abs/core-testing/local-website/htdocs/mythtv-doc/i18n/.svn/entries new file mode 100644 index 0000000..4deb045 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/i18n/.svn/entries @@ -0,0 +1,40 @@ +8 + +dir +17449 +http://svn.mythtv.org/svn/branches/release-0-21-fixes/mythtv/docs/i18n +http://svn.mythtv.org/svn + + + +2005-06-22T17:08:33.437073Z +6689 +rkulagow + + +svn:special svn:externals svn:needs-lock + + + + + + + + + + + +7dbf422c-18fa-0310-86e9-fd20926502f2 + +keys_de.txt +file + + + + +2008-02-17T05:32:05.000000Z +c1a687298b5a96e93dd9daed3ee6f452 +2005-06-22T17:08:33.437073Z +6689 +rkulagow + diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/i18n/.svn/format b/abs/core-testing/local-website/htdocs/mythtv-doc/i18n/.svn/format new file mode 100644 index 0000000..45a4fb7 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/i18n/.svn/format @@ -0,0 +1 @@ +8 diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/i18n/.svn/text-base/keys_de.txt.svn-base b/abs/core-testing/local-website/htdocs/mythtv-doc/i18n/.svn/text-base/keys_de.txt.svn-base new file mode 100644 index 0000000..3e7346c --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/i18n/.svn/text-base/keys_de.txt.svn-base @@ -0,0 +1,298 @@ +Translation provided by Michael Haas (hansi.urpils at gmail.com) 2005-06-22 + +Verschiedene Tasten und ihre Funktionen: + +mythfrontend +------------ + +- Pfeiltasten werden benutzt, um einen Menuepunkt auszuwaehlen. +- ALT-F4 beendet die Anwendung. +- Leertaste oder Enter, um den gewählten Menupünkt zu aktiveren. +- P zum Abspielen, sowohl in "Aufnahmen ansehen" als auch in "Loeschen". +- D zum Loeschen, sowohl in "Aufnahmen ansehen" als auch in "Loeschen". +- U fuer eine Detailansicht der momentan ausgewaehlten Sendung in "Aufnahmen + ansehen", "Loeschen", "EPG", "Suche" und "FIXME" sowie in den Suchergebnissen. +- O für eine Liste der anstehenden Folgen der momentan ausgewählten Sendung in + "EPG", "Suche", "Sendung Aufnahmeprioritaeten" und "FIXME" sowie in den + Suchergebnissen. +- I zum Bearbeiten der Aufnahmeoptionen in "EPG", "Suche", + "Sendung Aufnahmeprioritäten" und FIXME. In den Bildschirmen + "Aufnahmen ansehen" und "Loeschen" zeigt 'I' Optionen für aufgenommene + Sendungen wie "Automatisch löschen" oder "Aufnahme stoppen". + +Aufnahmen oder Fernsehen schauen +-------------------------------- + +- Pfeiltasten hoch und runter, um den Kanal zu wechseln +- Eine Nummer eintippen, um zu einem bestimmten Kanal oder um um eine bestimmte + Zeitspanne zu springen (HHMM-Format) +- P für Pause/Abspielen + - Es ist ebenfalls möglich, eine bestimmte Taste fuer "Abspielen" + ueber die Konfiguration der Tastenbelegung in MythWeb festzulegen, + um von Zeitlupenmodus, Zurückspulen, Vorspulen oder Pause wieder auf + normale Geschwindigkeit zu wechseln. + - C zum Wechseln des Eingangs auf der TV-Karte + - ESC zum Abbrechen + - I ruft das On-Screen-Display auf. + - Während der Wiedergabe wechselt 'I' zwischen Informationen zur aktuellen + Position und der Beschreibung der Sendung hin und her. Wenn eine Zeit + (HHMM) angegeben wird, springt MythTV um diese Zeit. + - M ruft das EPG auf. siehe Abschnitt zu EPG. + - Bild Runter springt um die vorkonfigurierte Zeitspanne zurueck. Standardwert ist 10 Minuten. + - Bild Hoch springt um die vorkonfigurierte Zeitspanne vor. Standardwert ist + 10 Minuten. + - Ende oder 'Z', um zur nächsten Werbungsmarkierung zu springen. + - Position 1 oder 'Q', um zur vorherigen Werbungsmarkierung zu springen. + - T zum Ein-/Ausschalten der Untertitel. + - F rotiert zwischen den verschiedenen Bildeinstellungen (Farbe, Farbton etc.) + Waehrend dieser Bildschirm zu sehen ist, benutzt man die linke bzw + rechte Pfeiltaste, um Einstellungen vorzunehmen. Diese Einstellungen + beeinflussen das Aussehen der Videowiedergabe und sind unabhaengig von + den Einstellungen, die mit der Taste 'G' gemacht werden koennen (siehe + unten) die bei der Aufnahme benutzt werden. + - [ oder F10 verringert die Lautstaerke + - ] oder F11 erhoeht die Lautstaerke + - / springt zum nächsten "bevorzugten Sender". + - ? kennzeichnet den aktuellen Kanal als "bevorzugten Sender" + - U erhöht die Abspielgeschwindigkeit + - J verringert die Abspielgeschwindigkeit + - A passt den Zeitraffer an (Beschleunigung oder Verlangsamung FIXME) + - W veraendert das Seitenverhaeltnis. Zur Auswahl stehen: 4:3, 16:9, + 4:3 Zoom (wie "Pan and Scan" FIXME), 16:9 Zoom und 16:9 "Stretch" FIXME + (beseitigt schwarze Raender im TV-Signal) + - Links (falls eine Sprungzeit angegeben wurde), um diese Zeitspanne + zurueckspringen + - Rechts (falls eine Sprungzeit angegeben wurde), um diese Zeitspanne + vorzuspringen + - F8 wechselt zwischen den Einstellungen des "sleep timer" FIXME: + 30min->1h->1h30min->2h->Aus. + +"Klebrige" Tasten ("sticky keys") ausgeschaltet: + + - Linke Pfeiltaste spult um die konfigurierte Zeitspanne (Standard: 5s) + zurueck. + - Rechte Pfeiltaste spult um die konfigurierte Zeitspanne (Standard: 30s) + vor. + - < startet den Rueckspulmodus (wie wenn "klebrige Tasten" aktiviert waere) + - > startet den Vorspulmodus (wie wenn "klebrige Tasten" aktiviert waere) + + "Klebrige" Tasten ("sticky keys") eingeschaltet: + + - Rechte Pfeiltaste startet den Vorspulmodus + - Linke Pfeiltaste startet den Rueckspulmodus + Waehrend dem Spulen: + - Linke/Rechte Pfeiltaste erhoeht die Vor-/Rueckspulgeschwindigkeit + - 0 spielt mit Normalgeschnwindigkeit, laesst allerdings den Zeitanzeiger + auf dem Bildschirm + - 1 oder 2, um langsamer als normales Vor-/Zurueckspulen zu spulen + (1 ist am langsamsten) + - 3 fuer normale Vor-/Rueckspulgeschwindigkeit + - 4 - 9 spult schneller als normales Vor-/Zurueckspulen + (9 ist am schnellsten) + - Leertaste, um den Spulmodus zu verlassen + +Nur Fernsehen: + + - G rotiert zwischen den verschiedenen Bildeinstellungen (Farbe, Farbton etc.) + fuer Aufnahmen. Diese Werte beeinflussen das Aussehen der resultierenden + .nuv-Datei. Waehrend dieser Bildschirm zu sehen ist, + benutzt man die linke bzw rechte Pfeiltaste, um Einstellungen vorzunehmen. + - H Senderverlauf. Jeder Druck auf diese Taste schaltet auf den jeweils + vorher geschauten Sender um. + - O schaltet den Browse-Modus an und erlaubt es so dem Benutzer, in den + Kanaelen und deren Programminformation zu stoebern waehrend er die + aktuelle Sendung in voller groesse schaut. + - Y wechselt zwischen den TV-Karten. + +Browse-Modus waehrend LiveTV + + - Linke Pfeiltaste blaettert im Programm vor dem aktuell angezeigten. + - Rechte Pfeiltaste blaettert im Programm nach dem aktuell angezeigten. + - Pfeiltaste Hoch blaettert im Programm des Kanals ueber dem aktuell + angezeigten. + - Pfeiltaste Runter blaettert im Programm des Kanals unter dem aktuell + angezeigten. + - / blattert durch das Programm des naechsten "bevorzugten Senders". + - 0-9 ermoeglicht es, eine Kanalnummer einzugeben und deren Programm + einzusehen. + - Leertaste/Enter wechselt den Kanal zu dem aktuell angezeigten. + - R/r nimmt die angezeigte Sendung auf (wechselt durch die Typen) + - ESC/O beendet den Browse-Modus + +Zoom-Modus während der Wiedergabe einer Aufnahme + - Linke Pfeiltaste bewegt das Video nach links + - Rechte Pfeiltaste bewegt das Video nach rechts + - Pfeiltaste Hoch bewegt das Video nach oben + - Pfeiltaste Runter bewegt das Video nach unten + - Bild Hoch zoomt rein + - Bild Runter zoomt raus + - Leertaste/Enter beendet den Zoom-Modus und laesst das Bild bei der momentanen + Groesse und Position + - ESC beendet den Zoom-Modus und kehrt zur Ausgangsgroesse zurück. + +Wenn man zwei oder mehr TV-Karten hat: + + - V schaltet Bild-in-Bild ein oder aus + - B holt die verschiedenen Fenster nacheinander in den Fokus + (erlaubt den Kanalwechsel im Bild-in-Bild-Fenster + - N vertauscht die Beiden Sender, indem die Kanäle auf beiden Karten gewechselt + werden + +Waehrend man eine Aufnahme ansieht: + - Leertaste oder Enter setzt ein Lesezeichen an dem Punkt. Wenn die Aufnahme + das nächste mal angeschaut wird, springt MythTV automatisch zu diesem + Punkt und loescht das Lesezeichen. + - E oder M startet/beendet den "Aufnahme bearbeiten"-Modus. + - Die linke und rechte Pfeiltaste bewegen den Cursor rueckwaerts und + vorwaerts + - Die Pfeiltasten Hoch und Runter veraendern die Zeitspanne, um die man + vorwaerts oder rueckwaerts springt. Verfügbare Schritte: naechster + Schnittpunkt, naechster Video-Keyframe, 1 frame, 0,5 Sekunden, + 1 Sekunde, 20 Sekunden, 1 Minute, 5 Minuten und 10 Minuten. + - Bild Hoch und Bild Runter wechseln zum naechsten Schnittpunkt + - < und > springen um das 10-fache der gesetzten Zeitspanne + nach vorne. + - 'Z' laedt die Liste mit den erkannten Werbespots in die Schnittliste, + falls eine existiert. + - 'C' oder 'Q' löschen alle Schnittpunkte in der Schnittliste. + - 'I' kehrt die Schnittliste um. + - X reiht die Aufnahme in die Warteschlange zur Umwandlung ein. + - O ruft das Menue zur Einstellung von "Automatisch loeschen", + "Werbung ueberspringen", etc auf. + - D beendet die gerade laufende Wiedergabe und zeigt das "Löschen"-Menue an. + +EPG +--- + +- Pfeiltasten werden benutzt, um einen Menuepunkt auszuwaehlen. +- A, D, S und W tun das selbe wie die Pfeiltasten. +- Bild Hoch/Bild Runter bewegen die Kanalliste eine Seite hoch oder runter. +- Position 1 oder Ende bewegen die Auswahl um einen Tag nach links oder rechts. +- 9, 3, 7 und 1 (wie auf dem Nummernblock) tun das gleiche wie Bild Hoch, + Bild Runter, Position 1 und Ende. +- I zeigt mehr Informationen ueber eine Sendung an und erlaubt es, eine + Aufnahme zu programmieren. + - Wenn man "Diese Sendung aufnehmen" auswaehlt waehrend man LiveTV schaut, + kann man eine Sendung direkt aufnehmen. +- Leertaste oder Enter, um Konflikte aufzuloesen oder um Sonderoptionen + zu veraendern. Wenn die Sendung nicht bereits zur Aufnahme bestimmt ist, + verhaelt sich MythTV als waere stattdessen 'I' gedrueckt worden. +- M, um auf den ausgewaehlten Kanal zu wechseln. +- ESC oder C, um den EPG zu verlassen, ohne den Kanal zu wechseln. +- R wechselt zwischen Aufnehmen/nicht Aufnehmen. Fortlaufendes Betätigen + wechselt zwischen den Aufnahmemodi. +- X wechselt den Kanal zu dem momentan ausgewaehlten, ohne den EPG zu verlassen. +- ? kennzeichnet den aktuellen Kanal als "bevorzugten Sender" +- / oder 4 zeigt alternativ nur die "bevorzugten Sender" an, bzw. schaltet + wieder zurueck zur normalen Ansicht. + +Setzen der "Sendung Aufnahmeprioritäten" und der "Sender Aufnahmeprioritäten" +---------------------------------------------------------------------------- + +- Die Rechte Pfeiltaste erhöht den Prioritaetswert +- Die Linke Pfeiltaste verringert den Prioritaetswert +- 1 sortiert nach dem Titel +- 2 sortiert nach der Priorität +- Position 1/Ende schaltet zwischen der Sortierung nach Prioritaet hin und her +- I, um die Aufnahmeoptionen zu editieren +- ESC speichert die Änderungen und verlässt den Bildschirm + +Ansehen der geplanten Aufnahmen/Konflikte lösen +------------------------------------------------ + +- 1 zeigt alle Aufnahmen an +- 2 zeigt nur wichtige Aufnahmen +- Position1/Ende wechselt zwischen der Ansicht von wichtigen und normalen + Aufnahmen. +- I, um die Aufnahmeoptionen zu editieren +- Leertaste oder Enter, um Konflikte zu lösen/außer Kraft zu setzen + +Ansehen der Suchlisten: +----------------------- + +- Position 1 wechselt zur vorherigen Ansicht, wenn anwendbar +- Ende wechselt zur naechsten Ansicht, wenn verfügbar +- M wechselt zu einer anderen Ansicht, wenn moeglich + - In dem Suchbildschirm für Titel und Beschreibung, druecke M noch einmal um + die ausgewählte Ansicht zu editieren oder zu löschen + +Einstellungsbildschirm der Aufnahmeprofile: +------------------------------------------ +- D ruft einen Bildschirm zum Löschen einer eigenen Profilgruppe auf. + +Aufnahmegruppen: +--------------- + +Aufnahmegruppen erlauben es, Programme in benutzerdefinierte Kategorien zu +unterteilen, wie beispielsweise "Kinder", "Alice", "Karl-Heinz" etc. +Diese Funktion kann benutzt werden, um Durcheinanger zu reduzieren oder um +Inhalt (Sendungen etc) abzusondern, wenn man die PIN-Funktion nutzt. + +Im "Aufnahmen ansehen"-Bildschirm: +- M wechselt die Ansicht oder setzt ein Passwort für die Gruppe +- I verschiebt eine Sendung von einer Gruppe in eine andere + +"Aufnahmen ansehen"-Bildschirm: +------------------------------- + +- "1" oder F1 zeigt einen Bildschirm mit der Bedeutung der Icons +- / markiert eine Aufnahme. Markierte Aufnahmen koennen als Gruppe + abgespielt (in Reihenfolge oder zufaellig) und geloescht werden. + Man kann ebenfalls die Aufnahmegruppe für einige Aufnahmen aendern, + indem man sie markiert und dann mit dem INFO-Menue die Aufnahmegruppe + aendert. +- ? leert die Liste der markierten Aufnahmen + +Fernbedienungen +--------------- + +Wenn man MythTV nur mit einer Fernbedienung benutzt, ist es empfohlen, dass man +die Tasten auf der Fernbedienung wie unten beschrieben belegt. +Es ist moeglich, dass die Fernbedienung nicht den gleichen Satz an Tasten +wie die unten genannten hat, die Namen sind nur Vorschlaege, die ungefaehr +der Funktion entsprechen. + +Wenn man neue Tastaturbelegungen zu dem Programm hinzufügt, wird es Benutzern +von Fernbedienungen helfen, wenn die vorgeschlagene Liste berücksichtigt wird. + +Diese Liste nimmt eine minimale Fernbedienung an, die nur 20 Tasten hat. +Nahezu alle Faehigkeiten koennen mit dieser Konfiguration genutzt werden. +Wenn man mehr Tasten hart, kann man alle Faehigkeiten ausnutzen. +Mit nru 16 Tasten sind die meisten Fähigkeiten verfügbar. + + +Fernbedienung LIRC-Tastendruck Funktion +------------- ---------------- -------- + +0 - 9 0 - 9 Kanalauswahl, Navigation im + EPG, + Rück-/Vorspulgeschwindigkeit + (mit "klebigen Tasten") + +Linke Pfeiltaste Left nach links scrollen, + zurueckspulen + +Rechte Pfeiltaste Right nach rechts scrollen, + vorspulen + +Pfeiltaste hoch Up hoch scrollen, Kanalwechsel + nach oben + +Pfeiltaste runter Down runter scrollen, Kanalwechsel + nach unten + +Auswahl/OK/Abspielen Space Menuepunkt auswaehlen, Abspielen + (mit "klebrigen Tasten"), + Lesezeichen setzen + +Abbrechen Escape Abbrechen, Wiedergabe beenden + +Menue m EPG (in LiveTV) + Editieren (bei Aufnahmen) + +Pause p Pause + +Andere Taste 1 i Information + +Andere Taste 2 c Wechselt den Eingang der + TV-Karte diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/i18n/keys_de.txt b/abs/core-testing/local-website/htdocs/mythtv-doc/i18n/keys_de.txt new file mode 100644 index 0000000..3e7346c --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/i18n/keys_de.txt @@ -0,0 +1,298 @@ +Translation provided by Michael Haas (hansi.urpils at gmail.com) 2005-06-22 + +Verschiedene Tasten und ihre Funktionen: + +mythfrontend +------------ + +- Pfeiltasten werden benutzt, um einen Menuepunkt auszuwaehlen. +- ALT-F4 beendet die Anwendung. +- Leertaste oder Enter, um den gewählten Menupünkt zu aktiveren. +- P zum Abspielen, sowohl in "Aufnahmen ansehen" als auch in "Loeschen". +- D zum Loeschen, sowohl in "Aufnahmen ansehen" als auch in "Loeschen". +- U fuer eine Detailansicht der momentan ausgewaehlten Sendung in "Aufnahmen + ansehen", "Loeschen", "EPG", "Suche" und "FIXME" sowie in den Suchergebnissen. +- O für eine Liste der anstehenden Folgen der momentan ausgewählten Sendung in + "EPG", "Suche", "Sendung Aufnahmeprioritaeten" und "FIXME" sowie in den + Suchergebnissen. +- I zum Bearbeiten der Aufnahmeoptionen in "EPG", "Suche", + "Sendung Aufnahmeprioritäten" und FIXME. In den Bildschirmen + "Aufnahmen ansehen" und "Loeschen" zeigt 'I' Optionen für aufgenommene + Sendungen wie "Automatisch löschen" oder "Aufnahme stoppen". + +Aufnahmen oder Fernsehen schauen +-------------------------------- + +- Pfeiltasten hoch und runter, um den Kanal zu wechseln +- Eine Nummer eintippen, um zu einem bestimmten Kanal oder um um eine bestimmte + Zeitspanne zu springen (HHMM-Format) +- P für Pause/Abspielen + - Es ist ebenfalls möglich, eine bestimmte Taste fuer "Abspielen" + ueber die Konfiguration der Tastenbelegung in MythWeb festzulegen, + um von Zeitlupenmodus, Zurückspulen, Vorspulen oder Pause wieder auf + normale Geschwindigkeit zu wechseln. + - C zum Wechseln des Eingangs auf der TV-Karte + - ESC zum Abbrechen + - I ruft das On-Screen-Display auf. + - Während der Wiedergabe wechselt 'I' zwischen Informationen zur aktuellen + Position und der Beschreibung der Sendung hin und her. Wenn eine Zeit + (HHMM) angegeben wird, springt MythTV um diese Zeit. + - M ruft das EPG auf. siehe Abschnitt zu EPG. + - Bild Runter springt um die vorkonfigurierte Zeitspanne zurueck. Standardwert ist 10 Minuten. + - Bild Hoch springt um die vorkonfigurierte Zeitspanne vor. Standardwert ist + 10 Minuten. + - Ende oder 'Z', um zur nächsten Werbungsmarkierung zu springen. + - Position 1 oder 'Q', um zur vorherigen Werbungsmarkierung zu springen. + - T zum Ein-/Ausschalten der Untertitel. + - F rotiert zwischen den verschiedenen Bildeinstellungen (Farbe, Farbton etc.) + Waehrend dieser Bildschirm zu sehen ist, benutzt man die linke bzw + rechte Pfeiltaste, um Einstellungen vorzunehmen. Diese Einstellungen + beeinflussen das Aussehen der Videowiedergabe und sind unabhaengig von + den Einstellungen, die mit der Taste 'G' gemacht werden koennen (siehe + unten) die bei der Aufnahme benutzt werden. + - [ oder F10 verringert die Lautstaerke + - ] oder F11 erhoeht die Lautstaerke + - / springt zum nächsten "bevorzugten Sender". + - ? kennzeichnet den aktuellen Kanal als "bevorzugten Sender" + - U erhöht die Abspielgeschwindigkeit + - J verringert die Abspielgeschwindigkeit + - A passt den Zeitraffer an (Beschleunigung oder Verlangsamung FIXME) + - W veraendert das Seitenverhaeltnis. Zur Auswahl stehen: 4:3, 16:9, + 4:3 Zoom (wie "Pan and Scan" FIXME), 16:9 Zoom und 16:9 "Stretch" FIXME + (beseitigt schwarze Raender im TV-Signal) + - Links (falls eine Sprungzeit angegeben wurde), um diese Zeitspanne + zurueckspringen + - Rechts (falls eine Sprungzeit angegeben wurde), um diese Zeitspanne + vorzuspringen + - F8 wechselt zwischen den Einstellungen des "sleep timer" FIXME: + 30min->1h->1h30min->2h->Aus. + +"Klebrige" Tasten ("sticky keys") ausgeschaltet: + + - Linke Pfeiltaste spult um die konfigurierte Zeitspanne (Standard: 5s) + zurueck. + - Rechte Pfeiltaste spult um die konfigurierte Zeitspanne (Standard: 30s) + vor. + - < startet den Rueckspulmodus (wie wenn "klebrige Tasten" aktiviert waere) + - > startet den Vorspulmodus (wie wenn "klebrige Tasten" aktiviert waere) + + "Klebrige" Tasten ("sticky keys") eingeschaltet: + + - Rechte Pfeiltaste startet den Vorspulmodus + - Linke Pfeiltaste startet den Rueckspulmodus + Waehrend dem Spulen: + - Linke/Rechte Pfeiltaste erhoeht die Vor-/Rueckspulgeschwindigkeit + - 0 spielt mit Normalgeschnwindigkeit, laesst allerdings den Zeitanzeiger + auf dem Bildschirm + - 1 oder 2, um langsamer als normales Vor-/Zurueckspulen zu spulen + (1 ist am langsamsten) + - 3 fuer normale Vor-/Rueckspulgeschwindigkeit + - 4 - 9 spult schneller als normales Vor-/Zurueckspulen + (9 ist am schnellsten) + - Leertaste, um den Spulmodus zu verlassen + +Nur Fernsehen: + + - G rotiert zwischen den verschiedenen Bildeinstellungen (Farbe, Farbton etc.) + fuer Aufnahmen. Diese Werte beeinflussen das Aussehen der resultierenden + .nuv-Datei. Waehrend dieser Bildschirm zu sehen ist, + benutzt man die linke bzw rechte Pfeiltaste, um Einstellungen vorzunehmen. + - H Senderverlauf. Jeder Druck auf diese Taste schaltet auf den jeweils + vorher geschauten Sender um. + - O schaltet den Browse-Modus an und erlaubt es so dem Benutzer, in den + Kanaelen und deren Programminformation zu stoebern waehrend er die + aktuelle Sendung in voller groesse schaut. + - Y wechselt zwischen den TV-Karten. + +Browse-Modus waehrend LiveTV + + - Linke Pfeiltaste blaettert im Programm vor dem aktuell angezeigten. + - Rechte Pfeiltaste blaettert im Programm nach dem aktuell angezeigten. + - Pfeiltaste Hoch blaettert im Programm des Kanals ueber dem aktuell + angezeigten. + - Pfeiltaste Runter blaettert im Programm des Kanals unter dem aktuell + angezeigten. + - / blattert durch das Programm des naechsten "bevorzugten Senders". + - 0-9 ermoeglicht es, eine Kanalnummer einzugeben und deren Programm + einzusehen. + - Leertaste/Enter wechselt den Kanal zu dem aktuell angezeigten. + - R/r nimmt die angezeigte Sendung auf (wechselt durch die Typen) + - ESC/O beendet den Browse-Modus + +Zoom-Modus während der Wiedergabe einer Aufnahme + - Linke Pfeiltaste bewegt das Video nach links + - Rechte Pfeiltaste bewegt das Video nach rechts + - Pfeiltaste Hoch bewegt das Video nach oben + - Pfeiltaste Runter bewegt das Video nach unten + - Bild Hoch zoomt rein + - Bild Runter zoomt raus + - Leertaste/Enter beendet den Zoom-Modus und laesst das Bild bei der momentanen + Groesse und Position + - ESC beendet den Zoom-Modus und kehrt zur Ausgangsgroesse zurück. + +Wenn man zwei oder mehr TV-Karten hat: + + - V schaltet Bild-in-Bild ein oder aus + - B holt die verschiedenen Fenster nacheinander in den Fokus + (erlaubt den Kanalwechsel im Bild-in-Bild-Fenster + - N vertauscht die Beiden Sender, indem die Kanäle auf beiden Karten gewechselt + werden + +Waehrend man eine Aufnahme ansieht: + - Leertaste oder Enter setzt ein Lesezeichen an dem Punkt. Wenn die Aufnahme + das nächste mal angeschaut wird, springt MythTV automatisch zu diesem + Punkt und loescht das Lesezeichen. + - E oder M startet/beendet den "Aufnahme bearbeiten"-Modus. + - Die linke und rechte Pfeiltaste bewegen den Cursor rueckwaerts und + vorwaerts + - Die Pfeiltasten Hoch und Runter veraendern die Zeitspanne, um die man + vorwaerts oder rueckwaerts springt. Verfügbare Schritte: naechster + Schnittpunkt, naechster Video-Keyframe, 1 frame, 0,5 Sekunden, + 1 Sekunde, 20 Sekunden, 1 Minute, 5 Minuten und 10 Minuten. + - Bild Hoch und Bild Runter wechseln zum naechsten Schnittpunkt + - < und > springen um das 10-fache der gesetzten Zeitspanne + nach vorne. + - 'Z' laedt die Liste mit den erkannten Werbespots in die Schnittliste, + falls eine existiert. + - 'C' oder 'Q' löschen alle Schnittpunkte in der Schnittliste. + - 'I' kehrt die Schnittliste um. + - X reiht die Aufnahme in die Warteschlange zur Umwandlung ein. + - O ruft das Menue zur Einstellung von "Automatisch loeschen", + "Werbung ueberspringen", etc auf. + - D beendet die gerade laufende Wiedergabe und zeigt das "Löschen"-Menue an. + +EPG +--- + +- Pfeiltasten werden benutzt, um einen Menuepunkt auszuwaehlen. +- A, D, S und W tun das selbe wie die Pfeiltasten. +- Bild Hoch/Bild Runter bewegen die Kanalliste eine Seite hoch oder runter. +- Position 1 oder Ende bewegen die Auswahl um einen Tag nach links oder rechts. +- 9, 3, 7 und 1 (wie auf dem Nummernblock) tun das gleiche wie Bild Hoch, + Bild Runter, Position 1 und Ende. +- I zeigt mehr Informationen ueber eine Sendung an und erlaubt es, eine + Aufnahme zu programmieren. + - Wenn man "Diese Sendung aufnehmen" auswaehlt waehrend man LiveTV schaut, + kann man eine Sendung direkt aufnehmen. +- Leertaste oder Enter, um Konflikte aufzuloesen oder um Sonderoptionen + zu veraendern. Wenn die Sendung nicht bereits zur Aufnahme bestimmt ist, + verhaelt sich MythTV als waere stattdessen 'I' gedrueckt worden. +- M, um auf den ausgewaehlten Kanal zu wechseln. +- ESC oder C, um den EPG zu verlassen, ohne den Kanal zu wechseln. +- R wechselt zwischen Aufnehmen/nicht Aufnehmen. Fortlaufendes Betätigen + wechselt zwischen den Aufnahmemodi. +- X wechselt den Kanal zu dem momentan ausgewaehlten, ohne den EPG zu verlassen. +- ? kennzeichnet den aktuellen Kanal als "bevorzugten Sender" +- / oder 4 zeigt alternativ nur die "bevorzugten Sender" an, bzw. schaltet + wieder zurueck zur normalen Ansicht. + +Setzen der "Sendung Aufnahmeprioritäten" und der "Sender Aufnahmeprioritäten" +---------------------------------------------------------------------------- + +- Die Rechte Pfeiltaste erhöht den Prioritaetswert +- Die Linke Pfeiltaste verringert den Prioritaetswert +- 1 sortiert nach dem Titel +- 2 sortiert nach der Priorität +- Position 1/Ende schaltet zwischen der Sortierung nach Prioritaet hin und her +- I, um die Aufnahmeoptionen zu editieren +- ESC speichert die Änderungen und verlässt den Bildschirm + +Ansehen der geplanten Aufnahmen/Konflikte lösen +------------------------------------------------ + +- 1 zeigt alle Aufnahmen an +- 2 zeigt nur wichtige Aufnahmen +- Position1/Ende wechselt zwischen der Ansicht von wichtigen und normalen + Aufnahmen. +- I, um die Aufnahmeoptionen zu editieren +- Leertaste oder Enter, um Konflikte zu lösen/außer Kraft zu setzen + +Ansehen der Suchlisten: +----------------------- + +- Position 1 wechselt zur vorherigen Ansicht, wenn anwendbar +- Ende wechselt zur naechsten Ansicht, wenn verfügbar +- M wechselt zu einer anderen Ansicht, wenn moeglich + - In dem Suchbildschirm für Titel und Beschreibung, druecke M noch einmal um + die ausgewählte Ansicht zu editieren oder zu löschen + +Einstellungsbildschirm der Aufnahmeprofile: +------------------------------------------ +- D ruft einen Bildschirm zum Löschen einer eigenen Profilgruppe auf. + +Aufnahmegruppen: +--------------- + +Aufnahmegruppen erlauben es, Programme in benutzerdefinierte Kategorien zu +unterteilen, wie beispielsweise "Kinder", "Alice", "Karl-Heinz" etc. +Diese Funktion kann benutzt werden, um Durcheinanger zu reduzieren oder um +Inhalt (Sendungen etc) abzusondern, wenn man die PIN-Funktion nutzt. + +Im "Aufnahmen ansehen"-Bildschirm: +- M wechselt die Ansicht oder setzt ein Passwort für die Gruppe +- I verschiebt eine Sendung von einer Gruppe in eine andere + +"Aufnahmen ansehen"-Bildschirm: +------------------------------- + +- "1" oder F1 zeigt einen Bildschirm mit der Bedeutung der Icons +- / markiert eine Aufnahme. Markierte Aufnahmen koennen als Gruppe + abgespielt (in Reihenfolge oder zufaellig) und geloescht werden. + Man kann ebenfalls die Aufnahmegruppe für einige Aufnahmen aendern, + indem man sie markiert und dann mit dem INFO-Menue die Aufnahmegruppe + aendert. +- ? leert die Liste der markierten Aufnahmen + +Fernbedienungen +--------------- + +Wenn man MythTV nur mit einer Fernbedienung benutzt, ist es empfohlen, dass man +die Tasten auf der Fernbedienung wie unten beschrieben belegt. +Es ist moeglich, dass die Fernbedienung nicht den gleichen Satz an Tasten +wie die unten genannten hat, die Namen sind nur Vorschlaege, die ungefaehr +der Funktion entsprechen. + +Wenn man neue Tastaturbelegungen zu dem Programm hinzufügt, wird es Benutzern +von Fernbedienungen helfen, wenn die vorgeschlagene Liste berücksichtigt wird. + +Diese Liste nimmt eine minimale Fernbedienung an, die nur 20 Tasten hat. +Nahezu alle Faehigkeiten koennen mit dieser Konfiguration genutzt werden. +Wenn man mehr Tasten hart, kann man alle Faehigkeiten ausnutzen. +Mit nru 16 Tasten sind die meisten Fähigkeiten verfügbar. + + +Fernbedienung LIRC-Tastendruck Funktion +------------- ---------------- -------- + +0 - 9 0 - 9 Kanalauswahl, Navigation im + EPG, + Rück-/Vorspulgeschwindigkeit + (mit "klebigen Tasten") + +Linke Pfeiltaste Left nach links scrollen, + zurueckspulen + +Rechte Pfeiltaste Right nach rechts scrollen, + vorspulen + +Pfeiltaste hoch Up hoch scrollen, Kanalwechsel + nach oben + +Pfeiltaste runter Down runter scrollen, Kanalwechsel + nach unten + +Auswahl/OK/Abspielen Space Menuepunkt auswaehlen, Abspielen + (mit "klebrigen Tasten"), + Lesezeichen setzen + +Abbrechen Escape Abbrechen, Wiedergabe beenden + +Menue m EPG (in LiveTV) + Editieren (bei Aufnahmen) + +Pause p Pause + +Andere Taste 1 i Information + +Andere Taste 2 c Wechselt den Eingang der + TV-Karte diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/index.html b/abs/core-testing/local-website/htdocs/mythtv-doc/index.html new file mode 100644 index 0000000..6efe675 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/index.html @@ -0,0 +1,250 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV</TITLE> + <LINK HREF="mythtv-HOWTO-1.html" REL=next> + + +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-1.html">Next</A> +Previous +Contents +<HR> +<H1>Installing and using MythTV</H1> + +<H2>Robert Kulagowski, +<A HREF="mailto:rkulagow@rocketmail.com">mailto:rkulagow@rocketmail.com</A></H2>2008-06-04, v0.21.02 +<HR> +<EM>Initially, installation of MythTV seems like a huge task. There are lots +of dependencies, and various distributions seem to do the same thing +different ways. This document will attempt to give general installation +instructions, as well as including distribution-specific instructions where +necessary.</EM> +<HR> +<P> +<H2><A NAME="toc1">1.</A> <A HREF="mythtv-HOWTO-1.html">First things first.</A></H2> + +<UL> +<LI><A NAME="toc1.1">1.1</A> <A HREF="mythtv-HOWTO-1.html#ss1.1">What is MythTV?</A> +<LI><A NAME="toc1.2">1.2</A> <A HREF="mythtv-HOWTO-1.html#ss1.2">QuickStart</A> +<LI><A NAME="toc1.3">1.3</A> <A HREF="mythtv-HOWTO-1.html#ss1.3">Upgrading from previous versions</A> +<LI><A NAME="toc1.4">1.4</A> <A HREF="mythtv-HOWTO-1.html#ss1.4">How to obtain this document / PDF versions of this document </A> +<LI><A NAME="toc1.5">1.5</A> <A HREF="mythtv-HOWTO-1.html#ss1.5">Books about MythTV</A> +<LI><A NAME="toc1.6">1.6</A> <A HREF="mythtv-HOWTO-1.html#ss1.6">Document conventions</A> +<LI><A NAME="toc1.7">1.7</A> <A HREF="mythtv-HOWTO-1.html#ss1.7">Mailing lists / getting help</A> +<LI><A NAME="toc1.8">1.8</A> <A HREF="mythtv-HOWTO-1.html#ss1.8">IRC</A> +<LI><A NAME="toc1.9">1.9</A> <A HREF="mythtv-HOWTO-1.html#ss1.9">Bug database</A> +<LI><A NAME="toc1.10">1.10</A> <A HREF="mythtv-HOWTO-1.html#ss1.10">Contributing to this document</A> +</UL> +<P> +<H2><A NAME="toc2">2.</A> <A HREF="mythtv-HOWTO-2.html">Introduction.</A></H2> + +<P> +<H2><A NAME="toc3">3.</A> <A HREF="mythtv-HOWTO-3.html">Checking prerequisites. </A></H2> + +<UL> +<LI><A NAME="toc3.1">3.1</A> <A HREF="mythtv-HOWTO-3.html#ss3.1">Hardware</A> +<LI><A NAME="toc3.2">3.2</A> <A HREF="mythtv-HOWTO-3.html#ss3.2">Software</A> +</UL> +<P> +<H2><A NAME="toc4">4.</A> <A HREF="mythtv-HOWTO-4.html">System Configuration Requirements for Compiling MythTV. </A></H2> + +<UL> +<LI><A NAME="toc4.1">4.1</A> <A HREF="mythtv-HOWTO-4.html#ss4.1">Software requirements for compiling MythTV</A> +<LI><A NAME="toc4.2">4.2</A> <A HREF="mythtv-HOWTO-4.html#ss4.2">Shared-Library requirements for MythTV </A> +<LI><A NAME="toc4.3">4.3</A> <A HREF="mythtv-HOWTO-4.html#ss4.3">Environment variable requirements for MythTV</A> +</UL> +<P> +<H2><A NAME="toc5">5.</A> <A HREF="mythtv-HOWTO-5.html">Downloading and compiling. </A></H2> + +<UL> +<LI><A NAME="toc5.1">5.1</A> <A HREF="mythtv-HOWTO-5.html#ss5.1">Building LAME</A> +<LI><A NAME="toc5.2">5.2</A> <A HREF="mythtv-HOWTO-5.html#ss5.2">XMLTV</A> +<LI><A NAME="toc5.3">5.3</A> <A HREF="mythtv-HOWTO-5.html#ss5.3">Configuring the Schedules Direct service </A> +<LI><A NAME="toc5.4">5.4</A> <A HREF="mythtv-HOWTO-5.html#ss5.4">Manually building MythTV</A> +<LI><A NAME="toc5.5">5.5</A> <A HREF="mythtv-HOWTO-5.html#ss5.5">Gentoo </A> +</UL> +<P> +<H2><A NAME="toc6">6.</A> <A HREF="mythtv-HOWTO-6.html">MySQL.</A></H2> + +<UL> +<LI><A NAME="toc6.1">6.1</A> <A HREF="mythtv-HOWTO-6.html#ss6.1">Distribution-specific information</A> +<LI><A NAME="toc6.2">6.2</A> <A HREF="mythtv-HOWTO-6.html#ss6.2">Setting up the initial database</A> +</UL> +<P> +<H2><A NAME="toc7">7.</A> <A HREF="mythtv-HOWTO-7.html">Configuring Sound.</A></H2> + +<UL> +<LI><A NAME="toc7.1">7.1</A> <A HREF="mythtv-HOWTO-7.html#ss7.1">Graphically setting up the mixer</A> +<LI><A NAME="toc7.2">7.2</A> <A HREF="mythtv-HOWTO-7.html#ss7.2">Setting the mixer from the command line</A> +</UL> +<P> +<H2><A NAME="toc8">8.</A> <A HREF="mythtv-HOWTO-8.html">Setting up a remote control.</A></H2> + +<UL> +<LI><A NAME="toc8.1">8.1</A> <A HREF="mythtv-HOWTO-8.html#ss8.1">Gentoo</A> +<LI><A NAME="toc8.2">8.2</A> <A HREF="mythtv-HOWTO-8.html#ss8.2">Obtaining and compiling lirc</A> +<LI><A NAME="toc8.3">8.3</A> <A HREF="mythtv-HOWTO-8.html#ss8.3">Completing the lirc install </A> +<LI><A NAME="toc8.4">8.4</A> <A HREF="mythtv-HOWTO-8.html#ss8.4">Additional information for lirc</A> +<LI><A NAME="toc8.5">8.5</A> <A HREF="mythtv-HOWTO-8.html#ss8.5">Configuring lirc for use with an IR blaster</A> +</UL> +<P> +<H2><A NAME="toc9">9.</A> <A HREF="mythtv-HOWTO-9.html">Configuring MythTV. </A></H2> + +<UL> +<LI><A NAME="toc9.1">9.1</A> <A HREF="mythtv-HOWTO-9.html#ss9.1">Configuring the Master backend system</A> +<LI><A NAME="toc9.2">9.2</A> <A HREF="mythtv-HOWTO-9.html#ss9.2">Post-configuration</A> +<LI><A NAME="toc9.3">9.3</A> <A HREF="mythtv-HOWTO-9.html#ss9.3">Configuring a non-master backend </A> +<LI><A NAME="toc9.4">9.4</A> <A HREF="mythtv-HOWTO-9.html#ss9.4">Configuring and running mythfilldatabase</A> +<LI><A NAME="toc9.5">9.5</A> <A HREF="mythtv-HOWTO-9.html#ss9.5">Grabbing channel icons for Schedules Direct users</A> +</UL> +<P> +<H2><A NAME="toc10">10.</A> <A HREF="mythtv-HOWTO-10.html">Configuring mythfrontend.</A></H2> + +<UL> +<LI><A NAME="toc10.1">10.1</A> <A HREF="mythtv-HOWTO-10.html#ss10.1">General</A> +<LI><A NAME="toc10.2">10.2</A> <A HREF="mythtv-HOWTO-10.html#ss10.2">Appearance</A> +<LI><A NAME="toc10.3">10.3</A> <A HREF="mythtv-HOWTO-10.html#ss10.3">Program Guide</A> +<LI><A NAME="toc10.4">10.4</A> <A HREF="mythtv-HOWTO-10.html#ss10.4">Playback </A> +<LI><A NAME="toc10.5">10.5</A> <A HREF="mythtv-HOWTO-10.html#ss10.5">Recording </A> +<LI><A NAME="toc10.6">10.6</A> <A HREF="mythtv-HOWTO-10.html#ss10.6">Xbox Frontends</A> +</UL> +<P> +<H2><A NAME="toc11">11.</A> <A HREF="mythtv-HOWTO-11.html">Using MythTV.</A></H2> + +<UL> +<LI><A NAME="toc11.1">11.1</A> <A HREF="mythtv-HOWTO-11.html#ss11.1">Keyboard commands</A> +<LI><A NAME="toc11.2">11.2</A> <A HREF="mythtv-HOWTO-11.html#ss11.2">Using themes with MythTV</A> +<LI><A NAME="toc11.3">11.3</A> <A HREF="mythtv-HOWTO-11.html#ss11.3">Adding DishTV information to the database</A> +<LI><A NAME="toc11.4">11.4</A> <A HREF="mythtv-HOWTO-11.html#ss11.4">Adding support for an external tuner</A> +<LI><A NAME="toc11.5">11.5</A> <A HREF="mythtv-HOWTO-11.html#ss11.5">Using Shutdown/Wakeup</A> +<LI><A NAME="toc11.6">11.6</A> <A HREF="mythtv-HOWTO-11.html#ss11.6">Controlling the mythfrontend via telnet</A> +</UL> +<P> +<H2><A NAME="toc12">12.</A> <A HREF="mythtv-HOWTO-12.html">Scheduling Recordings.</A></H2> + +<UL> +<LI><A NAME="toc12.1">12.1</A> <A HREF="mythtv-HOWTO-12.html#ss12.1">Record Types</A> +<LI><A NAME="toc12.2">12.2</A> <A HREF="mythtv-HOWTO-12.html#ss12.2">Scheduling Options</A> +<LI><A NAME="toc12.3">12.3</A> <A HREF="mythtv-HOWTO-12.html#ss12.3">Storage Options</A> +<LI><A NAME="toc12.4">12.4</A> <A HREF="mythtv-HOWTO-12.html#ss12.4">Post Recording Processing</A> +<LI><A NAME="toc12.5">12.5</A> <A HREF="mythtv-HOWTO-12.html#ss12.5">Advanced Recording Options</A> +<LI><A NAME="toc12.6">12.6</A> <A HREF="mythtv-HOWTO-12.html#ss12.6">Scheduling with more than one Input</A> +</UL> +<P> +<H2><A NAME="toc13">13.</A> <A HREF="mythtv-HOWTO-13.html">MythPlugins. </A></H2> + +<P> +<H2><A NAME="toc14">14.</A> <A HREF="mythtv-HOWTO-14.html">MythWeb.</A></H2> + +<UL> +<LI><A NAME="toc14.1">14.1</A> <A HREF="mythtv-HOWTO-14.html#ss14.1">Installation and prerequisites</A> +<LI><A NAME="toc14.2">14.2</A> <A HREF="mythtv-HOWTO-14.html#ss14.2">Completing the installation</A> +<LI><A NAME="toc14.3">14.3</A> <A HREF="mythtv-HOWTO-14.html#ss14.3">Resetting the key binding table</A> +<LI><A NAME="toc14.4">14.4</A> <A HREF="mythtv-HOWTO-14.html#ss14.4">Resetting the theme.</A> +</UL> +<P> +<H2><A NAME="toc15">15.</A> <A HREF="mythtv-HOWTO-15.html">MythGallery.</A></H2> + +<UL> +<LI><A NAME="toc15.1">15.1</A> <A HREF="mythtv-HOWTO-15.html#ss15.1">Installation and prerequisites</A> +<LI><A NAME="toc15.2">15.2</A> <A HREF="mythtv-HOWTO-15.html#ss15.2">Using MythGallery</A> +<LI><A NAME="toc15.3">15.3</A> <A HREF="mythtv-HOWTO-15.html#ss15.3">Importing Pictures</A> +</UL> +<P> +<H2><A NAME="toc16">16.</A> <A HREF="mythtv-HOWTO-16.html">MythGame.</A></H2> + +<UL> +<LI><A NAME="toc16.1">16.1</A> <A HREF="mythtv-HOWTO-16.html#ss16.1">Setup Directory Structure</A> +<LI><A NAME="toc16.2">16.2</A> <A HREF="mythtv-HOWTO-16.html#ss16.2">Download and Install xmame</A> +<LI><A NAME="toc16.3">16.3</A> <A HREF="mythtv-HOWTO-16.html#ss16.3">Download extra files</A> +<LI><A NAME="toc16.4">16.4</A> <A HREF="mythtv-HOWTO-16.html#ss16.4">Download and Install MythGame.</A> +<LI><A NAME="toc16.5">16.5</A> <A HREF="mythtv-HOWTO-16.html#ss16.5">Setup xmame in MythGame</A> +<LI><A NAME="toc16.6">16.6</A> <A HREF="mythtv-HOWTO-16.html#ss16.6">Hints:</A> +</UL> +<P> +<H2><A NAME="toc17">17.</A> <A HREF="mythtv-HOWTO-17.html">MythMusic. </A></H2> + +<UL> +<LI><A NAME="toc17.1">17.1</A> <A HREF="mythtv-HOWTO-17.html#ss17.1">Manual installation of prerequisites</A> +<LI><A NAME="toc17.2">17.2</A> <A HREF="mythtv-HOWTO-17.html#ss17.2">Mandriva</A> +<LI><A NAME="toc17.3">17.3</A> <A HREF="mythtv-HOWTO-17.html#ss17.3">Red Hat Linux 9</A> +<LI><A NAME="toc17.4">17.4</A> <A HREF="mythtv-HOWTO-17.html#ss17.4">Compiling MythMusic</A> +<LI><A NAME="toc17.5">17.5</A> <A HREF="mythtv-HOWTO-17.html#ss17.5">Configuring MythMusic</A> +<LI><A NAME="toc17.6">17.6</A> <A HREF="mythtv-HOWTO-17.html#ss17.6">Using MythMusic</A> +<LI><A NAME="toc17.7">17.7</A> <A HREF="mythtv-HOWTO-17.html#ss17.7">Troubleshooting MythMusic</A> +</UL> +<P> +<H2><A NAME="toc18">18.</A> <A HREF="mythtv-HOWTO-18.html">MythWeather.</A></H2> + +<P> +<H2><A NAME="toc19">19.</A> <A HREF="mythtv-HOWTO-19.html">MythVideo.</A></H2> + +<P> +<H2><A NAME="toc20">20.</A> <A HREF="mythtv-HOWTO-20.html">MythDVD.</A></H2> + +<UL> +<LI><A NAME="toc20.1">20.1</A> <A HREF="mythtv-HOWTO-20.html#ss20.1">Manual Compilation of Prerequisites</A> +<LI><A NAME="toc20.2">20.2</A> <A HREF="mythtv-HOWTO-20.html#ss20.2">Pre-compiled binaries</A> +<LI><A NAME="toc20.3">20.3</A> <A HREF="mythtv-HOWTO-20.html#ss20.3">Running the Myth Transcoding Daemon</A> +</UL> +<P> +<H2><A NAME="toc21">21.</A> <A HREF="mythtv-HOWTO-21.html">MythNews.</A></H2> + +<P> +<H2><A NAME="toc22">22.</A> <A HREF="mythtv-HOWTO-22.html">Troubleshooting.</A></H2> + +<UL> +<LI><A NAME="toc22.1">22.1</A> <A HREF="mythtv-HOWTO-22.html#ss22.1">Compiling</A> +<LI><A NAME="toc22.2">22.2</A> <A HREF="mythtv-HOWTO-22.html#ss22.2">Debugging </A> +<LI><A NAME="toc22.3">22.3</A> <A HREF="mythtv-HOWTO-22.html#ss22.3">Installing</A> +<LI><A NAME="toc22.4">22.4</A> <A HREF="mythtv-HOWTO-22.html#ss22.4">Using</A> +<LI><A NAME="toc22.5">22.5</A> <A HREF="mythtv-HOWTO-22.html#ss22.5">Miscellaneous</A> +</UL> +<P> +<H2><A NAME="toc23">23.</A> <A HREF="mythtv-HOWTO-23.html">Miscellaneous. </A></H2> + +<UL> +<LI><A NAME="toc23.1">23.1</A> <A HREF="mythtv-HOWTO-23.html#ss23.1">I'd like to watch the files without using MythTV / I'd like to convert the files to some other format</A> +<LI><A NAME="toc23.2">23.2</A> <A HREF="mythtv-HOWTO-23.html#ss23.2">Using a different window manager</A> +<LI><A NAME="toc23.3">23.3</A> <A HREF="mythtv-HOWTO-23.html#ss23.3">What capture resolution should I use? How does video work? </A> +<LI><A NAME="toc23.4">23.4</A> <A HREF="mythtv-HOWTO-23.html#ss23.4">MythTV GUI and X Display Sizes</A> +<LI><A NAME="toc23.5">23.5</A> <A HREF="mythtv-HOWTO-23.html#ss23.5">Saving or restoring the database </A> +<LI><A NAME="toc23.6">23.6</A> <A HREF="mythtv-HOWTO-23.html#ss23.6">Deleting the MySQL database</A> +<LI><A NAME="toc23.7">23.7</A> <A HREF="mythtv-HOWTO-23.html#ss23.7">Moving your data to new hardware</A> +<LI><A NAME="toc23.8">23.8</A> <A HREF="mythtv-HOWTO-23.html#ss23.8">btaudio </A> +<LI><A NAME="toc23.9">23.9</A> <A HREF="mythtv-HOWTO-23.html#ss23.9">Removing unwanted channels</A> +<LI><A NAME="toc23.10">23.10</A> <A HREF="mythtv-HOWTO-23.html#ss23.10">NFS</A> +<LI><A NAME="toc23.11">23.11</A> <A HREF="mythtv-HOWTO-23.html#ss23.11">Automatically starting mythfrontend at system boot time</A> +<LI><A NAME="toc23.12">23.12</A> <A HREF="mythtv-HOWTO-23.html#ss23.12">Automatically starting mythbackend at system boot time</A> +<LI><A NAME="toc23.13">23.13</A> <A HREF="mythtv-HOWTO-23.html#ss23.13">Advanced Backend Configurations </A> +<LI><A NAME="toc23.14">23.14</A> <A HREF="mythtv-HOWTO-23.html#ss23.14">Using the transcoder</A> +<LI><A NAME="toc23.15">23.15</A> <A HREF="mythtv-HOWTO-23.html#ss23.15">Changing your hostname</A> +<LI><A NAME="toc23.16">23.16</A> <A HREF="mythtv-HOWTO-23.html#ss23.16">Can I run MythTV on my TiVo?</A> +<LI><A NAME="toc23.17">23.17</A> <A HREF="mythtv-HOWTO-23.html#ss23.17">Can I run MythTV on my ReplayTV?</A> +<LI><A NAME="toc23.18">23.18</A> <A HREF="mythtv-HOWTO-23.html#ss23.18">Can a wireless connection be used between the frontend and the backend?</A> +<LI><A NAME="toc23.19">23.19</A> <A HREF="mythtv-HOWTO-23.html#ss23.19">How can I burn shows that I have recorded to a DVD?</A> +<LI><A NAME="toc23.20">23.20</A> <A HREF="mythtv-HOWTO-23.html#ss23.20">Using the DBoxII within MythTV</A> +<LI><A NAME="toc23.21">23.21</A> <A HREF="mythtv-HOWTO-23.html#ss23.21">What do the icons on the Watch Recordings screen mean?</A> +<LI><A NAME="toc23.22">23.22</A> <A HREF="mythtv-HOWTO-23.html#ss23.22">What do the letters mean when I change channels?</A> +<LI><A NAME="toc23.23">23.23</A> <A HREF="mythtv-HOWTO-23.html#ss23.23">What is the difference between the various Hauppauge PVR models?</A> +<LI><A NAME="toc23.24">23.24</A> <A HREF="mythtv-HOWTO-23.html#ss23.24">Changing channels on an external Set Top Box</A> +<LI><A NAME="toc23.25">23.25</A> <A HREF="mythtv-HOWTO-23.html#ss23.25">Configuring one machine to flag all commercials</A> +</UL> +<P> +<H2><A NAME="toc24">24.</A> <A HREF="mythtv-HOWTO-24.html">Example Configurations.</A></H2> + +<UL> +<LI><A NAME="toc24.1">24.1</A> <A HREF="mythtv-HOWTO-24.html#ss24.1">Logical Volume Manager (LVM) </A> +<LI><A NAME="toc24.2">24.2</A> <A HREF="mythtv-HOWTO-24.html#ss24.2">Advanced Partition Formatting </A> +<LI><A NAME="toc24.3">24.3</A> <A HREF="mythtv-HOWTO-24.html#ss24.3">Migrating from DataDirect Labs to Schedules Direct</A> +<LI><A NAME="toc24.4">24.4</A> <A HREF="mythtv-HOWTO-24.html#ss24.4">Caching support for Schedules Direct</A> +</UL> +<HR> +<A HREF="mythtv-HOWTO-1.html">Next</A> +Previous +Contents +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/keys.txt b/abs/core-testing/local-website/htdocs/mythtv-doc/keys.txt new file mode 100644 index 0000000..4385fb4 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/keys.txt @@ -0,0 +1,325 @@ +Various keys and their actions: + +mythfrontend +------------ + +- Arrow keys are used to move the highlight point around. +- ALT-F4 to exit out of the application. +- Space or Enter to take action on the item under the highlight point. +- P to play in both "Watch a Recording" and "Delete a Recording". +- D to delete in both "Watch a Recording" and "Delete a Recording". +- E to enter the Custom Record editor for the selected title on the EPG, + "Program Finder", "Upcoming Recordings" and search results screens. +- U to view details for the currently selected show on the Watch or + Delete screens, EPG, "Program Finder", "Upcoming Recordings" + and search results screens. +- O to list the upcoming episodes for the currently selected show + on any page where a show title may be highlighed. +- I to edit recording options from any of the pages for scheduling + recordings. From the Watch and Delete screens, 'I' presents options + for recorded shows such as Auto Expire or Stop Recording. +- Y on the "Upcoming Recordings" page switches which capture cards' + items are displayed in the highlight color. + +Watching TV or a recording +-------------------------- + +- P Pause / Play. + You may also add an explicit keybinding for "Play" through the + MythWeb keybindings page, returning you to normal speed if you + are in slow-motion, rewind, fast forward or pause mode. +- ESC Exit player if no OSD on screen, otherwise exit OSD. +- I Puts the On-screen Display up again. + During playback, 'I' toggles between position and show description info. + If a number of minutes is entered, jump to that position. +- M Menu (allows access to EPG and many other useful features +- K Jumps to the bookmark position. +- T In North America this toggles closed caption support. +- T In Europe follow this with the teletext page and another T +- F Rotate between the various Picture Adjustments (Colour, Hue, etc.) + While Picture Adjustment is on-screen, use Left and Right arrows + to adjust. These settings adjust the look of the video playback, + and are independent of the G-key settings used at record-time. + The Xv picture controls must be enabled in the Playback settings. +- U Increase the play speed [muted] +- J Decrease the play speed [muted] +- A Adjust time stretch (speed up or slow down play speed [with audio]) + Use the arrow keys to make adjustment. +- W Cycle through zoom modes: Half, Full, Stretch +- Ctrl-W Force aspect ratio of video to be treated as either 4:3 or 16:9 +- S Display the Program Guide (EPG). +- F6 Display the Program Finder. +- F8 Cycle through sleep timer settings Off->30m->1hr->1hr30m->2hr->Off +- Left arrow Skip back +- Right arrow Skip ahead + NOTE: During playback of a recording you can enter a number of minutes to + jump before using the Skip key. Otherwise, the configured defaults + will be used. Seconds can be entered by entering four digits in the + MMss format. + +- Page Up Jump back the configured number of minutes. (default is 10) +- Page Down Jump ahead the configured number of minutes. (default is 10) +- Z or End Skip to next commercial break marker +- Q or Home Skip back to previous commercial break marker +- + or - Cycle through audio streams +- | or F9 Toggle mute +- [ or F10 Decrease volume +- ] or F11 Increase volume +- Ctrl+B Jump to the beginning of the recording / ringbuffer. + +When in Teletext Menu mode: +- Up/Down Previous/Next Page +- Left/Right Previous/Next Subpage +- T Exit Teletext Menu +- F2-F6 Menu Red, Green, Yellow, Blue, or White, respectively +- F7 Toggle Background on/off +- F8 Reveal hidden text. + +When MHEG ITV is enabled: +- F2-F5 Menu Red, Green, Yellow, or Blue, respectively +- F6 Exit key, exits from interactive mode on some channels +- F7 Text key, enters interactive mode on some channels +- F12 EPG key, enters EPG mode (New Zealand only). + The effect of these keys depends on what is being displayed. The arrow, + Enter, and 0-9 keys may also be used. + +Without the stickykeys option selected: + +- Left arrow to rewind the configured number of seconds. (default is 5) +- Right arrow to fast forward the configured number of seconds. (default is 30) +- < starts rewind mode as if stickykeys are selected. + If a jump amount is entered, jump to that position. +- > starts fast forward mode as if stickykeys are selected. + If a jump amount is entered, jump that amount from the end. + +With the stickykeys option selected: + +- Right starts fast forward mode. +- Left starts rewind mode. + While in fast forward or rewind mode. + - Left/Right increases the ff/rew speed. + - 0 plays at normal speed, but leaves the time indicator on screen. + - 1 or 2 plays back more slowly than normal ff/rew speed (1 is slowest). + - 3 plays back at normal ff/rew speed. + - 4 - 9 plays back faster than normal ff/rew speed (9 is fastest). + - Space exits fast forward or rewind mode. + +With the video paused: + +- Left arrow Rewind one frame +- < or comma Rewind one second +- Right arrow Advance one frame +- > or period Advance one second + +Watching TV only: + +- 0-9 Enter a channel number... + If the channel is not unique or smart channel change is disabled + press Return/OK when done, to commit the channel change. +- G Rotate between the various Picture Adjustments (Colour, Hue, etc.) + for recording. These values affect the look for all recordings made + with the current capture card and are independent of the playback + picture settings. While Picture Adjustment is on-screen, use Left and + Right arrows to adjust. +- Ctrl-G The same as G, except it affects the look for all recordings made + on the current channel, independent of the capture card used. +- H Channel history. Each repeat steps back through the previous channels. +- O Turns on 'Browse' mode, allowing user to browse channels and program + info while watching current show FullScreen. +- / Change to the next "favorite" channel +- ? Mark/Unmark the current channel as a "favorite" channel +- Y Switch to the next available capture source +- Ctrl-Y Switch to the previous capture source +- C Change to the next available tuner card input +- F7 Monitor signal quality on a card capable of signal monitoring + +LiveTV while not in Browse Mode: +- Up/Down arrows Change the channel. + +LiveTV Browse Mode: +- Left browse program prior to current listed program. +- Right browse program following current listed program. +- Up browse program on channel above current listed channel/program. +- Down browse program on channel below current listed channel/program. +- / browse program on next favorite channel. +- 0-9 enter a channel number to browse. +- Space/Enter change channel to channel of current listed program. +- R Toggle recording of current program (cycles through types) +- ESC/O Exit Browse mode. + +Playback Recording +- Y Adjust Audio Sync +- R Cycle Commercial-Skip Mode + +Playback Recording Zoom Mode: +- Left Move video to Left +- Right Move video to Right +- Up Move video Up +- Down Move video Down +- PageUp Zoom In +- PageDown Zoom Out +- Space/Enter Exit Zoom mode leaving picture at current size and position +- ESC Exit Zoom mode and return to original size. + +If you have two or more tuner cards: + +- V toggle Picture-in-picture on or off +- B toggles the window focus (lets you change channels on the PiP window). +- N swaps the two channels by changing channels on both cards. + +While watching a recording: + +- SPACE or ENTER will set a bookmark at that point. Next time you start the + recording, you will automatically jump forward to this point and clear the + bookmark. +- E or M enters/exits edit mode. + - The left and right keys move forward and backward. + - The up and down arrow keys alter the amount of time you jump forward and + backward. Increments are: nearest cutpoint, nearest video keyframe, + 1 frame, 0.5 seconds, 1 second, 20 seconds, 1 minute, 5 minutes, and + 10 minutes. + - The page up and down keys move forward and backward to the nearest cut + point. + - The < or comma and > or period keys move forward or backward by 10 times + the normal jump amount. + - Space/Enter allows you to set or delete a cut point. + - 'Z' loads the commercial skip list (if one exists) into the cutlist. + - 'C' and 'Q' clear all cut points in the cutlist. + - 'I' inverts the cutlist. +- X queues the current recording for transcoding. +- O brings up menu to allow toggling settings such as Commercial Auto-Skip, + Auto-Expire, etc. +- D exits the current recording and displays the Delete menu for it. + + +EPG +--- + +- Arrow keys are used to move the highlighted program point around. +- The keys A, D, S, W perform the same as left, right, down and up. +- PageUp and PageDown move the channel list up or down a page. +- Home and End move the highlight left or right by one day. +- Control-Left and Control Right, <, >, period and comma keys move the + highlight left or right by one page. +- The keys 9, 3, 7 and 1 (like a numeric keypad) perform the same as PageUp, + PageDown, Home and End. +- I will bring up more information about a show, and allow you to schedule + a recording. + - If you select "Record this showing" while watching Live TV you can + "Instant Record" a program. +- Space or Enter will allow you resolve conflicts or change overrides. + If the program is not already scheduled to record, it will act like + pressing I instead. +- Pressing M when on a channel will change to that channel. +- Pressing ESC or C exits without changing the channel. +- Pressing R will change the current item from Recording/Not-Recording. + Successive keypresses cycle through the scheduled recording type list. +- Pressing X will change the channel to the currently selected channel without + leaving the EPG (Most useful in the alternate EPG) +- Pressing '?' will mark/unmark the current channel as a "favorite" +- Pressing '/' or 4 will toggle the guide listing between all channels and + "favorites". + +Set Program Recording Priorities and Set Channel Recording Priorities +--------------------------------------------------------------------- + +- Right increases priority value. +- Left decreases priority value. +- 1 sorts by title. +- 2 sorts by priority. +- Home/End to toggle sort priority. +- I to edit recording options. +- ESC commits changes and exits. + +Viewing Scheduled Recordings/Resolving Conflicts +------------------------------------------------- + +- 1 to show all recordings. +- 2 to show only important recordings. +- Home/End to toggle show showing all/important. +- I to edit recording options. +- Space or Enter to resolve conflict or override. + +Viewing Search Listings +----------------------- +- Home to change to the previous view if applicable. +- End to change to the next view if applicable. +- M to select another view if applicable. + - In the title and description search popup, press M again to edit or + delete the selected view. + +Program Finder +-------------- +- R will change the current item from Recording/Not-Recording. + Successive keypresses cycle through the scheduled recording type list. +- 4 switch to the Program Guide. +- 5 move to the middle of the active list. + +Recording Profiles Setup Screen +------------------------------- + +- D on a custom profile group displays a popup to delete the group. + +Recording Groups +---------------- + +Recording Groups allow you to separate programs into user-defined +categories, such as "Kids", "Alice", "Bob", etc. This can be used to reduce +clutter, or to segregate content if you use the PIN function. + +In the Watch Recordings Screen +- M to change the view or to set a group password +- I to move a program from one Recording Group to another + +Watch Recordings Screen +----------------------- + +- "1" or F1 to get a popup on the meaning of the icons +- / to tag a recording. Tagged recordings can be played (in order or + shuffled) and deleted as a group. You can also change the + recording group for several recordings at once by tagging them and + using the popup INFO menu to change the recording group. +- ? to clear the tagged list. + +Remote Controls +--------------- + +If you are using MythTV with just a remote control then it is suggested that you +map the remote control keys as described below. Your remote control may not +have the same set of keys as those named below, the names are only a suggestion +that roughly correspond to the function. + +If you are adding new key bindings to the program then consideration of this +suggested list will help users with remote controls. + +This list assumes a minimal remote control that only has 20 keys, nearly all +features can be used with this configuration. If you have more keys then you +can access all of the features. With only 16 keys most features are usable. + + +Remote Control LIRC Keystroke Function +-------------- -------------- -------- + +0 - 9 0 - 9 channel selection, EPG navigation, + ff/rew speed setting (with stickykeys) + +Left Arrow Left scroll left, rewind +Right Arrow Right scroll right, fast forward + +Up Arrow Up scroll up, channel change up +Down Arrow Down scroll down, channel change down + +Select / OK / Play Space Select item, play (with stickykeys) + set bookmark + +Cancel Escape Cancel, quit playback + +Menu m EPG (from watching TV) + edit (from playback). + +Pause p Pause + +Other key 1 i Information + +Other key 2 c Change tuner card input + diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-1.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-1.html new file mode 100644 index 0000000..2f9fb22 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-1.html @@ -0,0 +1,272 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: First things first.</TITLE> + <LINK HREF="mythtv-HOWTO-2.html" REL=next> + + <LINK HREF="mythtv-HOWTO.html#toc1" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-2.html">Next</A> +Previous +<A HREF="mythtv-HOWTO.html#toc1">Contents</A> +<HR> +<H2><A NAME="s1">1.</A> <A HREF="mythtv-HOWTO.html#toc1">First things first.</A></H2> + +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Please note that I, Robert Kulagowski, am <EM>NOT</EM> the +author/programmer of the MythTV application! I can not give you +personalized installation support. If you are having issues installing +MythTV you should examine the archives, or post your question to the +MythTV-users mailing list. If you send me "Does MythTV work with 'X'"? +messages - I will simply instruct you to ask your question on the +mythtv-users mailing list.</CAPTION> +</FIGURE> +</P> +<H2><A NAME="ss1.1">1.1</A> <A HREF="mythtv-HOWTO.html#toc1.1">What is MythTV?</A> +</H2> + +<P>MythTV is a GPL licensed suite of programs that allow you to build the +mythical home media convergence box on your own using Open Source software +and operating systems. MythTV is known to work on Linux and Mac OS X +(PowerPC and Intel). It does not run on Windows.</P> +<P>MythTV has a number of capabilities. The television portion allows you to +do the following: +<UL> +<LI>You may pause, fast-forward and rewind live Television.</LI> +<LI>You may install multiple video capture cards to record more than one +program at a time.</LI> +<LI>You can have multiple servers (called "backends"), each with multiple +capture cards in them. All scheduling is performed by the Master backend, +which arbitrates which recording will be performed by each device. All +recording requests are managed by the Master backend, so you can schedule a +recording from any client.</LI> +<LI>You can have multiple clients (called "frontends" in MythTV parlance), +each with a common view of all available programs. Any client can watch any +program that was recorded by any of the servers, assuming that they have the +hardware capabilities to view the content; a low-powered frontend will not +be able to watch HDTV, for example. Clients can be diskless and controlled +entirely by a remote control.</LI> +<LI>You may use any combination of standard analog capture card, MPEG-2, +MJPEG, DVB, HDTV, USB and firewire capture devices. With appropriate +hardware, MythTV can control set top boxes, often found in digital cable and +satellite TV systems.</LI> +<LI>Program Guide Data in North America is downloaded from +schedulesdirect.org, a non-profit organization which has licensed data from +Tribune Media Services. This service provides almost two weeks of +scheduling information. Program Guide Data in other countries is obtained +using XMLTV. MythTV uses this information to create a schedule that +maximizes the number of programs that can be recorded if you don't have +enough tuners.</LI> +<LI>MythTV implements a UPNP server, so a UPNP client should automatically +see content from your MythTV system.</LI> +</UL> + +Other modules in MythTV include: +<UL> +<LI>MythArchive, a tool to create DVDs</LI> +<LI>MythBrowser, a web browser</LI> +<LI>MythControls, an application to configure your remote control</LI> +<LI>MythFlix, a Netflix module</LI> +<LI>MythGallery, a picture-viewing application</LI> +<LI>MythGame</LI> +<LI>MythMusic, a music playing / ripping application which supports MP3 +and FLAC</LI> +<LI>MythNews, a RSS news grabber</LI> +<LI>MythPhone, phone and videophone using SIP.</LI> +<LI>MythVideo, DVD ripper and a media-viewer for content not created within MythTV</LI> +<LI>MythWeather</LI> +<LI>MythWeb, which allows you to control your MythTV system using a web +browser. With MythWeb, you can schedule and delete recordings, change +keybindings and more. With proper security, you may even schedule a program +over the Internet and have it immediately acted on by the Master backend.</LI> +</UL> +</P> +<H2><A NAME="ss1.2">1.2</A> <A HREF="mythtv-HOWTO.html#toc1.2">QuickStart</A> +</H2> + +<P>Custom mini-distributions are available to make it easier to install +MythTV. A mini-distribution removes many of the "general purpose" +workstation / server software packages that may be installed by default if +you use one of the big-name OS packages.</P> +<P>See +<A HREF="http://mysettopbox.tv">http://mysettopbox.tv</A> if you'd +like to install a custom version of Knoppix optimized for MythTV.</P> +<P>See +<A HREF="http://www.minimyth.org">http://www.minimyth.org</A> if you'd like +to install MythTV onto a diskless system.</P> +<P>See +<A HREF="http://bit.blkbk.com">http://bit.blkbk.com</A> if you'd +like to install MythTV on a Xbox. +<B>NOTE</B>: Site appears unmaintained.</P> +<P>See +<A HREF="http://wilsonet.com/mythtv/">http://wilsonet.com/mythtv/</A> for instructions tailored to RedHat's +Fedora Core distribution.</P> +<P>See +<A HREF="http://www.mythbuntu.org">http://www.mythbuntu.org</A> if +you'd like to install a customized version of Ubuntu optimized for MythTV.</P> +<P>There is a MythTV wiki at +<A HREF="http://wiki.mythtv.org">http://wiki.mythtv.org</A>.</P> +<P>If you are installing this version for Schedules Direct support, please see +the +<A HREF="mythtv-HOWTO-24.html#migratingtoSD">Migrating from DataDirect Labs to Schedules Direct</A> section for additional information.</P> + +<H2><A NAME="ss1.3">1.3</A> <A HREF="mythtv-HOWTO.html#toc1.3">Upgrading from previous versions</A> +</H2> + +<P>The upgrade from previous versions should be transparent. Any changes to +the database structure should be applied automatically.</P> +<P>It is <EM>strongly</EM> recommended that you back up your database before +installing a new version of MythTV.</P> +<P>See +<A HREF="mythtv-HOWTO-23.html#backupdb">Saving or Restoring the database</A> for instructions.</P> + +<H2><A NAME="how_to_obtain"></A> <A NAME="ss1.4">1.4</A> <A HREF="mythtv-HOWTO.html#toc1.4">How to obtain this document / PDF versions of this document </A> +</H2> + +<P>This HOWTO document is maintained at the primary MythTV website: +<A HREF="http://www.mythtv.org">http://www.mythtv.org</A> by Robert +Kulagowski +<A HREF="mailto:rkulagow@rocketmail.com">mailto:rkulagow@rocketmail.com</A>.</P> +<P>This document is available as a single-page HTML document at +<A HREF="http://www.mythtv.org/docs/mythtv-HOWTO-singlehtml.html">http://www.mythtv.org/docs/mythtv-HOWTO-singlehtml.html</A> or as a PDF +at +<A HREF="http://www.mythtv.org/docs/mythtv-HOWTO.pdf">http://www.mythtv.org/docs/mythtv-HOWTO.pdf</A>.</P> +<P>This HOWTO is for MythTV v0.21</P> +<P>Release notes for this version may be found in the MythTV Wiki at +<A HREF="http://www.mythtv.org/wiki/index.php/Release_Notes_-_0.21">http://www.mythtv.org/wiki/index.php/Release_Notes_-_0.21</A></P> + +<H2><A NAME="ss1.5">1.5</A> <A HREF="mythtv-HOWTO.html#toc1.5">Books about MythTV</A> +</H2> + +<P>If you would like to purchase a book specifically about MythTV:</P> +<P> +<UL> +<LI>Hacking MythTV, ISBN 978-0470037874 by Wilson, Tittel, Wright and Korelc</LI> +<LI>Practical MythTV: Building a PVR and Media Center PC, ISBN 978-1590597798 by Smith and Still</LI> +</UL> +</P> + +<H2><A NAME="ss1.6">1.6</A> <A HREF="mythtv-HOWTO.html#toc1.6">Document conventions</A> +</H2> + +<P>The following conventions are used throughout this document.<BR> +<B>boldface</B> - used for program names.<BR> +<CODE>typewriter</CODE> - used for program paths.<BR> +<EM>emphasis</EM> - Pay attention here.<BR></P> +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION>Pay more attention.</CAPTION> +</FIGURE> +</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION>Ignore at your own peril.</CAPTION> +</FIGURE> +</P> +<P> +<FIGURE> +<EPS FILE="add.eps"> +<IMG SRC="add.png"> +<CAPTION>Feature that has been added to SVN (subversion, a revision control system) +but is not available in the current release.</CAPTION> +</FIGURE> +</P> + +<H2><A NAME="ss1.7">1.7</A> <A HREF="mythtv-HOWTO.html#toc1.7">Mailing lists / getting help</A> +</H2> + +<P>It's recommended that you join the user list at +<A HREF="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</A>. The developer +list is at +<A HREF="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev</A>. Please keep +the developer list strictly for development-related issues.</P> +<P>Searchable archives for the lists are available at +<A HREF="http://www.gossamer-threads.com/lists/mythtv/">http://www.gossamer-threads.com/lists/mythtv/</A>.</P> + +<H2><A NAME="ss1.8">1.8</A> <A HREF="mythtv-HOWTO.html#toc1.8">IRC</A> +</H2> + +<P>There are two IRC channels dedicated to MythTV which can be found on +irc.freenode.net +<UL> +<LI>mythtv</LI> +<LI>mythtv-users</LI> +</UL> +</P> +<P>The <CODE>mythtv</CODE> channel is where the developers discuss code. It is +<EM>not</EM> a user-support channel. Please don't ask non-development +related questions there.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION>Really. Even if there's no one in the mythtv-users IRC group or everyone +seems to be ignoring you.</CAPTION> +</FIGURE> +</P> + +<H2><A NAME="ss1.9">1.9</A> <A HREF="mythtv-HOWTO.html#toc1.9">Bug database</A> +</H2> + +<P>If you feel you need to contribute to a bug database, use the MythTV bug +ticketing system at +<A HREF="http://svn.mythtv.org/trac">http://svn.mythtv.org/trac</A>.</P> +<P>Good entries will contain the following: +<OL> +<LI>Qt version</LI> +<LI>Linux distribution</LI> +<LI>gcc version</LI> +<LI>the last entry in config.log to detail how you compiled</LI> +<LI>MythTV version numbers (<EM>e.g.</EM>from mythfrontend --version)</LI> +<LI>Hardware</LI> +<LI>How you are able to reproduce the bug</LI> +</OL> +</P> +<P>See the instructions on how to debug in +<A HREF="mythtv-HOWTO-22.html#debugging">Section 22</A>.</P> +<P>The bug database is not a chat room, so restrict your entries to what is +relevant. It's also not a repository of feature requests; a feature request +without an accompanying patch file to implement that feature will be quickly +closed. There is a feature wishlist on the wiki at +<A HREF="http://www.mythtv.org/wiki/index.php/Feature_Wishlist">http://www.mythtv.org/wiki/index.php/Feature_Wishlist</A>. There is no +guarantee that anything on the wishlist will ever get code written to +implement it.</P> +<P>If a developer closes out your bug, it's likely you didn't provide enough +information. Don't re-open a bug without providing additional information.</P> + +<H2><A NAME="ss1.10">1.10</A> <A HREF="mythtv-HOWTO.html#toc1.10">Contributing to this document</A> +</H2> + +<P>Contributions to the HOWTO are welcome, especially if you find a +grammatical or spelling error, or if the wording of something is just plain +confusing.</P> +<P>If you'd like to make a new contribution, create a ticket at +<A HREF="http://svn.mythtv.org/trac">http://svn.mythtv.org/trac</A> and +click "New Ticket". The type should be set to "patch" and the owner set to +"rkulagow" to ensure that I see your contribution.</P> +<P>Please send it as either SGML or as plain text. <EM>NO HTML</EM>. The +source used to create the HOWTO is in SGML / Linuxdoc. Do not be afraid of +SGML! A quick look at the source of this HOWTO will show that it is not +difficult, because there aren't that many tags to worry about, so at least +<EM>try</EM> to submit as SGML. See the Linuxdoc HOWTO at +<A HREF="http://www.tldp.org/HOWTO/Howtos-with-LinuxDoc.html">http://www.tldp.org/HOWTO/Howtos-with-LinuxDoc.html</A> for information +on the linuxdoc format itself, or look at the <CODE>mythtv-HOWTO.sgml</CODE> +file as an example.</P> +<P>To create the actual patch, run <B>diff -u origfilename newfile > +doc.patch</B> and attach your contribution to the trac ticket.</P> + +<HR> +<A HREF="mythtv-HOWTO-2.html">Next</A> +Previous +<A HREF="mythtv-HOWTO.html#toc1">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-10.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-10.html new file mode 100644 index 0000000..636696e --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-10.html @@ -0,0 +1,387 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: Configuring mythfrontend.</TITLE> + <LINK HREF="mythtv-HOWTO-11.html" REL=next> + <LINK HREF="mythtv-HOWTO-9.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc10" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-11.html">Next</A> +<A HREF="mythtv-HOWTO-9.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc10">Contents</A> +<HR> +<H2><A NAME="s10">10.</A> <A HREF="mythtv-HOWTO.html#toc10">Configuring mythfrontend.</A></H2> + +<P>Once you have completed configuration of your backend systems, the next +step is to configure the frontend client. </P> +<P>When you start mythfrontend for the first time, it will attempt to connect +to a configuration database on the local machine. If there is none, a +"Database Configuration" screen will appear, and you will need to fill in +some details. The "Host name" field needs the backend or database server's +IP address or DNS name, and the User or password fields may need to be set +to match your database user accounts. After editing those fields, press +Enter twice to write these configurations on your local machine, and attempt +to connect to the database. If you make any mistakes, the screens will pop +up again.</P> +<P>Now that mythfrontend has started up, you should have a number of +buttons/choices. Before doing anything, go to TV, then to Setup and +configure the frontend client. +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: You should go through the various setup screens in +mythfrontend before using any other modules to ensure that the the database +is correctly initialized.</CAPTION> +</FIGURE> +</P> +<H2><A NAME="ss10.1">10.1</A> <A HREF="mythtv-HOWTO.html#toc10.1">General</A> +</H2> + +<P>The General screen has configuration items that don't really fit anywhere +else. The first few configuration items ask you to indicate the number of +seconds to record before or after a program, which is useful if the +broadcast network or your system clock are out of sync and will help prevent +you missing the beginning or end of a program. </P> +<P>To change the value, use the left and right arrow keys to increment and +decrement the number of seconds. When you're satisfied with the result, use +the down arrow to put the input focus on the Next button or press RETURN to +continue to the next page.</P> +<P>The next page has a number of options to do with how channels are displayed +on your system. The help text will give you more information. Move the +focus to Next and press the space bar to continue.</P> +<P>The last General page sets up some final configuration items. See the help +text for more information.</P> + +<H2><A NAME="ss10.2">10.2</A> <A HREF="mythtv-HOWTO.html#toc10.2">Appearance</A> +</H2> + +<P>This set of screens is mostly concerned with how MythTV will look on your +system. From here, you can choose different themes and set the resolution +of your system.</P> + +<H2><A NAME="ss10.3">10.3</A> <A HREF="mythtv-HOWTO.html#toc10.3">Program Guide</A> +</H2> + +<P>Fairly self explanatory. Note that the alternate program guide does not +use the same font settings as defined in Appearance, so if the EPG is +unreadable this is where you make the adjustments to fonts, number of +elements displayed, etc.</P> + +<H2><A NAME="deinterlace_"></A> <A NAME="ss10.4">10.4</A> <A HREF="mythtv-HOWTO.html#toc10.4">Playback </A> + </H2> + +<P>The one configuration item which may cause problems on your system is the +"Deinterlace playback" setting. MythTV uses a linear blend algorithm for +deinterlacing, which will improve how the image looks on your screen. +Deinterlacing requires that your processor support SSE. (Streaming SIMD +Extensions, aka "MMX2"). Early Intel Celeron (those that don't use the +Coppermine 0.18um core and are usually <600MHz), Pentium Pro and Pentium II +CPUs do not have SSE, so make sure you haven't enabled deinterlacing if +your processor doesn't support it. If you enable it, and your processor +doesn't support SSE, you will get "Illegal Instruction" errors.</P> +<P>To determine if you've got SSE on an Intel processor, you can: +<BLOCKQUOTE><CODE> +<PRE> +$ cat /proc/cpuinfo +[snip] +flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca +cmov pat pse36 mmx fxsr sse +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Notice the <B>sse</B> at the end of the line - this tells you that this +processor will be able to deinterlace correctly.</P> +<P>On an AMD processor, look for "3dnow" in the cpuinfo line; "3dnow" is AMD's +implementation of SSE instructions, so if your processor has 3dnow you +shouldn't have any issues with deinterlacing.</P> +<H3>Video Filters</H3> + +<P>MythTV provides a means of employing video filters while recording and +during playback. These filters can be used to improve or modify the video +image, including hiding the effects of an interlaced image or reducing the +impact of noise in a poor video signal. The following is a brief +introduction to introduce you to the filters that are available in MythTV +version 0.20 and higher.</P> +<H3>Applying filters</H3> + +<P>One or more filters can be included in a "filter chain". The filters to +be used are identified in a "filter string". A filter string is a group of +filter names and parameters separated by commas. To include parameters, the +filter name is followed by "=" and the parameter information. There should +be no spaces in the filter string. Here is an example filter string:</P> +<P>With parameters: <CODE>kerneldeint=10:1,denoise3d=12</CODE></P> +<P>Without: <CODE>kerneldeint,denoise3d</CODE></P> +<P>Recording filters are set for each individual channel. These may be used +when encoding in software (MPEG-4, RTjpeg) but do not apply when using a +capture card with hardware encoding such as those supported by the ivtv +driver, DVB, HDTV or MJPEG cards. You can run MythTV's "setup" program and +select the "Channel Editor". On the first page for each channel, you can +enter a filter string in the box titled "Video filters". If you are running +"mythweb" on your web server, you can click on "Settings" then "Channels" +and enter filter strings in the "videofilters" column.</P> +<P>Playback filters are per-host and apply to any recording you watch from the +frontend where filters have been applied. Playback filtering can only +work with software decoding so the viaslice, xvmc, and ivtv outputs ignore +filters entirely. From "mythfrontend" go to Setup->TV Settings->Playback. +Enter your filter string in the box titled "Custom Filters".</P> + +<H3>Currently Available Filters</H3> + +<P>"Deinterlace Playback" checkbox.</P> +<P>This implements special behavior needed for the "bobdeint" filter but can +also be used to choose any of the deinterlace filters. If you prefer, you +may leave this unchecked and include any of the deinterlace filters, other +than "bobdeint", in your custom filter chain.</P> +<P>o The "invert" filter</P> +<P>Invert ignores any parameters and inverts the pixel values of the video +frames. In other words, a negative image. This would rarely be useful but +may be a good example to verify that your filter strings take effect.</P> +<P>o The "linearblend" filter</P> +<P>It is a simple deinterlacing filter that ignores parameters and works by +blending adjacent lines. It replaces combing in interlaced video with a +less distracting "ghost" image.</P> +<P>o The "bobdeint" filter</P> +<P>This filter splits the interlaced image into two separate fields that +can be line doubled then displayed at twice the frame rate. If the +display is at the same refresh rate as the recording (59.92Hz NTSC or +50Hz PAL) this will cause each refresh to show objects in motion in +a new position with no jagged edges. However, if the display is not +synchronous, it will cause flickering or the appearance of the picture +moving up and down by one line.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: This filter requires the frame rate to be doubled +and therefore can only be used with the "Deinterlace Playback" checkbox. +Do not include this in your filter chain.</CAPTION> +</FIGURE> +</P> +<P>o The "kerneldeint" filter</P> +<P>Kerneldeint is a more complex deinterlacing filter which applies a filter +kernel using input from several lines. It generally removes combing without +a "ghost" image, sometimes leaving a faint outline of the image from the +other field. It is considered to be less distracting to watch than +linearblend or no filter at all. It accepts one or two integer parameters +separated by a colon.</P> +<P>The first parameter is the filter threshold and defaults to 12. Adjacent +lines differing by more than the threshold value are filtered. The second +option defaults to 0. If set to a non-zero value, it will cause the filter +to skip chroma, and filter only the luminance. It may be useful on some +capture cards which do not capture the chroma fields of interlaced video +correctly.</P> +<P>o The "onefield" filter</P> +<P>This is a simple one-field deinterlacing filter that uses only one field of +the interlaced video. By default it keeps the top field, though passing the +parameter "bottom" will cause it to keep the bottom field instead.</P> +<P>This filter is primarily useful for those who display 1080i HDTV signals +with a video mode that has 540 pixels vertically. The advantage over other +deinterlacing filters is that scenes with motion never show combing or +ghosting.</P> +<P>o The "adjust" filter</P> +<P>This filter adjusts the digital values for luma and chroma to ensure that +they will fall within the ranges specified in the ITU-R601 standard. By +default, this corrects a known problem for the luma range used by bt8x8 +chips which causes video to look washed out. If parameters are passed, there +need to be exactly six. However, passing a single parameter of "-1" will +disable the filter.</P> +<P>1: luma minimum input value (int) +2: luma maximum input value (int) +3: luma gamma correction (float) +4: chroma minimum input value (int) +5: chroma maximum input value (int) +6: chroma gamma correction (float)</P> +<P>The default bt8x8 correction values are equivalent to +"16:253:1.0:2:253:1.0". Output ranges are fixed at ITU-R601 values (16-235 +luma, 16-240 chroma).</P> +<P><B>NOTE</B>: If it is not already specified in the filter chain, this +filter will be automatically applied when recording with the "bttv" driver.</P> +<P>o The "quickdnr" filter</P> +<P>A fast temporal denoiser. This can take 1, 2 or 4 parameters, each being a +value from "0" for the least filtering to "255" for the greatest filtering. +With one parameter, the filter will compute the values it should use for all +of its variables. Two parameters will set the filter strength for luma and +chroma independently. If you are interested in how the algorithm works, you +may examine the source code to see how four parameter are used.</P> +<P>o The "denoise3d" filter</P> +<P>A slower denoiser that applies a spatial and temporal low-pass filter. The +spatial filter can remove some noise that quickdnr can't, but a more +powerful CPU is needed. This filter accepts 3 float parameters:</P> +<P> +<UL> +<LI>luma spatial filter strength</LI> +<LI>chroma spatial filter strength</LI> +<LI>luma temporal filter strength</LI> +</UL> +</P> +<P>Reasonable defaults will be selected for omitted parameters. The chroma +temporal filter strength is calculated from the other filter strengths.</P> +<P>o The "crop" filter</P> +<P>Covers edges of video with black bars. This helps improve video quality +when the edges of the frame are distorted. By default, this removes 16 +pixels from each edge. This can optionally take four parameters representing +top:left:bottom:right. The number times 16 is the number of pixels to remove +so, for example, the default is "=1:1:1:1".</P> +<P>o The "forceyv12" and "forceyuv422p" filters</P> +<P>These force the filter manager to use the given format. You can use one of +these at the head of a filter chain to change the capture format. The most +likely use would be forceyuv422p to use YUV422P capture on cards with known +chroma interlacing problems with YV12.</P> +<P>There are some filters included in the MythTV source code that should +not be used:</P> +<P>o The "forcergb24" and "forceargb32" filters</P> +<P>The two RGB formats should not be used because there is no conversion filter +for them yet.</P> +<P>o The "convert" filter</P> +<P>It exists but don't use it. The filter manager uses this filter +automatically when it is unable to match the input/output formats of two +adjacent filters.</P> +<P>o The "postprocess" filter</P> +<P>While this exists in MythTV source code, it is currently not recommended for +use.</P> + +<H3>Usage Considerations</H3> + +<P>There are trade-offs to consider when deciding if it would be wise to use +a filter. Any processing will modify the original image so you should assess +if the filter has made a noticeable improvement to the picture in order to +justify the impact of the processing. Adding any filter will inherently +increase CPU usage. The impact can vary dramatically depending on your CPU +type and speed, the resolution of the recording, which filters you are using +and other factors. You can only determine what is right for you through +experimentation. However, as a starting point, here are some filter strings +that you may find useful:</P> +<P>For typical broadcast stations: "kerneldeint,quickdnr"</P> +<P>For stations with poor signal quality: "linearblend,denoise3d=12"</P> +<P>For synchronous TV-out: check Deinterlace with "Bob (2x framerate)"</P> + +<H2><A NAME="Recording"></A> <A NAME="ss10.5">10.5</A> <A HREF="mythtv-HOWTO.html#toc10.5">Recording </A> +</H2> + +<P>Depending on your capture card, MythTV offers different video encoders. +The following types of hardware encoding cards are supported: +<UL> +<LI>MJPEG - Zoran-based cards; see +<A HREF="http://mjpeg.sourceforge.net">http://mjpeg.sourceforge.net</A></LI> +<LI>MPEG-2 - iTVC15/16 based cards (Hauppauge PVR-250/PVR-350); see +<A HREF="http://ivtvdriver.org">http://ivtvdriver.org</A> </LI> +<LI>HDTV - pcHDTV cards; see +<A HREF="http://pchdtv.com">http://pchdtv.com</A> and +the Air2PC-ATSC-PCI see +<A HREF="http://www.cyberestore.com/product_info.php?cPath=28&products_id=103">http://www.cyberestore.com/product_info.php?cPath=28&products_id=103</A></LI> +<LI>DVB - cards supporting DVB; see +<A HREF="http://linuxtv.org">http://linuxtv.org</A></LI> +</UL> + +For cards without hardware encoding capabilities (all cards supported by +V4L not listed above), Myth includes two methods for software encoding: +RTjpeg and MPEG-4. RTjpeg has significantly fewer CPU demands than MPEG-4, +but it generates larger files than MPEG-4 for a given recording.</P> +<P>For DVB and HDTV cards, no further configuration is required after +setting up the card using the 'mythtv-setup' program. +For all other cards, configuration is done through MythFrontend. +Selecting 'Recording Profiles' from the 'TV Settings' screen will list +the profiles currently available for the cards in your system. +Depending on what types of cards you have installed you may see: +<BLOCKQUOTE><CODE> +<PRE> +(Create new profile group) +Software Encoders +Hardware MPEG Encoders +Hardware MJPEG Encoders +Transcoders +</PRE> +</CODE></BLOCKQUOTE> + +The '(Create new profile group)' option will allow you to create custom +profiles in case you have multiple backends. Note that custom profiles +are per backend and card type. If you have 2 MPEG-2 encoders in a given +backend system, creating a custom profile will affect both of them. This +option should not be needed otherwise.</P> +<P>The 'Transcoders' group is a little different from the others. Selecting +this group will result in a menu with the following options: 'RTjpeg/MPEG-4' +and 'MPEG-2'. These types indicate what transcoder options will be used for +a given input type (i.e. the 'MPEG-2' settings would be used to transcode +MPEG-2 files into MPEG-4. The source of the MPEG-2 stream (DVB, HDTV, or +PVR-x50) does not matter. Configuration of the options is the same as below +(although any resolution settings will be ignored).</P> +<P>Selecting any of the other options will show a new screen with a list of +four profiles: +<UL> +<LI>Default</LI> +<LI>Live TV</LI> +<LI>Low Quality</LI> +<LI>High Quality</LI> +</UL> +</P> +<P>The Default profile will be used for any recording which does not otherwise +have a specific profile assigned. The 'Live TV' profile will be used when +watching TV. The remaining two profiles are available for customizing to +allow for more precise control over what quality is used for a given +program.</P> +<P>Selecting a profile will allow you to adjust the relevant options for that +card. The most significant setting is the recording resolution, but you can +also choose encoding format, audio format, and tweak other encoder specific +properties.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: although the width and height can be changed to almost +anything, if you start MythTV and don't see video or you get "segmentation +fault" errors, it is likely that the video4linux (v4l) subsystem did not +like the height and width parameters specified. It's best to leave the +default as-is until you're sure that MythTV is operational.</CAPTION> +</FIGURE> +</P> +<P>See the +<A HREF="mythtv-HOWTO-23.html#capture_resolution_">What capture resolution should I use? How does video work?</A> section for more information.</P> + +<H2><A NAME="ss10.6">10.6</A> <A HREF="mythtv-HOWTO.html#toc10.6">Xbox Frontends</A> +</H2> + +<P>MythTV is able to control the LED on the Xbox to indicate backend +recording status. </P> +<P>To control the LED, you will need the <B>blink</B> program from the +xbox-linux project, which is installed as <CODE>/bin/led</CODE> on GentooX. On +Xebian (the new Ed's Debian) you must install it yourself. On other +distributions it may or may not be installed as a program called +<B>blink</B> and should be located in your path. (Type <CODE>which +blink</CODE> to see if the program is available.) If you do not have +<B>blink</B>, you may obtain it from the Xbox-Linux project site at +<A HREF="http://xbox-linux.sf.net/">http://xbox-linux.sf.net/</A>. The +program you need is part of the <CODE>eds_i2c_staff</CODE> module in CVS. Note +the spelling.</P> +<P>Once you have installed <B>blink</B> you will need to set permissions. +<B>blink</B> needs write permission to the i2c device to function +properly. There are three methods to accomplish this. First, you could run +<CODE>mythfrontend</CODE> as root, which is the simplest method, but could +potentially be a security risk. Next, you may make the <B>blink</B> +binary setuid root, which allows non-privileged users to run a program with +root capability. This is done by typing the command: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# chmod u+s /path/to/blink +</PRE> +</CODE></BLOCKQUOTE> + +The final technique would be to set the <CODE>/dev/i2c/0</CODE> device read/write +for all users, but this is the least preferred method.</P> +<P>Now it's time to setup MythTV for Xbox hardware. Enter Setup -> General. +On the second page check the 'Enable Xbox Hardware' option. Upon reentering +the settings, you should have a new option named 'Xbox'. Within this option +you may select the distribution, LED colors for recording and the update +interval. If you select GentooX as the distribution <B>led</B> will be +used as the <B>blink</B> binary name, otherwise, <B>blink</B> is used. +Colors should be self explanatory. The update interval determines how often +the frontend should poll the backend to determine if the status has changed.</P> + +<HR> +<A HREF="mythtv-HOWTO-11.html">Next</A> +<A HREF="mythtv-HOWTO-9.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc10">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-11.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-11.html new file mode 100644 index 0000000..696189f --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-11.html @@ -0,0 +1,626 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: Using MythTV.</TITLE> + <LINK HREF="mythtv-HOWTO-12.html" REL=next> + <LINK HREF="mythtv-HOWTO-10.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc11" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-12.html">Next</A> +<A HREF="mythtv-HOWTO-10.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc11">Contents</A> +<HR> +<H2><A NAME="s11">11.</A> <A HREF="mythtv-HOWTO.html#toc11">Using MythTV.</A></H2> + +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE to Red Hat/Fedora 4 users</B>: Red Hat Linux and Fedora Core ship +with Gnome as the default desktop environment. However, Gnome seems to have +issues with window focus and window switching which sometimes cause +mythfrontend to obscure the video. KDE does not seem to have any such +issues. Therefore you will need to switch to KDE by selecting +RedHatMenu>Extras>System Settings>Desktop Switching Tool and choose "KDE". +<B>NOTE to Fedora Core 5 and 6 users</B>: Fedora 5 and 6 no longer have +this tool in the Menu. Use "switchdesk KDE" from a command line. Read "man +switchdesk" for further information about changing to other desktop +environments.</CAPTION> +</FIGURE> +</P> +<H2><A NAME="ss11.1">11.1</A> <A HREF="mythtv-HOWTO.html#toc11.1">Keyboard commands</A> +</H2> + +<P>The <CODE>keys.txt</CODE> file describes what the various keyboard commands are. +If you have loaded mythweb, you may change the default keys to your liking.</P> +<H3>mythfrontend</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Arrow keys </TD><TD> used to move the highlight point around </TD></TR><TR><TD> +ALT-F4 </TD><TD> exit out of the application </TD></TR><TR><TD> +Space/Enter </TD><TD> take action on the item under the highlight point </TD></TR><TR><TD> +P </TD><TD> play in both "Watch a Recording" and "Delete a Recording" </TD></TR><TR><TD> +D </TD><TD> delete in both "Watch a Recording" and "Delete a Recording" </TD></TR><TR><TD> +U </TD><TD> to view details for the currently selected show on the Watch or Delete screens, EPG, "Program Finder", "Fix Scheduling Conflicts" and search results screens </TD></TR><TR><TD> +O </TD><TD> to list the upcoming episodes for the currently selected show on the EPG, "Program Finder", "Program Recording Priorities", "Fix Scheduling Conflicts" or search results screens </TD></TR><TR><TD> +I </TD><TD> edit recording options from the EPG, "Program Finder", "Program Recording Priorities", or "Fix Scheduling Conflicts" screens. From the Playback and Delete screens, 'I' presents options for recorded shows such as Auto Expire or Stop Recording. Pressing 'I' while on the Recording Options screen will take you to the Advanced Recording Options screen. +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Watching TV or a recording</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Up or down </TD><TD> keys change the channel </TD></TR><TR><TD> +num pad </TD><TD> Type a number to enter a channel number or jump amount (HHMM format) </TD></TR><TR><TD> +P </TD><TD> pause / play. You may also add an explicit keybinding for 'Play' through MythWeb, returning you to normal speed if you are in slow motion, rewind fast forward or pause mode. </TD></TR><TR><TD> +C </TD><TD> change inputs on TV Tuner card </TD></TR><TR><TD> +ESC </TD><TD> quits </TD></TR><TR><TD> +I </TD><TD> puts the On-screen Display up again. During playback, 'I' toggles between position and show description info. If a jump amount is entered, jump to that position. </TD></TR><TR><TD> +M </TD><TD> brings up the electronic program guide (Grid) -- see the EPG section </TD></TR><TR><TD> +Page Up </TD><TD> jump back the configured number of minutes (default is 10) </TD></TR><TR><TD> +Page Down </TD><TD> jump ahead the configured number of minutes (default is 10) </TD></TR><TR><TD> +End or Z </TD><TD> skip to next commercial break marker </TD></TR><TR><TD> +Home or Q </TD><TD> skip back to previous commercial break marker </TD></TR><TR><TD> +T </TD><TD> toggle close caption support Pressing 0-9 (preferably 3 times) + T changes teletext page and turns on teletext. </TD></TR><TR><TD> +F </TD><TD> rotate between the various Picture Adjustments (Colour, Hue, etc.) While Picture Adjustment is on-screen, use Left and Right arrows to adjust. These settings adjust the look of the video playback, and are independent of the G-key settings used at record-time. </TD></TR><TR><TD> +[ or F10 </TD><TD> decrease volume </TD></TR><TR><TD> +] or F11 </TD><TD> increase volume </TD></TR><TR><TD> +| or F9 </TD><TD> toggle mute </TD></TR><TR><TD> +/ </TD><TD> jump to the next "favorite" channel </TD></TR><TR><TD> +? </TD><TD> mark/unmark the current channel as a "favorite" </TD></TR><TR><TD> +U </TD><TD> increase the play speed </TD></TR><TR><TD> +J </TD><TD> decrease the play speed </TD></TR><TR><TD> +A </TD><TD> Adjust time stretch (speed up or slow down normal play of audio and video </TD></TR><TR><TD> +W </TD><TD> cycle through zoom and fill modes: 4:3 aspect ratio, 16:9, 4:3 Zoom (like Pan and Scan), 16:9 Zoom, and 16:9 Stretch (eliminates black sidebars in TV signal) </TD></TR><TR><TD> +F8 </TD><TD> toggle the sleep timer 30m->1hr->1hr30m->2hr->Off </TD></TR><TR><TD> +CTRL-B </TD><TD> Jump to the beginning of the recording / ringbuffer </TD></TR><TR><TD> ++ </TD><TD> Switch between audio streams </TD></TR><TR><TD> +Left </TD><TD> (if a jump amount is entered) to jump back that amount </TD></TR><TR><TD> +Right </TD><TD> (if a jump amount is entered) to jump ahead that amount </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> <B>Without the stickykeys option selected</B> </TD></TR><TR><TD> +Left </TD><TD> rewind the configured number of seconds (default is 5) </TD></TR><TR><TD> +Right </TD><TD> fast forward the configured number of seconds (default is 30) </TD></TR><TR><TD> +< </TD><TD> starts rewind mode as if stickykeys are selected </TD></TR><TR><TD> +> </TD><TD> starts fast forward mode as if stickykeys are selected </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> <B>With Stickykeys option selected</B> </TD></TR><TR><TD> +Right </TD><TD> starts fast forward mode </TD></TR><TR><TD> +Left </TD><TD> starts rewind mode </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> <B>In fast forward or rewind mode:</B> </TD></TR><TR><TD> +Left/Right </TD><TD> increases the ff/rew speed </TD></TR><TR><TD> +0 </TD><TD> plays at normal speed, but leaves the time indicator on screen </TD></TR><TR><TD> +1 or 2 </TD><TD> plays back more slowly than normal ff/rew speed (1 is slowest) </TD></TR><TR><TD> +3 </TD><TD> plays back at normal ff/rew speed </TD></TR><TR><TD> +4-9 </TD><TD> plays back faster than normal ff/rew speed (9 is fastest) </TD></TR><TR><TD> +Space </TD><TD> exits fast forward or rewind mode </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> <B>While video is paused:</B> </TD></TR><TR><TD> +Left </TD><TD> rewind 1 frame </TD></TR><TR><TD> +< </TD><TD> rewind 1 second </TD></TR><TR><TD> +Right </TD><TD> advance 1 frame </TD></TR><TR><TD> +> </TD><TD> advance 1 second +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Watching TV only</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +G </TD><TD> rotate between the various Picture Adjustments (Colour, Hue, etc.) for recording. These values affect the look of the resulting .nuv file, and are independent of the playback picture settings. While Picture Adjustment is on-screen, use Left and Right arrows to adjust. </TD></TR><TR><TD> +H </TD><TD> Channel history. Each repeat steps back through the previous channels. </TD></TR><TR><TD> +O </TD><TD> Turns on 'Browse' mode, allowing user to browse channels and program info while watching current show FullScreen. </TD></TR><TR><TD> +Y </TD><TD> switch between multiple capture cards. <B>NOTE</B>: you will lose your LiveTV buffer on your current card. Useful for different-sourced cards (such as Dish Network on one, HDTV over-the-air on another card.) </TD></TR><TR><TD> +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>LiveTV Browse Mode</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Left </TD><TD> browse program prior to current listed program </TD></TR><TR><TD> +Right </TD><TD> browse program following current listed program </TD></TR><TR><TD> +Up </TD><TD> browse program on channel above current listed channel/program </TD></TR><TR><TD> +Down </TD><TD> browse program on channel below current listed channel/program </TD></TR><TR><TD> +/ </TD><TD> browse program on next favorite channel </TD></TR><TR><TD> +0-9 </TD><TD> enter a channel number to browse </TD></TR><TR><TD> +Space/Enter </TD><TD> change channel to channel of current listed program </TD></TR><TR><TD> +R/r </TD><TD> Toggle recording of current program (cycles through types) </TD></TR><TR><TD> +ESC/O </TD><TD> Exit Browse mode +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Playback Recording Zoom Mode</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Left </TD><TD> Move video to Left </TD></TR><TR><TD> +Right </TD><TD> Move video to Right </TD></TR><TR><TD> +Up </TD><TD> Move video Up </TD></TR><TR><TD> +Down </TD><TD> Move video Down </TD></TR><TR><TD> +PageUp </TD><TD> Zoom In </TD></TR><TR><TD> +PageDown </TD><TD> Zoom Out </TD></TR><TR><TD> +Space/Enter </TD><TD> Exit Zoom mode leaving picture at current size and position </TD></TR><TR><TD> +ESC </TD><TD> Exit Zoom mode and return to original size +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>If you have two or more tuner cards</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +V </TD><TD> toggle Picture-in-picture on or off </TD></TR><TR><TD> +B </TD><TD> toggles the window focus (lets you change channels on the PiP window) </TD></TR><TR><TD> +N </TD><TD> swaps the two channels by changing channels on both cards +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Watching a recording only</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Space/Enter </TD><TD> set a bookmark at that point. Next time you start the recording, you will automatically jump forward to this point and clear the bookmark. </TD></TR><TR><TD> +X </TD><TD> queues the current recording for transcoding </TD></TR><TR><TD> +O </TD><TD> brings up menu to allow toggling settings such as Commercial Auto-Skip, Auto-Expire, etc. </TD></TR><TR><TD> +D </TD><TD> exits the current recording and displays the Delete menu </TD></TR><TR><TD> +E or M </TD><TD> enters/exits edit mode. </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> <B>In edit mode</B> </TD></TR><TR><TD> +Left/Right </TD><TD> move forward and backward </TD></TR><TR><TD> +Up/Down </TD><TD> alter the amount of time you jump forward and backward. Increments are: nearest cutpoint, nearest video keyframe, 1 frame, 0.5 seconds, 1 second, 20 seconds, 1 minute, 5 minutes, and 10 minutes. </TD></TR><TR><TD> +PageUp/PageDown </TD><TD> move forward and backward to the nearest cut point </TD></TR><TR><TD> +< or > </TD><TD> move forward or backward by 10 times the normal jump amount </TD></TR><TR><TD> +Space/Enter </TD><TD> allows you to set or delete a cut point </TD></TR><TR><TD> +Z </TD><TD> loads the commercial skip list (if one exists) into the cutlist </TD></TR><TR><TD> +C or Q </TD><TD> clear all cut points in the cutlist </TD></TR><TR><TD> +I </TD><TD> Inverts the cutlist +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>EPG</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Arrows </TD><TD> are used to move the highlighted program point around </TD></TR><TR><TD> +A, D, S, W </TD><TD> perform the same as left, right, down and up </TD></TR><TR><TD> +PageUp/PageDown </TD><TD> move the channel list up or down a page </TD></TR><TR><TD> +Home/End </TD><TD> move the highlight left or right by one day </TD></TR><TR><TD> +Ctrl+Left or < </TD><TD> move the highlight left by one page </TD></TR><TR><TD> +Ctrl+Right or > </TD><TD> move the highlight right by one page </TD></TR><TR><TD> +9, 3, 7, 1 </TD><TD> (like a numeric keypad) perform the same as PageUp, PageDown, Home and End </TD></TR><TR><TD> +I </TD><TD> bring up more information about a show, and allow you to schedule a recording. If you select "Record this showing" while watching Live TV you can "Instant Record" a program. </TD></TR><TR><TD> +Space/Enter </TD><TD> allow you resolve conflicts or change overrides. If the program is not already scheduled to record, it will instead act like pressing 'I'. </TD></TR><TR><TD> +M </TD><TD> when on a channel will change to that channel </TD></TR><TR><TD> +ESC or C </TD><TD> exits without changing the channel </TD></TR><TR><TD> +R </TD><TD> change the current item from Recording/Not-Recording. Successive keypresses cycle through the scheduled recording type list. </TD></TR><TR><TD> +X </TD><TD> change the channel to the currently selected channel without leaving the EPG (Most useful in the alternate EPG) </TD></TR><TR><TD> +? </TD><TD> mark/unmark the current channel as a "favorite" </TD></TR><TR><TD> +/ or 4 </TD><TD> toggle the guide listing between all channels and filtered "favorites" +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Setting Program or Channel Recording Priorities</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Right </TD><TD> increases priority value </TD></TR><TR><TD> +Left </TD><TD> decreases priority value </TD></TR><TR><TD> +1 </TD><TD> sorts by title </TD></TR><TR><TD> +2 </TD><TD> sorts by priority </TD></TR><TR><TD> +Home/End </TD><TD> toggle sort priority </TD></TR><TR><TD> +I </TD><TD> edit recording options </TD></TR><TR><TD> +ESC </TD><TD> commits changes and exits +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Viewing Scheduled Recordings/Resolving Conflicts</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +1 </TD><TD> show all recordings </TD></TR><TR><TD> +2 </TD><TD> show only important recordings </TD></TR><TR><TD> +Home/End </TD><TD> toggle show showing all/important </TD></TR><TR><TD> +I </TD><TD> edit recording options </TD></TR><TR><TD> +Space/Enter </TD><TD> resolve conflict or override +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Viewing Search Listings</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Home </TD><TD> change to the previous view if applicable </TD></TR><TR><TD> +End </TD><TD> change to the next view if applicable </TD></TR><TR><TD> +M </TD><TD> select another view if applicable. In the title and description search popup, press M again to edit or delete the selected view. +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Recording Profiles Setup Screen</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +D </TD><TD> on a custom profile group displays a popup to delete the group</TD></TR><TR><TD> +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Recording Groups</H3> + +<P>In the Watch Recordings screen, Recording Groups allow you to separate +programs into user-defined categories, such as "Kids", "Alice", "Bob", etc. +This can be used to reduce clutter, or to segregate content if you use the +PIN function. +<BR><CENTER> +<TABLE BORDER><TR><TD> +M </TD><TD> change the view or to set a group password </TD></TR><TR><TD> +I </TD><TD> move a program from one Recording Group to another +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Watch Recordings Screen</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +1 or F1 </TD><TD> Meaning of the icons </TD></TR><TR><TD> +/ </TD><TD> Tags a recording. Tagged recordings can be played either in order or shuffled and deleted as a group. You can also change the recording group for several recordings at once by tagging them and using the Menu (m) button, selecting "Playlist options", then "Change Recording Group". </TD></TR><TR><TD> +? </TD><TD> Clear the tagged list. +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Remote Controls</H3> + +<P>If you are using MythTV with just a remote control then it is suggested that you +map the remote control keys as described below. Your remote control may not +have the same set of keys as those named below, the names are only a suggestion +that roughly correspond to the function.</P> +<P>If you are adding new key bindings to the program then consideration of this +suggested list will help users with remote controls.</P> +<P>This list assumes a minimal remote control that only has 20 keys, nearly all +features can be used with this configuration. If you have more keys then you +can access all of the features. With only 16 keys most features are usable. +<BR><CENTER> +<TABLE BORDER><TR><TD> +REMOTE CONTROL </TD><TD> LIRC KEYSTROKE </TD><TD> FUNCTION </TD></TR><TR><TD> +0 - 9 </TD><TD> 0 - 9 </TD><TD> channel selection, EPG navigation, ff/rew speed setting (with stickykeys) </TD></TR><TR><TD> +Left Arrow </TD><TD> Left </TD><TD> scroll left, rewind </TD></TR><TR><TD> +Right Arrow </TD><TD> Right </TD><TD> scroll right, fast forward </TD></TR><TR><TD> +Up Arrow </TD><TD> Up </TD><TD> scroll up, channel change up </TD></TR><TR><TD> +Down Arrow </TD><TD> Down </TD><TD> scroll down, channel change down </TD></TR><TR><TD> +Select / OK / Play </TD><TD> Space </TD><TD> Select item, play (with stickykeys) set bookmark </TD></TR><TR><TD> +Cancel </TD><TD> Escape </TD><TD> Cancel, quit playback </TD></TR><TR><TD> +Menu </TD><TD> m </TD><TD> EPG (from watching TV) edit (from playback). </TD></TR><TR><TD> +Pause </TD><TD> p </TD><TD> Pause </TD></TR><TR><TD> +Other key 1 </TD><TD> i </TD><TD> Information </TD></TR><TR><TD> +Other key 2 </TD><TD> c </TD><TD> Change tuner card input +</TD></TR></TABLE> +</CENTER><BR> +</P> + +<H2><A NAME="ss11.2">11.2</A> <A HREF="mythtv-HOWTO.html#toc11.2">Using themes with MythTV</A> +</H2> + +<P>MythTV is "themeable", meaning that the visual appearance of the program +can be modified by the user without re-compiling or altering the program +functionality. Download the MythThemes tarball from the website and untar it:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xjf myththemes-0.21.tar.bz2 +$ cd ~/myththemes-0.21 +$ qmake myththemes.pro +$ su - +# make install +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The theme will now be available in the mythfrontend Appearance section.</P> + +<H2><A NAME="ss11.3">11.3</A> <A HREF="mythtv-HOWTO.html#toc11.3">Adding DishTV information to the database</A> +</H2> + +<P>A script for adding Pay Per View information into the MythTV database for +DishTV subscribers is available at +<A HREF="http://www.mythppv.com/">http://www.mythppv.com/</A>.</P> + +<H2><A NAME="ss11.4">11.4</A> <A HREF="mythtv-HOWTO.html#toc11.4">Adding support for an external tuner</A> +</H2> + +<P>MythTV supports changing the channel on an external tuner. If you have +an external tuner, such as a DirecTV or digital cable set top box, you +should add <CODE>/usr/local/bin/changechannel</CODE> to your Input Connections in the +mythbackend configuration GUI.</P> +<P>However, there is not <B>changechannel</B> program per-se, because this is +going to be dependent on what sort of external tuner you have. Look in the +<CODE>contrib/channel_changers</CODE> directory for a number of programs and +scripts which may be used to change channels. Once you find one which +works, copy it to <CODE>/usr/local/bin/changechannel</CODE>.</P> +<P>Feel free to browse some of what sort of hardware is available at +<A HREF="http://store.snapstream.com/accessories.html">http://store.snapstream.com/accessories.html</A>, or if you wish to +assemble your own, rather than purchase, the following may be helpful: +<A HREF="http://www.dtvcontrol.com/">http://www.dtvcontrol.com/</A> for +cable pinouts.</P> + +<H2><A NAME="ss11.5">11.5</A> <A HREF="mythtv-HOWTO.html#toc11.5">Using Shutdown/Wakeup</A> +</H2> + +<P>What does the MythTV Shutdown/Wakeup function do? The scheduler on the +Master backend (MBE) keeps track of the idle status of the entire MythTV +system, including the Slave backends (SBE). If it considers the system to be +idle, and thus ready to shutdown, it sets the wakeuptime to the time of the +next recording and then proceeds to shut down all Slave backends and then +itself. Once it is time to begin recording, the Master backend and the Slave +Backends are automatically woken up. This system allows MythTV to record +like a normal VCR, thereby conserving power when not in active use.</P> +<P>In order to use the Shutdown/Wakeup function there must be some method of +waking up the Master backend. There are any number of solutions, but we +will discuss in detail two possibilities:</P> +<P> +<UL> +<LI>Use another server that runs 24/7 and have it send a WakeOnLAN (WOL) +packet to wake the Master backend. This assumes that you have the WOL tools +installed, and that your Master backend motherboard supports WOL.</LI> +<LI>Use your motherboard's BIOS wakeup capability. You'll need a motherboard +that supports BIOS wakeup, and some tools. Two that work are: +<A HREF="http://sourceforge.net/projects/nvram-wakeup">http://sourceforge.net/projects/nvram-wakeup</A> and +<A HREF="http://www.malloc.de/tools/wakeup_clock.html">http://www.malloc.de/tools/wakeup_clock.html</A></LI> +</UL> +</P> + +<H3>A deeper look into the operation</H3> + +<P>The scheduler keeps track of the idle status of the MythTV system. To +determine whether or not the MythTV system is idle, the following conditions +must be met for a period of time defined in the "Idle timeout (secs)" +parameter. +<UL> +<LI>no client is connected to the server</LI> +<LI>no recording (neither LiveTV nor a regular recording) is currently taking place</LI> +<LI>no recording starts within a definable amount of time ("Max. wait for recording (min)")</LI> +<LI>the "pre Shutdown check-command" returns 0 </LI> +</UL> +</P> +<P>If we get to this idle state the Master backend will set the wakeuptime using the "Set +wakeuptime command", which is the same for WOL and BIOS wakeup. The Master backend will +then shut down the Slave backends and itself using the "Server halt command".</P> +<P>One caveat is that the scheduler tries to guess if the Master backend was started by a +wakeup call or by the user. If it thinks it was woken up by a user, it +blocks shutdown until a client connects to the Master backend, after which it will +behave as described above. To disable this feature, unset "Block shutdown +before client connected" in the mythfrontend Setup->Setup->General screen.</P> +<P>Once it is time to startup the system, the Master backend is woken up first and will +wakeup the Slave backends using the "Wake command for slaves". At this time, there is +no support for starting only the required Slave backend, so all Slave backends will startup.</P> + +<H3>Setting up the MythTV side of this extension.</H3> + +<P>There are a number of options that are used to control the Shutdown / +Wakeup feature.</P> +<P>Shutdown/Wakeup Options: +<UL> +<LI>"Idle timeout (secs)" is the time the server waits while idle until a +shutdown occurs.</LI> +<LI>"Max. wait for recording (min)" is the time the Master backend waits for a recording +without shutting down. For example, this would be used to prevent a 10 +minute system shutdown if a recording is set to start 15 minutes from now.</LI> +<LI>"Startup before rec. (secs)" Sets how long before a programmed +recording the MythTV system will be woken up. This should be roughly be the +time your systems need to bootup, and if you have Slave backends, you'll +need to ensure this value is long enough for all your machines to perform +their bootup cycle.</LI> +<LI>"Wakeup time format" is the format of the wakeup time that is given in +the "Set wakeuptime command" as a parameter "$time". You need to set this +according to your wakeup mechanism. If you need seconds since the epoch +(1970-01-01) set the "Wakeup time format" to "time_t".</LI> +<LI>"Set wakeuptime command" is the command executed to set the new wakeuptime. </LI> +<LI>"Server Halt Command" is the command executed to shutdown the Master +backend and the Slave backends.</LI> +<LI>"pre Shutdown check-command" is used to give a +"Go/NO-GO" decision from a non-MythTV source. This command is executed +immediately before the shutdown would occur. The return value is use to make +the following choices: +<UL> +<LI>If it returns a "0" the shutdown will occur as scheduled.</LI> +<LI>If it returns a "1" the "idle timeout" will be reset and the system +waits again for the timeout.</LI> +<LI>If it returns a "2" the entire shutdown sequence is reset. This means +that a new client connect is needed before a shutdown occurs, unless you have +the "Wait for client connect" setting disabled, in which case this is the same as +returning "1". An example of a use for this return value is to prevent the shutdown +if a user is currently logged in, or if a specific program (i.e. transcode, +automatic updates, etc.) is currently running. If you don't need it, leave +the field blank.</LI> +</UL> +</LI> +</UL> +</P> +<P>The "WakeOnLan settings": +These settings have nothing to do with using BIOS or WOL wakeup, they are +the same for both. +<UL> +<LI>"Master backend" This setting defines timings for the frontends to +wakeup the Master backend using WOL. Useful if your frontend can emit a WOL +packet so you don't need to physically go to the Master backend if you're +trying to watch TV.</LI> +<LI>"Reconnect wait time (secs)" is the time the frontend waits after +executing the "Wake command" before attempting to retry the connection. This +should be roughly the amount of time your Master backend needs for bootup. +Set to "0" to disable. The frontends will retry to connect for "Count of +reconnect tries" times before giving up.</LI> +<LI>"Wake command for slaves" is the <EM>one</EM> command executed to wake +your Slave backends. This should be a script that contains the calls to +wakeup all Slave backend systems.</LI> +</UL> +</P> + +<H3>Using WOL to wake your Master backend. </H3> + +<P>To use WOL to wake your Master backend you will need a WOL capable Master +backend, a machine that runs 24/7 which can execute an at-job and nc (netcat) +on the Master backend. I use some little bash scripts to make my DSL router +wakeup my mythbox if required.</P> +<P>Replace $SERVER and $PORT with your own settings! +On my Master backend I have a script that gets called as 'setwakeuptime command' which +looks like the following: +<BLOCKQUOTE><CODE> +<PRE> +#! /bin/sh +echo $@ | nc $SERVER $PORT +</PRE> +</CODE></BLOCKQUOTE> + +This simply cats the parameters (that is $time) to my 24/7 server. On my +$SERVER I have (x)inetd listening on $PORT starting a little script which +cares about setting the at-job. The following additions are necessary on the +$SERVER:</P> +<P>If you use <B>inetd</B>:</P> +<P>In <CODE>/etc/inetd.conf</CODE> add: +<BLOCKQUOTE><CODE> +<PRE> +mythwake stream tcp nowait mythtv /usr/sbin/tcpd /usr/local/bin/mythwake +</PRE> +</CODE></BLOCKQUOTE> + +If you use <B>xinetd</B>, save the following as <B>mythwake</B> in your +<CODE>/etc/xinet.d/</CODE> directory: +<BLOCKQUOTE><CODE> +<PRE> +service mythwake + { + socket_type = stream + wait = no + user = mythtv + protocol = tcp + id = mythwake + server = /usr/local/bin/mythwake + } +</PRE> +</CODE></BLOCKQUOTE> + +and add the following to <CODE>/etc/services</CODE>: +<BLOCKQUOTE><CODE> +<PRE> +mythwake $PORT/tcp +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Finally, <CODE>/usr/local/bin/mythwake</CODE> looks like: +<BLOCKQUOTE><CODE> +<PRE> +#! /bin/bash +#this should be a command to wake your server +WAKECMD="#!/bin/sh\n /usr/local/bin/wakeMBE" +#first we need to delete all wake jobs in queue +for JOB in atq | cut -f 1 ; do + atrm $JOB; +done +#now we read the date from 'nc' +read date; +#now set the atjob +echo -e "$WAKECMD" | at $date ; +</PRE> +</CODE></BLOCKQUOTE> + +<B>SECURITY WARNING</B>: +Be sure to secure $SERVER:$PORT from untrusted networks, because this +allows 3rd parties to run arbitrary code on your server!</P> + +<H3>Using BIOS wakeup to wake your Master backend.</H3> + +<P>Since I don't use this, I cannot say much about this. If your motherboard +supports any wakeup tool you have to call that tool as "Set wakeuptime +command" with the "Wakeup time format" suitable for that tool.</P> +<H3>Wakeup the MySQL server using WOL</H3> + +<P>If your MySQL server and your Master backend are not on the same machine, +you can have the Master backend wake your MySQL server using WOL. You will +find the settings for this in the second page of the mythtv-setup program, +or at the end of <CODE>mysql.txt</CODE>. The meanings are the same as +discussed in "The WakeOnLan settings" above.</P> + +<H3>Tips/Tricks:</H3> + +<P>If, for example, one of the Slave backends is also your desktop computer, +you could simply use a little script as 'server halt command' which first +calls <CODE>/sbin/shutdown -t TIMEOUT</CODE> where TIMEOUT is a value sufficient +for you to react. You could then popup a window using *dialog, asking for +permission to shutdown. If you cancel the shutdown, simply call +<CODE>/sbin/shutdown -c</CODE>.</P> +<P>If you get "nvram-wakeup: /dev/rtc: Device or resource busy" your +set-wakeuptime-script should stop the program that uses <CODE>/dev/rtc</CODE> before +setting the wakeuptime.</P> +<H2><A NAME="ss11.6">11.6</A> <A HREF="mythtv-HOWTO.html#toc11.6">Controlling the mythfrontend via telnet</A> +</H2> + +<P>To use this feature you must first enable it in Settings>General>General</P> +<P>The network control listens on port 6546, as demonstrated below:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ telnet basement 6546 +Connected to basement. +Escape character is '^]'. +MythFrontend Network Control +Type 'help' for usage information +--------------------------------- +# help +Valid Commands: +--------------- +jump - Jump to a specified location in Myth +key - Send a keypress to the program +play - Playback related commands +query - Queries +exit - Exit Network Control + +Type 'help COMMANDNAME' for help on any specific command. + +# help jump +Usage: jump JUMPPOINT + +Where JUMPPOINT is one of the following: +channelpriorities - Channel Recording Priorities +channelrecpriority - Channel Recording Priorities +deletebox - TV Recording Deletion +deleterecordings - TV Recording Deletion +guidegrid - Program Guide +livetv - Live TV +livetvinguide - Live TV In Guide +mainmenu - Main Menu +...snip... +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Please note that this feature only allows one connection at a time, so any +new connections will automatically terminate prior ones.</P> + +<HR> +<A HREF="mythtv-HOWTO-12.html">Next</A> +<A HREF="mythtv-HOWTO-10.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc11">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-12.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-12.html new file mode 100644 index 0000000..f9cf96e --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-12.html @@ -0,0 +1,1112 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: Scheduling Recordings.</TITLE> + <LINK HREF="mythtv-HOWTO-13.html" REL=next> + <LINK HREF="mythtv-HOWTO-11.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc12" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-13.html">Next</A> +<A HREF="mythtv-HOWTO-11.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc12">Contents</A> +<HR> +<H2><A NAME="s12">12.</A> <A HREF="mythtv-HOWTO.html#toc12">Scheduling Recordings.</A></H2> + +<P>The MythTV master backend is responsible for managing the schedule for +all TV tuner cards on the master and any slave. Its job is to search the TV +listing for the shows you have requested and assign recordings to the TV +tuner cards. If none of the shows that you've chosen overlap, it simply +records all of them. However, if there are shows where the beginning +and end times overlap, the scheduler follows rules that you've specified or +makes logical decisions about what would be best if you haven't expressed your +preference. Further, the "Upcoming Recordings" page allows you make specific +decisions about what you really do and don't want to record.</P> + +<H2><A NAME="ss12.1">12.1</A> <A HREF="mythtv-HOWTO.html#toc12.1">Record Types</A> +</H2> + +<P>When you choose a show that you would like to record from the +Options Page, there are eight different types of rules to help the +scheduler find which showings you would like to record.</P> +<P> +<UL> +<LI>Single Record -- record only this title at this specific time and +this station. This is the best way to be sure that a certain showing will +be recorded. However, if the TV listings change and the show is not broadcast +at that time, the show will not be recorded but will be marked as Not Listed +to let you know that you should investigate. +</LI> +<LI>Find One -- this will record a title once from any of the times +that appear in the TV listings. This is useful for recording a movie +or special that has multiple showings because it allows the scheduler +to choose one that doesn't conflict. It is not a good choice for +recording a single episode of a series because it records the first +available showing of the title without regard to the episode +information. +</LI> +<LI>Record Weekly -- this records a show whenever the title is listed +on the same channel, weekday and time. Note that if the TV station +changes the schedule for a special episode, it would not be +recorded. However, you can add a Single record for the special +episode. If there are no matching showings in the TV listings, +a Not Listed item will be added to your schedule for the next +time slot to let you know that you should investigate. +</LI> +<LI>Find Weekly -- this will record a title once per week from any +of the times that appear in the TV listings beginning from the time of +the showing that was selected when the rule was set. This is useful +for news, current events or other programs where the same episode is +shown several times each week but the listings may not include +descriptive information. This may not be a good choice if there are +different episodes shown during the week. +</LI> +<LI>Record Daily -- this records a show whenever the title is listed +for the time and station on any day of the week. Here again, a show +will not be recorded if the time was altered by the station. If there +are no matching showings in the TV listings, a Not Listed item will be +added to your schedule for the next time slot to let you know that you +should investigate. +</LI> +<LI>Find Daily -- this will record a title once per day from any +of the times that appear in the TV listings beginning from the time of +the showing that was selected when the rule was set. This is useful +for news, current events or other programs where the same episode is +shown several times each day but the listings may not include +descriptive information. This may not be a good choice if there are +different episodes shown during the day. +</LI> +<LI>Channel Record -- records one showing of each unique episode from +any of the times the title is listed on this station. This is perhaps +the most common rule to use for most shows. +</LI> +<LI>Record All -- records one showing of each unique episode from +any of the times this title is listed on any channel. This can be +useful if a station has sister stations where shows are rebroadcast +allowing the scheduler to record rebroadcasts on the other station +when the original airing cannot be recorded.</LI> +</UL> +</P> + +<H2><A NAME="ss12.2">12.2</A> <A HREF="mythtv-HOWTO.html#toc12.2">Scheduling Options</A> +</H2> + +<H3>Priority</H3> + +<P>By default, all shows you select have equal value to the +scheduler. There are a set of rules to make good choices when +two or more shows are in conflict. However, priority values let the +scheduler know what you prefer so that it can set the schedule based +on your preferences.</P> +<P>Initially, recording rule priority values are set to zero. You may choose +to leave everything at "0" and let the scheduler follow rules to guess +what you might prefer when there are conflicts. However, if you have +one or two favorite shows, you may want to increase the priority +value so the scheduler will know that you would prefer recording +these over other shows. You might use certain values to rate shows +so that all favorites are 2. good shows are 1 and extra 'filler' +shows are all -1 for example. You could sort each title on the "Set +Priorities" page to have a unique value so the scheduler can know +which show you'd prefer versus any other show. The choice and style +are entirely up to you. However, the more information you give to +the scheduler, the more likely it will make the choices you would +prefer in the first place.</P> +<P>The scheduler choices are based on the total priority for a showing by +adding up all priority factors that match the showing. By default, most +of these factors are "0" but you may use any combination to express your +likes and needs.</P> +<P> +<UL> +<LI>Per record rule -- this is the "priority" selection in the "Scheduling +Options" section of the options page and this value is included for any +showings that match the recording rule. You may choose to only use these +values and not use the other factors for the sake of simplicity and clarity.</LI> +<LI>Per record type -- Setup->TV Settings->Recording Priorities->General allows +you to add to the priority based on the type. It may make sense to increase +the value for "Single" so that by default they have an extra advantage over +other shows. The default is +1. You may want to decrease the value for Find +rules so that they will be less likely to interfere with regularly scheduled +shows and will be more likely to record in a non-conflicting time instead. +The default is -1.</LI> +<LI>Per channel -- Setup->TV Settings->Recording Priorities->Channel Priorities +can be useful if you believe that you prefer any of the shows on certain +channels. This would give all shows on a channel an advantage by default.</LI> +<LI>Input priority -- in the "mythtv-setup" program, the "Input Connections" +section allows you to add additional priority in the "Input priority". +This is simply another priority factor but has an interesting effect. If a +card input has a higher value than the other cards, the scheduler will see +that you would rather record showings of episodes on this input rather than a +showing on other inputs. If you have multiple cards of different quality, +you may want to set input priority to encourage the scheduler to record +shows on your best card(s) whenever possible. This can also be useful if you +have multiple video sources which include the same stations. For example, +with digital and analog cable you could increase the digital cable input +preference by 1 to tell the scheduler that you want to record from the +digital channel whenever possible but the channel on the analog input could +still be used when the digital input is busy.</LI> +<LI>Custom Priority -- this allows you to add any specialized factors you +would like in order to influence scheduling decisions. See the +<A HREF="#Custom Priority">Custom Priority</A> section below.</LI> +</UL> + +For any single showing of any show you've chosen to record, these factors +are added together to find the "total priority". This is the priority that +the scheduler uses to decide which showings are given the first choice when +filling in the schedule.</P> +<P>The scheduling priority of a show may also be used to determine +auto-expiration of recordings when disk space gets full (see +<A HREF="#Auto-Expire">Auto-Expire</A>, below).</P> + +<H3>Duplicates</H3> + +<P>Singles will record without regard to duplicate matching.</P> + +<P>The standard recurring methods of All, Channel, Weekly and Daily use the +descriptive information in the TV listings to try to record only one showing +of each unique episode. However, This goal is sometimes complicated by the +fact that the stations may not include a description for a specific episode +but use a generic description for the series instead. When there is a +generic description, the default behavior is to assume that it may be an +episode that you have not seen and to record it for you. One of the +duplicate matching options is "Record new episodes only". If this is +selected, listing that have an original air date of more than 14 days +earlier are considered repeats and are not eligible to record. Generally, +generic episodes will be marked as repeats also.</P> + +<P>Because of generic episodes and other situations, MythTV offers an +alternative approach where shows may be recorded by choosing from multiple +showings even when the descriptive information is not reliable. All of the +"Find" record types look for matching titles in the listings. If there is a +showing with specific episode information and that episode has recorded +before, that showing is marked as previously or currently recorded. The +scheduler will then choose to record the earliest non-conflicting showing +from any of other remaining showings regardless of the descriptive +information. Generally, Find One is most useful for movies or specials and +the Find Daily and Find Weekly rules are best for news or current events +shows that are repeated. However, these may be useful in other situations +where the standard recording rules may not work correctly.</P> + +<H3>Conflicts</H3> + +<P>As you add more shows that you would like to record, the scheduler +will eventually encounter conflicts. If there are two shows at the +same time and you have two or more TV tuner cards, both shows will +record. However, if there are more shows than cards, the scheduler +will have to decide what it thinks it should not record based on the +information you have given. If you see an unexpected situation you +are not "stuck" with the scheduler's choice. You can still tell the +scheduler exactly which shows you do want to record and/or don't +want to record in any situation.</P> + +<H3>Scheduling decisions</H3> + +<P>Here are the actual decisions made by the scheduler as it fills in the +schedule.</P> +<P> +<UL> +<LI>Currently recording beats not currently recording -- A recording +in progress can not be moved to another input or time so it "wins" +its current timeslot. +</LI> +<LI>Single, Daily, or Weekly rules with no match are marked Not Listed -- +If these or Overrides do not match the current listings because the +listings have changed, they are added to the schedule and marked to +indicate that they will not record. +</LI> +<LI>Rules that could record beat rules that can not record a showing -- +If two rules match the same showing of a program, a rule marked as inactive +or a showing marked as a repeat, for example, yield to the other rule. +</LI> +<LI>More specific record type is used in place of less specific -- If +two rules match the same showing of a program, preference is given to +Don't Record then Override, Single, Find One, Record Weekly, Find Weekly, +Record Daily, Find Daily, Channel and finally All. +</LI> +<LI>Higher total priority beats lower total priority -- This is the +core of the scheduling process. Episodes of the highest priority show +are placed on the first available input followed by the next highest +priority show and so on. +</LI> +<LI>Future start time beats past start time -- If there is an +episode in progress and also a later showing of the same episode, it +is better to record the complete episode. If there isn't another +showing, it will start recording immediately to record the remaining +portion. This should only happen if you add a new rule while the show +is in progress or if the master backend is started after the start time +of a scheduled show. +</LI> +<LI>More specific record type beats less specific record type -- If +two shows are on at the same time and have the same total priority but +different types they will be sorted by Single then Find One, Record +Weekly, Find Weekly, Record Daily, Find Daily, Channel and finally +All. This only applies if the priorities are the same. +</LI> +<LI>If both start times have passed, later start time beats earlier start +time -- This attempts to miss the least amount of time. +</LI> +<LI>If neither start time has passed, earlier start time beats later +start time -- This helps assure that the earliest showing of an episode +has the advantage. +</LI> +<LI>Lower input id beats higher input id -- The scheduler fills in +open time slots on the first available input for the video source. The +next input is used when there is another show already placed for the +card of the first input. +</LI> +<LI>Older record rule beats newer record rule -- If two shows are still +equal after all of these other checks, the show whose record rule was added +first is preferred over a more recent addition. +</LI> +<LI>Postpone showings to resolve conflicts -- If Reschedule Higher +Priorities is set or if a conflict has the same priority as a show +that was scheduled at the same time, the scheduler will check to see +if a scheduled show can be moved to another input or later matching +showing without creating a new conflict so that the conflicting show +can be scheduled to record. +</LI> +</UL> +</P> + +<H3>Reschedule Higher Priorities</H3> + +<P>Setup->TV Settings->Recording Priorities->General has a checkbox for +"Reschedule Higher Priorities" which tells the scheduler to try to be a +little smarter in certain situations. If this is checked, the scheduler will +look for situations where a show cannot record because all inputs for the +channel are used for higher priority shows. It will check to see if any of +the other shows could be recorded at another time so that the conflicting +show can be recorded in its place.</P> +<P>Generally, this is a good strategy but there are tradeoffs. If a higher +priority show is postponed, you will not get to watch it until it is +recorded in the later timeslot. There is also a risk that the TV listings +may change and the later showing may go away. In this rare case the higher +priority show may never record. On the other hand, if you do not use this +option you will miss recording some lower priority shows unnecessarily +unless you manually make similar changes.</P> +<P>By using Reschedule Higher Priorities, the scheduler will do a better job of +recording as many of your shows as possible when left unattended. It will +also be easy to see that shows have been marked to record at a later time. +You can then decide for yourself when you would prefer to record the first +showing by clicking "Record anyway".</P> + +<H3>Controlling Your Schedule</H3> + +<P>The Manage Recordings->Upcoming Recordings page is your control center +for the MythTV scheduler. Unlike other DVR systems, this one page gives you +all of the information and tools you need to see all of your alternatives +and make whatever adjustments you desire.</P> +<P>The upper half of the screen has a scrollable box listing items that match +your record rules sorted by time. The lower half shows the details for the +highlighted item. There are two 'views' available. Press "1" to include all +of the items that match record rules even if they do not need to be +recorded. Press "2" to focus on just the things that will record and items +that may need your attention. The message in the upper right-hand corner +will remind you when there are conflicts that would prevent one or more +shows from being recorded.</P> +<P>The items in the list are colored in the record color for things that +will record, white for things that may need attention, gray for those +that do not need to record and yellow when there is a time conflict. +Items at the top of the list may also be highlighted indicating that the +recording is in progress.</P> +<P>Along with the channels, start times and titles, the right-hand column has +a status code. Numbers indicate which card number has been assigned to +record the show. Letters are used to indicate the reason that something +will not be recorded. Just below the box is a short status message for the +highlighted item that indicates the type of record rule that was matched, +the "total priority" for this showing and a one or two word explanation of +the status code. If you press SELECT, you will see more information about +the status.</P> +<P>There are a few status codes that may require your attention. "C" indicates +that there are more overlapping shows to record than there are TV tuners to +record them. "L" indicates that the scheduler found that it may be better to +record a later showing of this episode. These states happen as a result of +your choices and should normally reflect your preferences. However, you may +notice situations where you would like to modify the scheduler's initial +choices.</P> +<P>The first thing you can do is to highlight an item and press INFO to +see the recording options page. From this page you can change the +record rule type, the duplicate matching rules, or raise or lower the +priority to resolve whatever problem you noticed.</P> +<P>Additionally, you can treat any individual showing as an exception that you +do want to record or don't want to record. To use these "override" features, +highlight the item and press SELECT. You will see a message explaining the +current status and at least an "OK" button to exit without making changes.</P> +<P>For items scheduled to record, there will be a button for "Don't record" +which will prevent recording this showing but will still allow the same +episode to record in the future. If there is episode description +information, you may also see a button for "Never record". This prevents +recording this showing and tells MythTV to remember that this is an episode +that you've seen or don't need to see if it is ever in the TV listings +again.</P> +<P>For items that are not scheduled to record, the message will describe the +reason and in the case of "C" or "L" it will include a list of the shows +that are scheduled to record instead. For any item that could potentially be +recorded there will be buttons for "Edit Options" and "Add Override". "Edit +Options" will allow you to change the options for the existing record rule +such as raising the priority so that the show will record. These changes +would apply to this and all future showings that match this record rule. +"Add Override" will allow you to set options that apply to the specific +showing without affecting the recurring record rule.</P> +<P>If you return to an override page after an override has already been set, +you will also see a "Clear Override" to undo your changes. This option makes +it very easy to try out some "what if" attempts when deciding on your best +strategy in a difficult situation.</P> +<P>For a recording in progress, there will be a "Change Ending Time" button. +This will take you to the options page for a Single or Override or create +an Override if it is a recurring rule. Here you can go to the Recording +Options section to change the program end time offset. If you extend the +end time so that it overlaps upcoming recordings, the schedule will change +to accommodate the new end time. This may cause a conflict or later showing +even for a show with higher priority. Therefore, it is a good idea to +check your schedule after changing the end time of a recording in +progress.</P> + +<H2><A NAME="ss12.3">12.3</A> <A HREF="mythtv-HOWTO.html#toc12.3">Storage Options</A> +</H2> + +<H3>Recording Profile</H3> + +<P>Each recording rule can be configured with a different recording +profile. For example, colorful cinematography can be configured with a +"High Quality" profile, while 'talking heads' interviews shows can be +configured with a "Low Quality" profile. These recording profiles need to +be configured before using them (see +<A HREF="mythtv-HOWTO-10.html#Recording">Recording</A>, +above).</P> + +<H3><A NAME="Recording Group"></A> Recording Group </H3> + +<P>For organization of the "Watch Recordings" screen and the MythWeb +interface, recordings can be assigned into "recording groups".</P> + +<H3><A HREF="mythtv-HOWTO-9.html#storagegroups">Storage Groups</A></H3> + +<P>This allows you to select any special "Storage Groups" you may have +created to determine where recordings from this rule should be stored +on your disks. The "Default" storage group is always available.</P> + +<H3><A NAME="Playback Group"></A> Playback Group </H3> + +<P>This selects a set of pre-configured playback parameters which can be +created and edited in Setup->TV Settings->Playback Groups. When the +recording is played, the values from this playback group will be +used. This allows you to choose a default time stretch value, skip and +jump amounts appropriate for this type of television program.</P> + +<H3><A NAME="Auto-Expire"></A> Auto-Expire </H3> + +<P>MythTV will "autoexpire" old recordings to make room for new recordings +when disk space gets filled up. This option can be set to "Don't allow +auto expire" to prevent these recordings from being automatically deleted +when disk space fills up.</P> + +<P>The default setting is for all scheduled recordings to be eligible +for auto-expiration; this can be changed in the Settings->TV +Settings->General page by manipulating the "Auto Expire Default" +checkbox.</P> + +<P>The default auto-expire policy is "Oldest Show First"; the oldest +recordings are deleted first. The "Lowest Priority First" method +chooses to expire the lowest-priority recordings first.</P> + +<H3>Episode Limit</H3> + +<P>An episode limit can also be configured to limit the maximum number +of episodes recorded of a single series, to restrict that series' disk +usage. If this is set, you can further decide what to do when this +limit is reached; either stop recording that series, or to delete the +oldest episodes in favor of the new ones.</P> + +<H2><A NAME="ss12.4">12.4</A> <A HREF="mythtv-HOWTO.html#toc12.4">Post Recording Processing</A> +</H2> + +<H3>Commercial Flagging</H3> + +<P>Select whether or not to automatically flag commercials for these +recordings. Commercial Flagging parameters can be set in +Setup->TV Settings->General.</P> + +<H3>Transcoding</H3> + +<P>Select whether or not to automatically transcode recordings to save +disk space. Before using this, you must first enable auto-transcode in +the recording profile and configure the transcoding parameters; see +<A HREF="mythtv-HOWTO-10.html#Recording">Recording</A>, above.</P> + +<H3>User Jobs</H3> + +<P>User Jobs allow you to configure up to 4 custom commands to run on +recordings. They can be configured in mythtv-setup. The following +tokens have special meaning when used in the User Job commands:</P> +<P> +<UL> +<LI>%DIR% - the directory component of the recording's filename</LI> +<LI>%FILE% - the filename component of the recording's filename</LI> +<LI>%TITLE% - the title of the recording (e.g., name of the series)</LI> +<LI>%SUBTITLE% - the subtitle of the recording (e.g., name of the +episode)</LI> +<LI>%DESCRIPTION% - description text for the recording (from guide +data)</LI> +<LI>%HOSTNAME% - the backend making the recording</LI> +<LI>%CATEGORY% - the category of the recording (from guide data)</LI> +<LI>%RECGROUP% - the +<A HREF="#Recording Group">recording group</A></LI> +<LI>%CHANID% - the MythTV channel ID making the recording</LI> +<LI>%STARTTIME% - the recording start time (YYYYMMDDhhmmss)</LI> +<LI>%ENDTIME% - the recording end time (YYYYMMDDhhmmss)</LI> +<LI>%STARTTIMEISO% - the recording start time in ISO 8601 format +(YYYY-MM-DDTHH:MM:SS)</LI> +<LI>%ENDTIMEISO% - the recording end time in ISO 8601 format</LI> +<LI>%PROGSTART% - the recording's start time (from guide data; +YYYYMMDDhhmmss)</LI> +<LI>%PROGEND% - the recording's end time (from guide data)</LI> +<LI>%PROGSTARTISO%, %PROGENDISO% - the recording's start and end +time in ISO 8601 format.</LI> +</UL> +</P> + +<H2><A NAME="ss12.5">12.5</A> <A HREF="mythtv-HOWTO.html#toc12.5">Advanced Recording Options</A> +</H2> + +<H3>Creating Power Search rules with Custom Record</H3> + +<P>MythTV's "Custom Record" feature gives you unlimited control for creating +specialized search recording rules to meet your needs. It allows you to +choose your criteria to search for matching shows based on any of the +information in the program listings, channel information, time functions and +more. This goes beyond the capabilities of any other DVR system and it is +unlikely that this level of scheduling customization will ever be available +in any commercial DVR system.</P> + +<H3>Getting Started</H3> + +<P>Go to Schedule Recordings->Custom Record. This page, helps you build a +database search one clause at a time. Each added clause further limits +which showings will be matched in the TV listings. You can test the +search at any time and when you are done, you can save your search as a +recording rule.</P> +<P>To familiarize yourself with how you can create custom rules, create a +simple rule to record "Nova" only in primetime.</P> +<P>The first item at the top of the page allows you to edit an existing rule +or create a new rule. Leave it on "<New rule>". Arrow down to the +third item which says "Match an exact title". Right and left arrows would +allow you to select any of several prefabricated pieces or full examples +but leave it on the default for now. Arrow down to "Add this example +clause" and press SELECT (Enter or Space on a keyboard). The large text +box should now show: +<BLOCKQUOTE><CODE> +<PRE> + program.title = 'Nova' +</PRE> +</CODE></BLOCKQUOTE> + +As you have probably guessed, this says that we want to search for all +programs with the title "Nova" regardless of the time, day, channel, etc.</P> +<P>If you do not receive a PBS station that carries "Nova" or would like to use +another title, edit the title by pressing the down arrow to highlight the +text box and right arrow over the the word "Nova". If you are using a +keyboard you can simply delete the four letters and type a different title +between the quotes. With a remote control, you can do 'cell phone' style +text entry with the number pad. The delete key is the "X" in the grouping +for "1", zero is grouped with "9" and "0" acts as the "Caps Lock" key. You +can press ENTER in the text box to popup a virtual keyboard.</P> +<P>Note: the text box honors many familiar Emacs control keys. It is also +possible to cut and paste text into the text box so you can edit with a +favorite editor or insert a rule sent in email or from other sources.</P> +<P>In any case, choose a title that is shown both in primetime and late night +or daytime. Next, click the "Test" button. You should see a list of the +upcoming episodes for "Nova" just as if you had clicked the Upcoming +button for "Nova" elsewhere in MythTV.</P> +<P>Press ESC to go back to the Custom Record page. Move to the example +selector then press the right or left arrows until you find "Only in +primetime". Click "Add this example clause". You should now see: +<BLOCKQUOTE><CODE> +<PRE> + program.title = 'Nova' + AND HOUR(program.starttime) >= 19 + AND HOUR(program.starttime) < 23 +</PRE> +</CODE></BLOCKQUOTE> + +Click "Test". You should now see a shorter list with only the showings that +begin between 7PM and 11PM. To create a rule for this, press ESC to go back +to the custom page and move to "Rule Name:" then type "Nova" or anything +else you would like. This is only a label and will not affect the search +results. Once a name has been entered, the "Record" button will light up. +Click this to enter the recording options page. If you named it "Nova" the +title will say "Nova (Power Search)". Set whatever options you would like +then click "Save these settings". You now have a special rule to record +"Nova" but only when it is shown in primetime.</P> +<P>You can make further modifications to this rule by returning to the Custom +Record page then press the right or left arrow keys on "Edit Rule:" until +you find "Nova". You can experiment and test but the saved rule will not +be updated until you click "Record" then "Save these settings".</P> +<P>To remove this, or any other rule, you can go to the "Recording Priorities" +page, arrow down to the title, press Enter and change the the recording type +to "Do not record this program" then "Save these settings".</P> + +<H3>How it Works</H3> + +<P>MythTV stores TV program information in a database and uses the Structured +Query Language (SQL) to access the data. Information about each TV program +is stored in the 'program' table and information about each TV station you +receive is stored in 'channel'. These two tables are used in the scheduler +queries and their columns are available to be used in your rules. The rules +you create are stored in 'record'.</P> +<P>Normal rules in MythTV simply match the title in the rule with the titles +in the 'program' table. MythTV also has search rules for "Titles", +"Keywords" and "People". These store the key phrase in the description +column of the rule and includes them in specialized SQL replacements for +the normal title check. There is also a type called "Power Search" which +takes the raw SQL in the description as the replacement for title +matching.</P> +<P>Custom Record is a tool to help you build valid SQL for Power Search rules. +You do not need to be a SQL expert to use Custom Record because the +examples are known to work correctly and are usually self-explanatory so you +can choose the pieces you need then modify them. Many powerful solutions to +unique problems are possible by combining the examples. With some creativity +and some knowledge of SQL, the possibilities are limitless.</P> + +<H3>Common Tricks and Tips</H3> + +<P>The example clauses marked "complete example" are actual rules that have +been used to address specific problems. You may find that some of these +are useful for you as-is or with slight modifications. These show off how +powerful custom rules can be but there are also several simple idioms that +you may find useful for many of the shows you would like to record.</P> +<P>Wait for a known title -- If there is a movie that you anticipate will be +televised in the coming months but is not yet in the listings, you can +select "Match an exact title", edit the movie title, click "Record" then +choose "Record one showing of this title". The rule will wait weeks, months +or years until this title shows up in your listings then it will record one +showing. These rules have no impact on the scheduler throughout the day and +only take a tiny fraction of a second when the master backend starts or when +the listings are updated.</P> +<P>Silence series out of season -- "Celebrity Poker Showdown", for example, +will have new episodes for a while then long periods where reruns are shown +dozens of times per week. By checking the previously shown flag you can +create a rule that will only match new episodes. Therefore, your schedule +won't be polluted with dozens of entries marked as "Repeat" or "Previously +Recorded". +<BLOCKQUOTE><CODE> +<PRE> + program.title = "Celebrity Poker Showdown" + AND program.previouslyshown = 0 +</PRE> +</CODE></BLOCKQUOTE> + +This allows you to keep rules for your favorite shows that are dormant while +out of season but will spring back to life when new episodes appear.</P> +<P>Choose showings on certain days -- Several cable stations will show their +highest rated shows a dozen on more times per week. However, the scheduler +only needs two or three choices to do a good job of making a flexible +choice. +<BLOCKQUOTE><CODE> +<PRE> + program.title LIKE "Celebrity Fit Club%" + AND DAYNAME(program.starttime) = "Sunday" +</PRE> +</CODE></BLOCKQUOTE> + +This says to choose any showing of an episode that hasn't been recorded +when it appears on Sunday. This prevents all the other showings during the +week from being listed in the schedule.</P> +<P>Notice the word "LIKE" and the "%" at the end. This does wildcard matching +so that this would match even if the title ended with "2". "III" or +":Revenge of the Snapple Lady". This can be useful where the title may +change from one season to the next like "Survivor: %", "Big Brother%" or +"The Amazing Race%".</P> + +<H3>Working with SQL</H3> + +<P>As you experiment, it is possible that you may misplace a quote or mistype a +word. If there is a mistake when you press "Test" or "Record" you will see +an error message returned from the database. This will usually give you a +good idea about what needs to be fixed. However, for more subtle MySQL +syntax errors, you can find more information in the documentation at +<A HREF="http://dev.mysql.com/doc/mysql/en/">http://dev.mysql.com/doc/mysql/en/</A>. This contains a lot of +information that can be useful for Power Search rules such as the "Date and +Time Functions". There are many other good resources for SQL on the Web.</P> +<P>While the example clauses demonstrate how to use many of the data columns, +you can get a more complete list of all the columns that are available by +using a MySQL client program: +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u mythtv -pmythtv mythconverg +mysql> describe program; +mysql> describe channel; +</PRE> +</CODE></BLOCKQUOTE> + +This will show the names of all of the columns along with their type and +default value. Most are easy to understand but a few need some explanation +in order to use them effectively with Power Search. +<UL> +<LI>"program.category_type" holds one of these exact four strings: "movie", +"series", "sports" or "tvshow". +</LI> +<LI>"program.airdate" is a string representing the year of release for +movies and may have no meaning for other types of shows. +</LI> +<LI>"program.stars" is a floating point number from 0.0 to 1.0. On a +four star scale, 1.0 would be four stars, 0.75 would be three stars and so +on. +</LI> +<LI>"program.originalairdate" if provided is the date when a show +was, or will be, first televised. This may be useful for finding +episodes before or after a certain date such as finding just the +original series of "Battlestar Galactica". +</LI> +<LI>"program.previouslyshown" is a column created by MythTV to try to +determine if a showing is more than 14 days after its original air date or +if the show was marked as a repeat and did not have a date for the first +airing. If this is "0" it usually means that this is a brand new show or a +rebroadcast within the first two weeks. +</LI> +<LI>"program.generic" is a column created by MythTV to try mark +showings for a series where the specific episode information is not +included. When these generic showings appear, it is impossible for the +system to determine if they are repeats of the same episode(s) or if +they are all different episodes. +</LI> +<LI>"program.first" is a column created by MythTV to mark the first +showing in the current listings for each episode, movie or special. +Choosing to match only the "first" showing can be useful for sports +that are brodcast live then repeated. +</LI> +<LI>"program.last" is a column created by MythTV to mark the last +showing in the current listings for each episode, movie or special. +If a showing is marked both "first" and "last" then it is the only +showing of that program in the current TV listings. +</LI> +<LI>"program.programid" is the Tribune Media Service database record +identifier for each program description. In general, these start with a two +letter prefix, MV, EP, SP or SH that correspond to the +"program.category_type". For most, the last four digits are "0000" except +EP where the last four digits are the episode number in the series. Note +that these are generated by TMS and not the show's producers but they are +usually in the same order as the original air dates for the episodes. +</LI> +<LI>"program.videoprop" also "audioprop" and "subtitletypes". +These columns contain bit flags for a variety of attributes that +may be associated with a program. These are filled with information +offered by the TV listings provider. However, your listings source +will not have information for all of the available flags. Therefore, +some of these may not be useful for your search rules. This information +is organized in "sets" and the MySQL function FIND_IN_SET() can be used +to test for any of these flags. For example: +<BLOCKQUOTE><CODE> +<PRE> +FIND_IN_SET('SURROUND', program.audioprop) > 0 +</PRE> +</CODE></BLOCKQUOTE> + +would be true for the programs where the surround sound bit is present. +To see all of the available attribute names: +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u mythtv -pmythtv mythconverg +mysql> SHOW COLUMNS FROM program LIKE '%prop'\G +mysql> SHOW COLUMNS FROM program LIKE 'subtitletypes'\G +</PRE> +</CODE></BLOCKQUOTE> +</LI> +</UL> + +Finally, if you are doing something very experimental and a column is not +giving you the results you had anticipated, you can always check the MythTV +source code to see exactly how a column is used. The open source for MythTV +is available from +<A HREF="http://www.mythtv.org/">http://www.mythtv.org/</A> .</P> + +<H2><A NAME="ss12.6">12.6</A> <A HREF="mythtv-HOWTO.html#toc12.6">Scheduling with more than one Input</A> +</H2> + + +<P>MythTV is designed to allow recording television programs from one or more +service providers, or video source, on one or more video input from each +provider. Some inputs may not be allowed to record at the same time as +each other while others may record simultaneously.</P> +<P>A television station may be broadcast on more than one channel from one +provider or may be available on channels from two or more providers. If a TV +station is available from more than one source, the video quality or type of +broadcast may differ. Therefore, MythTV allows you to control how you would +like the scheduler to select the best channel and input for a show which is +available on more than one input or more than one channel.</P> + +<H3>Mutually Exclusive Inputs</H3> + +<P>A single TV capture card may have video connections to more than +one of its inputs and each input may be from a different service. The card +may only be allowed to record from one of these inputs at one time because +there is only one encoder on the card that actually captures the content.</P> +<P> +<FIGURE> +<EPS FILE="BlockDiagramofavideocapturedevice.eps"> +<IMG SRC="BlockDiagramofavideocapturedevice.png"> +<CAPTION></CAPTION> +</FIGURE> +</P> +<P>These are mutually exclusive meaning that only one input or the other +may record at a given time but not both.</P> +<P>Usually, inputs on different cards can record at the same time +but two or more inputs on the same card cannot. However, there are cases +where inputs on different cards should not be allowed to record at the +same time, for example, a firewire card and s-video analog card connected +to the same set top cable box.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +| +| coax +--------------+ firewire ------------------+ +| .-=|Cable Provider|=------------=| Card 1 input 1 | HDTV +| | |HD/Cable STB |=--. +-----|||||||||||| +| | +--------------+ | s-video ------------------+ +| | `---------=| input 2 | Digital +|wall | coax | Card 2 | +|=---=^=------------------------------=| input 3 | Cable +| +-----|||||||||||| +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Input 1 and input 2 receive content from the same set top box and the +channels can not be tuned independently. Therefore only one of these two +inputs should be used at any given time. The solution is to create an "Input +Group" with <B>mythtv-setup</B> in "Input connections". Including these +two inputs in the same Input Group will tell the scheduler that these are +mutually exclusive and may not record at the same time. Inputs 2 and 3 are +automatically mutually exclusive because they are on the same card so there +is no need to create an Input Group for these inputs.</P> +<P>Cards such as the Hauppauge PVR-500 are able to record as two cards +simultaneously because it has two MPEG-2 encoders and each encoder appears +as a separate device. DVB cards may be allowed to capture content from more +than one channel at a time if the channels are in the same MUX.</P> + +<H3>Stations, Channels and Video Sources</H3> + +<P>Although we may be accustomed to thinking of a broadcast station and its +channel number as being synonymous, stations and channels are very different +things. A "station" is in a building with wires and employees. A "channel" +is a carrier frequency or digital ID that carries a broadcast stream. The +same TV station may be broadcast over different frequencies in different +cities or by different providers in the same city. The same frequency will +carry different stations in different cities. In the digital realm of DVB +and ATSC (HDTV), it is even possible for a single frequency to carry +multiple program streams but each of these streams of content are actually +different channels that the receiving devices can 'tune' to independently.</P> +<P> +<UL> +<LI>Station: building</LI> +<LI>Channel: frequency</LI> +</UL> +</P> +<P>In MythTV, a "video source" is a set of channels from a provider, or over +the air, that can be received by an input. The set defines the channels and +the broadcasters primarily associated with each of those channels. If you +have more than one device or cable from the same provider connected to more +than one card and input, you only need to create one video source in +mythtv-setup then associate that one source with each of these connected +inputs. This will let your MythTV system know that the same channels and +their TV listings are available to be recorded from any of these inputs.</P> +<P>For example. A MythTV system may have two capture cards. Both have a cable +connected to the coaxial connectors. These cables carry the local cable TV +service. In mythtv-setup, the user should create one "Video source" called +"Cable", for example. Under "Input connections", "Cable" should be +associated with each of the two tuner inputs. The scheduler will then know +that any program on one of the channels from the "Cable" source could be +recorded by either card from the card's tuner input.</P> +<P>You need to create a different video source for each provider or service +that has a different set of channels. Each input with a connection to that +service should be associated with the video source for that service so the +system will know which set of channels are available for each of your active +inputs.</P> +<P>Let's say that this user also has one digital cable set top box. The digital +cable service carries channels that are not available over basic cable. The +user would create another source called "Digital". This set top box is +connected to the second card by S-Video so under "Input connections", +"Digital" is associated with the S-Video input of card 2. The system would +then know that programs on channels from the Digital source can only be +recorded from this input. Further, the scheduler understands that it can +only record one show at a time from card 2 so it can assign Cable or Digital +shows to the card but not both at the same time.</P> +<P>Some TV stations may be broadcast over a channel from the Cable source and +also broadcast over a channel from the Digital source. Note that two +channels carrying the same primary station may not have the same TV listings +due to carrying the primary station part time, including local programming +exclusive to one of the channels, the channels may be in different +timezones, etc. Listings information must be associated with each channel +even if two or more channels report that they carry the same station.</P> + +<H3>Order of Inputs</H3> + +<P>By default the scheduler chooses the first (lowest numbered) input which has +a showing of the scheduled program as it fills the schedule. If a lower +priority show is on at the same time as a higher priority show that has been +assigned to input 1, then input 2 will be used next and so on. Therefore, +configure your best card and input first and next best card and input +second. There may be differences in the type or brand of capture card, +signal quality from the cable, system resources such as disk space, CPU, +etc. By configuring your best input first, more recordings, and your highest +priority recordings, will use that input.</P> +<P>A common situation is that a newer and better card is added last. For +example, you may initially setup your system with two analog cable cards and +then add a HDTV card. If NBC is on a cable channel and "The Apprentice" is +shown in HDTV on an NBC HD channel, the scheduler would still prefer analog +inputs 1 and 2 over the new HD input 3.</P> +<P>So, if you'd like the scheduler to prefer a new source, the simplest thing +is to run <B>mythtv-setup</B> and "Delete all capture cards" then enter +your cards and inputs in your preferred order. This will not remove your +sources and channels - you want to keep those and only renumber your cards +and inputs. In this example, once the changes have been made and the Master +Backend is restarted, the scheduler would then choose "The Apprentice" in HD +on the new input 1 and only use the analog inputs (now numbered 2 and 3) +when the HDTV input was occupied with another show.</P> + +<H3>Matching Callsigns</H3> + +<P>If a recording rule is a type that can record from any channel, "The +Apprentice" would match for any channel that shows episodes which may +include CNBC or BRAVO. However, for Single, Timeslot, Weekslot or Channel +rules, "The Apprentice" would only match showings on the selected station as +identified by the "callsign". For example, KVBC is an NBC affiliate on +channel 3. Channel 733 is KVBCDT which is HDTV over cable from the same +station. If a Single record rule was set for "The Apprentice" on KVBC +channel 3, it could not record this showing from KVBCDT on 733. If 733 was +chosen when the rule was saved, channel 3 could not be used to record.</P> +<P>However, the "Channel Editor" in mythtv-setup can be used to change the +Callsign for channel 733 to "KVBC". MythTV would then understand that both +of these channels are from the same broadcast station. Assuming the HDTV +input was input number "1", "The Apprentice" would record on 733. If, +however, this HDTV input already had a higher priority show assigned to it +in that time slot, "The Apprentice" would be assigned to KVBC channel 3 on +input 2.</P> +<P>Having two channels with the same callsign may affect how program +information is shown in mythfrontend. If two sources have the same callsign +and channel number, the program guide and program lists will only show one +instance of the channel number and callsign. If the same callsign is on two +different channel numbers, both will be shown and if two sources have +different callsigns with the same channel number, both of those will be +shown.</P> +<P>Continuing with the example above, the Electronic Program Guide would +include rows for both "3 KVBC" and "733 KVBC". If channel 3 KVBC was also +included in the Digital cable source, the EPG would still include just one +line for "3 KVBC" even though there are two different channels, Cable and +Digital, with this identification. Regardless of how these are displayed and +which "KVBC" channel you select to add a rule to record "The Apprentice", +the scheduler will pick the best channel, source and input to record "The +Apprentice" on "KVBC".</P> + +<H3>Using Priorities to Prefer an Input</H3> + +<P>The fundamental concept to keep in mind is that the MythTV scheduler will +choose the lowest numbered input available when showings have the same +priority. If there are factors that cause two showings of the same show to +have different priorities then the higher priority showing will be +considered before the showings with lower priority.</P> + +<H3>Input Priority</H3> + +<P>"Input Connections" in mythtv-setup includes a box to set "Input priority" +which defaults to "0". If a value is set, that amount will be added to the +"total priority" for showings on that input. This can be used to influence +using favored cards or not using less favored cards unless necessary.</P> +<P>Let's say the "The Apprentice" is on at 8:00pm with a priority of 3. "Who +Cares" is -2 and an episode is shown at 8:00pm then repeated at 11:00pm. The +scheduler would assign "The Apprentice" to card 1 and "Who Cares" to card 2 +at 8:00pm. If the input priority for the input on card 2 was changed to -1, +"Who Cares" would have a total priority of -2 for showings on card 1 and -3 +for showings on card 2. The scheduler would assign "The Apprentice" to card +1 at 8:00pm and "Who Cares" to card 1 at 11:00pm when the better card is +available. If there was another higher priority show at 11pm, the next best +choice for "Who Cares" would be card 2 at 8pm with the priority -3.</P> +<P>Card 1 and 2 have input priority "0":</P> +<P> +<FIGURE> +<EPS FILE="Card1 Pri 0 Card2 Pri 0.eps"> +<IMG SRC="Card1 Pri 0 Card2 Pri 0.png"> +<CAPTION></CAPTION> +</FIGURE> +</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> + Time Title Priority Card Status + 8:00 The Apprentice +3 1 Will Record + 8:00 Who Cares -2 2 Will Record +11:00 Who Cares -2 1 Earlier Showing +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Card 2 with input priority "-1":</P> +<P> +<FIGURE> +<EPS FILE="Card1 Pri 0 Card2 Pri -1.eps"> +<IMG SRC="Card1 Pri 0 Card2 Pri -1.png"> +<CAPTION></CAPTION> +</FIGURE> +</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> + Time Title Priority Card Status + 8:00 The Apprentice +3 1 Will Record + 8:00 Who Cares -3 2 Later Showing +11:00 Who Cares -2 1 Will Record +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Card 2 at "-1" but higher priority shows at both 8 P.M. and 11 P.M.:</P> +<P> +<FIGURE> +<EPS FILE="Card1 Pri 0 Card2 Pri -1-TDS.eps"> +<IMG SRC="Card1 Pri 0 Card2 Pri -1-TDS.png"> +<CAPTION></CAPTION> +</FIGURE> +</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> + Time Title Priority Card Status + 8:00 The Apprentice +3 1 Will Record + 8:00 Who Cares -3 2 Will Record +11:00 The Daily Show +1 1 Will Record +11:00 Who Cares -3 2 Earlier Showing +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Note the two different effects, each of which may be what you desire +depending on circumstance. If input priorities are equal, shows will record +at the earliest time if any input is available. If input priorities differ, +shows may be postponed to a later time in order to record on the best input.</P> + +<H3>Channel Priority</H3> + +<P>Priority can be added for individual channels (remember, frequencies from a +video source, not stations). This can be used to tell the system that you +generally prefer the content of the station on a channel over the formats of +other stations. You may want to raise the priority for ESPN, SciFi, Comedy +Central or lower the priority for CSPAN, CourtTV, etc. If the same station +is on two different channels, you can use channel priority to have the same +effect for these channels as input priority would have for whole inputs.</P> +<P>For example, say CNN is on analog channel 20 and there is an HD CNN on 750. +You may not want to tie up the HD input for news originating in standard +definition. Under TV Settings->Recording Priorities->Channel Priorities you +could set channel 750 to -1. The scheduler would then prefer to record CNN +shows on any analog channel 20 before considering using 750 only when there +are no analog inputs available.</P> + +<H3>Preferred Input</H3> + +<P>For an even finer grain of control, there is a per rule option to specify +which input should be preferred for showings that match the rule. By +default, this adds +2 to the priority for showings on the specified input.</P> +<P>For illustration, let's say there will be a Space Shuttle launch on CNN that +will be broadcast in high definition. Adding a rule to record the launch +with priority "0" should default to channel 20 on input 2. Channel 750 would +have this at -1 due to the channel priority set in the previous example. If +on the recording options page for this rule, the "Scheduling Options" had +the input set to prefer the HD input on card 1, then the showing on channel +750 for this input would be increased in value by +2 for a total of +1 and +would be the best choice for this launch coverage. While this one rule +would prefer the HD input with channel 750, all other rules that match shows +on CNN would still prefer channel 20.</P> +<P>Note that this will not work properly if the preferred input priority does +not out weigh differences in input and channel priorities. The value of the +priority boost when this option is chosen defaults to +2 but can be modified +in TV Settings->Recording Priorities->Set Recording Priorities.</P> + +<H3>HDTV Priority</H3> + +<P>In the preceeding fictious example, the Space Shuttle launch is broadcast in +high definition and a preferred input is selected to give preference to the +HD input. However, TV listings from zap2it.com through the DataDirect +service may allow this to work without having to use this per rule option.</P> +<P>In Settings->Recording Priorities->Set Recording Priorities there is an +option for "HDTV Recording Priority". This value will be added automatically +if the listings for the show have the "hdtv" flag set. DataDirect will set +this flag for shows known to be broadcast in HDTV on HD channels. However, +the flag is not set for standard definition channels. This is another +example of the listings being different for the same station on a different +channel. If the HDTV priority is set to "+2", the shuttle launch would +automatically have a total priority of +1 so that channel 750 would be +preferred over channel 20 for this HDTV broadcast.</P> +<P>Channel "750 CNN" at priority "-1" and HDTV broadcast priority at "+2":</P> +<P> +<FIGURE> +<EPS FILE="Card1 HDTV Card2 Cable.eps"> +<IMG SRC="Card1 HDTV Card2 Cable.png"> +<CAPTION></CAPTION> +</FIGURE> +</P> + +<H3><A NAME="Custom Priority"></A> Custom Priority </H3> + +<P> +<FIGURE> +<EPS FILE="add.eps"> +<IMG SRC="add.png"> +<CAPTION>New for MythTV 0.21</CAPTION> +</FIGURE> +</P> +<P>While Input, Channel, and HDTV Priority can be used for indicating a +preference for certain programs and inputs, there may be circumstances that +cannot be resolved easily with these standard features. MythTV version 0.21 +includes a feature for "power priority". The Custom Priority editor in +mythfrontend's "TV Settings" screen is similar to Custom Record, however, +Custom Priority allows you to create specialized power priority factors to +influence scheduling decisions.</P> +<P>For example, the 'program.closecaptioned' flag can be used in a +similar way as the 'program.hdtv' flag.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +Priority Rule Name: Closed Captioned priority +Priority Value: 2 +program.closecaptioned > 0 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>This will raise the priority of shows marked with "CC" over those that are +not by applying the "Priority Value" whenever the SQL fragment evaluates to +true. If the expression evaluates to false for a showing, the "Priority +Value" is not applied.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +Priority Rule Name: Priority when shown once +Priority Value: 1 +program.first > 0 AND program.last > 0 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The "first" and "last" flags for an episode will only be set for the +same showing when there is only one showing of that episode in the +current TV listings. This rule would raise the priority in these cases +so that these shows would have an advantage to record in their only +available time slot.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +Priority Rule Name: Input 1 signal quality +Priority Value: -1 +cardinput.cardinputid = 1 AND +channel.channum IN (3, 5, 39, 66) +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>A common issue with two or more analog capture cards is that one of +the cards may have more interference on some channels than the same +channels on other cards. This example gives a disadvantage to the +channels in this list but only for the first input. Therefore, a show +on channel 39 would choose input 2 or 3 if possible but for channels +not in this list, input 1 is still the first choice.</P> +<P>The Custom Priority editor includes many example fragments and complete +examples that can be used or you can create your own to suit your needs.</P> + +<HR> +<A HREF="mythtv-HOWTO-13.html">Next</A> +<A HREF="mythtv-HOWTO-11.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc12">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-13.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-13.html new file mode 100644 index 0000000..2f4f192 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-13.html @@ -0,0 +1,106 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: MythPlugins. </TITLE> + <LINK HREF="mythtv-HOWTO-14.html" REL=next> + <LINK HREF="mythtv-HOWTO-12.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc13" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-14.html">Next</A> +<A HREF="mythtv-HOWTO-12.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc13">Contents</A> +<HR> +<H2><A NAME="mythplugins_"></A> <A NAME="s13">13.</A> <A HREF="mythtv-HOWTO.html#toc13">MythPlugins. </A></H2> + +<P>MythTV has a rich set of plugins available. Once you have downloaded +the tarball, untar it and run the <B>configure</B> script:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xjf mythplugins-0.21.tar.bz2 +$ cd mythplugins-0.21 +$ ./configure --help + +Usage: configure [options] +Options: [defaults in brackets after descriptions] +NB: all --enable-* options can be reversed with --disable-* + +Generic options: + --help print this message + --enable-all Enable all options + --enable-opengl enable OpenGL (Music and Gallery) [default=no] + +MythBrowser related options: + --enable-mythbrowser build the mythbrowser plugin [default=yes] + +MythDVD related options: + --enable-mythdvd build the mythdvd plugin [default=yes] + --enable-transcode enable DVD ripping and transcoding [default=no] + --enable-vcd enable VCD playing [default=no] + +MythGallery related options: + --enable-mythgallery build the mythgallery plugin [default=yes] + --enable-exif enable reading of EXIF headers [default=no] + +MythGame related options: + --enable-mythgame build the mythgame plugin [default=yes] + +MythMusic related options: + --enable-mythmusic build the mythmusic plugin [default=yes] + --enable-fftw enable fftw visualizers [default=no] + --enable-sdl use SDL for the synaesthesia output [default=no] + --enable-aac enable AAC/MP4 audio file decompression [default=no] + +MythNews related options: + --enable-mythnews build the mythnews plugin [default=yes] + +MythPhone related options: + --enable-mythphone build the mythphone plugin [default=yes] + --enable-festival enable festival TTS Engine [default=no] + +MythVideo related options: + --enable-mythvideo build the mythvideo plugin [default=yes] + +MythWeather related options: + --enable-mythweather build the mythweather plugin [default=yes] +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The sections detailing configuration of the plugins assume that you are +already in the <CODE>~/mythplugins-0.21/</CODE> directory.</P> +<P>Note that a single <B>configure</B> script now does configuration for all +modules. By default, it will compile all modules. If you do not wish to +compile a module, either because it is of no use to you, or you do not have +the prerequisites, the simplest course of action is to go through the +various sections below, satisfying the prerequisites, and then compile all +modules at once.</P> +<P>For example, you would only like to compile and install MythGallery and +MythMusic. For MythGallery, you would like to use the EXIF data in the .JPG +file to present additional information onscreen. For MythMusic, you would +like to enable support for the opengl and FFT visualizations. The command +line would look like:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-opengl --enable-mythgallery --enable-exif --enable-mythmusic --enable-fft +$ qmake mythplugins.pro +$ make +$ su - +# make install +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>For simplicity, the examples below will disable compilation of all other +modules other than the one being discussed.</P> + +<HR> +<A HREF="mythtv-HOWTO-14.html">Next</A> +<A HREF="mythtv-HOWTO-12.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc13">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-14.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-14.html new file mode 100644 index 0000000..f1ab3cb --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-14.html @@ -0,0 +1,112 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: MythWeb.</TITLE> + <LINK HREF="mythtv-HOWTO-15.html" REL=next> + <LINK HREF="mythtv-HOWTO-13.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc14" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-15.html">Next</A> +<A HREF="mythtv-HOWTO-13.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc14">Contents</A> +<HR> +<H2><A NAME="s14">14.</A> <A HREF="mythtv-HOWTO.html#toc14">MythWeb.</A></H2> + +<P>MythWeb allows you to use a web page to control various aspects of your +MythTV system. MythWeb is a separate application, but it's dependent on +MythTV being installed and operational.</P> + +<H2><A NAME="ss14.1">14.1</A> <A HREF="mythtv-HOWTO.html#toc14.1">Installation and prerequisites</A> +</H2> + +<P>Mythweb is a part of the <B>mythplugins</B> package. See +<A HREF="mythtv-HOWTO-13.html#mythplugins_">MythPlugins</A> for instructions on downloading the +tarball. The next step depends on whether your distribution has a web server +and if you have PHP support.</P> + +<H3>Mandriva</H3> + +<P>Mandriva has <B>apache</B> and <B>PHP</B> pre-packaged, so +installation is quite simple. </P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Mandriva 9.1 users, perform the following:</CAPTION> +</FIGURE> + +<BLOCKQUOTE><CODE> +<PRE> +# urpmi apache2 apache2-mod_php php-mysql +# chkconfig --level 345 httpd on +# /etc/rc.d/init.d/httpd restart +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss14.2">14.2</A> <A HREF="mythtv-HOWTO.html#toc14.2">Completing the installation</A> +</H2> + +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21/mythweb +$ su +# mkdir /var/www/html/mythweb +# cp -r . /var/www/html/mythweb +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>By default, MythWeb uses an Apache <CODE>.htaccess</CODE> file to restrict +access to the website and to configure some variables.</P> +<P>To create the password file for Apache (if your system doesn't already have +one), you could do something like this: +<BLOCKQUOTE><CODE> +<PRE> +# cd /var/www +# htpasswd -c htpasswd mythtv +New password: +Re-type new password: +Adding password for user mythtv +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>See the man page for <B>htpasswd</B> for more examples.</P> +<P>To access the web page, open a web browser and use <B>http://[name or ip +address]/mythweb/</B></P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Make sure that you have a trailing slash on the URL, +otherwise you will get a <CODE>404 Page not Found</CODE> error.</CAPTION> +</FIGURE> +</P> +<H2><A NAME="ss14.3">14.3</A> <A HREF="mythtv-HOWTO.html#toc14.3">Resetting the key binding table</A> +</H2> + +<P>MythWeb allows you to configure which keys are bound to which actions +within MythTV. If you'd like to reset this back to the default, execute the +following command: +<BLOCKQUOTE><CODE> +<PRE> +$ echo "delete from keybindings ;" | mysql -u mythtv -pmythtv mythconverg +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H2><A NAME="ss14.4">14.4</A> <A HREF="mythtv-HOWTO.html#toc14.4">Resetting the theme.</A> +</H2> + +<P>If you find yourself wedged into a theme that isn't working, open your +web browser and go to site: +<CODE>http://mythweb_name_or_ip_address/mythweb/settings.php?RESET_THEME=yes</CODE></P> +<HR> +<A HREF="mythtv-HOWTO-15.html">Next</A> +<A HREF="mythtv-HOWTO-13.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc14">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-15.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-15.html new file mode 100644 index 0000000..f9a6ba7 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-15.html @@ -0,0 +1,137 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: MythGallery.</TITLE> + <LINK HREF="mythtv-HOWTO-16.html" REL=next> + <LINK HREF="mythtv-HOWTO-14.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc15" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-16.html">Next</A> +<A HREF="mythtv-HOWTO-14.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc15">Contents</A> +<HR> +<H2><A NAME="s15">15.</A> <A HREF="mythtv-HOWTO.html#toc15">MythGallery.</A></H2> + +<P>MythGallery is a photo and slideshow application. MythGallery is a +separate application, but it's dependent on MythTV being installed and +operational.</P> +<H2><A NAME="ss15.1">15.1</A> <A HREF="mythtv-HOWTO.html#toc15.1">Installation and prerequisites</A> +</H2> + +<P>MythGallery is a part of the <B>mythplugins</B> package. See +<A HREF="mythtv-HOWTO-13.html#mythplugins_">MythPlugins</A> for instructions on downloading the +tarball.</P> +<P>There are a number of transitions available, some requiring OpenGL +support. You will also need to install a TIFF library. Under Mandriva, you +would perform the following command: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi libtiff3-devel +</PRE> +</CODE></BLOCKQUOTE> + +Once you have satisfied the prerequisites for your distribution, install the application: +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-opengl --enable-mythgallery +$ qmake mythplugins.pro +$ make +# su +# make install +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> + +The configuration for MythGallery is accessed through the main Setup option +in mythfrontend. Make sure you set your pictures directory to wherever +you're storing your photos.</P> +<P>The controls for MythGallery can be found in the README that comes with the +application.</P> +<H2><A NAME="ss15.2">15.2</A> <A HREF="mythtv-HOWTO.html#toc15.2">Using MythGallery</A> +</H2> + +<P>When you first start MythGallery, you will see a thumbnail view of any +folders and pictures in the Gallery Directory you specified in setup. If +this is the first time you have accessed this directory, the thumbnails will +be generated on the fly. If the Gallery Dir is writable, these thumbnails +will be cached thus speeding up future access. On the left is a greyed-out +menu of options.</P> +<P>Use the arrow keys to select a folder or picture to open/view with the +Select key, or use the Menu key to toggle access the menu on the left. The +menu options are as follows: +<UL> +<LI> Slideshow - Will cycle through all the pictures in the current folder. +The currently selected item must be a picture (not a folder) for this to +work. It does not currently traverse subfolders.</LI> +<LI> Rotate CW - Rotate the current image 90 degrees in the clockwise +direction. This change persists if the current directory is writable.</LI> +<LI> Rotate CCW - As above except the direction of rotation is counter(anti) +clockwise.</LI> +<LI> Import - Import pictures into your Gallery Dir. This option is +described in the next section.</LI> +<LI> Settings - Access the MythGallery settings screen.</LI> +</UL> +</P> +<H2><A NAME="ss15.3">15.3</A> <A HREF="mythtv-HOWTO.html#toc15.3">Importing Pictures</A> +</H2> + +<P>The import path in the setup dialog is a colon separated list of +directories and/or executable files. When the import key is pressed, a new +directory (the destination directory) under the current directory will be +created and the import path will be searched. If the item in the import +path is a directory (the source directory), the contents of that directory +will be copied to the destination directory. If you would like the source +directory to be that of a removable device, it might be a good idea to use +autofs. See the automount howto at +<A HREF="www.linuxdoc.org">www.linuxdoc.org</A> for info on how to get it working.</P> +<P>If the item in the import path is an executable file, MythGallery will +attempt to execute it with the destination directory as its sole argument. +Be careful when using executable scripts that the script runs unattended +(doesn't need user intervention) and returns properly, otherwise it could +create the appearance of MythGallery hanging (e.g. running +<B>smbclient</B> and prompting for password). Also be sure that scripts +have executable permissions set.</P> +<P>Here is an example script that a user may want to run +on import: +<BLOCKQUOTE><CODE> +<PRE> +#!/bin/csh + +if ($#argv == 0) then + echo "Usage: $0 dest_dir" + exit +endif + +cd $argv[1] + +# get stuff over the network +wget http://www.somesite.dom/dir/file1.jpg +wget http://www.somesite.dom/dir/file2.jpg +wget http://www.somesite.dom/dir/file3.jpg + +# stuff that requires manual module loading and/or fs mounting +modprobe camera_module +mount /dev/camera /mnt/camera +cp /mnt/camera/* $argv[1] +umount /mnt/camera +rmmod camera_module + +# perform some processing +foreach pname (`ls *.jpg`) + jpegtran -flip vertical $pname > $pname.new + mv $pname.new $pname +end +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<HR> +<A HREF="mythtv-HOWTO-16.html">Next</A> +<A HREF="mythtv-HOWTO-14.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc15">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-16.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-16.html new file mode 100644 index 0000000..6660a7d --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-16.html @@ -0,0 +1,241 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: MythGame.</TITLE> + <LINK HREF="mythtv-HOWTO-17.html" REL=next> + <LINK HREF="mythtv-HOWTO-15.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc16" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-17.html">Next</A> +<A HREF="mythtv-HOWTO-15.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc16">Contents</A> +<HR> +<H2><A NAME="s16">16.</A> <A HREF="mythtv-HOWTO.html#toc16">MythGame.</A></H2> + +<P>MythGame can used as a frontend to start any emulator that your host OS +runs. This is an example of how to set up xmame on Linux. +<A HREF="http://www.mameworld.net/">http://www.mameworld.net/</A> is +an excellent resource for all things mame.</P> +<P>Installation overview: +<OL> +<LI>Setup directory structure</LI> +<LI>Download and install xmame</LI> +<LI>Download and place extra files (artwork/catver.ini/etc..)</LI> +<LI>Download and install MythGame plugin</LI> +<LI>Setup xmame in MythGame</LI> +<LI>Hints</LI> +</OL> +</P> +<H2><A NAME="ss16.1">16.1</A> <A HREF="mythtv-HOWTO.html#toc16.1">Setup Directory Structure</A> +</H2> + +<P>To keep things organized, create the following directories for <B>xmame</B> to use +in <CODE>/usr/local/share/xmame</CODE>: hiscore, roms, and snaps.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ mkdir -p /usr/local/share/xmame/{highscore,roms,snaps} +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss16.2">16.2</A> <A HREF="mythtv-HOWTO.html#toc16.2">Download and Install xmame</A> +</H2> + +<P><B>NOTE</B>: There may be pre-packaged versions of <B>xmame</B> +available for your distribution. Check +<A HREF="http://x.mame.net/download.html">http://x.mame.net/download.html</A> for the latest version.</P> +<P>Download the source to <B>xmame</B> from +<A HREF="http://x.mame.net/download/xmame-0.103.tar.bz2">http://x.mame.net/download/xmame-0.103.tar.bz2</A></P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ wget http://x.mame.net/download/xmame-0.103.tar.bz2 +$ tar -xjf xmame-0.103.tar.bz2 +$ cd xmame-0.103 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Edit the Makefile with your favorite editor. Adjust the options as required for your system. +<BLOCKQUOTE><CODE> +<PRE> +$ joe Makefile +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Then make and install xmame +<BLOCKQUOTE><CODE> +<PRE> +$ make +$ su +(enter password) +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>After <B>mame</B> has been installed, we need to create some defaults. +<BLOCKQUOTE><CODE> +<PRE> +$ mkdir ~/.xmame +$ cp docs/xmamerc.dist ~/.xmame/xmamerc +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Because some ROMS work better with different display toolkits, or possibly +even older versions of xmame, it's convenient to keep all of your +<B>xmame</B> binaries and to rename them to include the version number. +MythGame allows you to match individual roms to preferred binaries.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ su +(enter password) +# mv /usr/local/bin/xmame.x11 /usr/local/bin/xmame-0.103.x11 +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><B>NOTE</B>: Depending on how you compiled <B>xmame</B>, you may have +<B>xmame.X11</B>, <B>xmame.SDL</B> or <B>xmame.xgl</B> based on what +display toolkit you used. Also, you may need to remove and recreate +<CODE>xmamerc</CODE> after upgrading since some of the default options may have +changed.</P> +<P>Edit <CODE>~/.xmame/xmamerc</CODE> to include your paths. +<BLOCKQUOTE><CODE> +<PRE> +### Fileio Related ### +rompath /usr/local/share/xmame/roms +snapshot_directory /usr/local/share/xmame/snaps +cheat_file /usr/local/share/xmame/cheat.dat +hiscore_file /usr/local/share/xmame/hiscore.dat +hiscore_directory /usr/local/share/xmame/hiscore +history_file /usr/local/share/xmame/history.dat +mameinfo_file /usr/local/share/xmame/mameinfo.dat +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Confirm that <B>xmame</B> works before running it inside MythTV. Place +your ROM in the <CODE>/usr/local/share/xmame/roms</CODE> directory you created +earlier.</P> +<P><B>NOTE</B>: There are three public domain ROM sets available at +<A HREF="http://www.mame.net/downmisc.html">http://www.mame.net/downmisc.html</A></P> +<P>Launch <B>xmame</B> with your game of choice. In this example, we are using Gauntlet. +<BLOCKQUOTE><CODE> +<PRE> +$ xmame gauntlet +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Some basic <B>mame</B> keyboard commands: +<BLOCKQUOTE><CODE> +<PRE> +5 = Insert coin +1 = Player 1 start +arrow keys = movement +left control = button 1 +left alt = button 2 +SPACE = button 3 +ESC = exit +TAB - menu +~ to adjust Volume + < and > +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss16.3">16.3</A> <A HREF="mythtv-HOWTO.html#toc16.3">Download extra files</A> +</H2> + +<P>The following files allow you to add extra functionality. Place them +into <CODE>/usr/local/share/xmame</CODE></P> +<P>- <CODE>catver.ini</CODE> is a catalog of categories and versions of popular mame ROMs.</P> +<P>Useful for keeping large libraries of ROMs organized.</P> +<P>It may be downloaded from +<A HREF="http://www.catver.com">http://www.catver.com</A> or +<A HREF="http://www.mameworld.net/catlist">http://www.mameworld.net/catlist</A></P> +<P>- Screenshots aka "snaps"</P> +<P>These may be downloaded from +<A HREF="http://www.classicgaming.com/mame32qa/">http://www.classicgaming.com/mame32qa/</A></P> +<P>Screenshots are displayed when you are browsing your ROMS in <B>mythgame</B>. +Unzip and place them in <CODE>/usr/local/share/xmame/snaps</CODE></P> +<P>- <CODE>history.dat</CODE></P> +<P>Download from +<A HREF="http://www.arcade-history.com/">http://www.arcade-history.com/</A> +This file fills in a bit of background about each ROM.</P> +<P>- <CODE>hiscore.dat</CODE></P> +<P>Download from +<A HREF="http://www.mameworld.net/highscore/">http://www.mameworld.net/highscore/</A></P> +<P>- Cheats</P> +<P>Download from +<A HREF="http://cheat.retrogames.com/">http://cheat.retrogames.com/</A></P> + +<H2><A NAME="ss16.4">16.4</A> <A HREF="mythtv-HOWTO.html#toc16.4">Download and Install MythGame.</A> +</H2> + +<P><B>MythGame</B> is part of the mythplugins package. See the instructions +in the +<A HREF="mythtv-HOWTO-5.html#DownloadAndCompile">Downloading and Compiling</A> +section to obtain mythplugins.</P> +<P>Switch to the mythplugins directory: +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Compile and install mythgame: +<BLOCKQUOTE><CODE> +<PRE> +$ ./configure --disable-all --enable-mythgame +$ qmake mythplugins.pro +$ make +$ su +(enter password) +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss16.5">16.5</A> <A HREF="mythtv-HOWTO.html#toc16.5">Setup xmame in MythGame</A> +</H2> + +<P>Start <B>mythfrontend</B> and navigate to Utilities/Setup > Setup > Media +Settings > Game Settings > Game Players. Select <CODE>(New Game Player)</CODE>.</P> +<P>To set up a new player for xmame enter the following:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +Player Name: xmame-0.103.x11 (Name by which you want your emulator or game called) +Type: xmame (This is used for display purposes only and does not affect the function of your system) +Command: xmame-0.103.x11 -vidmod 1 -fullscreen (Path and name of binary + any optional parameters) +Rom Path: /usr/local/share/xmame/roms (This tells MythGame what directories to scan for roms to be used with this emulator) +ScreenShots: /usr/local/share/xmame/snaps (This tells MythGame what directories to scan for snapshots to be used with these roms) +Working Directory: (Directory to change to before launching game or emulator. Blank in our case ignores this setting) +File Extensions: (List of all file extension to be used for this emulator. Blank menas any file under the Rom Path) +[] Allow games to span multiple roms/disks (will treat game.1.rom game.2.rom game.3.rom as one game) +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss16.6">16.6</A> <A HREF="mythtv-HOWTO.html#toc16.6">Hints:</A> +</H2> + +<P> +<UL> +<LI>Rom name before options: %s can be used as a standin for rom names on the command line.</LI> +<LI>Multiple disk/rom games: %d1 %d2 etc can be used as standins for multiple disc games on the command line.</LI> +<LI>Associating a rom with an emulator: Browse to the desired rom and press 'M' to enter the settings page for that rom.</LI> +<LI>Assign a Game Favorite Status: Browse to the desired game and press "/".</LI> +</UL> +</P> + +<HR> +<A HREF="mythtv-HOWTO-17.html">Next</A> +<A HREF="mythtv-HOWTO-15.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc16">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-17.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-17.html new file mode 100644 index 0000000..e7eaf9c --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-17.html @@ -0,0 +1,348 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: MythMusic. </TITLE> + <LINK HREF="mythtv-HOWTO-18.html" REL=next> + <LINK HREF="mythtv-HOWTO-16.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc17" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-18.html">Next</A> +<A HREF="mythtv-HOWTO-16.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc17">Contents</A> +<HR> +<H2><A NAME="s17">17.</A> <A HREF="mythtv-HOWTO.html#toc17">MythMusic. </A></H2> + +<P>MythMusic has a number of prerequisites that must be satisfied before it +is operational. Depending on your distribution, some of these prerequisites can +be satisfied through the various package managers. If your distribution doesn't +offer pre-compiled versions of the software below, then follow the generic +instructions for manually compiling and installing the software.</P> +<P>The prerequisites for MythMusic are: +<UL> +<LI>MAD</LI> +<LI>taglib</LI> +<LI>libogg and libvorbis</LI> +<LI>FLAC</LI> +<LI>libcdaudio</LI> +<LI>CDParanoia</LI> +</UL> +</P> + +<H2><A NAME="ss17.1">17.1</A> <A HREF="mythtv-HOWTO.html#toc17.1">Manual installation of prerequisites</A> +</H2> + +<P>These instructions are for distributions which don't have pre-compiled +versions of the software necessary to run MythTV.</P> +<P>Download MAD from +<A HREF="http://www.underbit.com/products/mad">http://www.underbit.com/products/mad</A> and install:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xzf mad-0.15.1b.tar.gz +$ cd mad-0.15.1b +$ ./configure +$ make +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Download TagLib from +<A HREF="http://developer.kde.org/~wheeler/taglib.html">http://developer.kde.org/~wheeler/taglib.html</A> and install:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xzf taglib-1.4.tar.gz +$ cd taglib-1.4 +$ ./configure +$ make +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Download libogg and libvorbis from +<A HREF="http://www.xiph.org/downloads">http://www.xiph.org/downloads</A> and install in a similar manner +to the above packages.</P> +<P>Download FLAC from +<A HREF="http://flac.sourceforge.net">http://flac.sourceforge.net</A> and install: +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xzf flac-1.1.2.tar.gz +$ cd flac-1.1.2 +$ ./configure +$ make +$ su +# make install +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Download libcdaudio from +<A HREF="http://sourceforge.net/project/showfiles.php?group_id=27134">http://libcdaudio.sourceforge.net</A> and +install: +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xzf libcdaudio-0.99.12p2.tar.gz +$ cd libcdaudio-0.99.12p2 +$ ./configure +$ make +$ su +# make install +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Download cdparanoia from +<A HREF="http://www.xiph.org/paranoia/download/cdparanoia-III-alpha9.8.src.tgz">http://www.xiph.org/paranoia/down.html</A>. +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xzf cdparanoia-III-alpha9.8.src.tgz +$ cd cdparanoia-III-alpha9.8 +$ ./configure +$ make +$ su +# make install +# cd /usr/lib +# ln -sf libcdda_interface.so.0.9.8 libcdda_interface.so +# ln -sf libcdda_paranoia.so.0.9.8 libcdda_paranoia.so +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss17.2">17.2</A> <A HREF="mythtv-HOWTO.html#toc17.2">Mandriva</A> +</H2> + +<P>Mandriva has a number of the prerequisites available on the +installation CD. Some of the software you're going to need will have to be +obtained from the "contrib" or "cooker" development repositories. +Applications downloaded from "cooker" come from the development branch, so +there may be issues with some software. It isn't recommended that you mix +cooker and release-level software.</P> + +<P><B>urpmi</B> is the simplest tool for installation of packages from the +command line. The difficult part is the configuration, but this has been +made easier at the following website: +<A HREF="http://addmedia.linuxfornewbies.org/">http://addmedia.linuxfornewbies.org/</A> The website will allow +you to choose a mirror site and then present the command-line configuration +text for that mirror. You will most likely need to add a "Contrib" mirror +to your setup. Once you have done that, you can proceed. If <B>urpmi</B> +prompts you about other modules that need to be installed to satisfy +dependencies, say "Yes".</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +# urpmi libmad0 libmad0-devel libflac4 libflac4-devel libcdaudio1 cdparanoia +# urpmi libcdda0 libcdda0-devel libvorbis0 libvorbis0-devel +# urpmi libcdaudio1-devel libid3tag0 libid3tag0-devel +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3>Additional options with MythMusic</H3> + +<P>Additional visualizations have been added to MythMusic. If you wish to +use these, there are some prerequisites you must install prior to compiling.</P> +<P> +<UL> +<LI>fftw</LI> +<LI>OpenGL</LI> +<LI>SDL</LI> +</UL> +</P> +<P><CODE>fftw</CODE> may be obtained from +<A HREF="http://www.fftw.org/">http://www.fftw.org/</A>. In Mandriva it may be installed by +typing: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi libfftw2 libfftw2-devel +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><CODE>OpenGL</CODE> should be installed on practically all distributions. +However, you will need the devel module. In Mandriva it may be +installed by typing: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi libMesaGLU1-devel +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><CODE>SDL</CODE> may be obtained from +<A HREF="http://www.libsdl.org">http://www.libsdl.org</A>. In Mandriva it may be installed by +typing: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi libSDL1.2 libSDL1.2-devel +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss17.3">17.3</A> <A HREF="mythtv-HOWTO.html#toc17.3">Red Hat Linux 9</A> +</H2> + +<P>Red Hat provides packages for several of the prerequisites, making +installation very simple. Of the prerequisites, Red Hat provides +packages for Vorbis, cdparanoia, SDL, and OpenGL (which you probably +already have installed). To install these all at once, simply type (all on +the same line): +<BLOCKQUOTE><CODE> +<PRE> +$ up2date --solvedeps libvorbis libvorbis-devel vorbis-tools cdparanoia-devel cdparanoia-libs cdparanoia SDL-devel SDL +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you get the following message: "None of the packages you requested +were found, or they are already updated" it probably means you already +have all of those packages installed.</P> +<P>You must install the remaining packages, (MAD, FLAC, libcdaudio and +optionally fftw) manually following the installation directions above. When +installing fftw do not use the rpm package offered on the website because it +will cause an error, so use the source package instead.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: you can use the instructions given at the +<A HREF="mythtv-HOWTO-3.html#atrpms">automated installation section</A> to install all of MythMusic in one +step.</CAPTION> +</FIGURE> +</P> +<H2><A NAME="ss17.4">17.4</A> <A HREF="mythtv-HOWTO.html#toc17.4">Compiling MythMusic</A> +</H2> + +<P>Once all the prerequisites have been installed, you can proceed with +compiling MythMusic.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-mythmusic --enable-fftw --enable-sdl --enable-aac +$ qmake mythplugins.pro +$ make +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss17.5">17.5</A> <A HREF="mythtv-HOWTO.html#toc17.5">Configuring MythMusic</A> +</H2> + +<P>Configuration of MythMusic occurs in two places. The main mythfrontend +Setup is for global MythMusic configuration. Go to the +Setup/MythMusic/General Setup screen and adjust it for your particular +configuration.</P> +<P>The second configuration screen is within the MythMusic program and will +allow you rescan your music library, etc.</P> +<P>Here's some explanation about the Ignore_ID3 and The NonID3FileNameFormat:</P> +<P>If Ignore_ID3 is set to TRUE, MythMusic will try to determine the +Genre, Artist, Album, Track Number, and Title from the filename of the +mp3 file. The NonID3FileNameFormat variable should be set to the +directory/file format where the mp3 files are stored. For instance, I +store mine in the above shown Genre/Artist/Album/Track format. MythMusic +will then use this information to fill in the proper fields when it +populates the musicmetadata table rather than searching for an ID3 tag in +the mp3 file.</P> +<P>The files can be laid out in any format, such as:</P> +<P>Genre/Artist/Album/Title +Artist/Genre/Album/Title +Artist/Album/Title (with Genre left as Unknown)</P> +<P>The track number is optional but can be specified with the title by using +the TRACK_TITLE keyword instead of TITLE. If TRACK_TITLE is used, +then the filename can have a space, hyphen, or underscore separating the +track number from the track title. Keywords are case insensitive, so if +you specify GENRE it's the same as Genre in the format field.</P> +<P>The Ignore_ID3 option does not disable the code that determines the track +length, just the portion that tries to read ID3 info.</P> + +<H2><A NAME="ss17.6">17.6</A> <A HREF="mythtv-HOWTO.html#toc17.6">Using MythMusic</A> +</H2> + +<P>MythMusic is fairly simple to use. It is recommended that you insert the +CD before selecting "Import CD". You should also ensure that your system +doesn't try to automount the CD and begin playing it automatically.</P> +<P>Here's some information on playlist management:</P> +<P>Q: How do I create a new playlist? +A: Using the MythMusic "Select Music" menu option, setup the playlist as you +normally would by adding songs or other playlists as needed. When you are +ready to save the new playlist, highlight "Active Play Queue" at the bottom +of the selection tree and hit the "i" key. This will pop up a menu allowing +you to name and save the new playlist. You can also hit Enter to bring up +the popup on the Active Play Queue. This does not work on the playlists +above, as Enter is obviously bound to checking/unchecking the boxes. Any +number (i.e. keypad on remote) will also bring up the menu in both cases.</P> +<P>Q: How do I enter the playlist name in the text field without a keyboard? +A: Use the keypad number keys (bound to your remote) to select letters +quasi-cell phone style. Keys 2-9 work pretty much like any cell phone text +entry. 1 cycles through a few special characters, delete, and space. 0 is +like a CAPS LOCK. Hard to describe, fairly easy to use. You will soon be +able to specify the cycle timing in a Setup screen. You can type fairly +quickly through a combination of jumping around the number keys AND hitting +a non-number key (right arrow is particularly good for this) to force the +current character.</P> +<P>Q: How do I edit a playlist? +A: Highlight the playlist in the selection tree and hit the "i" key then +select "Move to Active Play Queue" in the popup. You can now modify the +"Active Play Queue" like normal, adding songs and playlists by selecting +them from the song tree. When you are done, highlight the "Active Play +Queue" in the selection tree and hit the "i" key then select "Save Back to +Playlist Tree". And whatever you were editing as your Active Queue before +you moved an existing playlist "on top" of Active reappears. Think of Active +has having a push on, pop off capability, but with a depth of only 1.</P> +<P>Q: How do I delete an item from a playlist? +A: Highlight the item in the selection tree and hit the "d" key.</P> +<P>Q: How do I rearrange the songs in my playlist? +A: Highlight a song and hit the "space" bar, the song will now have pair of +red arrows in front of it. Use the up and down arrow keys to move it around +in the playlist. When you have it where you want it, hit the "space" bar +again.</P> +<P>Q: How do I delete a playlist? +A: Highlight the playlist in the selection tree and hit the "i" key then +select "Delete this Playlist" from the popup.</P> + +<H2><A NAME="ss17.7">17.7</A> <A HREF="mythtv-HOWTO.html#toc17.7">Troubleshooting MythMusic</A> +</H2> + +<P>You may run into errors when running MythMusic.</P> +<H3>When I run MythMusic and try and look up a CD, I get an error message </H3> + +<P>The full text of the message will say: </P> +<P>databasebox.o: Couldn't find your CD. It may not be in the freedb database. +More likely, however, is that you need to delete /.cddb and /.cdserverrc +and restart mythmusic. Have a nice day.</P> +<P>If you get this message, you should go to the home directory of whatever +user MythMusic is running as and type: +<BLOCKQUOTE><CODE> +<PRE> +rm .cdserverrc +rm -rf .cddb/ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>These files aren't automatically deleted because of a conscious design +decision by the author that programs that automatically delete things are +bad.</P> +<P>The files are used to locally cache CD lookups. If you are re-inserting +CDs, your machine will not actually have to go out to the Internet to +determine what is on them. However, the URL used to access the freedb +database has recently changed, so the stale information in the files from +previous runs of MythMusic would cause the error above. Once the files have +been deleted the stale information will be gone and your local database +will be rebuilt as you use CDs.</P> + +<HR> +<A HREF="mythtv-HOWTO-18.html">Next</A> +<A HREF="mythtv-HOWTO-16.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc17">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-18.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-18.html new file mode 100644 index 0000000..01ca0e6 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-18.html @@ -0,0 +1,71 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: MythWeather.</TITLE> + <LINK HREF="mythtv-HOWTO-19.html" REL=next> + <LINK HREF="mythtv-HOWTO-17.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc18" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-19.html">Next</A> +<A HREF="mythtv-HOWTO-17.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc18">Contents</A> +<HR> +<H2><A NAME="s18">18.</A> <A HREF="mythtv-HOWTO.html#toc18">MythWeather.</A></H2> + +<P>MythWeather is a part of the <B>mythplugins</B> package. See +<A HREF="mythtv-HOWTO-13.html#mythplugins_">MythPlugins</A> for instructions on downloading the +tarball.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-mythweather +$ qmake mythplugins.pro +$ make +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>MythWeather uses MSNBC.com as its source for weather data and weather.com +for its radar image.</P> +<P>These are the keyboard commands for MythWeather: +<BLOCKQUOTE><CODE> +<PRE> +Left Key Goes back one page, and extends the time spent + on the page you are on. +Right Key Goes forward one page, see above. +Space Pause, wait on the current page until space is hit + again. +Numeric Keys You can check other weather by keying in other ZIP codes. +Enter Key Switch between Celsius and Fahrenheit. Can also + be used a way to force a data update. +"m" Key Resets the location to the database default, then updates the data. +"i" Enter / Save settings +ESC Exit the settings screen without saving / Exit the program +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>MythWeather also has an "Aggressiveness" setting. This affects how long +MythWeather waits for data from the msnbc.com website before timing out. If +you are on a slow connection, or have a slow DNS, or MythWeather just +doesn't seem to be working and you've already tried everything else, then +try increasing the aggressiveness level parameter. This parameter is +inverse; a higher number actually means that MythWeather will be less +aggressive, and will therefore wait longer before timing out.</P> +<P>MythWeather will print debugging information on the terminal. If you wish +to see additional debugging information while MythWeather is running, run +mythweather from the command line with as <CODE>mythweather --debug</CODE></P> +<P>You may also force mythweather to re-run the configuration by starting it on +the command line as <CODE>mythweather --configure</CODE>. These two options are +mutually exclusive.</P> + +<HR> +<A HREF="mythtv-HOWTO-19.html">Next</A> +<A HREF="mythtv-HOWTO-17.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc18">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-19.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-19.html new file mode 100644 index 0000000..f9e9969 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-19.html @@ -0,0 +1,42 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: MythVideo.</TITLE> + <LINK HREF="mythtv-HOWTO-20.html" REL=next> + <LINK HREF="mythtv-HOWTO-18.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc19" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-20.html">Next</A> +<A HREF="mythtv-HOWTO-18.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc19">Contents</A> +<HR> +<H2><A NAME="s19">19.</A> <A HREF="mythtv-HOWTO.html#toc19">MythVideo.</A></H2> + +<P>MythVideo is a part of the <B>mythplugins</B> package. See +<A HREF="mythtv-HOWTO-13.html#mythplugins_">MythPlugins</A> for instructions on downloading the +tarball.</P> +<P>MythVideo will allow you to use an external program to watch media files +that are not directly supported by MythTV.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-mythvideo +$ qmake mythplugins.pro +$ make +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>See MythVideo's <CODE>README</CODE> file for additional information.</P> + +<HR> +<A HREF="mythtv-HOWTO-20.html">Next</A> +<A HREF="mythtv-HOWTO-18.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc19">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-2.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-2.html new file mode 100644 index 0000000..c958ba0 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-2.html @@ -0,0 +1,27 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: Introduction.</TITLE> + <LINK HREF="mythtv-HOWTO-3.html" REL=next> + <LINK HREF="mythtv-HOWTO-1.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc2" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-3.html">Next</A> +<A HREF="mythtv-HOWTO-1.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc2">Contents</A> +<HR> +<H2><A NAME="s2">2.</A> <A HREF="mythtv-HOWTO.html#toc2">Introduction.</A></H2> + +<P>This HOWTO document will focus on manually building MythTV in a North +American environment. If you have installation instructions for a different +region or Linux distribution, please send them to the author so that it can +be included in other versions of this document.</P> + +<HR> +<A HREF="mythtv-HOWTO-3.html">Next</A> +<A HREF="mythtv-HOWTO-1.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc2">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-20.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-20.html new file mode 100644 index 0000000..6b3561b --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-20.html @@ -0,0 +1,102 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: MythDVD.</TITLE> + <LINK HREF="mythtv-HOWTO-21.html" REL=next> + <LINK HREF="mythtv-HOWTO-19.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc20" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-21.html">Next</A> +<A HREF="mythtv-HOWTO-19.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc20">Contents</A> +<HR> +<H2><A NAME="s20">20.</A> <A HREF="mythtv-HOWTO.html#toc20">MythDVD.</A></H2> + +<P>MythDVD is a part of the <B>mythplugins</B> package. See +<A HREF="mythtv-HOWTO-13.html#mythplugins_">MythPlugins</A> for instructions on downloading the +tarball. MythDVD is an application which rips DVDs and makes them available for +use with MythVideo. You may also transcode the DVD content from MPEG-2 to +other formats which should greatly reduce the amount of space the DVD +material takes up on your hard drive.</P> +<P>MythDVD has a number of prerequisites to enable transcoding functionality. +If you only wish to play DVDs rather than convert them to something like +MPEG-4 or xvid you may skip the prerequisite installation step.</P> + +<H2><A NAME="ss20.1">20.1</A> <A HREF="mythtv-HOWTO.html#toc20.1">Manual Compilation of Prerequisites</A> +</H2> + + +<H2><A NAME="ss20.2">20.2</A> <A HREF="mythtv-HOWTO.html#toc20.2">Pre-compiled binaries</A> +</H2> + +<P>Mandriva users may install the prerequisites this way: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi libdvdread3 libdvdread3-devel a52dec liba52dec-devel +# urpmi mplayer ogle xine +</PRE> +</CODE></BLOCKQUOTE> + +Assuming that you've added a PLF mirror, you may also load the rest of the +prerequisites using the following command: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi xvid xvid-devel fame libfame0.9-devel transcode libdvdcss +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>In the example below, we have enabled support for transcoding and for VCD +playing. You may remove these options if you don't need them. +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.20 +$ ./configure --disable-all --enable-mythdvd --enable-transcode --enable-vcd +$ qmake mythplugins.pro +$ make +$ su +# make install +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H2><A NAME="ss20.3">20.3</A> <A HREF="mythtv-HOWTO.html#toc20.3">Running the Myth Transcoding Daemon</A> +</H2> + +<P>Transcoding ("ripping") a DVD requires you to run the Myth Transcoding +Daemon (mtd). To ensure that mtd is configured correctly, you should first +test it at the command line. +<BLOCKQUOTE><CODE> +<PRE> +$ mtd -n +</PRE> +</CODE></BLOCKQUOTE> + +The last line of text should show something like: +<BLOCKQUOTE><CODE> +<PRE> +mtd is listening on port 2342 +</PRE> +</CODE></BLOCKQUOTE> + +This indicates that mtd is ready for use. Once you've successfully +tested mtd in the foreground, type <B>CTRL-C</B> to stop mtd. You may +then start it as a background (daemon) process. +<BLOCKQUOTE><CODE> +<PRE> +$ mtd -d +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Running mtd as a daemon will allow you to automatically start it during the +boot process. For example, you may add <CODE>mtd -d</CODE> to your +<CODE>rc.local</CODE> file, or you can adjust the script/steps outlined in the +section called +<A HREF="mythtv-HOWTO-23.html#mythbackend_autostart">Automatically starting mythbackend at system boot time</A> to start mtd instead of mythbackend.</P> + +<HR> +<A HREF="mythtv-HOWTO-21.html">Next</A> +<A HREF="mythtv-HOWTO-19.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc20">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-21.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-21.html new file mode 100644 index 0000000..8b8d7dd --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-21.html @@ -0,0 +1,37 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: MythNews.</TITLE> + <LINK HREF="mythtv-HOWTO-22.html" REL=next> + <LINK HREF="mythtv-HOWTO-20.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc21" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-22.html">Next</A> +<A HREF="mythtv-HOWTO-20.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc21">Contents</A> +<HR> +<H2><A NAME="s21">21.</A> <A HREF="mythtv-HOWTO.html#toc21">MythNews.</A></H2> + +<P>MythNews is a part of the <B>mythplugins</B> package. See +<A HREF="mythtv-HOWTO-13.html#mythplugins_">MythPlugins</A> for instructions on downloading the +tarball. MythNews is a RSS reader. +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-mythnews +$ qmake mythplugins.pro +$ make +$ su +# make install +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<HR> +<A HREF="mythtv-HOWTO-22.html">Next</A> +<A HREF="mythtv-HOWTO-20.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc21">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-22.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-22.html new file mode 100644 index 0000000..9a4f0b6 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-22.html @@ -0,0 +1,608 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: Troubleshooting.</TITLE> + <LINK HREF="mythtv-HOWTO-23.html" REL=next> + <LINK HREF="mythtv-HOWTO-21.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc22" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-23.html">Next</A> +<A HREF="mythtv-HOWTO-21.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc22">Contents</A> +<HR> +<H2><A NAME="s22">22.</A> <A HREF="mythtv-HOWTO.html#toc22">Troubleshooting.</A></H2> + +<H2><A NAME="ss22.1">22.1</A> <A HREF="mythtv-HOWTO.html#toc22.1">Compiling</A> +</H2> + +<H3>Compile errors</H3> + +<P>Some compile errors are worse than others. If you get an error that +doesn't abort the compilation, and says something like: +<BLOCKQUOTE><CODE> +<PRE> +cc1plus: warning: changing search order for system directory +"/usr/local/include" +cc1plus: warning: as it has already been specified as a non-system +directory +</PRE> +</CODE></BLOCKQUOTE> + +then it shouldn't be a problem.</P> +<P>If you get an error like <CODE>/usr/bin/ld: cannot find -lXext</CODE>, the +compiler is telling you that you don't have XFree86-devel installed, or that +your distribution hasn't set it up correctly. This needs to be fixed before +MythTV will compile.</P> + +<H3><A NAME="mkspecs_error"></A> make: *** No rule to make target /usr/lib/qt3/mkspecs/default/qmake.conf', needed by Makefile'. Stop. </H3> + +<P>This error happens when there's a missing link in the +<CODE>/usr/lib/qt3/mkspecs</CODE> directory. There are two ways to fix this +error:</P> +<P>1. Create the link manually: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# cd /usr/lib/qt3/mkspecs +# ln -sf linux-g++ default +</PRE> +</CODE></BLOCKQUOTE> + +and then restart the compile,</P> +<P>or</P> +<P>2. Run <B>qmake mythtv.pro</B> in the mythtv directory. Rerunning +<B>qmake</B> will create a new Makefile for you, however this still +doesn't fix the root cause of the issue, which is that your distribution +didn't create the symlink for you when the qt3 package was installed. The +first choice is the better solution.</P> + +<H3>make: *** No rule to make target /mkspecs/default/qmake.conf', needed by Makefile'. Stop.</H3> + +<P>You didn't set your <CODE>QTDIR</CODE>. Re-read the section on +<A HREF="mythtv-HOWTO-4.html#Setting_up_paths">Setting up paths</A>.</P> + +<H3>Internal Segmentation Fault.</H3> + +<P>This is most likely to be caused by an overheating processor rather than +an actual programming fault within gcc.</P> + +<H2><A NAME="debugging"></A> <A NAME="ss22.2">22.2</A> <A HREF="mythtv-HOWTO.html#toc22.2">Debugging </A> +</H2> + +<H3>MythTV segfaults</H3> + +<H3>MythTV isn't doing anything</H3> + +<H3>Debugging with GDB</H3> + +<P>Without details, the developers will not be able to determine if you have +discovered a genuine code-bug, or if the problem is with your system. In +order to determine what's going on, you must recompile MythTV with debugging +support and run MythTV within <B>gdb</B>, the GNU debugger. +Note that, on OS X, some data is provided without going through these steps. +See /Library/Logs/CrashReporter/MythFrontend.crash.log</P> +<P>Re-run the <B>configure</B> script and add <CODE>--compile-type=debug</CODE> +to any previous configuration options you may have used. Check the +<CODE>config.log</CODE> file if you have forgotten.</P> +<P>Now, you need to clear out the old versions of the software to ensure that +you're running with the debugging code, then compile and install. +<BLOCKQUOTE><CODE> +<PRE> +$ make distclean +$ ./configure --compile-type=debug +$ make +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>At this point, you now have debug-enabled software ready. To make sure that +you don't forget to type a command required for debugging, it's best to +setup a <CODE>gdbcommands</CODE> file. This will be read by <B>gdb</B> when it's +started. +Put the following into <CODE>gdbcommands</CODE> in your home directory:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +handle SIGPIPE nostop noprint +handle SIG33 nostop noprint +set logging on +set pagination off +set args -l myth.log -v record,channel,siparser +run +thread apply all bt full +set logging off +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Let's assume that the problem you're having is in <B>mythbackend</B>.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ gdb mythbackend -x gdbcommands +GNU gdb 6.3-debian +Copyright 2004 Free Software Foundation, Inc. +GDB is free software, covered by the GNU General Public License, and you are +welcome to change it and/or distribute copies of it under certain conditions. +Type "show copying" to see the conditions. +There is absolutely no warranty for GDB. Type "show warranty" for details. +This GDB was configured as "i386-linux".Using host libthread_db library "/lib/tls/libthread_db.so.1". +[Thread debugging using libthread_db enabled] +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><B>gdb</B> will automatically read the commands that you've placed in the +<CODE>gdbcommands</CODE> file and begin running the program you specified on the +command line.</P> +<P>If the program appears to be locked up, press CTRL-C to create the backtrace +file.</P> +<P>All of the output from <CODE>gdb.txt</CODE> should be posted to the mythtv-dev +mailing list, along with the steps you followed to get the program to crash.</P> +<P><B>NOTE</B>: If you're trimming the <CODE>gdb.txt</CODE> file to remove +extraneous information from the beginning of the file, make sure you include +at least 10 lines <EM>prior</EM> to the point where the backtrace actually +begins. This ensures that there is some context to the backtrace, and so +that it's possible to see what exactly caused the segfault.</P> +<P><B>gdb</B> has a number of options, read the <CODE>man</CODE> page for more +information. </P> +<P>Using the <CODE>gdbcommands</CODE> file in conjunction with a <B>while</B> loop +will ensure that <B>gdb</B> creates a trace file and then restarts:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ while true; do date >> gdb.txt; gdb mythbackend -x gdbcommands; done; +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><B>NOTE</B>: To exit this loop you will need to kill the while loop.</P> +<P>If you're trying to troubleshoot and you can't get back to the <B>gdb</B> window +for some reason, it may be easier to use two systems or to start +mythfrontend from the text console.</P> +<P>If you're going to troubleshoot from a remote system, connect to the machine +that you're going to test using <B>ssh</B> or <B>telnet</B>. Next, type +<CODE>$ export DISPLAY=localhost:0.0</CODE>. This will allow the graphics to be +displayed on the X console (usually ALT-F6 or ALT-F7) and still give you +output and control of <B>mythfrontend</B>, either from the <B>ssh</B> +session, or by switching back to the text console by pressing CTRL-ALT-F1. +You can now continue troubleshooting using <B>gdb</B> as detailed in the +instructions.</P> + +<H3>MythTV is crashing your system</H3> + +<P>When run as a non-privileged user, MythTV <EM>can not</EM> crash your +system. If your system is crashing when you run MythTV, then you have some +issue with the drivers for your capture card or other hardware, or the CPU +fan has fallen off/broken and your system is overheating when asked to +perform a CPU intensive task like encoding video.</P> +<P>If you are running as root, which is <B>strongly discouraged</B>, it is +possible that your system may crash due to the real-time thread using all +available CPU. You will not be able to interrupt the process, so for all +intents and purposes your computer will have crashed.</P> + +<H2><A NAME="ss22.3">22.3</A> <A HREF="mythtv-HOWTO.html#toc22.3">Installing</A> +</H2> + +<H3>When trying to run mythtv-setup, you get an error like this: "mythtv-setup: error while loading shared libraries:"</H3> + +<P>You didn't add <CODE>/usr/local/lib</CODE> to <CODE>/etc/ld.so.conf</CODE>. See the +section on modifying +<A HREF="mythtv-HOWTO-4.html#modifying_ld.so.conf">/etc/ld.so.conf</A>.</P> + +<H2><A NAME="ss22.4">22.4</A> <A HREF="mythtv-HOWTO.html#toc22.4">Using</A> +</H2> + +<H3>No programs are displayed in "Watch Recordings"</H3> + +<P>This situation occurs most often with a system that acts as a frontend +and a slave backend. MythTV supports system-global and user-specific +configuration files, with user-configuration files taking precedence. 99% +of the configuration for MythTV is in the MySQL database, but MythTV still +needs to know where the MySQL server is running. This information is in the +<CODE>mysql.txt</CODE> file. By default, it will be installed to +<CODE>/usr/local/share/mythtv</CODE>, but a copy placed into <CODE>~/.mythtv</CODE> +will over-ride the global configuration.</P> +<P>You must ensure that there aren't multiple, conflicting versions of this +file on your system! +<BLOCKQUOTE><CODE> +<PRE> +$ locate mysql.txt +/usr/local/share/mythtv/mysql.txt +/home/mythtv/.mythtv/mysql.txt +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>As you can see, in this example there are two <CODE>mysql.txt</CODE> files. If +they are not identical, then there may be unintended consequences.</P> +<P>You may also see this error if you completely fill the <CODE>/var</CODE> +partition. The most likely <EM>mythtv-related</EM> reason for this is an +overly large mythbackend or mythfrontend log file in <CODE>/var/log</CODE>. If +you have logging enabled for the backend, and myth runs for weeks at a time, +this may creep up and surprise you. Note that many system processes also +write to <CODE>/var</CODE> and the system may not boot if it is unable to write +to <CODE>/var</CODE> due to a full partition.</P> + +<H3>MySQL not connecting correctly</H3> + +<P>Your <B>MySQL</B> installation may have networking turned off. +Check that <CODE>/etc/mysql/my.cnf</CODE> <EM>does not</EM> contain +<CODE>skip-networking</CODE>. If it does, remove it. Also verify that +<CODE>bind-address</CODE> is set to your IP address instead of +<CODE>127.0.0.1</CODE>. If you change either of these items, restart +<B>MySQL</B>.</P> + +<H3>MySQL database is corrupt</H3> + +<P>If you have reason to believe that your MySQL database is corrupt, +execute the following commands to attempt to repair it.</P> +<P><B>NOTE</B>: Ensure that there are no programs accessing the database +while you attempt to repair it. Make sure that all backend and frontend +programs have exited.</P> +<P><CODE>mysqlcheck -r -umythtv -p<password> mythconverg</CODE></P> + +<H3>Using a MPEG-2 encoder card and the video appears "jittery"</H3> + +<H3>Using a MPEG-2 encoder card and the video is jumping up and down</H3> + +<P>This is a different problem than the one discussed in the previous +section. Currently, the ivtv driver or firmware appear to have some issues +if the vertical capture resolution is not the full screen height. If you +are having a jitter problem then ensure that you are capturing either 480 +lines (for NTSC) or 576 lines (for PAL). The default capture profiles may +need to be edited for your setup. Go to Settings->TV Settings->Recording +Profiles and adjust the <B>Default</B> and <B>Live TV</B> options to +480 or 576 from their defaults.</P> + +<H3>Screen goes blank but returns when mouse is moved or keyboard is used</H3> + +<P>This is due to DPMS, the Display Power Management System, which is used +to save power by turning off your monitor when the system decides that it's +not being used or due to a screensaver that has defaulted to a blank screen. +MythTV now has DPMS support built-in, and should intelligently handle the +screen. Continue reading if you wish to override DPMS and force it off.</P> +<P>Since it's likely that watching TV will not generate keyboard or mouse +events for a time, you need to turn off DPMS and the screensaver. There are +a few ways to do this. You may also need to check your BIOS for power +saving modes and disable screen blanking there as well.</P> +<P>Edit your <CODE>/etc/X11/XF86Config-4</CODE> or <CODE>/etc/X11/xorg.conf</CODE> +file, and look for: +<BLOCKQUOTE><CODE> +<PRE> +Section "ServerFlags" + #DontZap # disable <Ctrl><Alt><BS> (server abort) + #DontZoom # disable <Ctrl><Alt><KP_+>/<KP_-> (resolution switching) + AllowMouseOpenFail # allows the server to start up even if the mouse doesn't work + + Option "blank time" "0" + Option "standby time" "0" + Option "suspend time" "0" + Option "off time" "0" + Option "NoPM" "1" +EndSection +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Also, look for: +<BLOCKQUOTE><CODE> +<PRE> +Section "Device" + Identifier "device1" + VendorName "nVidia Corporation" + BoardName "NVIDIA GeForce 256 (generic)" + Driver "nv" + Option "DPMS" +EndSection +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>In this case, you would need to either delete the <CODE>Option "DPMS"</CODE> +line, or change it to <CODE># Option "DPMS"</CODE> to comment it out. The next +time you start XFree this change will take effect.</P> +<P>Finally, check: +<BLOCKQUOTE><CODE> +<PRE> +Section "Monitor" + Identifier "monitor1" + VendorName "Plug'n Play" + HorizSync 30-85 + VertRefresh 50-160 + + # Sony Vaio C1(X,XS,VE,VN)? + # 1024x480 @ 85.6 Hz, 48 kHz hsync + ModeLine "1024x480" 65.00 1024 1032 1176 1344 480 488 494 563 -hsync -vsync + + # TV fullscreen mode or DVD fullscreen output. + # 768x576 @ 79 Hz, 50 kHz hsync + ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630 + + # 768x576 @ 100 Hz, 61.6 kHz hsync + ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616 +EndSection +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Ensure that there isn't an <CODE>Option "DPMS"</CODE> in the Monitor +configuration.</P> +<P>You can also turn off DPMS from the Command Line, but this will not survive +a reboot. +<BLOCKQUOTE><CODE> +<PRE> +$ xset -dpms +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Using <CODE>xset +dpms</CODE> will turn it back on.</P> +<P>Another technique to try, which will turn off the screensaver: +<BLOCKQUOTE><CODE> +<PRE> +$ xset s off +</PRE> +</CODE></BLOCKQUOTE> + +You may also combine the command to turn off DPMS and the screensaver: +<BLOCKQUOTE><CODE> +<PRE> +$ xset -dpms s off +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Finally, depending on your distribution, you may be able to turn it off from +within the control panel.</P> +<H2><A NAME="ss22.5">22.5</A> <A HREF="mythtv-HOWTO.html#toc22.5">Miscellaneous</A> +</H2> + +<H3>mythfilldatabase failing</H3> + +<P>If mythfilldatabase suddenly appears to be failing, there are at least +two things to check. </P> +<P>First, if you are in North America, ensure that your DataDirect subscription +is still valid, otherwise, check to see what version of XMLTV you're +running and that it's the latest version.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: It is highly recommended that you run the latest +version of XMLTV available. Your listings provider may have made changes +which negatively impact XMLTV.</CAPTION> +</FIGURE> +</P> + +<H3><A NAME="Setting_DMA"></A> Fast CPU, choppy or jittery video </H3> + +<P>First, you should check that your kernel has been enabled for DMA: +<BLOCKQUOTE><CODE> +<PRE> +[mythtv@pvr mythtv]$ dmesg |grep DMA + ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA + ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio +hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63, UDMA(33) +hdb: 80043264 sectors (40982 MB) w/2048KiB Cache, CHS=4982/255/63, UDMA(33) +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>From the listing above, you can see that hda, hdb and hdc are set for DMA, +and hdd is set for pio. If your kernel is not reporting DMA being enabled, +you may need to recompile your kernel. Check your motherboard's chipset +(look in the "ATA/IDE/MFM/RLL support" section in "make menuconfig") for more +information.</P> +<P>Next, check that the hard drive has DMA enabled. Use the <B>hdparm</B> +program to check and enable DMA. +<BLOCKQUOTE><CODE> +<PRE> +# hdparm -d /dev/hd? +</PRE> +</CODE></BLOCKQUOTE> + will tell you the DMA status for your hard drives. If you run +<B>hdparm</B> with the <CODE>-d1</CODE> parameter, it will turn DMA on.</P> + +<P>You may also setup your PC to do this at boot time, either by adding the +command to your <CODE>/etc/rc.local</CODE> file, or by adding files to +/etc/sysconfig.</P> +<P>On Mandriva and other distributions, if you install <B>hdparm</B> from an RPM you +will most likely get a <CODE>/etc/sysconfig/harddisks</CODE> file installed. +This file will be parsed by the <CODE>/etc/rc.sysinit</CODE> script. If you use +the default <CODE>harddisks</CODE> file, your changes will affect all IDE devices +(including CD ROMs). If you wish to use different parameters for various +devices, rename and/or copy the file to <CODE>harddiskhda</CODE>, +<CODE>harddiskhdb</CODE>, etc. Edit the file to your liking and on the next +reboot your setting will be preserved.</P> + +<H3>Frontend appears to be slow at jumping / seeking.</H3> + +<H3>On-screen Display shows incorrect program length.</H3> + +<P>This may occur when MythTV doesn't have an accurate seek table. Run +<B>mythcommflag --rebuild</B></P> + +<H3><A NAME="Troubleshooting_Audio"></A> Troubleshooting audio </H3> + +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: the following instructions do not apply to PVR-250/350 +encoders; the MPEG-2 file will have the audio embedded in the stream so it +is not accessible using <CODE>/dev/dsp</CODE>. </CAPTION> +</FIGURE> +</P> +<P>Audio appears to be one of the bigger issues that users run into on the +mailing list. If the audio isn't configured correctly, then MythTV will +often appear to hang, when in fact it is trying to manipulate the audio +subsystem and failing. You may or may not receive error messages indicating +that the source of the error is the audio subsystem.</P> +<P>You can not use <B>xawtv</B> to determine if your audio is working +correctly, since <B>xawtv</B> is simply using the analog sound patched +through line-in to line-out. It doesn't need to digitize the sound unless +you are using the recording function.</P> +<P>A better test to verify that sound will work for MythTV (and recording with +<B>xawtv</B> for that matter) is to startup <B>xawtv</B>, mute the +line-in then run <CODE>aplay /dev/dsp</CODE>. You should hear the recorded audio +slightly delayed behind the real-time video. You should see messages about +"underrun". These can be ignored but they do confirm that the driver is +loaded and there is an active device. Once this test succeeds, MythTV +should work correctly because it writes to and read from /dev/dsp in +the same way that <B>aplay</B> does.</P> +<P>To record audio along with video the audio signal must be digitized by a DSP +so that the audio data can be stored in a file. On playback, the audio data +is written to /dev/dsp and converted back to an analog signal. This analog +signal should then be sent to your speakers. Here is what is needed in +<B>alsamixer</B>. If you are using an ALSA version after 1.0.6, use +<B>alsamixer -V all</B>:</P> +<P>CAPTUR source - the analog source to be sent to the DSP. This should be set +to the input source from the tuner card to the sound card. In most cases +this is Line but this could also be Aux, CD, Mic, etc., depending on how you +connect the input cable. This source should be muted to prevent patching +through the analog sound. The volume of this source will not affect the +record level.</P> +<P>Capture mixer - this sets the level for the analog to digital recording. +While a volume of 100% is recommended for testing, distortion may occur. +Lowering this level to 75% to 85% may result in better audio quality. +"Capture" should be marked as the CAPTUR destination.</P> +<P>PCM mixer - this sets the level for the digital to analog playback. While a +volume of 100% is recommended for testing, distortion may occur. Lowering +this level to 75% to 85% may result in better audio quality.</P> +<P>Master mixer - sets the level for the analog signal sent to line-out or the +speakers.</P> +<P>You may also want to ensure that <CODE>/dev/dsp</CODE> , or whatever device file +is being used, hasn't already been grabbed by another process, like +<B>esd</B> or <B>artsd</B>. If the device file isn't available, then +MythTV won't work. You may wish to run <B>configure</B> and enable +support for these.</P> +<P>If you wish to see what application is grabbing a resource, you can use the +<CODE>fuser</CODE> command: +<BLOCKQUOTE><CODE> +<PRE> +# fuser -v /dev/dsp +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>To disable aRts in KDE, go to KDE->Control Center->Sound->Sound System and +uncheck the "Start aRts soundserver on KDE startup" box. Run <CODE># killall +artsd</CODE> from the command line to stop the artsd program.</P> +<P>If you're using multiple sound cards and multiple tuners, use <CODE>alsamixer +-c 1</CODE> to work with the second sound card. The first card is #0, the +second card is #1, etc.</P> + +<H3>Mythbackend reports that your card is not reporting full duplex capabilities</H3> + +<H3>The mythbackend program told me to look at this section</H3> + +<P>mythbackend does a check to see if your sound device is capable of full +duplex operation. If it's not, it's most likely that you're going to run +into issues when you try to record and play sound at the same time. If your +backend is a separate machine than your frontend, then there's no problem, +since you're only going to be doing one thing at a time with the card. +Likewise, if you're running the frontend and backend on the same machine, +but you're using btaudio or a hardware encoder card such as the Hauppauge +PVR-250, DVB cards or HDTV capture cards as your recording source and you're +only using the playback function of your sound card, then you also shouldn't +have an issue, since the sound card isn't being asked to perform two +functions at once.</P> +<P>If you can't get your sound card to go full-duplex and need it to, then check +your distribution for updated sound drivers. If your sound card is not +capable of full-duplex operation, either because the drivers don't support +it, or it has been designed that way, then you're pretty much out of luck +and will either need to purchase a new sound card, or will need to get +btaudio +<A HREF="mythtv-HOWTO-23.html#btaudio">operational</A>.</P> + +<H3>My remote doesn't work / works sometimes and not others / "ghost" keypresses</H3> + +<P>This can be due to a number of factors. The simplest case is the +"ghost" keypresses. For me, it was due to compact fluorescent lights in +the same room as the IR receiver, which the receiver was picking up as +keypresses. Once the lights were switched to incandescent bulbs, the ghost +went away.</P> +<P>You may have an issue with <B>lirc</B> misinterpreting IR commands from a +different remote. I also have an issue where the TiVo "Peanut" remote will +eventually cause <B>lircd</B> to stop responding; even though <B>lircd</B> +is configured for the Pinnacle Systems remote, the TiVo remote IR patterns +are being seen by the IR receiver.</P> +<P>If your remote has been properly configured, and <B>irw</B> and +<B>irxevent</B> are working correctly, then it's highly likely that your +window manager is not giving focus correctly to the various Myth programs as +they run. The following window managers are known to work correctly:</P> +<P> +<UL> +<LI>fvwm</LI> +<LI>blackbox (using "Sloppy Focus" and "Focus New Windows")</LI> +</UL> +</P> +<P><B>NOTE</B>: You do not need to use <B>irxevent</B> if you are using +MythTV's native LIRC support, so the window manager focus issue does not +apply in that case.</P> + +<H3>Where's "canada-cable"?</H3> + +<H3>Channels are off by one</H3> + +<P>There is no such thing as "Canada Cable"; Canada uses the same +frequencies as the United States. "Canada Cable" was a hack that some +people used when they would discover that their channels were off-by-one, +i.e. when tuning to channel 42, they might get channel 41 or 43. This is +actually due to the tuner on the video capture device being mis-detected. +You must manually specify the tuner type in your <CODE>/etc/modules.conf</CODE>. +See the video4linux mailing list ( +<A HREF="https://listman.redhat.com/mailman/listinfo/video4linux-list">https://listman.redhat.com/mailman/listinfo/video4linux-list</A>) for +more information.</P> + +<H3>Mythweb is showing a db_open error when I connect to it</H3> + +<P>Find your <CODE>php.ini</CODE> file. Make sure you've got a line in it like this:</P> +<P><CODE>extension=mysql.so</CODE></P> +<P>Restart <B>apache</B> for it to take effect.</P> + +<H3>Mouse pointer disappears when placed over the MythTV windows</H3> + +<P>This is the intended behavior. The MythTV interface is meant for use +with a remote control or a keyboard.</P> + +<H3>What does "strange error flushing buffer" mean on the console?</H3> + +<P>Nothing, really. It's just lame (the mp3 encoder) complaining for some +obscure reason. This seems to be fixed in more recent versions of the +libmp3lame library.</P> + +<H3>Can't change the channel when watching Live TV.</H3> + +<P>Something's wrong with your program database. Did mythfilldatabase run +with no major errors? Or, MythTV may not have permissions to the +appropriate video4linux devices. See the section titled +<A HREF="mythtv-HOWTO-4.html#devperms">Device Permissions</A> for an example.</P> + +<H3>Screen goes black when you try to play something</H3> + +<P>MythTV prints error and status messages to the shell that was used to +start the application. If nothing seems to be happening when you try to +view a program, try switching back to the shell and look for error messages +there, or, if you're running from a startup script, check the log file.</P> + +<H3>Poor performance with NVidia cards and XvMC</H3> + +<P>XvMC is a NVidia driver feature which is supposed to help with decoding +video. Users have reported that rather than speeding up their video it +appears to be doing the opposite. You may want to check that your color +depth is set for 24bpp.</P> + +<H3>Computer is loading a media player application when you insert a CD or DVD</H3> + +<P>You need to disable any sort of auto-running media player in your +environment, otherwise MythDVD or MythMusic will not be able to work +properly.</P> +<P>In KDE, you may want to perform the following: +<BLOCKQUOTE><CODE> +<PRE> +$ rm ~/.kde/Autostart/Autorun.desktop +</PRE> +</CODE></BLOCKQUOTE> +</P> +<HR> +<A HREF="mythtv-HOWTO-23.html">Next</A> +<A HREF="mythtv-HOWTO-21.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc22">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-23.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-23.html new file mode 100644 index 0000000..8b7439e --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-23.html @@ -0,0 +1,1193 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: Miscellaneous. </TITLE> + <LINK HREF="mythtv-HOWTO-24.html" REL=next> + <LINK HREF="mythtv-HOWTO-22.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc23" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-24.html">Next</A> +<A HREF="mythtv-HOWTO-22.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc23">Contents</A> +<HR> +<H2><A NAME="s23">23.</A> <A HREF="mythtv-HOWTO.html#toc23">Miscellaneous. </A></H2> + +<H2><A NAME="ss23.1">23.1</A> <A HREF="mythtv-HOWTO.html#toc23.1">I'd like to watch the files without using MythTV / I'd like to convert the files to some other format</A> +</H2> + +<P>First, check if the <B>mytharchive</B> plugin does what you want. If not, then +read on:</P> +<P>MythTV comes with a utility called <B>mythtranscode</B> which can +decode nuv files into raw format for use with other applications. This +command-line utility was not designed to be used by the end-user, but +instead to be called by other applications or scripts. Programs like +<B>nuvexport</B> ( +<A HREF="http://forevermore.net/myth/">http://forevermore.net/myth/</A>) are better suited for the end user. +However, since <B>mythtranscode</B> can be a useful tool, directions on +using it follow.</P> +<P><B>mythtranscode</B> creates raw streams, which means that they do not +contain any container information such as resolution, frame-rate, or audio +sampling rate. In order to process the output, you must supply this +information to the processing utility. <B>mythtranscode</B> provides the +relevant information on STDOUT.</P> +<P>There are two modes in which <B>mythtranscode</B> can create raw streams. +The first has no synchronization and assumes that the processing utility +will read audio and video at a constant rate. This method is useful when a +single application will be processing the raw output, such as +<B>mencoder</B> or <B>ffmpeg</B>. The second method assumes that two +separate applications will be processing the audio and video streams +independently, and there is no rate control between them which means that +the two programs don't coordinate their efforts to maintain synchronization.</P> + +<H3>mythtranscode example</H3> + +<P>First, start <B>mythtranscode</B>. You will need to determine the +channel and the start time manually. +<BLOCKQUOTE><CODE> +<PRE> +$ mythtranscode --chanid 1036 --starttime 2003-10-20T15:30:00 --profile \ +autodetect --fifodir . & +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>When <B>mythtranscode</B> begins executing, it will create two FIFOs +("audout" and "vidout") in the directory specified (in this case ".", +meaning the current directory) and will print out information about the +video stream.</P> +<P>The next step is to start the processing application. The following assumes +that the stream is NTSC 640x480 with 32Kbps audio.</P> +<P>To use <B>mencoder</B> you would enter a command like: +<BLOCKQUOTE><CODE> +<PRE> +mencoder -audiofile audout -audio-demuxer 20 -rawaudio rate=32000 \ +-rawvideo on:w=640:h=480:fps=29.97 -ovc lavc -oac mp3lame -o out.avi \ +vidout +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: You must use mencoder 1.0PRE1 or later. <B>mencoder</B> +version 0.9x <EM>WILL NOT WORK!</EM></CAPTION> +</FIGURE> + +Using ffmepg: +<BLOCKQUOTE><CODE> +<PRE> +ffmpeg -f u16le -ar 32000 -ac 2 -i audout -f rawvideo -s 640x480 -r 29.97 \ +-i vidout -vcodec mpeg4 -b 2000 -acodec mp3 -ab 128 out.avi +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Or to play directly using mplayer (again 1.0PRE1 or later is needed): +<BLOCKQUOTE><CODE> +<PRE> +mplayer -audiofile audout -audio-demuxer 20 -rawaudio rate=32000 \ +-rawvideo on:w=640:h=480:fps=29.97 vidout +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you wanted to write the raw data to separate audio and video files for +later processing, the following would work (note the use of --fifosync +for rate-control): +<BLOCKQUOTE><CODE> +<PRE> +$ mythtranscode --chanid 1036 --starttime 2003-10-20T15:30:00 \ +--profile autodetect --fifodir . --fifosync & +$ cat audout > audio.raw & +$ cat vidout > video.yuv +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss23.2">23.2</A> <A HREF="mythtv-HOWTO.html#toc23.2">Using a different window manager</A> +</H2> + +<P>MythTV is not dependent on any particular window manager. If you wish to +run a lightweight window manager, the <CODE>contrib/configfiles/</CODE> directory has an +example of a <CODE>.twmrc</CODE> and <CODE>.fvwmrc</CODE> file you may use.</P> + +<H2><A NAME="capture_resolution_"></A> <A NAME="ss23.3">23.3</A> <A HREF="mythtv-HOWTO.html#toc23.3">What capture resolution should I use? How does video work? </A> +</H2> + +<P>While MythTV allows you to set various GUI and capture resolutions, not +all combinations make sense.</P> +<P>First, analog video signals have a defined vertical resolution. In NTSC, +the video standard specifies that there are 525 vertical scan lines. Once +the "extra" lines are removed (they're used to synchronize the video signal, +and encode closed captioning data), you have 480 horizontal lines stacked +vertically.</P> +<P>In PAL, there are 625 "raw" lines of resolution, with a net of 576 +horizontal lines stacked vertically.</P> +<P>Horizontally, the maximum value allowed for a Bt8X8 chip is 720. However, +due to limitations in the chip and other limitations of broadcast +television, there may not be a noticeable improvement in image quality +beyond 400 or 500 pixels.</P> +<P>With this in mind, there are certain commonly accepted values for +resolution. While other values may be accepted for the vertical +resolution, they will cause scan lines to be repeated or dropped.</P> +<P>From "best" to "worst", in NTSC: +<UL> +<LI>720x480 "DVD" resolution. ReplayTV High and medium resolution</LI> +<LI>704x480 DVD standalone recorder standard resolution</LI> +<LI>640x480 4:3</LI> +<LI>544x480 TiVo Best resolution</LI> +<LI>480x480 SuperVCD (SVCD) Video CD resolution, TiVo High resolution</LI> +<LI>352x480 ReplayTV "Standard" quality, TiVo Basic and Medium resolution, DVD "LP" resolution</LI> +<LI>320x480 </LI> +<LI>544x240</LI> +<LI>480x240 </LI> +<LI>352x240 Video CD (VCD) resolution</LI> +<LI>320x240</LI> +</UL> +</P> +<P>As you can see, the lower quality values are half of the better ones. +720x240 is possible, but isn't a good tradeoff relative to the number of +vertical lines lost. In a PAL country, the you would use values like +720x576 or x288.</P> +<P>The higher resolutions will be more CPU intensive if you're using software +encoding (PVR-250/350 will have minimal host CPU impact even if you're using +720x480). If the CPU is overtaxed, frames will be dropped causing uneven +motion. You will likely see the best results at resolutions which average at +least 10% CPU idle time. You can use system tools such as <CODE>top</CODE> or +<CODE>sar</CODE> to check the CPU % idle while recording. If the CPU average +usage is consistently exceeding 90%, frames will need to be dropped during +peak times when more than 100% of the available CPU would be needed to +process all of the frames.</P> +<P>If you'd like to read more on this, go to the vcdhelp website at +<A HREF="http://www.vcdhelp.com/forum/userguides/94382.php">http://www.vcdhelp.com/forum/userguides/94382.php</A>.</P> + +<H2><A NAME="ss23.4">23.4</A> <A HREF="mythtv-HOWTO.html#toc23.4">MythTV GUI and X Display Sizes</A> +</H2> + +<P>MythTV is designed to be run as dedicated full screen TV application +but can also be run as a desktop application on a computer monitor. Here +are a few consideration for configuring sizes to best suit you needs.</P> + +<H3>X Dimensions</H3> + +<P>For output to a Television, common resolutions are 640x480, 800x600, and +some rare devices support 1024x768. Generally, higher resolutions are +better. However, you may find that you prefer the picture quality at one of +the lower resolutions. Everything in MythTV is scalable and should 'fit' +regardless of the resolution you choose.</P> +<P>Edit your X configuration file, usually <CODE>/etc/X11/XF86Config-4</CODE> for +XFree, or <CODE>/etc/X11/xorg.conf</CODE> for Xorg, so that the resolution you +want to use is listed first in the lists under "Screen". If this resolution +is higher than the resolutions supported by your output device, you will see +a 'panning' effect where moving the mouse to the edge will scroll around a +desktop area which is larger than the display size. If this happens, edit +your X configuration file to match the display size then restart X.</P> + +<H3>MythTV Dimensions</H3> + +<P>From "mythfrontend" go to Setup->Appearance. +The default for the height and width is "0" - this will cause +MythTV to automatically size itself to full screen.</P> +<P>If the MythTV GUI width and height are not 0, mythfrontend uses these GUI +dimensions and is anchored to the upper left corner of the X Desktop. If +the GUI X and/or Y are not 0, the upper left corner is positioned at the +specified coordinates. If the "Run the frontend in a window" box is checked, +the window will have a frame and can then be dragged to any position on the +desktop.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: When the GUI is full screen, you may see windows rapidly +flipping on top of each other. If this happens you will need to set your +window manager to 'Click to Focus' for windows to stack properly.</CAPTION> +</FIGURE> + +The fonts for the GUI and OSD will scale to whatever sizes you use. Most +font sizes can be changed in setup selections or in the .xml files under +<CODE>/usr/local/share/mythtv/</CODE> . Make sure to use fonts large enough +to be read on a TV screen from a distance.</P> +<P>The full screen TV size is based on the X display size. For Xinerama, you +can specify a screen in Setup->General. The TV picture will be stretched +to fit the entire GUI area regardless of the +<A HREF="#capture_resolution_">capture resolutions</A> used. However, during playback, the "W" key can +to used to correct differences between 16:9 and 4:3.</P> + +<H3>Overscan Dimensions</H3> + +<P>Because picture edges can be ragged and screen edges aren't straight, +Television is designed to project an image larger than the physical screen. +This is called "overscan". Underscan is fitting the entire image inside the +screen. Underscan is useful for computer monitors so that toolbars and +scrollbars at the edges can be seen.</P> +<P>For best results, match the X display area as close as possible to the edges +of the physical screen. This can only be adjusted by your tv-out device or +by the settings for the television set. Many sets have these adjustments in +a 'service mode'. If you cannot make these adjustments, there will be black +borders around the edges of the X desktop, MythTV GUI and TV playback.</P> +<P>MythTV has settings for "Overscan" in Setup->Playback. These can not, and do +not, cause the image to display beyond the edge of the X display area. The +purpose of these settings are to cut off rough edges and to expand the image +so that objects will appear to be the same size as a normal overscanned TV +picture.</P> + +<H2><A NAME="backupdb"></A> <A NAME="ss23.5">23.5</A> <A HREF="mythtv-HOWTO.html#toc23.5">Saving or restoring the database </A> +</H2> + +<P>See the <B>mysqldump</B> manpage for more information. +<BLOCKQUOTE><CODE> +<PRE> +$ mysqldump -u mythtv -pmythtv mythconverg -c > mythtv_backup.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>To restore: (assuming that you've dropped the database) +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root +mysql>create database mythconverg; +mysql>exit +$ mysql -u mythtv -pmythtv mythconverg < mythtv_backup.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>You may need to alter the MySQL permissions if this database is being shared +with multiple systems. See the +<A HREF="mythtv-HOWTO-6.html#modify_perm_mysql">Modifying access to the MySQL database for multiple systems</A> section for more +information.</P> + +<H2><A NAME="ss23.6">23.6</A> <A HREF="mythtv-HOWTO.html#toc23.6">Deleting the MySQL database</A> +</H2> + +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Performing this step will remove the entire database. You will lose all of your settings and will need to re-run the mc.sql script +to setup the database structure before running the mythtv-setup program.</CAPTION> +</FIGURE> + +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root +mysql> drop database mythconverg; +mysql> quit +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss23.7">23.7</A> <A HREF="mythtv-HOWTO.html#toc23.7">Moving your data to new hardware</A> +</H2> + +<P>This assumes that you will be moving your data to newer / bigger hardware +and don't want to lose your programs.</P> +<P>The first step is to create a database backup as demonstrated in an earlier +section.</P> +<P>Next, you will extract only the data that is relevant to the programs: +<BLOCKQUOTE><CODE> +<PRE> +$ grep "INSERT INTO record " mythtv_backup.sql > restore.sql +$ grep "INSERT INTO recorded " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO oldrecorded " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO recordedprogram " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO recordedrating " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO recordedmarkup " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO recordedseek " mythtv_backup.sql >> restore.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><B>NOTE</B>: Newer versions of <B>mysqldump</B> place backticks around +the table names. Backticks are not the same as apostrophes! On a typical +North American keyboard, backticks are located to the left of the "1" key, +on the same key as the tilde. Also, because the <B>bash</B> shell may try +to interpret the backticks, make sure you use a \ before each one.</P> +<P>If your <CODE>restore.sql</CODE> file is empty, you'll need to re-run the +commands like this: +<BLOCKQUOTE><CODE> +<PRE> +$ grep "INSERT INTO \`record\` " mythtv_backup.sql > restore.sql +$ grep "INSERT INTO \`recorded\` " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO \`oldrecorded\` " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO \`recordedprogram\` " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO \`recordedrating\` " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO \`recordedmarkup\` " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO \`recordedseek\` " mythtv_backup.sql >> restore.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Note the space after the table name and the ">>" to append to the file for +all but the first <B>grep</B>. "recordedmarkup" and "recordedseek" are +huge and there may be hundreds of thousands of lines if you had lots of +hours of recordings.</P> +<P>After you have moved the data files to the new hardware, configure MythTV +using the <B>mythtv-setup</B> program as you normally would with a +standard MythTV installation.</P> +<P>At this point we will restore the information about your programs back into +the database: +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u mythtv -pmythtv mythconverg < restore.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>After successful insertion of the data you may delete the +<CODE>restore.sql</CODE> file.</P> + +<H2><A NAME="btaudio"></A> <A NAME="ss23.8">23.8</A> <A HREF="mythtv-HOWTO.html#toc23.8">btaudio </A> +</H2> + +<P>btaudio allows you to obtain the audio data from your tuner card directly +over the PCI bus without using a sound card. This is useful if you would +like to use multiple tuner cards in a system without adding a sound card for +each one, or if your existing sound card is not capable of full-duplex +operation.</P> +<P>In order to use btaudio, your tuner card will need certain hardware +installed on it, and that hardware must be wired correctly. The chip that +will allow you to use the btaudio module is the MSP34xx. However, having a +MSP34xx is no guarantee that you will be able to use the btaudio module.</P> +<P>As of 2003-03-31, this is the current list of cards and their status: +Works with btaudio:</P> +<P> +<UL> +<LI>Hauppauge WinTV-radio with dbx-TV stereo, model 401</LI> +<LI>Hauppauge WinTV-Theater, model 495, 498 (Europe)</LI> +<LI>ATI TV Wonder</LI> +</UL> +</P> +<P>The following cards do not work: +<UL> +<LI>Pinnacle Studio PCTV Pro - note: this has a MSP34xx, but it's not +wired correctly to the BT878 chip.</LI> +<LI>ATI TV Wonder VE</LI> +<LI>Leadtek Winfast 2000 XP (PAL, UK and NTSC)</LI> +<LI>I/O Magic PC-PVR. No MSP34xx chip.</LI> +</UL> +</P> +<P>The following cards have been reported to work, but have issues: +<UL> +<LI>Avermedia AVerTV Studio (no digital DSP output, "whiney noise" on +analog)</LI> +</UL> +</P> +<P>Once btaudio loads, it should register additional <CODE>/dev/dsp</CODE> and +<CODE>/dev/mixer</CODE> devices. Typing <CODE>$ dmesg</CODE> will let you know +what's going on.</P> + +<H2><A NAME="ss23.9">23.9</A> <A HREF="mythtv-HOWTO.html#toc23.9">Removing unwanted channels</A> +</H2> + +<P>If <B>mythfilldatabase</B> grabbed a channel which you do not want to +include in your TV listings, you can remove the entries from the grabber +configuration and the MySQL database. This often happens with premium +channels; for example, HBO or Showtime may be available on your cable TV +system, but is scrambled because you're not a subscriber to that channel. +Since you can never watch it, you want to get rid of it.</P> +<P>If you are using the DataDirect service, login to your account at +<A HREF="http://labs.zap2it.com/">http://labs.zap2it.com/</A> to +modify your lineup. Uncheck the boxes for any unwanted channels, and they +will no longer be included in your download.</P> +<P>If you are using a grabber from XMLTV, comment out the channel from the +<CODE>~/.mythtv/<sourcename>.xmltv</CODE> file by inserting the word "not +" (including the space) in front of the unwanted entry. This will prevent +<B>xmltv</B> from grabbing future listings.</P> +<P>Next, delete the unwanted item from the channel table so that it will not +appear in the EPG or when changing channels. To delete the data from the +database we need to perform some steps. First, assuming that HBO is channel +15, we need to find out the internal <CODE>chanid</CODE> used by MySQL: +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root mythconverg +mysql> select chanid from channel where channum=15; ++--------+ +| chanid | ++--------+ +| 1015 | ++--------+ +1 row in set (0.00 sec) +mysql> delete from channel where chanid = 1015; +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Old program data will be removed over the course of a week. However, you may +want to immediately delete any current program listings for the channel that +has been removed: +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root mythconverg +mysql> delete from program where chanid = 1015; +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss23.10">23.10</A> <A HREF="mythtv-HOWTO.html#toc23.10">NFS</A> +</H2> + +<P>You may want to use a central server to store your files. </P> +<P>On the host machine, (in this case, the hostname is "masterbackend") you'll +want to edit your <CODE>/etc/exports</CODE> file and use something like: +<BLOCKQUOTE><CODE> +<PRE> +/var/video (rw) +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>To export the <CODE>/var/video</CODE> directory with read / write privileges.</P> +<P>On the "slave" machine, you'll want to edit the <CODE>/etc/fstab</CODE> file and +add something like: +<BLOCKQUOTE><CODE> +<PRE> +masterbackend:/var/video /var/video nfs rsize=8192,wsize=8192,hard,intr,nfsvers=3,actimeo=0 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Then run <CODE># mount -a</CODE> to re-read the file to mount the file system.</P> +<P>In this case, the source is a machine called "masterbackend" which is +exporting the directory "/var/video", which we're mounting locally at +"/var/video". The rsize and wsize options are used to increase the +performance of NFS; "hard,intr" is there because that's the recommendation +of the NFS-HOWTO, the nfsvers is required for filesizes over 2GB and actimeo +is used to turn off file attribute caching. Attribute caching for a shared +media point causes problems; you always want to see the latest state of the +directory and files. See +<A HREF="http://www.mythtv.org/wiki/index.php/Optimizing_Performance">http://www.mythtv.org/wiki/index.php/Optimizing_Performance</A> for +additional information regarding performance optimization.</P> + +<H2><A NAME="ss23.11">23.11</A> <A HREF="mythtv-HOWTO.html#toc23.11">Automatically starting mythfrontend at system boot time</A> +</H2> + +<P>Here's an example submitted to the mythtv-dev list by Pat Pflaum +<A HREF="mailto:pat@netburp.com">mailto:pat@netburp.com</A> using fvwm: +<BLOCKQUOTE><CODE> +<PRE> +$ cat > .xinitrc +fvwm & +mythfrontend +^D +$ cat > .fvwmrc +Style myth* NoTitle, NoHandles, Sticky, WindowListSkip, SloppyFocus, GrabFocus, BorderWidth 0 +^D +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The following also works with blackbox: +<BLOCKQUOTE><CODE> +<PRE> +$ cat > .xinitrc +xset -dpms s off & +irxevent & +mythfrontend & +blackbox +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Make sure that your <CODE>.blackboxrc</CODE> file has: +<BLOCKQUOTE><CODE> +<PRE> +session.screen0.focusNewWindows: True +session.screen0.focusModel: SloppyFocus +</PRE> +</CODE></BLOCKQUOTE> + in it.</P> +<P> +<A NAME="mythbackend_autostart"></A> </P> +<H2><A NAME="ss23.12">23.12</A> <A HREF="mythtv-HOWTO.html#toc23.12">Automatically starting mythbackend at system boot time</A> +</H2> + +<H3>Red Hat And Mandriva</H3> + +<P>Here's a method for automatically starting mythbackend submitted by Mike +Thomson ( +<A HREF="mailto:linux@m-thomson.net">mailto:linux@m-thomson.net</A>) and Stu Tomlinson ( +<A HREF="mailto:stu@nosnilmot.com">mailto:stu@nosnilmot.com</A>).</P> +<P>Copy the files from the MythTV <CODE>contrib</CODE> directory or from Mike's web +site ( +<A HREF="http://m-thomson.net/mythtv/">http://m-thomson.net/mythtv/</A>) as follows:</P> +<P><CODE>etc.rc.d.init.mythbackend</CODE> should be made executable and copied to +<CODE>/etc/rc.d/init.d/</CODE>: +<BLOCKQUOTE><CODE> +<PRE> +$ cd contrib +$ su +# chmod a+x etc.rc.d.init.d.mythbackend +# cp etc.rc.d.init.d.mythbackend /etc/rc.d/init.d/mythbackend +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><CODE>etc.sysconfig.mythbackend</CODE> should be copied to +<CODE>/etc/sysconfig/</CODE>: +<BLOCKQUOTE><CODE> +<PRE> +$ cd contrib +$ su +# cp etc.sysconfig.mythbackend /etc/sysconfig/mythbackend +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Edit <CODE>/etc/sysconfig/mythbackend</CODE> if you want to change the defaults +(the userid that should start mythbackend, location of the logfile and (if +required) the name and location of the mythbackend binary).</P> +<P>Use <B>chkconfig</B> to make sure the script is called when +entering runlevels 3, 4 or 5: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# chkconfig --level 345 mythbackend on +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P> +<A NAME="logrotate"></A> </P> +<H3>Log files </H3> + +<P>By default, the log file for mythbackend will be written to +<CODE>/var/tmp/mythbackend.log</CODE>. This has been tested and is known to work +on Mandriva and Red Hat, but many people prefer to place logs under +<CODE>/var/log/</CODE>.</P> +<P>To do this, create a group called <CODE>mythtv</CODE> (or anything you prefer) +and add your usual MythTV users to that group. If you changed the user that +starts mythbackend from the default of root you <EM>must</EM> perform this +step.</P> +<P>Create the directory <CODE>/var/log/mythtv</CODE> and set its +permissions as follows: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# mkdir /var/log/mythtv +# chown root:mythtv /var/log/mythtv +# chmod 0775 /var/log/mythtv +# exit +$ ls -ld /var/log/mythtv +drwxrwxr-x 2 root mythtv 4096 Apr 28 21:58 /var/log/mythtv/ +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Create a <CODE>mythtv</CODE> file in <CODE>/etc/logrotate.d</CODE>: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# cat > /etc/logrotate.d/mythtv +# Set default values for all log files first... + +# Rotate the logs once a week, or more frequently if they +# exceed 10Mb in size (size is checked daily). +weekly +size 10M + +# 'copytruncate' is used for logs generated by +# currently-running programs that should not be restarted +# (and can't be signalled to start a new log) after the +# rotation. It duplicates the existing log file and then +# sets the length of the existing file to 0. The only time +# this would break would be if the program writing the log +# was using lseek. +copytruncate + +# After rotating the files, leave the most recent rotated +# copy alone but gzip everything else to save space. +compress +delaycompress + +# If a log isn't present then don't worry about it. +missingok + +# Don't rotate an empty file. +notifempty + +# end of the global options + +/var/log/mythtv/mythbackend.log /var/log/mythtv/mythfrontend.log { + # Keep logs until they are 2 months old or the number of + # logs reaches 12. If the log files stay small, the age will + # kick in first and you'll only have 8 log files. If they + # get larger than 10Mb then you won't keep all 60 days. + rotate 12 + maxage 60 +} + +# Different options for mythfilldatabase: +/var/log/mythtv/mythfilldatabase.log { + rotate 2 +} +^D +# +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3>Mandriva </H3> + +<P>Mandriva adds one more twist in the form of the <CODE>msec</CODE> utility, +which runs regularly and (at the default or any higher security level) sets +permissions on many files, including those under <CODE>/var/log</CODE>.</P> +<P>To tell msec about the MythTV log files and their directory, you need to +edit the <CODE>/etc/security/msec/perm.local</CODE> file to include the +following: +<BLOCKQUOTE><CODE> +<PRE> +# /etc/security/msec/perm.local +# Local overrides to the msec program +# +# Full file path user.group permissions +/var/log/mythtv/ root.mythtv 775 +/var/log/mythtv/* root.mythtv 664 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>A copy of the above has been included in the contrib/ directory. You may +add it by typing: +<BLOCKQUOTE><CODE> +<PRE> +$ cd contrib +$ su +# cat etc.security.msec.perm.local >> /etc/security/msec/perm.local +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Finally run the <CODE>msec</CODE> tool to check and implement your +changes. +<BLOCKQUOTE><CODE> +<PRE> +$ su +# msec +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: msec can only <EM>reduce</EM> the permissions of files, so if +you don't get the results you expect, check that you're not asking +<CODE>msec</CODE> to add missing permissions to the files or directories you +created.</CAPTION> +</FIGURE> +</P> +<H3>Gentoo</H3> + +<P>The portage file for MythTV has scripts that will allow you to run +mythbackend at startup.</P> +<P>To run mythbackend as a daemon which starts at boot time: +<BLOCKQUOTE><CODE> +<PRE> +# rc-update add mythbackend default +</PRE> +</CODE></BLOCKQUOTE> + +To stop mythbackend as a daemon: +<BLOCKQUOTE><CODE> +<PRE> +# /etc/init.d/mythbackend stop +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>To obtain a list of options: +<BLOCKQUOTE><CODE> +<PRE> +# /etc/init.d/mythbackend +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="advanced_backend_config"></A> <A NAME="ss23.13">23.13</A> <A HREF="mythtv-HOWTO.html#toc23.13">Advanced Backend Configurations </A> +</H2> + +<P>MythTV is flexible in the way that you define multiple backend tuner +configurations. The only hard-and-fast rule is that the Master backend +<EM>must</EM> have a capture device defined, but shouldn't imply that the +capture device in the Master backend must be the first capture card defined in the +database.</P> +<P>One example of an advanced configuration is the round-robin scheme. Rather +than defining all of the cards on the master, you could first go into +mythtv-setup on the master to define globals such as the general configuration +and the channel lineup but not the host-specific configuration item like the +capture card. In this example, we will use a 4 tuner configuration, where two +slaves have one card each and the master has two. +<OL> +<LI>Add the first capture card on one of the slaves. Complete the +configuration, connecting the input source to the card. This will get +cardid #1 in the database. Exit mythtv-setup.</LI> +<LI>Configure the first capture card on the master backend. This will get +cardid #2 in the database. Exit mythtv-setup.</LI> +<LI>Configure the first capture card on the second slave. This will be +cardid #3 in the database. Exit mythtv-setup.</LI> +<LI>Configure the second capture card on the master backend. This will +get cardid #4 in the database. Exit mythtv-setup.</LI> +</OL> +</P> +<P>Using this scheme, the master backend will not use both capture cards until +one of the following happens: +<UL> +<LI>There are four recordings scheduled for the same time</LI> +<LI>Both slaves are unavailable</LI> +</UL> +</P> +<P>The scheduler in MythTV checks whether an encoder is available; if a slave +backend isn't running, its encoder isn't available, so the scheduler will +look for the next available encoder. This makes MythTV very flexible; slave +tuners can come and go, and as long as there are enough tuners for what +you'd like to record it doesn't matter which tuner in particular is going to +be used.</P> +<P>Using this round-robin scheme along with a shared storage directory like +NFS and enabling the Master Backend Override setting will allow you to view +content even if the slave backend that recorded a program is not available.</P> + +<H2><A NAME="ss23.14">23.14</A> <A HREF="mythtv-HOWTO.html#toc23.14">Using the transcoder</A> +</H2> + +<P>MythTV's built-in transcoder re-encodes recordings from one codec to +another. The transcoder has three primary uses; it can transcode MPEG-2 +files captured using a hardware encoder (PVR cards, DVB cards, ATSC HD, +etc.) to MPEG-4, it can be used to transcode RTjpeg files (usually only used +on systems that can not real-time encode to MPEG-4 using a framegrabber) to +MPEG-4, and finally it can be used to remove commercials from a MPEG-2 file +while leaving the file in MPEG-2 format.</P> +<P>When MythTV transcodes a file to MPEG-4 or RTjpeg the resulting file format +is NuppelVideo (nuv). NuppelVideo is a container which provides a method of +keeping the audio and video in sync throughout the recording, which is why +it is used instead of the <CODE>.avi</CODE> format. You may have difficulty +playing <CODE>.nuv</CODE> files in non-MythTV systems.</P> + +<P>The original file is removed when the transcoding process is complete. +Unless you're sure that you will be satisfied with the result you may want +to enable the <B>mythtv-setup</B> option which causes <B>mythbackend</B> +to keep the original file after transcoding. This option is on the second +page of the General section in mythtv-setup. Enabling this allows you to +compare the two files and restore the original if you like. Outside of the +initial setup phase it usually isn't necessary to leave this option enabled. +A recording can be transcoded in two ways:</P> +<P> +<UL> +<LI>Automatically transcode the file once it has completed +recording.</LI> +<LI>Manually choosing to transcode a recording, usually after +importing a cutlist or manually marking commercials to be +removed.</LI> +</UL> +</P> +<P>The second method can be used on files that have already been transcoded (or +files which were are already in the desired format), so only the frames +immediately following a cut section will be re-encoded, resulting in a +minimal loss of quality when removing commercials with the added benefit of +being extremely quick.</P> +<P>The current transcoding system has a lot flexibility, but there are +a number of steps involved in setting it up. In order to +automatically transcode a given recording you must do the following: +<OL> +<LI>Configure recording profile for your capture source and enable +transcoding on one or more profiles.</LI> +<LI>Configure one or more transcoding profiles.</LI> +<LI>Create or alter existing scheduled recordings to enable +transcoding for that recording.</LI> +</OL> +</P> + +<H3>Configuring Recording Profiles to Allow Transcoding</H3> + +<P>Enter the Utilities/Setup > Setup > TV Settings > Recording Profiles +section in <B>mythfrontend</B>. Choose the option that corresponds to +your capture source (ignore the Transcoders for now.) Choose the quality +profile you are interested in using for transcoding. Ensure that "Enable +auto-transcode after recording" is checked. </P> + +<H3>Configure Transcoding Profiles</H3> + +<P>Enter the Recording Profiles > Transcoders menu. There are three quality +settings to choose from and a two special Autodetect settings. Later, when +scheduling recordings you'll have to choose one of Autodetect, High, Medium, +and Low Quality transcode settings in addition to the recording profile we +set up above. If you choose the Autodetect transcoding profile for a +recording, MythTV will use the "Autodetect from RTjpeg/MPEG-4" profile for +recordings which are RTjpeg/MPEG-4 files. Otherwise, it will use the +"Autodetect from MPEG-2" profile provided it's an MPEG-2 recording. If you +choose one of the others (High, Medium, Low) it will use the settings in +that profile regardless of the codec of the original recording.</P> +<P>There are a number of options for transcoding but the simplest is to enable +lossless transcoding (the first option) which subsequently removes all other +options. Enabling lossless encoding simply removes commercials (if you've +marked them) and attempts to clean up MPEG-2 streams. Note that with this +option MythTV will not apply any sort of filters and will only attempt to +normalize the stream into something cleaner and less likely to have trouble +with other less forgiving MPEG-2 hardware/software (including players, video +editors, etc.)</P> +<P>If you enable resizing of the recording the next page has the settings for +choosing the final resolution. MythTV will scale the video as appropriate, +not crop it to this resolution.</P> +<P>The final two pages allow configuration of the video and audio codecs. +Although RTjpeg is an option for video codec there is no reason to transcode +<EM>to</EM> this format because it will produce larger files than MPEG-4 and +the recording will take <EM>more</EM> CPU power to play back. The MPEG-4 +settings are described in the documentation for the <B>ffmpeg</B> project +at +<A HREF="http://ffmpeg.sourceforge.net/ffmpeg-doc.html">http://ffmpeg.sourceforge.net/ffmpeg-doc.html</A>. It's a matter of +trial and error to discover which settings achieve a good compromise between +size and quality.</P> +<P>If you wish to return to the default settings, they are Bitrate: 2200-2500, +MaxQ: 2, MinQ: 15, MaxQDiff: 3, and "Scale bitrate for frame size" is +enabled. The other options are unchecked. </P> + +<H3>Create/Alter Scheduled Recordings to Enable Transcoding</H3> + +<P>Transcoding is actually enabled on a per-recording basis. Two things +must be true before any given recording will be auto-transcoded, however. +The first is that the recording must have been made with a recording profile +that has auto-transcode enabled. Under "Storage Options" for the recording +you must set the "Record using the "X" profile" to the profile you +configured in the first step. In addition, under the "Post Recording +Options" section of the recording you must also set "Transcode new +recordings." This is also where you specify the Transcoding profile to use +(Auto, High, Medium, Low.)</P> +<P>It may not be obvious from above but the flexibility of this system is +primarily to make it possible to auto-transcode a show recorded via one +source (ie: pcHDTV 3000), and not transcode that same show if it's recorded +on another kind of card (ie: PVR-250.) There are other uses however. You +could have a PVR-250 and a V4L card. You may want to transcode the MPEG-2 +from the PVR-250 but there is no need to transcode the recordings made with +the V4L card, as it's already likely to be MPEG-4.</P> +<P>As an example, you could configure the Default profile for "Hardware DVB +Encoders" (the profile group used for DVB cards, including ATSC cards like +the pcHDTV 3000) to "Enable auto-transcoding". In the Default profile for +MPEG-2 Encoders (PVR cards) you'd leave "Enable auto-transcoding" unchecked. +For programs that are available on both kinds of cards you'd set the +recording profile to Default and enable auto-transcoding in the record +settings. Then you pick your transcoding profile. The result is that when +a program is recorded on your DVB card, it will get transcoded. When it +plays on a channel available via your PVR card, it won't be.</P> + +<H3>Manual Transcoding</H3> + +<P>Manually transcoding is activated while watching a show by hitting 'x', +from the OSD menu by choosing the Transcode option, or by choosing Job +Options/Transcode from the info menu from the Watch or Delete +Recordings screens.</P> +<P>The transcoding profile used for manual transcoding is whatever was set when +the recording was originally configured, even if you didn't enable +auto-transcoding. The only way to change what transcoding profile will be +used is to alter the transcoder column in the recorded table in the +database. The transcoder column contains a number which corresponds with +the id column in the recordingprofiles table. You can find out the id +number for each profile in the transcoder group with an SQL command like:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +mysql> select r.* from recordingprofiles r,profilegroups p where p.name='Transcoders' and p.id=r.profilegroup; ++----+----------------+------------+------------+--------------+ +| id | name | videocodec | audiocodec | profilegroup | ++----+----------------+------------+------------+--------------+ +| 21 | RTjpeg/MPEG4 | MPEG-4 | MP3 | 6 | +| 22 | MPEG2 | MPEG-4 | MP3 | 6 | +| 27 | High Quality | MPEG-4 | MP3 | 6 | +| 28 | Medium Quality | MPEG-4 | MP3 | 6 | +| 29 | Low Quality | MPEG-4 | MP3 | 6 | ++----+----------------+------------+------------+--------------+ +5 rows in set (0.01 sec) + +mysql> +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Armed with the knowledge of what the profile ID's are you can also choose to +run mythtranscode from the command line and explicitly specify the transcoder +profile. Run <CODE>mythtranscode --help</CODE> for usage information.</P> + +<H2><A NAME="ss23.15">23.15</A> <A HREF="mythtv-HOWTO.html#toc23.15">Changing your hostname</A> +</H2> + +<P>If you need to change the name of the computers used with MythTV you'll +need to perform a sequence of steps. There are a number of pieces of +information that MythTV keeps track of which are tied to the hostname of the +box, so changing the hostname involves altering the name in the +operating system and in the MySQL database. In the examples below, the old +name of the system was "frontend1" and we're going to change it to +"kidsroom".</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Changing the hostname using direct SQL update commands will +break things. You <EM>MUST</EM> use this indirect method.</CAPTION> +</FIGURE> + </P> +<P>1. Stop all backends. If you run <B>mythbackend</B> from a terminal +session, press control-c. If your backends are started with an init +script, you would do something like the following: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# /etc/init.d/mythbackend stop +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>2. Change the hostname.</P> +<P>For Red Hat and derived distributions, edit the +<CODE>/etc/sysconfig/network</CODE> file. Look for +<CODE>HOSTNAME=frontend1</CODE> and change this to +<CODE>HOSTNAME=kidsroom</CODE> or whatever you'll be using. For other +distributions, refer to the documentation, such as the +<PRE> +hostname(1) +</PRE> + man page.</P> + +<P>To alter the +hostname in the current session, run: +<BLOCKQUOTE><CODE> +<PRE> +# hostname kidsroom +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>3. Dump the database. +<BLOCKQUOTE><CODE> +<PRE> +$ mysqldump -u mythtv -pmythtv mythconverg -c > mythtv_backup.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>4. Rename the host in the database. First, ensure that the new hostname +you'll be using isn't already in the database. +<BLOCKQUOTE><CODE> +<PRE> +$ grep kidsroom mythtv_backup.sql +</PRE> +</CODE></BLOCKQUOTE> + +Now we're actually going to change the name. The following should all be +typed on the same line: +<BLOCKQUOTE><CODE> +<PRE> +$ cat mythtv_backup.sql | sed s/\'frontend1\'/\'kidsroom\'/g >> mythtv_restore.sql +</PRE> +</CODE></BLOCKQUOTE> + +If you don't feel comfortable using <B>sed</B>, you can open the +<CODE>mythtv_backup.sql</CODE> file in a text editor and perform a global search +and replace. When saving the file, make sure you use the new name, +<CODE>mythtv_restore.sql</CODE> or the rest of the steps below will fail.</P> +<P>5. Drop and recreate the database. +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root +mysql>drop database mythconverg; +mysql>create database mythconverg; +mysql>exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>6. Restore the database using your edited version. +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u mythtv -pmythtv mythconverg < mythtv_restore.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you are running slave backends or frontends, don't forget to re-enable +access as detailed in +<A HREF="mythtv-HOWTO-6.html#modify_perm_mysql">Modifying access to the MySQL database for multiple systems</A>. </P> +<P>7. Start the backends. If you use init scripts, do the following, otherwise +start them from terminal consoles. +<BLOCKQUOTE><CODE> +<PRE> +# /etc/init.d/mythbackend start +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>8. Quit and restart all frontends. Delete the <CODE>mythtv_backup.sql</CODE> +and <CODE>mythtv_restore.sql</CODE> files.</P> + +<H2><A NAME="ss23.16">23.16</A> <A HREF="mythtv-HOWTO.html#toc23.16">Can I run MythTV on my TiVo?</A> +</H2> + +<H2><A NAME="ss23.17">23.17</A> <A HREF="mythtv-HOWTO.html#toc23.17">Can I run MythTV on my ReplayTV?</A> +</H2> + +<P>No.</P> +<P>While it is true that the TiVo runs the Linux kernel, and TiVo has released +their changes to the kernel under the GPL, the TiVo is <EM>not</EM> a +general-purpose computer, and there is no programming information available +for the custom hardware contained within a TiVo. TiVo is under no +obligation to release the source code to their <EM>application</EM>.</P> +<P>The ReplayTV runs VxWorks, a Real Time Operating System from Wind River +Systems.</P> +<H2><A NAME="ss23.18">23.18</A> <A HREF="mythtv-HOWTO.html#toc23.18">Can a wireless connection be used between the frontend and the backend?</A> +</H2> + +<P>Yes, assuming that your wireless connection has sufficient bandwidth to +maintain the datarate between the frontend and the backend. 802.11b should +be sufficient if the encoded bitrate of the content is less than the +datarate of your wireless connection, which in the case of 802.11b would be +approximately 4 Mbps. (The advertised rate of 11Mbps gives an actual +throughput of 4 Mbps.) 802.11a and 802.11g, if operating in their high-speed +modes, or proprietary 802.11b "Turbo" schemes should be adequate. Multiple +wireless frontends, poor signal strength or other factors can severely +impact the viewing experience on the frontend.</P> + +<H2><A NAME="ss23.19">23.19</A> <A HREF="mythtv-HOWTO.html#toc23.19">How can I burn shows that I have recorded to a DVD?</A> +</H2> + +<P>Use the mytharchive plugin.</P> + +<H2><A NAME="ss23.20">23.20</A> <A HREF="mythtv-HOWTO.html#toc23.20">Using the DBoxII within MythTV</A> +</H2> + +<P>The configuration of the DBoxII for use within MythTV is tricky (as of +May 16 2005), that's why it's covered here. Your DBoxII has to be running +linux and the Neutrino GUI instead of the stock BetaNova firmware. For +further information, please refer to +<A HREF="http://www.tuxbox.org">http://www.tuxbox.org</A>. Additionally, you need to enable the SPTS +mode in Neutrino.</P> +<P> +<UL> +<LI>Add a new "Capture Card" in the setup. The "Card type" is "DBOX2 Input", +the other values have to be adjusted according to your setup. +The default values, except for the "DBOX2 host ip", should work fine.</LI> +<LI>Define a new video source. It doesn't need to be configured, +you just need to define it. MythTV grabs the EPG from the DBoxII.</LI> +<LI>Connect the DBoxII to the newly defined input source in "input connections".</LI> +<LI>Since channel scanning is not implemented yet, you need to define channels +in the "Channel Editor". Make sure that you use the same value for +"Channel Name" as on the DBoxII. You can get a list of available +channels from the web interface of Neutrino at http://ip-of-your-box:80/. +Associate the channel with your new video source and repeat when needed.</LI> +</UL> +</P> +<P>You may leave the Setup now and proceed as usual.</P> + +<H2><A NAME="ss23.21">23.21</A> <A HREF="mythtv-HOWTO.html#toc23.21">What do the icons on the Watch Recordings screen mean?</A> +</H2> + +<P>Press "1" or F1 to get a popup.</P> +<H2><A NAME="ss23.22">23.22</A> <A HREF="mythtv-HOWTO.html#toc23.22">What do the letters mean when I change channels?</A> +</H2> + +<P>These letters let you know what's going on with the backend as it tries +to tune to a channel.</P> +<P>Lower case = seen</P> +<P>Upper Case = seen & good +<UL> +<LI>l/L = Lock : This could be seen by PVR-250/BTTV users</LI> +<LI>a/A = PAT : Any recording transmitted in MPEG </LI> +<LI>m/M = PMT : Any recording transmitted in MPEG </LI> +<LI>g/G = MGT : ATSC only</LI> +<LI>v/V = VCT : ATSC only</LI> +<LI>n/N = NIT : DVB only</LI> +<LI>s/S = SDT : DVB only</LI> +</UL> +</P> +<H2><A NAME="ss23.23">23.23</A> <A HREF="mythtv-HOWTO.html#toc23.23">What is the difference between the various Hauppauge PVR models?</A> +</H2> + +<P>This is covered in the hardware section, and extensively covered on the +Hauppauge website. ( +<A HREF="http://www.hauppauge.com/pages/compare_pvr.html">http://www.hauppauge.com/pages/compare_pvr.html</A>) Please check the +Hauppauge website for the most accurate information.</P> +<P>A PVR-150 comes in a number of versions: +<UL> +<LI>The PVR-150 (Model 1045) is the retail kit. It comes with a remote +control and an IR Blaster. It does not have a radio tuner.</LI> +<LI>The PVR-150 MCE (Model 1042) will usually come in a plain white box and is +sold as an OEM device. It does not come with a remote control, since it's +usually used as the second, third, etc capture device.</LI> +<LI>The PVR-150 MCE Kit (Model 1062) does not have a radio tuner and +comes with a Microsoft Media Center remote control instead of Hauppauge's.</LI> +<LI>The PVR-150 low profile (Model 1086) is a low-profile card. It has a +radio tuner and is approximately half the height of a standard card. +However, it comes with a low-profile PCI bracket, so it is not suitable for +use in a standard PCI slot without removing the bracket, which may not be +worth the trouble.</LI> +</UL> +</P> +<P>A PVR-250 (Model 980) is a retail kit which comes with an IR receiver and a +remote control.</P> +<P>The PVR-250 MCE (Model 975) contains a FM radio tuner. The PVR-250 MCE does +not contain a IR receiver or a remote.</P> +<P>The PVR-250 Rev 1 contained an MPEG-2 decoder. However, this function was +not connected to any output jacks, and there doesn't appear to be any way to +pull decoded video from the card, so it's a fairly useless feature.</P> +<P>The PVR-350 (model 990) has the features of the PVR-250 as well as being +able to decode MPEG-2. The encode and decode functions may be used +simultaneously. The MPEG-2 decoder function gives superior video quality +compared to what you'll find on a standard video card. However, the decoder +function is only available once Linux has started, so you will not see any +boot-time messages. Also, the card is not capable of resolutions higher +than 720x480, so it cannot be used with HDTV. Make a conscious decision +(and ask for advice on the mailing list) that you want to tradeoff potential +HDTV use in the future compared to video quality.</P> +<P>The X-driver for the PVR-350 support playback using Xv efficiently but does +not support any other 2D or 3D acceleration. For some application this may +place a large load on the host CPU, some will run without any problem and +others (mplayer, xine, xmame etc.) should be configured to utilize the Xv +interface.</P> +<P>Note that for the PVR-350 there are some +<A HREF="mythtv-HOWTO-3.html#PVR-350">considerations</A> +regarding the way audio is handled.</P> +<P>The PVR-500 is a dual-encoder version of the PVR-150 card, so you can +simultaneously record two different programs at the same time, because there +are two encoder chips on the PCI card. Hauppuage has also installed an +onboard splitter, so you can use one COAX to feed both tuners. Current +versions of the PVR-500 should come with an adapter to allow you to connect +a second S-Video or composite input, but this will take up a second PCI +slot. Early adopters may need to purchase this item separately.</P> + +<H2><A NAME="ss23.24">23.24</A> <A HREF="mythtv-HOWTO.html#toc23.24">Changing channels on an external Set Top Box</A> +</H2> + +<P>If you need to use an external Set Top Box (STB), such as for satellite +TV or for digital cable you will need some way for MythTV to tell the STB to +switch to a new channel. There are several methods: +<OL> +<LI>Use an IR blaster. An IR blaster is an infrared transmitter connected +to your computer. When MythTV needs to change channels it will send IR +pulses, thereby emulating a remote control.</LI> +<LI>Use a direct serial connection. Some STB's have a serial port on the +back, although it may not look like a serial port. It may look like a phone +jack, or a strange VGA connector. It may be labeled "Low Speed Data". A +direct serial connection is more reliable than an IR blaster. Not all STB's +that have a Low Speed Data port have it enabled; you may need to convince +your service provider to turn it on. Stating that you have a Tivo may help; +the Tivo has a direct-connect capability.</LI> +<LI>Use a firewire connection. There is a <CODE>6200ch.c</CODE> in the MythTV +contrib directory which may work for you.</LI> +</OL> +</P> +<H2><A NAME="ss23.25">23.25</A> <A HREF="mythtv-HOWTO.html#toc23.25">Configuring one machine to flag all commercials</A> +</H2> + +<P>Commercial flagging can be CPU intensive. By default, the backend that +created a recording is the one which will flag commercials. You may wish to +use a different machine to run commercial flagging.</P> +<P>On the slower machine:</P> +<P>Start the mythtv-setup program. Advance through the pages until you get to +the Job Queue page. Turn off the setting that says "Allow Commercial +Detection jobs", thereby preventing any commercial flagging jobs from +running on this machine.</P> +<P>Next, make sure that "Run Jobs only on original recording host" is turned +OFF so that new jobs are allowed to run anywhere.</P> +<P>Restart <B>mythbackend</B> since it only reads this setting when it starts +up.</P> +<P>On the faster machine:</P> +<P>Start the <B>mythtv-setup</B> program. Advance through the pages until +you get to the Job Queue page. Ensure that "Allow Commercial Detection +jobs" is turned ON for this machine.</P> +<P>Run <B>mythjobqueue</B>. <B>mythjobqueue</B> will examine the JobQueue +and run any jobs it finds. <B>mythjobqueue</B> should be left running so +that it will pick up any new commercial flagging jobs that are added to the +queue, otherwise new jobs will be added to the queue and your programs won't +be flagged until you run manually run <B>mythjobqueue</B>.</P> +<P>Using this technique it's possible to add commercial flagging machines as +needed, even on systems that aren't running a backend. It's also possible +to run the commercial flagger in a virtual machine environment such as +VMWare.</P> + +<HR> +<A HREF="mythtv-HOWTO-24.html">Next</A> +<A HREF="mythtv-HOWTO-22.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc23">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-24.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-24.html new file mode 100644 index 0000000..32a0eb5 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-24.html @@ -0,0 +1,452 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: Example Configurations.</TITLE> + <LINK HREF="mythtv-HOWTO-23.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc24" REL=contents> +</HEAD> +<BODY> +Next +<A HREF="mythtv-HOWTO-23.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc24">Contents</A> +<HR> +<H2><A NAME="s24">24.</A> <A HREF="mythtv-HOWTO.html#toc24">Example Configurations.</A></H2> + +<H2><A NAME="LVM"></A> <A NAME="ss24.1">24.1</A> <A HREF="mythtv-HOWTO.html#toc24.1">Logical Volume Manager (LVM) </A> +</H2> + +<P>LVM greatly increases the flexibility you have in managing your storage +than traditional physical partitions. This section will provide some brief +notes on how to use LVM to create storage space for your video files and how +to add additional disk space in the future. There's lots more that can be +done with LVM, so check the LVM HOWTO +<A HREF="http://tldp.org/HOWTO/LVM-HOWTO/">http://tldp.org/HOWTO/LVM-HOWTO/</A> document for details.</P> + +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: If you are running MythTV 0.21 and you are using LVM to +create one large filesystem to store your recordings, it's no longer +recommended that you go the LVM route. The preferred solution is to use +<A HREF="mythtv-HOWTO-9.html#storagegroups">Storage Groups</A>. They're more flexible and less +likely to lose all of your recordings if you have a drive failure.</CAPTION> +</FIGURE> +</P> +<P>If you don't understand how to partition a drive, or how to change the +partition type you should stop and look at documentation on how to perform +these steps.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>BIG FAT WARNING</B>: Using an incorrect parameter can make your files +inaccessible, prevent your computer from booting, etc. Be careful!</CAPTION> +</FIGURE> +</P> +<P>Make sure your kernel configuration includes LVM support or that it's +available as a module. Today, most vendors include this by default. You'll +also want to ensure that you have a copy of the LVM utilities; check your +distribution, or get the latest versions from +<A HREF="http://www.sistina.com/products_lvm.htm">http://www.sistina.com/products_lvm.htm</A> and build them manually.</P> +<P>Check that the <B>vgscan</B> program is being run at some point during +your boot sequence - most distributions do this by default. Look for a +message during boot up that looks like this: <CODE>vgscan -- reading all +physical volumes (this may take a while...)</CODE> If you don't see any +messages during boot, you may need to install a LVM init script or confirm +that you have all of the LVM packages installed from your distribution.</P> +<P>LVM uses a few concepts you should be familiar with before starting. +<UL> +<LI>PV (Physical Volume). The actual partition on the hard drive.</LI> +<LI>VG (Volume Group). The aggregation of all the PVs make a VG.</LI> +<LI>LV (Logical Volume). Subdivision of the pool of space available in +the VG into individual chunks, like /usr, /var/video, etc.</LI> +</UL> +</P> +<P>The following example assumes that you want to create a LVM partition from a +chunk of space in /dev/hda5, using a reiserfs filesystem and mounted on +/var/video. You later decide to extend this filesystem by adding a new disk: +/dev/hdb.</P> +<P>You need to create at least one LVM partition for a physical volume. Use +<B>fdisk</B> or your favorite partition editor to set the type to LVM +(0x8e). If you're using an entire disk, create one big partition rather than +using the device itself. e.g. use /dev/hdb1 not /dev/hdb. </P> +<P>In the following example, you have a 15GB disk. The first 6GB are set as +your boot partition. <CODE>/dev/hda2</CODE> was added as an extended partition, +and within that partition you created the <CODE>/dev/hda5</CODE> linux (ext2) +partition.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +# fdisk /dev/hda + +The number of cylinders for this disk is set to 1823. +There is nothing wrong with that, but this is larger than 1024, +and could in certain setups cause problems with: +1) software that runs at boot time (e.g., old versions of LILO) +2) booting and partitioning software from other OSs + (e.g., DOS FDISK, OS/2 FDISK) + +Command (m for help): p + +Disk /dev/hda: 15.0 GB, 15000330240 bytes +255 heads, 63 sectors/track, 1823 cylinders +Units = cylinders of 16065 * 512 = 8225280 bytes + + Device Boot Start End Blocks Id System +/dev/hda1 * 1 764 6136798+ 83 Linux +/dev/hda2 765 1823 8506417+ 5 Extended +/dev/hda5 765 1823 8506417 83 Linux + +Command (m for help): t +Partition number (1-6): 5 +Hex code (type L to list codes): 8e + +Command (m for help): p + +Disk /dev/hda: 15.0 GB, 15000330240 bytes +255 heads, 63 sectors/track, 1823 cylinders +Units = cylinders of 16065 * 512 = 8225280 bytes + + Device Boot Start End Blocks Id System +/dev/hda1 * 1 764 6136798+ 83 Linux +/dev/hda2 765 1823 8506417+ 5 Extended +/dev/hda5 765 1823 8506417 8e Linux LVM + +Command (m for help): w + +# +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Create the LVM physical volume from the partitions (repeat if you have +multiple partitions to use): +<BLOCKQUOTE><CODE> +<PRE> +# pvcreate /dev/hda5 +</PRE> +</CODE></BLOCKQUOTE> + +Create a LVM volume group out of this physical volume called "VGforMyth" that is +allocated in chunks that are a multiple of 64MB +<BLOCKQUOTE><CODE> +<PRE> +# vgcreate VGforMyth -s 64m /dev/hda5 +</PRE> +</CODE></BLOCKQUOTE> + +Create a logical volume of 5GB called "video" and then create the reiserfs +filesystem and mount it: +<BLOCKQUOTE><CODE> +<PRE> +# lvcreate --name video --size 5G VGforMyth +# mkreiserfs /dev/VGforMyth/video +# mount /dev/VGforMyth/video /var/video +</PRE> +</CODE></BLOCKQUOTE> + +Now create a 3GB volume for mythmusic files if you like: +<BLOCKQUOTE><CODE> +<PRE> +# lvcreate --name music --size 3G VGforMyth +# mkreiserfs /dev/VGforMyth/music +# mount /dev/VGforMyth/music /var/music +</PRE> +</CODE></BLOCKQUOTE> + +Display the volume group status: +<CODE># vgdisplay -v</CODE></P> +<P>Now, lets suppose you want to add a 60GB hard disk to the system as hdb and +allocate 50GB of it to video storage.</P> +<P>First, create a single partition /dev/hdb1 covering the whole disk and make +it type 0x8e using your partition editor.</P> +<P><CODE># fdisk /dev/hdb</CODE> +.... create partition, set type, save and reboot if it says you have to</P> +<P>Create the new LVM physical volume:</P> +<P><CODE># pvcreate /dev/hdb1</CODE></P> +<P>Add the new physical volume to the volume group:</P> +<P><CODE># vgextend VGforMyth /dev/hdb1</CODE></P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: You may get errors at this point stating that there are no +physical volumes available for adding to the LV, even though you know for a +fact that there are. You may need to specify the physical volume in the <CODE>/dev/ide/host/bus/target/lun/etc</CODE> format.</CAPTION> +</FIGURE> + +Once you've completed one of the following two procedures, use <B>df</B> +to check that you've got more space.</P> +<P>Make the logical volume used for video bigger:</P> +<P><CODE># lvextend --size +50G /dev/VGforMyth/video</CODE></P> +<H3>ReiserFS</H3> + +<P>Unmount, resize and remount the filesystem. Technically, you don't need to +unmount and remount the ReiserFS. +<BLOCKQUOTE><CODE> +<PRE> +# umount /var/video +# resize_reiserfs /dev/VGforMyth/video +# mount /dev/VGforMyth/video /var/video +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3>ext2 or ext3</H3> + +<P>LVM comes with a program called <B>resize2fs</B>.</P> +<P>Unmount, resize and remount the filesystem. The filesystem <EM>must</EM> be +unmounted during this procedure. +<BLOCKQUOTE><CODE> +<PRE> +# umount /var/video +# resize2fs --size +50G /dev/VGforMyth/video +# mount /dev/VGforMyth/video /var/video +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H3>xfs</H3> + +<P>XFS does not need to be unmounted to extend the size: +<BLOCKQUOTE><CODE> +<PRE> +# xfs_growfs /var/video +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H2><A NAME="advancedpartitionformatting"></A> <A NAME="ss24.2">24.2</A> <A HREF="mythtv-HOWTO.html#toc24.2">Advanced Partition Formatting </A> +</H2> + +<P>The partitions that your distribution sets up for you may not be +optimized for large files. Using LVM in conjunction with the following +techniques can be quite useful.</P> +<P>Unlike a typical filesystem, a MythTV video partition is usually a very +large filesystem filled with a fairly small number of large files. +Filesystem I/O is usually not an issue, even in multi-tuner and/or +multi-frontend setups.</P> +<P>There is however, one aspect of filesystem performance that can have a +bearing on the performance of MythTV. In Linux, deleting a file will +utilize I/O bandwidth until the deletion has been completed. If deleting +the file takes long enough, the video capture buffer may overrun, thereby +resulting in dropped frames. Some filesystems are faster at deleting files +than others and, for multi-gigabyte MythTV video files, these differences +can be significant.</P> +<P>Fortunately, there are published tests ( +<A HREF="http://aurora.zemris.fer.hr/filesystems/big.html">http://aurora.zemris.fer.hr/filesystems/big.html</A>) that provide +insight into filesystem performance under conditions relevant to MythTV +usage. In addition, some limited testing (archived at +<A HREF="http://www.gossamer-threads.com/lists/mythtv/users/52672">http://www.gossamer-threads.com/lists/mythtv/users/52672</A>) +with very large files (10 gigabytes) was reported in the MythTV Users +mailing list.</P> + +<H3>Ext2</H3> + +<P>Ext2 was the defacto standard Linux filesystem for many years. It is +stable, provides good I/O performance and can quickly delete large files. +The primary disadvantage of Ext2 is that it is not a journaling filesystem, +so a file system consistency check (fsck, which is normally only performed +after a system crash) can take many hours on a filesystem the size of a +typical MythTV partition.</P> + +<H3>Ext3</H3> + +<P>Ext3 is Ext2 with a journal, so your biggest gain is that in case of a +crash and reboot you won't have to wait very long for your partition to be +remounted.</P> +<P>There are options available when formatting an Ext3 partition, as in: +<BLOCKQUOTE><CODE> +<PRE> +# mkfs.ext3 -T largefile4 /dev/hdb1 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>This example assumes that <CODE>/dev/hdb1</CODE> has already been created using +<B>fdisk</B>. If you're using LVM, <CODE>/dev/hdb1</CODE> may be something like +<CODE>/dev/VGforMyth/video</CODE>.</P> +<P>The "-T largefile4" option creates one inode per 4 megabytes, which can +provide a few percent more storage space. However, tests indicate that +using the "-T largefile4" option can drastically increase the amount of time +required to delete a large file and thus it should only be used with encoder +settings that produce small video files (YMMV).</P> +<P>You can check on your filesystem using the <B>dumpe2fs</B> program. See +the man page for details.</P> +<H3>ReiserFS</H3> + +<P>The Reiser filesystem is another journaling filesystem commonly +distributed with Linux. It is known to be an extremely efficient filesystem +and it especially excels at managing partitions containing a large number of +small files. However, tests indicate it is not the fastest at deleting very +large files. For that reason, it may not be the best choice when using +encoder bitrates that produce very large files.</P> + +<H3>JFS</H3> + +<P>JFS (Journaling File System) is a journaling filesystem originally +developed by IBM for AIX which was later released as open source. While not +as common as Ext3 or ReiserFS, it is distributed with RedHat 9 (RH9), Fedora +Core and Mandriva as well as other distros. According to tests, JFS is the +file deletion speed king, deleting virtually any file in under one second, +even files as large as 10 gigabytes.</P> + +<H3>XFS</H3> + +<P>XFS is a journaling file system originally developed by SGI for Irix, and +later released as open source. While not a part of the default RedHat Linux +9 or Fedora Core installation (although it is a part of Mandriva and Fedora +Core 2+), it can be easily installed via ATrpms. XFS provides deletion +speeds for large files only slightly slower than JFS. According to the test +results shown at ( +<A HREF="http://aurora.zemris.fer.hr/filesystems/big.html">http://aurora.zemris.fer.hr/filesystems/big.html</A>), XFS provide +higher I/O rates than JFS, albeit at a higher CPU loading. This may cause +issues if you do not have the spare CPU capacity to handle XFS, potentially +leading to dropped frames.</P> +<P> +<A NAME="migratingtoSD"></A> </P> +<H2><A NAME="ss24.3">24.3</A> <A HREF="mythtv-HOWTO.html#toc24.3">Migrating from DataDirect Labs to Schedules Direct</A> +</H2> + +<P>MythTV v0.20.2 or later is required to natively support Schedules Direct. +Code has been included to make the transition as simple as possible.</P> +<P><B>You do not need to delete your existing video sources or add new ones!</B> </P> +<P>The following steps should work for most users: +<UL> +<LI>Create a Schedules Direct account and use the same information as your +existing lineups at Zap2It Labs. Do not add or delete channels at this +time.</LI> +<LI>Shut down any running <B>mythfrontend</B> and <B>mythbackend</B> programs.</LI> +<LI>Perform a backup of your existing database. See +<A HREF="mythtv-HOWTO-23.html#backupdb">Saving or restoring the database</A> for instructions.</LI> +<LI>Run <B>mythtv-setup</B> -> Video Sources. Change the grabber to +Schedules Direct, update the username and password fields with the account +information you created at Schedules Direct and select "Retrieve Lineups". +Click Finish.</LI> +<LI>Exit <B>mythtv-setup</B> and run <B>mythfilldatabase</B>. Check +if there were any errors.</LI> +<LI>Restart your <B>mythbackend</B> and <B>mythfrontend</B> programs.</LI> +</UL> +</P> + +<H2><A NAME="ss24.4">24.4</A> <A HREF="mythtv-HOWTO.html#toc24.4">Caching support for Schedules Direct</A> +</H2> + +<P>MythTV 0.20.2 or later supports caching of downloaded information from +Schedules Direct, so devices that share a common source do not require +multiple downloads.</P> +<P>Before beginning, perform a backup of your existing database. See +<A HREF="mythtv-HOWTO-23.html#backupdb">Saving or restoring the database</A> for instructions.</P> +<P>In the following scenario, assume that you have the following: +<OL> +<LI>A PVR-150 MPEG-2 encoder card connected directly to a CATV source.</LI> +<LI>A PVR-250 MPEG-2 encoder card connected via S-Video to a CATV Set Top Box.</LI> +</OL> +</P> +<P>What we are going to do is to create a single lineup at Schedules Direct and +then create two Video Sources which use the same login information but have +different channels associated with them.</P> +<P>On your Schedules Direct account, create a lineup that has all of the +channels that you can receive. Because we have a Set Top Box (STB), choose +a Digital lineup. Yes, this means that you may have 900 channels in this +lineup, but that's OK.</P> +<P>Use the Schedules Direct channel editor and unselect any channels that you +can't tune without the STB. This will usually be channels higher than 125, +but check your CATV provider lineup if you're not sure. Once you've +deselected them (using a click on the first channel you can't receive and +then a shift-click on the last channel you can't receive will deselect all +the channels in between those two.) click the Save Changes button at the +bottom of the screen.</P> +<P>In <B>mythtv-setup</B>, create a Video Source with an appropriate name. +"SD-Analog Only" will be used in this example. Click "Retrieve Lineups" +and select the digital lineup you just created at Schedules Direct.</P> +<P>Click "Finish" to return to the Video sources selector and then press the +ESC key to go back to the main screen.</P> +<P>Now choose Input Connections. Select the PVR-150 which is connected +directly to the CATV. Set the Video Source to "SD-Analog Only" and click +"Fetch channels from listings source".</P> +<P>Set the start channel to an appropriate value.</P> +<P><B>NOTE</B>: There is a bug where the "Fetch" command may not work; you +can tell that the Fetch did not retrieve any channels in one of two ways: in +the text-mode console, you will see a connection to Schedules Direct, but it +doesn't appear to retrieve any channel information: +<BLOCKQUOTE><CODE> +<PRE> +2007-08-25 15:03:05.526 New DB DataDirect connection +2007-08-25 15:03:05.526 Connected to database 'mythconverg' at host: localhost +2007-08-25 15:03:05.536 DataDirect: Your subscription expires on 11/23/2007 01:12:10 PM +2007-08-25 15:03:05.707 New DB connection, total: 3 +2007-08-25 15:03:05.707 Connected to database 'mythconverg' at host: localhost +2007-08-25 15:03:05.708 sourceid 2 has lineup type: CableDigital +2007-08-25 15:03:06.623 Data fetching complete. +2007-08-25 15:03:06.624 DataDirect: Deleting temporary files +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>or, the "Please add channels to this source" message in the "Starting +channel" field stays on the screen.</P> +<P>If either of these happens, save the information on this screen by clicking +the "Finish" button. Exit back to the Input connections screen by pressing +ESC, then select this Input Connection again. This time the Fetch will work +and the "Please add channels to this source" message will disappear.</P> +<P>If you look at the text-mode console, you'll see this if the channel +retrieval is working: +<BLOCKQUOTE><CODE> +<PRE> +2007-08-25 15:04:32.437 New DB DataDirect connection +2007-08-25 15:04:32.437 Connected to database 'mythconverg' at host: localhost +2007-08-25 15:04:32.447 DataDirect: Your subscription expires on 11/23/2007 01:12:10 PM +2007-08-25 15:04:32.622 New DB connection, total: 3 +2007-08-25 15:04:32.622 Connected to database 'mythconverg' at host: localhost +2007-08-25 15:04:32.623 sourceid 2 has lineup type: CableDigital +2007-08-25 15:04:33.418 DataDirect: Adding channel 41 'AMC' (AMC). +2007-08-25 15:04:33.422 DataDirect: Adding channel 32 'A & E Network' (AETV). +2007-08-25 15:04:33.425 DataDirect: Adding channel 66 'Black Entertainment Television' (BET). +2007-08-25 15:04:33.427 DataDirect: Adding channel 180 'Bravo' (BRAVO). +2007-08-25 15:04:33.430 DataDirect: Adding channel 51 'ABC Family' (FAM). +2007-08-25 15:04:33.432 DataDirect: Adding channel 146 'Country Music Television' (CMTV). +2007-08-25 15:04:33.435 DataDirect: Adding channel 39 'CNBC' (CNBC). +2007-08-25 15:04:33.437 DataDirect: Adding channel 36 'Cable News Network' (CNN). +2007-08-25 15:04:33.440 DataDirect: Adding channel 35 'CNN Headline News' (CNNH). +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Repeat the Input Connection configuration for any other capture devices that +are connected directly to the CATV system. You do not need to click Fetch +once you've done one successful download of the channel information - the +Starting channel should be automatically populated.</P> +<P>Go back to Schedules Direct and re-enable the channels that you had +previously deselected, then click Save Changes.</P> +<P>Create a new Video Source, here called "SD-All Digital Channels". Perform +the same "Retrieve Listings" you did before.</P> +<P>Go back to the Input Connections screen, select the PVR-250 which is +connected to the STB, assign the "SD-All Digital Channels" video source and +perform a retrieve channels. This will pull down the complete channel +listing, but only for <EM>this</EM> device.</P> +<P>When <B>mythfilldatabase</B> runs, it will cache the "big" download which +is appropriate for the STB, and then copy the information to the channels +that can only be accessed without the STB. But by default +<B>mythfilldatabase</B> is going to notice that the "Analog only" video +source is missing the channels that are in the Digital lineup you created at +Schedules Direct, so we need to override the addition of new channels.</P> +<P>When you run <B>mythfilldatabase</B> to populate your database, you'll +need to run it like this:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ mythfilldatabase --remove-new-channels +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>You will also need to modify how the <B>mythbackend</B> calls +<B>mythfilldatabase</B> when it performs its automatic listings update.</P> +<P>In <B>mythfrontend</B>, select "Setup" -> "General".</P> +<P>Continue press ENTER until you reach the Mythfilldatabase configuration +screen. In the "mythfilldatabase Arguments" field, type +--remove-new-channels</P> +<P>then press the TAB key until you reach Finish, then press ENTER to save. +You can then press ESC until you return to the main screen.</P> +<HR> +Next +<A HREF="mythtv-HOWTO-23.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc24">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-3.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-3.html new file mode 100644 index 0000000..bd6e3b4 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-3.html @@ -0,0 +1,805 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: Checking prerequisites. </TITLE> + <LINK HREF="mythtv-HOWTO-4.html" REL=next> + <LINK HREF="mythtv-HOWTO-2.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc3" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-4.html">Next</A> +<A HREF="mythtv-HOWTO-2.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc3">Contents</A> +<HR> +<H2><A NAME="s3">3.</A> <A HREF="mythtv-HOWTO.html#toc3">Checking prerequisites. </A></H2> + +<P>You must ensure that any firewalls (either hardware, or a software +firewall installed by your distribution) will not block access to the ports +that will be used by the MythTV clients and servers on the "inside" LAN. +The ports for MySQL (TCP port 3306) and mythbackend (TCP ports 6543 and +6544) must be open. It is <EM>strongly</EM> recommended that you do +<EM>not</EM> expose the MythTV and MySQL ports to the Internet or your +"Outside" LAN.</P> + +<H2><A NAME="ss3.1">3.1</A> <A HREF="mythtv-HOWTO.html#toc3.1">Hardware</A> +</H2> + +<P>Hardware selection is a complex topic, one this HOWTO will only discuss +briefly and in general terms. The following subsections offer some general +guidance but stop short of offering specific recommendations.</P> +<P>For a good MythTV experience, you must understand that MythTV exercises your +hardware more than a typical desktop. Encoder cards generate DMA across the +PCI bus. The CPU is busy encoding / decoding video. Hard drives are +constantly reading and writing data. Building a MythTV system on older / +"spare" hardware may be an exercise in frustration and can waste many hours +of valuable time.</P> +<P>For more detail about actual configurations that others have used, Mark +Cooper has setup a hardware database at +<A HREF="http://pvrhw.goldfish.org/">http://pvrhw.goldfish.org/</A>. The +website will let you browse what other users have reported as their hardware +configuration, and how happy they are with the results.</P> +<P>If you have specific questions about the suitability of specific hardware +choices, you can consult the archives of the mythtv-users mailing list at +<A HREF="http://www.gossamer-threads.com/lists/mythtv/">http://www.gossamer-threads.com/lists/mythtv/</A> or +post a question to the list.</P> +<H3>CPU Type and Speed</H3> + +<P>Selection of CPU type and speed is one of the trickiest elements of +hardware selection, mainly because there are so many tradeoffs which can be +made. For example, if you have plenty of CPU, you can use higher bitrates +or capture sizes, etc.</P> +<P>MythTV has two modes of operation. First, it can function as a software +video encoder, which means that it uses a fairly generic "dumb" video +capture card to get frames of video, encodes them using the CPU on your +motherboard and writes them to disk. High-end video capture cards and +devices like the TiVo and ReplayTV have dedicated encoder chips which use +specialized hardware to convert the video stream to the MPEG-2 format +without using the motherboard CPU. The main CPU has the responsibility of +running the Operating System and reading and writing the encoded frames to +the disk. These tasks have fairly low CPU requirements compared to encoding +video, which is why a device like a Series 1 TiVo can run with only 16MB of +RAM and a 54MHz CPU.</P> +<P>There are many variables that go into the question: "How fast a CPU do I +need to run MythTV"? Obviously, the faster your CPU, the better your +experience will be with MythTV. If you are using the software MPEG-4 +encoder and performing the "Watch TV" function, where the CPU is both +encoding and decoding video simultaneously to allow Pause, Fast Forward and +Rewind functions for live TV requires more CPU then just encoding or +decoding. MythTV also supports multiple encoder cards in a single PC, +thereby increasing the CPU requirements if you plan on simultaneously +encoding multiple programs. As a general guideline, plan on 1GHz per +encoder if you are doing software-based encoding, less if you are using a +hardware-based encoder.</P> +<P>Here are a few data points: +<UL> +<LI>A PIII/733MHz system can encode one video stream using the MPEG-4 +codec using 480x480 capture resolution. This does not allow for live TV +watching, but does allow for encoding video and then watching it later.</LI> +<LI>A developer states that his AMD1800+ system can <B>almost</B> +encode two MPEG-4 video streams and watch one program simultaneously.</LI> +<LI>A PIII/800MHz system with 512MB RAM can encode one video +stream using the RTjpeg codec with 480x480 capture resolution and play it back +simultaneously, thereby allowing live TV watching.</LI> +<LI>A dual Celeron/450MHz is able to view a 480x480 MPEG-4/3300kbps file +created on a different system with 30% CPU usage.</LI> +<LI>A P4 2.4GHz machine can encode two 3300Kbps 480x480 MPEG-4 files and +simultaneously serve content to a remote frontend.</LI> +</UL> +</P> +<P>The second mode of operation is where MythTV is paired with a hardware-based +video encoder, such as a Matrox G200 or a Hauppauge +WinTV-PVR-150/250/350/500. In this mode, because the video encoding is +being done by a dedicated video processor, the host CPU requirements are +quite low. See the +<A HREF="#video_capture_device">Video Capture Device</A> section for details.</P> +<P>The price differential between a frame grabber and a card that implements +hardware MPEG-2 encoding, such as the Hauppauge PVR-x50 series, is now less +than $30 US. Primary development in MythTV has transitioned to supporting +MPEG-2 capture devices and HDTV, so if given the option, go with the +hardware MPEG-2 encoder.</P> +<P>If you have a Via M10000 series or a Hauppauge PVR-350, MythTV can use the +hardware-based video decoder for playback, which further reduces CPU +requirements.</P> + +<H3>Memory</H3> + +<P>A MythTV host that is both a backend and a frontend and using software +encoding with a single capture card should run adequately in 256MB of RAM. +Additional RAM above 256MB will not necessarily increase performance, but +may be useful if you are running multiple encoders.</P> + +<H3>Hard Disk(s)</H3> + +<P>Encoded video takes up a lot of hard disk space. The exact amount depends +on the encoding scheme, the size of the raw images and the frames per +second, but typical values for MythTV range from 700 megabytes/hour for +MPEG-4, 2 GB/hour for MPEG-2 and RTjpeg and 7 GB/hour for ATSC HDTV.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: You <EM>must</EM> use DMA for hard drive access to prevent +choppy or jittery video. Not all distributions enable DMA at boot time. See the Troubleshooting Section for +<A HREF="mythtv-HOWTO-22.html#Setting_DMA">instructions</A> on how to do this.</CAPTION> +</FIGURE> +</P> +<P>Writing video to disk is sensitive to timing issues; RTjpeg requires less +CPU with the tradeoff being larger files and needing to write to the disk +faster. MPEG-4 requires more CPU, but the files are smaller. At the +default resolution, MPEG-2 creates the largest files of all with almost no +CPU impact.</P> +<P>See the Troubleshooting +<A HREF="mythtv-HOWTO-22.html#Setting_DMA">section</A> for more +information.</P> + +<H3>Filesystems</H3> + +<P>MythTV creates large files, many in excess of 4GB. You <EM>must</EM> +use a 64 or 128 bit filesystem. These will allow you to create large files. +Filesystems known to have problems with large files are FAT (all versions), +and ReiserFS (versions 3 and 4). </P> +<P>Because MythTV creates very large files, a filesystem that does well at +deleting large files is important. Numerous benchmarks show that XFS and +JFS do very well at this task. You are <EM>strongly</EM> encouraged to +consider one of these for your MythTV filesystem. JFS is the absolute best +at deletion, so you may want to try it if XFS gives you problems. MythTV +.21 incorporates a "slow delete" feature, which progressively shrinks +the file rather than attempting to delete it all at once, so if you're more +comfortable with a filesystem such as ext3 (whose delete performance for +large files isn't that good) you may use it rather than one of the +known-good high-performance file systems. There are other ramifications to +using XFS and JFS - neither offer the opportunity to shrink a filesystem; +they may only be expanded.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: You <EM>must not</EM> use ReiserFS v3 for +your recordings. You will get corrupted recordings if you do.</CAPTION> +</FIGURE> +</P> +<P>Because of the size of the MythTV files, it may be useful to plan for future +expansion right from the beginning. If your case and power supply have the +capacity for additional hard drives, read through the +<A HREF="mythtv-HOWTO-24.html#LVM">LVM</A> and +<A HREF="mythtv-HOWTO-24.html#advancedpartitionformatting">Advanced Partition Formatting</A> sections for some pointers.</P> +<P> +<A NAME="video_capture_device"></A> </P> +<H3>Video Capture Device </H3> + +<P>In order to capture video, MythTV will need one or more video capture +devices with Linux drivers. There are a number of classes of hardware +available for capturing video. </P> +<H3>Frame Grabbers.</H3> + +<P>This class of card is the simplest and is usually the cheapest. There is no +on-board encoding of the analog video; hardware known as a Digital-Analog +Converter (DAC) takes the video and presents it to the computer in an +essentially raw digital form.</P> +<P>For a list of video capture cards known to work with Linux, please see +<CODE>/usr/src/linux/Documentation/video4linux/bttv</CODE> for a partial +listing; even if your specific card is not listed, it may be that the vendor +is actually using a standard reference design and placing their own name on +it. See the video4linux mailing list ( +<A HREF="https://listman.redhat.com/mailman/listinfo/video4linux-list">https://listman.redhat.com/mailman/listinfo/video4linux-list</A>) for +more information and for specific hardware questions.</P> +<P>The most common inexpensive cards available use the Bt848, Bt878 or CX2388x +series of video capture chips; examples are the "Hauppauge WinTV Go" card and +the "AverTV Desktop PVR" card, both of which use the bttv kernel module.</P> +<P> +<HR> +<PRE> +NOTE: The ATI TV Wonder series and the ATI All-in-Wonder series of cards +are not the same. The All-in-Wonder cards will not work with MythTV. +</PRE> +<HR> +</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +</FIGURE> + +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: The ATI All-in-Wonder cards (which are not the same +as the ATI TV Wonder, TV Wonder VE or TV Wonder Pro) <EM>will not</EM> work +as a MythTV capture device because the GATOS +<A HREF="http://gatos.sourceforge.net">http://gatos.sourceforge.net</A> +drivers that are available provide only a limited subset of the V4L API. The TV Wonder series of cards are supported by the Bt8x8 Video4Linux driver.</CAPTION> +</FIGURE> +</P> +<P>After you have installed a suitable capture device, you can check that +the kernel sees it with <CODE>lspci</CODE>. Look for an entry labeled "Multimedia +video controller". To get more detailed information about the card, use +<CODE>lspci -v</CODE> or <CODE>lspci -vv</CODE>. Ensure that your system is loading +the bttv modules by typing: +<BLOCKQUOTE><CODE> +<PRE> +# lsmod |grep bttv +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>You want to see the <CODE>bttv</CODE> module listed.</P> +<H3>Hardware MPEG-2 encoders.</H3> + +<P>While inexpensive video-capture cards simply capture raw frames, leaving +encoding to software, some higher-end cards incorporate hardware-based +encoding. Using either a G200 MJPEG encoder card, or a MPEG-2 encoder card +supported by the IvyTV project +<A HREF="http://ivtvdriver.org/">http://ivtvdriver.org</A> such as the Hauppauge +PVR-150/250/350/500, Avermedia M179, Hauppauge "Freestyle" or Yuan M600 +cards will allow you to use dedicated hardware encoders rather than your +CPU. (The PVR-350 can simultaneously be used as an output device.) Using the +on-board MPEG-2 encoder greatly reduces the CPU requirements for +encoding.</P> +<P>The ivtv driver was incorporated into the Linux kernel starting at v2.6.22.</P> +<P>There is a Beta driver for the HVR-1600 card at +<A HREF="http://www.ivtvdriver.org/index.php/Cx18">http://www.ivtvdriver.org/index.php/Cx18</A></P> +<P><B>NOTE</B>: Motherboards with the Via chipset are notoriously bad with +DMA and have caused numerous issues with ivtv, including hard locks. See +the ivtv website +<A HREF="http://ivtvdriver.org">http://ivtvdriver.org</A> +for the latest information on what works and what doesn't.</P> +<P>Here are some data points for encoding: +<UL> +<LI>A Celeron 450 uses 2% CPU for encoding a 480x480 16Mbps MPEG-2 stream.</LI> +</UL> +</P> +<P>Here are some data points for decoding:</P> +<P> +<UL> +<LI>An Athlon 1800XP can decode a 720x480 8Mbps MPEG-2 file using 10% CPU</LI> +<LI>An Athlon 1GHz can decode a 720x480 16Mbps MPEG-2 file using 30-50% +CPU, can decode a 480x480 16Mbps MPEG-2 using 30% CPU and approximately 30% +for Live TV at 416x480.</LI> +<LI>A P3-550 can decode a 480x480 16Mbps MPEG-2 file with 55% CPU.</LI> +<LI>A Celeron 450 (no SSE) can decode a 480x480 16Mbps MPEG-2 file with +80% CPU.</LI> +</UL> +</P> + +<H3>DVB capture cards.</H3> + +<P>DVB is a video standard primarily found in Europe (where it comes in +DVB-C, DVB-T and DVB-S varieties for Cable, Terrestrial and Satellite) and +is also used as the programming interface for HDTV capture cards in Linux. +To see if your DVB card is supported, see the list of cards in the +"Supported Hardware" section of the DVB Wiki at +<A HREF="http://www.linuxtv.org/wiki/index.php/Main_Page">http://www.linuxtv.org/wiki/index.php/Main_Page</A> for more +information.</P> +<P>In the United States, you may use a card such as the TwinHan to obtain +unencrypted Free-To-Air satellite channels. See +<A HREF="http://www.lyngsat.com/">http://www.lyngsat.com/</A> for the types +of content which is available.</P> + +<H3>HDTV.</H3> + +<P>There are a number of HDTV cards with Linux drivers which are known to +operate in the United States; a complete list of cards with DVB drivers can +be found at +<A HREF="http://www.linuxtv.org/wiki/index.php/ATSC_Devices">http://www.linuxtv.org/wiki/index.php/ATSC_Devices</A> Some cards +support capture of unencrypted digital cable TV (utilizing QAM256), others +will only work with Over The Air (aka "OTA") signals captured with an +antenna (with 8VSB).</P> +<P>Cards that have been reported to work include: +<UL> +<LI>pcHDTV HD-2000, Air2PC PCI rev 1-3 (8VSB only)</LI> +<LI>SiliconDust HDHomeRun (8VSB, QAM256)</LI> +<LI>pcHDTV HD-3000/5500 (8VSB, QAM256)</LI> +<LI>Air2PC HD-5000 (8VSB, QAM256)</LI> +<LI>DViCO Fusion HDTV Lite/Gold 5 (8VSB, QAM256)</LI> +</UL> +</P> +<P><B>NOTE</B>: There are no known consumer-level capture devices which will +allow you to capture the HDTV output (DVI, HDMI, VGA, YPbPr / Component) +from a set-top box commonly found with digital cable systems or satellite +systems. <EM>None</EM> of the capture devices listed above +perform any encoding; they merely allow your computer to save a copy of a +HDTV stream which has already been converted to MPEG-2 at the broadcast +facility.</P> +<P><B>NOTE:</B>: All of the cards listed above (except for the HD-2000 and +HDHomeRun) should be configured as DVB cards. The HD-2000 can be configured +as a pcHDTV card if you use the V4L drivers from +<A HREF="http://www.pchdtv.com">http://www.pchdtv.com</A> and use Linux +kernel 2.6.9 or earlier. With kernel 2.6.10 and higher it must be +configured as a DVB card, but you lose access to the second antenna input in +ATSC mode. The HDHomeRun should be configured as two HDHomeRun cards, one +for each tuner.</P> +<P>To playback HDTV content, plan on a powerful CPU. "How powerful?" depends +on a number of factors, such as the capture resolution, whether the video is +progressive or interlaced, and whether your display card has hardware-assist +support for Linux.</P> +<P>The Simple Answer: Once you are in the 3.2 Ghz P4-class of CPU you should have +no issues with viewing HDTV.</P> +<P>The Complicated Answer:</P> +<P>For 720p content (1280x720), a 2.4GHz P4 should be sufficient.</P> +<P>For 1920x1080i->1920x1080p with the better deinterlacing methods +done in real time a 2.4GHz CPU is taxed, but should work if you use "Bob and +Weave" deinterlacing, or if you have an NVIDIA card with MPEG-2 hardware +acceleration. If you enable the hardware acceleration, you may be able to +use a 1.8GHz processor.</P> + +<H3>Firewire.</H3> + +<P>You may use the Firewire output of the Motorola DCT6200 or the SA3250. +If your provider uses 5C encryption on a particular channel, you won't be +able to get any content.</P> + +<H3>DBoxII or other devices running Neutrino</H3> + +<P>You may use the Ethernet port of an DBoxII or a similar device to capture +MPEG2. Your set top box has to be running the Neutrino GUI. </P> + +<H3>USB Capture Devices.</H3> + +<P>The Plextor ConvertX PVR devices are supported through Linux drivers +available from +<A HREF="http://www.plextor.com/english/support/LinuxSDK.htm">http://www.plextor.com/english/support/LinuxSDK.htm</A>. MythTV uses the +Plextor to capture hardware encoded MPEG-4, so the host CPU requirements are low.</P> +<P>Hauppauge WinTV-PVR-USB2 (driver available at +<A HREF="http://www.isely.net/pvrusb2/">http://www.isely.net/pvrusb2/</A>) +emulates a PVR-x50 card.</P> + +<H3>IP Recorder (RTSP, RTS, UDP)</H3> + +<P>MPEG-2, MPEG-4 and H.264 internet TS stream recording is supported using +the IPTV recorder in MythTV. This recorder expects the channels to be supplied +as a m3u playlist. If your DSL/Fiber provider supplies television service, +but does not provide a m3u playlist for the channels, you can construct one +for your own use. You do not need to download it from the same server as the +streams themselves, and can also read it from a file if this is more convenient.</P> +<P><B>NOTE</B>: Some DSL providers only allow you to use one recorder at a +time, so you may need to limit yourself to one recorder in MythTV and turn +off any set top box the cable provider sold or rented to you with your +service. This limitation is independent of the bandwidth you have purchased.</P> + +<H3>Hardware known NOT to work and other issues</H3> + +<P> +<UL> +<LI>Hauppauge WinTV-D or -HD (no driver)</LI> +<LI>Hauppauge WinTV-USB series</LI> +<LI>Hauppauge WinTV-PVR-usb (model 602), or WinTV-PVR-PCI (model 880) cards (no driver - this is not the PVR-250/350 +series of cards supported by the IvyTV driver)</LI> +<LI>ATI All-in-Wonder series</LI> +</UL> +</P> + +<H3>Sound card</H3> + +<P>The system needs a sound card or an on-board equivalent on the motherboard +to play back and in most cases, to record sound. Any sound card that can be +operated by the ALSA (Advanced Linux Sound Architecture) kernel modules will +work with MythTV. However, some cards and drivers will provide better +quality or compatibility than others. In particular, many audio +devices included on motherboards can be problematic.</P> +<P>The usual practice for capturing the audio associated with the video is to +run a cable from an audio output on the video capture card to the Line input +on a sound card. However, some video capture cards provide on-board audio +capabilities that work with the kernel <CODE>btaudio</CODE> module instead, +thereby eliminating the need for a cable. This is useful if you will be +using multiple capture cards in a single chassis, since each capture card +will not need its own sound card. Note that a separate sound card is still +required for playback when using <CODE>btaudio</CODE>, and that often the audio +recorded in this way will be mono only. See the +<A HREF="mythtv-HOWTO-23.html#btaudio">btaudio</A> section for more information.</P> +<P> +<FIGURE> +<EPS FILE="warning"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: Analog video capture cards are the only ones which +require a soundcard for capturing audio. DVB, HDTV, and other hardware +encoder cards all provide a combined audio / video stream.</CAPTION> +</FIGURE> +</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Plugging a Line-level device into the Mic input is +not recommended. Line-level devices have higher voltages and can damage the +sound card. In addition, even if it doesn't break your card, you will be +getting Mono sound. See the Linux MP3 HOWTO at +<A HREF="http://www.tldp.org/HOWTO/MP3-HOWTO.html">http://www.tldp.org/HOWTO/MP3-HOWTO.html</A> for additional information.</CAPTION> +</FIGURE> +</P> + +<H3>Video Display Card</H3> + +<P>MythTV will work with just about any video card. However, it is highly +recommended that you use a card which supports XVideo (XV) extensions. If +your card does not support XV, color conversion and scaling will be +performed by your CPU rather than the video card. This is very CPU +and memory intensive and will often result in dropped frames and a +corresponding degradation of quality. Check the X documentation +for details if you are uncertain about your preferred card. You may +also run <CODE>xvinfo</CODE>; look for your video card to be listed as one +of the adapters.</P> + +<P>If you want to use MythTV with a standard television, you will need a +physical connection from your video card to your TV set, which can either be +a TV-out port on the card itself or an external adapter that converts the +VGA signal to an appropriate video signal. "Appropriate" depends on a number +of factors, such as video standard (NTSC vs. PAL), the type of input +connection (Composite vs. SVideo), etc.</P> +<P>Note that with some video cards and X drivers, XVideo extensions are +only supported on the VGA output, and not on the TV output.</P> + +<H3>Cards with TV-out</H3> + +<P>The next section deals with a number of cards that are known to have +TV-out ports. The list is unlikely to be complete, so if you know of +others, please post a message to the mythtv-users mailing list so the +information can be included in future versions of the HOWTO. The list is +organized by manufacturer.</P> +<P>Reports here are based on what users of the cards have posted on the +mythtv-users mailing list, so if you need configuration details, please +search the archives at +<A HREF="http://www.gossamer-threads.com/lists/mythtv/">http://www.gossamer-threads.com/lists/mythtv/</A> using +the card name in your search string.</P> + +<H3>ATI</H3> + +<P>ATI makes many cards with TV-out capability, but only offers Linux +drivers for Radeon 8500 and above cards. See the Drivers and Software +section of +<A HREF="http://www.ati.com/">http://www.ati.com</A> for the +driver and additional information.</P> +<P>The enhanced ati.2 X driver created by the GATOS +<A HREF="http://gatos.sourceforge.net">http://gatos.sourceforge.net</A> +project offers some support for TV-out on other ATI cards, but only in its +"experimental" version, available through CVS. There have been reports from +people who say they have made this driver work with one or another ATI card. +For example, Bruce Markey +<A HREF="mailto:bjm@lvcm.com">mailto:bjm@lvcm.com</A> writes (on the +mythtv-users mailing list): "I got this to work. You can quote me on that. +I've used TV-out on several models of ATI cards both All-In-Wonder and +regular cards with TV-out." See the "Adventurous Setup" section of +<A HREF="http://gatos.sourceforge.net/watching_tv.php">http://gatos.sourceforge.net/watching_tv.php</A> for details. Also see +<A HREF="http://www.retinalburn.net/linux/tvout.html">http://www.retinalburn.net/linux/tvout.html</A> for more information.</P> + +<H3>NVIDIA</H3> + +<P>Some NVIDIA cards with TV-out can be run using the standard nv driver in +X, combined with the userspace application <B>nvtv</B> to control the TV-out +port. See +<A HREF="http://sourceforge.net/projects/nv-tv-out/">http://sourceforge.net/projects/nv-tv-out/</A> for details. Recent +versions of the NVIDIA driver have better support for overscan and other +features useful with TV-Out, so the <B>nvtv</B> application may not be +required.</P> +<P>Some NVIDIA cards can be run with a proprietary NVIDIA X driver made +available by NVIDIA. See +<A HREF="http://www.nvidia.com/object/unix.html">http://www.nvidia.com/object/unix.html</A> for more information.</P> +<P><B>NOTE</B>: It's strongly recommended that you use the proprietary +NVIDIA drivers; they have excellent support for XvMC and ship with a good +configuration utility. XvMC provides MPEG-2 hardware acceleration, which is +important if you want to display HDTV.</P> + +<H3><A NAME="PVR-350"></A> Hauppauge PVR-350 </H3> + +<P>MythTV supports the TV-out and MPEG-2 decoder functions in the IvyTV +driver.</P> +<P>The PVR-350 is unique amongst the Hauppauge PVR-x50 cards in that it also +supports audio output, but you need to connect that audio output to +something. There are two courses of action you may take: +<OL> +<LI>Take the audio output from the PVR-350 and plug it into an input on a +sound card on your machine. You may then use MythTV's internal audio +controls.</LI> +<LI>Take the audio output from the PVR-350 and connect it directly to your +television / audio system. You must indicate that you are using external +audio control on the PVR-350 setup page.</LI> +</OL> +</P> + +<H3>Other Options</H3> + +<P>Some devices with on-board TV-out capability, such as Xboxes converted to +Linux and some laptops can be used as MythTV frontends to display on a +television screen. Please consult the mythtv-users mailing list for messages +that report the details of these special arrangements.</P> + +<H3>External Adapters</H3> + +<P>External adapters convert standard VGA output to a form suitable for +display on a television. The output format varies by region, since +different countries have different TV standards. People on the mythtv-users +list have mentioned these adapters:</P> +<P> +<UL> +<LI>AITech Web Cable Plus, powered by external transformer or takes power +from PS/2 keyboard connector, support resolutions up to 1024x768, outputs +composite and SVideo, provides position adjustment.</LI> +<LI>Averkey lite, powered by a USB port, has Composite, SVideo, YPbPr +outputs; pan, brightness, overscan/underscan controls; supports up to +1024x768 outputs; and supports PAL and NTSC.</LI> +<LI>ADS TV Elite XGA</LI> +<LI>AverKey iMicro (comments are generally favorable)</LI> +<LI>AITech Web Cable (comments are generally unfavorable, different than +the "Plus" version above)</LI> +<LI>TVIEW Gold (mentioned once, favorably)</LI> +</UL> +</P> + +<H2><A NAME="ss3.2">3.2</A> <A HREF="mythtv-HOWTO.html#toc3.2">Software</A> +</H2> + +<P>There are a few ways of installing programs on Linux systems; you can +either use a pre-compiled package, or install from a tarball after +satisfying any prerequisites.</P> +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: you must have the MySQL database software installed on a +system to store the master database. This does not necessarily mean that +MySQL must run on one of the MythTV boxes. The minimum MySQL version is 5.0.</CAPTION> +</FIGURE> +</P> + +<H3><A NAME="precompiled"></A> Pre-compiled packages </H3> + +<P>A number of people have created pre-compiled packages for MythTV that may +make your installation easier.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>BIG FAT WARNING</B>: This HOWTO assumes that you have <EM>not</EM> +installed MythTV from a package. All example command lines and file +locations are based on the MythTV tarball defaults. Some packagers have +modified the filenames, binaries and file locations to match what is +commonly found in that distribution. Any issues with MythTV installed via a +pre-compiled package <B>MUST</B> be raised with the packager.</CAPTION> +</FIGURE> +</P> +<P>If you use any of the pre-compiled packages you may not need to perform any +additional configuration steps in this HOWTO. The next logical step is +<A HREF="mythtv-HOWTO-6.html#mysql">configuring MySQL</A>, which you may or may not have to +perform. See your package documentation.</P> + +<H3><A NAME="atrpms"></A> Red Hat Linux / Fedora Core </H3> + +<P>The definitive documentation on installing MythTV on Red Hat Linux / +Fedora Core can be found in Jarod Wilson's ( +<A HREF="mailto:jcw@wilsonet.com">mailto:jcw@wilsonet.com</A>) HOWTO at +<A HREF="http://wilsonet.com/mythtv/">http://wilsonet.com/mythtv/</A> Just +like 3rd-party packages, any 3rd-party documentation problems should be +brought up with the 3rd-parties (maintainer, lists, bugzillas etc.). The +installation instructions which follow should be used as a guide only; refer +to Jarod's guide.</P> +<P>Red Hat Linux and Fedora Core packages for MythTV and all of its add-on +modules and some themes have been packaged by +<A HREF="mailto:Axel.Thimm@ATrpms.net">mailto:Axel.Thimm@ATrpms.net</A> and +are available at +<A HREF="http://ATrpms.net/topic/multimedia/">http://ATrpms.net/topic/multimedia/</A>. All of the prerequisites for +MythTV (such as XMLTV) are available as RPM packages. If you have problems +with the RPMs, please contact the ATrpms lists at +<A HREF="http://lists.ATrpms.net/">http://lists.ATrpms.net/</A> or file a +bug against +<A HREF="http://bugzilla.ATrpms.net/">http://bugzilla.ATrpms.net/</A>.</P> +<P>Given the large number of dependent RPMs you are advised to use tools like +apt or yum for automatic retrieval and installation of the required RPMs. +( +<A HREF="http://ATrpms.net/install.html">http://ATrpms.net/install.html</A>) In this case a +special meta-package called mythtv-suite will allow you to install all of +MythTV and its add-ons, plus all dependencies.</P> +<P>If you don't have <B>apt</B> or <B>yum</B> on your machine, download and +install the atrpms-kickstart package from +<A HREF="http://ATrpms.net/name/atrpms-kickstart/">http://ATrpms.net/name/atrpms-kickstart/</A>. +Install the package with: +<BLOCKQUOTE><CODE> +<PRE> +# rpm -Uvh atrpms-kickstart* +</PRE> +</CODE></BLOCKQUOTE> + +Then run: +<BLOCKQUOTE><CODE> +<PRE> +# apt-get update +# apt-get dist-upgrade +# apt-get update +</PRE> +</CODE></BLOCKQUOTE> + +And finally: +<BLOCKQUOTE><CODE> +<PRE> +# apt-get install mythtv-suite +</PRE> +</CODE></BLOCKQUOTE> + +These steps however, do NOT perform the installation of any drivers required +for <B>ALSA</B>, capture cards, <B>lirc kernel modules</B>, etc., nor do +they set up your MythTV database. Check +<A HREF="http://ATrpms.net/topic/multimedia/">http://ATrpms.net/topic/multimedia/</A> for the drivers you +need.</P> + +<H3>Mandriva</H3> + +<P>Thac has created RPMs for MythTV for Mandriva which may +be obtained from +<A HREF="http://rpm.nyvalls.se/">http://rpm.nyvalls.se/</A> If you have problems with the RPMs, please +send him email directly at +<A HREF="thac@nyvalls.se">thac@nyvalls.se</A>.</P> +<H3>Debian</H3> + +<P>Debian packages for MythTV and most of its add-on modules are maintained +by Christian Marillat +<A HREF="mailto:marillat@free.fr">mailto:marillat@free.fr</A> and are available at +<A HREF="http://www.debian-multimedia.org/">http://www.debian-multimedia.org/</A>. +Installation instructions can be found on those pages as well. All of the +prerequisites for MythTV are available as Debian packages, most of them from +the official Debian archive.</P> +<P>If you have followed the instructions on the above page you should have added +<BLOCKQUOTE><CODE> +<PRE> +deb-src http://www.debian-multimedia.org sid main +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>to your <CODE>/etc/apt/sources.list</CODE> file. Running <B>apt-get update</B> and then +executing <B>apt-get build-dep mythtv</B> should install all the +pre-requisites required to compile MythTV.</P> +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: Due to the requirement for Qt 3.3+, there are no packages for +Debian woody/stable.</CAPTION> +</FIGURE> +</P> + +<P>The Debian packages are configured such that MythTV programs should be +run as the <CODE>mythtv</CODE> user, which is automatically created during +installation. This user has access to write new recordings to disk in the +default directory, read and write the database, access the audio and video +devices, and everything else that MythTV needs to do.</P> + +<P>See <CODE>/usr/share/doc/<I>packagename</I>/README.Debian</CODE> for more +information, including copies of the MythTV documentation. The +<CODE>mythtv-doc</CODE> package contains a copy of this HOWTO in +<CODE>/usr/share/doc/mythtv-doc</CODE>.</P> +<H3>Manual installation</H3> + +<P>You may use the graphical tools that come with your distribution, or you +can use command-line utilities. Either system will get the job done, and it +all depends on your comfort level with Linux.</P> +<P>In order to compile MythTV, we need to make sure that the software it needs +is installed. This list includes <B>mysql</B>, <B>gcc</B>, +<B>freetype2-devel</B>, <B>xorg-xserver-devel</B>, <B>qt-devel</B> and +<B>lame</B>. If you're going to use a remote control with MythTV, you're +going to need the <B>cdialog</B> package in order to compile +<B>lircd</B> if your distribution doesn't have a pre-packaged +<B>lirc</B>. If you are using <B>XMLTV</B> as a grabber, you will need +<B>perl</B>.</P> +<P> +<HR> +<PRE> +NOTE: Qt v3.3 or higher is required. + +NOTE: MythTV DOES NOT WORK with Qt4. + +NOTE: If you are going to be using RPMs to install various +components, you should be aware that not all packages include the necessary +headers for compiling. If you're having trouble compiling, ensure +that you've installed the -devel version of a prerequisite. +</PRE> +<HR> +</P> + +<H3><A NAME="CLIinstalltools_"></A> Command-line installation </H3> + +<P> This section details the various methods for installing prerequisites +from the command line.</P> + +<H3>Mandriva</H3> + +<P><B>NOTE</B>: The following instructions should be considered out of +date as of 2006-09-10. If updated instructions are not submitted by the +release of v0.21 of MythTV they will be removed.</P> +<P><B>urpmi</B> is the simplest tool for installation of packages from the +command line, but properly configuring it can be difficult. The +following website +<A HREF="http://easyurpmi.zarb.org/">http://easyurpmi.zarb.org/</A> will allow you to choose +a mirror site and then present the command-line configuration text for that +mirror. You will most likely need to add a "Contrib" mirror to your setup. +If you add a site from the "Penguin Liberation Front", you will be able to +load the <CODE>lame</CODE> library without compiling from source.</P> +<P>Open a shell, and execute the following. You may get +asked a number of questions regarding dependencies. It's best to answer +"YES". +<BLOCKQUOTE><CODE> +<PRE> +$ su +# urpmi mysql gcc gcc-c++ freetype2-devel cdialog alsa-utils +# urpmi XFree86-devel perl +# urpmi libqt3-devel libMesaGLU1-devel +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P> +<HR> +<PRE> +NOTE for Mandriva 9.1+ users: execute the following command. + +# urpmi libqt3-mysql +</PRE> +<HR> + +However, you might get this when you execute the commands above: +<BLOCKQUOTE><CODE> +<PRE> +everything already installed +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>In that case, you're ready to move to the next +<A HREF="mythtv-HOWTO-4.html#Setting_up_paths">section</A>. Once you have completed installing the pre-requisites, +exit out of the shell and start a new one to ensure that any environment +variables setup by the installation have a chance to take effect.</P> + +<H3>Gentoo. </H3> + +<P><B>NOTE</B>: MythTV does <EM>not</EM> run on Qt4. +If Qt has not been installed on your system: Edit +<CODE>/etc/make.conf</CODE> and locate the "USE" variable. If the line is +commented out, remove the comment. The line should have at least: +<BLOCKQUOTE><CODE> +<PRE> +USE="mysql alsa" +</PRE> +</CODE></BLOCKQUOTE> + +Next you need to build Qt. If you don't plan on using the ebuilds as +described in the Gentoo section then you also need to install lame. +<BLOCKQUOTE><CODE> +<PRE> +# emerge lame mysql qt +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you have already installed Qt: you will need to rebuild because the +default installation doesn't include MySQL support, a requirement for MythTV. +To enable SQL support, add "mysql" to your USE variable in +<CODE>/etc/make.conf</CODE> and rebuild Qt by running +<BLOCKQUOTE><CODE> +<PRE> +# emerge qt +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>All the necessary files will be downloaded and built. Even on a fast machine +this may take a lot of time if you need to do a full Qt build.</P> + +<H3>Debian.</H3> + +<P>Build-dependencies for MythTV can be satisfied by adding the following to +your <CODE>/etc/apt/sources.list</CODE> +<BLOCKQUOTE><CODE> +<PRE> +# Christian Marillat's packages (mplayer, lame) +deb http://www.debian-multimedia.org sid main +deb-src http://www.debian-multimedia.org sid main +</PRE> +</CODE></BLOCKQUOTE> + +and executing: +<BLOCKQUOTE><CODE> +<PRE> +# apt-get build-dep mythtv +# apt-get source mythtv --compile +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<HR> +<A HREF="mythtv-HOWTO-4.html">Next</A> +<A HREF="mythtv-HOWTO-2.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc3">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-4.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-4.html new file mode 100644 index 0000000..fbe5386 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-4.html @@ -0,0 +1,181 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: System Configuration Requirements for Compiling MythTV. </TITLE> + <LINK HREF="mythtv-HOWTO-5.html" REL=next> + <LINK HREF="mythtv-HOWTO-3.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc4" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-5.html">Next</A> +<A HREF="mythtv-HOWTO-3.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc4">Contents</A> +<HR> +<H2><A NAME="Setting_up_paths"></A> <A NAME="s4">4.</A> <A HREF="mythtv-HOWTO.html#toc4">System Configuration Requirements for Compiling MythTV. </A></H2> + +<P>Before you compile MythTV from the current source tarball or from +<B>subversion</B>, you may need to modify your system configuration in a +few ways.</P> +<P>In general, if you install MythTV from pre-packaged binaries for your Linux +distribution/version, you don't need to be too concerned about the issues in +this section of the HOWTO - the install script for the packages should take +care of them. However, this section is still recommended reading which may +help if the packager skipped a step in their packaging.</P> + +<H2><A NAME="ss4.1">4.1</A> <A HREF="mythtv-HOWTO.html#toc4.1">Software requirements for compiling MythTV</A> +</H2> + +<H3>General requirements</H3> + +<P>MythTV is written in C++ and requires a fairly complete, but standard, +compilation environment, including a recent g++ compiler, <CODE>make</CODE>, and +appropriate header files for shared libraries. Any standard Linux +distribution should be able to install a suitable compilation environment +from its packaging system. Section 3.2 of this HOWTO provides some details +of how to install the required environment for many distributions.</P> +<P>Subsequent sections of this chapter address the few oddities that you may +have to adjust by hand before you compile MythTV.</P> +<P>The reference compilation system for MythTV is Ubuntu.</P> + +<H2><A NAME="ss4.2">4.2</A> <A HREF="mythtv-HOWTO.html#toc4.2">Shared-Library requirements for MythTV </A> +</H2> + +<H3><A NAME="modifying_ld.so.conf"></A> Modifying /etc/ld.so.conf </H3> + +<P>The runtime manager for shared libraries, <B>/lib/ld.so</B>, gets +information about the locations and contents of shared libraries from +<CODE>/etc/ld.so.cache</CODE>, a file created by <B>ldconfig</B> from +information in <CODE>/etc/ld.so.conf</CODE>. Because MythTV installs some +shared libraries in <CODE>/usr/local/lib</CODE>, that directory needs to be +added to the list of directories for <B>ld.so</B> to search when doing +runtime linking of programs, if it is not already there. +You do this, as root, by editing <CODE>/etc/ld.so.conf</CODE>, then +running <B>ldconfig</B>. There are many ways to do this; one that +works is to enter this series of commands:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ su - +# echo /usr/local/lib >> /etc/ld.so.conf +# /sbin/ldconfig +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H2><A NAME="ss4.3">4.3</A> <A HREF="mythtv-HOWTO.html#toc4.3">Environment variable requirements for MythTV</A> +</H2> + +<H3>General requirements</H3> + +<H3>QT libraries and binaries</H3> + +<P>The compiler needs to be able to locate QT binaries and libraries in +order to compile MythTV. QTDIR needs to be set and the directory holding the +QT binaries needs to be added to your PATH. Your distribution may already +be making these changes as a part of the installation of the software +prerequisites detailed earlier.</P> +<P>One way to do this is as follows: +<A NAME="Checking_that_it_worked"></A> </P> +<P>Open a shell and execute the following: +<BLOCKQUOTE><CODE> +<PRE> +$ echo $PATH +/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/games:/usr/lib/qt3/bin:/home/mythtv/bin:/usr/lib/qt3/bin +$ echo $QTDIR +/usr/lib/qt3 +$ which qmake +/usr/lib/qt3/bin/qmake +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>For Mandriva, you should see a value like <CODE>/usr/lib/qt3</CODE> for +<CODE>QTDIR</CODE> and <CODE>/usr/lib/qt3/bin</CODE> should be in $PATH.</P> +<P>For Gentoo, you should see a value like <CODE>/usr/qt/3</CODE> for <CODE>QTDIR</CODE> +and <CODE>/usr/qt/3/bin</CODE> should be in $PATH.</P> +<P>If you don't, do not proceed past this step until you have resolved this +error. You may need to manually specify the QTDIR and PATH at the shell +prompt before compiling.</P> +<P>Also, check that there has been a link created in +<CODE>/usr/lib/qt3/mkspecs</CODE> (<CODE>/usr/share/qt3/mkspecs</CODE> for Debian) +called <CODE>default</CODE>. If not, you'll get errors during the compile. See +the Troubleshooting Section for more information.</P> +<H3>Distribution-Specific Notes</H3> + +<H3>Mandriva</H3> + +<P>The following instructions work for Mandriva using +<B>bash</B> as the shell, and may be applicable for a distribution which +uses <CODE>/etc/profile.d</CODE>.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Mandriva 10 installs a <CODE>/etc/profile.d/qtdir3.sh</CODE> +file, but it doesn't include the addition of the PATH variable. If you're +running Mandriva 10, don't create a <CODE>mythtv.sh</CODE> file as detailed +below; edit the <CODE>qtdir3.sh</CODE> file and add the PATH statement within +the if / fi block.</CAPTION> +</FIGURE> + +As root, create the following file in <CODE>/etc/profile.d</CODE> The example +filename is "mythtv.sh". Use what you feel is appropriate.</P> +<P>Open a shell, and switch to superuser mode. </P> +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: ^D means press CTRL and d at the same time.</CAPTION> +</FIGURE> + +<BLOCKQUOTE><CODE> +<PRE> +$ su +# cd /etc/profile.d +cat > mythtv.sh +export QTDIR=/usr/lib/qt3 +export PATH=$PATH:/usr/lib/qt3/bin +^D + +# chmod a+x mythtv.sh +# exit +$ exit +</PRE> +</CODE></BLOCKQUOTE> + +The last two commands are to exit out of the shell. This way, when you next +open a shell your new commands +will take effect.</P> + +<H3><A NAME="devperms"></A> Device Permissions </H3> + +<P>MythTV will need access to the video4linux devices on your system. By +default, your distribution may restrict access to these devices to the +logged-in user, so if you will be automatically starting +<B>mythbackend</B> from a script rather than an interactive terminal +session you will need to make some adjustments.</P> +<P><B>NOTE</B>: The following instructions are accurate for Mandriva.</P> +<P>Check for a file called <CODE>/etc/security/console.perms</CODE>. Open the file +in your favorite text editor and look for a line that has: +<BLOCKQUOTE><CODE> +<PRE> +<console> 0600 <v4l> 0600 root.video +</PRE> +</CODE></BLOCKQUOTE> + +and replace it with +<BLOCKQUOTE><CODE> +<PRE> +<console> 0666 <v4l> 0666 root.video +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>What we're doing is allowing read and write access to the files in the +video4linux directory.</P> +<HR> +<A HREF="mythtv-HOWTO-5.html">Next</A> +<A HREF="mythtv-HOWTO-3.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc4">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-5.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-5.html new file mode 100644 index 0000000..0ecf975 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-5.html @@ -0,0 +1,426 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: Downloading and compiling. </TITLE> + <LINK HREF="mythtv-HOWTO-6.html" REL=next> + <LINK HREF="mythtv-HOWTO-4.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc5" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-6.html">Next</A> +<A HREF="mythtv-HOWTO-4.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc5">Contents</A> +<HR> +<H2><A NAME="DownloadAndCompile"></A> <A NAME="s5">5.</A> <A HREF="mythtv-HOWTO.html#toc5">Downloading and compiling. </A></H2> + +<P>Get MythTV from the +<A HREF="http://www.mythtv.org">http://www.mythtv.org</A> web site. There are two installation methods +you may choose from. The first is to download the latest release in tarball +format and compile. The tarball release of MythTV should work on a wide +variety of systems and should be the preferred method for new users. If you +wish to use the <B>subversion</B> copy of MythTV you may obtain it from +<A HREF="http://svn.mythtv.org">http://svn.mythtv.org</A></P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: If you are going to use <B>subversion</B> to +compile MythTV rather than using the distribution tarball, you <EM>must</EM> +join the +<A HREF="http://www.mythtv.org/mailman/listinfo/mythtv-commits/">http://www.mythtv.org/mailman/listinfo/mythtv-commits/</A> and +<A HREF="http://www.mythtv.org/mailman/listinfo/mythtv-dev/">http://www.mythtv.org/mailman/listinfo/mythtv-dev/</A> mailing lists to +keep up to date with the current status of the code. Code obtained from +subversion has no guarantees regarding stability, etc.</CAPTION> +</FIGURE> +</P> +<P>If you are in North America you will use the Schedules Direct grabber which is +built-in to MythTV. You <EM>do not</EM> need to install XMLTV (so you may +skip XMLTV-related instructions), but you need <B>wget</B> version 1.9.1 +or higher.</P> +<P>Get XMLTV from +<A HREF="http://xmltv.sourceforge.net">http://xmltv.sourceforge.net</A>. Download the latest version (0.5.51).</P> +<P> +<HR> +<PRE> +NOTE for Mandriva users: If you have added a "PLF" mirror, you may skip the +next step and type: + +# urpmi libmp3lame0 libmp3lame0-devel + +After downloading, be sure to install both: +# rpm -Uvh lame* +</PRE> +<HR> +</P> +<P>Get lame from +<A HREF="http://lame.sourceforge.net/">http://lame.sourceforge.net/</A>. Download the source code to v3.96.1 +by following the links from "Using" through "Download...".</P> + +<H2><A NAME="ss5.1">5.1</A> <A HREF="mythtv-HOWTO.html#toc5.1">Building LAME</A> +</H2> + +<P>Open a shell and switch to the directory where you saved lame. +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xzf lame-3.96.1.tar.gz +$ cd lame-3.96.1 +$ ./configure +$ make +$ make test +$ su +# make install +</PRE> +</CODE></BLOCKQUOTE> + +Check that it worked: +<BLOCKQUOTE><CODE> +<PRE> +# ls -l /usr/local/lib +-rw-r--r-- 1 root root 381706 Nov 4 14:22 libmp3lame.a +-rwxr-xr-x 1 root root 674 Nov 4 14:22 libmp3lame.la* +lrwxrwxrwx 1 root root 19 Nov 4 14:22 libmp3lame.so -> +libmp3lame.so.0.0.0* +lrwxrwxrwx 1 root root 19 Nov 4 14:22 libmp3lame.so.0 -> +libmp3lame.so.0.0.0* +-rwxr-xr-x 1 root root 360197 Nov 4 14:22 +libmp3lame.so.0.0.0* + +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss5.2">5.2</A> <A HREF="mythtv-HOWTO.html#toc5.2">XMLTV</A> +</H2> + +<H3>Red Hat Linux and Fedora Core:</H3> + +<P>RPMs for <B>XMLTV</B> and all of its dependencies can be obtained from +<A HREF="http://ATrpms.net/name/xmltv/">http://ATrpms.net/name/xmltv/</A>. The web page has a +list of all the dependent packages you must download and install. +<BLOCKQUOTE><CODE> +<PRE> +# rpm -Uvh xmltv* perl* +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you install from this location you may skip to +<A HREF="#manually_building_mythtv">Manually building MythTV</A>.</P> +<H3>Mandriva</H3> + +<P>RPMs for <B>XMLTV</B> and all of its dependencies are located in +Mandriva's "contrib". If you have added a contrib mirror, try installing +<B>XMLTV</B>: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi xmltv xmltv-grabbers +</PRE> +</CODE></BLOCKQUOTE> + +If this does not work, it is possible that contrib for your Mandriva version +does not have <B>XMLTV</B>, so you may install the XMLTV prerequisites by typing: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi perl-xml-twig perl-xml-writer perl-datemanip perl-libwww-perl +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>and skip straight to the XMLTV compilation step.</P> + +<H3>Manual installation</H3> + +<P> +<A NAME="untarring_xmltv"></A> Untar the xmltv file: +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xjf xmltv-0.5.51.tar.bz2 +</PRE> +</CODE></BLOCKQUOTE> + +Install the xmltv prerequisites. The following prerequisites are the +minimum required; when you actually start running the xmltv setup program it +may alert you to other modules that are required.:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ su +# perl -MCPAN -e shell +cpan> install XML::Twig +cpan> install Date::Manip +Date::Manip is up to date. +cpan> install LWP +cpan> install XML::Writer +cpan> exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Change to the XMLTV directory and compile it: +<BLOCKQUOTE><CODE> +<PRE> +$ cd xmltv-0.5.51 +$ perl Makefile.PL +</PRE> +</CODE></BLOCKQUOTE> + +You can answer "N" to the tv_check, tv_pick_cgi questions. Say "yes" to +the grabber required for your location.</P> +<P>You may get errors about modules not being installed. You will need to +resolve any missing dependencies at this point, or your grabber may not work +correctly. +<BLOCKQUOTE><CODE> +<PRE> +$ make +$ make test +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ConfigureSD"></A> <A NAME="ss5.3">5.3</A> <A HREF="mythtv-HOWTO.html#toc5.3">Configuring the Schedules Direct service </A> +</H2> + +<P>As of 2007-09-01, Tribune Media Services will no longer offer free guide +data. Schedules Direct is a non-profit organization which has licensed the +data to make it available to users of Freeware and Open Source applications.</P> +<P>If you wish to use Schedules Direct, you'll need to establish a user +account. Go to +<A HREF="http://www.schedulesdirect.org">http://www.schedulesdirect.org</A> and click on the "Membership" link. </P> +<P>Once you've read and agreed to the Subscriber Agreement, Terms of Use and +Privacy Policy proceed to the lineup choices and configure your account for +your particular location and the channels that you have. This configuration +will be imported into MythTV when you first run the <B>mythtv-setup</B> +program.</P> + +<P> +<A NAME="manually_building_mythtv"></A> </P> +<H2><A NAME="ss5.4">5.4</A> <A HREF="mythtv-HOWTO.html#toc5.4">Manually building MythTV</A> +</H2> + +<P>If you are going to use <B>subversion</B>, execute the following +instructions to obtain the latest version of MythTV:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ mkdir mythtv +$ svn co http://svn.mythtv.org/svn/trunk/ mythtv +$ cd mythtv +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>To use a release version, you can execute: +<BLOCKQUOTE><CODE> +<PRE> +$ mkdir mythtv-release-0.21 +$ svn co http://svn.mythtv.org/svn/branches/release-0-21-fixes/ mythtv-release-0.21 +$ cd mythtv-release-0.21 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><B>NOTE</B>: Using a svn version of the code allows you to stay +up-to-date with changes. So, if there's an update to the 0.21 release and +you originally obtained it using svn, you could enter the +mythtv-release-0.21 directory and type "svn up", which will update your copy +with the fixed version from the website. You would then recompile and +install the updated 0.21 code.</P> +<P>If you are using the tarball, then unpack it: +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xjf mythtv-0.21.tar.bz2 +$ cd mythtv-0.21 +$ ./configure +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you wish to change options, run <B>./configure --help</B> to +see what is available and to override and automatically detected options. +See the <CODE>config.log</CODE> file after running <B>configure</B> to see +previous runs.</P> +<P>To compile: +<BLOCKQUOTE><CODE> +<PRE> +$ make -j 2 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The MythTV compile can take advantage of multiple CPUs, SMP and +Hyperthreading. If you want to build MythTV on a multi-CPU machine (or with +<B>distcc</B>), specify "-j numjobs", where "numjobs" is greater than 2. +In the above example, we had two concurrent jobs executing, which is +recommended for a single CPU system. Do not set the number of jobs too +high, or your compile will actually take longer to complete than it would if +you did a "normal" build.</P> +<P>If you are using <B>distcc</B>, and you had two other host machines (red, blue) +participating, you would do something like: +<BLOCKQUOTE><CODE> +<PRE> +$ export DISTCC_HOSTS='localhost red blue' +$ make -j 6 CXX=distcc +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The actual speed-up, if any, is dependant on a number of factors, such as +number of CPUs / hosts, etc. The <B>distcc</B> documentation recommends +using a <CODE>-j</CODE> value of twice the number of CPUs available to keep all +of them busy.</P> +<P>Some timing information. The following should only be used for +illustration; your actual results may vary. The test involves a complete +<CODE>make distclean</CODE> to the final binary. +<UL> +<LI>P4 3.2Ghz HT: "standard" make: 12m 49s</LI> +<LI>P4 3.2Ghz HT: make -j 2: 11m 24s </LI> +</UL> +</P> +<P>In the above example, we see that with a single CPU, a multi-stage +<B>make</B> does not significantly decrease compile time.</P> +<P>Once the compile is done, switch to superuser: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: subsequent configuration steps assume that you are within +the MythTV directory that you <CODE>cd</CODE>'d to above.</CAPTION> +</FIGURE> +</P> + +<H3>Enabling real-time scheduling of the display thread.</H3> + +<P>MythTV supports real-time scheduling of the video output thread. There +are three ways to go about enabling this: You can use rlimits, you can use +the realtime security module, or on older systems you can SUID the +executable. Enabling real-time scheduling is optional, but can make the +video display smoother, especially if you are decoding HDTV.</P> + +<H3>rlimits</H3> + +<P>The rlimits method is the preferred method and is included in Linux +2.6.12 and above. Unfortunately, you need PAM version 0.79 or above, which +may not be supported by your distribution yet. Assuming anyone running +<B>mythfrontend</B> is in the audio group and rlimits are supported, all +you need to do is place this in your <CODE>/etc/security/limits.conf</CODE></P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +* - rtprio 0 +* - nice 0 +@audio - rtprio 50 +@audio - nice 0 +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3>realtime module</H3> + +<P>The second option is to use the Linux realtime kernel module. +This is will be phased out over time, but is currently supported +by many distributions that do not yet support rlimits. If you are +not using the distribution kernel you must configure your kernel +with: +<BLOCKQUOTE><CODE> +<PRE> +Security options : [*] Enable different security models +Security options : [M] Default Linux Capabilties +</PRE> +</CODE></BLOCKQUOTE> + +You may also need to install the realtime module, using your distribution's +realtime package. Assuming the users who will be running +<B>mythfrontend</B> will be in the audio group you can get the GUID of a named +group like so: +<BLOCKQUOTE><CODE> +<PRE> +$ grep audio /etc/group +</PRE> +</CODE></BLOCKQUOTE> + +If the number printed out from the grep was 18, you can now load +this module as root before starting <B>mythfrontend</B>: +<BLOCKQUOTE><CODE> +<PRE> +# modprobe realtime gid=18 +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3>run as root option (not safe)</H3> + +<P>The final and least preferred option is to set the sticky bit +on the <B>mythfrontend</B> executable. This <B>opens a security hole</B>, +but is the only option on systems that do not support either +rlimits or the realtime module. This does not work on modern +distributions either, and is <B><EM>not recommended</EM></B> +on any system connected to the Internet. This may also make it +impossible to debug MythTV without running <B>gdb</B> as root. If you +would still like to do this, you just need to run this as root: +<BLOCKQUOTE><CODE> +<PRE> +# chmod a+s /usr/local/bin/mythfrontend /usr/local/bin/mythtv +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3><A NAME="frontend-only"></A> Frontend-only configuration </H3> + +<P>Since MythTV uses a client/server architecture, multiple frontend +computers can simultaneously access content on a Myth system. Live TV, +watching and scheduling recordings, etc. are all possible from multiple +frontends.</P> +<P>To get a better picture of what is needed to run a frontend, note the +following: +<LI>You do NOT need the MySQL server installed on your remote frontend</LI> +<LI>You do NOT need XMLTV installed on your remote frontend</LI> +<LI>You do NOT need to run the mythtv-setup program on +your frontend machine</LI> +</P> +<P>Other than the exclusion of the MySQL server and XMLTV, the MythTV +compilation procedure is the same as when you're setting up both a backend +and a frontend. However, you <EM>will</EM> need to install the database +access libraries.</P> +<P>Once MythTV is compiled and installed: +<LI>Run the mythtv-setup program on your Master backend. Under the "General" +menu, change the IP address of the current machine (by default, "127.0.0.1") +to the real external IP address - 127.0.0.1 is the loopback address and no +external machine can access it. Change the Master Server IP setting to the +same IP address as well.</LI> +<LI>Run the mythfrontend program on your frontend machine, +and a "Database Configuration" screen should appear. +Set the "Host name" field to point to your Master backend's IP address.</LI> +</P> + +<H2><A NAME="Gentoo_build"></A> <A NAME="ss5.5">5.5</A> <A HREF="mythtv-HOWTO.html#toc5.5">Gentoo </A> +</H2> + +<P>Installation of MythTV on Gentoo consists of simply emerging the desired +ebuild because all of the packages are now part of the official Portage tree. +<BLOCKQUOTE><CODE> +<PRE> +$ su - +# emerge --sync # make sure portage is up to date. +# vi /etc/make.conf +</PRE> +</CODE></BLOCKQUOTE> + +Add mysql to your USE variable. i.e. <CODE>USE="mysql ...."</CODE> +<BLOCKQUOTE><CODE> +<PRE> +# emerge mythtv +</PRE> +</CODE></BLOCKQUOTE> +</P> +<HR> +<A HREF="mythtv-HOWTO-6.html">Next</A> +<A HREF="mythtv-HOWTO-4.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc5">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-6.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-6.html new file mode 100644 index 0000000..2f9af20 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-6.html @@ -0,0 +1,176 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: MySQL.</TITLE> + <LINK HREF="mythtv-HOWTO-7.html" REL=next> + <LINK HREF="mythtv-HOWTO-5.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc6" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-7.html">Next</A> +<A HREF="mythtv-HOWTO-5.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc6">Contents</A> +<HR> +<H2><A NAME="mysql"></A> <A NAME="s6">6.</A> <A HREF="mythtv-HOWTO.html#toc6">MySQL.</A></H2> + +<P>When you install MySQL 5.x you will also want to comment +out "log-bin" in your <CODE>my.cnf</CODE> configuration file. This option will +quickly fill your "/var" disk partition with many gigabytes of data, +unless you are doing database replication and deleting these files regularly.</P> +<H2><A NAME="ss6.1">6.1</A> <A HREF="mythtv-HOWTO.html#toc6.1">Distribution-specific information</A> +</H2> + +<H3>Mandriva</H3> + +<P>If this is the system maintaining the database, make sure that MySQL is +running and started at boot. Click on Mandriva Control +Center->System->Services, find MySQL and click the "On Boot" button and the +"Start" button if the MySQL status shows that it isn't running yet.</P> +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: There have been reports that MySQL isn't starting at boot. +If this is happening to you, try running the following commands.</CAPTION> +</FIGURE> + +<BLOCKQUOTE><CODE> +<PRE> +$ su +# chkconfig --level 35 mysql on +# /etc/rc.d/init.d/mysql start +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3>Red Hat Linux and Fedora Core</H3> + +<P>If this is the system maintaining the database, make sure that MySQL is +running and started at boot. Click on Redhat menu>Server Settings>Services +and enter the root password when asked. Check "mysqld" and then click Start. +Click Save, then close the window.</P> +<P>This can be done from the command line by typing: +<BLOCKQUOTE><CODE> +<PRE> +# /sbin/chkconfig mysqld on +# /sbin/service mysqld start +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3>Gentoo</H3> + +<P>After installing MySQL you need to initialize the database by running +<B>mysql_install_db</B> as root. </P> +<H2><A NAME="ss6.2">6.2</A> <A HREF="mythtv-HOWTO.html#toc6.2">Setting up the initial database</A> +</H2> + +<P>This step is only required on the system maintaining the database, which +may or may not be one of your MythTV boxes. If the database is on a +non-MythTV machine you'll need to copy the <CODE>database/mc.sql</CODE> file to it.</P> +<P>To setup the initial MySQL databases: +<BLOCKQUOTE><CODE> +<PRE> +$ cd database +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H3>Mandriva and Red Hat Linux/Fedora Core</H3> + +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root < mc.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H3>Debian 3.0</H3> + +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ mysql < mc.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H3>Gentoo</H3> + +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ su +# mysql < /usr/share/mythtv/database/mc.sql +</PRE> +</CODE></BLOCKQUOTE> + +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: It is good practice to set a root password for MySQL. Instructions for doing so can be found on MySQL's web site at +<A HREF="http://www.mysql.com/doc/en/Security.html">http://www.mysql.com/doc/en/Security.html</A>.</CAPTION> +</FIGURE> +</P> +<H3><A NAME="modify_perm_mysql"></A> Modifying access to the MySQL database for multiple systems </H3> + +<P>If you're going to have multiple systems accessing a master database, +you must grant access to the database from remote systems. By default, the +<CODE>mc.sql</CODE> script is only granting access to the local host.</P> +<P>To allow other hosts access to your master database, you can either set it +up for no security at all, or with more granularity. Note that the "%" is +the wildcard character in MySQL.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: The "no security" option is <EM>very</EM> dangerous unless +you're in a controlled environment.</CAPTION> +</FIGURE> + +This example has no security at all, and allows access from any host. +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root mythconverg +mysql> grant all on mythconverg.* to mythtv@"%" identified by "mythtv"; +mysql> flush privileges; +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>For a more secure setup, you can restrict which machines or subnets have +access. If you have a complete DNS system operational, you could do the +following: +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root mythconverg +mysql> grant all on mythconverg.* to mythtv@"%.mydomain.com" identified by "mythtv"; +mysql> flush privileges; +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Finally, if you just want to restrict by IP subnet (in this example, the +192.168.1. network): +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root mythconverg +mysql> grant all on mythconverg.* to mythtv@"192.168.1.%" identified by "mythtv"; +mysql> flush privileges; +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>You'll also need to check that the "networking" feature of MySQL is turned +on. Check that <CODE>/etc/mysql/my.cnf</CODE> <EM>does not</EM> contain +<CODE>skip-networking</CODE>. If it does, remove it. Also verify that +<CODE>bind-address</CODE> is set to your IP address instead of +<CODE>127.0.0.1</CODE>. If you change either of these items, restart +<B>MySQL</B>.</P> +<P><B>NOTE</B>: Your distribution may have a customized MySQL configuration +file; in Mandriva, check <CODE>/etc/sysconfig/mysqld</CODE> for additional +configuration.</P> + +<HR> +<A HREF="mythtv-HOWTO-7.html">Next</A> +<A HREF="mythtv-HOWTO-5.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc6">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-7.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-7.html new file mode 100644 index 0000000..97bc763 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-7.html @@ -0,0 +1,130 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: Configuring Sound.</TITLE> + <LINK HREF="mythtv-HOWTO-8.html" REL=next> + <LINK HREF="mythtv-HOWTO-6.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc7" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-8.html">Next</A> +<A HREF="mythtv-HOWTO-6.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc7">Contents</A> +<HR> +<H2><A NAME="s7">7.</A> <A HREF="mythtv-HOWTO.html#toc7">Configuring Sound.</A></H2> + +<P>If your video doesn't appear to be in-sync with your audio and you're +using an analog video capture card and a soundcard to capture audio, it +could be because you are listening to the real-time audio from your video +card rather than after it's been processed and synchronized to the video by +MythTV. Because MythTV is a personal video recorder, "Live TV" isn't really +live - to let you pause live TV, MythTV is actually encoding the video, +saving to disk, and then playing it back. This procedure puts your MythTV +"live" TV about 2 seconds behind real-time, so it's important that you're +not listening to the live audio. However, if you're having an issue where +the audio and video aren't synchronized by small but varying amount, it's +most likely because the sound driver that you're using doesn't have the +DSP_CAP_REALTIME capability. This was the case with ALSA (0.5), but not +with newer versions. See the +<A HREF="mythtv-HOWTO-22.html#Troubleshooting_Audio">Troubleshooting Audio</A> section for more information if you're having +issues with sound. Also, ensure that no other programs are grabbing the +audio output, like <B>arts</B> or <B>esd</B>.</P> +<P>What you need to do is to mute the "line-in" of your sound card and also +set it as the recording source.</P> +<P>There are two ways to do this. Graphically, and from the command line.</P> + +<H2><A NAME="ss7.1">7.1</A> <A HREF="mythtv-HOWTO.html#toc7.1">Graphically setting up the mixer</A> +</H2> + +<H3>Mandriva and Red Hat Linux/Fedora Core</H3> + +<P>Open Kmix by clicking K->Multimedia->Sound->Kmix for Mandriva, or +<PRE> +RedHat Menu>Sound & Video>Volume Control +</PRE> + on Red Hat/Fedora.</P> +<P>Click on Settings->Configure Make sure that "Tick Marks" and "Show +labels" have "X"'s in them. This will make it easier to find the correct +audio source. Click OK.</P> +<P>On the mixer page, look for Line-In on your sound card. You should see +two LED's - a green one at the top, and a red one at the bottom. The green +one at the top is for muting; you want to make sure that the green LED is a +dark green, meaning that it's "off". You also want to click on the red LED +so that it turns bright red, indicating that it's "ON"; this insures that +the Line-in is used as the source. Click OK, and make sure that you save +the settings so that this is your default.</P> + +<H3>Using ALSA.</H3> + +<P>To use ALSA, you'll need to correctly setup your +<CODE>asoundrc</CODE> file. Configuring this file is beyond the scope of this +HOWTO. Once ALSA is working correctly, change the output sound device in +mythfrontend->setup->Audio from <CODE>/dev/dsp</CODE> to <CODE>ALSA:default</CODE>. +This field may be edited to suit your ALSA requirements.</P> + +<H2><A NAME="ss7.2">7.2</A> <A HREF="mythtv-HOWTO.html#toc7.2">Setting the mixer from the command line</A> +</H2> + +<P>If you have installed the alsa-utils package, then the <B>amixer</B> +program can be used to setup the mixer. The "Master" volume setting is only +required on a frontend machine to ensure that the sound channels are unmuted +and configured for outputting sound. The "Line" and "Capture" controls are +required for your sound card to actually capture audio from the external +Line-in if it's connected to an analog frame grabber. Not all sound cards +have a "Capture" control, but if yours does and you don't set it then MythTV +will not capture audio.</P> +<P> +<HR> +<PRE> +Note the spelling in the following commands. +</PRE> +<HR> + +<BLOCKQUOTE><CODE> +<PRE> +$ amixer set Master,0 100%,100% unmute +$ amixer set PCM,0 100%,100% unmute +$ amixer set Line,0 75%,75% mute captur +$ amixer set Capture,0 100%,100% captur +$ su +# alsactl store +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you have multiple sound cards, then use the <CODE>-c</CODE> parameter to +specify which card to adjust. Note that the first card will be "0", the +second will be "1", etc.</P> +<P>That takes care of setting the volume correctly, and the ALSA startup script +will restore the volume after a reboot. If you find that your sound is +distorted, it's possible that the levels in the above examples are too high +for your particular hardware combination. Try reducing the percentages by +5-10% and checking again. Once you're satisfied, re-run the <CODE>alsactl +store</CODE> command.</P> +<P>You may also use the <B>alsamixer</B> program to set the volume. If you +are using an ALSA version after 1.0.6, use <B>alsamixer -V all</B> First, +start <B>alsamixer</B> from the command line. You should start out on the +"Master" volume control slider. Use the up and down cursor to set the +master volume to around 75%. Next, use the left and right cursor keys to +move around on the screen until you find the "Line" slider. Press SPACE to +set it as the capture source, set the level to around 50-75% and press "M" +to mute it. You can now press ESC to exit out of the <B>alsamixer</B> +program. You can also have MythTV manage all volume and mute settings, but +this will only affect the "Master" or PCM volume, not the capture volume. See +the mythfrontend setup page for options.</P> +<P>Finally, if you've performed all of the above steps, and you still don't seem to have any sound, it's possible that your video capture device is muting the audio output. +<BLOCKQUOTE><CODE> +<PRE> +$ v4lctl -c /dev/video0 setattr mute off +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<HR> +<A HREF="mythtv-HOWTO-8.html">Next</A> +<A HREF="mythtv-HOWTO-6.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc7">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-8.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-8.html new file mode 100644 index 0000000..98d4b66 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-8.html @@ -0,0 +1,530 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: Setting up a remote control.</TITLE> + <LINK HREF="mythtv-HOWTO-9.html" REL=next> + <LINK HREF="mythtv-HOWTO-7.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc8" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-9.html">Next</A> +<A HREF="mythtv-HOWTO-7.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc8">Contents</A> +<HR> +<H2><A NAME="s8">8.</A> <A HREF="mythtv-HOWTO.html#toc8">Setting up a remote control.</A></H2> + +<P>MythTV does not have native remote control receiver and decoder software +built-in. Instead, remote control functions are implemented by cooperating +with <B>lirc</B>, the Linux Infrared Remote Control program. <B>lirc</B> +handles the IR hardware and passes keystrokes to MythTV, which then acts as +if the user had pressed the keys on the keyboard. The file +<CODE>keys.txt</CODE> describes the keys used to control MythTV.</P> +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: If you are running Mandriva, you may install +<B>lirc</B> by executing: <CODE># urpmi lirc lirc-remotes</CODE> and bypass +the manual compilation steps described below by jumping to the +<A HREF="#completing_lirc_install">Completing the lirc install</A> section. See the contrib/mandrake91.etc.sysconfig.lircd file for an example of how to +configure lircd.</CAPTION> +</FIGURE> +</P> +<P>Some IR devices require a kernel recompile, and some don't. However, all at +least require having the kernel source available as a resource for the lirc +build process. </P> + +<H2><A NAME="ss8.1">8.1</A> <A HREF="mythtv-HOWTO.html#toc8.1">Gentoo</A> +</H2> + +<P>To install lirc on Gentoo, all you need to do is: +<BLOCKQUOTE><CODE> +<PRE> +# emerge lirc +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss8.2">8.2</A> <A HREF="mythtv-HOWTO.html#toc8.2">Obtaining and compiling lirc</A> +</H2> + +<P>You're going to need to download and compile <B>lircd</B>. Go to +<A HREF="http://www.lirc.org">http://www.lirc.org</A> and download lirc; as +of 2006-01-21, the version available is 0.8.0. Grab the remotes.tar.bz2 file as +well. +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xjf lirc-0.8.0.tar.bz2 +$ cd lirc-0.8.0 +$ ./setup.sh +</PRE> +</CODE></BLOCKQUOTE> + +You're going to need to know what sort of receiver you have and where it's +connected. In the case of the Pinnacle Studio TV card, with the IR receiver +connected to COM1 (/dev/ttys0), once the configuration menu comes up, +perform the configuration by going to Driver Configuration->Other Serial +Port Devices->Pinnacle Systems Receiver->OK and on the next page select +COM1->OK.</P> +<P>Each remote is different; some remote receivers connect directly to your +capture card and not to a serial port, so make sure that you've got the +correct one.</P> +<P>You then click "Save Configuration and run configure" to continue.</P> +<P>Make sure you read the last text generated by the configure step. It will +tell you if you require a kernel recompile, and what the name of your kernel +module will be (if necessary). For instance a home-built receiver may +require a kernel recompile, so you would be notified that you will have to +load the lirc_serial module. If you did not get any such messages skip the +kernel recompile steps below and go directly to making and installing the +lirc driver.</P> +<P>Once the configuration step is complete: +<BLOCKQUOTE><CODE> +<PRE> +$ make +$ su +# make install +# chmod 666 /dev/lircd +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>At this point, if you're using a serial receiver, check that there's a +<CODE>lirc</CODE> device in <CODE>/dev</CODE>: +<BLOCKQUOTE><CODE> +<PRE> +$ ls -l /dev/li* +lr-xr-xr-x 1 root root 5 Jan 27 09:00 /dev/lirc -> ttyS0 +srw-rw-rw- 1 root root 0 Jan 27 15:01 /dev/lircd= +prw-r--r-- 1 root root 0 Jan 27 09:00 /dev/lircm| +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>As you can see, there's a link from /dev/lirc to ttyS0, a.k.a. "COM1", which is +appropriate for the Pinnacle Systems PCTV Pro. However, you may notice +something like this: +<BLOCKQUOTE><CODE> +<PRE> +crw------- 1 root root 61, 0 Dec 31 1969 lirc +</PRE> +</CODE></BLOCKQUOTE> + +Some IR receivers (including some homebrew units) use a character device as +their data interface as opposed to a link to a serial port. If the <CODE>make +install</CODE> step has created a character device for you, don't replace it +with a link to a COM port.</P> +<P>So, if the link or character device was not created (but should have been), +ensure that you ran the <CODE>make install</CODE> step as root. If it still +doesn't work, then there are three options. The first option is to re-read +the <B>lirc</B> documentation to determine whether your IR receiver is a +character device or should be a link to a serial port and to create the +link/character device manually. In this example, the IR device is connected +to ttyS0. If it were connected to "COM2", then use ttyS1, etc. +<BLOCKQUOTE><CODE> +<PRE> +$ su +# cd /dev +# ln -sf ttyS0 lirc +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: The above example assumes that your receiver uses the +standard serial driver. Some receivers do not, including receivers that +plug into a TV capture card. Check the lirc documentation, but it may be +necessary to replace the link created above with a character pipe:</CAPTION> +</FIGURE> + +<BLOCKQUOTE><CODE> +<PRE> +# mknod /dev/lirc c 61 0 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>See the lirc documentation for additional information. The lirc +installation <EM>should</EM> create this for you, so manually creating it +indicates that your lirc installation may have other issues.</P> +<P>The second option is to post your issue to the <EM>lirc</EM> list, not the +mythtv-users list. The lirc programmers will be the ones that can assist +you best.</P> +<P>The third option is to dispense with lirc altogether by purchasing an IR +keyboard (various options exist, although Chicony appears to work for some +people) and a learning remote control. The IR keyboard receiver plugs into +the PS/2 keyboard port on your PC and you would train your learning remote +to emulate the various keystrokes from <CODE>keys.txt</CODE> of your IR +keyboard. Using this method removes lirc entirely from the picture - your +remote will be sending keypresses that your PC "sees" on the keyboard port.</P> + +<H2><A NAME="completing_lirc_install"></A> <A NAME="ss8.3">8.3</A> <A HREF="mythtv-HOWTO.html#toc8.3">Completing the lirc install </A> +</H2> + +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE to Mandriva 9.1 users</B>: skip to the manual start paragraph +below.</CAPTION> +</FIGURE> +</P> +<P>If the lirc configure program / compile did not mention anything about a +kernel module, then you are finished. If it did mention a kernel module, you +must edit the <CODE>/etc/modules.conf</CODE> file. Add this line as the first +thing in the file. It must come first, or it may not work. +<BLOCKQUOTE><CODE> +<PRE> +alias char-major-61 XXX +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>replace XXX with the name which you determined earlier, which in this +example was "lirc_serial" +<BLOCKQUOTE><CODE> +<PRE> +$ su +# modprobe lirc_serial +# /sbin/ldconfig +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Next, we're going to manually start lircd the first time. Mandriva 9.1 +users, type: <CODE># /etc/rc.d/init.d/lircd start</CODE> instead of: +<BLOCKQUOTE><CODE> +<PRE> +# /usr/local/sbin/lircd +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><B>NOTE</B>: Read this next section if you're not familiar with how lirc works!</P> +<P>There are two separate files used by lirc, and both are required for your +remote control to do anything useful. First is the <CODE>lircd.conf</CODE> file. +<CODE>lircd.conf</CODE> tells the lirc daemon how to interpret the IR pulses +that it receives from a remote control and what name to assign to each +sequence of pulses. Without getting too involved, a particular series of +pulses may correlate to "Channel Up". The <CODE>lircd.conf</CODE> file will +then contain a line that looks something like this:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> + ChannelUp 0x0000000000001020 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The <CODE>lircd.conf</CODE> file can have multiple remote controls defined.</P> +<P>The second file is <CODE>lircrc</CODE>, which takes the name of the button which +was pressed ("ChannelUp") in the above example, and correlates that to an +action to be performed by a program using the remote control. So in MythTV, +ChannelUp means one thing, while in <B>mplayer</B> it means something +different. <CODE>lircrc</CODE> gives you the flexibility of taking the name of +the button and having it perform different actions depending on which +program you're using at the time.</P> +<P><B>NOTE</B>: The definitions in <CODE>lircd.conf</CODE> come from the user +community, and there is no standard for the common button names. One +<CODE>lircd.conf</CODE> file may contain a definition for a button called +"ChannelUp", while another may contain a definition for "Chan+". Your +<CODE>lircrc</CODE> file must therefore be configured appropriately, or it won't +work.</P> +<P>If this fails, complaining of a missing <CODE>lircd.conf</CODE> file, then you +must find or make one. First look for a pre-made configuration file at +<A HREF="http://lirc.sourceforge.net/remotes/">http://lirc.sourceforge.net/remotes/</A>. Mandriva 9.1 users, look in +<CODE>/usr/share/lirc-remotes</CODE>. If you find one your remotes either on the +website or in <CODE>/usr/share</CODE>, download or copy the file, name it +<CODE>lircd.conf</CODE> and put it in your <CODE>/etc</CODE> directory. If you +couldn't find your remote, you must make your own <CODE>lircd.conf</CODE> file.</P> +<P>To make your own <CODE>lircd.conf</CODE> file +<BLOCKQUOTE><CODE> +<PRE> +$ irrecord myremote +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Follow the on-screen directions to train your remote and define keys. If +your remote ends up working well, you should consider submitting your +<CODE>lircd.conf</CODE> file back to the lirc developers. Once finished: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# cp myremote /etc/lircd.conf +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>now try to start lircd again: +<BLOCKQUOTE><CODE> +<PRE> +# /usr/local/sbin/lircd +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Now, we're going to add the commands necessary for lircd to run each time we +boot. Mandriva 9.1 users, you can execute: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# chkconfig --level 35 lircd on +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>All other distributions: +<BLOCKQUOTE><CODE> +<PRE> +# cd /etc/rc.d +# cat >> rc.local +echo "Starting lircd" +/usr/local/sbin/lircd +^D +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> + </P> +<P>This takes care of the lircd portion, which "listens" for the IR signals. If +everything went well, the install script for lircd put an appropriate +configuration file for your remote into <CODE>/etc/lircd.conf</CODE> This file +maps the buttons on the remote control to the IR pulses coming from the +receiver.</P> +<P>The next step is to convert those signals into something that can be used +to control MythTV. MythTV now includes native support for lirc and can +interact directly with </P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythtv-0.21/contrib/configfiles +$ cp lircrc.example ~/.lircrc +</PRE> +</CODE></BLOCKQUOTE> + +or +<BLOCKQUOTE><CODE> +<PRE> +$ cp lircrc.example.pinnaclestudiopctv ~/.lircrc +</PRE> +</CODE></BLOCKQUOTE> + +if you've got a Pinnacle Studio PCTV remote. +<BLOCKQUOTE><CODE> +<PRE> +$ irw +</PRE> +</CODE></BLOCKQUOTE> + +Start pressing the keys on your remote; <B>irw</B> will +print the name of the button as it is defined in your +<CODE>/etc/lircd.conf</CODE>. If you don't see anything at this point, you need +to troubleshoot further by going back to the lirc home page and investigating +from there.</P> +<P>If it is working, then press <B>CTRL-C</B> to abort the program. Once you +know that your remote is working, you can either recompile MythTV with +native lirc support by enabling it in <B>configure</B> or you +need to run the <B>irxevent</B> program, which takes the key presses and +sends them to MythTV. If you use native lirc support, you don't need to run +<B>irxevent</B>. If you are going to use irxevent, then you need to run +it like this: +<BLOCKQUOTE><CODE> +<PRE> +$ irxevent & +</PRE> +</CODE></BLOCKQUOTE> + +If <B>irxevent</B> isn't running, then MythTV will not respond to your remote +control unless you're using native lirc support.</P> + +<H2><A NAME="ss8.4">8.4</A> <A HREF="mythtv-HOWTO.html#toc8.4">Additional information for lirc</A> +</H2> + +<P>Take a look at the lircrc.example files in the <CODE>contrib/configfiles/</CODE> +directory. In my case, (Pinnacle Studio card) the channel up and down functions +weren't working, due to the fact that the button names were different than +the default <CODE>lircrc.example</CODE> file that came with MythTV.</P> +<P>The <CODE>lircrc.example</CODE> file has this: +<BLOCKQUOTE><CODE> +<PRE> +begin + prog = irxevent + button = ChannelUp + config = Key Up CurrentWindow +end + +begin + prog = irxevent + button = ChannelDown + config = Key Down CurrentWindow +end +</PRE> +</CODE></BLOCKQUOTE> + +but the <CODE>/etc/lircd.conf</CODE> that comes in the lircd package +defines the buttons for the Pinnacle Studio PCTV as: +<BLOCKQUOTE><CODE> +<PRE> + channel+ 0x0000000000000017 + channel- 0x000000000000001C +</PRE> +</CODE></BLOCKQUOTE> + +rather than "ChannelUp" and "ChannelDown". I added the +following to my /home/[yourusername]/.lircrc file: +<BLOCKQUOTE><CODE> +<PRE> +begin + prog = irxevent + button = channel+ + repeat = 3 + config = Key Up CurrentWindow +end + +begin + prog = irxevent + button = channel- + repeat = 3 + config = Key Down CurrentWindow +end +</PRE> +</CODE></BLOCKQUOTE> + +which took care of basic functionality. Because the PCTV Studio remote +has additional buttons, look at the +<CODE>contrib/configfiles/lircrc.example.pinnaclestudiopctv</CODE> for an example of how +to define additional buttons, and how to debug potential button name +conflicts between the <CODE>lircrc.example</CODE> file and how <B>your</B> +remote defines the button names.</P> +<P>By examining the button names defined in <CODE>/etc/lircd.conf</CODE> and using +the <B>irw</B> program to make sure that your remote is working, you can +create the appropriate mappings in <CODE>.lircrc</CODE> to get excellent remote +functionality with MythTV.</P> +<P>Note the <B>repeat =</B> parameter. This informs the <CODE>irxevent</CODE> +program to pass through every third keypress. By default, <CODE>lirc</CODE> +will only send one keypress to the application, even if you're holding down +the key. The actual <B>repeat =</B> number will vary from system to +system, so experiment and see which value works best for you.</P> + +<H2><A NAME="ss8.5">8.5</A> <A HREF="mythtv-HOWTO.html#toc8.5">Configuring lirc for use with an IR blaster</A> +</H2> + +<P>Lirc has support for various IR transmitters. A popular model is the Actisys +IR-200L +<A HREF="http://store.snapstreamstore.com/accessories.html">http://store.snapstreamstore.com/accessories.html</A>. It was +originally designed for IRDA communication, but can be used to transmit A/V remote +control codes. By using the lirc SIR driver, this device can easily be +integrated with MythTV. I have tested this device with an AT&T DCT2000 +digital cable box but the instructions can be used to configure other IRDA +devices and A/V remotes.</P> +<P>Follow the steps in the previous section. When you run setup.sh, select +option 1, driver configuration. From here select option 6, IrDA hardware. +Select your appropriate device and the corresponding serial port, then Save +configuration & run configure from the main menu. Once configure is done +type: +<BLOCKQUOTE><CODE> +<PRE> +$ make +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Please note: unlike the Pinnacle receiver above you will be compiling lircd +in addition to a kernel module for the SIR transmitter. Depending on whether +you have your serial port driver configured as a kernel module you might see +the following message during make: +<BLOCKQUOTE><CODE> +<PRE> +lirc_sir.c:56:2: warning: #warning +"******************************************" + +lirc_sir.c:57:2: warning: #warning "Your serial port driver is compiled into " + +lirc_sir.c:58:2: warning: #warning "the kernel. You will have to release the " + +lirc_sir.c:59:2: warning: #warning "port you want to use for LIRC with:" + +lirc_sir.c:60:2: warning: #warning "setserial /dev/ttySx uart none" + +lirc_sir.c:61:2: warning: #warning +"******************************************" +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you do receive this statement make sure to run the <B>setserial</B> command +before you load the lirc_sir module. Follow this with the install: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# make install +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>You will notice that lirc installs the kernel module in +<CODE>/lib/modules/uname -a/misc</CODE>. </P> +<P>The configuration for starting <B>lircd</B> differs if you're going to be +sending and receiving IR versus just receiving. +<BLOCKQUOTE><CODE> +<PRE> + +# cd /etc/rc.d +# cat >> rc.local +echo "Starting lircd" +setserial /dev/ttySx uart none # (if required) +modprobe lirc_sir +/usr/local/sbin/lircd +^D +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>At this point you have to populate the <CODE>/etc/lircd.conf</CODE> file with the proper +codes for your A/V remote. You should be able to find your remote within the +lirc remote tar file located at +<A HREF="http://www.lirc.org/remotes.tar.bz2">http://www.lirc.org/remotes.tar.bz2</A>. In my case I +extracted the file from remotes/motorola/DCT2000 (gi-motorola-dct2000)</P> +<P>To test the lirc_sir module you can run <B>irw</B> to verify the codes are being +received. If everything is configured correctly +you should see something similar to the following: +<BLOCKQUOTE><CODE> +<PRE> +$ irw +0000000000007ff0 00 1 gi-motorola-dct2000 +000000000000bff8 00 2 gi-motorola-dct2000 +000000000000f7f0 00 ENTER gi-motorola-dct2000 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Once you've verified lirc is working you can press <B>CTRL-C</B> to exit +<B>irw</B> and configure the channel changing script.</P> +<P>The path to the channel changing script will need to be entered on the +mythtv-setup screen for Input Connections.</P> +<P>This csh script will be called each time MythTV needs to change the channel. +Below is a copy of the script followed by the corresponding perl script. +Make sure both are in your path. Also make sure you leave the #!/bin/csh +setting and not change it to Bourne or bash. This will create a frustrating +symptom to diagnose where MythTV cannot open /dev/device. Unlike Bourne or +bash, csh scripts automatically close parent file descriptors before they +start. +<BLOCKQUOTE><CODE> +<PRE> +$ cd /usr/local/bin +# su +# cat > change_channel.csh +#!/bin/csh +echo "changing to $1" +/usr/local/bin/channel.pl $1 & +^D +# chmod a+x change_channel.csh +# exit +$ exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>See <CODE>contrib/channel.pl</CODE> for the actual file. Copy it to +<CODE>/usr/local/bin/</CODE></P> +<P>The last statement within the perl script is the lirc rc command. This is +the command that transmits the code to your cable/DSS box. Make sure to have +the IRDA device within a few feet of the box.</P> + +<HR> +<A HREF="mythtv-HOWTO-9.html">Next</A> +<A HREF="mythtv-HOWTO-7.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc8">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-9.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-9.html new file mode 100644 index 0000000..4fc01d5 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-9.html @@ -0,0 +1,649 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV: Configuring MythTV. </TITLE> + <LINK HREF="mythtv-HOWTO-10.html" REL=next> + <LINK HREF="mythtv-HOWTO-8.html" REL=previous> + <LINK HREF="mythtv-HOWTO.html#toc9" REL=contents> +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-10.html">Next</A> +<A HREF="mythtv-HOWTO-8.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc9">Contents</A> +<HR> +<H2><A NAME="Configuring_mythtv"></A> <A NAME="s9">9.</A> <A HREF="mythtv-HOWTO.html#toc9">Configuring MythTV. </A></H2> + +<P>By this point, all of the compile-time prerequisites have been installed, +<B>mysql</B> is running and has had its initial database setup. It's now +time to configure MythTV. +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: If you're running Debian unstable and you have compiled +MythTV from source, you will need to install an additional package before +you will be able to run MythTV. Execute the following to install the MySQL +driver for QT.</CAPTION> +</FIGURE> + +<BLOCKQUOTE><CODE> +<PRE> +$ su - +# apt-get install libqt3c102-mt-mysql +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H2><A NAME="ss9.1">9.1</A> <A HREF="mythtv-HOWTO.html#toc9.1">Configuring the Master backend system</A> +</H2> + +<P>Open a shell and decide where you will store your video files. This may +be one directory or multiple directories on the same or different +filesystems. There is no default directory used for new recordings, you +<B>must</B> create at least one storage directory and configure Myth to +use it by running <B>mythtv-setup</B>. If you do not do this, then MythTV +will be unable to record anything. The following example is specific for +<CODE>/var/video</CODE>, but the same instructions would apply for any directory +name you choose to use. See the +<A HREF="mythtv-HOWTO-24.html#advancedpartitionformatting">Advanced Partition Formatting</A> section for hints on creating a +partition for MythTV.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ su +# mkdir /var/video +# chmod a+rwx /var/video +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><B>NOTE</B>: The last slash "/" is not required.</P> +<P> +<A NAME="storagegrouptip"></A> +<B>TIP</B>: Try not to have your video mount point on the same partition +as your root partition, which could lead to the filling up of your root +partition with video data if the mount fails. For example:</P> +<P>If <CODE>/var/video</CODE> is created on your root partition and you then +perform a mount of another drive to this directory there won't be any +problems if everything is working the way it should. However, if the mount +fails for some reason, <CODE>/var/video</CODE> still exists, so MythTV will find +the directory and write files to it. If your <CODE>/</CODE> mount point is +space limited, <CODE>/var/video</CODE> will <B>also</B> be space limited, and +it won't take long to fill the partition. This will cause a number of +side-effects, most of them bad. Instead, create subdirectories as the +destination for the storage group.</P> +<P>Your directory structure could then look something like this: +<BLOCKQUOTE><CODE> +<PRE> +/mnt/video/drive1/video +/mnt/video/drive2/video +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Your <CODE>/etc/fstab</CODE> would look like this: +<BLOCKQUOTE><CODE> +<PRE> +/dev/hdb1 /mnt/video/drive1 +/dev/hdc1 /mnt/video/drive2 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Because the Storage Group path is <CODE>/mnt/video/drive1/video</CODE>, if the +mythbackend can only find <CODE>/mnt/video/drive1</CODE> it will <EM>not</EM> +write files to that share.</P> +<P>After you create the desired directory or directories for storing your video +files, you will need to add them to the proper Storage Group using +<B>mythtv-setup</B>. This procedure is described below in the +<A HREF="#storagegroups">Storage Groups</A> section.</P> +<P>The first thing to configure is the Master backend system. If you are +running multiple backend systems, the Master backend will make all +decisions about which programs will be recorded on which tuners. If you +have only one backend, then it will be its own master.</P> +<P>The Master backend will always choose the first available tuner in the same +order as you add cards through "mythtv-setup". In other words, the second +card you add will only be used when there are two overlapping recordings, +the third when there are three, and so on. + Therefore, you will want to have +the greatest amount of disk space on the Master backend because its tuner +will always be the first choice. You will then want to add your +<A HREF="#nonmaster_backend">other backends</A> in the order of your +preference for recording.</P> +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: It is possible to <EM>not</EM> have the cards on the Master +backend be the first ones used. However, if you are new to MythTV it is +easier to configure the Master backend first before moving on to the Slaves, +at least until you become more familiar with the MythTV system. See +<A HREF="mythtv-HOWTO-23.html#advanced_backend_config">Advanced Backend Configurations</A> for +information on configuring multiple backend systems in various ways.</CAPTION> +</FIGURE> +</P> +<P>Because MythTV uses a database to store all configuration variables, +part of the bootstrap of MythTV is to indicate the location of the MySQL +database server. If the frontend, backend and MySQL database server are all +going to be running on the same box, you can continue to the next step. If +not, you'll need to change the Host Name in the "Database Configuration" +screen of the mythfrontend program.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Users that have been running the frontend and the backend on +different machines have stated that they have been having issues with remote +access to the MySQL database. The following instructions may or may not +work. Add the following to <CODE>/etc/my.cnf</CODE> on the backend machine and +restart MySQL.</CAPTION> +</FIGURE> + +<BLOCKQUOTE><CODE> +<PRE> +skip-innodb +set-variable=thread_stack=256k +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Run the setup program: +<BLOCKQUOTE><CODE> +<PRE> +$ mythtv-setup +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The backend setup program will start and offer you a number of choices. It +is <EM>strongly</EM> recommended that you go through them in order.</P> +<P>The first question will ask if you wish to clear out your existing +configurations for your capture cards. Initially, you should say "YES" so +that there are no surprises later.</P> +<P>The next question will ask you if you wish to clear out your video source +information. You should answer "YES" to this as well.</P> +<P>Once the graphical setup starts, you'll see that there are six choices</P> +<P> +<FIGURE> +<EPS FILE="add.eps"> +<IMG SRC="add.png"> +<CAPTION>The Storage Directories feature is available only in the SVN version of MythTV.</CAPTION> +</FIGURE> +</P> +<P> +<OL> +<LI>General</LI> +<LI>Capture Cards</LI> +<LI>Video Sources</LI> +<LI>Input connections</LI> +<LI>Channel Editor</LI> +<LI>Storage Directories</LI> +</OL> +</P> +<P>Use the arrow keys to move around, and press the space bar to select which +option you wish to configure.</P> + +<H3>General</H3> + +<P>The first screen of the General configuration deals with IP addresses of the +system that you're running mythtv-setup on and any master backend you may have. +If you've only got one machine, then the default values are fine and you can +move to the next page by pressing the space bar. If you need to move around +the screen, use the arrow keys to move focus between settings, not the +mouse.</P> +<P>If you will be deploying multiple backends, or if your backend is on one +system and you're running the frontend on another machine then <EM>do +not</EM> use the "127.0.0.1" IP address.</P> +<P><B>NOTE</B>: 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.</P> +<P>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)</P> +<P>Once you're satisfied with the values, move the focus down to Next and hit +the space bar.</P> +<P>The next screen details the Host-specific Backend setup. This is where you +will set the specific directory paths for this particular backend. Make +sure that you've followed the steps at the beginning of this section and +created a directory that exists and that MythTV will have write privileges +to. When you're done, press Next to continue, taking you to the Global +Backend Setup.</P> +<P>On the Global Backend Setup configure your backend with the appropriate +settings. Use the left and right arrow keys to iterate through the choices +available on each setting, and the up and down keys to move between +settings. Move to Finish when you're done and press the space bar, taking +you back to the main configuration screen.</P> + +<H3>Capture Cards</H3> + +<P>You should have no capture cards defined, so the highlight will be on +(New Capture Card). Press space to begin.</P> +<P>Choose the appropriate settings for your particular tuner. Use the arrow +keys to move around and to make your choices, and press RETURN when +complete. Pressing RETURN will take you back to the Capture Cards screen; +if you have additional capture cards in this machine, press the space bar +when the highlight is on the (New Capture Card) row to define another card. </P> +<P>If you have made a mistake, you can delete a card by highlighting it and +pressing the 'D' key, or you can highlight it and press the RETURN or 'E' +key to edit it.</P> +<P>Once you have no additional cards to setup, press ESC.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: If you have a dual digital/analog card, such as the pcHDTV +cards and some DViCO cards, then you should not configure this as two +separate cards. Configure the digital portion as a DVB card, then click +on the "Analog Options" button within the DVB configuration panel for +the card and configure the analog portion of the card there.</CAPTION> +</FIGURE> +</P> + +<H3><A NAME="VideoSources"></A> Video Sources </H3> + +<P>When you start, the highlight should be on (New Video Source). Press the +space bar to begin. The first field asks for the name of the video source. +You may choose something easy to remember, like "Antenna" or "Cable". Once +you've chosen a name, press the down arrow to move to the next field. </P> +<P>If you're in North America, change the grabber to +"SchedulesDirect.org(Internal)", then continue pressing the down arrow to +move to the next field. Fill in the username (lowercase only) and password +that you have established with Schedules Direct, then move to the "Retrieve +Listings" button and press the space bar.</P> +<P><B>NOTE</B>: You need <B>wget</B> version 1.9.1 or higher to use +Schedules Direct.</P> +<P>The mythtv-setup program will contact the Schedules Direct servers and get +your account information. Once you're done, you may click the Finish button +and skip the next few paragraphs in this document since they only apply to +users that are using the external XMLTV script to get their guide data.</P> +<P>If you wish to continue using the XMLTV grabber, then move to the Zip/postal +code field and put in the appropriate value.</P> +<P>If you're outside of North America, then some manual interaction will be +required with XMLTV. You may need to switch from the MythTV setup program +to the console it was run on to interact with XMLTV.</P> +<P>Once you have chosen your provider, press RETURN to continue. XMLTV will +now begin collecting the initial data for your location. The screen may +blank for a few seconds to several minutes, depending on the load of the +listings provider and the speed of your connection to the Internet. Be +patient!</P> +<P>You will then be returned to the Video Sources screen. If you have multiple +video sources available, such as Antenna, Cable, etc, go ahead and define +them all, even if they're not all going to be physically connected to the +master backend server. Once you're done, press ESC to return to the main +screen.</P> + +<H3>Input Connections</H3> + +<P>The final configuration item is Input Connections. On this screen, you +will associate the various video sources you defined earlier with a physical +input to a encoder card. It's entirely possible that you have multiple +tuners, and each tuner has a different input, so on this screen you let +MythTV know which device will connect to which input source.</P> +<P>When you start this screen, you should see a listing of the various input +connections available on each of the Capture cards you defined earlier. For +example, you may have a capture card with a tuner, a SVideo and a Composite +connection. If you wanted to associate the tuner (a.k.a., "Television") +with an "Antenna" source you defined in Video Sources, you would move to the +<CODE>/dev/videodevice (Television) -> </CODE> line and press the space bar. +Using the left and right arrow keys will show you the various choices you +have already created for video source. In our case, you would use the +left/right cursor keys until "Antenna" was shown in the Video Source field. +Press down to move to the next setting.</P> +<P>On the connection pane there is a "Scan for channels" button, if you are +configuring a digital source such as a DVB card, you need scan for channels +and you must do this before pressing the "Fetch channels from listings +source" button. You may scan for analog channels on an analog input, but +this is not needed.</P> + +<P>The other button is called "Fetch channels from listings source". As long as +you have a real listings source you should fetch channels from them for +analog channels. You can do this for digital sources as well (unless the +listing source is transmitted EIT data). If you are using XMLTV, you may need +to switch from the MythTV setup program to the console it was run on to +interact with XMLTV after pressing this button. It is possible to fetch the +channels on the command line using mythfilldatabase. But if you need to do +this, you will probably need to re-enter the MythTV setup program to +configure the "Starting channel" setting for this source->input connection.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: If you have a Hauppauge PVR-500, you must think of +it has two PVR-150's on a single PCI card. For example, if you have a +single PVR-500 card, it will appear as <CODE>/dev/video0</CODE> and +<CODE>/dev/video1</CODE>. Each <CODE>/dev/video</CODE> device will have a Tuner input.</CAPTION> +</FIGURE> + +Once you're done, press RETURN to go back to the Input Connections screen. +You would then finish associating the video sources to any other hardware +devices you have available.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Don't add a video source to a hardware input if you don't +actually have anything connected there. For example, adding "Cable" to the +Tuner and to the Composite inputs without having something connected to +Composite will lead to blank recordings.</CAPTION> +</FIGURE> +</P> +<P>Press ESC to return to the main menu, and press ESC again if you have no +further items to configure, thereby returning you to the command line.</P> + +<H3>Channel Editor</H3> + +<P>The channel editor is used to globally alter channel information, +including items like hue, contrast, fine tuning and others. Users in North +America shouldn't run the channel editor until you've completed the initial +mythtv-setup and ran <B>mythfilldatabase</B> at least once to populate the +database.</P> + +<H3><A NAME="storagegroups"></A> Storage Groups </H3> + +<P> +<FIGURE> +<EPS FILE="add.eps"> +<IMG SRC="add.png"> +<CAPTION>New in MythTV 0.21</CAPTION> +</FIGURE> +</P> +<H3>Introduction.</H3> + +<P>Storage Groups are lists of directories that are used to hold MythTV +recording files giving you a flexible way to allow you to add capacity to +your MythTV system without having to use exotic solutions such as LVM, +filesystem expansion or RAID Online Capacity Expansion. You can also use +Storage Groups to organize recordings and to put recordings of a certain +type into one subdirectory.</P> +<P>Storage Groups do not offer redundancy in case of hard drive failure, but +unlike LVM, if you lose a hard drive, you only lose the recordings that were +on that drive. With LVM, if you lose a hard drive, you will most likely +lose <B>everything</B>.</P> + +<H3>How to use Storage Groups.</H3> + +<P>By default, there is only one Storage Group called "Default", and it is +used for all recordings and Live TV.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: You need to add at least one directory to the Default +Storage Group or else you will not be able to record anything with MythTV.</CAPTION> +</FIGURE> +</P> +<P>For example, if you have 5 hard drives in your system, your first hard drive +could be your "boot" drive, and the remaining four could be dedicated to +media storage. You could format the drives and mount them as +<CODE>/mnt/store/d2</CODE>, <CODE>/mnt/store/d3</CODE>, <CODE>/mnt/store/d4</CODE> and +<CODE>/mnt/store/d5</CODE>.</P> +<P>Within each mount point, it's <EM>strongly</EM> recommended that you use a +sub-directory and make that the destination path for the Storage Group. See +the +<A HREF="#storagegrouptip">Tip</A> in the "Configuring the Master +backend" section for additional information.</P> +<P>You would then add the four subdirectories you created under the mount +points (<CODE>/mnt/store/d1/video</CODE>, etc) into the "Default" Storage Group.</P> +<P>At recording time, if there were four simultaneous recordings, MythTV would +put one recording onto each drive.</P> +<P>Or, say that you originally installed MythTV to a 80GB hard drive, and that +hard drive is now filling up. You could simply add a new drive to your +system, mount it and update the Storage Group to add additional space.</P> +<P>You may create additional Storage Groups to store specific recordings in +their own directories. Storage Groups are edited via the 'Storage +Directories' section of mythtv-setup. </P> +<P>You can also create multiple Storage Groups to group recordings together; +recording schedules now have an option to specify which Storage Group to +use.</P> +<P>MythTV will balance concurrent recordings across the available directories +in a Storage Group in order to spread out the file I/O load. MythTV will +prefer filesystems that are local to the backend over filesystems that are +remote until the local filesystem has 2 concurrent recordings active or +other equivalent I/O, then the next recording will go to the remote +filesystem. The balancing method is based purely on I/O, Myth does not try +to balance out disk space unless a filesystem is too low on free disk space +in which case it will not be used except as a last resort.</P> +<P>Storage Groups are global, but can be overridden on a slave backend by +creating a local Storage Group by running <B>mythtv-setup</B> on the +slave. If a problem occurs and the slave backend is unable to use the +desired Storage Group, it will fail back and try the directories defined in +the master's Storage Group.</P> +<P>There's also a special 'LiveTV' Storage Group, but the directory list starts +out empty. If you add a directory to the Storage Group, it will be used +instead of putting LiveTV recordings in the Default Storage Group. This +will allow you to put your LiveTV recordings on their own filesystem, which +is similar to the old MythTV method which used a RingBuffer for LiveTV. Of +course, you don't have to do anything, and Live TV recordings will just go +into the Default Storage Group where they'll be the first programs eligible +for expiration if the system needs free space for recordings.</P> +<P>Usage information for all Storage Group directories is visible on the +mythfrontend status screen as well as the mythbackend status webpage. +MythTV is smart enough to determine which directories are on shared +filesystems so it should not count free or used space multiple times if you +have more than one directory on the same filesystem.</P> + +<H3>Migrating to Storage Groups.</H3> + +<P>Migrating to Storage groups is very simple: if you have existing +recordings in a storage directory, then the system will automatically add +that directory to the Default Storage Group. If you then add additional +directories to a storage group, the system is flexible enough to check +<EM>all</EM> Storage Groups for a file before deciding that it can't be +found, which means that you can use the <B>mv</B> command from the Unix +command line to arrange files however you'd like.</P> + +<H3>Advanced: Algorithm used by the Storage Group</H3> + +<P>This section details the logic of the Storage Group allocation engine.</P> +<P>The current load-balancing preferences (in order) are: +<UL> +<LI>Local filesystems over remote</LI> +<LI>Less-busy (less weight) over more-busy (more weight)</LI> +<LI>More Free Space over Less Free Space</LI> +</UL> +</P> +<P>The 'business' of a filesystem is determined by weights. The following +weights are added to a filesystem if it is in use for the following things: +<UL> +<LI>recording = +10</LI> +<LI>playback = +5 (mythfrontend)</LI> +<LI>comm flagging = +5 (mythcommflag)</LI> +<LI>transcoding = +5 (mythtranscode)</LI> +</UL> +</P> +<P>If a recording is due to end within 3 minutes, it is not counted against +the weight of a filesystem. This is done to account for the pre/post-roll +and start-early/end-late settings. </P> + +<H2><A NAME="ss9.2">9.2</A> <A HREF="mythtv-HOWTO.html#toc9.2">Post-configuration</A> +</H2> + +<P>Run the <CODE>mythfilldatabase</CODE> program as directed. The master +backend will obtain guide data for all the video sources you defined during +setup.</P> +<P><B>NOTE</B>: If you are using Schedules Direct and watching the output messages +on the console or the log file it is normal to see a "401 Unauthorized" +error followed by a "200 OK" when the connection to Schedules Direct is being +established. +<BLOCKQUOTE><CODE> +<PRE> +From : Sun Jun 13 05:00:00 2004 To : Mon Jun 14 05:00:00 2004 (UTC) +--02:58:01-- +http://datadirect.webservices.zap2it.com/tvlistings/xtvdService + => -' +Resolving datadirect.webservices.zap2it.com... 206.18.98.160 +Connecting to datadirect.webservices.zap2it.com[206.18.98.160]:80... +connected. +HTTP request sent, awaiting response... 401 Unauthorized +Connecting to datadirect.webservices.zap2it.com[206.18.98.160]:80... +connected. +HTTP request sent, awaiting response... 200 OK +Length: unspecified [text/xml] + + [ <=> ] 114,125 63.57K/s + +02:58:03 (63.53 KB/s) - -' saved [114125] + +Your subscription expires on 08/20/2004 12:00:00 AM +Grab complete. Actual data from Sun Jun 13 05:00:00 2004 to Mon Jun 14 +00:00:00 2004 (UTC) +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Once <CODE>mythfilldatabase</CODE> has finished, start the master server before +continuing. +<BLOCKQUOTE><CODE> +<PRE> +$ mythbackend +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>mythbackend will print information about connections and what it's doing to +the console. If you'd like to see the options that are available for +mythbackend, type <CODE>mythbackend -h</CODE> for help.</P> +<P>As of MythTV v0.21, the available options are: +<BLOCKQUOTE><CODE> +<PRE> +$ mythbackend --help +Valid options are: +-h or --help List valid command line parameters +-l or --logfile filename Writes STDERR and STDOUT messages to filename +-p or --pidfile filename Write PID of mythbackend to filename +-d or --daemon Runs mythbackend as a daemon +-v or --verbose debug-level Use '-v help' for level info +--printexpire List of auto-expire programs +--printsched Upcoming scheduled programs +--testsched Test run scheduler (ignore existing schedule) +--resched Force the scheduler to update +--nosched Do not perform any scheduling +--nojobqueue Do not start the JobQueue +--noautoexpire Do not start the AutoExpire thread +--version Version information +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Running mythbackend as a daemon and using the logfile option will allow you +to have mythbackend automatically start up during boot. You can follow the +steps outlined in the section called +<A HREF="mythtv-HOWTO-23.html#mythbackend_autostart">Automatically starting mythbackend at system boot time</A> for +configuration steps.</P> +<P>If you enable the <CODE>-l</CODE> parameter, you will want to keep your logfiles +rotated (so that they don't fill up a partition). See the section called +<A HREF="mythtv-HOWTO-23.html#logrotate">Automatically rotating logs</A> for more +information.</P> + +<H2><A NAME="nonmaster_backend"></A> <A NAME="ss9.3">9.3</A> <A HREF="mythtv-HOWTO.html#toc9.3">Configuring a non-master backend </A> +</H2> + +<P>Ensure that you've granted access to the master MySQL database for remote +backends as discussed in the section titled +<A HREF="mythtv-HOWTO-6.html#modify_perm_mysql">Modifying access to the MySQL database for multiple systems</A> and that +you have the correct IP address for the database server in the "Database +Configuration" screen of the mythtv-setup application on this slave backend.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Slave backends <B>must not</B> run a local MySQL +daemon. By default, they will connect to their local daemon rather than the +central database, causing unexpected behavior such as empty "Watch +Recordings" lists and a failure to locate the Video Sources defined on the +master backend. Modify the <CODE>/usr/local/share/mythtv/mysql.txt</CODE> file +on all slave backends to ensure that the <CODE>DBHostName</CODE> has the address +of the MySQL server. +Caveat: You may make a slave backend the primary MySQL server, or run a +non-MythTV database on a slave backend as long as you have edited the +<CODE>mysql.txt</CODE> file on <B>all</B> systems and made it consistent. There can be only one authoritative MySQL database in a MythTV system - +errors such as the one above ensue if backends and frontends have differing +ideas of which MySQL database they should talk to.</CAPTION> +</FIGURE> +</P> +<P>Make sure that the IP addresses on the General setup screen are accurate. +If the slave backend can't communicate with the master backend due to IP +address misconfiguration then MythTV will not function properly.</P> +<P>Configuration of a non-master backend follows the same general procedure +as that of the master backend, with the exception that you skip over the +"Video Sources" step. All possible video sources need to be defined on the +master backend system; only the master backend will query a listings +provider to obtain guide data for all the non-master backends.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Do not run <CODE>mythfilldatabase</CODE> on a non-master backend.</CAPTION> +</FIGURE> +</P> +<H2><A NAME="ss9.4">9.4</A> <A HREF="mythtv-HOWTO.html#toc9.4">Configuring and running mythfilldatabase</A> +</H2> + +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: <B>mythfilldatabase</B> might take a while to complete, +depending on any number of factors, most of which you can't control. It's +best to just let the program run to completion.</CAPTION> +</FIGURE> + +<B>mythfilldatabase --help</B> will give a full listing of the options +available. </P> +<P><B>mythfilldatabase --manual</B> is another option; the manual option will +allow you to fine tune channel frequencies and specify which channels will +be added to the database. </P> +<P><B>mythfilldatabase --file</B> is an option if there isn't an XMLTV grabber +for your country, but you <B>do</B> have an XML formatted listings file +created by some other program.</P> +<P><B>mythfilldatabase --xawchannels</B> is an option if you have used +<B>xawtv</B> to fine-tune your channels and would like to import the fine +tuning offsets into MythTV.</P> +<P><B>mythfilldatabase --refresh-today</B> will only pull guide data for +today (in case of late-breaking changes to the schedule).</P> + + +<H3>Periodically running <B>mythfilldatabase</B></H3> + +<P>In order to keep your database filled, <B>mythfilldatabase</B> should be +run once a day.</P> +<P>To use MythTV's built-in capability, you'll need to run the +<B>mythfrontend</B> Setup option. From the mythfrontend, enter the +Setup>General screen and advance to "Mythfilldatabase", the fourth screen. +Select the checkbox, then complete the options as you see fit. The +<B>mythbackend</B> program will now run <B>mythfilldatabase</B> for you.</P> + +<H2><A NAME="ss9.5">9.5</A> <A HREF="mythtv-HOWTO.html#toc9.5">Grabbing channel icons for Schedules Direct users</A> +</H2> + +<P>While the Schedules Direct TV listings service has several advantages, it +does not support grabbing logo icons for the stations you receive. However, +there are utilities provided with MythTV which you may use to grab your +initial set of icons and to keep them updated if your lineups change.</P> +<P>First, you need to generate or obtain an XML file with the information for +your stations.</P> +<P>If you have XMLTV software installed, there is a perl script in MythTV's +<CODE>contrib/</CODE> directory which will generate this file for you. Run the +command: +<BLOCKQUOTE><CODE> +<PRE> +$ perl mkiconmap.pl +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>You will be asked for your zip code and the service that you use. If there +are no errors, the <CODE>iconmap.xml</CODE> file that you need for the next step +will be created.</P> +<P>If you do not have XMLTV software installed and do not want to install it +for the sake of this minor task, there is a generic +<CODE>contrib/master_iconmap.xml</CODE> which you can copy and use but this may +not be as complete as using the specific information for your service.</P> +<P>Once you have an <CODE>iconmap.xml</CODE> file, add the icon information to your +database and grab any new icons with the command: +<BLOCKQUOTE><CODE> +<PRE> +$ mythfilldatabase --import-icon-map iconmap.xml --update-icon-map +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<HR> +<A HREF="mythtv-HOWTO-10.html">Next</A> +<A HREF="mythtv-HOWTO-8.html">Previous</A> +<A HREF="mythtv-HOWTO.html#toc9">Contents</A> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-singlehtml.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-singlehtml.html new file mode 100644 index 0000000..b5b82a2 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO-singlehtml.html @@ -0,0 +1,8532 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV</TITLE> +</HEAD> +<BODY> +<H1>Installing and using MythTV</H1> + +<H2>Robert Kulagowski, +<A HREF="mailto:rkulagow@rocketmail.com">mailto:rkulagow@rocketmail.com</A></H2>2008-06-04, v0.21.02 +<HR> +<EM>Initially, installation of MythTV seems like a huge task. There are lots +of dependencies, and various distributions seem to do the same thing +different ways. This document will attempt to give general installation +instructions, as well as including distribution-specific instructions where +necessary.</EM> +<HR> +<P> +<H2><A NAME="toc1">1.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s1">First things first.</A></H2> + +<UL> +<LI><A NAME="toc1.1">1.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss1.1">What is MythTV?</A> +<LI><A NAME="toc1.2">1.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss1.2">QuickStart</A> +<LI><A NAME="toc1.3">1.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss1.3">Upgrading from previous versions</A> +<LI><A NAME="toc1.4">1.4</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss1.4">How to obtain this document / PDF versions of this document </A> +<LI><A NAME="toc1.5">1.5</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss1.5">Books about MythTV</A> +<LI><A NAME="toc1.6">1.6</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss1.6">Document conventions</A> +<LI><A NAME="toc1.7">1.7</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss1.7">Mailing lists / getting help</A> +<LI><A NAME="toc1.8">1.8</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss1.8">IRC</A> +<LI><A NAME="toc1.9">1.9</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss1.9">Bug database</A> +<LI><A NAME="toc1.10">1.10</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss1.10">Contributing to this document</A> +</UL> +<P> +<H2><A NAME="toc2">2.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s2">Introduction.</A></H2> + +<P> +<H2><A NAME="toc3">3.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s3">Checking prerequisites. </A></H2> + +<UL> +<LI><A NAME="toc3.1">3.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss3.1">Hardware</A> +<LI><A NAME="toc3.2">3.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss3.2">Software</A> +</UL> +<P> +<H2><A NAME="toc4">4.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s4">System Configuration Requirements for Compiling MythTV. </A></H2> + +<UL> +<LI><A NAME="toc4.1">4.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss4.1">Software requirements for compiling MythTV</A> +<LI><A NAME="toc4.2">4.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss4.2">Shared-Library requirements for MythTV </A> +<LI><A NAME="toc4.3">4.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss4.3">Environment variable requirements for MythTV</A> +</UL> +<P> +<H2><A NAME="toc5">5.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s5">Downloading and compiling. </A></H2> + +<UL> +<LI><A NAME="toc5.1">5.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss5.1">Building LAME</A> +<LI><A NAME="toc5.2">5.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss5.2">XMLTV</A> +<LI><A NAME="toc5.3">5.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss5.3">Configuring the Schedules Direct service </A> +<LI><A NAME="toc5.4">5.4</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss5.4">Manually building MythTV</A> +<LI><A NAME="toc5.5">5.5</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss5.5">Gentoo </A> +</UL> +<P> +<H2><A NAME="toc6">6.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s6">MySQL.</A></H2> + +<UL> +<LI><A NAME="toc6.1">6.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss6.1">Distribution-specific information</A> +<LI><A NAME="toc6.2">6.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss6.2">Setting up the initial database</A> +</UL> +<P> +<H2><A NAME="toc7">7.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s7">Configuring Sound.</A></H2> + +<UL> +<LI><A NAME="toc7.1">7.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss7.1">Graphically setting up the mixer</A> +<LI><A NAME="toc7.2">7.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss7.2">Setting the mixer from the command line</A> +</UL> +<P> +<H2><A NAME="toc8">8.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s8">Setting up a remote control.</A></H2> + +<UL> +<LI><A NAME="toc8.1">8.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss8.1">Gentoo</A> +<LI><A NAME="toc8.2">8.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss8.2">Obtaining and compiling lirc</A> +<LI><A NAME="toc8.3">8.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss8.3">Completing the lirc install </A> +<LI><A NAME="toc8.4">8.4</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss8.4">Additional information for lirc</A> +<LI><A NAME="toc8.5">8.5</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss8.5">Configuring lirc for use with an IR blaster</A> +</UL> +<P> +<H2><A NAME="toc9">9.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s9">Configuring MythTV. </A></H2> + +<UL> +<LI><A NAME="toc9.1">9.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss9.1">Configuring the Master backend system</A> +<LI><A NAME="toc9.2">9.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss9.2">Post-configuration</A> +<LI><A NAME="toc9.3">9.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss9.3">Configuring a non-master backend </A> +<LI><A NAME="toc9.4">9.4</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss9.4">Configuring and running mythfilldatabase</A> +<LI><A NAME="toc9.5">9.5</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss9.5">Grabbing channel icons for Schedules Direct users</A> +</UL> +<P> +<H2><A NAME="toc10">10.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s10">Configuring mythfrontend.</A></H2> + +<UL> +<LI><A NAME="toc10.1">10.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss10.1">General</A> +<LI><A NAME="toc10.2">10.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss10.2">Appearance</A> +<LI><A NAME="toc10.3">10.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss10.3">Program Guide</A> +<LI><A NAME="toc10.4">10.4</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss10.4">Playback </A> +<LI><A NAME="toc10.5">10.5</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss10.5">Recording </A> +<LI><A NAME="toc10.6">10.6</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss10.6">Xbox Frontends</A> +</UL> +<P> +<H2><A NAME="toc11">11.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s11">Using MythTV.</A></H2> + +<UL> +<LI><A NAME="toc11.1">11.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss11.1">Keyboard commands</A> +<LI><A NAME="toc11.2">11.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss11.2">Using themes with MythTV</A> +<LI><A NAME="toc11.3">11.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss11.3">Adding DishTV information to the database</A> +<LI><A NAME="toc11.4">11.4</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss11.4">Adding support for an external tuner</A> +<LI><A NAME="toc11.5">11.5</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss11.5">Using Shutdown/Wakeup</A> +<LI><A NAME="toc11.6">11.6</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss11.6">Controlling the mythfrontend via telnet</A> +</UL> +<P> +<H2><A NAME="toc12">12.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s12">Scheduling Recordings.</A></H2> + +<UL> +<LI><A NAME="toc12.1">12.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss12.1">Record Types</A> +<LI><A NAME="toc12.2">12.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss12.2">Scheduling Options</A> +<LI><A NAME="toc12.3">12.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss12.3">Storage Options</A> +<LI><A NAME="toc12.4">12.4</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss12.4">Post Recording Processing</A> +<LI><A NAME="toc12.5">12.5</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss12.5">Advanced Recording Options</A> +<LI><A NAME="toc12.6">12.6</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss12.6">Scheduling with more than one Input</A> +</UL> +<P> +<H2><A NAME="toc13">13.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s13">MythPlugins. </A></H2> + +<P> +<H2><A NAME="toc14">14.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s14">MythWeb.</A></H2> + +<UL> +<LI><A NAME="toc14.1">14.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss14.1">Installation and prerequisites</A> +<LI><A NAME="toc14.2">14.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss14.2">Completing the installation</A> +<LI><A NAME="toc14.3">14.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss14.3">Resetting the key binding table</A> +<LI><A NAME="toc14.4">14.4</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss14.4">Resetting the theme.</A> +</UL> +<P> +<H2><A NAME="toc15">15.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s15">MythGallery.</A></H2> + +<UL> +<LI><A NAME="toc15.1">15.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss15.1">Installation and prerequisites</A> +<LI><A NAME="toc15.2">15.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss15.2">Using MythGallery</A> +<LI><A NAME="toc15.3">15.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss15.3">Importing Pictures</A> +</UL> +<P> +<H2><A NAME="toc16">16.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s16">MythGame.</A></H2> + +<UL> +<LI><A NAME="toc16.1">16.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss16.1">Setup Directory Structure</A> +<LI><A NAME="toc16.2">16.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss16.2">Download and Install xmame</A> +<LI><A NAME="toc16.3">16.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss16.3">Download extra files</A> +<LI><A NAME="toc16.4">16.4</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss16.4">Download and Install MythGame.</A> +<LI><A NAME="toc16.5">16.5</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss16.5">Setup xmame in MythGame</A> +<LI><A NAME="toc16.6">16.6</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss16.6">Hints:</A> +</UL> +<P> +<H2><A NAME="toc17">17.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s17">MythMusic. </A></H2> + +<UL> +<LI><A NAME="toc17.1">17.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss17.1">Manual installation of prerequisites</A> +<LI><A NAME="toc17.2">17.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss17.2">Mandriva</A> +<LI><A NAME="toc17.3">17.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss17.3">Red Hat Linux 9</A> +<LI><A NAME="toc17.4">17.4</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss17.4">Compiling MythMusic</A> +<LI><A NAME="toc17.5">17.5</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss17.5">Configuring MythMusic</A> +<LI><A NAME="toc17.6">17.6</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss17.6">Using MythMusic</A> +<LI><A NAME="toc17.7">17.7</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss17.7">Troubleshooting MythMusic</A> +</UL> +<P> +<H2><A NAME="toc18">18.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s18">MythWeather.</A></H2> + +<P> +<H2><A NAME="toc19">19.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s19">MythVideo.</A></H2> + +<P> +<H2><A NAME="toc20">20.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s20">MythDVD.</A></H2> + +<UL> +<LI><A NAME="toc20.1">20.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss20.1">Manual Compilation of Prerequisites</A> +<LI><A NAME="toc20.2">20.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss20.2">Pre-compiled binaries</A> +<LI><A NAME="toc20.3">20.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss20.3">Running the Myth Transcoding Daemon</A> +</UL> +<P> +<H2><A NAME="toc21">21.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s21">MythNews.</A></H2> + +<P> +<H2><A NAME="toc22">22.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s22">Troubleshooting.</A></H2> + +<UL> +<LI><A NAME="toc22.1">22.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss22.1">Compiling</A> +<LI><A NAME="toc22.2">22.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss22.2">Debugging </A> +<LI><A NAME="toc22.3">22.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss22.3">Installing</A> +<LI><A NAME="toc22.4">22.4</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss22.4">Using</A> +<LI><A NAME="toc22.5">22.5</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss22.5">Miscellaneous</A> +</UL> +<P> +<H2><A NAME="toc23">23.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s23">Miscellaneous. </A></H2> + +<UL> +<LI><A NAME="toc23.1">23.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.1">I'd like to watch the files without using MythTV / I'd like to convert the files to some other format</A> +<LI><A NAME="toc23.2">23.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.2">Using a different window manager</A> +<LI><A NAME="toc23.3">23.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.3">What capture resolution should I use? How does video work? </A> +<LI><A NAME="toc23.4">23.4</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.4">MythTV GUI and X Display Sizes</A> +<LI><A NAME="toc23.5">23.5</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.5">Saving or restoring the database </A> +<LI><A NAME="toc23.6">23.6</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.6">Deleting the MySQL database</A> +<LI><A NAME="toc23.7">23.7</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.7">Moving your data to new hardware</A> +<LI><A NAME="toc23.8">23.8</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.8">btaudio </A> +<LI><A NAME="toc23.9">23.9</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.9">Removing unwanted channels</A> +<LI><A NAME="toc23.10">23.10</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.10">NFS</A> +<LI><A NAME="toc23.11">23.11</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.11">Automatically starting mythfrontend at system boot time</A> +<LI><A NAME="toc23.12">23.12</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.12">Automatically starting mythbackend at system boot time</A> +<LI><A NAME="toc23.13">23.13</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.13">Advanced Backend Configurations </A> +<LI><A NAME="toc23.14">23.14</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.14">Using the transcoder</A> +<LI><A NAME="toc23.15">23.15</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.15">Changing your hostname</A> +<LI><A NAME="toc23.16">23.16</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.16">Can I run MythTV on my TiVo?</A> +<LI><A NAME="toc23.17">23.17</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.17">Can I run MythTV on my ReplayTV?</A> +<LI><A NAME="toc23.18">23.18</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.18">Can a wireless connection be used between the frontend and the backend?</A> +<LI><A NAME="toc23.19">23.19</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.19">How can I burn shows that I have recorded to a DVD?</A> +<LI><A NAME="toc23.20">23.20</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.20">Using the DBoxII within MythTV</A> +<LI><A NAME="toc23.21">23.21</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.21">What do the icons on the Watch Recordings screen mean?</A> +<LI><A NAME="toc23.22">23.22</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.22">What do the letters mean when I change channels?</A> +<LI><A NAME="toc23.23">23.23</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.23">What is the difference between the various Hauppauge PVR models?</A> +<LI><A NAME="toc23.24">23.24</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.24">Changing channels on an external Set Top Box</A> +<LI><A NAME="toc23.25">23.25</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss23.25">Configuring one machine to flag all commercials</A> +</UL> +<P> +<H2><A NAME="toc24">24.</A> <A HREF="mythtv-HOWTO-singlehtml.html#s24">Example Configurations.</A></H2> + +<UL> +<LI><A NAME="toc24.1">24.1</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss24.1">Logical Volume Manager (LVM) </A> +<LI><A NAME="toc24.2">24.2</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss24.2">Advanced Partition Formatting </A> +<LI><A NAME="toc24.3">24.3</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss24.3">Migrating from DataDirect Labs to Schedules Direct</A> +<LI><A NAME="toc24.4">24.4</A> <A HREF="mythtv-HOWTO-singlehtml.html#ss24.4">Caching support for Schedules Direct</A> +</UL> + +<HR> +<H2><A NAME="s1">1.</A> <A HREF="#toc1">First things first.</A></H2> + +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Please note that I, Robert Kulagowski, am <EM>NOT</EM> the +author/programmer of the MythTV application! I can not give you +personalized installation support. If you are having issues installing +MythTV you should examine the archives, or post your question to the +MythTV-users mailing list. If you send me "Does MythTV work with 'X'"? +messages - I will simply instruct you to ask your question on the +mythtv-users mailing list.</CAPTION> +</FIGURE> +</P> +<H2><A NAME="ss1.1">1.1</A> <A HREF="#toc1.1">What is MythTV?</A> +</H2> + +<P>MythTV is a GPL licensed suite of programs that allow you to build the +mythical home media convergence box on your own using Open Source software +and operating systems. MythTV is known to work on Linux and Mac OS X +(PowerPC and Intel). It does not run on Windows.</P> +<P>MythTV has a number of capabilities. The television portion allows you to +do the following: +<UL> +<LI>You may pause, fast-forward and rewind live Television.</LI> +<LI>You may install multiple video capture cards to record more than one +program at a time.</LI> +<LI>You can have multiple servers (called "backends"), each with multiple +capture cards in them. All scheduling is performed by the Master backend, +which arbitrates which recording will be performed by each device. All +recording requests are managed by the Master backend, so you can schedule a +recording from any client.</LI> +<LI>You can have multiple clients (called "frontends" in MythTV parlance), +each with a common view of all available programs. Any client can watch any +program that was recorded by any of the servers, assuming that they have the +hardware capabilities to view the content; a low-powered frontend will not +be able to watch HDTV, for example. Clients can be diskless and controlled +entirely by a remote control.</LI> +<LI>You may use any combination of standard analog capture card, MPEG-2, +MJPEG, DVB, HDTV, USB and firewire capture devices. With appropriate +hardware, MythTV can control set top boxes, often found in digital cable and +satellite TV systems.</LI> +<LI>Program Guide Data in North America is downloaded from +schedulesdirect.org, a non-profit organization which has licensed data from +Tribune Media Services. This service provides almost two weeks of +scheduling information. Program Guide Data in other countries is obtained +using XMLTV. MythTV uses this information to create a schedule that +maximizes the number of programs that can be recorded if you don't have +enough tuners.</LI> +<LI>MythTV implements a UPNP server, so a UPNP client should automatically +see content from your MythTV system.</LI> +</UL> + +Other modules in MythTV include: +<UL> +<LI>MythArchive, a tool to create DVDs</LI> +<LI>MythBrowser, a web browser</LI> +<LI>MythControls, an application to configure your remote control</LI> +<LI>MythFlix, a Netflix module</LI> +<LI>MythGallery, a picture-viewing application</LI> +<LI>MythGame</LI> +<LI>MythMusic, a music playing / ripping application which supports MP3 +and FLAC</LI> +<LI>MythNews, a RSS news grabber</LI> +<LI>MythPhone, phone and videophone using SIP.</LI> +<LI>MythVideo, DVD ripper and a media-viewer for content not created within MythTV</LI> +<LI>MythWeather</LI> +<LI>MythWeb, which allows you to control your MythTV system using a web +browser. With MythWeb, you can schedule and delete recordings, change +keybindings and more. With proper security, you may even schedule a program +over the Internet and have it immediately acted on by the Master backend.</LI> +</UL> +</P> +<H2><A NAME="ss1.2">1.2</A> <A HREF="#toc1.2">QuickStart</A> +</H2> + +<P>Custom mini-distributions are available to make it easier to install +MythTV. A mini-distribution removes many of the "general purpose" +workstation / server software packages that may be installed by default if +you use one of the big-name OS packages.</P> +<P>See +<A HREF="http://mysettopbox.tv">http://mysettopbox.tv</A> if you'd +like to install a custom version of Knoppix optimized for MythTV.</P> +<P>See +<A HREF="http://www.minimyth.org">http://www.minimyth.org</A> if you'd like +to install MythTV onto a diskless system.</P> +<P>See +<A HREF="http://bit.blkbk.com">http://bit.blkbk.com</A> if you'd +like to install MythTV on a Xbox. +<B>NOTE</B>: Site appears unmaintained.</P> +<P>See +<A HREF="http://wilsonet.com/mythtv/">http://wilsonet.com/mythtv/</A> for instructions tailored to RedHat's +Fedora Core distribution.</P> +<P>See +<A HREF="http://www.mythbuntu.org">http://www.mythbuntu.org</A> if +you'd like to install a customized version of Ubuntu optimized for MythTV.</P> +<P>There is a MythTV wiki at +<A HREF="http://wiki.mythtv.org">http://wiki.mythtv.org</A>.</P> +<P>If you are installing this version for Schedules Direct support, please see +the +<A HREF="#migratingtoSD">Migrating from DataDirect Labs to Schedules Direct</A> section for additional information.</P> + +<H2><A NAME="ss1.3">1.3</A> <A HREF="#toc1.3">Upgrading from previous versions</A> +</H2> + +<P>The upgrade from previous versions should be transparent. Any changes to +the database structure should be applied automatically.</P> +<P>It is <EM>strongly</EM> recommended that you back up your database before +installing a new version of MythTV.</P> +<P>See +<A HREF="#backupdb">Saving or Restoring the database</A> for instructions.</P> + +<H2><A NAME="how_to_obtain"></A> <A NAME="ss1.4">1.4</A> <A HREF="#toc1.4">How to obtain this document / PDF versions of this document </A> +</H2> + +<P>This HOWTO document is maintained at the primary MythTV website: +<A HREF="http://www.mythtv.org">http://www.mythtv.org</A> by Robert +Kulagowski +<A HREF="mailto:rkulagow@rocketmail.com">mailto:rkulagow@rocketmail.com</A>.</P> +<P>This document is available as a single-page HTML document at +<A HREF="http://www.mythtv.org/docs/mythtv-HOWTO-singlehtml.html">http://www.mythtv.org/docs/mythtv-HOWTO-singlehtml.html</A> or as a PDF +at +<A HREF="http://www.mythtv.org/docs/mythtv-HOWTO.pdf">http://www.mythtv.org/docs/mythtv-HOWTO.pdf</A>.</P> +<P>This HOWTO is for MythTV v0.21</P> +<P>Release notes for this version may be found in the MythTV Wiki at +<A HREF="http://www.mythtv.org/wiki/index.php/Release_Notes_-_0.21">http://www.mythtv.org/wiki/index.php/Release_Notes_-_0.21</A></P> + +<H2><A NAME="ss1.5">1.5</A> <A HREF="#toc1.5">Books about MythTV</A> +</H2> + +<P>If you would like to purchase a book specifically about MythTV:</P> +<P> +<UL> +<LI>Hacking MythTV, ISBN 978-0470037874 by Wilson, Tittel, Wright and Korelc</LI> +<LI>Practical MythTV: Building a PVR and Media Center PC, ISBN 978-1590597798 by Smith and Still</LI> +</UL> +</P> + +<H2><A NAME="ss1.6">1.6</A> <A HREF="#toc1.6">Document conventions</A> +</H2> + +<P>The following conventions are used throughout this document.<BR> +<B>boldface</B> - used for program names.<BR> +<CODE>typewriter</CODE> - used for program paths.<BR> +<EM>emphasis</EM> - Pay attention here.<BR></P> +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION>Pay more attention.</CAPTION> +</FIGURE> +</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION>Ignore at your own peril.</CAPTION> +</FIGURE> +</P> +<P> +<FIGURE> +<EPS FILE="add.eps"> +<IMG SRC="add.png"> +<CAPTION>Feature that has been added to SVN (subversion, a revision control system) +but is not available in the current release.</CAPTION> +</FIGURE> +</P> + +<H2><A NAME="ss1.7">1.7</A> <A HREF="#toc1.7">Mailing lists / getting help</A> +</H2> + +<P>It's recommended that you join the user list at +<A HREF="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</A>. The developer +list is at +<A HREF="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev</A>. Please keep +the developer list strictly for development-related issues.</P> +<P>Searchable archives for the lists are available at +<A HREF="http://www.gossamer-threads.com/lists/mythtv/">http://www.gossamer-threads.com/lists/mythtv/</A>.</P> + +<H2><A NAME="ss1.8">1.8</A> <A HREF="#toc1.8">IRC</A> +</H2> + +<P>There are two IRC channels dedicated to MythTV which can be found on +irc.freenode.net +<UL> +<LI>mythtv</LI> +<LI>mythtv-users</LI> +</UL> +</P> +<P>The <CODE>mythtv</CODE> channel is where the developers discuss code. It is +<EM>not</EM> a user-support channel. Please don't ask non-development +related questions there.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION>Really. Even if there's no one in the mythtv-users IRC group or everyone +seems to be ignoring you.</CAPTION> +</FIGURE> +</P> + +<H2><A NAME="ss1.9">1.9</A> <A HREF="#toc1.9">Bug database</A> +</H2> + +<P>If you feel you need to contribute to a bug database, use the MythTV bug +ticketing system at +<A HREF="http://svn.mythtv.org/trac">http://svn.mythtv.org/trac</A>.</P> +<P>Good entries will contain the following: +<OL> +<LI>Qt version</LI> +<LI>Linux distribution</LI> +<LI>gcc version</LI> +<LI>the last entry in config.log to detail how you compiled</LI> +<LI>MythTV version numbers (<EM>e.g.</EM>from mythfrontend --version)</LI> +<LI>Hardware</LI> +<LI>How you are able to reproduce the bug</LI> +</OL> +</P> +<P>See the instructions on how to debug in +<A HREF="#debugging">Section 22</A>.</P> +<P>The bug database is not a chat room, so restrict your entries to what is +relevant. It's also not a repository of feature requests; a feature request +without an accompanying patch file to implement that feature will be quickly +closed. There is a feature wishlist on the wiki at +<A HREF="http://www.mythtv.org/wiki/index.php/Feature_Wishlist">http://www.mythtv.org/wiki/index.php/Feature_Wishlist</A>. There is no +guarantee that anything on the wishlist will ever get code written to +implement it.</P> +<P>If a developer closes out your bug, it's likely you didn't provide enough +information. Don't re-open a bug without providing additional information.</P> + +<H2><A NAME="ss1.10">1.10</A> <A HREF="#toc1.10">Contributing to this document</A> +</H2> + +<P>Contributions to the HOWTO are welcome, especially if you find a +grammatical or spelling error, or if the wording of something is just plain +confusing.</P> +<P>If you'd like to make a new contribution, create a ticket at +<A HREF="http://svn.mythtv.org/trac">http://svn.mythtv.org/trac</A> and +click "New Ticket". The type should be set to "patch" and the owner set to +"rkulagow" to ensure that I see your contribution.</P> +<P>Please send it as either SGML or as plain text. <EM>NO HTML</EM>. The +source used to create the HOWTO is in SGML / Linuxdoc. Do not be afraid of +SGML! A quick look at the source of this HOWTO will show that it is not +difficult, because there aren't that many tags to worry about, so at least +<EM>try</EM> to submit as SGML. See the Linuxdoc HOWTO at +<A HREF="http://www.tldp.org/HOWTO/Howtos-with-LinuxDoc.html">http://www.tldp.org/HOWTO/Howtos-with-LinuxDoc.html</A> for information +on the linuxdoc format itself, or look at the <CODE>mythtv-HOWTO.sgml</CODE> +file as an example.</P> +<P>To create the actual patch, run <B>diff -u origfilename newfile > +doc.patch</B> and attach your contribution to the trac ticket.</P> + +<H2><A NAME="s2">2.</A> <A HREF="#toc2">Introduction.</A></H2> + +<P>This HOWTO document will focus on manually building MythTV in a North +American environment. If you have installation instructions for a different +region or Linux distribution, please send them to the author so that it can +be included in other versions of this document.</P> + +<H2><A NAME="s3">3.</A> <A HREF="#toc3">Checking prerequisites. </A></H2> + +<P>You must ensure that any firewalls (either hardware, or a software +firewall installed by your distribution) will not block access to the ports +that will be used by the MythTV clients and servers on the "inside" LAN. +The ports for MySQL (TCP port 3306) and mythbackend (TCP ports 6543 and +6544) must be open. It is <EM>strongly</EM> recommended that you do +<EM>not</EM> expose the MythTV and MySQL ports to the Internet or your +"Outside" LAN.</P> + +<H2><A NAME="ss3.1">3.1</A> <A HREF="#toc3.1">Hardware</A> +</H2> + +<P>Hardware selection is a complex topic, one this HOWTO will only discuss +briefly and in general terms. The following subsections offer some general +guidance but stop short of offering specific recommendations.</P> +<P>For a good MythTV experience, you must understand that MythTV exercises your +hardware more than a typical desktop. Encoder cards generate DMA across the +PCI bus. The CPU is busy encoding / decoding video. Hard drives are +constantly reading and writing data. Building a MythTV system on older / +"spare" hardware may be an exercise in frustration and can waste many hours +of valuable time.</P> +<P>For more detail about actual configurations that others have used, Mark +Cooper has setup a hardware database at +<A HREF="http://pvrhw.goldfish.org/">http://pvrhw.goldfish.org/</A>. The +website will let you browse what other users have reported as their hardware +configuration, and how happy they are with the results.</P> +<P>If you have specific questions about the suitability of specific hardware +choices, you can consult the archives of the mythtv-users mailing list at +<A HREF="http://www.gossamer-threads.com/lists/mythtv/">http://www.gossamer-threads.com/lists/mythtv/</A> or +post a question to the list.</P> +<H3>CPU Type and Speed</H3> + +<P>Selection of CPU type and speed is one of the trickiest elements of +hardware selection, mainly because there are so many tradeoffs which can be +made. For example, if you have plenty of CPU, you can use higher bitrates +or capture sizes, etc.</P> +<P>MythTV has two modes of operation. First, it can function as a software +video encoder, which means that it uses a fairly generic "dumb" video +capture card to get frames of video, encodes them using the CPU on your +motherboard and writes them to disk. High-end video capture cards and +devices like the TiVo and ReplayTV have dedicated encoder chips which use +specialized hardware to convert the video stream to the MPEG-2 format +without using the motherboard CPU. The main CPU has the responsibility of +running the Operating System and reading and writing the encoded frames to +the disk. These tasks have fairly low CPU requirements compared to encoding +video, which is why a device like a Series 1 TiVo can run with only 16MB of +RAM and a 54MHz CPU.</P> +<P>There are many variables that go into the question: "How fast a CPU do I +need to run MythTV"? Obviously, the faster your CPU, the better your +experience will be with MythTV. If you are using the software MPEG-4 +encoder and performing the "Watch TV" function, where the CPU is both +encoding and decoding video simultaneously to allow Pause, Fast Forward and +Rewind functions for live TV requires more CPU then just encoding or +decoding. MythTV also supports multiple encoder cards in a single PC, +thereby increasing the CPU requirements if you plan on simultaneously +encoding multiple programs. As a general guideline, plan on 1GHz per +encoder if you are doing software-based encoding, less if you are using a +hardware-based encoder.</P> +<P>Here are a few data points: +<UL> +<LI>A PIII/733MHz system can encode one video stream using the MPEG-4 +codec using 480x480 capture resolution. This does not allow for live TV +watching, but does allow for encoding video and then watching it later.</LI> +<LI>A developer states that his AMD1800+ system can <B>almost</B> +encode two MPEG-4 video streams and watch one program simultaneously.</LI> +<LI>A PIII/800MHz system with 512MB RAM can encode one video +stream using the RTjpeg codec with 480x480 capture resolution and play it back +simultaneously, thereby allowing live TV watching.</LI> +<LI>A dual Celeron/450MHz is able to view a 480x480 MPEG-4/3300kbps file +created on a different system with 30% CPU usage.</LI> +<LI>A P4 2.4GHz machine can encode two 3300Kbps 480x480 MPEG-4 files and +simultaneously serve content to a remote frontend.</LI> +</UL> +</P> +<P>The second mode of operation is where MythTV is paired with a hardware-based +video encoder, such as a Matrox G200 or a Hauppauge +WinTV-PVR-150/250/350/500. In this mode, because the video encoding is +being done by a dedicated video processor, the host CPU requirements are +quite low. See the +<A HREF="#video_capture_device">Video Capture Device</A> section for details.</P> +<P>The price differential between a frame grabber and a card that implements +hardware MPEG-2 encoding, such as the Hauppauge PVR-x50 series, is now less +than $30 US. Primary development in MythTV has transitioned to supporting +MPEG-2 capture devices and HDTV, so if given the option, go with the +hardware MPEG-2 encoder.</P> +<P>If you have a Via M10000 series or a Hauppauge PVR-350, MythTV can use the +hardware-based video decoder for playback, which further reduces CPU +requirements.</P> + +<H3>Memory</H3> + +<P>A MythTV host that is both a backend and a frontend and using software +encoding with a single capture card should run adequately in 256MB of RAM. +Additional RAM above 256MB will not necessarily increase performance, but +may be useful if you are running multiple encoders.</P> + +<H3>Hard Disk(s)</H3> + +<P>Encoded video takes up a lot of hard disk space. The exact amount depends +on the encoding scheme, the size of the raw images and the frames per +second, but typical values for MythTV range from 700 megabytes/hour for +MPEG-4, 2 GB/hour for MPEG-2 and RTjpeg and 7 GB/hour for ATSC HDTV.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: You <EM>must</EM> use DMA for hard drive access to prevent +choppy or jittery video. Not all distributions enable DMA at boot time. See the Troubleshooting Section for +<A HREF="#Setting_DMA">instructions</A> on how to do this.</CAPTION> +</FIGURE> +</P> +<P>Writing video to disk is sensitive to timing issues; RTjpeg requires less +CPU with the tradeoff being larger files and needing to write to the disk +faster. MPEG-4 requires more CPU, but the files are smaller. At the +default resolution, MPEG-2 creates the largest files of all with almost no +CPU impact.</P> +<P>See the Troubleshooting +<A HREF="#Setting_DMA">section</A> for more +information.</P> + +<H3>Filesystems</H3> + +<P>MythTV creates large files, many in excess of 4GB. You <EM>must</EM> +use a 64 or 128 bit filesystem. These will allow you to create large files. +Filesystems known to have problems with large files are FAT (all versions), +and ReiserFS (versions 3 and 4). </P> +<P>Because MythTV creates very large files, a filesystem that does well at +deleting large files is important. Numerous benchmarks show that XFS and +JFS do very well at this task. You are <EM>strongly</EM> encouraged to +consider one of these for your MythTV filesystem. JFS is the absolute best +at deletion, so you may want to try it if XFS gives you problems. MythTV +.21 incorporates a "slow delete" feature, which progressively shrinks +the file rather than attempting to delete it all at once, so if you're more +comfortable with a filesystem such as ext3 (whose delete performance for +large files isn't that good) you may use it rather than one of the +known-good high-performance file systems. There are other ramifications to +using XFS and JFS - neither offer the opportunity to shrink a filesystem; +they may only be expanded.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: You <EM>must not</EM> use ReiserFS v3 for +your recordings. You will get corrupted recordings if you do.</CAPTION> +</FIGURE> +</P> +<P>Because of the size of the MythTV files, it may be useful to plan for future +expansion right from the beginning. If your case and power supply have the +capacity for additional hard drives, read through the +<A HREF="#LVM">LVM</A> and +<A HREF="#advancedpartitionformatting">Advanced Partition Formatting</A> sections for some pointers.</P> +<P> +<A NAME="video_capture_device"></A> </P> +<H3>Video Capture Device </H3> + +<P>In order to capture video, MythTV will need one or more video capture +devices with Linux drivers. There are a number of classes of hardware +available for capturing video. </P> +<H3>Frame Grabbers.</H3> + +<P>This class of card is the simplest and is usually the cheapest. There is no +on-board encoding of the analog video; hardware known as a Digital-Analog +Converter (DAC) takes the video and presents it to the computer in an +essentially raw digital form.</P> +<P>For a list of video capture cards known to work with Linux, please see +<CODE>/usr/src/linux/Documentation/video4linux/bttv</CODE> for a partial +listing; even if your specific card is not listed, it may be that the vendor +is actually using a standard reference design and placing their own name on +it. See the video4linux mailing list ( +<A HREF="https://listman.redhat.com/mailman/listinfo/video4linux-list">https://listman.redhat.com/mailman/listinfo/video4linux-list</A>) for +more information and for specific hardware questions.</P> +<P>The most common inexpensive cards available use the Bt848, Bt878 or CX2388x +series of video capture chips; examples are the "Hauppauge WinTV Go" card and +the "AverTV Desktop PVR" card, both of which use the bttv kernel module.</P> +<P> +<HR> +<PRE> +NOTE: The ATI TV Wonder series and the ATI All-in-Wonder series of cards +are not the same. The All-in-Wonder cards will not work with MythTV. +</PRE> +<HR> +</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +</FIGURE> + +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: The ATI All-in-Wonder cards (which are not the same +as the ATI TV Wonder, TV Wonder VE or TV Wonder Pro) <EM>will not</EM> work +as a MythTV capture device because the GATOS +<A HREF="http://gatos.sourceforge.net">http://gatos.sourceforge.net</A> +drivers that are available provide only a limited subset of the V4L API. The TV Wonder series of cards are supported by the Bt8x8 Video4Linux driver.</CAPTION> +</FIGURE> +</P> +<P>After you have installed a suitable capture device, you can check that +the kernel sees it with <CODE>lspci</CODE>. Look for an entry labeled "Multimedia +video controller". To get more detailed information about the card, use +<CODE>lspci -v</CODE> or <CODE>lspci -vv</CODE>. Ensure that your system is loading +the bttv modules by typing: +<BLOCKQUOTE><CODE> +<PRE> +# lsmod |grep bttv +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>You want to see the <CODE>bttv</CODE> module listed.</P> +<H3>Hardware MPEG-2 encoders.</H3> + +<P>While inexpensive video-capture cards simply capture raw frames, leaving +encoding to software, some higher-end cards incorporate hardware-based +encoding. Using either a G200 MJPEG encoder card, or a MPEG-2 encoder card +supported by the IvyTV project +<A HREF="http://ivtvdriver.org/">http://ivtvdriver.org</A> such as the Hauppauge +PVR-150/250/350/500, Avermedia M179, Hauppauge "Freestyle" or Yuan M600 +cards will allow you to use dedicated hardware encoders rather than your +CPU. (The PVR-350 can simultaneously be used as an output device.) Using the +on-board MPEG-2 encoder greatly reduces the CPU requirements for +encoding.</P> +<P>The ivtv driver was incorporated into the Linux kernel starting at v2.6.22.</P> +<P>There is a Beta driver for the HVR-1600 card at +<A HREF="http://www.ivtvdriver.org/index.php/Cx18">http://www.ivtvdriver.org/index.php/Cx18</A></P> +<P><B>NOTE</B>: Motherboards with the Via chipset are notoriously bad with +DMA and have caused numerous issues with ivtv, including hard locks. See +the ivtv website +<A HREF="http://ivtvdriver.org">http://ivtvdriver.org</A> +for the latest information on what works and what doesn't.</P> +<P>Here are some data points for encoding: +<UL> +<LI>A Celeron 450 uses 2% CPU for encoding a 480x480 16Mbps MPEG-2 stream.</LI> +</UL> +</P> +<P>Here are some data points for decoding:</P> +<P> +<UL> +<LI>An Athlon 1800XP can decode a 720x480 8Mbps MPEG-2 file using 10% CPU</LI> +<LI>An Athlon 1GHz can decode a 720x480 16Mbps MPEG-2 file using 30-50% +CPU, can decode a 480x480 16Mbps MPEG-2 using 30% CPU and approximately 30% +for Live TV at 416x480.</LI> +<LI>A P3-550 can decode a 480x480 16Mbps MPEG-2 file with 55% CPU.</LI> +<LI>A Celeron 450 (no SSE) can decode a 480x480 16Mbps MPEG-2 file with +80% CPU.</LI> +</UL> +</P> + +<H3>DVB capture cards.</H3> + +<P>DVB is a video standard primarily found in Europe (where it comes in +DVB-C, DVB-T and DVB-S varieties for Cable, Terrestrial and Satellite) and +is also used as the programming interface for HDTV capture cards in Linux. +To see if your DVB card is supported, see the list of cards in the +"Supported Hardware" section of the DVB Wiki at +<A HREF="http://www.linuxtv.org/wiki/index.php/Main_Page">http://www.linuxtv.org/wiki/index.php/Main_Page</A> for more +information.</P> +<P>In the United States, you may use a card such as the TwinHan to obtain +unencrypted Free-To-Air satellite channels. See +<A HREF="http://www.lyngsat.com/">http://www.lyngsat.com/</A> for the types +of content which is available.</P> + +<H3>HDTV.</H3> + +<P>There are a number of HDTV cards with Linux drivers which are known to +operate in the United States; a complete list of cards with DVB drivers can +be found at +<A HREF="http://www.linuxtv.org/wiki/index.php/ATSC_Devices">http://www.linuxtv.org/wiki/index.php/ATSC_Devices</A> Some cards +support capture of unencrypted digital cable TV (utilizing QAM256), others +will only work with Over The Air (aka "OTA") signals captured with an +antenna (with 8VSB).</P> +<P>Cards that have been reported to work include: +<UL> +<LI>pcHDTV HD-2000, Air2PC PCI rev 1-3 (8VSB only)</LI> +<LI>SiliconDust HDHomeRun (8VSB, QAM256)</LI> +<LI>pcHDTV HD-3000/5500 (8VSB, QAM256)</LI> +<LI>Air2PC HD-5000 (8VSB, QAM256)</LI> +<LI>DViCO Fusion HDTV Lite/Gold 5 (8VSB, QAM256)</LI> +</UL> +</P> +<P><B>NOTE</B>: There are no known consumer-level capture devices which will +allow you to capture the HDTV output (DVI, HDMI, VGA, YPbPr / Component) +from a set-top box commonly found with digital cable systems or satellite +systems. <EM>None</EM> of the capture devices listed above +perform any encoding; they merely allow your computer to save a copy of a +HDTV stream which has already been converted to MPEG-2 at the broadcast +facility.</P> +<P><B>NOTE:</B>: All of the cards listed above (except for the HD-2000 and +HDHomeRun) should be configured as DVB cards. The HD-2000 can be configured +as a pcHDTV card if you use the V4L drivers from +<A HREF="http://www.pchdtv.com">http://www.pchdtv.com</A> and use Linux +kernel 2.6.9 or earlier. With kernel 2.6.10 and higher it must be +configured as a DVB card, but you lose access to the second antenna input in +ATSC mode. The HDHomeRun should be configured as two HDHomeRun cards, one +for each tuner.</P> +<P>To playback HDTV content, plan on a powerful CPU. "How powerful?" depends +on a number of factors, such as the capture resolution, whether the video is +progressive or interlaced, and whether your display card has hardware-assist +support for Linux.</P> +<P>The Simple Answer: Once you are in the 3.2 Ghz P4-class of CPU you should have +no issues with viewing HDTV.</P> +<P>The Complicated Answer:</P> +<P>For 720p content (1280x720), a 2.4GHz P4 should be sufficient.</P> +<P>For 1920x1080i->1920x1080p with the better deinterlacing methods +done in real time a 2.4GHz CPU is taxed, but should work if you use "Bob and +Weave" deinterlacing, or if you have an NVIDIA card with MPEG-2 hardware +acceleration. If you enable the hardware acceleration, you may be able to +use a 1.8GHz processor.</P> + +<H3>Firewire.</H3> + +<P>You may use the Firewire output of the Motorola DCT6200 or the SA3250. +If your provider uses 5C encryption on a particular channel, you won't be +able to get any content.</P> + +<H3>DBoxII or other devices running Neutrino</H3> + +<P>You may use the Ethernet port of an DBoxII or a similar device to capture +MPEG2. Your set top box has to be running the Neutrino GUI. </P> + +<H3>USB Capture Devices.</H3> + +<P>The Plextor ConvertX PVR devices are supported through Linux drivers +available from +<A HREF="http://www.plextor.com/english/support/LinuxSDK.htm">http://www.plextor.com/english/support/LinuxSDK.htm</A>. MythTV uses the +Plextor to capture hardware encoded MPEG-4, so the host CPU requirements are low.</P> +<P>Hauppauge WinTV-PVR-USB2 (driver available at +<A HREF="http://www.isely.net/pvrusb2/">http://www.isely.net/pvrusb2/</A>) +emulates a PVR-x50 card.</P> + +<H3>IP Recorder (RTSP, RTS, UDP)</H3> + +<P>MPEG-2, MPEG-4 and H.264 internet TS stream recording is supported using +the IPTV recorder in MythTV. This recorder expects the channels to be supplied +as a m3u playlist. If your DSL/Fiber provider supplies television service, +but does not provide a m3u playlist for the channels, you can construct one +for your own use. You do not need to download it from the same server as the +streams themselves, and can also read it from a file if this is more convenient.</P> +<P><B>NOTE</B>: Some DSL providers only allow you to use one recorder at a +time, so you may need to limit yourself to one recorder in MythTV and turn +off any set top box the cable provider sold or rented to you with your +service. This limitation is independent of the bandwidth you have purchased.</P> + +<H3>Hardware known NOT to work and other issues</H3> + +<P> +<UL> +<LI>Hauppauge WinTV-D or -HD (no driver)</LI> +<LI>Hauppauge WinTV-USB series</LI> +<LI>Hauppauge WinTV-PVR-usb (model 602), or WinTV-PVR-PCI (model 880) cards (no driver - this is not the PVR-250/350 +series of cards supported by the IvyTV driver)</LI> +<LI>ATI All-in-Wonder series</LI> +</UL> +</P> + +<H3>Sound card</H3> + +<P>The system needs a sound card or an on-board equivalent on the motherboard +to play back and in most cases, to record sound. Any sound card that can be +operated by the ALSA (Advanced Linux Sound Architecture) kernel modules will +work with MythTV. However, some cards and drivers will provide better +quality or compatibility than others. In particular, many audio +devices included on motherboards can be problematic.</P> +<P>The usual practice for capturing the audio associated with the video is to +run a cable from an audio output on the video capture card to the Line input +on a sound card. However, some video capture cards provide on-board audio +capabilities that work with the kernel <CODE>btaudio</CODE> module instead, +thereby eliminating the need for a cable. This is useful if you will be +using multiple capture cards in a single chassis, since each capture card +will not need its own sound card. Note that a separate sound card is still +required for playback when using <CODE>btaudio</CODE>, and that often the audio +recorded in this way will be mono only. See the +<A HREF="#btaudio">btaudio</A> section for more information.</P> +<P> +<FIGURE> +<EPS FILE="warning"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: Analog video capture cards are the only ones which +require a soundcard for capturing audio. DVB, HDTV, and other hardware +encoder cards all provide a combined audio / video stream.</CAPTION> +</FIGURE> +</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Plugging a Line-level device into the Mic input is +not recommended. Line-level devices have higher voltages and can damage the +sound card. In addition, even if it doesn't break your card, you will be +getting Mono sound. See the Linux MP3 HOWTO at +<A HREF="http://www.tldp.org/HOWTO/MP3-HOWTO.html">http://www.tldp.org/HOWTO/MP3-HOWTO.html</A> for additional information.</CAPTION> +</FIGURE> +</P> + +<H3>Video Display Card</H3> + +<P>MythTV will work with just about any video card. However, it is highly +recommended that you use a card which supports XVideo (XV) extensions. If +your card does not support XV, color conversion and scaling will be +performed by your CPU rather than the video card. This is very CPU +and memory intensive and will often result in dropped frames and a +corresponding degradation of quality. Check the X documentation +for details if you are uncertain about your preferred card. You may +also run <CODE>xvinfo</CODE>; look for your video card to be listed as one +of the adapters.</P> + +<P>If you want to use MythTV with a standard television, you will need a +physical connection from your video card to your TV set, which can either be +a TV-out port on the card itself or an external adapter that converts the +VGA signal to an appropriate video signal. "Appropriate" depends on a number +of factors, such as video standard (NTSC vs. PAL), the type of input +connection (Composite vs. SVideo), etc.</P> +<P>Note that with some video cards and X drivers, XVideo extensions are +only supported on the VGA output, and not on the TV output.</P> + +<H3>Cards with TV-out</H3> + +<P>The next section deals with a number of cards that are known to have +TV-out ports. The list is unlikely to be complete, so if you know of +others, please post a message to the mythtv-users mailing list so the +information can be included in future versions of the HOWTO. The list is +organized by manufacturer.</P> +<P>Reports here are based on what users of the cards have posted on the +mythtv-users mailing list, so if you need configuration details, please +search the archives at +<A HREF="http://www.gossamer-threads.com/lists/mythtv/">http://www.gossamer-threads.com/lists/mythtv/</A> using +the card name in your search string.</P> + +<H3>ATI</H3> + +<P>ATI makes many cards with TV-out capability, but only offers Linux +drivers for Radeon 8500 and above cards. See the Drivers and Software +section of +<A HREF="http://www.ati.com/">http://www.ati.com</A> for the +driver and additional information.</P> +<P>The enhanced ati.2 X driver created by the GATOS +<A HREF="http://gatos.sourceforge.net">http://gatos.sourceforge.net</A> +project offers some support for TV-out on other ATI cards, but only in its +"experimental" version, available through CVS. There have been reports from +people who say they have made this driver work with one or another ATI card. +For example, Bruce Markey +<A HREF="mailto:bjm@lvcm.com">mailto:bjm@lvcm.com</A> writes (on the +mythtv-users mailing list): "I got this to work. You can quote me on that. +I've used TV-out on several models of ATI cards both All-In-Wonder and +regular cards with TV-out." See the "Adventurous Setup" section of +<A HREF="http://gatos.sourceforge.net/watching_tv.php">http://gatos.sourceforge.net/watching_tv.php</A> for details. Also see +<A HREF="http://www.retinalburn.net/linux/tvout.html">http://www.retinalburn.net/linux/tvout.html</A> for more information.</P> + +<H3>NVIDIA</H3> + +<P>Some NVIDIA cards with TV-out can be run using the standard nv driver in +X, combined with the userspace application <B>nvtv</B> to control the TV-out +port. See +<A HREF="http://sourceforge.net/projects/nv-tv-out/">http://sourceforge.net/projects/nv-tv-out/</A> for details. Recent +versions of the NVIDIA driver have better support for overscan and other +features useful with TV-Out, so the <B>nvtv</B> application may not be +required.</P> +<P>Some NVIDIA cards can be run with a proprietary NVIDIA X driver made +available by NVIDIA. See +<A HREF="http://www.nvidia.com/object/unix.html">http://www.nvidia.com/object/unix.html</A> for more information.</P> +<P><B>NOTE</B>: It's strongly recommended that you use the proprietary +NVIDIA drivers; they have excellent support for XvMC and ship with a good +configuration utility. XvMC provides MPEG-2 hardware acceleration, which is +important if you want to display HDTV.</P> + +<H3><A NAME="PVR-350"></A> Hauppauge PVR-350 </H3> + +<P>MythTV supports the TV-out and MPEG-2 decoder functions in the IvyTV +driver.</P> +<P>The PVR-350 is unique amongst the Hauppauge PVR-x50 cards in that it also +supports audio output, but you need to connect that audio output to +something. There are two courses of action you may take: +<OL> +<LI>Take the audio output from the PVR-350 and plug it into an input on a +sound card on your machine. You may then use MythTV's internal audio +controls.</LI> +<LI>Take the audio output from the PVR-350 and connect it directly to your +television / audio system. You must indicate that you are using external +audio control on the PVR-350 setup page.</LI> +</OL> +</P> + +<H3>Other Options</H3> + +<P>Some devices with on-board TV-out capability, such as Xboxes converted to +Linux and some laptops can be used as MythTV frontends to display on a +television screen. Please consult the mythtv-users mailing list for messages +that report the details of these special arrangements.</P> + +<H3>External Adapters</H3> + +<P>External adapters convert standard VGA output to a form suitable for +display on a television. The output format varies by region, since +different countries have different TV standards. People on the mythtv-users +list have mentioned these adapters:</P> +<P> +<UL> +<LI>AITech Web Cable Plus, powered by external transformer or takes power +from PS/2 keyboard connector, support resolutions up to 1024x768, outputs +composite and SVideo, provides position adjustment.</LI> +<LI>Averkey lite, powered by a USB port, has Composite, SVideo, YPbPr +outputs; pan, brightness, overscan/underscan controls; supports up to +1024x768 outputs; and supports PAL and NTSC.</LI> +<LI>ADS TV Elite XGA</LI> +<LI>AverKey iMicro (comments are generally favorable)</LI> +<LI>AITech Web Cable (comments are generally unfavorable, different than +the "Plus" version above)</LI> +<LI>TVIEW Gold (mentioned once, favorably)</LI> +</UL> +</P> + +<H2><A NAME="ss3.2">3.2</A> <A HREF="#toc3.2">Software</A> +</H2> + +<P>There are a few ways of installing programs on Linux systems; you can +either use a pre-compiled package, or install from a tarball after +satisfying any prerequisites.</P> +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: you must have the MySQL database software installed on a +system to store the master database. This does not necessarily mean that +MySQL must run on one of the MythTV boxes. The minimum MySQL version is 5.0.</CAPTION> +</FIGURE> +</P> + +<H3><A NAME="precompiled"></A> Pre-compiled packages </H3> + +<P>A number of people have created pre-compiled packages for MythTV that may +make your installation easier.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>BIG FAT WARNING</B>: This HOWTO assumes that you have <EM>not</EM> +installed MythTV from a package. All example command lines and file +locations are based on the MythTV tarball defaults. Some packagers have +modified the filenames, binaries and file locations to match what is +commonly found in that distribution. Any issues with MythTV installed via a +pre-compiled package <B>MUST</B> be raised with the packager.</CAPTION> +</FIGURE> +</P> +<P>If you use any of the pre-compiled packages you may not need to perform any +additional configuration steps in this HOWTO. The next logical step is +<A HREF="#mysql">configuring MySQL</A>, which you may or may not have to +perform. See your package documentation.</P> + +<H3><A NAME="atrpms"></A> Red Hat Linux / Fedora Core </H3> + +<P>The definitive documentation on installing MythTV on Red Hat Linux / +Fedora Core can be found in Jarod Wilson's ( +<A HREF="mailto:jcw@wilsonet.com">mailto:jcw@wilsonet.com</A>) HOWTO at +<A HREF="http://wilsonet.com/mythtv/">http://wilsonet.com/mythtv/</A> Just +like 3rd-party packages, any 3rd-party documentation problems should be +brought up with the 3rd-parties (maintainer, lists, bugzillas etc.). The +installation instructions which follow should be used as a guide only; refer +to Jarod's guide.</P> +<P>Red Hat Linux and Fedora Core packages for MythTV and all of its add-on +modules and some themes have been packaged by +<A HREF="mailto:Axel.Thimm@ATrpms.net">mailto:Axel.Thimm@ATrpms.net</A> and +are available at +<A HREF="http://ATrpms.net/topic/multimedia/">http://ATrpms.net/topic/multimedia/</A>. All of the prerequisites for +MythTV (such as XMLTV) are available as RPM packages. If you have problems +with the RPMs, please contact the ATrpms lists at +<A HREF="http://lists.ATrpms.net/">http://lists.ATrpms.net/</A> or file a +bug against +<A HREF="http://bugzilla.ATrpms.net/">http://bugzilla.ATrpms.net/</A>.</P> +<P>Given the large number of dependent RPMs you are advised to use tools like +apt or yum for automatic retrieval and installation of the required RPMs. +( +<A HREF="http://ATrpms.net/install.html">http://ATrpms.net/install.html</A>) In this case a +special meta-package called mythtv-suite will allow you to install all of +MythTV and its add-ons, plus all dependencies.</P> +<P>If you don't have <B>apt</B> or <B>yum</B> on your machine, download and +install the atrpms-kickstart package from +<A HREF="http://ATrpms.net/name/atrpms-kickstart/">http://ATrpms.net/name/atrpms-kickstart/</A>. +Install the package with: +<BLOCKQUOTE><CODE> +<PRE> +# rpm -Uvh atrpms-kickstart* +</PRE> +</CODE></BLOCKQUOTE> + +Then run: +<BLOCKQUOTE><CODE> +<PRE> +# apt-get update +# apt-get dist-upgrade +# apt-get update +</PRE> +</CODE></BLOCKQUOTE> + +And finally: +<BLOCKQUOTE><CODE> +<PRE> +# apt-get install mythtv-suite +</PRE> +</CODE></BLOCKQUOTE> + +These steps however, do NOT perform the installation of any drivers required +for <B>ALSA</B>, capture cards, <B>lirc kernel modules</B>, etc., nor do +they set up your MythTV database. Check +<A HREF="http://ATrpms.net/topic/multimedia/">http://ATrpms.net/topic/multimedia/</A> for the drivers you +need.</P> + +<H3>Mandriva</H3> + +<P>Thac has created RPMs for MythTV for Mandriva which may +be obtained from +<A HREF="http://rpm.nyvalls.se/">http://rpm.nyvalls.se/</A> If you have problems with the RPMs, please +send him email directly at +<A HREF="thac@nyvalls.se">thac@nyvalls.se</A>.</P> +<H3>Debian</H3> + +<P>Debian packages for MythTV and most of its add-on modules are maintained +by Christian Marillat +<A HREF="mailto:marillat@free.fr">mailto:marillat@free.fr</A> and are available at +<A HREF="http://www.debian-multimedia.org/">http://www.debian-multimedia.org/</A>. +Installation instructions can be found on those pages as well. All of the +prerequisites for MythTV are available as Debian packages, most of them from +the official Debian archive.</P> +<P>If you have followed the instructions on the above page you should have added +<BLOCKQUOTE><CODE> +<PRE> +deb-src http://www.debian-multimedia.org sid main +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>to your <CODE>/etc/apt/sources.list</CODE> file. Running <B>apt-get update</B> and then +executing <B>apt-get build-dep mythtv</B> should install all the +pre-requisites required to compile MythTV.</P> +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: Due to the requirement for Qt 3.3+, there are no packages for +Debian woody/stable.</CAPTION> +</FIGURE> +</P> + +<P>The Debian packages are configured such that MythTV programs should be +run as the <CODE>mythtv</CODE> user, which is automatically created during +installation. This user has access to write new recordings to disk in the +default directory, read and write the database, access the audio and video +devices, and everything else that MythTV needs to do.</P> + +<P>See <CODE>/usr/share/doc/<I>packagename</I>/README.Debian</CODE> for more +information, including copies of the MythTV documentation. The +<CODE>mythtv-doc</CODE> package contains a copy of this HOWTO in +<CODE>/usr/share/doc/mythtv-doc</CODE>.</P> +<H3>Manual installation</H3> + +<P>You may use the graphical tools that come with your distribution, or you +can use command-line utilities. Either system will get the job done, and it +all depends on your comfort level with Linux.</P> +<P>In order to compile MythTV, we need to make sure that the software it needs +is installed. This list includes <B>mysql</B>, <B>gcc</B>, +<B>freetype2-devel</B>, <B>xorg-xserver-devel</B>, <B>qt-devel</B> and +<B>lame</B>. If you're going to use a remote control with MythTV, you're +going to need the <B>cdialog</B> package in order to compile +<B>lircd</B> if your distribution doesn't have a pre-packaged +<B>lirc</B>. If you are using <B>XMLTV</B> as a grabber, you will need +<B>perl</B>.</P> +<P> +<HR> +<PRE> +NOTE: Qt v3.3 or higher is required. + +NOTE: MythTV DOES NOT WORK with Qt4. + +NOTE: If you are going to be using RPMs to install various +components, you should be aware that not all packages include the necessary +headers for compiling. If you're having trouble compiling, ensure +that you've installed the -devel version of a prerequisite. +</PRE> +<HR> +</P> + +<H3><A NAME="CLIinstalltools_"></A> Command-line installation </H3> + +<P> This section details the various methods for installing prerequisites +from the command line.</P> + +<H3>Mandriva</H3> + +<P><B>NOTE</B>: The following instructions should be considered out of +date as of 2006-09-10. If updated instructions are not submitted by the +release of v0.21 of MythTV they will be removed.</P> +<P><B>urpmi</B> is the simplest tool for installation of packages from the +command line, but properly configuring it can be difficult. The +following website +<A HREF="http://easyurpmi.zarb.org/">http://easyurpmi.zarb.org/</A> will allow you to choose +a mirror site and then present the command-line configuration text for that +mirror. You will most likely need to add a "Contrib" mirror to your setup. +If you add a site from the "Penguin Liberation Front", you will be able to +load the <CODE>lame</CODE> library without compiling from source.</P> +<P>Open a shell, and execute the following. You may get +asked a number of questions regarding dependencies. It's best to answer +"YES". +<BLOCKQUOTE><CODE> +<PRE> +$ su +# urpmi mysql gcc gcc-c++ freetype2-devel cdialog alsa-utils +# urpmi XFree86-devel perl +# urpmi libqt3-devel libMesaGLU1-devel +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P> +<HR> +<PRE> +NOTE for Mandriva 9.1+ users: execute the following command. + +# urpmi libqt3-mysql +</PRE> +<HR> + +However, you might get this when you execute the commands above: +<BLOCKQUOTE><CODE> +<PRE> +everything already installed +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>In that case, you're ready to move to the next +<A HREF="#Setting_up_paths">section</A>. Once you have completed installing the pre-requisites, +exit out of the shell and start a new one to ensure that any environment +variables setup by the installation have a chance to take effect.</P> + +<H3>Gentoo. </H3> + +<P><B>NOTE</B>: MythTV does <EM>not</EM> run on Qt4. +If Qt has not been installed on your system: Edit +<CODE>/etc/make.conf</CODE> and locate the "USE" variable. If the line is +commented out, remove the comment. The line should have at least: +<BLOCKQUOTE><CODE> +<PRE> +USE="mysql alsa" +</PRE> +</CODE></BLOCKQUOTE> + +Next you need to build Qt. If you don't plan on using the ebuilds as +described in the Gentoo section then you also need to install lame. +<BLOCKQUOTE><CODE> +<PRE> +# emerge lame mysql qt +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you have already installed Qt: you will need to rebuild because the +default installation doesn't include MySQL support, a requirement for MythTV. +To enable SQL support, add "mysql" to your USE variable in +<CODE>/etc/make.conf</CODE> and rebuild Qt by running +<BLOCKQUOTE><CODE> +<PRE> +# emerge qt +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>All the necessary files will be downloaded and built. Even on a fast machine +this may take a lot of time if you need to do a full Qt build.</P> + +<H3>Debian.</H3> + +<P>Build-dependencies for MythTV can be satisfied by adding the following to +your <CODE>/etc/apt/sources.list</CODE> +<BLOCKQUOTE><CODE> +<PRE> +# Christian Marillat's packages (mplayer, lame) +deb http://www.debian-multimedia.org sid main +deb-src http://www.debian-multimedia.org sid main +</PRE> +</CODE></BLOCKQUOTE> + +and executing: +<BLOCKQUOTE><CODE> +<PRE> +# apt-get build-dep mythtv +# apt-get source mythtv --compile +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="Setting_up_paths"></A> <A NAME="s4">4.</A> <A HREF="#toc4">System Configuration Requirements for Compiling MythTV. </A></H2> + +<P>Before you compile MythTV from the current source tarball or from +<B>subversion</B>, you may need to modify your system configuration in a +few ways.</P> +<P>In general, if you install MythTV from pre-packaged binaries for your Linux +distribution/version, you don't need to be too concerned about the issues in +this section of the HOWTO - the install script for the packages should take +care of them. However, this section is still recommended reading which may +help if the packager skipped a step in their packaging.</P> + +<H2><A NAME="ss4.1">4.1</A> <A HREF="#toc4.1">Software requirements for compiling MythTV</A> +</H2> + +<H3>General requirements</H3> + +<P>MythTV is written in C++ and requires a fairly complete, but standard, +compilation environment, including a recent g++ compiler, <CODE>make</CODE>, and +appropriate header files for shared libraries. Any standard Linux +distribution should be able to install a suitable compilation environment +from its packaging system. Section 3.2 of this HOWTO provides some details +of how to install the required environment for many distributions.</P> +<P>Subsequent sections of this chapter address the few oddities that you may +have to adjust by hand before you compile MythTV.</P> +<P>The reference compilation system for MythTV is Ubuntu.</P> + +<H2><A NAME="ss4.2">4.2</A> <A HREF="#toc4.2">Shared-Library requirements for MythTV </A> +</H2> + +<H3><A NAME="modifying_ld.so.conf"></A> Modifying /etc/ld.so.conf </H3> + +<P>The runtime manager for shared libraries, <B>/lib/ld.so</B>, gets +information about the locations and contents of shared libraries from +<CODE>/etc/ld.so.cache</CODE>, a file created by <B>ldconfig</B> from +information in <CODE>/etc/ld.so.conf</CODE>. Because MythTV installs some +shared libraries in <CODE>/usr/local/lib</CODE>, that directory needs to be +added to the list of directories for <B>ld.so</B> to search when doing +runtime linking of programs, if it is not already there. +You do this, as root, by editing <CODE>/etc/ld.so.conf</CODE>, then +running <B>ldconfig</B>. There are many ways to do this; one that +works is to enter this series of commands:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ su - +# echo /usr/local/lib >> /etc/ld.so.conf +# /sbin/ldconfig +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H2><A NAME="ss4.3">4.3</A> <A HREF="#toc4.3">Environment variable requirements for MythTV</A> +</H2> + +<H3>General requirements</H3> + +<H3>QT libraries and binaries</H3> + +<P>The compiler needs to be able to locate QT binaries and libraries in +order to compile MythTV. QTDIR needs to be set and the directory holding the +QT binaries needs to be added to your PATH. Your distribution may already +be making these changes as a part of the installation of the software +prerequisites detailed earlier.</P> +<P>One way to do this is as follows: +<A NAME="Checking_that_it_worked"></A> </P> +<P>Open a shell and execute the following: +<BLOCKQUOTE><CODE> +<PRE> +$ echo $PATH +/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/games:/usr/lib/qt3/bin:/home/mythtv/bin:/usr/lib/qt3/bin +$ echo $QTDIR +/usr/lib/qt3 +$ which qmake +/usr/lib/qt3/bin/qmake +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>For Mandriva, you should see a value like <CODE>/usr/lib/qt3</CODE> for +<CODE>QTDIR</CODE> and <CODE>/usr/lib/qt3/bin</CODE> should be in $PATH.</P> +<P>For Gentoo, you should see a value like <CODE>/usr/qt/3</CODE> for <CODE>QTDIR</CODE> +and <CODE>/usr/qt/3/bin</CODE> should be in $PATH.</P> +<P>If you don't, do not proceed past this step until you have resolved this +error. You may need to manually specify the QTDIR and PATH at the shell +prompt before compiling.</P> +<P>Also, check that there has been a link created in +<CODE>/usr/lib/qt3/mkspecs</CODE> (<CODE>/usr/share/qt3/mkspecs</CODE> for Debian) +called <CODE>default</CODE>. If not, you'll get errors during the compile. See +the Troubleshooting Section for more information.</P> +<H3>Distribution-Specific Notes</H3> + +<H3>Mandriva</H3> + +<P>The following instructions work for Mandriva using +<B>bash</B> as the shell, and may be applicable for a distribution which +uses <CODE>/etc/profile.d</CODE>.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Mandriva 10 installs a <CODE>/etc/profile.d/qtdir3.sh</CODE> +file, but it doesn't include the addition of the PATH variable. If you're +running Mandriva 10, don't create a <CODE>mythtv.sh</CODE> file as detailed +below; edit the <CODE>qtdir3.sh</CODE> file and add the PATH statement within +the if / fi block.</CAPTION> +</FIGURE> + +As root, create the following file in <CODE>/etc/profile.d</CODE> The example +filename is "mythtv.sh". Use what you feel is appropriate.</P> +<P>Open a shell, and switch to superuser mode. </P> +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: ^D means press CTRL and d at the same time.</CAPTION> +</FIGURE> + +<BLOCKQUOTE><CODE> +<PRE> +$ su +# cd /etc/profile.d +cat > mythtv.sh +export QTDIR=/usr/lib/qt3 +export PATH=$PATH:/usr/lib/qt3/bin +^D + +# chmod a+x mythtv.sh +# exit +$ exit +</PRE> +</CODE></BLOCKQUOTE> + +The last two commands are to exit out of the shell. This way, when you next +open a shell your new commands +will take effect.</P> + +<H3><A NAME="devperms"></A> Device Permissions </H3> + +<P>MythTV will need access to the video4linux devices on your system. By +default, your distribution may restrict access to these devices to the +logged-in user, so if you will be automatically starting +<B>mythbackend</B> from a script rather than an interactive terminal +session you will need to make some adjustments.</P> +<P><B>NOTE</B>: The following instructions are accurate for Mandriva.</P> +<P>Check for a file called <CODE>/etc/security/console.perms</CODE>. Open the file +in your favorite text editor and look for a line that has: +<BLOCKQUOTE><CODE> +<PRE> +<console> 0600 <v4l> 0600 root.video +</PRE> +</CODE></BLOCKQUOTE> + +and replace it with +<BLOCKQUOTE><CODE> +<PRE> +<console> 0666 <v4l> 0666 root.video +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>What we're doing is allowing read and write access to the files in the +video4linux directory.</P> +<H2><A NAME="DownloadAndCompile"></A> <A NAME="s5">5.</A> <A HREF="#toc5">Downloading and compiling. </A></H2> + +<P>Get MythTV from the +<A HREF="http://www.mythtv.org">http://www.mythtv.org</A> web site. There are two installation methods +you may choose from. The first is to download the latest release in tarball +format and compile. The tarball release of MythTV should work on a wide +variety of systems and should be the preferred method for new users. If you +wish to use the <B>subversion</B> copy of MythTV you may obtain it from +<A HREF="http://svn.mythtv.org">http://svn.mythtv.org</A></P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: If you are going to use <B>subversion</B> to +compile MythTV rather than using the distribution tarball, you <EM>must</EM> +join the +<A HREF="http://www.mythtv.org/mailman/listinfo/mythtv-commits/">http://www.mythtv.org/mailman/listinfo/mythtv-commits/</A> and +<A HREF="http://www.mythtv.org/mailman/listinfo/mythtv-dev/">http://www.mythtv.org/mailman/listinfo/mythtv-dev/</A> mailing lists to +keep up to date with the current status of the code. Code obtained from +subversion has no guarantees regarding stability, etc.</CAPTION> +</FIGURE> +</P> +<P>If you are in North America you will use the Schedules Direct grabber which is +built-in to MythTV. You <EM>do not</EM> need to install XMLTV (so you may +skip XMLTV-related instructions), but you need <B>wget</B> version 1.9.1 +or higher.</P> +<P>Get XMLTV from +<A HREF="http://xmltv.sourceforge.net">http://xmltv.sourceforge.net</A>. Download the latest version (0.5.51).</P> +<P> +<HR> +<PRE> +NOTE for Mandriva users: If you have added a "PLF" mirror, you may skip the +next step and type: + +# urpmi libmp3lame0 libmp3lame0-devel + +After downloading, be sure to install both: +# rpm -Uvh lame* +</PRE> +<HR> +</P> +<P>Get lame from +<A HREF="http://lame.sourceforge.net/">http://lame.sourceforge.net/</A>. Download the source code to v3.96.1 +by following the links from "Using" through "Download...".</P> + +<H2><A NAME="ss5.1">5.1</A> <A HREF="#toc5.1">Building LAME</A> +</H2> + +<P>Open a shell and switch to the directory where you saved lame. +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xzf lame-3.96.1.tar.gz +$ cd lame-3.96.1 +$ ./configure +$ make +$ make test +$ su +# make install +</PRE> +</CODE></BLOCKQUOTE> + +Check that it worked: +<BLOCKQUOTE><CODE> +<PRE> +# ls -l /usr/local/lib +-rw-r--r-- 1 root root 381706 Nov 4 14:22 libmp3lame.a +-rwxr-xr-x 1 root root 674 Nov 4 14:22 libmp3lame.la* +lrwxrwxrwx 1 root root 19 Nov 4 14:22 libmp3lame.so -> +libmp3lame.so.0.0.0* +lrwxrwxrwx 1 root root 19 Nov 4 14:22 libmp3lame.so.0 -> +libmp3lame.so.0.0.0* +-rwxr-xr-x 1 root root 360197 Nov 4 14:22 +libmp3lame.so.0.0.0* + +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss5.2">5.2</A> <A HREF="#toc5.2">XMLTV</A> +</H2> + +<H3>Red Hat Linux and Fedora Core:</H3> + +<P>RPMs for <B>XMLTV</B> and all of its dependencies can be obtained from +<A HREF="http://ATrpms.net/name/xmltv/">http://ATrpms.net/name/xmltv/</A>. The web page has a +list of all the dependent packages you must download and install. +<BLOCKQUOTE><CODE> +<PRE> +# rpm -Uvh xmltv* perl* +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you install from this location you may skip to +<A HREF="#manually_building_mythtv">Manually building MythTV</A>.</P> +<H3>Mandriva</H3> + +<P>RPMs for <B>XMLTV</B> and all of its dependencies are located in +Mandriva's "contrib". If you have added a contrib mirror, try installing +<B>XMLTV</B>: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi xmltv xmltv-grabbers +</PRE> +</CODE></BLOCKQUOTE> + +If this does not work, it is possible that contrib for your Mandriva version +does not have <B>XMLTV</B>, so you may install the XMLTV prerequisites by typing: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi perl-xml-twig perl-xml-writer perl-datemanip perl-libwww-perl +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>and skip straight to the XMLTV compilation step.</P> + +<H3>Manual installation</H3> + +<P> +<A NAME="untarring_xmltv"></A> Untar the xmltv file: +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xjf xmltv-0.5.51.tar.bz2 +</PRE> +</CODE></BLOCKQUOTE> + +Install the xmltv prerequisites. The following prerequisites are the +minimum required; when you actually start running the xmltv setup program it +may alert you to other modules that are required.:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ su +# perl -MCPAN -e shell +cpan> install XML::Twig +cpan> install Date::Manip +Date::Manip is up to date. +cpan> install LWP +cpan> install XML::Writer +cpan> exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Change to the XMLTV directory and compile it: +<BLOCKQUOTE><CODE> +<PRE> +$ cd xmltv-0.5.51 +$ perl Makefile.PL +</PRE> +</CODE></BLOCKQUOTE> + +You can answer "N" to the tv_check, tv_pick_cgi questions. Say "yes" to +the grabber required for your location.</P> +<P>You may get errors about modules not being installed. You will need to +resolve any missing dependencies at this point, or your grabber may not work +correctly. +<BLOCKQUOTE><CODE> +<PRE> +$ make +$ make test +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ConfigureSD"></A> <A NAME="ss5.3">5.3</A> <A HREF="#toc5.3">Configuring the Schedules Direct service </A> +</H2> + +<P>As of 2007-09-01, Tribune Media Services will no longer offer free guide +data. Schedules Direct is a non-profit organization which has licensed the +data to make it available to users of Freeware and Open Source applications.</P> +<P>If you wish to use Schedules Direct, you'll need to establish a user +account. Go to +<A HREF="http://www.schedulesdirect.org">http://www.schedulesdirect.org</A> and click on the "Membership" link. </P> +<P>Once you've read and agreed to the Subscriber Agreement, Terms of Use and +Privacy Policy proceed to the lineup choices and configure your account for +your particular location and the channels that you have. This configuration +will be imported into MythTV when you first run the <B>mythtv-setup</B> +program.</P> + +<P> +<A NAME="manually_building_mythtv"></A> </P> +<H2><A NAME="ss5.4">5.4</A> <A HREF="#toc5.4">Manually building MythTV</A> +</H2> + +<P>If you are going to use <B>subversion</B>, execute the following +instructions to obtain the latest version of MythTV:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ mkdir mythtv +$ svn co http://svn.mythtv.org/svn/trunk/ mythtv +$ cd mythtv +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>To use a release version, you can execute: +<BLOCKQUOTE><CODE> +<PRE> +$ mkdir mythtv-release-0.21 +$ svn co http://svn.mythtv.org/svn/branches/release-0-21-fixes/ mythtv-release-0.21 +$ cd mythtv-release-0.21 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><B>NOTE</B>: Using a svn version of the code allows you to stay +up-to-date with changes. So, if there's an update to the 0.21 release and +you originally obtained it using svn, you could enter the +mythtv-release-0.21 directory and type "svn up", which will update your copy +with the fixed version from the website. You would then recompile and +install the updated 0.21 code.</P> +<P>If you are using the tarball, then unpack it: +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xjf mythtv-0.21.tar.bz2 +$ cd mythtv-0.21 +$ ./configure +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you wish to change options, run <B>./configure --help</B> to +see what is available and to override and automatically detected options. +See the <CODE>config.log</CODE> file after running <B>configure</B> to see +previous runs.</P> +<P>To compile: +<BLOCKQUOTE><CODE> +<PRE> +$ make -j 2 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The MythTV compile can take advantage of multiple CPUs, SMP and +Hyperthreading. If you want to build MythTV on a multi-CPU machine (or with +<B>distcc</B>), specify "-j numjobs", where "numjobs" is greater than 2. +In the above example, we had two concurrent jobs executing, which is +recommended for a single CPU system. Do not set the number of jobs too +high, or your compile will actually take longer to complete than it would if +you did a "normal" build.</P> +<P>If you are using <B>distcc</B>, and you had two other host machines (red, blue) +participating, you would do something like: +<BLOCKQUOTE><CODE> +<PRE> +$ export DISTCC_HOSTS='localhost red blue' +$ make -j 6 CXX=distcc +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The actual speed-up, if any, is dependant on a number of factors, such as +number of CPUs / hosts, etc. The <B>distcc</B> documentation recommends +using a <CODE>-j</CODE> value of twice the number of CPUs available to keep all +of them busy.</P> +<P>Some timing information. The following should only be used for +illustration; your actual results may vary. The test involves a complete +<CODE>make distclean</CODE> to the final binary. +<UL> +<LI>P4 3.2Ghz HT: "standard" make: 12m 49s</LI> +<LI>P4 3.2Ghz HT: make -j 2: 11m 24s </LI> +</UL> +</P> +<P>In the above example, we see that with a single CPU, a multi-stage +<B>make</B> does not significantly decrease compile time.</P> +<P>Once the compile is done, switch to superuser: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: subsequent configuration steps assume that you are within +the MythTV directory that you <CODE>cd</CODE>'d to above.</CAPTION> +</FIGURE> +</P> + +<H3>Enabling real-time scheduling of the display thread.</H3> + +<P>MythTV supports real-time scheduling of the video output thread. There +are three ways to go about enabling this: You can use rlimits, you can use +the realtime security module, or on older systems you can SUID the +executable. Enabling real-time scheduling is optional, but can make the +video display smoother, especially if you are decoding HDTV.</P> + +<H3>rlimits</H3> + +<P>The rlimits method is the preferred method and is included in Linux +2.6.12 and above. Unfortunately, you need PAM version 0.79 or above, which +may not be supported by your distribution yet. Assuming anyone running +<B>mythfrontend</B> is in the audio group and rlimits are supported, all +you need to do is place this in your <CODE>/etc/security/limits.conf</CODE></P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +* - rtprio 0 +* - nice 0 +@audio - rtprio 50 +@audio - nice 0 +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3>realtime module</H3> + +<P>The second option is to use the Linux realtime kernel module. +This is will be phased out over time, but is currently supported +by many distributions that do not yet support rlimits. If you are +not using the distribution kernel you must configure your kernel +with: +<BLOCKQUOTE><CODE> +<PRE> +Security options : [*] Enable different security models +Security options : [M] Default Linux Capabilties +</PRE> +</CODE></BLOCKQUOTE> + +You may also need to install the realtime module, using your distribution's +realtime package. Assuming the users who will be running +<B>mythfrontend</B> will be in the audio group you can get the GUID of a named +group like so: +<BLOCKQUOTE><CODE> +<PRE> +$ grep audio /etc/group +</PRE> +</CODE></BLOCKQUOTE> + +If the number printed out from the grep was 18, you can now load +this module as root before starting <B>mythfrontend</B>: +<BLOCKQUOTE><CODE> +<PRE> +# modprobe realtime gid=18 +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3>run as root option (not safe)</H3> + +<P>The final and least preferred option is to set the sticky bit +on the <B>mythfrontend</B> executable. This <B>opens a security hole</B>, +but is the only option on systems that do not support either +rlimits or the realtime module. This does not work on modern +distributions either, and is <B><EM>not recommended</EM></B> +on any system connected to the Internet. This may also make it +impossible to debug MythTV without running <B>gdb</B> as root. If you +would still like to do this, you just need to run this as root: +<BLOCKQUOTE><CODE> +<PRE> +# chmod a+s /usr/local/bin/mythfrontend /usr/local/bin/mythtv +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3><A NAME="frontend-only"></A> Frontend-only configuration </H3> + +<P>Since MythTV uses a client/server architecture, multiple frontend +computers can simultaneously access content on a Myth system. Live TV, +watching and scheduling recordings, etc. are all possible from multiple +frontends.</P> +<P>To get a better picture of what is needed to run a frontend, note the +following: +<LI>You do NOT need the MySQL server installed on your remote frontend</LI> +<LI>You do NOT need XMLTV installed on your remote frontend</LI> +<LI>You do NOT need to run the mythtv-setup program on +your frontend machine</LI> +</P> +<P>Other than the exclusion of the MySQL server and XMLTV, the MythTV +compilation procedure is the same as when you're setting up both a backend +and a frontend. However, you <EM>will</EM> need to install the database +access libraries.</P> +<P>Once MythTV is compiled and installed: +<LI>Run the mythtv-setup program on your Master backend. Under the "General" +menu, change the IP address of the current machine (by default, "127.0.0.1") +to the real external IP address - 127.0.0.1 is the loopback address and no +external machine can access it. Change the Master Server IP setting to the +same IP address as well.</LI> +<LI>Run the mythfrontend program on your frontend machine, +and a "Database Configuration" screen should appear. +Set the "Host name" field to point to your Master backend's IP address.</LI> +</P> + +<H2><A NAME="Gentoo_build"></A> <A NAME="ss5.5">5.5</A> <A HREF="#toc5.5">Gentoo </A> +</H2> + +<P>Installation of MythTV on Gentoo consists of simply emerging the desired +ebuild because all of the packages are now part of the official Portage tree. +<BLOCKQUOTE><CODE> +<PRE> +$ su - +# emerge --sync # make sure portage is up to date. +# vi /etc/make.conf +</PRE> +</CODE></BLOCKQUOTE> + +Add mysql to your USE variable. i.e. <CODE>USE="mysql ...."</CODE> +<BLOCKQUOTE><CODE> +<PRE> +# emerge mythtv +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H2><A NAME="mysql"></A> <A NAME="s6">6.</A> <A HREF="#toc6">MySQL.</A></H2> + +<P>When you install MySQL 5.x you will also want to comment +out "log-bin" in your <CODE>my.cnf</CODE> configuration file. This option will +quickly fill your "/var" disk partition with many gigabytes of data, +unless you are doing database replication and deleting these files regularly.</P> +<H2><A NAME="ss6.1">6.1</A> <A HREF="#toc6.1">Distribution-specific information</A> +</H2> + +<H3>Mandriva</H3> + +<P>If this is the system maintaining the database, make sure that MySQL is +running and started at boot. Click on Mandriva Control +Center->System->Services, find MySQL and click the "On Boot" button and the +"Start" button if the MySQL status shows that it isn't running yet.</P> +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: There have been reports that MySQL isn't starting at boot. +If this is happening to you, try running the following commands.</CAPTION> +</FIGURE> + +<BLOCKQUOTE><CODE> +<PRE> +$ su +# chkconfig --level 35 mysql on +# /etc/rc.d/init.d/mysql start +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3>Red Hat Linux and Fedora Core</H3> + +<P>If this is the system maintaining the database, make sure that MySQL is +running and started at boot. Click on Redhat menu>Server Settings>Services +and enter the root password when asked. Check "mysqld" and then click Start. +Click Save, then close the window.</P> +<P>This can be done from the command line by typing: +<BLOCKQUOTE><CODE> +<PRE> +# /sbin/chkconfig mysqld on +# /sbin/service mysqld start +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3>Gentoo</H3> + +<P>After installing MySQL you need to initialize the database by running +<B>mysql_install_db</B> as root. </P> +<H2><A NAME="ss6.2">6.2</A> <A HREF="#toc6.2">Setting up the initial database</A> +</H2> + +<P>This step is only required on the system maintaining the database, which +may or may not be one of your MythTV boxes. If the database is on a +non-MythTV machine you'll need to copy the <CODE>database/mc.sql</CODE> file to it.</P> +<P>To setup the initial MySQL databases: +<BLOCKQUOTE><CODE> +<PRE> +$ cd database +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H3>Mandriva and Red Hat Linux/Fedora Core</H3> + +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root < mc.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H3>Debian 3.0</H3> + +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ mysql < mc.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H3>Gentoo</H3> + +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ su +# mysql < /usr/share/mythtv/database/mc.sql +</PRE> +</CODE></BLOCKQUOTE> + +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: It is good practice to set a root password for MySQL. Instructions for doing so can be found on MySQL's web site at +<A HREF="http://www.mysql.com/doc/en/Security.html">http://www.mysql.com/doc/en/Security.html</A>.</CAPTION> +</FIGURE> +</P> +<H3><A NAME="modify_perm_mysql"></A> Modifying access to the MySQL database for multiple systems </H3> + +<P>If you're going to have multiple systems accessing a master database, +you must grant access to the database from remote systems. By default, the +<CODE>mc.sql</CODE> script is only granting access to the local host.</P> +<P>To allow other hosts access to your master database, you can either set it +up for no security at all, or with more granularity. Note that the "%" is +the wildcard character in MySQL.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: The "no security" option is <EM>very</EM> dangerous unless +you're in a controlled environment.</CAPTION> +</FIGURE> + +This example has no security at all, and allows access from any host. +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root mythconverg +mysql> grant all on mythconverg.* to mythtv@"%" identified by "mythtv"; +mysql> flush privileges; +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>For a more secure setup, you can restrict which machines or subnets have +access. If you have a complete DNS system operational, you could do the +following: +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root mythconverg +mysql> grant all on mythconverg.* to mythtv@"%.mydomain.com" identified by "mythtv"; +mysql> flush privileges; +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Finally, if you just want to restrict by IP subnet (in this example, the +192.168.1. network): +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root mythconverg +mysql> grant all on mythconverg.* to mythtv@"192.168.1.%" identified by "mythtv"; +mysql> flush privileges; +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>You'll also need to check that the "networking" feature of MySQL is turned +on. Check that <CODE>/etc/mysql/my.cnf</CODE> <EM>does not</EM> contain +<CODE>skip-networking</CODE>. If it does, remove it. Also verify that +<CODE>bind-address</CODE> is set to your IP address instead of +<CODE>127.0.0.1</CODE>. If you change either of these items, restart +<B>MySQL</B>.</P> +<P><B>NOTE</B>: Your distribution may have a customized MySQL configuration +file; in Mandriva, check <CODE>/etc/sysconfig/mysqld</CODE> for additional +configuration.</P> + +<H2><A NAME="s7">7.</A> <A HREF="#toc7">Configuring Sound.</A></H2> + +<P>If your video doesn't appear to be in-sync with your audio and you're +using an analog video capture card and a soundcard to capture audio, it +could be because you are listening to the real-time audio from your video +card rather than after it's been processed and synchronized to the video by +MythTV. Because MythTV is a personal video recorder, "Live TV" isn't really +live - to let you pause live TV, MythTV is actually encoding the video, +saving to disk, and then playing it back. This procedure puts your MythTV +"live" TV about 2 seconds behind real-time, so it's important that you're +not listening to the live audio. However, if you're having an issue where +the audio and video aren't synchronized by small but varying amount, it's +most likely because the sound driver that you're using doesn't have the +DSP_CAP_REALTIME capability. This was the case with ALSA (0.5), but not +with newer versions. See the +<A HREF="#Troubleshooting_Audio">Troubleshooting Audio</A> section for more information if you're having +issues with sound. Also, ensure that no other programs are grabbing the +audio output, like <B>arts</B> or <B>esd</B>.</P> +<P>What you need to do is to mute the "line-in" of your sound card and also +set it as the recording source.</P> +<P>There are two ways to do this. Graphically, and from the command line.</P> + +<H2><A NAME="ss7.1">7.1</A> <A HREF="#toc7.1">Graphically setting up the mixer</A> +</H2> + +<H3>Mandriva and Red Hat Linux/Fedora Core</H3> + +<P>Open Kmix by clicking K->Multimedia->Sound->Kmix for Mandriva, or +<PRE> +RedHat Menu>Sound & Video>Volume Control +</PRE> + on Red Hat/Fedora.</P> +<P>Click on Settings->Configure Make sure that "Tick Marks" and "Show +labels" have "X"'s in them. This will make it easier to find the correct +audio source. Click OK.</P> +<P>On the mixer page, look for Line-In on your sound card. You should see +two LED's - a green one at the top, and a red one at the bottom. The green +one at the top is for muting; you want to make sure that the green LED is a +dark green, meaning that it's "off". You also want to click on the red LED +so that it turns bright red, indicating that it's "ON"; this insures that +the Line-in is used as the source. Click OK, and make sure that you save +the settings so that this is your default.</P> + +<H3>Using ALSA.</H3> + +<P>To use ALSA, you'll need to correctly setup your +<CODE>asoundrc</CODE> file. Configuring this file is beyond the scope of this +HOWTO. Once ALSA is working correctly, change the output sound device in +mythfrontend->setup->Audio from <CODE>/dev/dsp</CODE> to <CODE>ALSA:default</CODE>. +This field may be edited to suit your ALSA requirements.</P> + +<H2><A NAME="ss7.2">7.2</A> <A HREF="#toc7.2">Setting the mixer from the command line</A> +</H2> + +<P>If you have installed the alsa-utils package, then the <B>amixer</B> +program can be used to setup the mixer. The "Master" volume setting is only +required on a frontend machine to ensure that the sound channels are unmuted +and configured for outputting sound. The "Line" and "Capture" controls are +required for your sound card to actually capture audio from the external +Line-in if it's connected to an analog frame grabber. Not all sound cards +have a "Capture" control, but if yours does and you don't set it then MythTV +will not capture audio.</P> +<P> +<HR> +<PRE> +Note the spelling in the following commands. +</PRE> +<HR> + +<BLOCKQUOTE><CODE> +<PRE> +$ amixer set Master,0 100%,100% unmute +$ amixer set PCM,0 100%,100% unmute +$ amixer set Line,0 75%,75% mute captur +$ amixer set Capture,0 100%,100% captur +$ su +# alsactl store +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you have multiple sound cards, then use the <CODE>-c</CODE> parameter to +specify which card to adjust. Note that the first card will be "0", the +second will be "1", etc.</P> +<P>That takes care of setting the volume correctly, and the ALSA startup script +will restore the volume after a reboot. If you find that your sound is +distorted, it's possible that the levels in the above examples are too high +for your particular hardware combination. Try reducing the percentages by +5-10% and checking again. Once you're satisfied, re-run the <CODE>alsactl +store</CODE> command.</P> +<P>You may also use the <B>alsamixer</B> program to set the volume. If you +are using an ALSA version after 1.0.6, use <B>alsamixer -V all</B> First, +start <B>alsamixer</B> from the command line. You should start out on the +"Master" volume control slider. Use the up and down cursor to set the +master volume to around 75%. Next, use the left and right cursor keys to +move around on the screen until you find the "Line" slider. Press SPACE to +set it as the capture source, set the level to around 50-75% and press "M" +to mute it. You can now press ESC to exit out of the <B>alsamixer</B> +program. You can also have MythTV manage all volume and mute settings, but +this will only affect the "Master" or PCM volume, not the capture volume. See +the mythfrontend setup page for options.</P> +<P>Finally, if you've performed all of the above steps, and you still don't seem to have any sound, it's possible that your video capture device is muting the audio output. +<BLOCKQUOTE><CODE> +<PRE> +$ v4lctl -c /dev/video0 setattr mute off +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="s8">8.</A> <A HREF="#toc8">Setting up a remote control.</A></H2> + +<P>MythTV does not have native remote control receiver and decoder software +built-in. Instead, remote control functions are implemented by cooperating +with <B>lirc</B>, the Linux Infrared Remote Control program. <B>lirc</B> +handles the IR hardware and passes keystrokes to MythTV, which then acts as +if the user had pressed the keys on the keyboard. The file +<CODE>keys.txt</CODE> describes the keys used to control MythTV.</P> +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: If you are running Mandriva, you may install +<B>lirc</B> by executing: <CODE># urpmi lirc lirc-remotes</CODE> and bypass +the manual compilation steps described below by jumping to the +<A HREF="#completing_lirc_install">Completing the lirc install</A> section. See the contrib/mandrake91.etc.sysconfig.lircd file for an example of how to +configure lircd.</CAPTION> +</FIGURE> +</P> +<P>Some IR devices require a kernel recompile, and some don't. However, all at +least require having the kernel source available as a resource for the lirc +build process. </P> + +<H2><A NAME="ss8.1">8.1</A> <A HREF="#toc8.1">Gentoo</A> +</H2> + +<P>To install lirc on Gentoo, all you need to do is: +<BLOCKQUOTE><CODE> +<PRE> +# emerge lirc +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss8.2">8.2</A> <A HREF="#toc8.2">Obtaining and compiling lirc</A> +</H2> + +<P>You're going to need to download and compile <B>lircd</B>. Go to +<A HREF="http://www.lirc.org">http://www.lirc.org</A> and download lirc; as +of 2006-01-21, the version available is 0.8.0. Grab the remotes.tar.bz2 file as +well. +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xjf lirc-0.8.0.tar.bz2 +$ cd lirc-0.8.0 +$ ./setup.sh +</PRE> +</CODE></BLOCKQUOTE> + +You're going to need to know what sort of receiver you have and where it's +connected. In the case of the Pinnacle Studio TV card, with the IR receiver +connected to COM1 (/dev/ttys0), once the configuration menu comes up, +perform the configuration by going to Driver Configuration->Other Serial +Port Devices->Pinnacle Systems Receiver->OK and on the next page select +COM1->OK.</P> +<P>Each remote is different; some remote receivers connect directly to your +capture card and not to a serial port, so make sure that you've got the +correct one.</P> +<P>You then click "Save Configuration and run configure" to continue.</P> +<P>Make sure you read the last text generated by the configure step. It will +tell you if you require a kernel recompile, and what the name of your kernel +module will be (if necessary). For instance a home-built receiver may +require a kernel recompile, so you would be notified that you will have to +load the lirc_serial module. If you did not get any such messages skip the +kernel recompile steps below and go directly to making and installing the +lirc driver.</P> +<P>Once the configuration step is complete: +<BLOCKQUOTE><CODE> +<PRE> +$ make +$ su +# make install +# chmod 666 /dev/lircd +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>At this point, if you're using a serial receiver, check that there's a +<CODE>lirc</CODE> device in <CODE>/dev</CODE>: +<BLOCKQUOTE><CODE> +<PRE> +$ ls -l /dev/li* +lr-xr-xr-x 1 root root 5 Jan 27 09:00 /dev/lirc -> ttyS0 +srw-rw-rw- 1 root root 0 Jan 27 15:01 /dev/lircd= +prw-r--r-- 1 root root 0 Jan 27 09:00 /dev/lircm| +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>As you can see, there's a link from /dev/lirc to ttyS0, a.k.a. "COM1", which is +appropriate for the Pinnacle Systems PCTV Pro. However, you may notice +something like this: +<BLOCKQUOTE><CODE> +<PRE> +crw------- 1 root root 61, 0 Dec 31 1969 lirc +</PRE> +</CODE></BLOCKQUOTE> + +Some IR receivers (including some homebrew units) use a character device as +their data interface as opposed to a link to a serial port. If the <CODE>make +install</CODE> step has created a character device for you, don't replace it +with a link to a COM port.</P> +<P>So, if the link or character device was not created (but should have been), +ensure that you ran the <CODE>make install</CODE> step as root. If it still +doesn't work, then there are three options. The first option is to re-read +the <B>lirc</B> documentation to determine whether your IR receiver is a +character device or should be a link to a serial port and to create the +link/character device manually. In this example, the IR device is connected +to ttyS0. If it were connected to "COM2", then use ttyS1, etc. +<BLOCKQUOTE><CODE> +<PRE> +$ su +# cd /dev +# ln -sf ttyS0 lirc +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: The above example assumes that your receiver uses the +standard serial driver. Some receivers do not, including receivers that +plug into a TV capture card. Check the lirc documentation, but it may be +necessary to replace the link created above with a character pipe:</CAPTION> +</FIGURE> + +<BLOCKQUOTE><CODE> +<PRE> +# mknod /dev/lirc c 61 0 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>See the lirc documentation for additional information. The lirc +installation <EM>should</EM> create this for you, so manually creating it +indicates that your lirc installation may have other issues.</P> +<P>The second option is to post your issue to the <EM>lirc</EM> list, not the +mythtv-users list. The lirc programmers will be the ones that can assist +you best.</P> +<P>The third option is to dispense with lirc altogether by purchasing an IR +keyboard (various options exist, although Chicony appears to work for some +people) and a learning remote control. The IR keyboard receiver plugs into +the PS/2 keyboard port on your PC and you would train your learning remote +to emulate the various keystrokes from <CODE>keys.txt</CODE> of your IR +keyboard. Using this method removes lirc entirely from the picture - your +remote will be sending keypresses that your PC "sees" on the keyboard port.</P> + +<H2><A NAME="completing_lirc_install"></A> <A NAME="ss8.3">8.3</A> <A HREF="#toc8.3">Completing the lirc install </A> +</H2> + +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE to Mandriva 9.1 users</B>: skip to the manual start paragraph +below.</CAPTION> +</FIGURE> +</P> +<P>If the lirc configure program / compile did not mention anything about a +kernel module, then you are finished. If it did mention a kernel module, you +must edit the <CODE>/etc/modules.conf</CODE> file. Add this line as the first +thing in the file. It must come first, or it may not work. +<BLOCKQUOTE><CODE> +<PRE> +alias char-major-61 XXX +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>replace XXX with the name which you determined earlier, which in this +example was "lirc_serial" +<BLOCKQUOTE><CODE> +<PRE> +$ su +# modprobe lirc_serial +# /sbin/ldconfig +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Next, we're going to manually start lircd the first time. Mandriva 9.1 +users, type: <CODE># /etc/rc.d/init.d/lircd start</CODE> instead of: +<BLOCKQUOTE><CODE> +<PRE> +# /usr/local/sbin/lircd +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><B>NOTE</B>: Read this next section if you're not familiar with how lirc works!</P> +<P>There are two separate files used by lirc, and both are required for your +remote control to do anything useful. First is the <CODE>lircd.conf</CODE> file. +<CODE>lircd.conf</CODE> tells the lirc daemon how to interpret the IR pulses +that it receives from a remote control and what name to assign to each +sequence of pulses. Without getting too involved, a particular series of +pulses may correlate to "Channel Up". The <CODE>lircd.conf</CODE> file will +then contain a line that looks something like this:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> + ChannelUp 0x0000000000001020 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The <CODE>lircd.conf</CODE> file can have multiple remote controls defined.</P> +<P>The second file is <CODE>lircrc</CODE>, which takes the name of the button which +was pressed ("ChannelUp") in the above example, and correlates that to an +action to be performed by a program using the remote control. So in MythTV, +ChannelUp means one thing, while in <B>mplayer</B> it means something +different. <CODE>lircrc</CODE> gives you the flexibility of taking the name of +the button and having it perform different actions depending on which +program you're using at the time.</P> +<P><B>NOTE</B>: The definitions in <CODE>lircd.conf</CODE> come from the user +community, and there is no standard for the common button names. One +<CODE>lircd.conf</CODE> file may contain a definition for a button called +"ChannelUp", while another may contain a definition for "Chan+". Your +<CODE>lircrc</CODE> file must therefore be configured appropriately, or it won't +work.</P> +<P>If this fails, complaining of a missing <CODE>lircd.conf</CODE> file, then you +must find or make one. First look for a pre-made configuration file at +<A HREF="http://lirc.sourceforge.net/remotes/">http://lirc.sourceforge.net/remotes/</A>. Mandriva 9.1 users, look in +<CODE>/usr/share/lirc-remotes</CODE>. If you find one your remotes either on the +website or in <CODE>/usr/share</CODE>, download or copy the file, name it +<CODE>lircd.conf</CODE> and put it in your <CODE>/etc</CODE> directory. If you +couldn't find your remote, you must make your own <CODE>lircd.conf</CODE> file.</P> +<P>To make your own <CODE>lircd.conf</CODE> file +<BLOCKQUOTE><CODE> +<PRE> +$ irrecord myremote +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Follow the on-screen directions to train your remote and define keys. If +your remote ends up working well, you should consider submitting your +<CODE>lircd.conf</CODE> file back to the lirc developers. Once finished: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# cp myremote /etc/lircd.conf +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>now try to start lircd again: +<BLOCKQUOTE><CODE> +<PRE> +# /usr/local/sbin/lircd +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Now, we're going to add the commands necessary for lircd to run each time we +boot. Mandriva 9.1 users, you can execute: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# chkconfig --level 35 lircd on +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>All other distributions: +<BLOCKQUOTE><CODE> +<PRE> +# cd /etc/rc.d +# cat >> rc.local +echo "Starting lircd" +/usr/local/sbin/lircd +^D +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> + </P> +<P>This takes care of the lircd portion, which "listens" for the IR signals. If +everything went well, the install script for lircd put an appropriate +configuration file for your remote into <CODE>/etc/lircd.conf</CODE> This file +maps the buttons on the remote control to the IR pulses coming from the +receiver.</P> +<P>The next step is to convert those signals into something that can be used +to control MythTV. MythTV now includes native support for lirc and can +interact directly with </P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythtv-0.21/contrib/configfiles +$ cp lircrc.example ~/.lircrc +</PRE> +</CODE></BLOCKQUOTE> + +or +<BLOCKQUOTE><CODE> +<PRE> +$ cp lircrc.example.pinnaclestudiopctv ~/.lircrc +</PRE> +</CODE></BLOCKQUOTE> + +if you've got a Pinnacle Studio PCTV remote. +<BLOCKQUOTE><CODE> +<PRE> +$ irw +</PRE> +</CODE></BLOCKQUOTE> + +Start pressing the keys on your remote; <B>irw</B> will +print the name of the button as it is defined in your +<CODE>/etc/lircd.conf</CODE>. If you don't see anything at this point, you need +to troubleshoot further by going back to the lirc home page and investigating +from there.</P> +<P>If it is working, then press <B>CTRL-C</B> to abort the program. Once you +know that your remote is working, you can either recompile MythTV with +native lirc support by enabling it in <B>configure</B> or you +need to run the <B>irxevent</B> program, which takes the key presses and +sends them to MythTV. If you use native lirc support, you don't need to run +<B>irxevent</B>. If you are going to use irxevent, then you need to run +it like this: +<BLOCKQUOTE><CODE> +<PRE> +$ irxevent & +</PRE> +</CODE></BLOCKQUOTE> + +If <B>irxevent</B> isn't running, then MythTV will not respond to your remote +control unless you're using native lirc support.</P> + +<H2><A NAME="ss8.4">8.4</A> <A HREF="#toc8.4">Additional information for lirc</A> +</H2> + +<P>Take a look at the lircrc.example files in the <CODE>contrib/configfiles/</CODE> +directory. In my case, (Pinnacle Studio card) the channel up and down functions +weren't working, due to the fact that the button names were different than +the default <CODE>lircrc.example</CODE> file that came with MythTV.</P> +<P>The <CODE>lircrc.example</CODE> file has this: +<BLOCKQUOTE><CODE> +<PRE> +begin + prog = irxevent + button = ChannelUp + config = Key Up CurrentWindow +end + +begin + prog = irxevent + button = ChannelDown + config = Key Down CurrentWindow +end +</PRE> +</CODE></BLOCKQUOTE> + +but the <CODE>/etc/lircd.conf</CODE> that comes in the lircd package +defines the buttons for the Pinnacle Studio PCTV as: +<BLOCKQUOTE><CODE> +<PRE> + channel+ 0x0000000000000017 + channel- 0x000000000000001C +</PRE> +</CODE></BLOCKQUOTE> + +rather than "ChannelUp" and "ChannelDown". I added the +following to my /home/[yourusername]/.lircrc file: +<BLOCKQUOTE><CODE> +<PRE> +begin + prog = irxevent + button = channel+ + repeat = 3 + config = Key Up CurrentWindow +end + +begin + prog = irxevent + button = channel- + repeat = 3 + config = Key Down CurrentWindow +end +</PRE> +</CODE></BLOCKQUOTE> + +which took care of basic functionality. Because the PCTV Studio remote +has additional buttons, look at the +<CODE>contrib/configfiles/lircrc.example.pinnaclestudiopctv</CODE> for an example of how +to define additional buttons, and how to debug potential button name +conflicts between the <CODE>lircrc.example</CODE> file and how <B>your</B> +remote defines the button names.</P> +<P>By examining the button names defined in <CODE>/etc/lircd.conf</CODE> and using +the <B>irw</B> program to make sure that your remote is working, you can +create the appropriate mappings in <CODE>.lircrc</CODE> to get excellent remote +functionality with MythTV.</P> +<P>Note the <B>repeat =</B> parameter. This informs the <CODE>irxevent</CODE> +program to pass through every third keypress. By default, <CODE>lirc</CODE> +will only send one keypress to the application, even if you're holding down +the key. The actual <B>repeat =</B> number will vary from system to +system, so experiment and see which value works best for you.</P> + +<H2><A NAME="ss8.5">8.5</A> <A HREF="#toc8.5">Configuring lirc for use with an IR blaster</A> +</H2> + +<P>Lirc has support for various IR transmitters. A popular model is the Actisys +IR-200L +<A HREF="http://store.snapstreamstore.com/accessories.html">http://store.snapstreamstore.com/accessories.html</A>. It was +originally designed for IRDA communication, but can be used to transmit A/V remote +control codes. By using the lirc SIR driver, this device can easily be +integrated with MythTV. I have tested this device with an AT&T DCT2000 +digital cable box but the instructions can be used to configure other IRDA +devices and A/V remotes.</P> +<P>Follow the steps in the previous section. When you run setup.sh, select +option 1, driver configuration. From here select option 6, IrDA hardware. +Select your appropriate device and the corresponding serial port, then Save +configuration & run configure from the main menu. Once configure is done +type: +<BLOCKQUOTE><CODE> +<PRE> +$ make +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Please note: unlike the Pinnacle receiver above you will be compiling lircd +in addition to a kernel module for the SIR transmitter. Depending on whether +you have your serial port driver configured as a kernel module you might see +the following message during make: +<BLOCKQUOTE><CODE> +<PRE> +lirc_sir.c:56:2: warning: #warning +"******************************************" + +lirc_sir.c:57:2: warning: #warning "Your serial port driver is compiled into " + +lirc_sir.c:58:2: warning: #warning "the kernel. You will have to release the " + +lirc_sir.c:59:2: warning: #warning "port you want to use for LIRC with:" + +lirc_sir.c:60:2: warning: #warning "setserial /dev/ttySx uart none" + +lirc_sir.c:61:2: warning: #warning +"******************************************" +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you do receive this statement make sure to run the <B>setserial</B> command +before you load the lirc_sir module. Follow this with the install: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# make install +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>You will notice that lirc installs the kernel module in +<CODE>/lib/modules/uname -a/misc</CODE>. </P> +<P>The configuration for starting <B>lircd</B> differs if you're going to be +sending and receiving IR versus just receiving. +<BLOCKQUOTE><CODE> +<PRE> + +# cd /etc/rc.d +# cat >> rc.local +echo "Starting lircd" +setserial /dev/ttySx uart none # (if required) +modprobe lirc_sir +/usr/local/sbin/lircd +^D +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>At this point you have to populate the <CODE>/etc/lircd.conf</CODE> file with the proper +codes for your A/V remote. You should be able to find your remote within the +lirc remote tar file located at +<A HREF="http://www.lirc.org/remotes.tar.bz2">http://www.lirc.org/remotes.tar.bz2</A>. In my case I +extracted the file from remotes/motorola/DCT2000 (gi-motorola-dct2000)</P> +<P>To test the lirc_sir module you can run <B>irw</B> to verify the codes are being +received. If everything is configured correctly +you should see something similar to the following: +<BLOCKQUOTE><CODE> +<PRE> +$ irw +0000000000007ff0 00 1 gi-motorola-dct2000 +000000000000bff8 00 2 gi-motorola-dct2000 +000000000000f7f0 00 ENTER gi-motorola-dct2000 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Once you've verified lirc is working you can press <B>CTRL-C</B> to exit +<B>irw</B> and configure the channel changing script.</P> +<P>The path to the channel changing script will need to be entered on the +mythtv-setup screen for Input Connections.</P> +<P>This csh script will be called each time MythTV needs to change the channel. +Below is a copy of the script followed by the corresponding perl script. +Make sure both are in your path. Also make sure you leave the #!/bin/csh +setting and not change it to Bourne or bash. This will create a frustrating +symptom to diagnose where MythTV cannot open /dev/device. Unlike Bourne or +bash, csh scripts automatically close parent file descriptors before they +start. +<BLOCKQUOTE><CODE> +<PRE> +$ cd /usr/local/bin +# su +# cat > change_channel.csh +#!/bin/csh +echo "changing to $1" +/usr/local/bin/channel.pl $1 & +^D +# chmod a+x change_channel.csh +# exit +$ exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>See <CODE>contrib/channel.pl</CODE> for the actual file. Copy it to +<CODE>/usr/local/bin/</CODE></P> +<P>The last statement within the perl script is the lirc rc command. This is +the command that transmits the code to your cable/DSS box. Make sure to have +the IRDA device within a few feet of the box.</P> + +<H2><A NAME="Configuring_mythtv"></A> <A NAME="s9">9.</A> <A HREF="#toc9">Configuring MythTV. </A></H2> + +<P>By this point, all of the compile-time prerequisites have been installed, +<B>mysql</B> is running and has had its initial database setup. It's now +time to configure MythTV. +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: If you're running Debian unstable and you have compiled +MythTV from source, you will need to install an additional package before +you will be able to run MythTV. Execute the following to install the MySQL +driver for QT.</CAPTION> +</FIGURE> + +<BLOCKQUOTE><CODE> +<PRE> +$ su - +# apt-get install libqt3c102-mt-mysql +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H2><A NAME="ss9.1">9.1</A> <A HREF="#toc9.1">Configuring the Master backend system</A> +</H2> + +<P>Open a shell and decide where you will store your video files. This may +be one directory or multiple directories on the same or different +filesystems. There is no default directory used for new recordings, you +<B>must</B> create at least one storage directory and configure Myth to +use it by running <B>mythtv-setup</B>. If you do not do this, then MythTV +will be unable to record anything. The following example is specific for +<CODE>/var/video</CODE>, but the same instructions would apply for any directory +name you choose to use. See the +<A HREF="#advancedpartitionformatting">Advanced Partition Formatting</A> section for hints on creating a +partition for MythTV.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ su +# mkdir /var/video +# chmod a+rwx /var/video +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><B>NOTE</B>: The last slash "/" is not required.</P> +<P> +<A NAME="storagegrouptip"></A> +<B>TIP</B>: Try not to have your video mount point on the same partition +as your root partition, which could lead to the filling up of your root +partition with video data if the mount fails. For example:</P> +<P>If <CODE>/var/video</CODE> is created on your root partition and you then +perform a mount of another drive to this directory there won't be any +problems if everything is working the way it should. However, if the mount +fails for some reason, <CODE>/var/video</CODE> still exists, so MythTV will find +the directory and write files to it. If your <CODE>/</CODE> mount point is +space limited, <CODE>/var/video</CODE> will <B>also</B> be space limited, and +it won't take long to fill the partition. This will cause a number of +side-effects, most of them bad. Instead, create subdirectories as the +destination for the storage group.</P> +<P>Your directory structure could then look something like this: +<BLOCKQUOTE><CODE> +<PRE> +/mnt/video/drive1/video +/mnt/video/drive2/video +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Your <CODE>/etc/fstab</CODE> would look like this: +<BLOCKQUOTE><CODE> +<PRE> +/dev/hdb1 /mnt/video/drive1 +/dev/hdc1 /mnt/video/drive2 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Because the Storage Group path is <CODE>/mnt/video/drive1/video</CODE>, if the +mythbackend can only find <CODE>/mnt/video/drive1</CODE> it will <EM>not</EM> +write files to that share.</P> +<P>After you create the desired directory or directories for storing your video +files, you will need to add them to the proper Storage Group using +<B>mythtv-setup</B>. This procedure is described below in the +<A HREF="#storagegroups">Storage Groups</A> section.</P> +<P>The first thing to configure is the Master backend system. If you are +running multiple backend systems, the Master backend will make all +decisions about which programs will be recorded on which tuners. If you +have only one backend, then it will be its own master.</P> +<P>The Master backend will always choose the first available tuner in the same +order as you add cards through "mythtv-setup". In other words, the second +card you add will only be used when there are two overlapping recordings, +the third when there are three, and so on. + Therefore, you will want to have +the greatest amount of disk space on the Master backend because its tuner +will always be the first choice. You will then want to add your +<A HREF="#nonmaster_backend">other backends</A> in the order of your +preference for recording.</P> +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: It is possible to <EM>not</EM> have the cards on the Master +backend be the first ones used. However, if you are new to MythTV it is +easier to configure the Master backend first before moving on to the Slaves, +at least until you become more familiar with the MythTV system. See +<A HREF="#advanced_backend_config">Advanced Backend Configurations</A> for +information on configuring multiple backend systems in various ways.</CAPTION> +</FIGURE> +</P> +<P>Because MythTV uses a database to store all configuration variables, +part of the bootstrap of MythTV is to indicate the location of the MySQL +database server. If the frontend, backend and MySQL database server are all +going to be running on the same box, you can continue to the next step. If +not, you'll need to change the Host Name in the "Database Configuration" +screen of the mythfrontend program.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Users that have been running the frontend and the backend on +different machines have stated that they have been having issues with remote +access to the MySQL database. The following instructions may or may not +work. Add the following to <CODE>/etc/my.cnf</CODE> on the backend machine and +restart MySQL.</CAPTION> +</FIGURE> + +<BLOCKQUOTE><CODE> +<PRE> +skip-innodb +set-variable=thread_stack=256k +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Run the setup program: +<BLOCKQUOTE><CODE> +<PRE> +$ mythtv-setup +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The backend setup program will start and offer you a number of choices. It +is <EM>strongly</EM> recommended that you go through them in order.</P> +<P>The first question will ask if you wish to clear out your existing +configurations for your capture cards. Initially, you should say "YES" so +that there are no surprises later.</P> +<P>The next question will ask you if you wish to clear out your video source +information. You should answer "YES" to this as well.</P> +<P>Once the graphical setup starts, you'll see that there are six choices</P> +<P> +<FIGURE> +<EPS FILE="add.eps"> +<IMG SRC="add.png"> +<CAPTION>The Storage Directories feature is available only in the SVN version of MythTV.</CAPTION> +</FIGURE> +</P> +<P> +<OL> +<LI>General</LI> +<LI>Capture Cards</LI> +<LI>Video Sources</LI> +<LI>Input connections</LI> +<LI>Channel Editor</LI> +<LI>Storage Directories</LI> +</OL> +</P> +<P>Use the arrow keys to move around, and press the space bar to select which +option you wish to configure.</P> + +<H3>General</H3> + +<P>The first screen of the General configuration deals with IP addresses of the +system that you're running mythtv-setup on and any master backend you may have. +If you've only got one machine, then the default values are fine and you can +move to the next page by pressing the space bar. If you need to move around +the screen, use the arrow keys to move focus between settings, not the +mouse.</P> +<P>If you will be deploying multiple backends, or if your backend is on one +system and you're running the frontend on another machine then <EM>do +not</EM> use the "127.0.0.1" IP address.</P> +<P><B>NOTE</B>: 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.</P> +<P>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)</P> +<P>Once you're satisfied with the values, move the focus down to Next and hit +the space bar.</P> +<P>The next screen details the Host-specific Backend setup. This is where you +will set the specific directory paths for this particular backend. Make +sure that you've followed the steps at the beginning of this section and +created a directory that exists and that MythTV will have write privileges +to. When you're done, press Next to continue, taking you to the Global +Backend Setup.</P> +<P>On the Global Backend Setup configure your backend with the appropriate +settings. Use the left and right arrow keys to iterate through the choices +available on each setting, and the up and down keys to move between +settings. Move to Finish when you're done and press the space bar, taking +you back to the main configuration screen.</P> + +<H3>Capture Cards</H3> + +<P>You should have no capture cards defined, so the highlight will be on +(New Capture Card). Press space to begin.</P> +<P>Choose the appropriate settings for your particular tuner. Use the arrow +keys to move around and to make your choices, and press RETURN when +complete. Pressing RETURN will take you back to the Capture Cards screen; +if you have additional capture cards in this machine, press the space bar +when the highlight is on the (New Capture Card) row to define another card. </P> +<P>If you have made a mistake, you can delete a card by highlighting it and +pressing the 'D' key, or you can highlight it and press the RETURN or 'E' +key to edit it.</P> +<P>Once you have no additional cards to setup, press ESC.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: If you have a dual digital/analog card, such as the pcHDTV +cards and some DViCO cards, then you should not configure this as two +separate cards. Configure the digital portion as a DVB card, then click +on the "Analog Options" button within the DVB configuration panel for +the card and configure the analog portion of the card there.</CAPTION> +</FIGURE> +</P> + +<H3><A NAME="VideoSources"></A> Video Sources </H3> + +<P>When you start, the highlight should be on (New Video Source). Press the +space bar to begin. The first field asks for the name of the video source. +You may choose something easy to remember, like "Antenna" or "Cable". Once +you've chosen a name, press the down arrow to move to the next field. </P> +<P>If you're in North America, change the grabber to +"SchedulesDirect.org(Internal)", then continue pressing the down arrow to +move to the next field. Fill in the username (lowercase only) and password +that you have established with Schedules Direct, then move to the "Retrieve +Listings" button and press the space bar.</P> +<P><B>NOTE</B>: You need <B>wget</B> version 1.9.1 or higher to use +Schedules Direct.</P> +<P>The mythtv-setup program will contact the Schedules Direct servers and get +your account information. Once you're done, you may click the Finish button +and skip the next few paragraphs in this document since they only apply to +users that are using the external XMLTV script to get their guide data.</P> +<P>If you wish to continue using the XMLTV grabber, then move to the Zip/postal +code field and put in the appropriate value.</P> +<P>If you're outside of North America, then some manual interaction will be +required with XMLTV. You may need to switch from the MythTV setup program +to the console it was run on to interact with XMLTV.</P> +<P>Once you have chosen your provider, press RETURN to continue. XMLTV will +now begin collecting the initial data for your location. The screen may +blank for a few seconds to several minutes, depending on the load of the +listings provider and the speed of your connection to the Internet. Be +patient!</P> +<P>You will then be returned to the Video Sources screen. If you have multiple +video sources available, such as Antenna, Cable, etc, go ahead and define +them all, even if they're not all going to be physically connected to the +master backend server. Once you're done, press ESC to return to the main +screen.</P> + +<H3>Input Connections</H3> + +<P>The final configuration item is Input Connections. On this screen, you +will associate the various video sources you defined earlier with a physical +input to a encoder card. It's entirely possible that you have multiple +tuners, and each tuner has a different input, so on this screen you let +MythTV know which device will connect to which input source.</P> +<P>When you start this screen, you should see a listing of the various input +connections available on each of the Capture cards you defined earlier. For +example, you may have a capture card with a tuner, a SVideo and a Composite +connection. If you wanted to associate the tuner (a.k.a., "Television") +with an "Antenna" source you defined in Video Sources, you would move to the +<CODE>/dev/videodevice (Television) -> </CODE> line and press the space bar. +Using the left and right arrow keys will show you the various choices you +have already created for video source. In our case, you would use the +left/right cursor keys until "Antenna" was shown in the Video Source field. +Press down to move to the next setting.</P> +<P>On the connection pane there is a "Scan for channels" button, if you are +configuring a digital source such as a DVB card, you need scan for channels +and you must do this before pressing the "Fetch channels from listings +source" button. You may scan for analog channels on an analog input, but +this is not needed.</P> + +<P>The other button is called "Fetch channels from listings source". As long as +you have a real listings source you should fetch channels from them for +analog channels. You can do this for digital sources as well (unless the +listing source is transmitted EIT data). If you are using XMLTV, you may need +to switch from the MythTV setup program to the console it was run on to +interact with XMLTV after pressing this button. It is possible to fetch the +channels on the command line using mythfilldatabase. But if you need to do +this, you will probably need to re-enter the MythTV setup program to +configure the "Starting channel" setting for this source->input connection.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: If you have a Hauppauge PVR-500, you must think of +it has two PVR-150's on a single PCI card. For example, if you have a +single PVR-500 card, it will appear as <CODE>/dev/video0</CODE> and +<CODE>/dev/video1</CODE>. Each <CODE>/dev/video</CODE> device will have a Tuner input.</CAPTION> +</FIGURE> + +Once you're done, press RETURN to go back to the Input Connections screen. +You would then finish associating the video sources to any other hardware +devices you have available.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Don't add a video source to a hardware input if you don't +actually have anything connected there. For example, adding "Cable" to the +Tuner and to the Composite inputs without having something connected to +Composite will lead to blank recordings.</CAPTION> +</FIGURE> +</P> +<P>Press ESC to return to the main menu, and press ESC again if you have no +further items to configure, thereby returning you to the command line.</P> + +<H3>Channel Editor</H3> + +<P>The channel editor is used to globally alter channel information, +including items like hue, contrast, fine tuning and others. Users in North +America shouldn't run the channel editor until you've completed the initial +mythtv-setup and ran <B>mythfilldatabase</B> at least once to populate the +database.</P> + +<H3><A NAME="storagegroups"></A> Storage Groups </H3> + +<P> +<FIGURE> +<EPS FILE="add.eps"> +<IMG SRC="add.png"> +<CAPTION>New in MythTV 0.21</CAPTION> +</FIGURE> +</P> +<H3>Introduction.</H3> + +<P>Storage Groups are lists of directories that are used to hold MythTV +recording files giving you a flexible way to allow you to add capacity to +your MythTV system without having to use exotic solutions such as LVM, +filesystem expansion or RAID Online Capacity Expansion. You can also use +Storage Groups to organize recordings and to put recordings of a certain +type into one subdirectory.</P> +<P>Storage Groups do not offer redundancy in case of hard drive failure, but +unlike LVM, if you lose a hard drive, you only lose the recordings that were +on that drive. With LVM, if you lose a hard drive, you will most likely +lose <B>everything</B>.</P> + +<H3>How to use Storage Groups.</H3> + +<P>By default, there is only one Storage Group called "Default", and it is +used for all recordings and Live TV.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: You need to add at least one directory to the Default +Storage Group or else you will not be able to record anything with MythTV.</CAPTION> +</FIGURE> +</P> +<P>For example, if you have 5 hard drives in your system, your first hard drive +could be your "boot" drive, and the remaining four could be dedicated to +media storage. You could format the drives and mount them as +<CODE>/mnt/store/d2</CODE>, <CODE>/mnt/store/d3</CODE>, <CODE>/mnt/store/d4</CODE> and +<CODE>/mnt/store/d5</CODE>.</P> +<P>Within each mount point, it's <EM>strongly</EM> recommended that you use a +sub-directory and make that the destination path for the Storage Group. See +the +<A HREF="#storagegrouptip">Tip</A> in the "Configuring the Master +backend" section for additional information.</P> +<P>You would then add the four subdirectories you created under the mount +points (<CODE>/mnt/store/d1/video</CODE>, etc) into the "Default" Storage Group.</P> +<P>At recording time, if there were four simultaneous recordings, MythTV would +put one recording onto each drive.</P> +<P>Or, say that you originally installed MythTV to a 80GB hard drive, and that +hard drive is now filling up. You could simply add a new drive to your +system, mount it and update the Storage Group to add additional space.</P> +<P>You may create additional Storage Groups to store specific recordings in +their own directories. Storage Groups are edited via the 'Storage +Directories' section of mythtv-setup. </P> +<P>You can also create multiple Storage Groups to group recordings together; +recording schedules now have an option to specify which Storage Group to +use.</P> +<P>MythTV will balance concurrent recordings across the available directories +in a Storage Group in order to spread out the file I/O load. MythTV will +prefer filesystems that are local to the backend over filesystems that are +remote until the local filesystem has 2 concurrent recordings active or +other equivalent I/O, then the next recording will go to the remote +filesystem. The balancing method is based purely on I/O, Myth does not try +to balance out disk space unless a filesystem is too low on free disk space +in which case it will not be used except as a last resort.</P> +<P>Storage Groups are global, but can be overridden on a slave backend by +creating a local Storage Group by running <B>mythtv-setup</B> on the +slave. If a problem occurs and the slave backend is unable to use the +desired Storage Group, it will fail back and try the directories defined in +the master's Storage Group.</P> +<P>There's also a special 'LiveTV' Storage Group, but the directory list starts +out empty. If you add a directory to the Storage Group, it will be used +instead of putting LiveTV recordings in the Default Storage Group. This +will allow you to put your LiveTV recordings on their own filesystem, which +is similar to the old MythTV method which used a RingBuffer for LiveTV. Of +course, you don't have to do anything, and Live TV recordings will just go +into the Default Storage Group where they'll be the first programs eligible +for expiration if the system needs free space for recordings.</P> +<P>Usage information for all Storage Group directories is visible on the +mythfrontend status screen as well as the mythbackend status webpage. +MythTV is smart enough to determine which directories are on shared +filesystems so it should not count free or used space multiple times if you +have more than one directory on the same filesystem.</P> + +<H3>Migrating to Storage Groups.</H3> + +<P>Migrating to Storage groups is very simple: if you have existing +recordings in a storage directory, then the system will automatically add +that directory to the Default Storage Group. If you then add additional +directories to a storage group, the system is flexible enough to check +<EM>all</EM> Storage Groups for a file before deciding that it can't be +found, which means that you can use the <B>mv</B> command from the Unix +command line to arrange files however you'd like.</P> + +<H3>Advanced: Algorithm used by the Storage Group</H3> + +<P>This section details the logic of the Storage Group allocation engine.</P> +<P>The current load-balancing preferences (in order) are: +<UL> +<LI>Local filesystems over remote</LI> +<LI>Less-busy (less weight) over more-busy (more weight)</LI> +<LI>More Free Space over Less Free Space</LI> +</UL> +</P> +<P>The 'business' of a filesystem is determined by weights. The following +weights are added to a filesystem if it is in use for the following things: +<UL> +<LI>recording = +10</LI> +<LI>playback = +5 (mythfrontend)</LI> +<LI>comm flagging = +5 (mythcommflag)</LI> +<LI>transcoding = +5 (mythtranscode)</LI> +</UL> +</P> +<P>If a recording is due to end within 3 minutes, it is not counted against +the weight of a filesystem. This is done to account for the pre/post-roll +and start-early/end-late settings. </P> + +<H2><A NAME="ss9.2">9.2</A> <A HREF="#toc9.2">Post-configuration</A> +</H2> + +<P>Run the <CODE>mythfilldatabase</CODE> program as directed. The master +backend will obtain guide data for all the video sources you defined during +setup.</P> +<P><B>NOTE</B>: If you are using Schedules Direct and watching the output messages +on the console or the log file it is normal to see a "401 Unauthorized" +error followed by a "200 OK" when the connection to Schedules Direct is being +established. +<BLOCKQUOTE><CODE> +<PRE> +From : Sun Jun 13 05:00:00 2004 To : Mon Jun 14 05:00:00 2004 (UTC) +--02:58:01-- +http://datadirect.webservices.zap2it.com/tvlistings/xtvdService + => -' +Resolving datadirect.webservices.zap2it.com... 206.18.98.160 +Connecting to datadirect.webservices.zap2it.com[206.18.98.160]:80... +connected. +HTTP request sent, awaiting response... 401 Unauthorized +Connecting to datadirect.webservices.zap2it.com[206.18.98.160]:80... +connected. +HTTP request sent, awaiting response... 200 OK +Length: unspecified [text/xml] + + [ <=> ] 114,125 63.57K/s + +02:58:03 (63.53 KB/s) - -' saved [114125] + +Your subscription expires on 08/20/2004 12:00:00 AM +Grab complete. Actual data from Sun Jun 13 05:00:00 2004 to Mon Jun 14 +00:00:00 2004 (UTC) +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Once <CODE>mythfilldatabase</CODE> has finished, start the master server before +continuing. +<BLOCKQUOTE><CODE> +<PRE> +$ mythbackend +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>mythbackend will print information about connections and what it's doing to +the console. If you'd like to see the options that are available for +mythbackend, type <CODE>mythbackend -h</CODE> for help.</P> +<P>As of MythTV v0.21, the available options are: +<BLOCKQUOTE><CODE> +<PRE> +$ mythbackend --help +Valid options are: +-h or --help List valid command line parameters +-l or --logfile filename Writes STDERR and STDOUT messages to filename +-p or --pidfile filename Write PID of mythbackend to filename +-d or --daemon Runs mythbackend as a daemon +-v or --verbose debug-level Use '-v help' for level info +--printexpire List of auto-expire programs +--printsched Upcoming scheduled programs +--testsched Test run scheduler (ignore existing schedule) +--resched Force the scheduler to update +--nosched Do not perform any scheduling +--nojobqueue Do not start the JobQueue +--noautoexpire Do not start the AutoExpire thread +--version Version information +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Running mythbackend as a daemon and using the logfile option will allow you +to have mythbackend automatically start up during boot. You can follow the +steps outlined in the section called +<A HREF="#mythbackend_autostart">Automatically starting mythbackend at system boot time</A> for +configuration steps.</P> +<P>If you enable the <CODE>-l</CODE> parameter, you will want to keep your logfiles +rotated (so that they don't fill up a partition). See the section called +<A HREF="#logrotate">Automatically rotating logs</A> for more +information.</P> + +<H2><A NAME="nonmaster_backend"></A> <A NAME="ss9.3">9.3</A> <A HREF="#toc9.3">Configuring a non-master backend </A> +</H2> + +<P>Ensure that you've granted access to the master MySQL database for remote +backends as discussed in the section titled +<A HREF="#modify_perm_mysql">Modifying access to the MySQL database for multiple systems</A> and that +you have the correct IP address for the database server in the "Database +Configuration" screen of the mythtv-setup application on this slave backend.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Slave backends <B>must not</B> run a local MySQL +daemon. By default, they will connect to their local daemon rather than the +central database, causing unexpected behavior such as empty "Watch +Recordings" lists and a failure to locate the Video Sources defined on the +master backend. Modify the <CODE>/usr/local/share/mythtv/mysql.txt</CODE> file +on all slave backends to ensure that the <CODE>DBHostName</CODE> has the address +of the MySQL server. +Caveat: You may make a slave backend the primary MySQL server, or run a +non-MythTV database on a slave backend as long as you have edited the +<CODE>mysql.txt</CODE> file on <B>all</B> systems and made it consistent. There can be only one authoritative MySQL database in a MythTV system - +errors such as the one above ensue if backends and frontends have differing +ideas of which MySQL database they should talk to.</CAPTION> +</FIGURE> +</P> +<P>Make sure that the IP addresses on the General setup screen are accurate. +If the slave backend can't communicate with the master backend due to IP +address misconfiguration then MythTV will not function properly.</P> +<P>Configuration of a non-master backend follows the same general procedure +as that of the master backend, with the exception that you skip over the +"Video Sources" step. All possible video sources need to be defined on the +master backend system; only the master backend will query a listings +provider to obtain guide data for all the non-master backends.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Do not run <CODE>mythfilldatabase</CODE> on a non-master backend.</CAPTION> +</FIGURE> +</P> +<H2><A NAME="ss9.4">9.4</A> <A HREF="#toc9.4">Configuring and running mythfilldatabase</A> +</H2> + +<P> +<FIGURE> +<EPS FILE="warning.eps"> +<IMG SRC="warning.png"> +<CAPTION><B>NOTE</B>: <B>mythfilldatabase</B> might take a while to complete, +depending on any number of factors, most of which you can't control. It's +best to just let the program run to completion.</CAPTION> +</FIGURE> + +<B>mythfilldatabase --help</B> will give a full listing of the options +available. </P> +<P><B>mythfilldatabase --manual</B> is another option; the manual option will +allow you to fine tune channel frequencies and specify which channels will +be added to the database. </P> +<P><B>mythfilldatabase --file</B> is an option if there isn't an XMLTV grabber +for your country, but you <B>do</B> have an XML formatted listings file +created by some other program.</P> +<P><B>mythfilldatabase --xawchannels</B> is an option if you have used +<B>xawtv</B> to fine-tune your channels and would like to import the fine +tuning offsets into MythTV.</P> +<P><B>mythfilldatabase --refresh-today</B> will only pull guide data for +today (in case of late-breaking changes to the schedule).</P> + + +<H3>Periodically running <B>mythfilldatabase</B></H3> + +<P>In order to keep your database filled, <B>mythfilldatabase</B> should be +run once a day.</P> +<P>To use MythTV's built-in capability, you'll need to run the +<B>mythfrontend</B> Setup option. From the mythfrontend, enter the +Setup>General screen and advance to "Mythfilldatabase", the fourth screen. +Select the checkbox, then complete the options as you see fit. The +<B>mythbackend</B> program will now run <B>mythfilldatabase</B> for you.</P> + +<H2><A NAME="ss9.5">9.5</A> <A HREF="#toc9.5">Grabbing channel icons for Schedules Direct users</A> +</H2> + +<P>While the Schedules Direct TV listings service has several advantages, it +does not support grabbing logo icons for the stations you receive. However, +there are utilities provided with MythTV which you may use to grab your +initial set of icons and to keep them updated if your lineups change.</P> +<P>First, you need to generate or obtain an XML file with the information for +your stations.</P> +<P>If you have XMLTV software installed, there is a perl script in MythTV's +<CODE>contrib/</CODE> directory which will generate this file for you. Run the +command: +<BLOCKQUOTE><CODE> +<PRE> +$ perl mkiconmap.pl +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>You will be asked for your zip code and the service that you use. If there +are no errors, the <CODE>iconmap.xml</CODE> file that you need for the next step +will be created.</P> +<P>If you do not have XMLTV software installed and do not want to install it +for the sake of this minor task, there is a generic +<CODE>contrib/master_iconmap.xml</CODE> which you can copy and use but this may +not be as complete as using the specific information for your service.</P> +<P>Once you have an <CODE>iconmap.xml</CODE> file, add the icon information to your +database and grab any new icons with the command: +<BLOCKQUOTE><CODE> +<PRE> +$ mythfilldatabase --import-icon-map iconmap.xml --update-icon-map +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="s10">10.</A> <A HREF="#toc10">Configuring mythfrontend.</A></H2> + +<P>Once you have completed configuration of your backend systems, the next +step is to configure the frontend client. </P> +<P>When you start mythfrontend for the first time, it will attempt to connect +to a configuration database on the local machine. If there is none, a +"Database Configuration" screen will appear, and you will need to fill in +some details. The "Host name" field needs the backend or database server's +IP address or DNS name, and the User or password fields may need to be set +to match your database user accounts. After editing those fields, press +Enter twice to write these configurations on your local machine, and attempt +to connect to the database. If you make any mistakes, the screens will pop +up again.</P> +<P>Now that mythfrontend has started up, you should have a number of +buttons/choices. Before doing anything, go to TV, then to Setup and +configure the frontend client. +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: You should go through the various setup screens in +mythfrontend before using any other modules to ensure that the the database +is correctly initialized.</CAPTION> +</FIGURE> +</P> +<H2><A NAME="ss10.1">10.1</A> <A HREF="#toc10.1">General</A> +</H2> + +<P>The General screen has configuration items that don't really fit anywhere +else. The first few configuration items ask you to indicate the number of +seconds to record before or after a program, which is useful if the +broadcast network or your system clock are out of sync and will help prevent +you missing the beginning or end of a program. </P> +<P>To change the value, use the left and right arrow keys to increment and +decrement the number of seconds. When you're satisfied with the result, use +the down arrow to put the input focus on the Next button or press RETURN to +continue to the next page.</P> +<P>The next page has a number of options to do with how channels are displayed +on your system. The help text will give you more information. Move the +focus to Next and press the space bar to continue.</P> +<P>The last General page sets up some final configuration items. See the help +text for more information.</P> + +<H2><A NAME="ss10.2">10.2</A> <A HREF="#toc10.2">Appearance</A> +</H2> + +<P>This set of screens is mostly concerned with how MythTV will look on your +system. From here, you can choose different themes and set the resolution +of your system.</P> + +<H2><A NAME="ss10.3">10.3</A> <A HREF="#toc10.3">Program Guide</A> +</H2> + +<P>Fairly self explanatory. Note that the alternate program guide does not +use the same font settings as defined in Appearance, so if the EPG is +unreadable this is where you make the adjustments to fonts, number of +elements displayed, etc.</P> + +<H2><A NAME="deinterlace_"></A> <A NAME="ss10.4">10.4</A> <A HREF="#toc10.4">Playback </A> + </H2> + +<P>The one configuration item which may cause problems on your system is the +"Deinterlace playback" setting. MythTV uses a linear blend algorithm for +deinterlacing, which will improve how the image looks on your screen. +Deinterlacing requires that your processor support SSE. (Streaming SIMD +Extensions, aka "MMX2"). Early Intel Celeron (those that don't use the +Coppermine 0.18um core and are usually <600MHz), Pentium Pro and Pentium II +CPUs do not have SSE, so make sure you haven't enabled deinterlacing if +your processor doesn't support it. If you enable it, and your processor +doesn't support SSE, you will get "Illegal Instruction" errors.</P> +<P>To determine if you've got SSE on an Intel processor, you can: +<BLOCKQUOTE><CODE> +<PRE> +$ cat /proc/cpuinfo +[snip] +flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca +cmov pat pse36 mmx fxsr sse +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Notice the <B>sse</B> at the end of the line - this tells you that this +processor will be able to deinterlace correctly.</P> +<P>On an AMD processor, look for "3dnow" in the cpuinfo line; "3dnow" is AMD's +implementation of SSE instructions, so if your processor has 3dnow you +shouldn't have any issues with deinterlacing.</P> +<H3>Video Filters</H3> + +<P>MythTV provides a means of employing video filters while recording and +during playback. These filters can be used to improve or modify the video +image, including hiding the effects of an interlaced image or reducing the +impact of noise in a poor video signal. The following is a brief +introduction to introduce you to the filters that are available in MythTV +version 0.20 and higher.</P> +<H3>Applying filters</H3> + +<P>One or more filters can be included in a "filter chain". The filters to +be used are identified in a "filter string". A filter string is a group of +filter names and parameters separated by commas. To include parameters, the +filter name is followed by "=" and the parameter information. There should +be no spaces in the filter string. Here is an example filter string:</P> +<P>With parameters: <CODE>kerneldeint=10:1,denoise3d=12</CODE></P> +<P>Without: <CODE>kerneldeint,denoise3d</CODE></P> +<P>Recording filters are set for each individual channel. These may be used +when encoding in software (MPEG-4, RTjpeg) but do not apply when using a +capture card with hardware encoding such as those supported by the ivtv +driver, DVB, HDTV or MJPEG cards. You can run MythTV's "setup" program and +select the "Channel Editor". On the first page for each channel, you can +enter a filter string in the box titled "Video filters". If you are running +"mythweb" on your web server, you can click on "Settings" then "Channels" +and enter filter strings in the "videofilters" column.</P> +<P>Playback filters are per-host and apply to any recording you watch from the +frontend where filters have been applied. Playback filtering can only +work with software decoding so the viaslice, xvmc, and ivtv outputs ignore +filters entirely. From "mythfrontend" go to Setup->TV Settings->Playback. +Enter your filter string in the box titled "Custom Filters".</P> + +<H3>Currently Available Filters</H3> + +<P>"Deinterlace Playback" checkbox.</P> +<P>This implements special behavior needed for the "bobdeint" filter but can +also be used to choose any of the deinterlace filters. If you prefer, you +may leave this unchecked and include any of the deinterlace filters, other +than "bobdeint", in your custom filter chain.</P> +<P>o The "invert" filter</P> +<P>Invert ignores any parameters and inverts the pixel values of the video +frames. In other words, a negative image. This would rarely be useful but +may be a good example to verify that your filter strings take effect.</P> +<P>o The "linearblend" filter</P> +<P>It is a simple deinterlacing filter that ignores parameters and works by +blending adjacent lines. It replaces combing in interlaced video with a +less distracting "ghost" image.</P> +<P>o The "bobdeint" filter</P> +<P>This filter splits the interlaced image into two separate fields that +can be line doubled then displayed at twice the frame rate. If the +display is at the same refresh rate as the recording (59.92Hz NTSC or +50Hz PAL) this will cause each refresh to show objects in motion in +a new position with no jagged edges. However, if the display is not +synchronous, it will cause flickering or the appearance of the picture +moving up and down by one line.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: This filter requires the frame rate to be doubled +and therefore can only be used with the "Deinterlace Playback" checkbox. +Do not include this in your filter chain.</CAPTION> +</FIGURE> +</P> +<P>o The "kerneldeint" filter</P> +<P>Kerneldeint is a more complex deinterlacing filter which applies a filter +kernel using input from several lines. It generally removes combing without +a "ghost" image, sometimes leaving a faint outline of the image from the +other field. It is considered to be less distracting to watch than +linearblend or no filter at all. It accepts one or two integer parameters +separated by a colon.</P> +<P>The first parameter is the filter threshold and defaults to 12. Adjacent +lines differing by more than the threshold value are filtered. The second +option defaults to 0. If set to a non-zero value, it will cause the filter +to skip chroma, and filter only the luminance. It may be useful on some +capture cards which do not capture the chroma fields of interlaced video +correctly.</P> +<P>o The "onefield" filter</P> +<P>This is a simple one-field deinterlacing filter that uses only one field of +the interlaced video. By default it keeps the top field, though passing the +parameter "bottom" will cause it to keep the bottom field instead.</P> +<P>This filter is primarily useful for those who display 1080i HDTV signals +with a video mode that has 540 pixels vertically. The advantage over other +deinterlacing filters is that scenes with motion never show combing or +ghosting.</P> +<P>o The "adjust" filter</P> +<P>This filter adjusts the digital values for luma and chroma to ensure that +they will fall within the ranges specified in the ITU-R601 standard. By +default, this corrects a known problem for the luma range used by bt8x8 +chips which causes video to look washed out. If parameters are passed, there +need to be exactly six. However, passing a single parameter of "-1" will +disable the filter.</P> +<P>1: luma minimum input value (int) +2: luma maximum input value (int) +3: luma gamma correction (float) +4: chroma minimum input value (int) +5: chroma maximum input value (int) +6: chroma gamma correction (float)</P> +<P>The default bt8x8 correction values are equivalent to +"16:253:1.0:2:253:1.0". Output ranges are fixed at ITU-R601 values (16-235 +luma, 16-240 chroma).</P> +<P><B>NOTE</B>: If it is not already specified in the filter chain, this +filter will be automatically applied when recording with the "bttv" driver.</P> +<P>o The "quickdnr" filter</P> +<P>A fast temporal denoiser. This can take 1, 2 or 4 parameters, each being a +value from "0" for the least filtering to "255" for the greatest filtering. +With one parameter, the filter will compute the values it should use for all +of its variables. Two parameters will set the filter strength for luma and +chroma independently. If you are interested in how the algorithm works, you +may examine the source code to see how four parameter are used.</P> +<P>o The "denoise3d" filter</P> +<P>A slower denoiser that applies a spatial and temporal low-pass filter. The +spatial filter can remove some noise that quickdnr can't, but a more +powerful CPU is needed. This filter accepts 3 float parameters:</P> +<P> +<UL> +<LI>luma spatial filter strength</LI> +<LI>chroma spatial filter strength</LI> +<LI>luma temporal filter strength</LI> +</UL> +</P> +<P>Reasonable defaults will be selected for omitted parameters. The chroma +temporal filter strength is calculated from the other filter strengths.</P> +<P>o The "crop" filter</P> +<P>Covers edges of video with black bars. This helps improve video quality +when the edges of the frame are distorted. By default, this removes 16 +pixels from each edge. This can optionally take four parameters representing +top:left:bottom:right. The number times 16 is the number of pixels to remove +so, for example, the default is "=1:1:1:1".</P> +<P>o The "forceyv12" and "forceyuv422p" filters</P> +<P>These force the filter manager to use the given format. You can use one of +these at the head of a filter chain to change the capture format. The most +likely use would be forceyuv422p to use YUV422P capture on cards with known +chroma interlacing problems with YV12.</P> +<P>There are some filters included in the MythTV source code that should +not be used:</P> +<P>o The "forcergb24" and "forceargb32" filters</P> +<P>The two RGB formats should not be used because there is no conversion filter +for them yet.</P> +<P>o The "convert" filter</P> +<P>It exists but don't use it. The filter manager uses this filter +automatically when it is unable to match the input/output formats of two +adjacent filters.</P> +<P>o The "postprocess" filter</P> +<P>While this exists in MythTV source code, it is currently not recommended for +use.</P> + +<H3>Usage Considerations</H3> + +<P>There are trade-offs to consider when deciding if it would be wise to use +a filter. Any processing will modify the original image so you should assess +if the filter has made a noticeable improvement to the picture in order to +justify the impact of the processing. Adding any filter will inherently +increase CPU usage. The impact can vary dramatically depending on your CPU +type and speed, the resolution of the recording, which filters you are using +and other factors. You can only determine what is right for you through +experimentation. However, as a starting point, here are some filter strings +that you may find useful:</P> +<P>For typical broadcast stations: "kerneldeint,quickdnr"</P> +<P>For stations with poor signal quality: "linearblend,denoise3d=12"</P> +<P>For synchronous TV-out: check Deinterlace with "Bob (2x framerate)"</P> + +<H2><A NAME="Recording"></A> <A NAME="ss10.5">10.5</A> <A HREF="#toc10.5">Recording </A> +</H2> + +<P>Depending on your capture card, MythTV offers different video encoders. +The following types of hardware encoding cards are supported: +<UL> +<LI>MJPEG - Zoran-based cards; see +<A HREF="http://mjpeg.sourceforge.net">http://mjpeg.sourceforge.net</A></LI> +<LI>MPEG-2 - iTVC15/16 based cards (Hauppauge PVR-250/PVR-350); see +<A HREF="http://ivtvdriver.org">http://ivtvdriver.org</A> </LI> +<LI>HDTV - pcHDTV cards; see +<A HREF="http://pchdtv.com">http://pchdtv.com</A> and +the Air2PC-ATSC-PCI see +<A HREF="http://www.cyberestore.com/product_info.php?cPath=28&products_id=103">http://www.cyberestore.com/product_info.php?cPath=28&products_id=103</A></LI> +<LI>DVB - cards supporting DVB; see +<A HREF="http://linuxtv.org">http://linuxtv.org</A></LI> +</UL> + +For cards without hardware encoding capabilities (all cards supported by +V4L not listed above), Myth includes two methods for software encoding: +RTjpeg and MPEG-4. RTjpeg has significantly fewer CPU demands than MPEG-4, +but it generates larger files than MPEG-4 for a given recording.</P> +<P>For DVB and HDTV cards, no further configuration is required after +setting up the card using the 'mythtv-setup' program. +For all other cards, configuration is done through MythFrontend. +Selecting 'Recording Profiles' from the 'TV Settings' screen will list +the profiles currently available for the cards in your system. +Depending on what types of cards you have installed you may see: +<BLOCKQUOTE><CODE> +<PRE> +(Create new profile group) +Software Encoders +Hardware MPEG Encoders +Hardware MJPEG Encoders +Transcoders +</PRE> +</CODE></BLOCKQUOTE> + +The '(Create new profile group)' option will allow you to create custom +profiles in case you have multiple backends. Note that custom profiles +are per backend and card type. If you have 2 MPEG-2 encoders in a given +backend system, creating a custom profile will affect both of them. This +option should not be needed otherwise.</P> +<P>The 'Transcoders' group is a little different from the others. Selecting +this group will result in a menu with the following options: 'RTjpeg/MPEG-4' +and 'MPEG-2'. These types indicate what transcoder options will be used for +a given input type (i.e. the 'MPEG-2' settings would be used to transcode +MPEG-2 files into MPEG-4. The source of the MPEG-2 stream (DVB, HDTV, or +PVR-x50) does not matter. Configuration of the options is the same as below +(although any resolution settings will be ignored).</P> +<P>Selecting any of the other options will show a new screen with a list of +four profiles: +<UL> +<LI>Default</LI> +<LI>Live TV</LI> +<LI>Low Quality</LI> +<LI>High Quality</LI> +</UL> +</P> +<P>The Default profile will be used for any recording which does not otherwise +have a specific profile assigned. The 'Live TV' profile will be used when +watching TV. The remaining two profiles are available for customizing to +allow for more precise control over what quality is used for a given +program.</P> +<P>Selecting a profile will allow you to adjust the relevant options for that +card. The most significant setting is the recording resolution, but you can +also choose encoding format, audio format, and tweak other encoder specific +properties.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: although the width and height can be changed to almost +anything, if you start MythTV and don't see video or you get "segmentation +fault" errors, it is likely that the video4linux (v4l) subsystem did not +like the height and width parameters specified. It's best to leave the +default as-is until you're sure that MythTV is operational.</CAPTION> +</FIGURE> +</P> +<P>See the +<A HREF="#capture_resolution_">What capture resolution should I use? How does video work?</A> section for more information.</P> + +<H2><A NAME="ss10.6">10.6</A> <A HREF="#toc10.6">Xbox Frontends</A> +</H2> + +<P>MythTV is able to control the LED on the Xbox to indicate backend +recording status. </P> +<P>To control the LED, you will need the <B>blink</B> program from the +xbox-linux project, which is installed as <CODE>/bin/led</CODE> on GentooX. On +Xebian (the new Ed's Debian) you must install it yourself. On other +distributions it may or may not be installed as a program called +<B>blink</B> and should be located in your path. (Type <CODE>which +blink</CODE> to see if the program is available.) If you do not have +<B>blink</B>, you may obtain it from the Xbox-Linux project site at +<A HREF="http://xbox-linux.sf.net/">http://xbox-linux.sf.net/</A>. The +program you need is part of the <CODE>eds_i2c_staff</CODE> module in CVS. Note +the spelling.</P> +<P>Once you have installed <B>blink</B> you will need to set permissions. +<B>blink</B> needs write permission to the i2c device to function +properly. There are three methods to accomplish this. First, you could run +<CODE>mythfrontend</CODE> as root, which is the simplest method, but could +potentially be a security risk. Next, you may make the <B>blink</B> +binary setuid root, which allows non-privileged users to run a program with +root capability. This is done by typing the command: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# chmod u+s /path/to/blink +</PRE> +</CODE></BLOCKQUOTE> + +The final technique would be to set the <CODE>/dev/i2c/0</CODE> device read/write +for all users, but this is the least preferred method.</P> +<P>Now it's time to setup MythTV for Xbox hardware. Enter Setup -> General. +On the second page check the 'Enable Xbox Hardware' option. Upon reentering +the settings, you should have a new option named 'Xbox'. Within this option +you may select the distribution, LED colors for recording and the update +interval. If you select GentooX as the distribution <B>led</B> will be +used as the <B>blink</B> binary name, otherwise, <B>blink</B> is used. +Colors should be self explanatory. The update interval determines how often +the frontend should poll the backend to determine if the status has changed.</P> + +<H2><A NAME="s11">11.</A> <A HREF="#toc11">Using MythTV.</A></H2> + +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE to Red Hat/Fedora 4 users</B>: Red Hat Linux and Fedora Core ship +with Gnome as the default desktop environment. However, Gnome seems to have +issues with window focus and window switching which sometimes cause +mythfrontend to obscure the video. KDE does not seem to have any such +issues. Therefore you will need to switch to KDE by selecting +RedHatMenu>Extras>System Settings>Desktop Switching Tool and choose "KDE". +<B>NOTE to Fedora Core 5 and 6 users</B>: Fedora 5 and 6 no longer have +this tool in the Menu. Use "switchdesk KDE" from a command line. Read "man +switchdesk" for further information about changing to other desktop +environments.</CAPTION> +</FIGURE> +</P> +<H2><A NAME="ss11.1">11.1</A> <A HREF="#toc11.1">Keyboard commands</A> +</H2> + +<P>The <CODE>keys.txt</CODE> file describes what the various keyboard commands are. +If you have loaded mythweb, you may change the default keys to your liking.</P> +<H3>mythfrontend</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Arrow keys </TD><TD> used to move the highlight point around </TD></TR><TR><TD> +ALT-F4 </TD><TD> exit out of the application </TD></TR><TR><TD> +Space/Enter </TD><TD> take action on the item under the highlight point </TD></TR><TR><TD> +P </TD><TD> play in both "Watch a Recording" and "Delete a Recording" </TD></TR><TR><TD> +D </TD><TD> delete in both "Watch a Recording" and "Delete a Recording" </TD></TR><TR><TD> +U </TD><TD> to view details for the currently selected show on the Watch or Delete screens, EPG, "Program Finder", "Fix Scheduling Conflicts" and search results screens </TD></TR><TR><TD> +O </TD><TD> to list the upcoming episodes for the currently selected show on the EPG, "Program Finder", "Program Recording Priorities", "Fix Scheduling Conflicts" or search results screens </TD></TR><TR><TD> +I </TD><TD> edit recording options from the EPG, "Program Finder", "Program Recording Priorities", or "Fix Scheduling Conflicts" screens. From the Playback and Delete screens, 'I' presents options for recorded shows such as Auto Expire or Stop Recording. Pressing 'I' while on the Recording Options screen will take you to the Advanced Recording Options screen. +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Watching TV or a recording</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Up or down </TD><TD> keys change the channel </TD></TR><TR><TD> +num pad </TD><TD> Type a number to enter a channel number or jump amount (HHMM format) </TD></TR><TR><TD> +P </TD><TD> pause / play. You may also add an explicit keybinding for 'Play' through MythWeb, returning you to normal speed if you are in slow motion, rewind fast forward or pause mode. </TD></TR><TR><TD> +C </TD><TD> change inputs on TV Tuner card </TD></TR><TR><TD> +ESC </TD><TD> quits </TD></TR><TR><TD> +I </TD><TD> puts the On-screen Display up again. During playback, 'I' toggles between position and show description info. If a jump amount is entered, jump to that position. </TD></TR><TR><TD> +M </TD><TD> brings up the electronic program guide (Grid) -- see the EPG section </TD></TR><TR><TD> +Page Up </TD><TD> jump back the configured number of minutes (default is 10) </TD></TR><TR><TD> +Page Down </TD><TD> jump ahead the configured number of minutes (default is 10) </TD></TR><TR><TD> +End or Z </TD><TD> skip to next commercial break marker </TD></TR><TR><TD> +Home or Q </TD><TD> skip back to previous commercial break marker </TD></TR><TR><TD> +T </TD><TD> toggle close caption support Pressing 0-9 (preferably 3 times) + T changes teletext page and turns on teletext. </TD></TR><TR><TD> +F </TD><TD> rotate between the various Picture Adjustments (Colour, Hue, etc.) While Picture Adjustment is on-screen, use Left and Right arrows to adjust. These settings adjust the look of the video playback, and are independent of the G-key settings used at record-time. </TD></TR><TR><TD> +[ or F10 </TD><TD> decrease volume </TD></TR><TR><TD> +] or F11 </TD><TD> increase volume </TD></TR><TR><TD> +| or F9 </TD><TD> toggle mute </TD></TR><TR><TD> +/ </TD><TD> jump to the next "favorite" channel </TD></TR><TR><TD> +? </TD><TD> mark/unmark the current channel as a "favorite" </TD></TR><TR><TD> +U </TD><TD> increase the play speed </TD></TR><TR><TD> +J </TD><TD> decrease the play speed </TD></TR><TR><TD> +A </TD><TD> Adjust time stretch (speed up or slow down normal play of audio and video </TD></TR><TR><TD> +W </TD><TD> cycle through zoom and fill modes: 4:3 aspect ratio, 16:9, 4:3 Zoom (like Pan and Scan), 16:9 Zoom, and 16:9 Stretch (eliminates black sidebars in TV signal) </TD></TR><TR><TD> +F8 </TD><TD> toggle the sleep timer 30m->1hr->1hr30m->2hr->Off </TD></TR><TR><TD> +CTRL-B </TD><TD> Jump to the beginning of the recording / ringbuffer </TD></TR><TR><TD> ++ </TD><TD> Switch between audio streams </TD></TR><TR><TD> +Left </TD><TD> (if a jump amount is entered) to jump back that amount </TD></TR><TR><TD> +Right </TD><TD> (if a jump amount is entered) to jump ahead that amount </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> <B>Without the stickykeys option selected</B> </TD></TR><TR><TD> +Left </TD><TD> rewind the configured number of seconds (default is 5) </TD></TR><TR><TD> +Right </TD><TD> fast forward the configured number of seconds (default is 30) </TD></TR><TR><TD> +< </TD><TD> starts rewind mode as if stickykeys are selected </TD></TR><TR><TD> +> </TD><TD> starts fast forward mode as if stickykeys are selected </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> <B>With Stickykeys option selected</B> </TD></TR><TR><TD> +Right </TD><TD> starts fast forward mode </TD></TR><TR><TD> +Left </TD><TD> starts rewind mode </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> <B>In fast forward or rewind mode:</B> </TD></TR><TR><TD> +Left/Right </TD><TD> increases the ff/rew speed </TD></TR><TR><TD> +0 </TD><TD> plays at normal speed, but leaves the time indicator on screen </TD></TR><TR><TD> +1 or 2 </TD><TD> plays back more slowly than normal ff/rew speed (1 is slowest) </TD></TR><TR><TD> +3 </TD><TD> plays back at normal ff/rew speed </TD></TR><TR><TD> +4-9 </TD><TD> plays back faster than normal ff/rew speed (9 is fastest) </TD></TR><TR><TD> +Space </TD><TD> exits fast forward or rewind mode </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> <B>While video is paused:</B> </TD></TR><TR><TD> +Left </TD><TD> rewind 1 frame </TD></TR><TR><TD> +< </TD><TD> rewind 1 second </TD></TR><TR><TD> +Right </TD><TD> advance 1 frame </TD></TR><TR><TD> +> </TD><TD> advance 1 second +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Watching TV only</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +G </TD><TD> rotate between the various Picture Adjustments (Colour, Hue, etc.) for recording. These values affect the look of the resulting .nuv file, and are independent of the playback picture settings. While Picture Adjustment is on-screen, use Left and Right arrows to adjust. </TD></TR><TR><TD> +H </TD><TD> Channel history. Each repeat steps back through the previous channels. </TD></TR><TR><TD> +O </TD><TD> Turns on 'Browse' mode, allowing user to browse channels and program info while watching current show FullScreen. </TD></TR><TR><TD> +Y </TD><TD> switch between multiple capture cards. <B>NOTE</B>: you will lose your LiveTV buffer on your current card. Useful for different-sourced cards (such as Dish Network on one, HDTV over-the-air on another card.) </TD></TR><TR><TD> +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>LiveTV Browse Mode</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Left </TD><TD> browse program prior to current listed program </TD></TR><TR><TD> +Right </TD><TD> browse program following current listed program </TD></TR><TR><TD> +Up </TD><TD> browse program on channel above current listed channel/program </TD></TR><TR><TD> +Down </TD><TD> browse program on channel below current listed channel/program </TD></TR><TR><TD> +/ </TD><TD> browse program on next favorite channel </TD></TR><TR><TD> +0-9 </TD><TD> enter a channel number to browse </TD></TR><TR><TD> +Space/Enter </TD><TD> change channel to channel of current listed program </TD></TR><TR><TD> +R/r </TD><TD> Toggle recording of current program (cycles through types) </TD></TR><TR><TD> +ESC/O </TD><TD> Exit Browse mode +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Playback Recording Zoom Mode</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Left </TD><TD> Move video to Left </TD></TR><TR><TD> +Right </TD><TD> Move video to Right </TD></TR><TR><TD> +Up </TD><TD> Move video Up </TD></TR><TR><TD> +Down </TD><TD> Move video Down </TD></TR><TR><TD> +PageUp </TD><TD> Zoom In </TD></TR><TR><TD> +PageDown </TD><TD> Zoom Out </TD></TR><TR><TD> +Space/Enter </TD><TD> Exit Zoom mode leaving picture at current size and position </TD></TR><TR><TD> +ESC </TD><TD> Exit Zoom mode and return to original size +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>If you have two or more tuner cards</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +V </TD><TD> toggle Picture-in-picture on or off </TD></TR><TR><TD> +B </TD><TD> toggles the window focus (lets you change channels on the PiP window) </TD></TR><TR><TD> +N </TD><TD> swaps the two channels by changing channels on both cards +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Watching a recording only</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Space/Enter </TD><TD> set a bookmark at that point. Next time you start the recording, you will automatically jump forward to this point and clear the bookmark. </TD></TR><TR><TD> +X </TD><TD> queues the current recording for transcoding </TD></TR><TR><TD> +O </TD><TD> brings up menu to allow toggling settings such as Commercial Auto-Skip, Auto-Expire, etc. </TD></TR><TR><TD> +D </TD><TD> exits the current recording and displays the Delete menu </TD></TR><TR><TD> +E or M </TD><TD> enters/exits edit mode. </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> </TD></TR><TR><TD> +</TD><TD> <B>In edit mode</B> </TD></TR><TR><TD> +Left/Right </TD><TD> move forward and backward </TD></TR><TR><TD> +Up/Down </TD><TD> alter the amount of time you jump forward and backward. Increments are: nearest cutpoint, nearest video keyframe, 1 frame, 0.5 seconds, 1 second, 20 seconds, 1 minute, 5 minutes, and 10 minutes. </TD></TR><TR><TD> +PageUp/PageDown </TD><TD> move forward and backward to the nearest cut point </TD></TR><TR><TD> +< or > </TD><TD> move forward or backward by 10 times the normal jump amount </TD></TR><TR><TD> +Space/Enter </TD><TD> allows you to set or delete a cut point </TD></TR><TR><TD> +Z </TD><TD> loads the commercial skip list (if one exists) into the cutlist </TD></TR><TR><TD> +C or Q </TD><TD> clear all cut points in the cutlist </TD></TR><TR><TD> +I </TD><TD> Inverts the cutlist +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>EPG</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Arrows </TD><TD> are used to move the highlighted program point around </TD></TR><TR><TD> +A, D, S, W </TD><TD> perform the same as left, right, down and up </TD></TR><TR><TD> +PageUp/PageDown </TD><TD> move the channel list up or down a page </TD></TR><TR><TD> +Home/End </TD><TD> move the highlight left or right by one day </TD></TR><TR><TD> +Ctrl+Left or < </TD><TD> move the highlight left by one page </TD></TR><TR><TD> +Ctrl+Right or > </TD><TD> move the highlight right by one page </TD></TR><TR><TD> +9, 3, 7, 1 </TD><TD> (like a numeric keypad) perform the same as PageUp, PageDown, Home and End </TD></TR><TR><TD> +I </TD><TD> bring up more information about a show, and allow you to schedule a recording. If you select "Record this showing" while watching Live TV you can "Instant Record" a program. </TD></TR><TR><TD> +Space/Enter </TD><TD> allow you resolve conflicts or change overrides. If the program is not already scheduled to record, it will instead act like pressing 'I'. </TD></TR><TR><TD> +M </TD><TD> when on a channel will change to that channel </TD></TR><TR><TD> +ESC or C </TD><TD> exits without changing the channel </TD></TR><TR><TD> +R </TD><TD> change the current item from Recording/Not-Recording. Successive keypresses cycle through the scheduled recording type list. </TD></TR><TR><TD> +X </TD><TD> change the channel to the currently selected channel without leaving the EPG (Most useful in the alternate EPG) </TD></TR><TR><TD> +? </TD><TD> mark/unmark the current channel as a "favorite" </TD></TR><TR><TD> +/ or 4 </TD><TD> toggle the guide listing between all channels and filtered "favorites" +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Setting Program or Channel Recording Priorities</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Right </TD><TD> increases priority value </TD></TR><TR><TD> +Left </TD><TD> decreases priority value </TD></TR><TR><TD> +1 </TD><TD> sorts by title </TD></TR><TR><TD> +2 </TD><TD> sorts by priority </TD></TR><TR><TD> +Home/End </TD><TD> toggle sort priority </TD></TR><TR><TD> +I </TD><TD> edit recording options </TD></TR><TR><TD> +ESC </TD><TD> commits changes and exits +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Viewing Scheduled Recordings/Resolving Conflicts</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +1 </TD><TD> show all recordings </TD></TR><TR><TD> +2 </TD><TD> show only important recordings </TD></TR><TR><TD> +Home/End </TD><TD> toggle show showing all/important </TD></TR><TR><TD> +I </TD><TD> edit recording options </TD></TR><TR><TD> +Space/Enter </TD><TD> resolve conflict or override +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Viewing Search Listings</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +Home </TD><TD> change to the previous view if applicable </TD></TR><TR><TD> +End </TD><TD> change to the next view if applicable </TD></TR><TR><TD> +M </TD><TD> select another view if applicable. In the title and description search popup, press M again to edit or delete the selected view. +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Recording Profiles Setup Screen</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +D </TD><TD> on a custom profile group displays a popup to delete the group</TD></TR><TR><TD> +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Recording Groups</H3> + +<P>In the Watch Recordings screen, Recording Groups allow you to separate +programs into user-defined categories, such as "Kids", "Alice", "Bob", etc. +This can be used to reduce clutter, or to segregate content if you use the +PIN function. +<BR><CENTER> +<TABLE BORDER><TR><TD> +M </TD><TD> change the view or to set a group password </TD></TR><TR><TD> +I </TD><TD> move a program from one Recording Group to another +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Watch Recordings Screen</H3> + +<P> +<BR><CENTER> +<TABLE BORDER><TR><TD> +1 or F1 </TD><TD> Meaning of the icons </TD></TR><TR><TD> +/ </TD><TD> Tags a recording. Tagged recordings can be played either in order or shuffled and deleted as a group. You can also change the recording group for several recordings at once by tagging them and using the Menu (m) button, selecting "Playlist options", then "Change Recording Group". </TD></TR><TR><TD> +? </TD><TD> Clear the tagged list. +</TD></TR></TABLE> +</CENTER><BR> +</P> +<H3>Remote Controls</H3> + +<P>If you are using MythTV with just a remote control then it is suggested that you +map the remote control keys as described below. Your remote control may not +have the same set of keys as those named below, the names are only a suggestion +that roughly correspond to the function.</P> +<P>If you are adding new key bindings to the program then consideration of this +suggested list will help users with remote controls.</P> +<P>This list assumes a minimal remote control that only has 20 keys, nearly all +features can be used with this configuration. If you have more keys then you +can access all of the features. With only 16 keys most features are usable. +<BR><CENTER> +<TABLE BORDER><TR><TD> +REMOTE CONTROL </TD><TD> LIRC KEYSTROKE </TD><TD> FUNCTION </TD></TR><TR><TD> +0 - 9 </TD><TD> 0 - 9 </TD><TD> channel selection, EPG navigation, ff/rew speed setting (with stickykeys) </TD></TR><TR><TD> +Left Arrow </TD><TD> Left </TD><TD> scroll left, rewind </TD></TR><TR><TD> +Right Arrow </TD><TD> Right </TD><TD> scroll right, fast forward </TD></TR><TR><TD> +Up Arrow </TD><TD> Up </TD><TD> scroll up, channel change up </TD></TR><TR><TD> +Down Arrow </TD><TD> Down </TD><TD> scroll down, channel change down </TD></TR><TR><TD> +Select / OK / Play </TD><TD> Space </TD><TD> Select item, play (with stickykeys) set bookmark </TD></TR><TR><TD> +Cancel </TD><TD> Escape </TD><TD> Cancel, quit playback </TD></TR><TR><TD> +Menu </TD><TD> m </TD><TD> EPG (from watching TV) edit (from playback). </TD></TR><TR><TD> +Pause </TD><TD> p </TD><TD> Pause </TD></TR><TR><TD> +Other key 1 </TD><TD> i </TD><TD> Information </TD></TR><TR><TD> +Other key 2 </TD><TD> c </TD><TD> Change tuner card input +</TD></TR></TABLE> +</CENTER><BR> +</P> + +<H2><A NAME="ss11.2">11.2</A> <A HREF="#toc11.2">Using themes with MythTV</A> +</H2> + +<P>MythTV is "themeable", meaning that the visual appearance of the program +can be modified by the user without re-compiling or altering the program +functionality. Download the MythThemes tarball from the website and untar it:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xjf myththemes-0.21.tar.bz2 +$ cd ~/myththemes-0.21 +$ qmake myththemes.pro +$ su - +# make install +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The theme will now be available in the mythfrontend Appearance section.</P> + +<H2><A NAME="ss11.3">11.3</A> <A HREF="#toc11.3">Adding DishTV information to the database</A> +</H2> + +<P>A script for adding Pay Per View information into the MythTV database for +DishTV subscribers is available at +<A HREF="http://www.mythppv.com/">http://www.mythppv.com/</A>.</P> + +<H2><A NAME="ss11.4">11.4</A> <A HREF="#toc11.4">Adding support for an external tuner</A> +</H2> + +<P>MythTV supports changing the channel on an external tuner. If you have +an external tuner, such as a DirecTV or digital cable set top box, you +should add <CODE>/usr/local/bin/changechannel</CODE> to your Input Connections in the +mythbackend configuration GUI.</P> +<P>However, there is not <B>changechannel</B> program per-se, because this is +going to be dependent on what sort of external tuner you have. Look in the +<CODE>contrib/channel_changers</CODE> directory for a number of programs and +scripts which may be used to change channels. Once you find one which +works, copy it to <CODE>/usr/local/bin/changechannel</CODE>.</P> +<P>Feel free to browse some of what sort of hardware is available at +<A HREF="http://store.snapstream.com/accessories.html">http://store.snapstream.com/accessories.html</A>, or if you wish to +assemble your own, rather than purchase, the following may be helpful: +<A HREF="http://www.dtvcontrol.com/">http://www.dtvcontrol.com/</A> for +cable pinouts.</P> + +<H2><A NAME="ss11.5">11.5</A> <A HREF="#toc11.5">Using Shutdown/Wakeup</A> +</H2> + +<P>What does the MythTV Shutdown/Wakeup function do? The scheduler on the +Master backend (MBE) keeps track of the idle status of the entire MythTV +system, including the Slave backends (SBE). If it considers the system to be +idle, and thus ready to shutdown, it sets the wakeuptime to the time of the +next recording and then proceeds to shut down all Slave backends and then +itself. Once it is time to begin recording, the Master backend and the Slave +Backends are automatically woken up. This system allows MythTV to record +like a normal VCR, thereby conserving power when not in active use.</P> +<P>In order to use the Shutdown/Wakeup function there must be some method of +waking up the Master backend. There are any number of solutions, but we +will discuss in detail two possibilities:</P> +<P> +<UL> +<LI>Use another server that runs 24/7 and have it send a WakeOnLAN (WOL) +packet to wake the Master backend. This assumes that you have the WOL tools +installed, and that your Master backend motherboard supports WOL.</LI> +<LI>Use your motherboard's BIOS wakeup capability. You'll need a motherboard +that supports BIOS wakeup, and some tools. Two that work are: +<A HREF="http://sourceforge.net/projects/nvram-wakeup">http://sourceforge.net/projects/nvram-wakeup</A> and +<A HREF="http://www.malloc.de/tools/wakeup_clock.html">http://www.malloc.de/tools/wakeup_clock.html</A></LI> +</UL> +</P> + +<H3>A deeper look into the operation</H3> + +<P>The scheduler keeps track of the idle status of the MythTV system. To +determine whether or not the MythTV system is idle, the following conditions +must be met for a period of time defined in the "Idle timeout (secs)" +parameter. +<UL> +<LI>no client is connected to the server</LI> +<LI>no recording (neither LiveTV nor a regular recording) is currently taking place</LI> +<LI>no recording starts within a definable amount of time ("Max. wait for recording (min)")</LI> +<LI>the "pre Shutdown check-command" returns 0 </LI> +</UL> +</P> +<P>If we get to this idle state the Master backend will set the wakeuptime using the "Set +wakeuptime command", which is the same for WOL and BIOS wakeup. The Master backend will +then shut down the Slave backends and itself using the "Server halt command".</P> +<P>One caveat is that the scheduler tries to guess if the Master backend was started by a +wakeup call or by the user. If it thinks it was woken up by a user, it +blocks shutdown until a client connects to the Master backend, after which it will +behave as described above. To disable this feature, unset "Block shutdown +before client connected" in the mythfrontend Setup->Setup->General screen.</P> +<P>Once it is time to startup the system, the Master backend is woken up first and will +wakeup the Slave backends using the "Wake command for slaves". At this time, there is +no support for starting only the required Slave backend, so all Slave backends will startup.</P> + +<H3>Setting up the MythTV side of this extension.</H3> + +<P>There are a number of options that are used to control the Shutdown / +Wakeup feature.</P> +<P>Shutdown/Wakeup Options: +<UL> +<LI>"Idle timeout (secs)" is the time the server waits while idle until a +shutdown occurs.</LI> +<LI>"Max. wait for recording (min)" is the time the Master backend waits for a recording +without shutting down. For example, this would be used to prevent a 10 +minute system shutdown if a recording is set to start 15 minutes from now.</LI> +<LI>"Startup before rec. (secs)" Sets how long before a programmed +recording the MythTV system will be woken up. This should be roughly be the +time your systems need to bootup, and if you have Slave backends, you'll +need to ensure this value is long enough for all your machines to perform +their bootup cycle.</LI> +<LI>"Wakeup time format" is the format of the wakeup time that is given in +the "Set wakeuptime command" as a parameter "$time". You need to set this +according to your wakeup mechanism. If you need seconds since the epoch +(1970-01-01) set the "Wakeup time format" to "time_t".</LI> +<LI>"Set wakeuptime command" is the command executed to set the new wakeuptime. </LI> +<LI>"Server Halt Command" is the command executed to shutdown the Master +backend and the Slave backends.</LI> +<LI>"pre Shutdown check-command" is used to give a +"Go/NO-GO" decision from a non-MythTV source. This command is executed +immediately before the shutdown would occur. The return value is use to make +the following choices: +<UL> +<LI>If it returns a "0" the shutdown will occur as scheduled.</LI> +<LI>If it returns a "1" the "idle timeout" will be reset and the system +waits again for the timeout.</LI> +<LI>If it returns a "2" the entire shutdown sequence is reset. This means +that a new client connect is needed before a shutdown occurs, unless you have +the "Wait for client connect" setting disabled, in which case this is the same as +returning "1". An example of a use for this return value is to prevent the shutdown +if a user is currently logged in, or if a specific program (i.e. transcode, +automatic updates, etc.) is currently running. If you don't need it, leave +the field blank.</LI> +</UL> +</LI> +</UL> +</P> +<P>The "WakeOnLan settings": +These settings have nothing to do with using BIOS or WOL wakeup, they are +the same for both. +<UL> +<LI>"Master backend" This setting defines timings for the frontends to +wakeup the Master backend using WOL. Useful if your frontend can emit a WOL +packet so you don't need to physically go to the Master backend if you're +trying to watch TV.</LI> +<LI>"Reconnect wait time (secs)" is the time the frontend waits after +executing the "Wake command" before attempting to retry the connection. This +should be roughly the amount of time your Master backend needs for bootup. +Set to "0" to disable. The frontends will retry to connect for "Count of +reconnect tries" times before giving up.</LI> +<LI>"Wake command for slaves" is the <EM>one</EM> command executed to wake +your Slave backends. This should be a script that contains the calls to +wakeup all Slave backend systems.</LI> +</UL> +</P> + +<H3>Using WOL to wake your Master backend. </H3> + +<P>To use WOL to wake your Master backend you will need a WOL capable Master +backend, a machine that runs 24/7 which can execute an at-job and nc (netcat) +on the Master backend. I use some little bash scripts to make my DSL router +wakeup my mythbox if required.</P> +<P>Replace $SERVER and $PORT with your own settings! +On my Master backend I have a script that gets called as 'setwakeuptime command' which +looks like the following: +<BLOCKQUOTE><CODE> +<PRE> +#! /bin/sh +echo $@ | nc $SERVER $PORT +</PRE> +</CODE></BLOCKQUOTE> + +This simply cats the parameters (that is $time) to my 24/7 server. On my +$SERVER I have (x)inetd listening on $PORT starting a little script which +cares about setting the at-job. The following additions are necessary on the +$SERVER:</P> +<P>If you use <B>inetd</B>:</P> +<P>In <CODE>/etc/inetd.conf</CODE> add: +<BLOCKQUOTE><CODE> +<PRE> +mythwake stream tcp nowait mythtv /usr/sbin/tcpd /usr/local/bin/mythwake +</PRE> +</CODE></BLOCKQUOTE> + +If you use <B>xinetd</B>, save the following as <B>mythwake</B> in your +<CODE>/etc/xinet.d/</CODE> directory: +<BLOCKQUOTE><CODE> +<PRE> +service mythwake + { + socket_type = stream + wait = no + user = mythtv + protocol = tcp + id = mythwake + server = /usr/local/bin/mythwake + } +</PRE> +</CODE></BLOCKQUOTE> + +and add the following to <CODE>/etc/services</CODE>: +<BLOCKQUOTE><CODE> +<PRE> +mythwake $PORT/tcp +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Finally, <CODE>/usr/local/bin/mythwake</CODE> looks like: +<BLOCKQUOTE><CODE> +<PRE> +#! /bin/bash +#this should be a command to wake your server +WAKECMD="#!/bin/sh\n /usr/local/bin/wakeMBE" +#first we need to delete all wake jobs in queue +for JOB in atq | cut -f 1 ; do + atrm $JOB; +done +#now we read the date from 'nc' +read date; +#now set the atjob +echo -e "$WAKECMD" | at $date ; +</PRE> +</CODE></BLOCKQUOTE> + +<B>SECURITY WARNING</B>: +Be sure to secure $SERVER:$PORT from untrusted networks, because this +allows 3rd parties to run arbitrary code on your server!</P> + +<H3>Using BIOS wakeup to wake your Master backend.</H3> + +<P>Since I don't use this, I cannot say much about this. If your motherboard +supports any wakeup tool you have to call that tool as "Set wakeuptime +command" with the "Wakeup time format" suitable for that tool.</P> +<H3>Wakeup the MySQL server using WOL</H3> + +<P>If your MySQL server and your Master backend are not on the same machine, +you can have the Master backend wake your MySQL server using WOL. You will +find the settings for this in the second page of the mythtv-setup program, +or at the end of <CODE>mysql.txt</CODE>. The meanings are the same as +discussed in "The WakeOnLan settings" above.</P> + +<H3>Tips/Tricks:</H3> + +<P>If, for example, one of the Slave backends is also your desktop computer, +you could simply use a little script as 'server halt command' which first +calls <CODE>/sbin/shutdown -t TIMEOUT</CODE> where TIMEOUT is a value sufficient +for you to react. You could then popup a window using *dialog, asking for +permission to shutdown. If you cancel the shutdown, simply call +<CODE>/sbin/shutdown -c</CODE>.</P> +<P>If you get "nvram-wakeup: /dev/rtc: Device or resource busy" your +set-wakeuptime-script should stop the program that uses <CODE>/dev/rtc</CODE> before +setting the wakeuptime.</P> +<H2><A NAME="ss11.6">11.6</A> <A HREF="#toc11.6">Controlling the mythfrontend via telnet</A> +</H2> + +<P>To use this feature you must first enable it in Settings>General>General</P> +<P>The network control listens on port 6546, as demonstrated below:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ telnet basement 6546 +Connected to basement. +Escape character is '^]'. +MythFrontend Network Control +Type 'help' for usage information +--------------------------------- +# help +Valid Commands: +--------------- +jump - Jump to a specified location in Myth +key - Send a keypress to the program +play - Playback related commands +query - Queries +exit - Exit Network Control + +Type 'help COMMANDNAME' for help on any specific command. + +# help jump +Usage: jump JUMPPOINT + +Where JUMPPOINT is one of the following: +channelpriorities - Channel Recording Priorities +channelrecpriority - Channel Recording Priorities +deletebox - TV Recording Deletion +deleterecordings - TV Recording Deletion +guidegrid - Program Guide +livetv - Live TV +livetvinguide - Live TV In Guide +mainmenu - Main Menu +...snip... +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Please note that this feature only allows one connection at a time, so any +new connections will automatically terminate prior ones.</P> + +<H2><A NAME="s12">12.</A> <A HREF="#toc12">Scheduling Recordings.</A></H2> + +<P>The MythTV master backend is responsible for managing the schedule for +all TV tuner cards on the master and any slave. Its job is to search the TV +listing for the shows you have requested and assign recordings to the TV +tuner cards. If none of the shows that you've chosen overlap, it simply +records all of them. However, if there are shows where the beginning +and end times overlap, the scheduler follows rules that you've specified or +makes logical decisions about what would be best if you haven't expressed your +preference. Further, the "Upcoming Recordings" page allows you make specific +decisions about what you really do and don't want to record.</P> + +<H2><A NAME="ss12.1">12.1</A> <A HREF="#toc12.1">Record Types</A> +</H2> + +<P>When you choose a show that you would like to record from the +Options Page, there are eight different types of rules to help the +scheduler find which showings you would like to record.</P> +<P> +<UL> +<LI>Single Record -- record only this title at this specific time and +this station. This is the best way to be sure that a certain showing will +be recorded. However, if the TV listings change and the show is not broadcast +at that time, the show will not be recorded but will be marked as Not Listed +to let you know that you should investigate. +</LI> +<LI>Find One -- this will record a title once from any of the times +that appear in the TV listings. This is useful for recording a movie +or special that has multiple showings because it allows the scheduler +to choose one that doesn't conflict. It is not a good choice for +recording a single episode of a series because it records the first +available showing of the title without regard to the episode +information. +</LI> +<LI>Record Weekly -- this records a show whenever the title is listed +on the same channel, weekday and time. Note that if the TV station +changes the schedule for a special episode, it would not be +recorded. However, you can add a Single record for the special +episode. If there are no matching showings in the TV listings, +a Not Listed item will be added to your schedule for the next +time slot to let you know that you should investigate. +</LI> +<LI>Find Weekly -- this will record a title once per week from any +of the times that appear in the TV listings beginning from the time of +the showing that was selected when the rule was set. This is useful +for news, current events or other programs where the same episode is +shown several times each week but the listings may not include +descriptive information. This may not be a good choice if there are +different episodes shown during the week. +</LI> +<LI>Record Daily -- this records a show whenever the title is listed +for the time and station on any day of the week. Here again, a show +will not be recorded if the time was altered by the station. If there +are no matching showings in the TV listings, a Not Listed item will be +added to your schedule for the next time slot to let you know that you +should investigate. +</LI> +<LI>Find Daily -- this will record a title once per day from any +of the times that appear in the TV listings beginning from the time of +the showing that was selected when the rule was set. This is useful +for news, current events or other programs where the same episode is +shown several times each day but the listings may not include +descriptive information. This may not be a good choice if there are +different episodes shown during the day. +</LI> +<LI>Channel Record -- records one showing of each unique episode from +any of the times the title is listed on this station. This is perhaps +the most common rule to use for most shows. +</LI> +<LI>Record All -- records one showing of each unique episode from +any of the times this title is listed on any channel. This can be +useful if a station has sister stations where shows are rebroadcast +allowing the scheduler to record rebroadcasts on the other station +when the original airing cannot be recorded.</LI> +</UL> +</P> + +<H2><A NAME="ss12.2">12.2</A> <A HREF="#toc12.2">Scheduling Options</A> +</H2> + +<H3>Priority</H3> + +<P>By default, all shows you select have equal value to the +scheduler. There are a set of rules to make good choices when +two or more shows are in conflict. However, priority values let the +scheduler know what you prefer so that it can set the schedule based +on your preferences.</P> +<P>Initially, recording rule priority values are set to zero. You may choose +to leave everything at "0" and let the scheduler follow rules to guess +what you might prefer when there are conflicts. However, if you have +one or two favorite shows, you may want to increase the priority +value so the scheduler will know that you would prefer recording +these over other shows. You might use certain values to rate shows +so that all favorites are 2. good shows are 1 and extra 'filler' +shows are all -1 for example. You could sort each title on the "Set +Priorities" page to have a unique value so the scheduler can know +which show you'd prefer versus any other show. The choice and style +are entirely up to you. However, the more information you give to +the scheduler, the more likely it will make the choices you would +prefer in the first place.</P> +<P>The scheduler choices are based on the total priority for a showing by +adding up all priority factors that match the showing. By default, most +of these factors are "0" but you may use any combination to express your +likes and needs.</P> +<P> +<UL> +<LI>Per record rule -- this is the "priority" selection in the "Scheduling +Options" section of the options page and this value is included for any +showings that match the recording rule. You may choose to only use these +values and not use the other factors for the sake of simplicity and clarity.</LI> +<LI>Per record type -- Setup->TV Settings->Recording Priorities->General allows +you to add to the priority based on the type. It may make sense to increase +the value for "Single" so that by default they have an extra advantage over +other shows. The default is +1. You may want to decrease the value for Find +rules so that they will be less likely to interfere with regularly scheduled +shows and will be more likely to record in a non-conflicting time instead. +The default is -1.</LI> +<LI>Per channel -- Setup->TV Settings->Recording Priorities->Channel Priorities +can be useful if you believe that you prefer any of the shows on certain +channels. This would give all shows on a channel an advantage by default.</LI> +<LI>Input priority -- in the "mythtv-setup" program, the "Input Connections" +section allows you to add additional priority in the "Input priority". +This is simply another priority factor but has an interesting effect. If a +card input has a higher value than the other cards, the scheduler will see +that you would rather record showings of episodes on this input rather than a +showing on other inputs. If you have multiple cards of different quality, +you may want to set input priority to encourage the scheduler to record +shows on your best card(s) whenever possible. This can also be useful if you +have multiple video sources which include the same stations. For example, +with digital and analog cable you could increase the digital cable input +preference by 1 to tell the scheduler that you want to record from the +digital channel whenever possible but the channel on the analog input could +still be used when the digital input is busy.</LI> +<LI>Custom Priority -- this allows you to add any specialized factors you +would like in order to influence scheduling decisions. See the +<A HREF="#Custom Priority">Custom Priority</A> section below.</LI> +</UL> + +For any single showing of any show you've chosen to record, these factors +are added together to find the "total priority". This is the priority that +the scheduler uses to decide which showings are given the first choice when +filling in the schedule.</P> +<P>The scheduling priority of a show may also be used to determine +auto-expiration of recordings when disk space gets full (see +<A HREF="#Auto-Expire">Auto-Expire</A>, below).</P> + +<H3>Duplicates</H3> + +<P>Singles will record without regard to duplicate matching.</P> + +<P>The standard recurring methods of All, Channel, Weekly and Daily use the +descriptive information in the TV listings to try to record only one showing +of each unique episode. However, This goal is sometimes complicated by the +fact that the stations may not include a description for a specific episode +but use a generic description for the series instead. When there is a +generic description, the default behavior is to assume that it may be an +episode that you have not seen and to record it for you. One of the +duplicate matching options is "Record new episodes only". If this is +selected, listing that have an original air date of more than 14 days +earlier are considered repeats and are not eligible to record. Generally, +generic episodes will be marked as repeats also.</P> + +<P>Because of generic episodes and other situations, MythTV offers an +alternative approach where shows may be recorded by choosing from multiple +showings even when the descriptive information is not reliable. All of the +"Find" record types look for matching titles in the listings. If there is a +showing with specific episode information and that episode has recorded +before, that showing is marked as previously or currently recorded. The +scheduler will then choose to record the earliest non-conflicting showing +from any of other remaining showings regardless of the descriptive +information. Generally, Find One is most useful for movies or specials and +the Find Daily and Find Weekly rules are best for news or current events +shows that are repeated. However, these may be useful in other situations +where the standard recording rules may not work correctly.</P> + +<H3>Conflicts</H3> + +<P>As you add more shows that you would like to record, the scheduler +will eventually encounter conflicts. If there are two shows at the +same time and you have two or more TV tuner cards, both shows will +record. However, if there are more shows than cards, the scheduler +will have to decide what it thinks it should not record based on the +information you have given. If you see an unexpected situation you +are not "stuck" with the scheduler's choice. You can still tell the +scheduler exactly which shows you do want to record and/or don't +want to record in any situation.</P> + +<H3>Scheduling decisions</H3> + +<P>Here are the actual decisions made by the scheduler as it fills in the +schedule.</P> +<P> +<UL> +<LI>Currently recording beats not currently recording -- A recording +in progress can not be moved to another input or time so it "wins" +its current timeslot. +</LI> +<LI>Single, Daily, or Weekly rules with no match are marked Not Listed -- +If these or Overrides do not match the current listings because the +listings have changed, they are added to the schedule and marked to +indicate that they will not record. +</LI> +<LI>Rules that could record beat rules that can not record a showing -- +If two rules match the same showing of a program, a rule marked as inactive +or a showing marked as a repeat, for example, yield to the other rule. +</LI> +<LI>More specific record type is used in place of less specific -- If +two rules match the same showing of a program, preference is given to +Don't Record then Override, Single, Find One, Record Weekly, Find Weekly, +Record Daily, Find Daily, Channel and finally All. +</LI> +<LI>Higher total priority beats lower total priority -- This is the +core of the scheduling process. Episodes of the highest priority show +are placed on the first available input followed by the next highest +priority show and so on. +</LI> +<LI>Future start time beats past start time -- If there is an +episode in progress and also a later showing of the same episode, it +is better to record the complete episode. If there isn't another +showing, it will start recording immediately to record the remaining +portion. This should only happen if you add a new rule while the show +is in progress or if the master backend is started after the start time +of a scheduled show. +</LI> +<LI>More specific record type beats less specific record type -- If +two shows are on at the same time and have the same total priority but +different types they will be sorted by Single then Find One, Record +Weekly, Find Weekly, Record Daily, Find Daily, Channel and finally +All. This only applies if the priorities are the same. +</LI> +<LI>If both start times have passed, later start time beats earlier start +time -- This attempts to miss the least amount of time. +</LI> +<LI>If neither start time has passed, earlier start time beats later +start time -- This helps assure that the earliest showing of an episode +has the advantage. +</LI> +<LI>Lower input id beats higher input id -- The scheduler fills in +open time slots on the first available input for the video source. The +next input is used when there is another show already placed for the +card of the first input. +</LI> +<LI>Older record rule beats newer record rule -- If two shows are still +equal after all of these other checks, the show whose record rule was added +first is preferred over a more recent addition. +</LI> +<LI>Postpone showings to resolve conflicts -- If Reschedule Higher +Priorities is set or if a conflict has the same priority as a show +that was scheduled at the same time, the scheduler will check to see +if a scheduled show can be moved to another input or later matching +showing without creating a new conflict so that the conflicting show +can be scheduled to record. +</LI> +</UL> +</P> + +<H3>Reschedule Higher Priorities</H3> + +<P>Setup->TV Settings->Recording Priorities->General has a checkbox for +"Reschedule Higher Priorities" which tells the scheduler to try to be a +little smarter in certain situations. If this is checked, the scheduler will +look for situations where a show cannot record because all inputs for the +channel are used for higher priority shows. It will check to see if any of +the other shows could be recorded at another time so that the conflicting +show can be recorded in its place.</P> +<P>Generally, this is a good strategy but there are tradeoffs. If a higher +priority show is postponed, you will not get to watch it until it is +recorded in the later timeslot. There is also a risk that the TV listings +may change and the later showing may go away. In this rare case the higher +priority show may never record. On the other hand, if you do not use this +option you will miss recording some lower priority shows unnecessarily +unless you manually make similar changes.</P> +<P>By using Reschedule Higher Priorities, the scheduler will do a better job of +recording as many of your shows as possible when left unattended. It will +also be easy to see that shows have been marked to record at a later time. +You can then decide for yourself when you would prefer to record the first +showing by clicking "Record anyway".</P> + +<H3>Controlling Your Schedule</H3> + +<P>The Manage Recordings->Upcoming Recordings page is your control center +for the MythTV scheduler. Unlike other DVR systems, this one page gives you +all of the information and tools you need to see all of your alternatives +and make whatever adjustments you desire.</P> +<P>The upper half of the screen has a scrollable box listing items that match +your record rules sorted by time. The lower half shows the details for the +highlighted item. There are two 'views' available. Press "1" to include all +of the items that match record rules even if they do not need to be +recorded. Press "2" to focus on just the things that will record and items +that may need your attention. The message in the upper right-hand corner +will remind you when there are conflicts that would prevent one or more +shows from being recorded.</P> +<P>The items in the list are colored in the record color for things that +will record, white for things that may need attention, gray for those +that do not need to record and yellow when there is a time conflict. +Items at the top of the list may also be highlighted indicating that the +recording is in progress.</P> +<P>Along with the channels, start times and titles, the right-hand column has +a status code. Numbers indicate which card number has been assigned to +record the show. Letters are used to indicate the reason that something +will not be recorded. Just below the box is a short status message for the +highlighted item that indicates the type of record rule that was matched, +the "total priority" for this showing and a one or two word explanation of +the status code. If you press SELECT, you will see more information about +the status.</P> +<P>There are a few status codes that may require your attention. "C" indicates +that there are more overlapping shows to record than there are TV tuners to +record them. "L" indicates that the scheduler found that it may be better to +record a later showing of this episode. These states happen as a result of +your choices and should normally reflect your preferences. However, you may +notice situations where you would like to modify the scheduler's initial +choices.</P> +<P>The first thing you can do is to highlight an item and press INFO to +see the recording options page. From this page you can change the +record rule type, the duplicate matching rules, or raise or lower the +priority to resolve whatever problem you noticed.</P> +<P>Additionally, you can treat any individual showing as an exception that you +do want to record or don't want to record. To use these "override" features, +highlight the item and press SELECT. You will see a message explaining the +current status and at least an "OK" button to exit without making changes.</P> +<P>For items scheduled to record, there will be a button for "Don't record" +which will prevent recording this showing but will still allow the same +episode to record in the future. If there is episode description +information, you may also see a button for "Never record". This prevents +recording this showing and tells MythTV to remember that this is an episode +that you've seen or don't need to see if it is ever in the TV listings +again.</P> +<P>For items that are not scheduled to record, the message will describe the +reason and in the case of "C" or "L" it will include a list of the shows +that are scheduled to record instead. For any item that could potentially be +recorded there will be buttons for "Edit Options" and "Add Override". "Edit +Options" will allow you to change the options for the existing record rule +such as raising the priority so that the show will record. These changes +would apply to this and all future showings that match this record rule. +"Add Override" will allow you to set options that apply to the specific +showing without affecting the recurring record rule.</P> +<P>If you return to an override page after an override has already been set, +you will also see a "Clear Override" to undo your changes. This option makes +it very easy to try out some "what if" attempts when deciding on your best +strategy in a difficult situation.</P> +<P>For a recording in progress, there will be a "Change Ending Time" button. +This will take you to the options page for a Single or Override or create +an Override if it is a recurring rule. Here you can go to the Recording +Options section to change the program end time offset. If you extend the +end time so that it overlaps upcoming recordings, the schedule will change +to accommodate the new end time. This may cause a conflict or later showing +even for a show with higher priority. Therefore, it is a good idea to +check your schedule after changing the end time of a recording in +progress.</P> + +<H2><A NAME="ss12.3">12.3</A> <A HREF="#toc12.3">Storage Options</A> +</H2> + +<H3>Recording Profile</H3> + +<P>Each recording rule can be configured with a different recording +profile. For example, colorful cinematography can be configured with a +"High Quality" profile, while 'talking heads' interviews shows can be +configured with a "Low Quality" profile. These recording profiles need to +be configured before using them (see +<A HREF="#Recording">Recording</A>, +above).</P> + +<H3><A NAME="Recording Group"></A> Recording Group </H3> + +<P>For organization of the "Watch Recordings" screen and the MythWeb +interface, recordings can be assigned into "recording groups".</P> + +<H3><A HREF="#storagegroups">Storage Groups</A></H3> + +<P>This allows you to select any special "Storage Groups" you may have +created to determine where recordings from this rule should be stored +on your disks. The "Default" storage group is always available.</P> + +<H3><A NAME="Playback Group"></A> Playback Group </H3> + +<P>This selects a set of pre-configured playback parameters which can be +created and edited in Setup->TV Settings->Playback Groups. When the +recording is played, the values from this playback group will be +used. This allows you to choose a default time stretch value, skip and +jump amounts appropriate for this type of television program.</P> + +<H3><A NAME="Auto-Expire"></A> Auto-Expire </H3> + +<P>MythTV will "autoexpire" old recordings to make room for new recordings +when disk space gets filled up. This option can be set to "Don't allow +auto expire" to prevent these recordings from being automatically deleted +when disk space fills up.</P> + +<P>The default setting is for all scheduled recordings to be eligible +for auto-expiration; this can be changed in the Settings->TV +Settings->General page by manipulating the "Auto Expire Default" +checkbox.</P> + +<P>The default auto-expire policy is "Oldest Show First"; the oldest +recordings are deleted first. The "Lowest Priority First" method +chooses to expire the lowest-priority recordings first.</P> + +<H3>Episode Limit</H3> + +<P>An episode limit can also be configured to limit the maximum number +of episodes recorded of a single series, to restrict that series' disk +usage. If this is set, you can further decide what to do when this +limit is reached; either stop recording that series, or to delete the +oldest episodes in favor of the new ones.</P> + +<H2><A NAME="ss12.4">12.4</A> <A HREF="#toc12.4">Post Recording Processing</A> +</H2> + +<H3>Commercial Flagging</H3> + +<P>Select whether or not to automatically flag commercials for these +recordings. Commercial Flagging parameters can be set in +Setup->TV Settings->General.</P> + +<H3>Transcoding</H3> + +<P>Select whether or not to automatically transcode recordings to save +disk space. Before using this, you must first enable auto-transcode in +the recording profile and configure the transcoding parameters; see +<A HREF="#Recording">Recording</A>, above.</P> + +<H3>User Jobs</H3> + +<P>User Jobs allow you to configure up to 4 custom commands to run on +recordings. They can be configured in mythtv-setup. The following +tokens have special meaning when used in the User Job commands:</P> +<P> +<UL> +<LI>%DIR% - the directory component of the recording's filename</LI> +<LI>%FILE% - the filename component of the recording's filename</LI> +<LI>%TITLE% - the title of the recording (e.g., name of the series)</LI> +<LI>%SUBTITLE% - the subtitle of the recording (e.g., name of the +episode)</LI> +<LI>%DESCRIPTION% - description text for the recording (from guide +data)</LI> +<LI>%HOSTNAME% - the backend making the recording</LI> +<LI>%CATEGORY% - the category of the recording (from guide data)</LI> +<LI>%RECGROUP% - the +<A HREF="#Recording Group">recording group</A></LI> +<LI>%CHANID% - the MythTV channel ID making the recording</LI> +<LI>%STARTTIME% - the recording start time (YYYYMMDDhhmmss)</LI> +<LI>%ENDTIME% - the recording end time (YYYYMMDDhhmmss)</LI> +<LI>%STARTTIMEISO% - the recording start time in ISO 8601 format +(YYYY-MM-DDTHH:MM:SS)</LI> +<LI>%ENDTIMEISO% - the recording end time in ISO 8601 format</LI> +<LI>%PROGSTART% - the recording's start time (from guide data; +YYYYMMDDhhmmss)</LI> +<LI>%PROGEND% - the recording's end time (from guide data)</LI> +<LI>%PROGSTARTISO%, %PROGENDISO% - the recording's start and end +time in ISO 8601 format.</LI> +</UL> +</P> + +<H2><A NAME="ss12.5">12.5</A> <A HREF="#toc12.5">Advanced Recording Options</A> +</H2> + +<H3>Creating Power Search rules with Custom Record</H3> + +<P>MythTV's "Custom Record" feature gives you unlimited control for creating +specialized search recording rules to meet your needs. It allows you to +choose your criteria to search for matching shows based on any of the +information in the program listings, channel information, time functions and +more. This goes beyond the capabilities of any other DVR system and it is +unlikely that this level of scheduling customization will ever be available +in any commercial DVR system.</P> + +<H3>Getting Started</H3> + +<P>Go to Schedule Recordings->Custom Record. This page, helps you build a +database search one clause at a time. Each added clause further limits +which showings will be matched in the TV listings. You can test the +search at any time and when you are done, you can save your search as a +recording rule.</P> +<P>To familiarize yourself with how you can create custom rules, create a +simple rule to record "Nova" only in primetime.</P> +<P>The first item at the top of the page allows you to edit an existing rule +or create a new rule. Leave it on "<New rule>". Arrow down to the +third item which says "Match an exact title". Right and left arrows would +allow you to select any of several prefabricated pieces or full examples +but leave it on the default for now. Arrow down to "Add this example +clause" and press SELECT (Enter or Space on a keyboard). The large text +box should now show: +<BLOCKQUOTE><CODE> +<PRE> + program.title = 'Nova' +</PRE> +</CODE></BLOCKQUOTE> + +As you have probably guessed, this says that we want to search for all +programs with the title "Nova" regardless of the time, day, channel, etc.</P> +<P>If you do not receive a PBS station that carries "Nova" or would like to use +another title, edit the title by pressing the down arrow to highlight the +text box and right arrow over the the word "Nova". If you are using a +keyboard you can simply delete the four letters and type a different title +between the quotes. With a remote control, you can do 'cell phone' style +text entry with the number pad. The delete key is the "X" in the grouping +for "1", zero is grouped with "9" and "0" acts as the "Caps Lock" key. You +can press ENTER in the text box to popup a virtual keyboard.</P> +<P>Note: the text box honors many familiar Emacs control keys. It is also +possible to cut and paste text into the text box so you can edit with a +favorite editor or insert a rule sent in email or from other sources.</P> +<P>In any case, choose a title that is shown both in primetime and late night +or daytime. Next, click the "Test" button. You should see a list of the +upcoming episodes for "Nova" just as if you had clicked the Upcoming +button for "Nova" elsewhere in MythTV.</P> +<P>Press ESC to go back to the Custom Record page. Move to the example +selector then press the right or left arrows until you find "Only in +primetime". Click "Add this example clause". You should now see: +<BLOCKQUOTE><CODE> +<PRE> + program.title = 'Nova' + AND HOUR(program.starttime) >= 19 + AND HOUR(program.starttime) < 23 +</PRE> +</CODE></BLOCKQUOTE> + +Click "Test". You should now see a shorter list with only the showings that +begin between 7PM and 11PM. To create a rule for this, press ESC to go back +to the custom page and move to "Rule Name:" then type "Nova" or anything +else you would like. This is only a label and will not affect the search +results. Once a name has been entered, the "Record" button will light up. +Click this to enter the recording options page. If you named it "Nova" the +title will say "Nova (Power Search)". Set whatever options you would like +then click "Save these settings". You now have a special rule to record +"Nova" but only when it is shown in primetime.</P> +<P>You can make further modifications to this rule by returning to the Custom +Record page then press the right or left arrow keys on "Edit Rule:" until +you find "Nova". You can experiment and test but the saved rule will not +be updated until you click "Record" then "Save these settings".</P> +<P>To remove this, or any other rule, you can go to the "Recording Priorities" +page, arrow down to the title, press Enter and change the the recording type +to "Do not record this program" then "Save these settings".</P> + +<H3>How it Works</H3> + +<P>MythTV stores TV program information in a database and uses the Structured +Query Language (SQL) to access the data. Information about each TV program +is stored in the 'program' table and information about each TV station you +receive is stored in 'channel'. These two tables are used in the scheduler +queries and their columns are available to be used in your rules. The rules +you create are stored in 'record'.</P> +<P>Normal rules in MythTV simply match the title in the rule with the titles +in the 'program' table. MythTV also has search rules for "Titles", +"Keywords" and "People". These store the key phrase in the description +column of the rule and includes them in specialized SQL replacements for +the normal title check. There is also a type called "Power Search" which +takes the raw SQL in the description as the replacement for title +matching.</P> +<P>Custom Record is a tool to help you build valid SQL for Power Search rules. +You do not need to be a SQL expert to use Custom Record because the +examples are known to work correctly and are usually self-explanatory so you +can choose the pieces you need then modify them. Many powerful solutions to +unique problems are possible by combining the examples. With some creativity +and some knowledge of SQL, the possibilities are limitless.</P> + +<H3>Common Tricks and Tips</H3> + +<P>The example clauses marked "complete example" are actual rules that have +been used to address specific problems. You may find that some of these +are useful for you as-is or with slight modifications. These show off how +powerful custom rules can be but there are also several simple idioms that +you may find useful for many of the shows you would like to record.</P> +<P>Wait for a known title -- If there is a movie that you anticipate will be +televised in the coming months but is not yet in the listings, you can +select "Match an exact title", edit the movie title, click "Record" then +choose "Record one showing of this title". The rule will wait weeks, months +or years until this title shows up in your listings then it will record one +showing. These rules have no impact on the scheduler throughout the day and +only take a tiny fraction of a second when the master backend starts or when +the listings are updated.</P> +<P>Silence series out of season -- "Celebrity Poker Showdown", for example, +will have new episodes for a while then long periods where reruns are shown +dozens of times per week. By checking the previously shown flag you can +create a rule that will only match new episodes. Therefore, your schedule +won't be polluted with dozens of entries marked as "Repeat" or "Previously +Recorded". +<BLOCKQUOTE><CODE> +<PRE> + program.title = "Celebrity Poker Showdown" + AND program.previouslyshown = 0 +</PRE> +</CODE></BLOCKQUOTE> + +This allows you to keep rules for your favorite shows that are dormant while +out of season but will spring back to life when new episodes appear.</P> +<P>Choose showings on certain days -- Several cable stations will show their +highest rated shows a dozen on more times per week. However, the scheduler +only needs two or three choices to do a good job of making a flexible +choice. +<BLOCKQUOTE><CODE> +<PRE> + program.title LIKE "Celebrity Fit Club%" + AND DAYNAME(program.starttime) = "Sunday" +</PRE> +</CODE></BLOCKQUOTE> + +This says to choose any showing of an episode that hasn't been recorded +when it appears on Sunday. This prevents all the other showings during the +week from being listed in the schedule.</P> +<P>Notice the word "LIKE" and the "%" at the end. This does wildcard matching +so that this would match even if the title ended with "2". "III" or +":Revenge of the Snapple Lady". This can be useful where the title may +change from one season to the next like "Survivor: %", "Big Brother%" or +"The Amazing Race%".</P> + +<H3>Working with SQL</H3> + +<P>As you experiment, it is possible that you may misplace a quote or mistype a +word. If there is a mistake when you press "Test" or "Record" you will see +an error message returned from the database. This will usually give you a +good idea about what needs to be fixed. However, for more subtle MySQL +syntax errors, you can find more information in the documentation at +<A HREF="http://dev.mysql.com/doc/mysql/en/">http://dev.mysql.com/doc/mysql/en/</A>. This contains a lot of +information that can be useful for Power Search rules such as the "Date and +Time Functions". There are many other good resources for SQL on the Web.</P> +<P>While the example clauses demonstrate how to use many of the data columns, +you can get a more complete list of all the columns that are available by +using a MySQL client program: +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u mythtv -pmythtv mythconverg +mysql> describe program; +mysql> describe channel; +</PRE> +</CODE></BLOCKQUOTE> + +This will show the names of all of the columns along with their type and +default value. Most are easy to understand but a few need some explanation +in order to use them effectively with Power Search. +<UL> +<LI>"program.category_type" holds one of these exact four strings: "movie", +"series", "sports" or "tvshow". +</LI> +<LI>"program.airdate" is a string representing the year of release for +movies and may have no meaning for other types of shows. +</LI> +<LI>"program.stars" is a floating point number from 0.0 to 1.0. On a +four star scale, 1.0 would be four stars, 0.75 would be three stars and so +on. +</LI> +<LI>"program.originalairdate" if provided is the date when a show +was, or will be, first televised. This may be useful for finding +episodes before or after a certain date such as finding just the +original series of "Battlestar Galactica". +</LI> +<LI>"program.previouslyshown" is a column created by MythTV to try to +determine if a showing is more than 14 days after its original air date or +if the show was marked as a repeat and did not have a date for the first +airing. If this is "0" it usually means that this is a brand new show or a +rebroadcast within the first two weeks. +</LI> +<LI>"program.generic" is a column created by MythTV to try mark +showings for a series where the specific episode information is not +included. When these generic showings appear, it is impossible for the +system to determine if they are repeats of the same episode(s) or if +they are all different episodes. +</LI> +<LI>"program.first" is a column created by MythTV to mark the first +showing in the current listings for each episode, movie or special. +Choosing to match only the "first" showing can be useful for sports +that are brodcast live then repeated. +</LI> +<LI>"program.last" is a column created by MythTV to mark the last +showing in the current listings for each episode, movie or special. +If a showing is marked both "first" and "last" then it is the only +showing of that program in the current TV listings. +</LI> +<LI>"program.programid" is the Tribune Media Service database record +identifier for each program description. In general, these start with a two +letter prefix, MV, EP, SP or SH that correspond to the +"program.category_type". For most, the last four digits are "0000" except +EP where the last four digits are the episode number in the series. Note +that these are generated by TMS and not the show's producers but they are +usually in the same order as the original air dates for the episodes. +</LI> +<LI>"program.videoprop" also "audioprop" and "subtitletypes". +These columns contain bit flags for a variety of attributes that +may be associated with a program. These are filled with information +offered by the TV listings provider. However, your listings source +will not have information for all of the available flags. Therefore, +some of these may not be useful for your search rules. This information +is organized in "sets" and the MySQL function FIND_IN_SET() can be used +to test for any of these flags. For example: +<BLOCKQUOTE><CODE> +<PRE> +FIND_IN_SET('SURROUND', program.audioprop) > 0 +</PRE> +</CODE></BLOCKQUOTE> + +would be true for the programs where the surround sound bit is present. +To see all of the available attribute names: +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u mythtv -pmythtv mythconverg +mysql> SHOW COLUMNS FROM program LIKE '%prop'\G +mysql> SHOW COLUMNS FROM program LIKE 'subtitletypes'\G +</PRE> +</CODE></BLOCKQUOTE> +</LI> +</UL> + +Finally, if you are doing something very experimental and a column is not +giving you the results you had anticipated, you can always check the MythTV +source code to see exactly how a column is used. The open source for MythTV +is available from +<A HREF="http://www.mythtv.org/">http://www.mythtv.org/</A> .</P> + +<H2><A NAME="ss12.6">12.6</A> <A HREF="#toc12.6">Scheduling with more than one Input</A> +</H2> + + +<P>MythTV is designed to allow recording television programs from one or more +service providers, or video source, on one or more video input from each +provider. Some inputs may not be allowed to record at the same time as +each other while others may record simultaneously.</P> +<P>A television station may be broadcast on more than one channel from one +provider or may be available on channels from two or more providers. If a TV +station is available from more than one source, the video quality or type of +broadcast may differ. Therefore, MythTV allows you to control how you would +like the scheduler to select the best channel and input for a show which is +available on more than one input or more than one channel.</P> + +<H3>Mutually Exclusive Inputs</H3> + +<P>A single TV capture card may have video connections to more than +one of its inputs and each input may be from a different service. The card +may only be allowed to record from one of these inputs at one time because +there is only one encoder on the card that actually captures the content.</P> +<P> +<FIGURE> +<EPS FILE="BlockDiagramofavideocapturedevice.eps"> +<IMG SRC="BlockDiagramofavideocapturedevice.png"> +<CAPTION></CAPTION> +</FIGURE> +</P> +<P>These are mutually exclusive meaning that only one input or the other +may record at a given time but not both.</P> +<P>Usually, inputs on different cards can record at the same time +but two or more inputs on the same card cannot. However, there are cases +where inputs on different cards should not be allowed to record at the +same time, for example, a firewire card and s-video analog card connected +to the same set top cable box.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +| +| coax +--------------+ firewire ------------------+ +| .-=|Cable Provider|=------------=| Card 1 input 1 | HDTV +| | |HD/Cable STB |=--. +-----|||||||||||| +| | +--------------+ | s-video ------------------+ +| | `---------=| input 2 | Digital +|wall | coax | Card 2 | +|=---=^=------------------------------=| input 3 | Cable +| +-----|||||||||||| +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Input 1 and input 2 receive content from the same set top box and the +channels can not be tuned independently. Therefore only one of these two +inputs should be used at any given time. The solution is to create an "Input +Group" with <B>mythtv-setup</B> in "Input connections". Including these +two inputs in the same Input Group will tell the scheduler that these are +mutually exclusive and may not record at the same time. Inputs 2 and 3 are +automatically mutually exclusive because they are on the same card so there +is no need to create an Input Group for these inputs.</P> +<P>Cards such as the Hauppauge PVR-500 are able to record as two cards +simultaneously because it has two MPEG-2 encoders and each encoder appears +as a separate device. DVB cards may be allowed to capture content from more +than one channel at a time if the channels are in the same MUX.</P> + +<H3>Stations, Channels and Video Sources</H3> + +<P>Although we may be accustomed to thinking of a broadcast station and its +channel number as being synonymous, stations and channels are very different +things. A "station" is in a building with wires and employees. A "channel" +is a carrier frequency or digital ID that carries a broadcast stream. The +same TV station may be broadcast over different frequencies in different +cities or by different providers in the same city. The same frequency will +carry different stations in different cities. In the digital realm of DVB +and ATSC (HDTV), it is even possible for a single frequency to carry +multiple program streams but each of these streams of content are actually +different channels that the receiving devices can 'tune' to independently.</P> +<P> +<UL> +<LI>Station: building</LI> +<LI>Channel: frequency</LI> +</UL> +</P> +<P>In MythTV, a "video source" is a set of channels from a provider, or over +the air, that can be received by an input. The set defines the channels and +the broadcasters primarily associated with each of those channels. If you +have more than one device or cable from the same provider connected to more +than one card and input, you only need to create one video source in +mythtv-setup then associate that one source with each of these connected +inputs. This will let your MythTV system know that the same channels and +their TV listings are available to be recorded from any of these inputs.</P> +<P>For example. A MythTV system may have two capture cards. Both have a cable +connected to the coaxial connectors. These cables carry the local cable TV +service. In mythtv-setup, the user should create one "Video source" called +"Cable", for example. Under "Input connections", "Cable" should be +associated with each of the two tuner inputs. The scheduler will then know +that any program on one of the channels from the "Cable" source could be +recorded by either card from the card's tuner input.</P> +<P>You need to create a different video source for each provider or service +that has a different set of channels. Each input with a connection to that +service should be associated with the video source for that service so the +system will know which set of channels are available for each of your active +inputs.</P> +<P>Let's say that this user also has one digital cable set top box. The digital +cable service carries channels that are not available over basic cable. The +user would create another source called "Digital". This set top box is +connected to the second card by S-Video so under "Input connections", +"Digital" is associated with the S-Video input of card 2. The system would +then know that programs on channels from the Digital source can only be +recorded from this input. Further, the scheduler understands that it can +only record one show at a time from card 2 so it can assign Cable or Digital +shows to the card but not both at the same time.</P> +<P>Some TV stations may be broadcast over a channel from the Cable source and +also broadcast over a channel from the Digital source. Note that two +channels carrying the same primary station may not have the same TV listings +due to carrying the primary station part time, including local programming +exclusive to one of the channels, the channels may be in different +timezones, etc. Listings information must be associated with each channel +even if two or more channels report that they carry the same station.</P> + +<H3>Order of Inputs</H3> + +<P>By default the scheduler chooses the first (lowest numbered) input which has +a showing of the scheduled program as it fills the schedule. If a lower +priority show is on at the same time as a higher priority show that has been +assigned to input 1, then input 2 will be used next and so on. Therefore, +configure your best card and input first and next best card and input +second. There may be differences in the type or brand of capture card, +signal quality from the cable, system resources such as disk space, CPU, +etc. By configuring your best input first, more recordings, and your highest +priority recordings, will use that input.</P> +<P>A common situation is that a newer and better card is added last. For +example, you may initially setup your system with two analog cable cards and +then add a HDTV card. If NBC is on a cable channel and "The Apprentice" is +shown in HDTV on an NBC HD channel, the scheduler would still prefer analog +inputs 1 and 2 over the new HD input 3.</P> +<P>So, if you'd like the scheduler to prefer a new source, the simplest thing +is to run <B>mythtv-setup</B> and "Delete all capture cards" then enter +your cards and inputs in your preferred order. This will not remove your +sources and channels - you want to keep those and only renumber your cards +and inputs. In this example, once the changes have been made and the Master +Backend is restarted, the scheduler would then choose "The Apprentice" in HD +on the new input 1 and only use the analog inputs (now numbered 2 and 3) +when the HDTV input was occupied with another show.</P> + +<H3>Matching Callsigns</H3> + +<P>If a recording rule is a type that can record from any channel, "The +Apprentice" would match for any channel that shows episodes which may +include CNBC or BRAVO. However, for Single, Timeslot, Weekslot or Channel +rules, "The Apprentice" would only match showings on the selected station as +identified by the "callsign". For example, KVBC is an NBC affiliate on +channel 3. Channel 733 is KVBCDT which is HDTV over cable from the same +station. If a Single record rule was set for "The Apprentice" on KVBC +channel 3, it could not record this showing from KVBCDT on 733. If 733 was +chosen when the rule was saved, channel 3 could not be used to record.</P> +<P>However, the "Channel Editor" in mythtv-setup can be used to change the +Callsign for channel 733 to "KVBC". MythTV would then understand that both +of these channels are from the same broadcast station. Assuming the HDTV +input was input number "1", "The Apprentice" would record on 733. If, +however, this HDTV input already had a higher priority show assigned to it +in that time slot, "The Apprentice" would be assigned to KVBC channel 3 on +input 2.</P> +<P>Having two channels with the same callsign may affect how program +information is shown in mythfrontend. If two sources have the same callsign +and channel number, the program guide and program lists will only show one +instance of the channel number and callsign. If the same callsign is on two +different channel numbers, both will be shown and if two sources have +different callsigns with the same channel number, both of those will be +shown.</P> +<P>Continuing with the example above, the Electronic Program Guide would +include rows for both "3 KVBC" and "733 KVBC". If channel 3 KVBC was also +included in the Digital cable source, the EPG would still include just one +line for "3 KVBC" even though there are two different channels, Cable and +Digital, with this identification. Regardless of how these are displayed and +which "KVBC" channel you select to add a rule to record "The Apprentice", +the scheduler will pick the best channel, source and input to record "The +Apprentice" on "KVBC".</P> + +<H3>Using Priorities to Prefer an Input</H3> + +<P>The fundamental concept to keep in mind is that the MythTV scheduler will +choose the lowest numbered input available when showings have the same +priority. If there are factors that cause two showings of the same show to +have different priorities then the higher priority showing will be +considered before the showings with lower priority.</P> + +<H3>Input Priority</H3> + +<P>"Input Connections" in mythtv-setup includes a box to set "Input priority" +which defaults to "0". If a value is set, that amount will be added to the +"total priority" for showings on that input. This can be used to influence +using favored cards or not using less favored cards unless necessary.</P> +<P>Let's say the "The Apprentice" is on at 8:00pm with a priority of 3. "Who +Cares" is -2 and an episode is shown at 8:00pm then repeated at 11:00pm. The +scheduler would assign "The Apprentice" to card 1 and "Who Cares" to card 2 +at 8:00pm. If the input priority for the input on card 2 was changed to -1, +"Who Cares" would have a total priority of -2 for showings on card 1 and -3 +for showings on card 2. The scheduler would assign "The Apprentice" to card +1 at 8:00pm and "Who Cares" to card 1 at 11:00pm when the better card is +available. If there was another higher priority show at 11pm, the next best +choice for "Who Cares" would be card 2 at 8pm with the priority -3.</P> +<P>Card 1 and 2 have input priority "0":</P> +<P> +<FIGURE> +<EPS FILE="Card1 Pri 0 Card2 Pri 0.eps"> +<IMG SRC="Card1 Pri 0 Card2 Pri 0.png"> +<CAPTION></CAPTION> +</FIGURE> +</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> + Time Title Priority Card Status + 8:00 The Apprentice +3 1 Will Record + 8:00 Who Cares -2 2 Will Record +11:00 Who Cares -2 1 Earlier Showing +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Card 2 with input priority "-1":</P> +<P> +<FIGURE> +<EPS FILE="Card1 Pri 0 Card2 Pri -1.eps"> +<IMG SRC="Card1 Pri 0 Card2 Pri -1.png"> +<CAPTION></CAPTION> +</FIGURE> +</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> + Time Title Priority Card Status + 8:00 The Apprentice +3 1 Will Record + 8:00 Who Cares -3 2 Later Showing +11:00 Who Cares -2 1 Will Record +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Card 2 at "-1" but higher priority shows at both 8 P.M. and 11 P.M.:</P> +<P> +<FIGURE> +<EPS FILE="Card1 Pri 0 Card2 Pri -1-TDS.eps"> +<IMG SRC="Card1 Pri 0 Card2 Pri -1-TDS.png"> +<CAPTION></CAPTION> +</FIGURE> +</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> + Time Title Priority Card Status + 8:00 The Apprentice +3 1 Will Record + 8:00 Who Cares -3 2 Will Record +11:00 The Daily Show +1 1 Will Record +11:00 Who Cares -3 2 Earlier Showing +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Note the two different effects, each of which may be what you desire +depending on circumstance. If input priorities are equal, shows will record +at the earliest time if any input is available. If input priorities differ, +shows may be postponed to a later time in order to record on the best input.</P> + +<H3>Channel Priority</H3> + +<P>Priority can be added for individual channels (remember, frequencies from a +video source, not stations). This can be used to tell the system that you +generally prefer the content of the station on a channel over the formats of +other stations. You may want to raise the priority for ESPN, SciFi, Comedy +Central or lower the priority for CSPAN, CourtTV, etc. If the same station +is on two different channels, you can use channel priority to have the same +effect for these channels as input priority would have for whole inputs.</P> +<P>For example, say CNN is on analog channel 20 and there is an HD CNN on 750. +You may not want to tie up the HD input for news originating in standard +definition. Under TV Settings->Recording Priorities->Channel Priorities you +could set channel 750 to -1. The scheduler would then prefer to record CNN +shows on any analog channel 20 before considering using 750 only when there +are no analog inputs available.</P> + +<H3>Preferred Input</H3> + +<P>For an even finer grain of control, there is a per rule option to specify +which input should be preferred for showings that match the rule. By +default, this adds +2 to the priority for showings on the specified input.</P> +<P>For illustration, let's say there will be a Space Shuttle launch on CNN that +will be broadcast in high definition. Adding a rule to record the launch +with priority "0" should default to channel 20 on input 2. Channel 750 would +have this at -1 due to the channel priority set in the previous example. If +on the recording options page for this rule, the "Scheduling Options" had +the input set to prefer the HD input on card 1, then the showing on channel +750 for this input would be increased in value by +2 for a total of +1 and +would be the best choice for this launch coverage. While this one rule +would prefer the HD input with channel 750, all other rules that match shows +on CNN would still prefer channel 20.</P> +<P>Note that this will not work properly if the preferred input priority does +not out weigh differences in input and channel priorities. The value of the +priority boost when this option is chosen defaults to +2 but can be modified +in TV Settings->Recording Priorities->Set Recording Priorities.</P> + +<H3>HDTV Priority</H3> + +<P>In the preceeding fictious example, the Space Shuttle launch is broadcast in +high definition and a preferred input is selected to give preference to the +HD input. However, TV listings from zap2it.com through the DataDirect +service may allow this to work without having to use this per rule option.</P> +<P>In Settings->Recording Priorities->Set Recording Priorities there is an +option for "HDTV Recording Priority". This value will be added automatically +if the listings for the show have the "hdtv" flag set. DataDirect will set +this flag for shows known to be broadcast in HDTV on HD channels. However, +the flag is not set for standard definition channels. This is another +example of the listings being different for the same station on a different +channel. If the HDTV priority is set to "+2", the shuttle launch would +automatically have a total priority of +1 so that channel 750 would be +preferred over channel 20 for this HDTV broadcast.</P> +<P>Channel "750 CNN" at priority "-1" and HDTV broadcast priority at "+2":</P> +<P> +<FIGURE> +<EPS FILE="Card1 HDTV Card2 Cable.eps"> +<IMG SRC="Card1 HDTV Card2 Cable.png"> +<CAPTION></CAPTION> +</FIGURE> +</P> + +<H3><A NAME="Custom Priority"></A> Custom Priority </H3> + +<P> +<FIGURE> +<EPS FILE="add.eps"> +<IMG SRC="add.png"> +<CAPTION>New for MythTV 0.21</CAPTION> +</FIGURE> +</P> +<P>While Input, Channel, and HDTV Priority can be used for indicating a +preference for certain programs and inputs, there may be circumstances that +cannot be resolved easily with these standard features. MythTV version 0.21 +includes a feature for "power priority". The Custom Priority editor in +mythfrontend's "TV Settings" screen is similar to Custom Record, however, +Custom Priority allows you to create specialized power priority factors to +influence scheduling decisions.</P> +<P>For example, the 'program.closecaptioned' flag can be used in a +similar way as the 'program.hdtv' flag.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +Priority Rule Name: Closed Captioned priority +Priority Value: 2 +program.closecaptioned > 0 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>This will raise the priority of shows marked with "CC" over those that are +not by applying the "Priority Value" whenever the SQL fragment evaluates to +true. If the expression evaluates to false for a showing, the "Priority +Value" is not applied.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +Priority Rule Name: Priority when shown once +Priority Value: 1 +program.first > 0 AND program.last > 0 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The "first" and "last" flags for an episode will only be set for the +same showing when there is only one showing of that episode in the +current TV listings. This rule would raise the priority in these cases +so that these shows would have an advantage to record in their only +available time slot.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +Priority Rule Name: Input 1 signal quality +Priority Value: -1 +cardinput.cardinputid = 1 AND +channel.channum IN (3, 5, 39, 66) +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>A common issue with two or more analog capture cards is that one of +the cards may have more interference on some channels than the same +channels on other cards. This example gives a disadvantage to the +channels in this list but only for the first input. Therefore, a show +on channel 39 would choose input 2 or 3 if possible but for channels +not in this list, input 1 is still the first choice.</P> +<P>The Custom Priority editor includes many example fragments and complete +examples that can be used or you can create your own to suit your needs.</P> + +<H2><A NAME="mythplugins_"></A> <A NAME="s13">13.</A> <A HREF="#toc13">MythPlugins. </A></H2> + +<P>MythTV has a rich set of plugins available. Once you have downloaded +the tarball, untar it and run the <B>configure</B> script:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xjf mythplugins-0.21.tar.bz2 +$ cd mythplugins-0.21 +$ ./configure --help + +Usage: configure [options] +Options: [defaults in brackets after descriptions] +NB: all --enable-* options can be reversed with --disable-* + +Generic options: + --help print this message + --enable-all Enable all options + --enable-opengl enable OpenGL (Music and Gallery) [default=no] + +MythBrowser related options: + --enable-mythbrowser build the mythbrowser plugin [default=yes] + +MythDVD related options: + --enable-mythdvd build the mythdvd plugin [default=yes] + --enable-transcode enable DVD ripping and transcoding [default=no] + --enable-vcd enable VCD playing [default=no] + +MythGallery related options: + --enable-mythgallery build the mythgallery plugin [default=yes] + --enable-exif enable reading of EXIF headers [default=no] + +MythGame related options: + --enable-mythgame build the mythgame plugin [default=yes] + +MythMusic related options: + --enable-mythmusic build the mythmusic plugin [default=yes] + --enable-fftw enable fftw visualizers [default=no] + --enable-sdl use SDL for the synaesthesia output [default=no] + --enable-aac enable AAC/MP4 audio file decompression [default=no] + +MythNews related options: + --enable-mythnews build the mythnews plugin [default=yes] + +MythPhone related options: + --enable-mythphone build the mythphone plugin [default=yes] + --enable-festival enable festival TTS Engine [default=no] + +MythVideo related options: + --enable-mythvideo build the mythvideo plugin [default=yes] + +MythWeather related options: + --enable-mythweather build the mythweather plugin [default=yes] +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The sections detailing configuration of the plugins assume that you are +already in the <CODE>~/mythplugins-0.21/</CODE> directory.</P> +<P>Note that a single <B>configure</B> script now does configuration for all +modules. By default, it will compile all modules. If you do not wish to +compile a module, either because it is of no use to you, or you do not have +the prerequisites, the simplest course of action is to go through the +various sections below, satisfying the prerequisites, and then compile all +modules at once.</P> +<P>For example, you would only like to compile and install MythGallery and +MythMusic. For MythGallery, you would like to use the EXIF data in the .JPG +file to present additional information onscreen. For MythMusic, you would +like to enable support for the opengl and FFT visualizations. The command +line would look like:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-opengl --enable-mythgallery --enable-exif --enable-mythmusic --enable-fft +$ qmake mythplugins.pro +$ make +$ su - +# make install +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>For simplicity, the examples below will disable compilation of all other +modules other than the one being discussed.</P> + +<H2><A NAME="s14">14.</A> <A HREF="#toc14">MythWeb.</A></H2> + +<P>MythWeb allows you to use a web page to control various aspects of your +MythTV system. MythWeb is a separate application, but it's dependent on +MythTV being installed and operational.</P> + +<H2><A NAME="ss14.1">14.1</A> <A HREF="#toc14.1">Installation and prerequisites</A> +</H2> + +<P>Mythweb is a part of the <B>mythplugins</B> package. See +<A HREF="#mythplugins_">MythPlugins</A> for instructions on downloading the +tarball. The next step depends on whether your distribution has a web server +and if you have PHP support.</P> + +<H3>Mandriva</H3> + +<P>Mandriva has <B>apache</B> and <B>PHP</B> pre-packaged, so +installation is quite simple. </P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Mandriva 9.1 users, perform the following:</CAPTION> +</FIGURE> + +<BLOCKQUOTE><CODE> +<PRE> +# urpmi apache2 apache2-mod_php php-mysql +# chkconfig --level 345 httpd on +# /etc/rc.d/init.d/httpd restart +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss14.2">14.2</A> <A HREF="#toc14.2">Completing the installation</A> +</H2> + +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21/mythweb +$ su +# mkdir /var/www/html/mythweb +# cp -r . /var/www/html/mythweb +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>By default, MythWeb uses an Apache <CODE>.htaccess</CODE> file to restrict +access to the website and to configure some variables.</P> +<P>To create the password file for Apache (if your system doesn't already have +one), you could do something like this: +<BLOCKQUOTE><CODE> +<PRE> +# cd /var/www +# htpasswd -c htpasswd mythtv +New password: +Re-type new password: +Adding password for user mythtv +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>See the man page for <B>htpasswd</B> for more examples.</P> +<P>To access the web page, open a web browser and use <B>http://[name or ip +address]/mythweb/</B></P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Make sure that you have a trailing slash on the URL, +otherwise you will get a <CODE>404 Page not Found</CODE> error.</CAPTION> +</FIGURE> +</P> +<H2><A NAME="ss14.3">14.3</A> <A HREF="#toc14.3">Resetting the key binding table</A> +</H2> + +<P>MythWeb allows you to configure which keys are bound to which actions +within MythTV. If you'd like to reset this back to the default, execute the +following command: +<BLOCKQUOTE><CODE> +<PRE> +$ echo "delete from keybindings ;" | mysql -u mythtv -pmythtv mythconverg +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H2><A NAME="ss14.4">14.4</A> <A HREF="#toc14.4">Resetting the theme.</A> +</H2> + +<P>If you find yourself wedged into a theme that isn't working, open your +web browser and go to site: +<CODE>http://mythweb_name_or_ip_address/mythweb/settings.php?RESET_THEME=yes</CODE></P> +<H2><A NAME="s15">15.</A> <A HREF="#toc15">MythGallery.</A></H2> + +<P>MythGallery is a photo and slideshow application. MythGallery is a +separate application, but it's dependent on MythTV being installed and +operational.</P> +<H2><A NAME="ss15.1">15.1</A> <A HREF="#toc15.1">Installation and prerequisites</A> +</H2> + +<P>MythGallery is a part of the <B>mythplugins</B> package. See +<A HREF="#mythplugins_">MythPlugins</A> for instructions on downloading the +tarball.</P> +<P>There are a number of transitions available, some requiring OpenGL +support. You will also need to install a TIFF library. Under Mandriva, you +would perform the following command: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi libtiff3-devel +</PRE> +</CODE></BLOCKQUOTE> + +Once you have satisfied the prerequisites for your distribution, install the application: +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-opengl --enable-mythgallery +$ qmake mythplugins.pro +$ make +# su +# make install +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> + +The configuration for MythGallery is accessed through the main Setup option +in mythfrontend. Make sure you set your pictures directory to wherever +you're storing your photos.</P> +<P>The controls for MythGallery can be found in the README that comes with the +application.</P> +<H2><A NAME="ss15.2">15.2</A> <A HREF="#toc15.2">Using MythGallery</A> +</H2> + +<P>When you first start MythGallery, you will see a thumbnail view of any +folders and pictures in the Gallery Directory you specified in setup. If +this is the first time you have accessed this directory, the thumbnails will +be generated on the fly. If the Gallery Dir is writable, these thumbnails +will be cached thus speeding up future access. On the left is a greyed-out +menu of options.</P> +<P>Use the arrow keys to select a folder or picture to open/view with the +Select key, or use the Menu key to toggle access the menu on the left. The +menu options are as follows: +<UL> +<LI> Slideshow - Will cycle through all the pictures in the current folder. +The currently selected item must be a picture (not a folder) for this to +work. It does not currently traverse subfolders.</LI> +<LI> Rotate CW - Rotate the current image 90 degrees in the clockwise +direction. This change persists if the current directory is writable.</LI> +<LI> Rotate CCW - As above except the direction of rotation is counter(anti) +clockwise.</LI> +<LI> Import - Import pictures into your Gallery Dir. This option is +described in the next section.</LI> +<LI> Settings - Access the MythGallery settings screen.</LI> +</UL> +</P> +<H2><A NAME="ss15.3">15.3</A> <A HREF="#toc15.3">Importing Pictures</A> +</H2> + +<P>The import path in the setup dialog is a colon separated list of +directories and/or executable files. When the import key is pressed, a new +directory (the destination directory) under the current directory will be +created and the import path will be searched. If the item in the import +path is a directory (the source directory), the contents of that directory +will be copied to the destination directory. If you would like the source +directory to be that of a removable device, it might be a good idea to use +autofs. See the automount howto at +<A HREF="www.linuxdoc.org">www.linuxdoc.org</A> for info on how to get it working.</P> +<P>If the item in the import path is an executable file, MythGallery will +attempt to execute it with the destination directory as its sole argument. +Be careful when using executable scripts that the script runs unattended +(doesn't need user intervention) and returns properly, otherwise it could +create the appearance of MythGallery hanging (e.g. running +<B>smbclient</B> and prompting for password). Also be sure that scripts +have executable permissions set.</P> +<P>Here is an example script that a user may want to run +on import: +<BLOCKQUOTE><CODE> +<PRE> +#!/bin/csh + +if ($#argv == 0) then + echo "Usage: $0 dest_dir" + exit +endif + +cd $argv[1] + +# get stuff over the network +wget http://www.somesite.dom/dir/file1.jpg +wget http://www.somesite.dom/dir/file2.jpg +wget http://www.somesite.dom/dir/file3.jpg + +# stuff that requires manual module loading and/or fs mounting +modprobe camera_module +mount /dev/camera /mnt/camera +cp /mnt/camera/* $argv[1] +umount /mnt/camera +rmmod camera_module + +# perform some processing +foreach pname (`ls *.jpg`) + jpegtran -flip vertical $pname > $pname.new + mv $pname.new $pname +end +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="s16">16.</A> <A HREF="#toc16">MythGame.</A></H2> + +<P>MythGame can used as a frontend to start any emulator that your host OS +runs. This is an example of how to set up xmame on Linux. +<A HREF="http://www.mameworld.net/">http://www.mameworld.net/</A> is +an excellent resource for all things mame.</P> +<P>Installation overview: +<OL> +<LI>Setup directory structure</LI> +<LI>Download and install xmame</LI> +<LI>Download and place extra files (artwork/catver.ini/etc..)</LI> +<LI>Download and install MythGame plugin</LI> +<LI>Setup xmame in MythGame</LI> +<LI>Hints</LI> +</OL> +</P> +<H2><A NAME="ss16.1">16.1</A> <A HREF="#toc16.1">Setup Directory Structure</A> +</H2> + +<P>To keep things organized, create the following directories for <B>xmame</B> to use +in <CODE>/usr/local/share/xmame</CODE>: hiscore, roms, and snaps.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ mkdir -p /usr/local/share/xmame/{highscore,roms,snaps} +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss16.2">16.2</A> <A HREF="#toc16.2">Download and Install xmame</A> +</H2> + +<P><B>NOTE</B>: There may be pre-packaged versions of <B>xmame</B> +available for your distribution. Check +<A HREF="http://x.mame.net/download.html">http://x.mame.net/download.html</A> for the latest version.</P> +<P>Download the source to <B>xmame</B> from +<A HREF="http://x.mame.net/download/xmame-0.103.tar.bz2">http://x.mame.net/download/xmame-0.103.tar.bz2</A></P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ wget http://x.mame.net/download/xmame-0.103.tar.bz2 +$ tar -xjf xmame-0.103.tar.bz2 +$ cd xmame-0.103 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Edit the Makefile with your favorite editor. Adjust the options as required for your system. +<BLOCKQUOTE><CODE> +<PRE> +$ joe Makefile +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Then make and install xmame +<BLOCKQUOTE><CODE> +<PRE> +$ make +$ su +(enter password) +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>After <B>mame</B> has been installed, we need to create some defaults. +<BLOCKQUOTE><CODE> +<PRE> +$ mkdir ~/.xmame +$ cp docs/xmamerc.dist ~/.xmame/xmamerc +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Because some ROMS work better with different display toolkits, or possibly +even older versions of xmame, it's convenient to keep all of your +<B>xmame</B> binaries and to rename them to include the version number. +MythGame allows you to match individual roms to preferred binaries.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ su +(enter password) +# mv /usr/local/bin/xmame.x11 /usr/local/bin/xmame-0.103.x11 +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><B>NOTE</B>: Depending on how you compiled <B>xmame</B>, you may have +<B>xmame.X11</B>, <B>xmame.SDL</B> or <B>xmame.xgl</B> based on what +display toolkit you used. Also, you may need to remove and recreate +<CODE>xmamerc</CODE> after upgrading since some of the default options may have +changed.</P> +<P>Edit <CODE>~/.xmame/xmamerc</CODE> to include your paths. +<BLOCKQUOTE><CODE> +<PRE> +### Fileio Related ### +rompath /usr/local/share/xmame/roms +snapshot_directory /usr/local/share/xmame/snaps +cheat_file /usr/local/share/xmame/cheat.dat +hiscore_file /usr/local/share/xmame/hiscore.dat +hiscore_directory /usr/local/share/xmame/hiscore +history_file /usr/local/share/xmame/history.dat +mameinfo_file /usr/local/share/xmame/mameinfo.dat +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Confirm that <B>xmame</B> works before running it inside MythTV. Place +your ROM in the <CODE>/usr/local/share/xmame/roms</CODE> directory you created +earlier.</P> +<P><B>NOTE</B>: There are three public domain ROM sets available at +<A HREF="http://www.mame.net/downmisc.html">http://www.mame.net/downmisc.html</A></P> +<P>Launch <B>xmame</B> with your game of choice. In this example, we are using Gauntlet. +<BLOCKQUOTE><CODE> +<PRE> +$ xmame gauntlet +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Some basic <B>mame</B> keyboard commands: +<BLOCKQUOTE><CODE> +<PRE> +5 = Insert coin +1 = Player 1 start +arrow keys = movement +left control = button 1 +left alt = button 2 +SPACE = button 3 +ESC = exit +TAB - menu +~ to adjust Volume + < and > +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss16.3">16.3</A> <A HREF="#toc16.3">Download extra files</A> +</H2> + +<P>The following files allow you to add extra functionality. Place them +into <CODE>/usr/local/share/xmame</CODE></P> +<P>- <CODE>catver.ini</CODE> is a catalog of categories and versions of popular mame ROMs.</P> +<P>Useful for keeping large libraries of ROMs organized.</P> +<P>It may be downloaded from +<A HREF="http://www.catver.com">http://www.catver.com</A> or +<A HREF="http://www.mameworld.net/catlist">http://www.mameworld.net/catlist</A></P> +<P>- Screenshots aka "snaps"</P> +<P>These may be downloaded from +<A HREF="http://www.classicgaming.com/mame32qa/">http://www.classicgaming.com/mame32qa/</A></P> +<P>Screenshots are displayed when you are browsing your ROMS in <B>mythgame</B>. +Unzip and place them in <CODE>/usr/local/share/xmame/snaps</CODE></P> +<P>- <CODE>history.dat</CODE></P> +<P>Download from +<A HREF="http://www.arcade-history.com/">http://www.arcade-history.com/</A> +This file fills in a bit of background about each ROM.</P> +<P>- <CODE>hiscore.dat</CODE></P> +<P>Download from +<A HREF="http://www.mameworld.net/highscore/">http://www.mameworld.net/highscore/</A></P> +<P>- Cheats</P> +<P>Download from +<A HREF="http://cheat.retrogames.com/">http://cheat.retrogames.com/</A></P> + +<H2><A NAME="ss16.4">16.4</A> <A HREF="#toc16.4">Download and Install MythGame.</A> +</H2> + +<P><B>MythGame</B> is part of the mythplugins package. See the instructions +in the +<A HREF="#DownloadAndCompile">Downloading and Compiling</A> +section to obtain mythplugins.</P> +<P>Switch to the mythplugins directory: +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Compile and install mythgame: +<BLOCKQUOTE><CODE> +<PRE> +$ ./configure --disable-all --enable-mythgame +$ qmake mythplugins.pro +$ make +$ su +(enter password) +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss16.5">16.5</A> <A HREF="#toc16.5">Setup xmame in MythGame</A> +</H2> + +<P>Start <B>mythfrontend</B> and navigate to Utilities/Setup > Setup > Media +Settings > Game Settings > Game Players. Select <CODE>(New Game Player)</CODE>.</P> +<P>To set up a new player for xmame enter the following:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +Player Name: xmame-0.103.x11 (Name by which you want your emulator or game called) +Type: xmame (This is used for display purposes only and does not affect the function of your system) +Command: xmame-0.103.x11 -vidmod 1 -fullscreen (Path and name of binary + any optional parameters) +Rom Path: /usr/local/share/xmame/roms (This tells MythGame what directories to scan for roms to be used with this emulator) +ScreenShots: /usr/local/share/xmame/snaps (This tells MythGame what directories to scan for snapshots to be used with these roms) +Working Directory: (Directory to change to before launching game or emulator. Blank in our case ignores this setting) +File Extensions: (List of all file extension to be used for this emulator. Blank menas any file under the Rom Path) +[] Allow games to span multiple roms/disks (will treat game.1.rom game.2.rom game.3.rom as one game) +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss16.6">16.6</A> <A HREF="#toc16.6">Hints:</A> +</H2> + +<P> +<UL> +<LI>Rom name before options: %s can be used as a standin for rom names on the command line.</LI> +<LI>Multiple disk/rom games: %d1 %d2 etc can be used as standins for multiple disc games on the command line.</LI> +<LI>Associating a rom with an emulator: Browse to the desired rom and press 'M' to enter the settings page for that rom.</LI> +<LI>Assign a Game Favorite Status: Browse to the desired game and press "/".</LI> +</UL> +</P> + +<H2><A NAME="s17">17.</A> <A HREF="#toc17">MythMusic. </A></H2> + +<P>MythMusic has a number of prerequisites that must be satisfied before it +is operational. Depending on your distribution, some of these prerequisites can +be satisfied through the various package managers. If your distribution doesn't +offer pre-compiled versions of the software below, then follow the generic +instructions for manually compiling and installing the software.</P> +<P>The prerequisites for MythMusic are: +<UL> +<LI>MAD</LI> +<LI>taglib</LI> +<LI>libogg and libvorbis</LI> +<LI>FLAC</LI> +<LI>libcdaudio</LI> +<LI>CDParanoia</LI> +</UL> +</P> + +<H2><A NAME="ss17.1">17.1</A> <A HREF="#toc17.1">Manual installation of prerequisites</A> +</H2> + +<P>These instructions are for distributions which don't have pre-compiled +versions of the software necessary to run MythTV.</P> +<P>Download MAD from +<A HREF="http://www.underbit.com/products/mad">http://www.underbit.com/products/mad</A> and install:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xzf mad-0.15.1b.tar.gz +$ cd mad-0.15.1b +$ ./configure +$ make +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Download TagLib from +<A HREF="http://developer.kde.org/~wheeler/taglib.html">http://developer.kde.org/~wheeler/taglib.html</A> and install:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xzf taglib-1.4.tar.gz +$ cd taglib-1.4 +$ ./configure +$ make +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Download libogg and libvorbis from +<A HREF="http://www.xiph.org/downloads">http://www.xiph.org/downloads</A> and install in a similar manner +to the above packages.</P> +<P>Download FLAC from +<A HREF="http://flac.sourceforge.net">http://flac.sourceforge.net</A> and install: +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xzf flac-1.1.2.tar.gz +$ cd flac-1.1.2 +$ ./configure +$ make +$ su +# make install +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Download libcdaudio from +<A HREF="http://sourceforge.net/project/showfiles.php?group_id=27134">http://libcdaudio.sourceforge.net</A> and +install: +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xzf libcdaudio-0.99.12p2.tar.gz +$ cd libcdaudio-0.99.12p2 +$ ./configure +$ make +$ su +# make install +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Download cdparanoia from +<A HREF="http://www.xiph.org/paranoia/download/cdparanoia-III-alpha9.8.src.tgz">http://www.xiph.org/paranoia/down.html</A>. +<BLOCKQUOTE><CODE> +<PRE> +$ tar -xzf cdparanoia-III-alpha9.8.src.tgz +$ cd cdparanoia-III-alpha9.8 +$ ./configure +$ make +$ su +# make install +# cd /usr/lib +# ln -sf libcdda_interface.so.0.9.8 libcdda_interface.so +# ln -sf libcdda_paranoia.so.0.9.8 libcdda_paranoia.so +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss17.2">17.2</A> <A HREF="#toc17.2">Mandriva</A> +</H2> + +<P>Mandriva has a number of the prerequisites available on the +installation CD. Some of the software you're going to need will have to be +obtained from the "contrib" or "cooker" development repositories. +Applications downloaded from "cooker" come from the development branch, so +there may be issues with some software. It isn't recommended that you mix +cooker and release-level software.</P> + +<P><B>urpmi</B> is the simplest tool for installation of packages from the +command line. The difficult part is the configuration, but this has been +made easier at the following website: +<A HREF="http://addmedia.linuxfornewbies.org/">http://addmedia.linuxfornewbies.org/</A> The website will allow +you to choose a mirror site and then present the command-line configuration +text for that mirror. You will most likely need to add a "Contrib" mirror +to your setup. Once you have done that, you can proceed. If <B>urpmi</B> +prompts you about other modules that need to be installed to satisfy +dependencies, say "Yes".</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +# urpmi libmad0 libmad0-devel libflac4 libflac4-devel libcdaudio1 cdparanoia +# urpmi libcdda0 libcdda0-devel libvorbis0 libvorbis0-devel +# urpmi libcdaudio1-devel libid3tag0 libid3tag0-devel +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3>Additional options with MythMusic</H3> + +<P>Additional visualizations have been added to MythMusic. If you wish to +use these, there are some prerequisites you must install prior to compiling.</P> +<P> +<UL> +<LI>fftw</LI> +<LI>OpenGL</LI> +<LI>SDL</LI> +</UL> +</P> +<P><CODE>fftw</CODE> may be obtained from +<A HREF="http://www.fftw.org/">http://www.fftw.org/</A>. In Mandriva it may be installed by +typing: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi libfftw2 libfftw2-devel +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><CODE>OpenGL</CODE> should be installed on practically all distributions. +However, you will need the devel module. In Mandriva it may be +installed by typing: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi libMesaGLU1-devel +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><CODE>SDL</CODE> may be obtained from +<A HREF="http://www.libsdl.org">http://www.libsdl.org</A>. In Mandriva it may be installed by +typing: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi libSDL1.2 libSDL1.2-devel +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss17.3">17.3</A> <A HREF="#toc17.3">Red Hat Linux 9</A> +</H2> + +<P>Red Hat provides packages for several of the prerequisites, making +installation very simple. Of the prerequisites, Red Hat provides +packages for Vorbis, cdparanoia, SDL, and OpenGL (which you probably +already have installed). To install these all at once, simply type (all on +the same line): +<BLOCKQUOTE><CODE> +<PRE> +$ up2date --solvedeps libvorbis libvorbis-devel vorbis-tools cdparanoia-devel cdparanoia-libs cdparanoia SDL-devel SDL +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you get the following message: "None of the packages you requested +were found, or they are already updated" it probably means you already +have all of those packages installed.</P> +<P>You must install the remaining packages, (MAD, FLAC, libcdaudio and +optionally fftw) manually following the installation directions above. When +installing fftw do not use the rpm package offered on the website because it +will cause an error, so use the source package instead.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: you can use the instructions given at the +<A HREF="#atrpms">automated installation section</A> to install all of MythMusic in one +step.</CAPTION> +</FIGURE> +</P> +<H2><A NAME="ss17.4">17.4</A> <A HREF="#toc17.4">Compiling MythMusic</A> +</H2> + +<P>Once all the prerequisites have been installed, you can proceed with +compiling MythMusic.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-mythmusic --enable-fftw --enable-sdl --enable-aac +$ qmake mythplugins.pro +$ make +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss17.5">17.5</A> <A HREF="#toc17.5">Configuring MythMusic</A> +</H2> + +<P>Configuration of MythMusic occurs in two places. The main mythfrontend +Setup is for global MythMusic configuration. Go to the +Setup/MythMusic/General Setup screen and adjust it for your particular +configuration.</P> +<P>The second configuration screen is within the MythMusic program and will +allow you rescan your music library, etc.</P> +<P>Here's some explanation about the Ignore_ID3 and The NonID3FileNameFormat:</P> +<P>If Ignore_ID3 is set to TRUE, MythMusic will try to determine the +Genre, Artist, Album, Track Number, and Title from the filename of the +mp3 file. The NonID3FileNameFormat variable should be set to the +directory/file format where the mp3 files are stored. For instance, I +store mine in the above shown Genre/Artist/Album/Track format. MythMusic +will then use this information to fill in the proper fields when it +populates the musicmetadata table rather than searching for an ID3 tag in +the mp3 file.</P> +<P>The files can be laid out in any format, such as:</P> +<P>Genre/Artist/Album/Title +Artist/Genre/Album/Title +Artist/Album/Title (with Genre left as Unknown)</P> +<P>The track number is optional but can be specified with the title by using +the TRACK_TITLE keyword instead of TITLE. If TRACK_TITLE is used, +then the filename can have a space, hyphen, or underscore separating the +track number from the track title. Keywords are case insensitive, so if +you specify GENRE it's the same as Genre in the format field.</P> +<P>The Ignore_ID3 option does not disable the code that determines the track +length, just the portion that tries to read ID3 info.</P> + +<H2><A NAME="ss17.6">17.6</A> <A HREF="#toc17.6">Using MythMusic</A> +</H2> + +<P>MythMusic is fairly simple to use. It is recommended that you insert the +CD before selecting "Import CD". You should also ensure that your system +doesn't try to automount the CD and begin playing it automatically.</P> +<P>Here's some information on playlist management:</P> +<P>Q: How do I create a new playlist? +A: Using the MythMusic "Select Music" menu option, setup the playlist as you +normally would by adding songs or other playlists as needed. When you are +ready to save the new playlist, highlight "Active Play Queue" at the bottom +of the selection tree and hit the "i" key. This will pop up a menu allowing +you to name and save the new playlist. You can also hit Enter to bring up +the popup on the Active Play Queue. This does not work on the playlists +above, as Enter is obviously bound to checking/unchecking the boxes. Any +number (i.e. keypad on remote) will also bring up the menu in both cases.</P> +<P>Q: How do I enter the playlist name in the text field without a keyboard? +A: Use the keypad number keys (bound to your remote) to select letters +quasi-cell phone style. Keys 2-9 work pretty much like any cell phone text +entry. 1 cycles through a few special characters, delete, and space. 0 is +like a CAPS LOCK. Hard to describe, fairly easy to use. You will soon be +able to specify the cycle timing in a Setup screen. You can type fairly +quickly through a combination of jumping around the number keys AND hitting +a non-number key (right arrow is particularly good for this) to force the +current character.</P> +<P>Q: How do I edit a playlist? +A: Highlight the playlist in the selection tree and hit the "i" key then +select "Move to Active Play Queue" in the popup. You can now modify the +"Active Play Queue" like normal, adding songs and playlists by selecting +them from the song tree. When you are done, highlight the "Active Play +Queue" in the selection tree and hit the "i" key then select "Save Back to +Playlist Tree". And whatever you were editing as your Active Queue before +you moved an existing playlist "on top" of Active reappears. Think of Active +has having a push on, pop off capability, but with a depth of only 1.</P> +<P>Q: How do I delete an item from a playlist? +A: Highlight the item in the selection tree and hit the "d" key.</P> +<P>Q: How do I rearrange the songs in my playlist? +A: Highlight a song and hit the "space" bar, the song will now have pair of +red arrows in front of it. Use the up and down arrow keys to move it around +in the playlist. When you have it where you want it, hit the "space" bar +again.</P> +<P>Q: How do I delete a playlist? +A: Highlight the playlist in the selection tree and hit the "i" key then +select "Delete this Playlist" from the popup.</P> + +<H2><A NAME="ss17.7">17.7</A> <A HREF="#toc17.7">Troubleshooting MythMusic</A> +</H2> + +<P>You may run into errors when running MythMusic.</P> +<H3>When I run MythMusic and try and look up a CD, I get an error message </H3> + +<P>The full text of the message will say: </P> +<P>databasebox.o: Couldn't find your CD. It may not be in the freedb database. +More likely, however, is that you need to delete /.cddb and /.cdserverrc +and restart mythmusic. Have a nice day.</P> +<P>If you get this message, you should go to the home directory of whatever +user MythMusic is running as and type: +<BLOCKQUOTE><CODE> +<PRE> +rm .cdserverrc +rm -rf .cddb/ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>These files aren't automatically deleted because of a conscious design +decision by the author that programs that automatically delete things are +bad.</P> +<P>The files are used to locally cache CD lookups. If you are re-inserting +CDs, your machine will not actually have to go out to the Internet to +determine what is on them. However, the URL used to access the freedb +database has recently changed, so the stale information in the files from +previous runs of MythMusic would cause the error above. Once the files have +been deleted the stale information will be gone and your local database +will be rebuilt as you use CDs.</P> + +<H2><A NAME="s18">18.</A> <A HREF="#toc18">MythWeather.</A></H2> + +<P>MythWeather is a part of the <B>mythplugins</B> package. See +<A HREF="#mythplugins_">MythPlugins</A> for instructions on downloading the +tarball.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-mythweather +$ qmake mythplugins.pro +$ make +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>MythWeather uses MSNBC.com as its source for weather data and weather.com +for its radar image.</P> +<P>These are the keyboard commands for MythWeather: +<BLOCKQUOTE><CODE> +<PRE> +Left Key Goes back one page, and extends the time spent + on the page you are on. +Right Key Goes forward one page, see above. +Space Pause, wait on the current page until space is hit + again. +Numeric Keys You can check other weather by keying in other ZIP codes. +Enter Key Switch between Celsius and Fahrenheit. Can also + be used a way to force a data update. +"m" Key Resets the location to the database default, then updates the data. +"i" Enter / Save settings +ESC Exit the settings screen without saving / Exit the program +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>MythWeather also has an "Aggressiveness" setting. This affects how long +MythWeather waits for data from the msnbc.com website before timing out. If +you are on a slow connection, or have a slow DNS, or MythWeather just +doesn't seem to be working and you've already tried everything else, then +try increasing the aggressiveness level parameter. This parameter is +inverse; a higher number actually means that MythWeather will be less +aggressive, and will therefore wait longer before timing out.</P> +<P>MythWeather will print debugging information on the terminal. If you wish +to see additional debugging information while MythWeather is running, run +mythweather from the command line with as <CODE>mythweather --debug</CODE></P> +<P>You may also force mythweather to re-run the configuration by starting it on +the command line as <CODE>mythweather --configure</CODE>. These two options are +mutually exclusive.</P> + +<H2><A NAME="s19">19.</A> <A HREF="#toc19">MythVideo.</A></H2> + +<P>MythVideo is a part of the <B>mythplugins</B> package. See +<A HREF="#mythplugins_">MythPlugins</A> for instructions on downloading the +tarball.</P> +<P>MythVideo will allow you to use an external program to watch media files +that are not directly supported by MythTV.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-mythvideo +$ qmake mythplugins.pro +$ make +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>See MythVideo's <CODE>README</CODE> file for additional information.</P> + +<H2><A NAME="s20">20.</A> <A HREF="#toc20">MythDVD.</A></H2> + +<P>MythDVD is a part of the <B>mythplugins</B> package. See +<A HREF="#mythplugins_">MythPlugins</A> for instructions on downloading the +tarball. MythDVD is an application which rips DVDs and makes them available for +use with MythVideo. You may also transcode the DVD content from MPEG-2 to +other formats which should greatly reduce the amount of space the DVD +material takes up on your hard drive.</P> +<P>MythDVD has a number of prerequisites to enable transcoding functionality. +If you only wish to play DVDs rather than convert them to something like +MPEG-4 or xvid you may skip the prerequisite installation step.</P> + +<H2><A NAME="ss20.1">20.1</A> <A HREF="#toc20.1">Manual Compilation of Prerequisites</A> +</H2> + + +<H2><A NAME="ss20.2">20.2</A> <A HREF="#toc20.2">Pre-compiled binaries</A> +</H2> + +<P>Mandriva users may install the prerequisites this way: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi libdvdread3 libdvdread3-devel a52dec liba52dec-devel +# urpmi mplayer ogle xine +</PRE> +</CODE></BLOCKQUOTE> + +Assuming that you've added a PLF mirror, you may also load the rest of the +prerequisites using the following command: +<BLOCKQUOTE><CODE> +<PRE> +# urpmi xvid xvid-devel fame libfame0.9-devel transcode libdvdcss +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>In the example below, we have enabled support for transcoding and for VCD +playing. You may remove these options if you don't need them. +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.20 +$ ./configure --disable-all --enable-mythdvd --enable-transcode --enable-vcd +$ qmake mythplugins.pro +$ make +$ su +# make install +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H2><A NAME="ss20.3">20.3</A> <A HREF="#toc20.3">Running the Myth Transcoding Daemon</A> +</H2> + +<P>Transcoding ("ripping") a DVD requires you to run the Myth Transcoding +Daemon (mtd). To ensure that mtd is configured correctly, you should first +test it at the command line. +<BLOCKQUOTE><CODE> +<PRE> +$ mtd -n +</PRE> +</CODE></BLOCKQUOTE> + +The last line of text should show something like: +<BLOCKQUOTE><CODE> +<PRE> +mtd is listening on port 2342 +</PRE> +</CODE></BLOCKQUOTE> + +This indicates that mtd is ready for use. Once you've successfully +tested mtd in the foreground, type <B>CTRL-C</B> to stop mtd. You may +then start it as a background (daemon) process. +<BLOCKQUOTE><CODE> +<PRE> +$ mtd -d +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Running mtd as a daemon will allow you to automatically start it during the +boot process. For example, you may add <CODE>mtd -d</CODE> to your +<CODE>rc.local</CODE> file, or you can adjust the script/steps outlined in the +section called +<A HREF="#mythbackend_autostart">Automatically starting mythbackend at system boot time</A> to start mtd instead of mythbackend.</P> + +<H2><A NAME="s21">21.</A> <A HREF="#toc21">MythNews.</A></H2> + +<P>MythNews is a part of the <B>mythplugins</B> package. See +<A HREF="#mythplugins_">MythPlugins</A> for instructions on downloading the +tarball. MythNews is a RSS reader. +<BLOCKQUOTE><CODE> +<PRE> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-mythnews +$ qmake mythplugins.pro +$ make +$ su +# make install +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="s22">22.</A> <A HREF="#toc22">Troubleshooting.</A></H2> + +<H2><A NAME="ss22.1">22.1</A> <A HREF="#toc22.1">Compiling</A> +</H2> + +<H3>Compile errors</H3> + +<P>Some compile errors are worse than others. If you get an error that +doesn't abort the compilation, and says something like: +<BLOCKQUOTE><CODE> +<PRE> +cc1plus: warning: changing search order for system directory +"/usr/local/include" +cc1plus: warning: as it has already been specified as a non-system +directory +</PRE> +</CODE></BLOCKQUOTE> + +then it shouldn't be a problem.</P> +<P>If you get an error like <CODE>/usr/bin/ld: cannot find -lXext</CODE>, the +compiler is telling you that you don't have XFree86-devel installed, or that +your distribution hasn't set it up correctly. This needs to be fixed before +MythTV will compile.</P> + +<H3><A NAME="mkspecs_error"></A> make: *** No rule to make target /usr/lib/qt3/mkspecs/default/qmake.conf', needed by Makefile'. Stop. </H3> + +<P>This error happens when there's a missing link in the +<CODE>/usr/lib/qt3/mkspecs</CODE> directory. There are two ways to fix this +error:</P> +<P>1. Create the link manually: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# cd /usr/lib/qt3/mkspecs +# ln -sf linux-g++ default +</PRE> +</CODE></BLOCKQUOTE> + +and then restart the compile,</P> +<P>or</P> +<P>2. Run <B>qmake mythtv.pro</B> in the mythtv directory. Rerunning +<B>qmake</B> will create a new Makefile for you, however this still +doesn't fix the root cause of the issue, which is that your distribution +didn't create the symlink for you when the qt3 package was installed. The +first choice is the better solution.</P> + +<H3>make: *** No rule to make target /mkspecs/default/qmake.conf', needed by Makefile'. Stop.</H3> + +<P>You didn't set your <CODE>QTDIR</CODE>. Re-read the section on +<A HREF="#Setting_up_paths">Setting up paths</A>.</P> + +<H3>Internal Segmentation Fault.</H3> + +<P>This is most likely to be caused by an overheating processor rather than +an actual programming fault within gcc.</P> + +<H2><A NAME="debugging"></A> <A NAME="ss22.2">22.2</A> <A HREF="#toc22.2">Debugging </A> +</H2> + +<H3>MythTV segfaults</H3> + +<H3>MythTV isn't doing anything</H3> + +<H3>Debugging with GDB</H3> + +<P>Without details, the developers will not be able to determine if you have +discovered a genuine code-bug, or if the problem is with your system. In +order to determine what's going on, you must recompile MythTV with debugging +support and run MythTV within <B>gdb</B>, the GNU debugger. +Note that, on OS X, some data is provided without going through these steps. +See /Library/Logs/CrashReporter/MythFrontend.crash.log</P> +<P>Re-run the <B>configure</B> script and add <CODE>--compile-type=debug</CODE> +to any previous configuration options you may have used. Check the +<CODE>config.log</CODE> file if you have forgotten.</P> +<P>Now, you need to clear out the old versions of the software to ensure that +you're running with the debugging code, then compile and install. +<BLOCKQUOTE><CODE> +<PRE> +$ make distclean +$ ./configure --compile-type=debug +$ make +$ su +# make install +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>At this point, you now have debug-enabled software ready. To make sure that +you don't forget to type a command required for debugging, it's best to +setup a <CODE>gdbcommands</CODE> file. This will be read by <B>gdb</B> when it's +started. +Put the following into <CODE>gdbcommands</CODE> in your home directory:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +handle SIGPIPE nostop noprint +handle SIG33 nostop noprint +set logging on +set pagination off +set args -l myth.log -v record,channel,siparser +run +thread apply all bt full +set logging off +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Let's assume that the problem you're having is in <B>mythbackend</B>.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ gdb mythbackend -x gdbcommands +GNU gdb 6.3-debian +Copyright 2004 Free Software Foundation, Inc. +GDB is free software, covered by the GNU General Public License, and you are +welcome to change it and/or distribute copies of it under certain conditions. +Type "show copying" to see the conditions. +There is absolutely no warranty for GDB. Type "show warranty" for details. +This GDB was configured as "i386-linux".Using host libthread_db library "/lib/tls/libthread_db.so.1". +[Thread debugging using libthread_db enabled] +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><B>gdb</B> will automatically read the commands that you've placed in the +<CODE>gdbcommands</CODE> file and begin running the program you specified on the +command line.</P> +<P>If the program appears to be locked up, press CTRL-C to create the backtrace +file.</P> +<P>All of the output from <CODE>gdb.txt</CODE> should be posted to the mythtv-dev +mailing list, along with the steps you followed to get the program to crash.</P> +<P><B>NOTE</B>: If you're trimming the <CODE>gdb.txt</CODE> file to remove +extraneous information from the beginning of the file, make sure you include +at least 10 lines <EM>prior</EM> to the point where the backtrace actually +begins. This ensures that there is some context to the backtrace, and so +that it's possible to see what exactly caused the segfault.</P> +<P><B>gdb</B> has a number of options, read the <CODE>man</CODE> page for more +information. </P> +<P>Using the <CODE>gdbcommands</CODE> file in conjunction with a <B>while</B> loop +will ensure that <B>gdb</B> creates a trace file and then restarts:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ while true; do date >> gdb.txt; gdb mythbackend -x gdbcommands; done; +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><B>NOTE</B>: To exit this loop you will need to kill the while loop.</P> +<P>If you're trying to troubleshoot and you can't get back to the <B>gdb</B> window +for some reason, it may be easier to use two systems or to start +mythfrontend from the text console.</P> +<P>If you're going to troubleshoot from a remote system, connect to the machine +that you're going to test using <B>ssh</B> or <B>telnet</B>. Next, type +<CODE>$ export DISPLAY=localhost:0.0</CODE>. This will allow the graphics to be +displayed on the X console (usually ALT-F6 or ALT-F7) and still give you +output and control of <B>mythfrontend</B>, either from the <B>ssh</B> +session, or by switching back to the text console by pressing CTRL-ALT-F1. +You can now continue troubleshooting using <B>gdb</B> as detailed in the +instructions.</P> + +<H3>MythTV is crashing your system</H3> + +<P>When run as a non-privileged user, MythTV <EM>can not</EM> crash your +system. If your system is crashing when you run MythTV, then you have some +issue with the drivers for your capture card or other hardware, or the CPU +fan has fallen off/broken and your system is overheating when asked to +perform a CPU intensive task like encoding video.</P> +<P>If you are running as root, which is <B>strongly discouraged</B>, it is +possible that your system may crash due to the real-time thread using all +available CPU. You will not be able to interrupt the process, so for all +intents and purposes your computer will have crashed.</P> + +<H2><A NAME="ss22.3">22.3</A> <A HREF="#toc22.3">Installing</A> +</H2> + +<H3>When trying to run mythtv-setup, you get an error like this: "mythtv-setup: error while loading shared libraries:"</H3> + +<P>You didn't add <CODE>/usr/local/lib</CODE> to <CODE>/etc/ld.so.conf</CODE>. See the +section on modifying +<A HREF="#modifying_ld.so.conf">/etc/ld.so.conf</A>.</P> + +<H2><A NAME="ss22.4">22.4</A> <A HREF="#toc22.4">Using</A> +</H2> + +<H3>No programs are displayed in "Watch Recordings"</H3> + +<P>This situation occurs most often with a system that acts as a frontend +and a slave backend. MythTV supports system-global and user-specific +configuration files, with user-configuration files taking precedence. 99% +of the configuration for MythTV is in the MySQL database, but MythTV still +needs to know where the MySQL server is running. This information is in the +<CODE>mysql.txt</CODE> file. By default, it will be installed to +<CODE>/usr/local/share/mythtv</CODE>, but a copy placed into <CODE>~/.mythtv</CODE> +will over-ride the global configuration.</P> +<P>You must ensure that there aren't multiple, conflicting versions of this +file on your system! +<BLOCKQUOTE><CODE> +<PRE> +$ locate mysql.txt +/usr/local/share/mythtv/mysql.txt +/home/mythtv/.mythtv/mysql.txt +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>As you can see, in this example there are two <CODE>mysql.txt</CODE> files. If +they are not identical, then there may be unintended consequences.</P> +<P>You may also see this error if you completely fill the <CODE>/var</CODE> +partition. The most likely <EM>mythtv-related</EM> reason for this is an +overly large mythbackend or mythfrontend log file in <CODE>/var/log</CODE>. If +you have logging enabled for the backend, and myth runs for weeks at a time, +this may creep up and surprise you. Note that many system processes also +write to <CODE>/var</CODE> and the system may not boot if it is unable to write +to <CODE>/var</CODE> due to a full partition.</P> + +<H3>MySQL not connecting correctly</H3> + +<P>Your <B>MySQL</B> installation may have networking turned off. +Check that <CODE>/etc/mysql/my.cnf</CODE> <EM>does not</EM> contain +<CODE>skip-networking</CODE>. If it does, remove it. Also verify that +<CODE>bind-address</CODE> is set to your IP address instead of +<CODE>127.0.0.1</CODE>. If you change either of these items, restart +<B>MySQL</B>.</P> + +<H3>MySQL database is corrupt</H3> + +<P>If you have reason to believe that your MySQL database is corrupt, +execute the following commands to attempt to repair it.</P> +<P><B>NOTE</B>: Ensure that there are no programs accessing the database +while you attempt to repair it. Make sure that all backend and frontend +programs have exited.</P> +<P><CODE>mysqlcheck -r -umythtv -p<password> mythconverg</CODE></P> + +<H3>Using a MPEG-2 encoder card and the video appears "jittery"</H3> + +<H3>Using a MPEG-2 encoder card and the video is jumping up and down</H3> + +<P>This is a different problem than the one discussed in the previous +section. Currently, the ivtv driver or firmware appear to have some issues +if the vertical capture resolution is not the full screen height. If you +are having a jitter problem then ensure that you are capturing either 480 +lines (for NTSC) or 576 lines (for PAL). The default capture profiles may +need to be edited for your setup. Go to Settings->TV Settings->Recording +Profiles and adjust the <B>Default</B> and <B>Live TV</B> options to +480 or 576 from their defaults.</P> + +<H3>Screen goes blank but returns when mouse is moved or keyboard is used</H3> + +<P>This is due to DPMS, the Display Power Management System, which is used +to save power by turning off your monitor when the system decides that it's +not being used or due to a screensaver that has defaulted to a blank screen. +MythTV now has DPMS support built-in, and should intelligently handle the +screen. Continue reading if you wish to override DPMS and force it off.</P> +<P>Since it's likely that watching TV will not generate keyboard or mouse +events for a time, you need to turn off DPMS and the screensaver. There are +a few ways to do this. You may also need to check your BIOS for power +saving modes and disable screen blanking there as well.</P> +<P>Edit your <CODE>/etc/X11/XF86Config-4</CODE> or <CODE>/etc/X11/xorg.conf</CODE> +file, and look for: +<BLOCKQUOTE><CODE> +<PRE> +Section "ServerFlags" + #DontZap # disable <Ctrl><Alt><BS> (server abort) + #DontZoom # disable <Ctrl><Alt><KP_+>/<KP_-> (resolution switching) + AllowMouseOpenFail # allows the server to start up even if the mouse doesn't work + + Option "blank time" "0" + Option "standby time" "0" + Option "suspend time" "0" + Option "off time" "0" + Option "NoPM" "1" +EndSection +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Also, look for: +<BLOCKQUOTE><CODE> +<PRE> +Section "Device" + Identifier "device1" + VendorName "nVidia Corporation" + BoardName "NVIDIA GeForce 256 (generic)" + Driver "nv" + Option "DPMS" +EndSection +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>In this case, you would need to either delete the <CODE>Option "DPMS"</CODE> +line, or change it to <CODE># Option "DPMS"</CODE> to comment it out. The next +time you start XFree this change will take effect.</P> +<P>Finally, check: +<BLOCKQUOTE><CODE> +<PRE> +Section "Monitor" + Identifier "monitor1" + VendorName "Plug'n Play" + HorizSync 30-85 + VertRefresh 50-160 + + # Sony Vaio C1(X,XS,VE,VN)? + # 1024x480 @ 85.6 Hz, 48 kHz hsync + ModeLine "1024x480" 65.00 1024 1032 1176 1344 480 488 494 563 -hsync -vsync + + # TV fullscreen mode or DVD fullscreen output. + # 768x576 @ 79 Hz, 50 kHz hsync + ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630 + + # 768x576 @ 100 Hz, 61.6 kHz hsync + ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616 +EndSection +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Ensure that there isn't an <CODE>Option "DPMS"</CODE> in the Monitor +configuration.</P> +<P>You can also turn off DPMS from the Command Line, but this will not survive +a reboot. +<BLOCKQUOTE><CODE> +<PRE> +$ xset -dpms +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Using <CODE>xset +dpms</CODE> will turn it back on.</P> +<P>Another technique to try, which will turn off the screensaver: +<BLOCKQUOTE><CODE> +<PRE> +$ xset s off +</PRE> +</CODE></BLOCKQUOTE> + +You may also combine the command to turn off DPMS and the screensaver: +<BLOCKQUOTE><CODE> +<PRE> +$ xset -dpms s off +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Finally, depending on your distribution, you may be able to turn it off from +within the control panel.</P> +<H2><A NAME="ss22.5">22.5</A> <A HREF="#toc22.5">Miscellaneous</A> +</H2> + +<H3>mythfilldatabase failing</H3> + +<P>If mythfilldatabase suddenly appears to be failing, there are at least +two things to check. </P> +<P>First, if you are in North America, ensure that your DataDirect subscription +is still valid, otherwise, check to see what version of XMLTV you're +running and that it's the latest version.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: It is highly recommended that you run the latest +version of XMLTV available. Your listings provider may have made changes +which negatively impact XMLTV.</CAPTION> +</FIGURE> +</P> + +<H3><A NAME="Setting_DMA"></A> Fast CPU, choppy or jittery video </H3> + +<P>First, you should check that your kernel has been enabled for DMA: +<BLOCKQUOTE><CODE> +<PRE> +[mythtv@pvr mythtv]$ dmesg |grep DMA + ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA + ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio +hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63, UDMA(33) +hdb: 80043264 sectors (40982 MB) w/2048KiB Cache, CHS=4982/255/63, UDMA(33) +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>From the listing above, you can see that hda, hdb and hdc are set for DMA, +and hdd is set for pio. If your kernel is not reporting DMA being enabled, +you may need to recompile your kernel. Check your motherboard's chipset +(look in the "ATA/IDE/MFM/RLL support" section in "make menuconfig") for more +information.</P> +<P>Next, check that the hard drive has DMA enabled. Use the <B>hdparm</B> +program to check and enable DMA. +<BLOCKQUOTE><CODE> +<PRE> +# hdparm -d /dev/hd? +</PRE> +</CODE></BLOCKQUOTE> + will tell you the DMA status for your hard drives. If you run +<B>hdparm</B> with the <CODE>-d1</CODE> parameter, it will turn DMA on.</P> + +<P>You may also setup your PC to do this at boot time, either by adding the +command to your <CODE>/etc/rc.local</CODE> file, or by adding files to +/etc/sysconfig.</P> +<P>On Mandriva and other distributions, if you install <B>hdparm</B> from an RPM you +will most likely get a <CODE>/etc/sysconfig/harddisks</CODE> file installed. +This file will be parsed by the <CODE>/etc/rc.sysinit</CODE> script. If you use +the default <CODE>harddisks</CODE> file, your changes will affect all IDE devices +(including CD ROMs). If you wish to use different parameters for various +devices, rename and/or copy the file to <CODE>harddiskhda</CODE>, +<CODE>harddiskhdb</CODE>, etc. Edit the file to your liking and on the next +reboot your setting will be preserved.</P> + +<H3>Frontend appears to be slow at jumping / seeking.</H3> + +<H3>On-screen Display shows incorrect program length.</H3> + +<P>This may occur when MythTV doesn't have an accurate seek table. Run +<B>mythcommflag --rebuild</B></P> + +<H3><A NAME="Troubleshooting_Audio"></A> Troubleshooting audio </H3> + +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: the following instructions do not apply to PVR-250/350 +encoders; the MPEG-2 file will have the audio embedded in the stream so it +is not accessible using <CODE>/dev/dsp</CODE>. </CAPTION> +</FIGURE> +</P> +<P>Audio appears to be one of the bigger issues that users run into on the +mailing list. If the audio isn't configured correctly, then MythTV will +often appear to hang, when in fact it is trying to manipulate the audio +subsystem and failing. You may or may not receive error messages indicating +that the source of the error is the audio subsystem.</P> +<P>You can not use <B>xawtv</B> to determine if your audio is working +correctly, since <B>xawtv</B> is simply using the analog sound patched +through line-in to line-out. It doesn't need to digitize the sound unless +you are using the recording function.</P> +<P>A better test to verify that sound will work for MythTV (and recording with +<B>xawtv</B> for that matter) is to startup <B>xawtv</B>, mute the +line-in then run <CODE>aplay /dev/dsp</CODE>. You should hear the recorded audio +slightly delayed behind the real-time video. You should see messages about +"underrun". These can be ignored but they do confirm that the driver is +loaded and there is an active device. Once this test succeeds, MythTV +should work correctly because it writes to and read from /dev/dsp in +the same way that <B>aplay</B> does.</P> +<P>To record audio along with video the audio signal must be digitized by a DSP +so that the audio data can be stored in a file. On playback, the audio data +is written to /dev/dsp and converted back to an analog signal. This analog +signal should then be sent to your speakers. Here is what is needed in +<B>alsamixer</B>. If you are using an ALSA version after 1.0.6, use +<B>alsamixer -V all</B>:</P> +<P>CAPTUR source - the analog source to be sent to the DSP. This should be set +to the input source from the tuner card to the sound card. In most cases +this is Line but this could also be Aux, CD, Mic, etc., depending on how you +connect the input cable. This source should be muted to prevent patching +through the analog sound. The volume of this source will not affect the +record level.</P> +<P>Capture mixer - this sets the level for the analog to digital recording. +While a volume of 100% is recommended for testing, distortion may occur. +Lowering this level to 75% to 85% may result in better audio quality. +"Capture" should be marked as the CAPTUR destination.</P> +<P>PCM mixer - this sets the level for the digital to analog playback. While a +volume of 100% is recommended for testing, distortion may occur. Lowering +this level to 75% to 85% may result in better audio quality.</P> +<P>Master mixer - sets the level for the analog signal sent to line-out or the +speakers.</P> +<P>You may also want to ensure that <CODE>/dev/dsp</CODE> , or whatever device file +is being used, hasn't already been grabbed by another process, like +<B>esd</B> or <B>artsd</B>. If the device file isn't available, then +MythTV won't work. You may wish to run <B>configure</B> and enable +support for these.</P> +<P>If you wish to see what application is grabbing a resource, you can use the +<CODE>fuser</CODE> command: +<BLOCKQUOTE><CODE> +<PRE> +# fuser -v /dev/dsp +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>To disable aRts in KDE, go to KDE->Control Center->Sound->Sound System and +uncheck the "Start aRts soundserver on KDE startup" box. Run <CODE># killall +artsd</CODE> from the command line to stop the artsd program.</P> +<P>If you're using multiple sound cards and multiple tuners, use <CODE>alsamixer +-c 1</CODE> to work with the second sound card. The first card is #0, the +second card is #1, etc.</P> + +<H3>Mythbackend reports that your card is not reporting full duplex capabilities</H3> + +<H3>The mythbackend program told me to look at this section</H3> + +<P>mythbackend does a check to see if your sound device is capable of full +duplex operation. If it's not, it's most likely that you're going to run +into issues when you try to record and play sound at the same time. If your +backend is a separate machine than your frontend, then there's no problem, +since you're only going to be doing one thing at a time with the card. +Likewise, if you're running the frontend and backend on the same machine, +but you're using btaudio or a hardware encoder card such as the Hauppauge +PVR-250, DVB cards or HDTV capture cards as your recording source and you're +only using the playback function of your sound card, then you also shouldn't +have an issue, since the sound card isn't being asked to perform two +functions at once.</P> +<P>If you can't get your sound card to go full-duplex and need it to, then check +your distribution for updated sound drivers. If your sound card is not +capable of full-duplex operation, either because the drivers don't support +it, or it has been designed that way, then you're pretty much out of luck +and will either need to purchase a new sound card, or will need to get +btaudio +<A HREF="#btaudio">operational</A>.</P> + +<H3>My remote doesn't work / works sometimes and not others / "ghost" keypresses</H3> + +<P>This can be due to a number of factors. The simplest case is the +"ghost" keypresses. For me, it was due to compact fluorescent lights in +the same room as the IR receiver, which the receiver was picking up as +keypresses. Once the lights were switched to incandescent bulbs, the ghost +went away.</P> +<P>You may have an issue with <B>lirc</B> misinterpreting IR commands from a +different remote. I also have an issue where the TiVo "Peanut" remote will +eventually cause <B>lircd</B> to stop responding; even though <B>lircd</B> +is configured for the Pinnacle Systems remote, the TiVo remote IR patterns +are being seen by the IR receiver.</P> +<P>If your remote has been properly configured, and <B>irw</B> and +<B>irxevent</B> are working correctly, then it's highly likely that your +window manager is not giving focus correctly to the various Myth programs as +they run. The following window managers are known to work correctly:</P> +<P> +<UL> +<LI>fvwm</LI> +<LI>blackbox (using "Sloppy Focus" and "Focus New Windows")</LI> +</UL> +</P> +<P><B>NOTE</B>: You do not need to use <B>irxevent</B> if you are using +MythTV's native LIRC support, so the window manager focus issue does not +apply in that case.</P> + +<H3>Where's "canada-cable"?</H3> + +<H3>Channels are off by one</H3> + +<P>There is no such thing as "Canada Cable"; Canada uses the same +frequencies as the United States. "Canada Cable" was a hack that some +people used when they would discover that their channels were off-by-one, +i.e. when tuning to channel 42, they might get channel 41 or 43. This is +actually due to the tuner on the video capture device being mis-detected. +You must manually specify the tuner type in your <CODE>/etc/modules.conf</CODE>. +See the video4linux mailing list ( +<A HREF="https://listman.redhat.com/mailman/listinfo/video4linux-list">https://listman.redhat.com/mailman/listinfo/video4linux-list</A>) for +more information.</P> + +<H3>Mythweb is showing a db_open error when I connect to it</H3> + +<P>Find your <CODE>php.ini</CODE> file. Make sure you've got a line in it like this:</P> +<P><CODE>extension=mysql.so</CODE></P> +<P>Restart <B>apache</B> for it to take effect.</P> + +<H3>Mouse pointer disappears when placed over the MythTV windows</H3> + +<P>This is the intended behavior. The MythTV interface is meant for use +with a remote control or a keyboard.</P> + +<H3>What does "strange error flushing buffer" mean on the console?</H3> + +<P>Nothing, really. It's just lame (the mp3 encoder) complaining for some +obscure reason. This seems to be fixed in more recent versions of the +libmp3lame library.</P> + +<H3>Can't change the channel when watching Live TV.</H3> + +<P>Something's wrong with your program database. Did mythfilldatabase run +with no major errors? Or, MythTV may not have permissions to the +appropriate video4linux devices. See the section titled +<A HREF="#devperms">Device Permissions</A> for an example.</P> + +<H3>Screen goes black when you try to play something</H3> + +<P>MythTV prints error and status messages to the shell that was used to +start the application. If nothing seems to be happening when you try to +view a program, try switching back to the shell and look for error messages +there, or, if you're running from a startup script, check the log file.</P> + +<H3>Poor performance with NVidia cards and XvMC</H3> + +<P>XvMC is a NVidia driver feature which is supposed to help with decoding +video. Users have reported that rather than speeding up their video it +appears to be doing the opposite. You may want to check that your color +depth is set for 24bpp.</P> + +<H3>Computer is loading a media player application when you insert a CD or DVD</H3> + +<P>You need to disable any sort of auto-running media player in your +environment, otherwise MythDVD or MythMusic will not be able to work +properly.</P> +<P>In KDE, you may want to perform the following: +<BLOCKQUOTE><CODE> +<PRE> +$ rm ~/.kde/Autostart/Autorun.desktop +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H2><A NAME="s23">23.</A> <A HREF="#toc23">Miscellaneous. </A></H2> + +<H2><A NAME="ss23.1">23.1</A> <A HREF="#toc23.1">I'd like to watch the files without using MythTV / I'd like to convert the files to some other format</A> +</H2> + +<P>First, check if the <B>mytharchive</B> plugin does what you want. If not, then +read on:</P> +<P>MythTV comes with a utility called <B>mythtranscode</B> which can +decode nuv files into raw format for use with other applications. This +command-line utility was not designed to be used by the end-user, but +instead to be called by other applications or scripts. Programs like +<B>nuvexport</B> ( +<A HREF="http://forevermore.net/myth/">http://forevermore.net/myth/</A>) are better suited for the end user. +However, since <B>mythtranscode</B> can be a useful tool, directions on +using it follow.</P> +<P><B>mythtranscode</B> creates raw streams, which means that they do not +contain any container information such as resolution, frame-rate, or audio +sampling rate. In order to process the output, you must supply this +information to the processing utility. <B>mythtranscode</B> provides the +relevant information on STDOUT.</P> +<P>There are two modes in which <B>mythtranscode</B> can create raw streams. +The first has no synchronization and assumes that the processing utility +will read audio and video at a constant rate. This method is useful when a +single application will be processing the raw output, such as +<B>mencoder</B> or <B>ffmpeg</B>. The second method assumes that two +separate applications will be processing the audio and video streams +independently, and there is no rate control between them which means that +the two programs don't coordinate their efforts to maintain synchronization.</P> + +<H3>mythtranscode example</H3> + +<P>First, start <B>mythtranscode</B>. You will need to determine the +channel and the start time manually. +<BLOCKQUOTE><CODE> +<PRE> +$ mythtranscode --chanid 1036 --starttime 2003-10-20T15:30:00 --profile \ +autodetect --fifodir . & +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>When <B>mythtranscode</B> begins executing, it will create two FIFOs +("audout" and "vidout") in the directory specified (in this case ".", +meaning the current directory) and will print out information about the +video stream.</P> +<P>The next step is to start the processing application. The following assumes +that the stream is NTSC 640x480 with 32Kbps audio.</P> +<P>To use <B>mencoder</B> you would enter a command like: +<BLOCKQUOTE><CODE> +<PRE> +mencoder -audiofile audout -audio-demuxer 20 -rawaudio rate=32000 \ +-rawvideo on:w=640:h=480:fps=29.97 -ovc lavc -oac mp3lame -o out.avi \ +vidout +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: You must use mencoder 1.0PRE1 or later. <B>mencoder</B> +version 0.9x <EM>WILL NOT WORK!</EM></CAPTION> +</FIGURE> + +Using ffmepg: +<BLOCKQUOTE><CODE> +<PRE> +ffmpeg -f u16le -ar 32000 -ac 2 -i audout -f rawvideo -s 640x480 -r 29.97 \ +-i vidout -vcodec mpeg4 -b 2000 -acodec mp3 -ab 128 out.avi +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Or to play directly using mplayer (again 1.0PRE1 or later is needed): +<BLOCKQUOTE><CODE> +<PRE> +mplayer -audiofile audout -audio-demuxer 20 -rawaudio rate=32000 \ +-rawvideo on:w=640:h=480:fps=29.97 vidout +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you wanted to write the raw data to separate audio and video files for +later processing, the following would work (note the use of --fifosync +for rate-control): +<BLOCKQUOTE><CODE> +<PRE> +$ mythtranscode --chanid 1036 --starttime 2003-10-20T15:30:00 \ +--profile autodetect --fifodir . --fifosync & +$ cat audout > audio.raw & +$ cat vidout > video.yuv +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss23.2">23.2</A> <A HREF="#toc23.2">Using a different window manager</A> +</H2> + +<P>MythTV is not dependent on any particular window manager. If you wish to +run a lightweight window manager, the <CODE>contrib/configfiles/</CODE> directory has an +example of a <CODE>.twmrc</CODE> and <CODE>.fvwmrc</CODE> file you may use.</P> + +<H2><A NAME="capture_resolution_"></A> <A NAME="ss23.3">23.3</A> <A HREF="#toc23.3">What capture resolution should I use? How does video work? </A> +</H2> + +<P>While MythTV allows you to set various GUI and capture resolutions, not +all combinations make sense.</P> +<P>First, analog video signals have a defined vertical resolution. In NTSC, +the video standard specifies that there are 525 vertical scan lines. Once +the "extra" lines are removed (they're used to synchronize the video signal, +and encode closed captioning data), you have 480 horizontal lines stacked +vertically.</P> +<P>In PAL, there are 625 "raw" lines of resolution, with a net of 576 +horizontal lines stacked vertically.</P> +<P>Horizontally, the maximum value allowed for a Bt8X8 chip is 720. However, +due to limitations in the chip and other limitations of broadcast +television, there may not be a noticeable improvement in image quality +beyond 400 or 500 pixels.</P> +<P>With this in mind, there are certain commonly accepted values for +resolution. While other values may be accepted for the vertical +resolution, they will cause scan lines to be repeated or dropped.</P> +<P>From "best" to "worst", in NTSC: +<UL> +<LI>720x480 "DVD" resolution. ReplayTV High and medium resolution</LI> +<LI>704x480 DVD standalone recorder standard resolution</LI> +<LI>640x480 4:3</LI> +<LI>544x480 TiVo Best resolution</LI> +<LI>480x480 SuperVCD (SVCD) Video CD resolution, TiVo High resolution</LI> +<LI>352x480 ReplayTV "Standard" quality, TiVo Basic and Medium resolution, DVD "LP" resolution</LI> +<LI>320x480 </LI> +<LI>544x240</LI> +<LI>480x240 </LI> +<LI>352x240 Video CD (VCD) resolution</LI> +<LI>320x240</LI> +</UL> +</P> +<P>As you can see, the lower quality values are half of the better ones. +720x240 is possible, but isn't a good tradeoff relative to the number of +vertical lines lost. In a PAL country, the you would use values like +720x576 or x288.</P> +<P>The higher resolutions will be more CPU intensive if you're using software +encoding (PVR-250/350 will have minimal host CPU impact even if you're using +720x480). If the CPU is overtaxed, frames will be dropped causing uneven +motion. You will likely see the best results at resolutions which average at +least 10% CPU idle time. You can use system tools such as <CODE>top</CODE> or +<CODE>sar</CODE> to check the CPU % idle while recording. If the CPU average +usage is consistently exceeding 90%, frames will need to be dropped during +peak times when more than 100% of the available CPU would be needed to +process all of the frames.</P> +<P>If you'd like to read more on this, go to the vcdhelp website at +<A HREF="http://www.vcdhelp.com/forum/userguides/94382.php">http://www.vcdhelp.com/forum/userguides/94382.php</A>.</P> + +<H2><A NAME="ss23.4">23.4</A> <A HREF="#toc23.4">MythTV GUI and X Display Sizes</A> +</H2> + +<P>MythTV is designed to be run as dedicated full screen TV application +but can also be run as a desktop application on a computer monitor. Here +are a few consideration for configuring sizes to best suit you needs.</P> + +<H3>X Dimensions</H3> + +<P>For output to a Television, common resolutions are 640x480, 800x600, and +some rare devices support 1024x768. Generally, higher resolutions are +better. However, you may find that you prefer the picture quality at one of +the lower resolutions. Everything in MythTV is scalable and should 'fit' +regardless of the resolution you choose.</P> +<P>Edit your X configuration file, usually <CODE>/etc/X11/XF86Config-4</CODE> for +XFree, or <CODE>/etc/X11/xorg.conf</CODE> for Xorg, so that the resolution you +want to use is listed first in the lists under "Screen". If this resolution +is higher than the resolutions supported by your output device, you will see +a 'panning' effect where moving the mouse to the edge will scroll around a +desktop area which is larger than the display size. If this happens, edit +your X configuration file to match the display size then restart X.</P> + +<H3>MythTV Dimensions</H3> + +<P>From "mythfrontend" go to Setup->Appearance. +The default for the height and width is "0" - this will cause +MythTV to automatically size itself to full screen.</P> +<P>If the MythTV GUI width and height are not 0, mythfrontend uses these GUI +dimensions and is anchored to the upper left corner of the X Desktop. If +the GUI X and/or Y are not 0, the upper left corner is positioned at the +specified coordinates. If the "Run the frontend in a window" box is checked, +the window will have a frame and can then be dragged to any position on the +desktop.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: When the GUI is full screen, you may see windows rapidly +flipping on top of each other. If this happens you will need to set your +window manager to 'Click to Focus' for windows to stack properly.</CAPTION> +</FIGURE> + +The fonts for the GUI and OSD will scale to whatever sizes you use. Most +font sizes can be changed in setup selections or in the .xml files under +<CODE>/usr/local/share/mythtv/</CODE> . Make sure to use fonts large enough +to be read on a TV screen from a distance.</P> +<P>The full screen TV size is based on the X display size. For Xinerama, you +can specify a screen in Setup->General. The TV picture will be stretched +to fit the entire GUI area regardless of the +<A HREF="#capture_resolution_">capture resolutions</A> used. However, during playback, the "W" key can +to used to correct differences between 16:9 and 4:3.</P> + +<H3>Overscan Dimensions</H3> + +<P>Because picture edges can be ragged and screen edges aren't straight, +Television is designed to project an image larger than the physical screen. +This is called "overscan". Underscan is fitting the entire image inside the +screen. Underscan is useful for computer monitors so that toolbars and +scrollbars at the edges can be seen.</P> +<P>For best results, match the X display area as close as possible to the edges +of the physical screen. This can only be adjusted by your tv-out device or +by the settings for the television set. Many sets have these adjustments in +a 'service mode'. If you cannot make these adjustments, there will be black +borders around the edges of the X desktop, MythTV GUI and TV playback.</P> +<P>MythTV has settings for "Overscan" in Setup->Playback. These can not, and do +not, cause the image to display beyond the edge of the X display area. The +purpose of these settings are to cut off rough edges and to expand the image +so that objects will appear to be the same size as a normal overscanned TV +picture.</P> + +<H2><A NAME="backupdb"></A> <A NAME="ss23.5">23.5</A> <A HREF="#toc23.5">Saving or restoring the database </A> +</H2> + +<P>See the <B>mysqldump</B> manpage for more information. +<BLOCKQUOTE><CODE> +<PRE> +$ mysqldump -u mythtv -pmythtv mythconverg -c > mythtv_backup.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>To restore: (assuming that you've dropped the database) +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root +mysql>create database mythconverg; +mysql>exit +$ mysql -u mythtv -pmythtv mythconverg < mythtv_backup.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>You may need to alter the MySQL permissions if this database is being shared +with multiple systems. See the +<A HREF="#modify_perm_mysql">Modifying access to the MySQL database for multiple systems</A> section for more +information.</P> + +<H2><A NAME="ss23.6">23.6</A> <A HREF="#toc23.6">Deleting the MySQL database</A> +</H2> + +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Performing this step will remove the entire database. You will lose all of your settings and will need to re-run the mc.sql script +to setup the database structure before running the mythtv-setup program.</CAPTION> +</FIGURE> + +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root +mysql> drop database mythconverg; +mysql> quit +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss23.7">23.7</A> <A HREF="#toc23.7">Moving your data to new hardware</A> +</H2> + +<P>This assumes that you will be moving your data to newer / bigger hardware +and don't want to lose your programs.</P> +<P>The first step is to create a database backup as demonstrated in an earlier +section.</P> +<P>Next, you will extract only the data that is relevant to the programs: +<BLOCKQUOTE><CODE> +<PRE> +$ grep "INSERT INTO record " mythtv_backup.sql > restore.sql +$ grep "INSERT INTO recorded " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO oldrecorded " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO recordedprogram " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO recordedrating " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO recordedmarkup " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO recordedseek " mythtv_backup.sql >> restore.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><B>NOTE</B>: Newer versions of <B>mysqldump</B> place backticks around +the table names. Backticks are not the same as apostrophes! On a typical +North American keyboard, backticks are located to the left of the "1" key, +on the same key as the tilde. Also, because the <B>bash</B> shell may try +to interpret the backticks, make sure you use a \ before each one.</P> +<P>If your <CODE>restore.sql</CODE> file is empty, you'll need to re-run the +commands like this: +<BLOCKQUOTE><CODE> +<PRE> +$ grep "INSERT INTO \`record\` " mythtv_backup.sql > restore.sql +$ grep "INSERT INTO \`recorded\` " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO \`oldrecorded\` " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO \`recordedprogram\` " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO \`recordedrating\` " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO \`recordedmarkup\` " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO \`recordedseek\` " mythtv_backup.sql >> restore.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Note the space after the table name and the ">>" to append to the file for +all but the first <B>grep</B>. "recordedmarkup" and "recordedseek" are +huge and there may be hundreds of thousands of lines if you had lots of +hours of recordings.</P> +<P>After you have moved the data files to the new hardware, configure MythTV +using the <B>mythtv-setup</B> program as you normally would with a +standard MythTV installation.</P> +<P>At this point we will restore the information about your programs back into +the database: +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u mythtv -pmythtv mythconverg < restore.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>After successful insertion of the data you may delete the +<CODE>restore.sql</CODE> file.</P> + +<H2><A NAME="btaudio"></A> <A NAME="ss23.8">23.8</A> <A HREF="#toc23.8">btaudio </A> +</H2> + +<P>btaudio allows you to obtain the audio data from your tuner card directly +over the PCI bus without using a sound card. This is useful if you would +like to use multiple tuner cards in a system without adding a sound card for +each one, or if your existing sound card is not capable of full-duplex +operation.</P> +<P>In order to use btaudio, your tuner card will need certain hardware +installed on it, and that hardware must be wired correctly. The chip that +will allow you to use the btaudio module is the MSP34xx. However, having a +MSP34xx is no guarantee that you will be able to use the btaudio module.</P> +<P>As of 2003-03-31, this is the current list of cards and their status: +Works with btaudio:</P> +<P> +<UL> +<LI>Hauppauge WinTV-radio with dbx-TV stereo, model 401</LI> +<LI>Hauppauge WinTV-Theater, model 495, 498 (Europe)</LI> +<LI>ATI TV Wonder</LI> +</UL> +</P> +<P>The following cards do not work: +<UL> +<LI>Pinnacle Studio PCTV Pro - note: this has a MSP34xx, but it's not +wired correctly to the BT878 chip.</LI> +<LI>ATI TV Wonder VE</LI> +<LI>Leadtek Winfast 2000 XP (PAL, UK and NTSC)</LI> +<LI>I/O Magic PC-PVR. No MSP34xx chip.</LI> +</UL> +</P> +<P>The following cards have been reported to work, but have issues: +<UL> +<LI>Avermedia AVerTV Studio (no digital DSP output, "whiney noise" on +analog)</LI> +</UL> +</P> +<P>Once btaudio loads, it should register additional <CODE>/dev/dsp</CODE> and +<CODE>/dev/mixer</CODE> devices. Typing <CODE>$ dmesg</CODE> will let you know +what's going on.</P> + +<H2><A NAME="ss23.9">23.9</A> <A HREF="#toc23.9">Removing unwanted channels</A> +</H2> + +<P>If <B>mythfilldatabase</B> grabbed a channel which you do not want to +include in your TV listings, you can remove the entries from the grabber +configuration and the MySQL database. This often happens with premium +channels; for example, HBO or Showtime may be available on your cable TV +system, but is scrambled because you're not a subscriber to that channel. +Since you can never watch it, you want to get rid of it.</P> +<P>If you are using the DataDirect service, login to your account at +<A HREF="http://labs.zap2it.com/">http://labs.zap2it.com/</A> to +modify your lineup. Uncheck the boxes for any unwanted channels, and they +will no longer be included in your download.</P> +<P>If you are using a grabber from XMLTV, comment out the channel from the +<CODE>~/.mythtv/<sourcename>.xmltv</CODE> file by inserting the word "not +" (including the space) in front of the unwanted entry. This will prevent +<B>xmltv</B> from grabbing future listings.</P> +<P>Next, delete the unwanted item from the channel table so that it will not +appear in the EPG or when changing channels. To delete the data from the +database we need to perform some steps. First, assuming that HBO is channel +15, we need to find out the internal <CODE>chanid</CODE> used by MySQL: +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root mythconverg +mysql> select chanid from channel where channum=15; ++--------+ +| chanid | ++--------+ +| 1015 | ++--------+ +1 row in set (0.00 sec) +mysql> delete from channel where chanid = 1015; +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Old program data will be removed over the course of a week. However, you may +want to immediately delete any current program listings for the channel that +has been removed: +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root mythconverg +mysql> delete from program where chanid = 1015; +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="ss23.10">23.10</A> <A HREF="#toc23.10">NFS</A> +</H2> + +<P>You may want to use a central server to store your files. </P> +<P>On the host machine, (in this case, the hostname is "masterbackend") you'll +want to edit your <CODE>/etc/exports</CODE> file and use something like: +<BLOCKQUOTE><CODE> +<PRE> +/var/video (rw) +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>To export the <CODE>/var/video</CODE> directory with read / write privileges.</P> +<P>On the "slave" machine, you'll want to edit the <CODE>/etc/fstab</CODE> file and +add something like: +<BLOCKQUOTE><CODE> +<PRE> +masterbackend:/var/video /var/video nfs rsize=8192,wsize=8192,hard,intr,nfsvers=3,actimeo=0 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Then run <CODE># mount -a</CODE> to re-read the file to mount the file system.</P> +<P>In this case, the source is a machine called "masterbackend" which is +exporting the directory "/var/video", which we're mounting locally at +"/var/video". The rsize and wsize options are used to increase the +performance of NFS; "hard,intr" is there because that's the recommendation +of the NFS-HOWTO, the nfsvers is required for filesizes over 2GB and actimeo +is used to turn off file attribute caching. Attribute caching for a shared +media point causes problems; you always want to see the latest state of the +directory and files. See +<A HREF="http://www.mythtv.org/wiki/index.php/Optimizing_Performance">http://www.mythtv.org/wiki/index.php/Optimizing_Performance</A> for +additional information regarding performance optimization.</P> + +<H2><A NAME="ss23.11">23.11</A> <A HREF="#toc23.11">Automatically starting mythfrontend at system boot time</A> +</H2> + +<P>Here's an example submitted to the mythtv-dev list by Pat Pflaum +<A HREF="mailto:pat@netburp.com">mailto:pat@netburp.com</A> using fvwm: +<BLOCKQUOTE><CODE> +<PRE> +$ cat > .xinitrc +fvwm & +mythfrontend +^D +$ cat > .fvwmrc +Style myth* NoTitle, NoHandles, Sticky, WindowListSkip, SloppyFocus, GrabFocus, BorderWidth 0 +^D +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>The following also works with blackbox: +<BLOCKQUOTE><CODE> +<PRE> +$ cat > .xinitrc +xset -dpms s off & +irxevent & +mythfrontend & +blackbox +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Make sure that your <CODE>.blackboxrc</CODE> file has: +<BLOCKQUOTE><CODE> +<PRE> +session.screen0.focusNewWindows: True +session.screen0.focusModel: SloppyFocus +</PRE> +</CODE></BLOCKQUOTE> + in it.</P> +<P> +<A NAME="mythbackend_autostart"></A> </P> +<H2><A NAME="ss23.12">23.12</A> <A HREF="#toc23.12">Automatically starting mythbackend at system boot time</A> +</H2> + +<H3>Red Hat And Mandriva</H3> + +<P>Here's a method for automatically starting mythbackend submitted by Mike +Thomson ( +<A HREF="mailto:linux@m-thomson.net">mailto:linux@m-thomson.net</A>) and Stu Tomlinson ( +<A HREF="mailto:stu@nosnilmot.com">mailto:stu@nosnilmot.com</A>).</P> +<P>Copy the files from the MythTV <CODE>contrib</CODE> directory or from Mike's web +site ( +<A HREF="http://m-thomson.net/mythtv/">http://m-thomson.net/mythtv/</A>) as follows:</P> +<P><CODE>etc.rc.d.init.mythbackend</CODE> should be made executable and copied to +<CODE>/etc/rc.d/init.d/</CODE>: +<BLOCKQUOTE><CODE> +<PRE> +$ cd contrib +$ su +# chmod a+x etc.rc.d.init.d.mythbackend +# cp etc.rc.d.init.d.mythbackend /etc/rc.d/init.d/mythbackend +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P><CODE>etc.sysconfig.mythbackend</CODE> should be copied to +<CODE>/etc/sysconfig/</CODE>: +<BLOCKQUOTE><CODE> +<PRE> +$ cd contrib +$ su +# cp etc.sysconfig.mythbackend /etc/sysconfig/mythbackend +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Edit <CODE>/etc/sysconfig/mythbackend</CODE> if you want to change the defaults +(the userid that should start mythbackend, location of the logfile and (if +required) the name and location of the mythbackend binary).</P> +<P>Use <B>chkconfig</B> to make sure the script is called when +entering runlevels 3, 4 or 5: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# chkconfig --level 345 mythbackend on +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P> +<A NAME="logrotate"></A> </P> +<H3>Log files </H3> + +<P>By default, the log file for mythbackend will be written to +<CODE>/var/tmp/mythbackend.log</CODE>. This has been tested and is known to work +on Mandriva and Red Hat, but many people prefer to place logs under +<CODE>/var/log/</CODE>.</P> +<P>To do this, create a group called <CODE>mythtv</CODE> (or anything you prefer) +and add your usual MythTV users to that group. If you changed the user that +starts mythbackend from the default of root you <EM>must</EM> perform this +step.</P> +<P>Create the directory <CODE>/var/log/mythtv</CODE> and set its +permissions as follows: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# mkdir /var/log/mythtv +# chown root:mythtv /var/log/mythtv +# chmod 0775 /var/log/mythtv +# exit +$ ls -ld /var/log/mythtv +drwxrwxr-x 2 root mythtv 4096 Apr 28 21:58 /var/log/mythtv/ +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Create a <CODE>mythtv</CODE> file in <CODE>/etc/logrotate.d</CODE>: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# cat > /etc/logrotate.d/mythtv +# Set default values for all log files first... + +# Rotate the logs once a week, or more frequently if they +# exceed 10Mb in size (size is checked daily). +weekly +size 10M + +# 'copytruncate' is used for logs generated by +# currently-running programs that should not be restarted +# (and can't be signalled to start a new log) after the +# rotation. It duplicates the existing log file and then +# sets the length of the existing file to 0. The only time +# this would break would be if the program writing the log +# was using lseek. +copytruncate + +# After rotating the files, leave the most recent rotated +# copy alone but gzip everything else to save space. +compress +delaycompress + +# If a log isn't present then don't worry about it. +missingok + +# Don't rotate an empty file. +notifempty + +# end of the global options + +/var/log/mythtv/mythbackend.log /var/log/mythtv/mythfrontend.log { + # Keep logs until they are 2 months old or the number of + # logs reaches 12. If the log files stay small, the age will + # kick in first and you'll only have 8 log files. If they + # get larger than 10Mb then you won't keep all 60 days. + rotate 12 + maxage 60 +} + +# Different options for mythfilldatabase: +/var/log/mythtv/mythfilldatabase.log { + rotate 2 +} +^D +# +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3>Mandriva </H3> + +<P>Mandriva adds one more twist in the form of the <CODE>msec</CODE> utility, +which runs regularly and (at the default or any higher security level) sets +permissions on many files, including those under <CODE>/var/log</CODE>.</P> +<P>To tell msec about the MythTV log files and their directory, you need to +edit the <CODE>/etc/security/msec/perm.local</CODE> file to include the +following: +<BLOCKQUOTE><CODE> +<PRE> +# /etc/security/msec/perm.local +# Local overrides to the msec program +# +# Full file path user.group permissions +/var/log/mythtv/ root.mythtv 775 +/var/log/mythtv/* root.mythtv 664 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>A copy of the above has been included in the contrib/ directory. You may +add it by typing: +<BLOCKQUOTE><CODE> +<PRE> +$ cd contrib +$ su +# cat etc.security.msec.perm.local >> /etc/security/msec/perm.local +# exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Finally run the <CODE>msec</CODE> tool to check and implement your +changes. +<BLOCKQUOTE><CODE> +<PRE> +$ su +# msec +# exit +$ +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: msec can only <EM>reduce</EM> the permissions of files, so if +you don't get the results you expect, check that you're not asking +<CODE>msec</CODE> to add missing permissions to the files or directories you +created.</CAPTION> +</FIGURE> +</P> +<H3>Gentoo</H3> + +<P>The portage file for MythTV has scripts that will allow you to run +mythbackend at startup.</P> +<P>To run mythbackend as a daemon which starts at boot time: +<BLOCKQUOTE><CODE> +<PRE> +# rc-update add mythbackend default +</PRE> +</CODE></BLOCKQUOTE> + +To stop mythbackend as a daemon: +<BLOCKQUOTE><CODE> +<PRE> +# /etc/init.d/mythbackend stop +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>To obtain a list of options: +<BLOCKQUOTE><CODE> +<PRE> +# /etc/init.d/mythbackend +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H2><A NAME="advanced_backend_config"></A> <A NAME="ss23.13">23.13</A> <A HREF="#toc23.13">Advanced Backend Configurations </A> +</H2> + +<P>MythTV is flexible in the way that you define multiple backend tuner +configurations. The only hard-and-fast rule is that the Master backend +<EM>must</EM> have a capture device defined, but shouldn't imply that the +capture device in the Master backend must be the first capture card defined in the +database.</P> +<P>One example of an advanced configuration is the round-robin scheme. Rather +than defining all of the cards on the master, you could first go into +mythtv-setup on the master to define globals such as the general configuration +and the channel lineup but not the host-specific configuration item like the +capture card. In this example, we will use a 4 tuner configuration, where two +slaves have one card each and the master has two. +<OL> +<LI>Add the first capture card on one of the slaves. Complete the +configuration, connecting the input source to the card. This will get +cardid #1 in the database. Exit mythtv-setup.</LI> +<LI>Configure the first capture card on the master backend. This will get +cardid #2 in the database. Exit mythtv-setup.</LI> +<LI>Configure the first capture card on the second slave. This will be +cardid #3 in the database. Exit mythtv-setup.</LI> +<LI>Configure the second capture card on the master backend. This will +get cardid #4 in the database. Exit mythtv-setup.</LI> +</OL> +</P> +<P>Using this scheme, the master backend will not use both capture cards until +one of the following happens: +<UL> +<LI>There are four recordings scheduled for the same time</LI> +<LI>Both slaves are unavailable</LI> +</UL> +</P> +<P>The scheduler in MythTV checks whether an encoder is available; if a slave +backend isn't running, its encoder isn't available, so the scheduler will +look for the next available encoder. This makes MythTV very flexible; slave +tuners can come and go, and as long as there are enough tuners for what +you'd like to record it doesn't matter which tuner in particular is going to +be used.</P> +<P>Using this round-robin scheme along with a shared storage directory like +NFS and enabling the Master Backend Override setting will allow you to view +content even if the slave backend that recorded a program is not available.</P> + +<H2><A NAME="ss23.14">23.14</A> <A HREF="#toc23.14">Using the transcoder</A> +</H2> + +<P>MythTV's built-in transcoder re-encodes recordings from one codec to +another. The transcoder has three primary uses; it can transcode MPEG-2 +files captured using a hardware encoder (PVR cards, DVB cards, ATSC HD, +etc.) to MPEG-4, it can be used to transcode RTjpeg files (usually only used +on systems that can not real-time encode to MPEG-4 using a framegrabber) to +MPEG-4, and finally it can be used to remove commercials from a MPEG-2 file +while leaving the file in MPEG-2 format.</P> +<P>When MythTV transcodes a file to MPEG-4 or RTjpeg the resulting file format +is NuppelVideo (nuv). NuppelVideo is a container which provides a method of +keeping the audio and video in sync throughout the recording, which is why +it is used instead of the <CODE>.avi</CODE> format. You may have difficulty +playing <CODE>.nuv</CODE> files in non-MythTV systems.</P> + +<P>The original file is removed when the transcoding process is complete. +Unless you're sure that you will be satisfied with the result you may want +to enable the <B>mythtv-setup</B> option which causes <B>mythbackend</B> +to keep the original file after transcoding. This option is on the second +page of the General section in mythtv-setup. Enabling this allows you to +compare the two files and restore the original if you like. Outside of the +initial setup phase it usually isn't necessary to leave this option enabled. +A recording can be transcoded in two ways:</P> +<P> +<UL> +<LI>Automatically transcode the file once it has completed +recording.</LI> +<LI>Manually choosing to transcode a recording, usually after +importing a cutlist or manually marking commercials to be +removed.</LI> +</UL> +</P> +<P>The second method can be used on files that have already been transcoded (or +files which were are already in the desired format), so only the frames +immediately following a cut section will be re-encoded, resulting in a +minimal loss of quality when removing commercials with the added benefit of +being extremely quick.</P> +<P>The current transcoding system has a lot flexibility, but there are +a number of steps involved in setting it up. In order to +automatically transcode a given recording you must do the following: +<OL> +<LI>Configure recording profile for your capture source and enable +transcoding on one or more profiles.</LI> +<LI>Configure one or more transcoding profiles.</LI> +<LI>Create or alter existing scheduled recordings to enable +transcoding for that recording.</LI> +</OL> +</P> + +<H3>Configuring Recording Profiles to Allow Transcoding</H3> + +<P>Enter the Utilities/Setup > Setup > TV Settings > Recording Profiles +section in <B>mythfrontend</B>. Choose the option that corresponds to +your capture source (ignore the Transcoders for now.) Choose the quality +profile you are interested in using for transcoding. Ensure that "Enable +auto-transcode after recording" is checked. </P> + +<H3>Configure Transcoding Profiles</H3> + +<P>Enter the Recording Profiles > Transcoders menu. There are three quality +settings to choose from and a two special Autodetect settings. Later, when +scheduling recordings you'll have to choose one of Autodetect, High, Medium, +and Low Quality transcode settings in addition to the recording profile we +set up above. If you choose the Autodetect transcoding profile for a +recording, MythTV will use the "Autodetect from RTjpeg/MPEG-4" profile for +recordings which are RTjpeg/MPEG-4 files. Otherwise, it will use the +"Autodetect from MPEG-2" profile provided it's an MPEG-2 recording. If you +choose one of the others (High, Medium, Low) it will use the settings in +that profile regardless of the codec of the original recording.</P> +<P>There are a number of options for transcoding but the simplest is to enable +lossless transcoding (the first option) which subsequently removes all other +options. Enabling lossless encoding simply removes commercials (if you've +marked them) and attempts to clean up MPEG-2 streams. Note that with this +option MythTV will not apply any sort of filters and will only attempt to +normalize the stream into something cleaner and less likely to have trouble +with other less forgiving MPEG-2 hardware/software (including players, video +editors, etc.)</P> +<P>If you enable resizing of the recording the next page has the settings for +choosing the final resolution. MythTV will scale the video as appropriate, +not crop it to this resolution.</P> +<P>The final two pages allow configuration of the video and audio codecs. +Although RTjpeg is an option for video codec there is no reason to transcode +<EM>to</EM> this format because it will produce larger files than MPEG-4 and +the recording will take <EM>more</EM> CPU power to play back. The MPEG-4 +settings are described in the documentation for the <B>ffmpeg</B> project +at +<A HREF="http://ffmpeg.sourceforge.net/ffmpeg-doc.html">http://ffmpeg.sourceforge.net/ffmpeg-doc.html</A>. It's a matter of +trial and error to discover which settings achieve a good compromise between +size and quality.</P> +<P>If you wish to return to the default settings, they are Bitrate: 2200-2500, +MaxQ: 2, MinQ: 15, MaxQDiff: 3, and "Scale bitrate for frame size" is +enabled. The other options are unchecked. </P> + +<H3>Create/Alter Scheduled Recordings to Enable Transcoding</H3> + +<P>Transcoding is actually enabled on a per-recording basis. Two things +must be true before any given recording will be auto-transcoded, however. +The first is that the recording must have been made with a recording profile +that has auto-transcode enabled. Under "Storage Options" for the recording +you must set the "Record using the "X" profile" to the profile you +configured in the first step. In addition, under the "Post Recording +Options" section of the recording you must also set "Transcode new +recordings." This is also where you specify the Transcoding profile to use +(Auto, High, Medium, Low.)</P> +<P>It may not be obvious from above but the flexibility of this system is +primarily to make it possible to auto-transcode a show recorded via one +source (ie: pcHDTV 3000), and not transcode that same show if it's recorded +on another kind of card (ie: PVR-250.) There are other uses however. You +could have a PVR-250 and a V4L card. You may want to transcode the MPEG-2 +from the PVR-250 but there is no need to transcode the recordings made with +the V4L card, as it's already likely to be MPEG-4.</P> +<P>As an example, you could configure the Default profile for "Hardware DVB +Encoders" (the profile group used for DVB cards, including ATSC cards like +the pcHDTV 3000) to "Enable auto-transcoding". In the Default profile for +MPEG-2 Encoders (PVR cards) you'd leave "Enable auto-transcoding" unchecked. +For programs that are available on both kinds of cards you'd set the +recording profile to Default and enable auto-transcoding in the record +settings. Then you pick your transcoding profile. The result is that when +a program is recorded on your DVB card, it will get transcoded. When it +plays on a channel available via your PVR card, it won't be.</P> + +<H3>Manual Transcoding</H3> + +<P>Manually transcoding is activated while watching a show by hitting 'x', +from the OSD menu by choosing the Transcode option, or by choosing Job +Options/Transcode from the info menu from the Watch or Delete +Recordings screens.</P> +<P>The transcoding profile used for manual transcoding is whatever was set when +the recording was originally configured, even if you didn't enable +auto-transcoding. The only way to change what transcoding profile will be +used is to alter the transcoder column in the recorded table in the +database. The transcoder column contains a number which corresponds with +the id column in the recordingprofiles table. You can find out the id +number for each profile in the transcoder group with an SQL command like:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +mysql> select r.* from recordingprofiles r,profilegroups p where p.name='Transcoders' and p.id=r.profilegroup; ++----+----------------+------------+------------+--------------+ +| id | name | videocodec | audiocodec | profilegroup | ++----+----------------+------------+------------+--------------+ +| 21 | RTjpeg/MPEG4 | MPEG-4 | MP3 | 6 | +| 22 | MPEG2 | MPEG-4 | MP3 | 6 | +| 27 | High Quality | MPEG-4 | MP3 | 6 | +| 28 | Medium Quality | MPEG-4 | MP3 | 6 | +| 29 | Low Quality | MPEG-4 | MP3 | 6 | ++----+----------------+------------+------------+--------------+ +5 rows in set (0.01 sec) + +mysql> +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Armed with the knowledge of what the profile ID's are you can also choose to +run mythtranscode from the command line and explicitly specify the transcoder +profile. Run <CODE>mythtranscode --help</CODE> for usage information.</P> + +<H2><A NAME="ss23.15">23.15</A> <A HREF="#toc23.15">Changing your hostname</A> +</H2> + +<P>If you need to change the name of the computers used with MythTV you'll +need to perform a sequence of steps. There are a number of pieces of +information that MythTV keeps track of which are tied to the hostname of the +box, so changing the hostname involves altering the name in the +operating system and in the MySQL database. In the examples below, the old +name of the system was "frontend1" and we're going to change it to +"kidsroom".</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: Changing the hostname using direct SQL update commands will +break things. You <EM>MUST</EM> use this indirect method.</CAPTION> +</FIGURE> + </P> +<P>1. Stop all backends. If you run <B>mythbackend</B> from a terminal +session, press control-c. If your backends are started with an init +script, you would do something like the following: +<BLOCKQUOTE><CODE> +<PRE> +$ su +# /etc/init.d/mythbackend stop +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>2. Change the hostname.</P> +<P>For Red Hat and derived distributions, edit the +<CODE>/etc/sysconfig/network</CODE> file. Look for +<CODE>HOSTNAME=frontend1</CODE> and change this to +<CODE>HOSTNAME=kidsroom</CODE> or whatever you'll be using. For other +distributions, refer to the documentation, such as the +<PRE> +hostname(1) +</PRE> + man page.</P> + +<P>To alter the +hostname in the current session, run: +<BLOCKQUOTE><CODE> +<PRE> +# hostname kidsroom +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>3. Dump the database. +<BLOCKQUOTE><CODE> +<PRE> +$ mysqldump -u mythtv -pmythtv mythconverg -c > mythtv_backup.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>4. Rename the host in the database. First, ensure that the new hostname +you'll be using isn't already in the database. +<BLOCKQUOTE><CODE> +<PRE> +$ grep kidsroom mythtv_backup.sql +</PRE> +</CODE></BLOCKQUOTE> + +Now we're actually going to change the name. The following should all be +typed on the same line: +<BLOCKQUOTE><CODE> +<PRE> +$ cat mythtv_backup.sql | sed s/\'frontend1\'/\'kidsroom\'/g >> mythtv_restore.sql +</PRE> +</CODE></BLOCKQUOTE> + +If you don't feel comfortable using <B>sed</B>, you can open the +<CODE>mythtv_backup.sql</CODE> file in a text editor and perform a global search +and replace. When saving the file, make sure you use the new name, +<CODE>mythtv_restore.sql</CODE> or the rest of the steps below will fail.</P> +<P>5. Drop and recreate the database. +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u root +mysql>drop database mythconverg; +mysql>create database mythconverg; +mysql>exit +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>6. Restore the database using your edited version. +<BLOCKQUOTE><CODE> +<PRE> +$ mysql -u mythtv -pmythtv mythconverg < mythtv_restore.sql +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>If you are running slave backends or frontends, don't forget to re-enable +access as detailed in +<A HREF="#modify_perm_mysql">Modifying access to the MySQL database for multiple systems</A>. </P> +<P>7. Start the backends. If you use init scripts, do the following, otherwise +start them from terminal consoles. +<BLOCKQUOTE><CODE> +<PRE> +# /etc/init.d/mythbackend start +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>8. Quit and restart all frontends. Delete the <CODE>mythtv_backup.sql</CODE> +and <CODE>mythtv_restore.sql</CODE> files.</P> + +<H2><A NAME="ss23.16">23.16</A> <A HREF="#toc23.16">Can I run MythTV on my TiVo?</A> +</H2> + +<H2><A NAME="ss23.17">23.17</A> <A HREF="#toc23.17">Can I run MythTV on my ReplayTV?</A> +</H2> + +<P>No.</P> +<P>While it is true that the TiVo runs the Linux kernel, and TiVo has released +their changes to the kernel under the GPL, the TiVo is <EM>not</EM> a +general-purpose computer, and there is no programming information available +for the custom hardware contained within a TiVo. TiVo is under no +obligation to release the source code to their <EM>application</EM>.</P> +<P>The ReplayTV runs VxWorks, a Real Time Operating System from Wind River +Systems.</P> +<H2><A NAME="ss23.18">23.18</A> <A HREF="#toc23.18">Can a wireless connection be used between the frontend and the backend?</A> +</H2> + +<P>Yes, assuming that your wireless connection has sufficient bandwidth to +maintain the datarate between the frontend and the backend. 802.11b should +be sufficient if the encoded bitrate of the content is less than the +datarate of your wireless connection, which in the case of 802.11b would be +approximately 4 Mbps. (The advertised rate of 11Mbps gives an actual +throughput of 4 Mbps.) 802.11a and 802.11g, if operating in their high-speed +modes, or proprietary 802.11b "Turbo" schemes should be adequate. Multiple +wireless frontends, poor signal strength or other factors can severely +impact the viewing experience on the frontend.</P> + +<H2><A NAME="ss23.19">23.19</A> <A HREF="#toc23.19">How can I burn shows that I have recorded to a DVD?</A> +</H2> + +<P>Use the mytharchive plugin.</P> + +<H2><A NAME="ss23.20">23.20</A> <A HREF="#toc23.20">Using the DBoxII within MythTV</A> +</H2> + +<P>The configuration of the DBoxII for use within MythTV is tricky (as of +May 16 2005), that's why it's covered here. Your DBoxII has to be running +linux and the Neutrino GUI instead of the stock BetaNova firmware. For +further information, please refer to +<A HREF="http://www.tuxbox.org">http://www.tuxbox.org</A>. Additionally, you need to enable the SPTS +mode in Neutrino.</P> +<P> +<UL> +<LI>Add a new "Capture Card" in the setup. The "Card type" is "DBOX2 Input", +the other values have to be adjusted according to your setup. +The default values, except for the "DBOX2 host ip", should work fine.</LI> +<LI>Define a new video source. It doesn't need to be configured, +you just need to define it. MythTV grabs the EPG from the DBoxII.</LI> +<LI>Connect the DBoxII to the newly defined input source in "input connections".</LI> +<LI>Since channel scanning is not implemented yet, you need to define channels +in the "Channel Editor". Make sure that you use the same value for +"Channel Name" as on the DBoxII. You can get a list of available +channels from the web interface of Neutrino at http://ip-of-your-box:80/. +Associate the channel with your new video source and repeat when needed.</LI> +</UL> +</P> +<P>You may leave the Setup now and proceed as usual.</P> + +<H2><A NAME="ss23.21">23.21</A> <A HREF="#toc23.21">What do the icons on the Watch Recordings screen mean?</A> +</H2> + +<P>Press "1" or F1 to get a popup.</P> +<H2><A NAME="ss23.22">23.22</A> <A HREF="#toc23.22">What do the letters mean when I change channels?</A> +</H2> + +<P>These letters let you know what's going on with the backend as it tries +to tune to a channel.</P> +<P>Lower case = seen</P> +<P>Upper Case = seen & good +<UL> +<LI>l/L = Lock : This could be seen by PVR-250/BTTV users</LI> +<LI>a/A = PAT : Any recording transmitted in MPEG </LI> +<LI>m/M = PMT : Any recording transmitted in MPEG </LI> +<LI>g/G = MGT : ATSC only</LI> +<LI>v/V = VCT : ATSC only</LI> +<LI>n/N = NIT : DVB only</LI> +<LI>s/S = SDT : DVB only</LI> +</UL> +</P> +<H2><A NAME="ss23.23">23.23</A> <A HREF="#toc23.23">What is the difference between the various Hauppauge PVR models?</A> +</H2> + +<P>This is covered in the hardware section, and extensively covered on the +Hauppauge website. ( +<A HREF="http://www.hauppauge.com/pages/compare_pvr.html">http://www.hauppauge.com/pages/compare_pvr.html</A>) Please check the +Hauppauge website for the most accurate information.</P> +<P>A PVR-150 comes in a number of versions: +<UL> +<LI>The PVR-150 (Model 1045) is the retail kit. It comes with a remote +control and an IR Blaster. It does not have a radio tuner.</LI> +<LI>The PVR-150 MCE (Model 1042) will usually come in a plain white box and is +sold as an OEM device. It does not come with a remote control, since it's +usually used as the second, third, etc capture device.</LI> +<LI>The PVR-150 MCE Kit (Model 1062) does not have a radio tuner and +comes with a Microsoft Media Center remote control instead of Hauppauge's.</LI> +<LI>The PVR-150 low profile (Model 1086) is a low-profile card. It has a +radio tuner and is approximately half the height of a standard card. +However, it comes with a low-profile PCI bracket, so it is not suitable for +use in a standard PCI slot without removing the bracket, which may not be +worth the trouble.</LI> +</UL> +</P> +<P>A PVR-250 (Model 980) is a retail kit which comes with an IR receiver and a +remote control.</P> +<P>The PVR-250 MCE (Model 975) contains a FM radio tuner. The PVR-250 MCE does +not contain a IR receiver or a remote.</P> +<P>The PVR-250 Rev 1 contained an MPEG-2 decoder. However, this function was +not connected to any output jacks, and there doesn't appear to be any way to +pull decoded video from the card, so it's a fairly useless feature.</P> +<P>The PVR-350 (model 990) has the features of the PVR-250 as well as being +able to decode MPEG-2. The encode and decode functions may be used +simultaneously. The MPEG-2 decoder function gives superior video quality +compared to what you'll find on a standard video card. However, the decoder +function is only available once Linux has started, so you will not see any +boot-time messages. Also, the card is not capable of resolutions higher +than 720x480, so it cannot be used with HDTV. Make a conscious decision +(and ask for advice on the mailing list) that you want to tradeoff potential +HDTV use in the future compared to video quality.</P> +<P>The X-driver for the PVR-350 support playback using Xv efficiently but does +not support any other 2D or 3D acceleration. For some application this may +place a large load on the host CPU, some will run without any problem and +others (mplayer, xine, xmame etc.) should be configured to utilize the Xv +interface.</P> +<P>Note that for the PVR-350 there are some +<A HREF="#PVR-350">considerations</A> +regarding the way audio is handled.</P> +<P>The PVR-500 is a dual-encoder version of the PVR-150 card, so you can +simultaneously record two different programs at the same time, because there +are two encoder chips on the PCI card. Hauppuage has also installed an +onboard splitter, so you can use one COAX to feed both tuners. Current +versions of the PVR-500 should come with an adapter to allow you to connect +a second S-Video or composite input, but this will take up a second PCI +slot. Early adopters may need to purchase this item separately.</P> + +<H2><A NAME="ss23.24">23.24</A> <A HREF="#toc23.24">Changing channels on an external Set Top Box</A> +</H2> + +<P>If you need to use an external Set Top Box (STB), such as for satellite +TV or for digital cable you will need some way for MythTV to tell the STB to +switch to a new channel. There are several methods: +<OL> +<LI>Use an IR blaster. An IR blaster is an infrared transmitter connected +to your computer. When MythTV needs to change channels it will send IR +pulses, thereby emulating a remote control.</LI> +<LI>Use a direct serial connection. Some STB's have a serial port on the +back, although it may not look like a serial port. It may look like a phone +jack, or a strange VGA connector. It may be labeled "Low Speed Data". A +direct serial connection is more reliable than an IR blaster. Not all STB's +that have a Low Speed Data port have it enabled; you may need to convince +your service provider to turn it on. Stating that you have a Tivo may help; +the Tivo has a direct-connect capability.</LI> +<LI>Use a firewire connection. There is a <CODE>6200ch.c</CODE> in the MythTV +contrib directory which may work for you.</LI> +</OL> +</P> +<H2><A NAME="ss23.25">23.25</A> <A HREF="#toc23.25">Configuring one machine to flag all commercials</A> +</H2> + +<P>Commercial flagging can be CPU intensive. By default, the backend that +created a recording is the one which will flag commercials. You may wish to +use a different machine to run commercial flagging.</P> +<P>On the slower machine:</P> +<P>Start the mythtv-setup program. Advance through the pages until you get to +the Job Queue page. Turn off the setting that says "Allow Commercial +Detection jobs", thereby preventing any commercial flagging jobs from +running on this machine.</P> +<P>Next, make sure that "Run Jobs only on original recording host" is turned +OFF so that new jobs are allowed to run anywhere.</P> +<P>Restart <B>mythbackend</B> since it only reads this setting when it starts +up.</P> +<P>On the faster machine:</P> +<P>Start the <B>mythtv-setup</B> program. Advance through the pages until +you get to the Job Queue page. Ensure that "Allow Commercial Detection +jobs" is turned ON for this machine.</P> +<P>Run <B>mythjobqueue</B>. <B>mythjobqueue</B> will examine the JobQueue +and run any jobs it finds. <B>mythjobqueue</B> should be left running so +that it will pick up any new commercial flagging jobs that are added to the +queue, otherwise new jobs will be added to the queue and your programs won't +be flagged until you run manually run <B>mythjobqueue</B>.</P> +<P>Using this technique it's possible to add commercial flagging machines as +needed, even on systems that aren't running a backend. It's also possible +to run the commercial flagger in a virtual machine environment such as +VMWare.</P> + +<H2><A NAME="s24">24.</A> <A HREF="#toc24">Example Configurations.</A></H2> + +<H2><A NAME="LVM"></A> <A NAME="ss24.1">24.1</A> <A HREF="#toc24.1">Logical Volume Manager (LVM) </A> +</H2> + +<P>LVM greatly increases the flexibility you have in managing your storage +than traditional physical partitions. This section will provide some brief +notes on how to use LVM to create storage space for your video files and how +to add additional disk space in the future. There's lots more that can be +done with LVM, so check the LVM HOWTO +<A HREF="http://tldp.org/HOWTO/LVM-HOWTO/">http://tldp.org/HOWTO/LVM-HOWTO/</A> document for details.</P> + +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: If you are running MythTV 0.21 and you are using LVM to +create one large filesystem to store your recordings, it's no longer +recommended that you go the LVM route. The preferred solution is to use +<A HREF="#storagegroups">Storage Groups</A>. They're more flexible and less +likely to lose all of your recordings if you have a drive failure.</CAPTION> +</FIGURE> +</P> +<P>If you don't understand how to partition a drive, or how to change the +partition type you should stop and look at documentation on how to perform +these steps.</P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>BIG FAT WARNING</B>: Using an incorrect parameter can make your files +inaccessible, prevent your computer from booting, etc. Be careful!</CAPTION> +</FIGURE> +</P> +<P>Make sure your kernel configuration includes LVM support or that it's +available as a module. Today, most vendors include this by default. You'll +also want to ensure that you have a copy of the LVM utilities; check your +distribution, or get the latest versions from +<A HREF="http://www.sistina.com/products_lvm.htm">http://www.sistina.com/products_lvm.htm</A> and build them manually.</P> +<P>Check that the <B>vgscan</B> program is being run at some point during +your boot sequence - most distributions do this by default. Look for a +message during boot up that looks like this: <CODE>vgscan -- reading all +physical volumes (this may take a while...)</CODE> If you don't see any +messages during boot, you may need to install a LVM init script or confirm +that you have all of the LVM packages installed from your distribution.</P> +<P>LVM uses a few concepts you should be familiar with before starting. +<UL> +<LI>PV (Physical Volume). The actual partition on the hard drive.</LI> +<LI>VG (Volume Group). The aggregation of all the PVs make a VG.</LI> +<LI>LV (Logical Volume). Subdivision of the pool of space available in +the VG into individual chunks, like /usr, /var/video, etc.</LI> +</UL> +</P> +<P>The following example assumes that you want to create a LVM partition from a +chunk of space in /dev/hda5, using a reiserfs filesystem and mounted on +/var/video. You later decide to extend this filesystem by adding a new disk: +/dev/hdb.</P> +<P>You need to create at least one LVM partition for a physical volume. Use +<B>fdisk</B> or your favorite partition editor to set the type to LVM +(0x8e). If you're using an entire disk, create one big partition rather than +using the device itself. e.g. use /dev/hdb1 not /dev/hdb. </P> +<P>In the following example, you have a 15GB disk. The first 6GB are set as +your boot partition. <CODE>/dev/hda2</CODE> was added as an extended partition, +and within that partition you created the <CODE>/dev/hda5</CODE> linux (ext2) +partition.</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +# fdisk /dev/hda + +The number of cylinders for this disk is set to 1823. +There is nothing wrong with that, but this is larger than 1024, +and could in certain setups cause problems with: +1) software that runs at boot time (e.g., old versions of LILO) +2) booting and partitioning software from other OSs + (e.g., DOS FDISK, OS/2 FDISK) + +Command (m for help): p + +Disk /dev/hda: 15.0 GB, 15000330240 bytes +255 heads, 63 sectors/track, 1823 cylinders +Units = cylinders of 16065 * 512 = 8225280 bytes + + Device Boot Start End Blocks Id System +/dev/hda1 * 1 764 6136798+ 83 Linux +/dev/hda2 765 1823 8506417+ 5 Extended +/dev/hda5 765 1823 8506417 83 Linux + +Command (m for help): t +Partition number (1-6): 5 +Hex code (type L to list codes): 8e + +Command (m for help): p + +Disk /dev/hda: 15.0 GB, 15000330240 bytes +255 heads, 63 sectors/track, 1823 cylinders +Units = cylinders of 16065 * 512 = 8225280 bytes + + Device Boot Start End Blocks Id System +/dev/hda1 * 1 764 6136798+ 83 Linux +/dev/hda2 765 1823 8506417+ 5 Extended +/dev/hda5 765 1823 8506417 8e Linux LVM + +Command (m for help): w + +# +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Create the LVM physical volume from the partitions (repeat if you have +multiple partitions to use): +<BLOCKQUOTE><CODE> +<PRE> +# pvcreate /dev/hda5 +</PRE> +</CODE></BLOCKQUOTE> + +Create a LVM volume group out of this physical volume called "VGforMyth" that is +allocated in chunks that are a multiple of 64MB +<BLOCKQUOTE><CODE> +<PRE> +# vgcreate VGforMyth -s 64m /dev/hda5 +</PRE> +</CODE></BLOCKQUOTE> + +Create a logical volume of 5GB called "video" and then create the reiserfs +filesystem and mount it: +<BLOCKQUOTE><CODE> +<PRE> +# lvcreate --name video --size 5G VGforMyth +# mkreiserfs /dev/VGforMyth/video +# mount /dev/VGforMyth/video /var/video +</PRE> +</CODE></BLOCKQUOTE> + +Now create a 3GB volume for mythmusic files if you like: +<BLOCKQUOTE><CODE> +<PRE> +# lvcreate --name music --size 3G VGforMyth +# mkreiserfs /dev/VGforMyth/music +# mount /dev/VGforMyth/music /var/music +</PRE> +</CODE></BLOCKQUOTE> + +Display the volume group status: +<CODE># vgdisplay -v</CODE></P> +<P>Now, lets suppose you want to add a 60GB hard disk to the system as hdb and +allocate 50GB of it to video storage.</P> +<P>First, create a single partition /dev/hdb1 covering the whole disk and make +it type 0x8e using your partition editor.</P> +<P><CODE># fdisk /dev/hdb</CODE> +.... create partition, set type, save and reboot if it says you have to</P> +<P>Create the new LVM physical volume:</P> +<P><CODE># pvcreate /dev/hdb1</CODE></P> +<P>Add the new physical volume to the volume group:</P> +<P><CODE># vgextend VGforMyth /dev/hdb1</CODE></P> +<P> +<FIGURE> +<EPS FILE="stop.eps"> +<IMG SRC="stop.png"> +<CAPTION><B>NOTE</B>: You may get errors at this point stating that there are no +physical volumes available for adding to the LV, even though you know for a +fact that there are. You may need to specify the physical volume in the <CODE>/dev/ide/host/bus/target/lun/etc</CODE> format.</CAPTION> +</FIGURE> + +Once you've completed one of the following two procedures, use <B>df</B> +to check that you've got more space.</P> +<P>Make the logical volume used for video bigger:</P> +<P><CODE># lvextend --size +50G /dev/VGforMyth/video</CODE></P> +<H3>ReiserFS</H3> + +<P>Unmount, resize and remount the filesystem. Technically, you don't need to +unmount and remount the ReiserFS. +<BLOCKQUOTE><CODE> +<PRE> +# umount /var/video +# resize_reiserfs /dev/VGforMyth/video +# mount /dev/VGforMyth/video /var/video +</PRE> +</CODE></BLOCKQUOTE> +</P> + +<H3>ext2 or ext3</H3> + +<P>LVM comes with a program called <B>resize2fs</B>.</P> +<P>Unmount, resize and remount the filesystem. The filesystem <EM>must</EM> be +unmounted during this procedure. +<BLOCKQUOTE><CODE> +<PRE> +# umount /var/video +# resize2fs --size +50G /dev/VGforMyth/video +# mount /dev/VGforMyth/video /var/video +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H3>xfs</H3> + +<P>XFS does not need to be unmounted to extend the size: +<BLOCKQUOTE><CODE> +<PRE> +# xfs_growfs /var/video +</PRE> +</CODE></BLOCKQUOTE> +</P> +<H2><A NAME="advancedpartitionformatting"></A> <A NAME="ss24.2">24.2</A> <A HREF="#toc24.2">Advanced Partition Formatting </A> +</H2> + +<P>The partitions that your distribution sets up for you may not be +optimized for large files. Using LVM in conjunction with the following +techniques can be quite useful.</P> +<P>Unlike a typical filesystem, a MythTV video partition is usually a very +large filesystem filled with a fairly small number of large files. +Filesystem I/O is usually not an issue, even in multi-tuner and/or +multi-frontend setups.</P> +<P>There is however, one aspect of filesystem performance that can have a +bearing on the performance of MythTV. In Linux, deleting a file will +utilize I/O bandwidth until the deletion has been completed. If deleting +the file takes long enough, the video capture buffer may overrun, thereby +resulting in dropped frames. Some filesystems are faster at deleting files +than others and, for multi-gigabyte MythTV video files, these differences +can be significant.</P> +<P>Fortunately, there are published tests ( +<A HREF="http://aurora.zemris.fer.hr/filesystems/big.html">http://aurora.zemris.fer.hr/filesystems/big.html</A>) that provide +insight into filesystem performance under conditions relevant to MythTV +usage. In addition, some limited testing (archived at +<A HREF="http://www.gossamer-threads.com/lists/mythtv/users/52672">http://www.gossamer-threads.com/lists/mythtv/users/52672</A>) +with very large files (10 gigabytes) was reported in the MythTV Users +mailing list.</P> + +<H3>Ext2</H3> + +<P>Ext2 was the defacto standard Linux filesystem for many years. It is +stable, provides good I/O performance and can quickly delete large files. +The primary disadvantage of Ext2 is that it is not a journaling filesystem, +so a file system consistency check (fsck, which is normally only performed +after a system crash) can take many hours on a filesystem the size of a +typical MythTV partition.</P> + +<H3>Ext3</H3> + +<P>Ext3 is Ext2 with a journal, so your biggest gain is that in case of a +crash and reboot you won't have to wait very long for your partition to be +remounted.</P> +<P>There are options available when formatting an Ext3 partition, as in: +<BLOCKQUOTE><CODE> +<PRE> +# mkfs.ext3 -T largefile4 /dev/hdb1 +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>This example assumes that <CODE>/dev/hdb1</CODE> has already been created using +<B>fdisk</B>. If you're using LVM, <CODE>/dev/hdb1</CODE> may be something like +<CODE>/dev/VGforMyth/video</CODE>.</P> +<P>The "-T largefile4" option creates one inode per 4 megabytes, which can +provide a few percent more storage space. However, tests indicate that +using the "-T largefile4" option can drastically increase the amount of time +required to delete a large file and thus it should only be used with encoder +settings that produce small video files (YMMV).</P> +<P>You can check on your filesystem using the <B>dumpe2fs</B> program. See +the man page for details.</P> +<H3>ReiserFS</H3> + +<P>The Reiser filesystem is another journaling filesystem commonly +distributed with Linux. It is known to be an extremely efficient filesystem +and it especially excels at managing partitions containing a large number of +small files. However, tests indicate it is not the fastest at deleting very +large files. For that reason, it may not be the best choice when using +encoder bitrates that produce very large files.</P> + +<H3>JFS</H3> + +<P>JFS (Journaling File System) is a journaling filesystem originally +developed by IBM for AIX which was later released as open source. While not +as common as Ext3 or ReiserFS, it is distributed with RedHat 9 (RH9), Fedora +Core and Mandriva as well as other distros. According to tests, JFS is the +file deletion speed king, deleting virtually any file in under one second, +even files as large as 10 gigabytes.</P> + +<H3>XFS</H3> + +<P>XFS is a journaling file system originally developed by SGI for Irix, and +later released as open source. While not a part of the default RedHat Linux +9 or Fedora Core installation (although it is a part of Mandriva and Fedora +Core 2+), it can be easily installed via ATrpms. XFS provides deletion +speeds for large files only slightly slower than JFS. According to the test +results shown at ( +<A HREF="http://aurora.zemris.fer.hr/filesystems/big.html">http://aurora.zemris.fer.hr/filesystems/big.html</A>), XFS provide +higher I/O rates than JFS, albeit at a higher CPU loading. This may cause +issues if you do not have the spare CPU capacity to handle XFS, potentially +leading to dropped frames.</P> +<P> +<A NAME="migratingtoSD"></A> </P> +<H2><A NAME="ss24.3">24.3</A> <A HREF="#toc24.3">Migrating from DataDirect Labs to Schedules Direct</A> +</H2> + +<P>MythTV v0.20.2 or later is required to natively support Schedules Direct. +Code has been included to make the transition as simple as possible.</P> +<P><B>You do not need to delete your existing video sources or add new ones!</B> </P> +<P>The following steps should work for most users: +<UL> +<LI>Create a Schedules Direct account and use the same information as your +existing lineups at Zap2It Labs. Do not add or delete channels at this +time.</LI> +<LI>Shut down any running <B>mythfrontend</B> and <B>mythbackend</B> programs.</LI> +<LI>Perform a backup of your existing database. See +<A HREF="#backupdb">Saving or restoring the database</A> for instructions.</LI> +<LI>Run <B>mythtv-setup</B> -> Video Sources. Change the grabber to +Schedules Direct, update the username and password fields with the account +information you created at Schedules Direct and select "Retrieve Lineups". +Click Finish.</LI> +<LI>Exit <B>mythtv-setup</B> and run <B>mythfilldatabase</B>. Check +if there were any errors.</LI> +<LI>Restart your <B>mythbackend</B> and <B>mythfrontend</B> programs.</LI> +</UL> +</P> + +<H2><A NAME="ss24.4">24.4</A> <A HREF="#toc24.4">Caching support for Schedules Direct</A> +</H2> + +<P>MythTV 0.20.2 or later supports caching of downloaded information from +Schedules Direct, so devices that share a common source do not require +multiple downloads.</P> +<P>Before beginning, perform a backup of your existing database. See +<A HREF="#backupdb">Saving or restoring the database</A> for instructions.</P> +<P>In the following scenario, assume that you have the following: +<OL> +<LI>A PVR-150 MPEG-2 encoder card connected directly to a CATV source.</LI> +<LI>A PVR-250 MPEG-2 encoder card connected via S-Video to a CATV Set Top Box.</LI> +</OL> +</P> +<P>What we are going to do is to create a single lineup at Schedules Direct and +then create two Video Sources which use the same login information but have +different channels associated with them.</P> +<P>On your Schedules Direct account, create a lineup that has all of the +channels that you can receive. Because we have a Set Top Box (STB), choose +a Digital lineup. Yes, this means that you may have 900 channels in this +lineup, but that's OK.</P> +<P>Use the Schedules Direct channel editor and unselect any channels that you +can't tune without the STB. This will usually be channels higher than 125, +but check your CATV provider lineup if you're not sure. Once you've +deselected them (using a click on the first channel you can't receive and +then a shift-click on the last channel you can't receive will deselect all +the channels in between those two.) click the Save Changes button at the +bottom of the screen.</P> +<P>In <B>mythtv-setup</B>, create a Video Source with an appropriate name. +"SD-Analog Only" will be used in this example. Click "Retrieve Lineups" +and select the digital lineup you just created at Schedules Direct.</P> +<P>Click "Finish" to return to the Video sources selector and then press the +ESC key to go back to the main screen.</P> +<P>Now choose Input Connections. Select the PVR-150 which is connected +directly to the CATV. Set the Video Source to "SD-Analog Only" and click +"Fetch channels from listings source".</P> +<P>Set the start channel to an appropriate value.</P> +<P><B>NOTE</B>: There is a bug where the "Fetch" command may not work; you +can tell that the Fetch did not retrieve any channels in one of two ways: in +the text-mode console, you will see a connection to Schedules Direct, but it +doesn't appear to retrieve any channel information: +<BLOCKQUOTE><CODE> +<PRE> +2007-08-25 15:03:05.526 New DB DataDirect connection +2007-08-25 15:03:05.526 Connected to database 'mythconverg' at host: localhost +2007-08-25 15:03:05.536 DataDirect: Your subscription expires on 11/23/2007 01:12:10 PM +2007-08-25 15:03:05.707 New DB connection, total: 3 +2007-08-25 15:03:05.707 Connected to database 'mythconverg' at host: localhost +2007-08-25 15:03:05.708 sourceid 2 has lineup type: CableDigital +2007-08-25 15:03:06.623 Data fetching complete. +2007-08-25 15:03:06.624 DataDirect: Deleting temporary files +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>or, the "Please add channels to this source" message in the "Starting +channel" field stays on the screen.</P> +<P>If either of these happens, save the information on this screen by clicking +the "Finish" button. Exit back to the Input connections screen by pressing +ESC, then select this Input Connection again. This time the Fetch will work +and the "Please add channels to this source" message will disappear.</P> +<P>If you look at the text-mode console, you'll see this if the channel +retrieval is working: +<BLOCKQUOTE><CODE> +<PRE> +2007-08-25 15:04:32.437 New DB DataDirect connection +2007-08-25 15:04:32.437 Connected to database 'mythconverg' at host: localhost +2007-08-25 15:04:32.447 DataDirect: Your subscription expires on 11/23/2007 01:12:10 PM +2007-08-25 15:04:32.622 New DB connection, total: 3 +2007-08-25 15:04:32.622 Connected to database 'mythconverg' at host: localhost +2007-08-25 15:04:32.623 sourceid 2 has lineup type: CableDigital +2007-08-25 15:04:33.418 DataDirect: Adding channel 41 'AMC' (AMC). +2007-08-25 15:04:33.422 DataDirect: Adding channel 32 'A & E Network' (AETV). +2007-08-25 15:04:33.425 DataDirect: Adding channel 66 'Black Entertainment Television' (BET). +2007-08-25 15:04:33.427 DataDirect: Adding channel 180 'Bravo' (BRAVO). +2007-08-25 15:04:33.430 DataDirect: Adding channel 51 'ABC Family' (FAM). +2007-08-25 15:04:33.432 DataDirect: Adding channel 146 'Country Music Television' (CMTV). +2007-08-25 15:04:33.435 DataDirect: Adding channel 39 'CNBC' (CNBC). +2007-08-25 15:04:33.437 DataDirect: Adding channel 36 'Cable News Network' (CNN). +2007-08-25 15:04:33.440 DataDirect: Adding channel 35 'CNN Headline News' (CNNH). +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>Repeat the Input Connection configuration for any other capture devices that +are connected directly to the CATV system. You do not need to click Fetch +once you've done one successful download of the channel information - the +Starting channel should be automatically populated.</P> +<P>Go back to Schedules Direct and re-enable the channels that you had +previously deselected, then click Save Changes.</P> +<P>Create a new Video Source, here called "SD-All Digital Channels". Perform +the same "Retrieve Listings" you did before.</P> +<P>Go back to the Input Connections screen, select the PVR-250 which is +connected to the STB, assign the "SD-All Digital Channels" video source and +perform a retrieve channels. This will pull down the complete channel +listing, but only for <EM>this</EM> device.</P> +<P>When <B>mythfilldatabase</B> runs, it will cache the "big" download which +is appropriate for the STB, and then copy the information to the channels +that can only be accessed without the STB. But by default +<B>mythfilldatabase</B> is going to notice that the "Analog only" video +source is missing the channels that are in the Digital lineup you created at +Schedules Direct, so we need to override the addition of new channels.</P> +<P>When you run <B>mythfilldatabase</B> to populate your database, you'll +need to run it like this:</P> +<P> +<BLOCKQUOTE><CODE> +<PRE> +$ mythfilldatabase --remove-new-channels +</PRE> +</CODE></BLOCKQUOTE> +</P> +<P>You will also need to modify how the <B>mythbackend</B> calls +<B>mythfilldatabase</B> when it performs its automatic listings update.</P> +<P>In <B>mythfrontend</B>, select "Setup" -> "General".</P> +<P>Continue press ENTER until you reach the Mythfilldatabase configuration +screen. In the "mythfilldatabase Arguments" field, type +--remove-new-channels</P> +<P>then press the TAB key until you reach Finish, then press ENTER to save. +You can then press ESC until you return to the main screen.</P> +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO.html b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO.html new file mode 100644 index 0000000..6efe675 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO.html @@ -0,0 +1,250 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<HTML> +<HEAD> + <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21"> + <TITLE>Installing and using MythTV</TITLE> + <LINK HREF="mythtv-HOWTO-1.html" REL=next> + + +</HEAD> +<BODY> +<A HREF="mythtv-HOWTO-1.html">Next</A> +Previous +Contents +<HR> +<H1>Installing and using MythTV</H1> + +<H2>Robert Kulagowski, +<A HREF="mailto:rkulagow@rocketmail.com">mailto:rkulagow@rocketmail.com</A></H2>2008-06-04, v0.21.02 +<HR> +<EM>Initially, installation of MythTV seems like a huge task. There are lots +of dependencies, and various distributions seem to do the same thing +different ways. This document will attempt to give general installation +instructions, as well as including distribution-specific instructions where +necessary.</EM> +<HR> +<P> +<H2><A NAME="toc1">1.</A> <A HREF="mythtv-HOWTO-1.html">First things first.</A></H2> + +<UL> +<LI><A NAME="toc1.1">1.1</A> <A HREF="mythtv-HOWTO-1.html#ss1.1">What is MythTV?</A> +<LI><A NAME="toc1.2">1.2</A> <A HREF="mythtv-HOWTO-1.html#ss1.2">QuickStart</A> +<LI><A NAME="toc1.3">1.3</A> <A HREF="mythtv-HOWTO-1.html#ss1.3">Upgrading from previous versions</A> +<LI><A NAME="toc1.4">1.4</A> <A HREF="mythtv-HOWTO-1.html#ss1.4">How to obtain this document / PDF versions of this document </A> +<LI><A NAME="toc1.5">1.5</A> <A HREF="mythtv-HOWTO-1.html#ss1.5">Books about MythTV</A> +<LI><A NAME="toc1.6">1.6</A> <A HREF="mythtv-HOWTO-1.html#ss1.6">Document conventions</A> +<LI><A NAME="toc1.7">1.7</A> <A HREF="mythtv-HOWTO-1.html#ss1.7">Mailing lists / getting help</A> +<LI><A NAME="toc1.8">1.8</A> <A HREF="mythtv-HOWTO-1.html#ss1.8">IRC</A> +<LI><A NAME="toc1.9">1.9</A> <A HREF="mythtv-HOWTO-1.html#ss1.9">Bug database</A> +<LI><A NAME="toc1.10">1.10</A> <A HREF="mythtv-HOWTO-1.html#ss1.10">Contributing to this document</A> +</UL> +<P> +<H2><A NAME="toc2">2.</A> <A HREF="mythtv-HOWTO-2.html">Introduction.</A></H2> + +<P> +<H2><A NAME="toc3">3.</A> <A HREF="mythtv-HOWTO-3.html">Checking prerequisites. </A></H2> + +<UL> +<LI><A NAME="toc3.1">3.1</A> <A HREF="mythtv-HOWTO-3.html#ss3.1">Hardware</A> +<LI><A NAME="toc3.2">3.2</A> <A HREF="mythtv-HOWTO-3.html#ss3.2">Software</A> +</UL> +<P> +<H2><A NAME="toc4">4.</A> <A HREF="mythtv-HOWTO-4.html">System Configuration Requirements for Compiling MythTV. </A></H2> + +<UL> +<LI><A NAME="toc4.1">4.1</A> <A HREF="mythtv-HOWTO-4.html#ss4.1">Software requirements for compiling MythTV</A> +<LI><A NAME="toc4.2">4.2</A> <A HREF="mythtv-HOWTO-4.html#ss4.2">Shared-Library requirements for MythTV </A> +<LI><A NAME="toc4.3">4.3</A> <A HREF="mythtv-HOWTO-4.html#ss4.3">Environment variable requirements for MythTV</A> +</UL> +<P> +<H2><A NAME="toc5">5.</A> <A HREF="mythtv-HOWTO-5.html">Downloading and compiling. </A></H2> + +<UL> +<LI><A NAME="toc5.1">5.1</A> <A HREF="mythtv-HOWTO-5.html#ss5.1">Building LAME</A> +<LI><A NAME="toc5.2">5.2</A> <A HREF="mythtv-HOWTO-5.html#ss5.2">XMLTV</A> +<LI><A NAME="toc5.3">5.3</A> <A HREF="mythtv-HOWTO-5.html#ss5.3">Configuring the Schedules Direct service </A> +<LI><A NAME="toc5.4">5.4</A> <A HREF="mythtv-HOWTO-5.html#ss5.4">Manually building MythTV</A> +<LI><A NAME="toc5.5">5.5</A> <A HREF="mythtv-HOWTO-5.html#ss5.5">Gentoo </A> +</UL> +<P> +<H2><A NAME="toc6">6.</A> <A HREF="mythtv-HOWTO-6.html">MySQL.</A></H2> + +<UL> +<LI><A NAME="toc6.1">6.1</A> <A HREF="mythtv-HOWTO-6.html#ss6.1">Distribution-specific information</A> +<LI><A NAME="toc6.2">6.2</A> <A HREF="mythtv-HOWTO-6.html#ss6.2">Setting up the initial database</A> +</UL> +<P> +<H2><A NAME="toc7">7.</A> <A HREF="mythtv-HOWTO-7.html">Configuring Sound.</A></H2> + +<UL> +<LI><A NAME="toc7.1">7.1</A> <A HREF="mythtv-HOWTO-7.html#ss7.1">Graphically setting up the mixer</A> +<LI><A NAME="toc7.2">7.2</A> <A HREF="mythtv-HOWTO-7.html#ss7.2">Setting the mixer from the command line</A> +</UL> +<P> +<H2><A NAME="toc8">8.</A> <A HREF="mythtv-HOWTO-8.html">Setting up a remote control.</A></H2> + +<UL> +<LI><A NAME="toc8.1">8.1</A> <A HREF="mythtv-HOWTO-8.html#ss8.1">Gentoo</A> +<LI><A NAME="toc8.2">8.2</A> <A HREF="mythtv-HOWTO-8.html#ss8.2">Obtaining and compiling lirc</A> +<LI><A NAME="toc8.3">8.3</A> <A HREF="mythtv-HOWTO-8.html#ss8.3">Completing the lirc install </A> +<LI><A NAME="toc8.4">8.4</A> <A HREF="mythtv-HOWTO-8.html#ss8.4">Additional information for lirc</A> +<LI><A NAME="toc8.5">8.5</A> <A HREF="mythtv-HOWTO-8.html#ss8.5">Configuring lirc for use with an IR blaster</A> +</UL> +<P> +<H2><A NAME="toc9">9.</A> <A HREF="mythtv-HOWTO-9.html">Configuring MythTV. </A></H2> + +<UL> +<LI><A NAME="toc9.1">9.1</A> <A HREF="mythtv-HOWTO-9.html#ss9.1">Configuring the Master backend system</A> +<LI><A NAME="toc9.2">9.2</A> <A HREF="mythtv-HOWTO-9.html#ss9.2">Post-configuration</A> +<LI><A NAME="toc9.3">9.3</A> <A HREF="mythtv-HOWTO-9.html#ss9.3">Configuring a non-master backend </A> +<LI><A NAME="toc9.4">9.4</A> <A HREF="mythtv-HOWTO-9.html#ss9.4">Configuring and running mythfilldatabase</A> +<LI><A NAME="toc9.5">9.5</A> <A HREF="mythtv-HOWTO-9.html#ss9.5">Grabbing channel icons for Schedules Direct users</A> +</UL> +<P> +<H2><A NAME="toc10">10.</A> <A HREF="mythtv-HOWTO-10.html">Configuring mythfrontend.</A></H2> + +<UL> +<LI><A NAME="toc10.1">10.1</A> <A HREF="mythtv-HOWTO-10.html#ss10.1">General</A> +<LI><A NAME="toc10.2">10.2</A> <A HREF="mythtv-HOWTO-10.html#ss10.2">Appearance</A> +<LI><A NAME="toc10.3">10.3</A> <A HREF="mythtv-HOWTO-10.html#ss10.3">Program Guide</A> +<LI><A NAME="toc10.4">10.4</A> <A HREF="mythtv-HOWTO-10.html#ss10.4">Playback </A> +<LI><A NAME="toc10.5">10.5</A> <A HREF="mythtv-HOWTO-10.html#ss10.5">Recording </A> +<LI><A NAME="toc10.6">10.6</A> <A HREF="mythtv-HOWTO-10.html#ss10.6">Xbox Frontends</A> +</UL> +<P> +<H2><A NAME="toc11">11.</A> <A HREF="mythtv-HOWTO-11.html">Using MythTV.</A></H2> + +<UL> +<LI><A NAME="toc11.1">11.1</A> <A HREF="mythtv-HOWTO-11.html#ss11.1">Keyboard commands</A> +<LI><A NAME="toc11.2">11.2</A> <A HREF="mythtv-HOWTO-11.html#ss11.2">Using themes with MythTV</A> +<LI><A NAME="toc11.3">11.3</A> <A HREF="mythtv-HOWTO-11.html#ss11.3">Adding DishTV information to the database</A> +<LI><A NAME="toc11.4">11.4</A> <A HREF="mythtv-HOWTO-11.html#ss11.4">Adding support for an external tuner</A> +<LI><A NAME="toc11.5">11.5</A> <A HREF="mythtv-HOWTO-11.html#ss11.5">Using Shutdown/Wakeup</A> +<LI><A NAME="toc11.6">11.6</A> <A HREF="mythtv-HOWTO-11.html#ss11.6">Controlling the mythfrontend via telnet</A> +</UL> +<P> +<H2><A NAME="toc12">12.</A> <A HREF="mythtv-HOWTO-12.html">Scheduling Recordings.</A></H2> + +<UL> +<LI><A NAME="toc12.1">12.1</A> <A HREF="mythtv-HOWTO-12.html#ss12.1">Record Types</A> +<LI><A NAME="toc12.2">12.2</A> <A HREF="mythtv-HOWTO-12.html#ss12.2">Scheduling Options</A> +<LI><A NAME="toc12.3">12.3</A> <A HREF="mythtv-HOWTO-12.html#ss12.3">Storage Options</A> +<LI><A NAME="toc12.4">12.4</A> <A HREF="mythtv-HOWTO-12.html#ss12.4">Post Recording Processing</A> +<LI><A NAME="toc12.5">12.5</A> <A HREF="mythtv-HOWTO-12.html#ss12.5">Advanced Recording Options</A> +<LI><A NAME="toc12.6">12.6</A> <A HREF="mythtv-HOWTO-12.html#ss12.6">Scheduling with more than one Input</A> +</UL> +<P> +<H2><A NAME="toc13">13.</A> <A HREF="mythtv-HOWTO-13.html">MythPlugins. </A></H2> + +<P> +<H2><A NAME="toc14">14.</A> <A HREF="mythtv-HOWTO-14.html">MythWeb.</A></H2> + +<UL> +<LI><A NAME="toc14.1">14.1</A> <A HREF="mythtv-HOWTO-14.html#ss14.1">Installation and prerequisites</A> +<LI><A NAME="toc14.2">14.2</A> <A HREF="mythtv-HOWTO-14.html#ss14.2">Completing the installation</A> +<LI><A NAME="toc14.3">14.3</A> <A HREF="mythtv-HOWTO-14.html#ss14.3">Resetting the key binding table</A> +<LI><A NAME="toc14.4">14.4</A> <A HREF="mythtv-HOWTO-14.html#ss14.4">Resetting the theme.</A> +</UL> +<P> +<H2><A NAME="toc15">15.</A> <A HREF="mythtv-HOWTO-15.html">MythGallery.</A></H2> + +<UL> +<LI><A NAME="toc15.1">15.1</A> <A HREF="mythtv-HOWTO-15.html#ss15.1">Installation and prerequisites</A> +<LI><A NAME="toc15.2">15.2</A> <A HREF="mythtv-HOWTO-15.html#ss15.2">Using MythGallery</A> +<LI><A NAME="toc15.3">15.3</A> <A HREF="mythtv-HOWTO-15.html#ss15.3">Importing Pictures</A> +</UL> +<P> +<H2><A NAME="toc16">16.</A> <A HREF="mythtv-HOWTO-16.html">MythGame.</A></H2> + +<UL> +<LI><A NAME="toc16.1">16.1</A> <A HREF="mythtv-HOWTO-16.html#ss16.1">Setup Directory Structure</A> +<LI><A NAME="toc16.2">16.2</A> <A HREF="mythtv-HOWTO-16.html#ss16.2">Download and Install xmame</A> +<LI><A NAME="toc16.3">16.3</A> <A HREF="mythtv-HOWTO-16.html#ss16.3">Download extra files</A> +<LI><A NAME="toc16.4">16.4</A> <A HREF="mythtv-HOWTO-16.html#ss16.4">Download and Install MythGame.</A> +<LI><A NAME="toc16.5">16.5</A> <A HREF="mythtv-HOWTO-16.html#ss16.5">Setup xmame in MythGame</A> +<LI><A NAME="toc16.6">16.6</A> <A HREF="mythtv-HOWTO-16.html#ss16.6">Hints:</A> +</UL> +<P> +<H2><A NAME="toc17">17.</A> <A HREF="mythtv-HOWTO-17.html">MythMusic. </A></H2> + +<UL> +<LI><A NAME="toc17.1">17.1</A> <A HREF="mythtv-HOWTO-17.html#ss17.1">Manual installation of prerequisites</A> +<LI><A NAME="toc17.2">17.2</A> <A HREF="mythtv-HOWTO-17.html#ss17.2">Mandriva</A> +<LI><A NAME="toc17.3">17.3</A> <A HREF="mythtv-HOWTO-17.html#ss17.3">Red Hat Linux 9</A> +<LI><A NAME="toc17.4">17.4</A> <A HREF="mythtv-HOWTO-17.html#ss17.4">Compiling MythMusic</A> +<LI><A NAME="toc17.5">17.5</A> <A HREF="mythtv-HOWTO-17.html#ss17.5">Configuring MythMusic</A> +<LI><A NAME="toc17.6">17.6</A> <A HREF="mythtv-HOWTO-17.html#ss17.6">Using MythMusic</A> +<LI><A NAME="toc17.7">17.7</A> <A HREF="mythtv-HOWTO-17.html#ss17.7">Troubleshooting MythMusic</A> +</UL> +<P> +<H2><A NAME="toc18">18.</A> <A HREF="mythtv-HOWTO-18.html">MythWeather.</A></H2> + +<P> +<H2><A NAME="toc19">19.</A> <A HREF="mythtv-HOWTO-19.html">MythVideo.</A></H2> + +<P> +<H2><A NAME="toc20">20.</A> <A HREF="mythtv-HOWTO-20.html">MythDVD.</A></H2> + +<UL> +<LI><A NAME="toc20.1">20.1</A> <A HREF="mythtv-HOWTO-20.html#ss20.1">Manual Compilation of Prerequisites</A> +<LI><A NAME="toc20.2">20.2</A> <A HREF="mythtv-HOWTO-20.html#ss20.2">Pre-compiled binaries</A> +<LI><A NAME="toc20.3">20.3</A> <A HREF="mythtv-HOWTO-20.html#ss20.3">Running the Myth Transcoding Daemon</A> +</UL> +<P> +<H2><A NAME="toc21">21.</A> <A HREF="mythtv-HOWTO-21.html">MythNews.</A></H2> + +<P> +<H2><A NAME="toc22">22.</A> <A HREF="mythtv-HOWTO-22.html">Troubleshooting.</A></H2> + +<UL> +<LI><A NAME="toc22.1">22.1</A> <A HREF="mythtv-HOWTO-22.html#ss22.1">Compiling</A> +<LI><A NAME="toc22.2">22.2</A> <A HREF="mythtv-HOWTO-22.html#ss22.2">Debugging </A> +<LI><A NAME="toc22.3">22.3</A> <A HREF="mythtv-HOWTO-22.html#ss22.3">Installing</A> +<LI><A NAME="toc22.4">22.4</A> <A HREF="mythtv-HOWTO-22.html#ss22.4">Using</A> +<LI><A NAME="toc22.5">22.5</A> <A HREF="mythtv-HOWTO-22.html#ss22.5">Miscellaneous</A> +</UL> +<P> +<H2><A NAME="toc23">23.</A> <A HREF="mythtv-HOWTO-23.html">Miscellaneous. </A></H2> + +<UL> +<LI><A NAME="toc23.1">23.1</A> <A HREF="mythtv-HOWTO-23.html#ss23.1">I'd like to watch the files without using MythTV / I'd like to convert the files to some other format</A> +<LI><A NAME="toc23.2">23.2</A> <A HREF="mythtv-HOWTO-23.html#ss23.2">Using a different window manager</A> +<LI><A NAME="toc23.3">23.3</A> <A HREF="mythtv-HOWTO-23.html#ss23.3">What capture resolution should I use? How does video work? </A> +<LI><A NAME="toc23.4">23.4</A> <A HREF="mythtv-HOWTO-23.html#ss23.4">MythTV GUI and X Display Sizes</A> +<LI><A NAME="toc23.5">23.5</A> <A HREF="mythtv-HOWTO-23.html#ss23.5">Saving or restoring the database </A> +<LI><A NAME="toc23.6">23.6</A> <A HREF="mythtv-HOWTO-23.html#ss23.6">Deleting the MySQL database</A> +<LI><A NAME="toc23.7">23.7</A> <A HREF="mythtv-HOWTO-23.html#ss23.7">Moving your data to new hardware</A> +<LI><A NAME="toc23.8">23.8</A> <A HREF="mythtv-HOWTO-23.html#ss23.8">btaudio </A> +<LI><A NAME="toc23.9">23.9</A> <A HREF="mythtv-HOWTO-23.html#ss23.9">Removing unwanted channels</A> +<LI><A NAME="toc23.10">23.10</A> <A HREF="mythtv-HOWTO-23.html#ss23.10">NFS</A> +<LI><A NAME="toc23.11">23.11</A> <A HREF="mythtv-HOWTO-23.html#ss23.11">Automatically starting mythfrontend at system boot time</A> +<LI><A NAME="toc23.12">23.12</A> <A HREF="mythtv-HOWTO-23.html#ss23.12">Automatically starting mythbackend at system boot time</A> +<LI><A NAME="toc23.13">23.13</A> <A HREF="mythtv-HOWTO-23.html#ss23.13">Advanced Backend Configurations </A> +<LI><A NAME="toc23.14">23.14</A> <A HREF="mythtv-HOWTO-23.html#ss23.14">Using the transcoder</A> +<LI><A NAME="toc23.15">23.15</A> <A HREF="mythtv-HOWTO-23.html#ss23.15">Changing your hostname</A> +<LI><A NAME="toc23.16">23.16</A> <A HREF="mythtv-HOWTO-23.html#ss23.16">Can I run MythTV on my TiVo?</A> +<LI><A NAME="toc23.17">23.17</A> <A HREF="mythtv-HOWTO-23.html#ss23.17">Can I run MythTV on my ReplayTV?</A> +<LI><A NAME="toc23.18">23.18</A> <A HREF="mythtv-HOWTO-23.html#ss23.18">Can a wireless connection be used between the frontend and the backend?</A> +<LI><A NAME="toc23.19">23.19</A> <A HREF="mythtv-HOWTO-23.html#ss23.19">How can I burn shows that I have recorded to a DVD?</A> +<LI><A NAME="toc23.20">23.20</A> <A HREF="mythtv-HOWTO-23.html#ss23.20">Using the DBoxII within MythTV</A> +<LI><A NAME="toc23.21">23.21</A> <A HREF="mythtv-HOWTO-23.html#ss23.21">What do the icons on the Watch Recordings screen mean?</A> +<LI><A NAME="toc23.22">23.22</A> <A HREF="mythtv-HOWTO-23.html#ss23.22">What do the letters mean when I change channels?</A> +<LI><A NAME="toc23.23">23.23</A> <A HREF="mythtv-HOWTO-23.html#ss23.23">What is the difference between the various Hauppauge PVR models?</A> +<LI><A NAME="toc23.24">23.24</A> <A HREF="mythtv-HOWTO-23.html#ss23.24">Changing channels on an external Set Top Box</A> +<LI><A NAME="toc23.25">23.25</A> <A HREF="mythtv-HOWTO-23.html#ss23.25">Configuring one machine to flag all commercials</A> +</UL> +<P> +<H2><A NAME="toc24">24.</A> <A HREF="mythtv-HOWTO-24.html">Example Configurations.</A></H2> + +<UL> +<LI><A NAME="toc24.1">24.1</A> <A HREF="mythtv-HOWTO-24.html#ss24.1">Logical Volume Manager (LVM) </A> +<LI><A NAME="toc24.2">24.2</A> <A HREF="mythtv-HOWTO-24.html#ss24.2">Advanced Partition Formatting </A> +<LI><A NAME="toc24.3">24.3</A> <A HREF="mythtv-HOWTO-24.html#ss24.3">Migrating from DataDirect Labs to Schedules Direct</A> +<LI><A NAME="toc24.4">24.4</A> <A HREF="mythtv-HOWTO-24.html#ss24.4">Caching support for Schedules Direct</A> +</UL> +<HR> +<A HREF="mythtv-HOWTO-1.html">Next</A> +Previous +Contents +</BODY> +</HTML> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO.pdf b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO.pdf Binary files differnew file mode 100644 index 0000000..47e70c1 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO.pdf diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO.sgml b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO.sgml new file mode 100644 index 0000000..08fc851 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO.sgml @@ -0,0 +1,7977 @@ +<!doctype linuxdoc system> +<article> +<title>Installing and using MythTV +<author>Robert Kulagowski, <url url="mailto:rkulagow@rocketmail.com" +name="mailto:rkulagow@rocketmail.com"> +<date>2008-06-04, v0.21.02 +<abstract> +Initially, installation of MythTV seems like a huge task. There are lots +of dependencies, and various distributions seem to do the same thing +different ways. This document will attempt to give general installation +instructions, as well as including distribution-specific instructions where +necessary. +</abstract> +<toc> +<sect>First things first. +<p><figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption> +<bf>NOTE</bf>: Please note that I, Robert Kulagowski, am <em>NOT</em> the +author/programmer of the MythTV application! I can not give you +personalized installation support. If you are having issues installing +MythTV you should examine the archives, or post your question to the +MythTV-users mailing list. If you send me "Does MythTV work with 'X'"? +messages - I will simply instruct you to ask your question on the +mythtv-users mailing list. +</caption> +</figure> +<sect1>What is MythTV? +<p>MythTV is a GPL licensed suite of programs that allow you to build the +mythical home media convergence box on your own using Open Source software +and operating systems. MythTV is known to work on Linux and Mac OS X +(PowerPC and Intel). It does not run on Windows. + +MythTV has a number of capabilities. The television portion allows you to +do the following: +<itemize> +<item>You may pause, fast-forward and rewind live Television. +<item>You may install multiple video capture cards to record more than one +program at a time. +<item>You can have multiple servers (called "backends"), each with multiple +capture cards in them. All scheduling is performed by the Master backend, +which arbitrates which recording will be performed by each device. All +recording requests are managed by the Master backend, so you can schedule a +recording from any client. +<item>You can have multiple clients (called "frontends" in MythTV parlance), +each with a common view of all available programs. Any client can watch any +program that was recorded by any of the servers, assuming that they have the +hardware capabilities to view the content; a low-powered frontend will not +be able to watch HDTV, for example. Clients can be diskless and controlled +entirely by a remote control. +<item>You may use any combination of standard analog capture card, MPEG-2, +MJPEG, DVB, HDTV, USB and firewire capture devices. With appropriate +hardware, MythTV can control set top boxes, often found in digital cable and +satellite TV systems. +<item>Program Guide Data in North America is downloaded from +schedulesdirect.org, a non-profit organization which has licensed data from +Tribune Media Services. This service provides almost two weeks of +scheduling information. Program Guide Data in other countries is obtained +using XMLTV. MythTV uses this information to create a schedule that +maximizes the number of programs that can be recorded if you don't have +enough tuners. +<item>MythTV implements a UPNP server, so a UPNP client should automatically +see content from your MythTV system. +</itemize> +Other modules in MythTV include: +<itemize> +<item>MythArchive, a tool to create DVDs +<item>MythBrowser, a web browser +<item>MythControls, an application to configure your remote control +<item>MythFlix, a Netflix module +<item>MythGallery, a picture-viewing application +<item>MythGame +<item>MythMusic, a music playing / ripping application which supports MP3 +and FLAC +<item>MythNews, a RSS news grabber +<item>MythPhone, phone and videophone using SIP. +<item>MythVideo, DVD ripper and a media-viewer for content not created within MythTV +<item>MythWeather +<item>MythWeb, which allows you to control your MythTV system using a web +browser. With MythWeb, you can schedule and delete recordings, change +keybindings and more. With proper security, you may even schedule a program +over the Internet and have it immediately acted on by the Master backend. +</itemize> +<sect1>QuickStart +<p>Custom mini-distributions are available to make it easier to install +MythTV. A mini-distribution removes many of the "general purpose" +workstation / server software packages that may be installed by default if +you use one of the big-name OS packages. + +See <url url="http://mysettopbox.tv" name="http://mysettopbox.tv"> if you'd +like to install a custom version of Knoppix optimized for MythTV. + +See <url url="http://www.minimyth.org" name="http://www.minimyth.org"> if you'd like +to install MythTV onto a diskless system. + +See <url url="http://bit.blkbk.com" name="http://bit.blkbk.com"> if you'd +like to install MythTV on a Xbox. +<bf>NOTE</bf>: Site appears unmaintained. + +See <url url="http://wilsonet.com/mythtv/" +name="http://wilsonet.com/mythtv/"> for instructions tailored to RedHat's +Fedora Core distribution. + +See <url url="http://www.mythbuntu.org" name="http://www.mythbuntu.org"> if +you'd like to install a customized version of Ubuntu optimized for MythTV. + +There is a MythTV wiki at <url url="http://wiki.mythtv.org" +name="http://wiki.mythtv.org">. + +If you are installing this version for Schedules Direct support, please see +the <ref id="migratingtoSD" name="Migrating from DataDirect Labs to +Schedules Direct"> section for additional information. + +<sect1>Upgrading from previous versions +<p>The upgrade from previous versions should be transparent. Any changes to +the database structure should be applied automatically. + +It is <em>strongly</em> recommended that you back up your database before +installing a new version of MythTV. + +See <ref id="backupdb" name="Saving or Restoring the database"> for instructions. + +<sect1>How to obtain this document / PDF versions of this document <label id="how_to_obtain"> +<p>This HOWTO document is maintained at the primary MythTV website: <url +url="http://www.mythtv.org" name="http://www.mythtv.org"> by Robert +Kulagowski <url url="mailto:rkulagow@rocketmail.com">. + +This document is available as a single-page HTML document at <url +url="http://www.mythtv.org/docs/mythtv-HOWTO-singlehtml.html" +name="http://www.mythtv.org/docs/mythtv-HOWTO-singlehtml.html"> or as a PDF +at <url url="http://www.mythtv.org/docs/mythtv-HOWTO.pdf" +name="http://www.mythtv.org/docs/mythtv-HOWTO.pdf">. + +This HOWTO is for MythTV v0.21 + +Release notes for this version may be found in the MythTV Wiki at <url +url="http://www.mythtv.org/wiki/index.php/Release_Notes_-_0.21" +name="http://www.mythtv.org/wiki/index.php/Release_Notes_-_0.21"> + +<sect1>Books about MythTV +<p>If you would like to purchase a book specifically about MythTV: + +<itemize> +<item>Hacking MythTV, ISBN 978-0470037874 by Wilson, Tittel, Wright and Korelc +<item>Practical MythTV: Building a PVR and Media Center PC, ISBN 978-1590597798 by Smith and Still +</itemize> + +<sect1>Document conventions +<p>The following conventions are used throughout this document.<newline> +<bf>boldface</bf> - used for program names.<newline> +<tt>typewriter</tt> - used for program paths.<newline> +<em>emphasis</em> - Pay attention here.<newline> + +<figure loc="here"> +<eps file="warning.eps" height="1cm"> +<img src="warning.png"> +<caption> +Pay more attention. +</caption> +</figure> + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption> +Ignore at your own peril. +</caption> +</figure> + +<figure loc="here"> +<eps file="add.eps" height="1cm"> +<img src="add.png"> +<caption> +Feature that has been added to SVN (subversion, a revision control system) +but is not available in the current release. +</caption> +</figure> + +<sect1>Mailing lists / getting help +<p>It's recommended that you join the user list at <url +url="http://www.mythtv.org/mailman/listinfo/mythtv-users" +name="http://www.mythtv.org/mailman/listinfo/mythtv-users">. The developer +list is at <url url="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev" +name="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev">. Please keep +the developer list strictly for development-related issues. + +Searchable archives for the lists are available at <url +url="http://www.gossamer-threads.com/lists/mythtv/" +name="http://www.gossamer-threads.com/lists/mythtv/">. + +<sect1>IRC +<p>There are two IRC channels dedicated to MythTV which can be found on +irc.freenode.net +<itemize> +<item>mythtv +<item>mythtv-users +</itemize> + +The <tt>mythtv</tt> channel is where the developers discuss code. It is +<em>not</em> a user-support channel. Please don't ask non-development +related questions there. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption> +Really. Even if there's no one in the mythtv-users IRC group or everyone +seems to be ignoring you. +</caption> +</figure> + +<sect1>Bug database +<p>If you feel you need to contribute to a bug database, use the MythTV bug +ticketing system at <url url="http://svn.mythtv.org/trac" +name="http://svn.mythtv.org/trac">. + +Good entries will contain the following: +<enum> +<item>Qt version +<item>Linux distribution +<item>gcc version +<item>the last entry in config.log to detail how you compiled +<item>MythTV version numbers (<em>e.g.</em>from mythfrontend --version) +<item>Hardware +<item>How you are able to reproduce the bug +</enum> + +See the instructions on how to debug in <ref id="debugging" name="Section 22">. + +The bug database is not a chat room, so restrict your entries to what is +relevant. It's also not a repository of feature requests; a feature request +without an accompanying patch file to implement that feature will be quickly +closed. There is a feature wishlist on the wiki at <url +url="http://www.mythtv.org/wiki/index.php/Feature_Wishlist" +name="http://www.mythtv.org/wiki/index.php/Feature_Wishlist">. There is no +guarantee that anything on the wishlist will ever get code written to +implement it. + +If a developer closes out your bug, it's likely you didn't provide enough +information. Don't re-open a bug without providing additional information. + +<sect1>Contributing to this document +<p>Contributions to the HOWTO are welcome, especially if you find a +grammatical or spelling error, or if the wording of something is just plain +confusing. + +If you'd like to make a new contribution, create a ticket at <url +url="http://svn.mythtv.org/trac" name="http://svn.mythtv.org/trac"> and +click "New Ticket". The type should be set to "patch" and the owner set to +"rkulagow" to ensure that I see your contribution. + +Please send it as either SGML or as plain text. <em>NO HTML</em>. The +source used to create the HOWTO is in SGML / Linuxdoc. Do not be afraid of +SGML! A quick look at the source of this HOWTO will show that it is not +difficult, because there aren't that many tags to worry about, so at least +<em>try</em> to submit as SGML. See the Linuxdoc HOWTO at <url +url="http://www.tldp.org/HOWTO/Howtos-with-LinuxDoc.html" +name="http://www.tldp.org/HOWTO/Howtos-with-LinuxDoc.html"> for information +on the linuxdoc format itself, or look at the <tt>mythtv-HOWTO.sgml</tt> +file as an example. + +To create the actual patch, run <bf>diff -u origfilename newfile > +doc.patch</bf> and attach your contribution to the trac ticket. + +<sect>Introduction. +<p>This HOWTO document will focus on manually building MythTV in a North +American environment. If you have installation instructions for a different +region or Linux distribution, please send them to the author so that it can +be included in other versions of this document. + +<sect>Checking prerequisites. +<p>You must ensure that any firewalls (either hardware, or a software +firewall installed by your distribution) will not block access to the ports +that will be used by the MythTV clients and servers on the "inside" LAN. +The ports for MySQL (TCP port 3306) and mythbackend (TCP ports 6543 and +6544) must be open. It is <em>strongly</em> recommended that you do +<em>not</em> expose the MythTV and MySQL ports to the Internet or your +"Outside" LAN. + +<sect1>Hardware +<p>Hardware selection is a complex topic, one this HOWTO will only discuss +briefly and in general terms. The following subsections offer some general +guidance but stop short of offering specific recommendations. + +For a good MythTV experience, you must understand that MythTV exercises your +hardware more than a typical desktop. Encoder cards generate DMA across the +PCI bus. The CPU is busy encoding / decoding video. Hard drives are +constantly reading and writing data. Building a MythTV system on older / +"spare" hardware may be an exercise in frustration and can waste many hours +of valuable time. + +For more detail about actual configurations that others have used, Mark +Cooper has setup a hardware database at <url +url="http://pvrhw.goldfish.org/" name="http://pvrhw.goldfish.org/">. The +website will let you browse what other users have reported as their hardware +configuration, and how happy they are with the results. + +If you have specific questions about the suitability of specific hardware +choices, you can consult the archives of the mythtv-users mailing list at +<url url="http://www.gossamer-threads.com/lists/mythtv/" +name="http://www.gossamer-threads.com/lists/mythtv/"> or +post a question to the list. +<sect2>CPU Type and Speed +<p>Selection of CPU type and speed is one of the trickiest elements of +hardware selection, mainly because there are so many tradeoffs which can be +made. For example, if you have plenty of CPU, you can use higher bitrates +or capture sizes, etc. + +MythTV has two modes of operation. First, it can function as a software +video encoder, which means that it uses a fairly generic "dumb" video +capture card to get frames of video, encodes them using the CPU on your +motherboard and writes them to disk. High-end video capture cards and +devices like the TiVo and ReplayTV have dedicated encoder chips which use +specialized hardware to convert the video stream to the MPEG-2 format +without using the motherboard CPU. The main CPU has the responsibility of +running the Operating System and reading and writing the encoded frames to +the disk. These tasks have fairly low CPU requirements compared to encoding +video, which is why a device like a Series 1 TiVo can run with only 16MB of +RAM and a 54MHz CPU. + +There are many variables that go into the question: "How fast a CPU do I +need to run MythTV"? Obviously, the faster your CPU, the better your +experience will be with MythTV. If you are using the software MPEG-4 +encoder and performing the "Watch TV" function, where the CPU is both +encoding and decoding video simultaneously to allow Pause, Fast Forward and +Rewind functions for live TV requires more CPU then just encoding or +decoding. MythTV also supports multiple encoder cards in a single PC, +thereby increasing the CPU requirements if you plan on simultaneously +encoding multiple programs. As a general guideline, plan on 1GHz per +encoder if you are doing software-based encoding, less if you are using a +hardware-based encoder. + +Here are a few data points: +<itemize> +<item>A PIII/733MHz system can encode one video stream using the MPEG-4 +codec using 480x480 capture resolution. This does not allow for live TV +watching, but does allow for encoding video and then watching it later. +<item>A developer states that his AMD1800+ system can <bf>almost</bf> +encode two MPEG-4 video streams and watch one program simultaneously. +<item>A PIII/800MHz system with 512MB RAM can encode one video +stream using the RTjpeg codec with 480x480 capture resolution and play it back +simultaneously, thereby allowing live TV watching. +<item>A dual Celeron/450MHz is able to view a 480x480 MPEG-4/3300kbps file +created on a different system with 30% CPU usage. +<item>A P4 2.4GHz machine can encode two 3300Kbps 480x480 MPEG-4 files and +simultaneously serve content to a remote frontend. +</itemize> + +The second mode of operation is where MythTV is paired with a hardware-based +video encoder, such as a Matrox G200 or a Hauppauge +WinTV-PVR-150/250/350/500. In this mode, because the video encoding is +being done by a dedicated video processor, the host CPU requirements are +quite low. See the <ref id="video_capture_device" name="Video Capture +Device"> section for details. + +The price differential between a frame grabber and a card that implements +hardware MPEG-2 encoding, such as the Hauppauge PVR-x50 series, is now less +than $30 US. Primary development in MythTV has transitioned to supporting +MPEG-2 capture devices and HDTV, so if given the option, go with the +hardware MPEG-2 encoder. + +If you have a Via M10000 series or a Hauppauge PVR-350, MythTV can use the +hardware-based video decoder for playback, which further reduces CPU +requirements. + +<sect2>Memory +<p>A MythTV host that is both a backend and a frontend and using software +encoding with a single capture card should run adequately in 256MB of RAM. +Additional RAM above 256MB will not necessarily increase performance, but +may be useful if you are running multiple encoders. + +<sect2>Hard Disk(s) +<p>Encoded video takes up a lot of hard disk space. The exact amount depends +on the encoding scheme, the size of the raw images and the frames per +second, but typical values for MythTV range from 700 megabytes/hour for +MPEG-4, 2 GB/hour for MPEG-2 and RTjpeg and 7 GB/hour for ATSC HDTV. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: You <em>must</em> use DMA for hard drive access to prevent +choppy or jittery video. Not all distributions enable DMA at boot time. +See the Troubleshooting Section for <ref id="Setting_DMA" +name="instructions"> on how to do this.</caption> +</figure> + +Writing video to disk is sensitive to timing issues; RTjpeg requires less +CPU with the tradeoff being larger files and needing to write to the disk +faster. MPEG-4 requires more CPU, but the files are smaller. At the +default resolution, MPEG-2 creates the largest files of all with almost no +CPU impact. + +See the Troubleshooting <ref id="Setting_DMA" name="section"> for more +information. + +<sect2>Filesystems +<p>MythTV creates large files, many in excess of 4GB. You <em>must</em> +use a 64 or 128 bit filesystem. These will allow you to create large files. +Filesystems known to have problems with large files are FAT (all versions), +and ReiserFS (versions 3 and 4). + +Because MythTV creates very large files, a filesystem that does well at +deleting large files is important. Numerous benchmarks show that XFS and +JFS do very well at this task. You are <em>strongly</em> encouraged to +consider one of these for your MythTV filesystem. JFS is the absolute best +at deletion, so you may want to try it if XFS gives you problems. MythTV +.21 incorporates a "slow delete" feature, which progressively shrinks +the file rather than attempting to delete it all at once, so if you're more +comfortable with a filesystem such as ext3 (whose delete performance for +large files isn't that good) you may use it rather than one of the +known-good high-performance file systems. There are other ramifications to +using XFS and JFS - neither offer the opportunity to shrink a filesystem; +they may only be expanded. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: You <em>must not</em> use ReiserFS v3 for +your recordings. You will get corrupted recordings if you do. +</caption> +</figure> + +Because of the size of the MythTV files, it may be useful to plan for future +expansion right from the beginning. If your case and power supply have the +capacity for additional hard drives, read through the <ref id="LVM" +name="LVM"> and <ref id="advancedpartitionformatting" name="Advanced +Partition Formatting"> sections for some pointers. + +<label id="video_capture_device"> +<sect2>Video Capture Device +<p>In order to capture video, MythTV will need one or more video capture +devices with Linux drivers. There are a number of classes of hardware +available for capturing video. +<sect3>Frame Grabbers. +<p>This class of card is the simplest and is usually the cheapest. There is no +on-board encoding of the analog video; hardware known as a Digital-Analog +Converter (DAC) takes the video and presents it to the computer in an +essentially raw digital form. + +For a list of video capture cards known to work with Linux, please see +<tt>/usr/src/linux/Documentation/video4linux/bttv</tt> for a partial +listing; even if your specific card is not listed, it may be that the vendor +is actually using a standard reference design and placing their own name on +it. See the video4linux mailing list (<url +url="https://listman.redhat.com/mailman/listinfo/video4linux-list" +name="https://listman.redhat.com/mailman/listinfo/video4linux-list">) for +more information and for specific hardware questions. + +The most common inexpensive cards available use the Bt848, Bt878 or CX2388x +series of video capture chips; examples are the "Hauppauge WinTV Go" card and +the "AverTV Desktop PVR" card, both of which use the bttv kernel module. + +<code> +NOTE: The ATI TV Wonder series and the ATI All-in-Wonder series of cards +are not the same. The All-in-Wonder cards will not work with MythTV. +</code> + +<figure loc="here"> +<eps file="stop.eps" height="4cm"> +<img src="stop.png"> +</figure> +<figure loc="here"> +<eps file="stop.eps" height="4cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: The ATI All-in-Wonder cards (which are not the same +as the ATI TV Wonder, TV Wonder VE or TV Wonder Pro) <em>will not</em> work +as a MythTV capture device because the GATOS <url +url="http://gatos.sourceforge.net" name="http://gatos.sourceforge.net"> +drivers that are available provide only a limited subset of the V4L API. +The TV Wonder series of cards are supported by the Bt8x8 Video4Linux driver. +</caption> +</figure> + +After you have installed a suitable capture device, you can check that +the kernel sees it with <tt>lspci</tt>. Look for an entry labeled "Multimedia +video controller". To get more detailed information about the card, use +<tt>lspci -v</tt> or <tt>lspci -vv</tt>. Ensure that your system is loading +the bttv modules by typing: +<tscreen><verb> +# lsmod |grep bttv +</verb></tscreen> + +You want to see the <tt>bttv</tt> module listed. +<sect3>Hardware MPEG-2 encoders. +<p>While inexpensive video-capture cards simply capture raw frames, leaving +encoding to software, some higher-end cards incorporate hardware-based +encoding. Using either a G200 MJPEG encoder card, or a MPEG-2 encoder card +supported by the IvyTV project <url url="http://ivtvdriver.org/" +name="http://ivtvdriver.org"> such as the Hauppauge +PVR-150/250/350/500, Avermedia M179, Hauppauge "Freestyle" or Yuan M600 +cards will allow you to use dedicated hardware encoders rather than your +CPU. (The PVR-350 can simultaneously be used as an output device.) Using the +on-board MPEG-2 encoder greatly reduces the CPU requirements for +encoding. + +The ivtv driver was incorporated into the Linux kernel starting at v2.6.22. + +There is a Beta driver for the HVR-1600 card at <url +url="http://www.ivtvdriver.org/index.php/Cx18" +name="http://www.ivtvdriver.org/index.php/Cx18"> + +<bf>NOTE</bf>: Motherboards with the Via chipset are notoriously bad with +DMA and have caused numerous issues with ivtv, including hard locks. See +the ivtv website <url url="http://ivtvdriver.org" name="http://ivtvdriver.org"> +for the latest information on what works and what doesn't. + +Here are some data points for encoding: +<itemize> +<item>A Celeron 450 uses 2% CPU for encoding a 480x480 16Mbps MPEG-2 stream. +</itemize> + +Here are some data points for decoding: + +<itemize> +<item>An Athlon 1800XP can decode a 720x480 8Mbps MPEG-2 file using 10% CPU +<item>An Athlon 1GHz can decode a 720x480 16Mbps MPEG-2 file using 30-50% +CPU, can decode a 480x480 16Mbps MPEG-2 using 30% CPU and approximately 30% +for Live TV at 416x480. +<item>A P3-550 can decode a 480x480 16Mbps MPEG-2 file with 55% CPU. +<item>A Celeron 450 (no SSE) can decode a 480x480 16Mbps MPEG-2 file with +80% CPU. +</itemize> + +<sect3>DVB capture cards. +<p>DVB is a video standard primarily found in Europe (where it comes in +DVB-C, DVB-T and DVB-S varieties for Cable, Terrestrial and Satellite) and +is also used as the programming interface for HDTV capture cards in Linux. +To see if your DVB card is supported, see the list of cards in the +"Supported Hardware" section of the DVB Wiki at <url +url="http://www.linuxtv.org/wiki/index.php/Main_Page" +name="http://www.linuxtv.org/wiki/index.php/Main_Page"> for more +information. + +In the United States, you may use a card such as the TwinHan to obtain +unencrypted Free-To-Air satellite channels. See <url +url="http://www.lyngsat.com/" name="http://www.lyngsat.com/"> for the types +of content which is available. + +<sect3>HDTV. +<p>There are a number of HDTV cards with Linux drivers which are known to +operate in the United States; a complete list of cards with DVB drivers can +be found at <url url="http://www.linuxtv.org/wiki/index.php/ATSC_Devices" +name="http://www.linuxtv.org/wiki/index.php/ATSC_Devices"> Some cards +support capture of unencrypted digital cable TV (utilizing QAM256), others +will only work with Over The Air (aka "OTA") signals captured with an +antenna (with 8VSB). + +Cards that have been reported to work include: +<itemize> +<item>pcHDTV HD-2000, Air2PC PCI rev 1-3 (8VSB only) +<item>SiliconDust HDHomeRun (8VSB, QAM256) +<item>pcHDTV HD-3000/5500 (8VSB, QAM256) +<item>Air2PC HD-5000 (8VSB, QAM256) +<item>DViCO Fusion HDTV Lite/Gold 5 (8VSB, QAM256) +</itemize> + +<bf>NOTE</bf>: There are no known consumer-level capture devices which will +allow you to capture the HDTV output (DVI, HDMI, VGA, YPbPr / Component) +from a set-top box commonly found with digital cable systems or satellite +systems. <em>None</em> of the capture devices listed above +perform any encoding; they merely allow your computer to save a copy of a +HDTV stream which has already been converted to MPEG-2 at the broadcast +facility. + +<bf>NOTE:</bf>: All of the cards listed above (except for the HD-2000 and +HDHomeRun) should be configured as DVB cards. The HD-2000 can be configured +as a pcHDTV card if you use the V4L drivers from <url +url="http://www.pchdtv.com" name="http://www.pchdtv.com"> and use Linux +kernel 2.6.9 or earlier. With kernel 2.6.10 and higher it must be +configured as a DVB card, but you lose access to the second antenna input in +ATSC mode. The HDHomeRun should be configured as two HDHomeRun cards, one +for each tuner. + +To playback HDTV content, plan on a powerful CPU. "How powerful?" depends +on a number of factors, such as the capture resolution, whether the video is +progressive or interlaced, and whether your display card has hardware-assist +support for Linux. + +The Simple Answer: Once you are in the 3.2 Ghz P4-class of CPU you should have +no issues with viewing HDTV. + +The Complicated Answer: + +For 720p content (1280x720), a 2.4GHz P4 should be sufficient. + +For 1920x1080i->1920x1080p with the better deinterlacing methods +done in real time a 2.4GHz CPU is taxed, but should work if you use "Bob and +Weave" deinterlacing, or if you have an NVIDIA card with MPEG-2 hardware +acceleration. If you enable the hardware acceleration, you may be able to +use a 1.8GHz processor. + +<sect3>Firewire. +<p>You may use the Firewire output of the Motorola DCT6200 or the SA3250. +If your provider uses 5C encryption on a particular channel, you won't be +able to get any content. + +<sect3>DBoxII or other devices running Neutrino +<p>You may use the Ethernet port of an DBoxII or a similar device to capture +MPEG2. Your set top box has to be running the Neutrino GUI. + +<sect3>USB Capture Devices. +<p>The Plextor ConvertX PVR devices are supported through Linux drivers +available from <url +url="http://www.plextor.com/english/support/LinuxSDK.htm" +name="http://www.plextor.com/english/support/LinuxSDK.htm">. MythTV uses the +Plextor to capture hardware encoded MPEG-4, so the host CPU requirements are low. + +Hauppauge WinTV-PVR-USB2 (driver available at <url +url="http://www.isely.net/pvrusb2/" name="http://www.isely.net/pvrusb2/">) +emulates a PVR-x50 card. + +<sect3>IP Recorder (RTSP, RTS, UDP) +<p>MPEG-2, MPEG-4 and H.264 internet TS stream recording is supported using +the IPTV recorder in MythTV. This recorder expects the channels to be supplied +as a m3u playlist. If your DSL/Fiber provider supplies television service, +but does not provide a m3u playlist for the channels, you can construct one +for your own use. You do not need to download it from the same server as the +streams themselves, and can also read it from a file if this is more convenient. + +<bf>NOTE</bf>: Some DSL providers only allow you to use one recorder at a +time, so you may need to limit yourself to one recorder in MythTV and turn +off any set top box the cable provider sold or rented to you with your +service. This limitation is independent of the bandwidth you have purchased. + +<sect2>Hardware known NOT to work and other issues +<p> +<itemize> +<item>Hauppauge WinTV-D or -HD (no driver) +<item>Hauppauge WinTV-USB series +<item>Hauppauge WinTV-PVR-usb (model 602), or WinTV-PVR-PCI (model 880) cards (no driver - this is not the PVR-250/350 +series of cards supported by the IvyTV driver) +<item>ATI All-in-Wonder series +</itemize> + +<sect2>Sound card +<p>The system needs a sound card or an on-board equivalent on the motherboard +to play back and in most cases, to record sound. Any sound card that can be +operated by the ALSA (Advanced Linux Sound Architecture) kernel modules will +work with MythTV. However, some cards and drivers will provide better +quality or compatibility than others. In particular, many audio +devices included on motherboards can be problematic. + +The usual practice for capturing the audio associated with the video is to +run a cable from an audio output on the video capture card to the Line input +on a sound card. However, some video capture cards provide on-board audio +capabilities that work with the kernel <tt>btaudio</tt> module instead, +thereby eliminating the need for a cable. This is useful if you will be +using multiple capture cards in a single chassis, since each capture card +will not need its own sound card. Note that a separate sound card is still +required for playback when using <tt>btaudio</tt>, and that often the audio +recorded in this way will be mono only. See the <ref id="btaudio" +name="btaudio"> section for more information. + +<figure loc="here"> +<eps file="warning" height="1cm"> +<img src="warning.png"> +<caption><bf>NOTE</bf>: Analog video capture cards are the only ones which +require a soundcard for capturing audio. DVB, HDTV, and other hardware +encoder cards all provide a combined audio / video stream. +</caption> +</figure> + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: Plugging a Line-level device into the Mic input is +not recommended. Line-level devices have higher voltages and can damage the +sound card. In addition, even if it doesn't break your card, you will be +getting Mono sound. See the Linux MP3 HOWTO at <url +url="http://www.tldp.org/HOWTO/MP3-HOWTO.html" +name="http://www.tldp.org/HOWTO/MP3-HOWTO.html"> for additional information. +</caption> +</figure> + +<sect2>Video Display Card +<p>MythTV will work with just about any video card. However, it is highly +recommended that you use a card which supports XVideo (XV) extensions. If +your card does not support XV, color conversion and scaling will be +performed by your CPU rather than the video card. This is very CPU +and memory intensive and will often result in dropped frames and a +corresponding degradation of quality. Check the X documentation +for details if you are uncertain about your preferred card. You may +also run <tt>xvinfo</tt>; look for your video card to be listed as one +of the adapters. + +<!-- Updated information from "Ray Olszewski" <ray@comarre.com> --> + +If you want to use MythTV with a standard television, you will need a +physical connection from your video card to your TV set, which can either be +a TV-out port on the card itself or an external adapter that converts the +VGA signal to an appropriate video signal. "Appropriate" depends on a number +of factors, such as video standard (NTSC vs. PAL), the type of input +connection (Composite vs. SVideo), etc. + +Note that with some video cards and X drivers, XVideo extensions are +only supported on the VGA output, and not on the TV output. + +<sect2>Cards with TV-out +<p>The next section deals with a number of cards that are known to have +TV-out ports. The list is unlikely to be complete, so if you know of +others, please post a message to the mythtv-users mailing list so the +information can be included in future versions of the HOWTO. The list is +organized by manufacturer. + +Reports here are based on what users of the cards have posted on the +mythtv-users mailing list, so if you need configuration details, please +search the archives at <url +url="http://www.gossamer-threads.com/lists/mythtv/" +name="http://www.gossamer-threads.com/lists/mythtv/"> using +the card name in your search string. + +<sect3>ATI +<p>ATI makes many cards with TV-out capability, but only offers Linux +drivers for Radeon 8500 and above cards. See the Drivers and Software +section of <url url="http://www.ati.com/" name="http://www.ati.com"> for the +driver and additional information. + +The enhanced ati.2 X driver created by the GATOS <url +url="http://gatos.sourceforge.net" name="http://gatos.sourceforge.net"> +project offers some support for TV-out on other ATI cards, but only in its +"experimental" version, available through CVS. There have been reports from +people who say they have made this driver work with one or another ATI card. +For example, Bruce Markey <url url="mailto:bjm@lvcm.com"> writes (on the +mythtv-users mailing list): "I got this to work. You can quote me on that. +I've used TV-out on several models of ATI cards both All-In-Wonder and +regular cards with TV-out." See the "Adventurous Setup" section of <url +url="http://gatos.sourceforge.net/watching_tv.php" +name="http://gatos.sourceforge.net/watching_tv.php"> for details. Also see +<url url="http://www.retinalburn.net/linux/tvout.html" +name="http://www.retinalburn.net/linux/tvout.html"> for more information. + +<sect3>NVIDIA +<p>Some NVIDIA cards with TV-out can be run using the standard nv driver in +X, combined with the userspace application <bf>nvtv</bf> to control the TV-out +port. See <url url="http://sourceforge.net/projects/nv-tv-out/" +name="http://sourceforge.net/projects/nv-tv-out/"> for details. Recent +versions of the NVIDIA driver have better support for overscan and other +features useful with TV-Out, so the <bf>nvtv</bf> application may not be +required. + +Some NVIDIA cards can be run with a proprietary NVIDIA X driver made +available by NVIDIA. See <url url="http://www.nvidia.com/object/unix.html" +name="http://www.nvidia.com/object/unix.html"> for more information. + +<bf>NOTE</bf>: It's strongly recommended that you use the proprietary +NVIDIA drivers; they have excellent support for XvMC and ship with a good +configuration utility. XvMC provides MPEG-2 hardware acceleration, which is +important if you want to display HDTV. + +<sect3>Hauppauge PVR-350 <label id="PVR-350"> +<p>MythTV supports the TV-out and MPEG-2 decoder functions in the IvyTV +driver. + +The PVR-350 is unique amongst the Hauppauge PVR-x50 cards in that it also +supports audio output, but you need to connect that audio output to +something. There are two courses of action you may take: +<enum> +<item>Take the audio output from the PVR-350 and plug it into an input on a +sound card on your machine. You may then use MythTV's internal audio +controls. +<item>Take the audio output from the PVR-350 and connect it directly to your +television / audio system. You must indicate that you are using external +audio control on the PVR-350 setup page. +</enum> + +<sect3>Other Options +<p>Some devices with on-board TV-out capability, such as Xboxes converted to +Linux and some laptops can be used as MythTV frontends to display on a +television screen. Please consult the mythtv-users mailing list for messages +that report the details of these special arrangements. + +<sect2>External Adapters +<p>External adapters convert standard VGA output to a form suitable for +display on a television. The output format varies by region, since +different countries have different TV standards. People on the mythtv-users +list have mentioned these adapters: + +<itemize> +<item>AITech Web Cable Plus, powered by external transformer or takes power +from PS/2 keyboard connector, support resolutions up to 1024x768, outputs +composite and SVideo, provides position adjustment. +<item>Averkey lite, powered by a USB port, has Composite, SVideo, YPbPr +outputs; pan, brightness, overscan/underscan controls; supports up to +1024x768 outputs; and supports PAL and NTSC. +<item>ADS TV Elite XGA +<item>AverKey iMicro (comments are generally favorable) +<item>AITech Web Cable (comments are generally unfavorable, different than +the "Plus" version above) +<item>TVIEW Gold (mentioned once, favorably) +</itemize> + +<sect1>Software +<p>There are a few ways of installing programs on Linux systems; you can +either use a pre-compiled package, or install from a tarball after +satisfying any prerequisites. + +<figure loc="here"> +<eps file="warning.eps" height="1cm"> +<img src="warning.png"> +<caption><bf>NOTE</bf>: you must have the MySQL database software installed on a +system to store the master database. This does not necessarily mean that +MySQL must run on one of the MythTV boxes. The minimum MySQL version is 5.0. +</caption></figure> + +<sect2>Pre-compiled packages <label id="precompiled"> +<p>A number of people have created pre-compiled packages for MythTV that may +make your installation easier. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption> +<bf>BIG FAT WARNING</bf>: This HOWTO assumes that you have <em>not</em> +installed MythTV from a package. All example command lines and file +locations are based on the MythTV tarball defaults. Some packagers have +modified the filenames, binaries and file locations to match what is +commonly found in that distribution. Any issues with MythTV installed via a +pre-compiled package <bf>MUST</bf> be raised with the packager. +</caption> +</figure> + +If you use any of the pre-compiled packages you may not need to perform any +additional configuration steps in this HOWTO. The next logical step is +<ref id="mysql" name="configuring MySQL">, which you may or may not have to +perform. See your package documentation. + +<sect3>Red Hat Linux / Fedora Core +<label id="atrpms"> +<p>The definitive documentation on installing MythTV on Red Hat Linux / +Fedora Core can be found in Jarod Wilson's (<url +url="mailto:jcw@wilsonet.com" name="mailto:jcw@wilsonet.com">) HOWTO at <url +url="http://wilsonet.com/mythtv/" name="http://wilsonet.com/mythtv/"> Just +like 3rd-party packages, any 3rd-party documentation problems should be +brought up with the 3rd-parties (maintainer, lists, bugzillas etc.). The +installation instructions which follow should be used as a guide only; refer +to Jarod's guide. + +Red Hat Linux and Fedora Core packages for MythTV and all of its add-on +modules and some themes have been packaged by <url +url="mailto:Axel.Thimm@ATrpms.net" name="mailto:Axel.Thimm@ATrpms.net"> and +are available at <url url="http://ATrpms.net/topic/multimedia/" +name="http://ATrpms.net/topic/multimedia/">. All of the prerequisites for +MythTV (such as XMLTV) are available as RPM packages. If you have problems +with the RPMs, please contact the ATrpms lists at <url +url="http://lists.ATrpms.net/" name="http://lists.ATrpms.net/"> or file a +bug against <url url="http://bugzilla.ATrpms.net/" +name="http://bugzilla.ATrpms.net/">. + +Given the large number of dependent RPMs you are advised to use tools like +apt or yum for automatic retrieval and installation of the required RPMs. +(<url url="http://ATrpms.net/install.html" +name="http://ATrpms.net/install.html">) In this case a +special meta-package called mythtv-suite will allow you to install all of +MythTV and its add-ons, plus all dependencies. + +If you don't have <bf>apt</bf> or <bf>yum</bf> on your machine, download and +install the atrpms-kickstart package from <url +url="http://ATrpms.net/name/atrpms-kickstart/" +name="http://ATrpms.net/name/atrpms-kickstart/">. +Install the package with: +<tscreen><verb> +# rpm -Uvh atrpms-kickstart* +</verb></tscreen> +Then run: +<tscreen><verb> +# apt-get update +# apt-get dist-upgrade +# apt-get update +</verb></tscreen> +And finally: +<tscreen><verb> +# apt-get install mythtv-suite +</verb></tscreen> +These steps however, do NOT perform the installation of any drivers required +for <bf>ALSA</bf>, capture cards, <bf>lirc kernel modules</bf>, etc., nor do +they set up your MythTV database. Check <url +url="http://ATrpms.net/topic/multimedia/" name="http://ATrpms.net/topic/multimedia/"> for the drivers you +need. + +<sect3>Mandriva +<p>Thac has created RPMs for MythTV for Mandriva which may +be obtained from <url url="http://rpm.nyvalls.se/" +name="http://rpm.nyvalls.se/"> If you have problems with the RPMs, please +send him email directly at <url url="thac@nyvalls.se" name="thac@nyvalls.se">. +<sect3>Debian +<p>Debian packages for MythTV and most of its add-on modules are maintained +by Christian Marillat <url url="mailto:marillat@free.fr" +name="mailto:marillat@free.fr"> and are available at <url +url="http://www.debian-multimedia.org/" +name="http://www.debian-multimedia.org/">. +Installation instructions can be found on those pages as well. All of the +prerequisites for MythTV are available as Debian packages, most of them from +the official Debian archive. + +If you have followed the instructions on the above page you should have added +<tscreen><verb> +deb-src http://www.debian-multimedia.org sid main +</verb></tscreen> + +to your <tt>/etc/apt/sources.list</tt> file. Running <bf>apt-get update</bf> and then +executing <bf>apt-get build-dep mythtv</bf> should install all the +pre-requisites required to compile MythTV. + +<figure loc="here"> +<eps file="warning.eps" height="1cm"> +<img src="warning.png"> +<caption><bf>NOTE</bf>: Due to the requirement for Qt 3.3+, there are no packages for +Debian woody/stable. +</caption></figure> + +<p>The Debian packages are configured such that MythTV programs should be +run as the <tt>mythtv</tt> user, which is automatically created during +installation. This user has access to write new recordings to disk in the +default directory, read and write the database, access the audio and video +devices, and everything else that MythTV needs to do. + +<p>See <tt>/usr/share/doc/<it>packagename</it>/README.Debian</tt> for more +information, including copies of the MythTV documentation. The +<tt>mythtv-doc</tt> package contains a copy of this HOWTO in +<tt>/usr/share/doc/mythtv-doc</tt>. +<sect2>Manual installation +<p>You may use the graphical tools that come with your distribution, or you +can use command-line utilities. Either system will get the job done, and it +all depends on your comfort level with Linux. + +In order to compile MythTV, we need to make sure that the software it needs +is installed. This list includes <bf>mysql</bf>, <bf>gcc</bf>, +<bf>freetype2-devel</bf>, <bf>xorg-xserver-devel</bf>, <bf>qt-devel</bf> and +<bf>lame</bf>. If you're going to use a remote control with MythTV, you're +going to need the <bf>cdialog</bf> package in order to compile +<bf>lircd</bf> if your distribution doesn't have a pre-packaged +<bf>lirc</bf>. If you are using <bf>XMLTV</bf> as a grabber, you will need +<bf>perl</bf>. + +<code> +NOTE: Qt v3.3 or higher is required. + +NOTE: MythTV DOES NOT WORK with Qt4. + +NOTE: If you are going to be using RPMs to install various +components, you should be aware that not all packages include the necessary +headers for compiling. If you're having trouble compiling, ensure +that you've installed the -devel version of a prerequisite. +</code> + +<sect2>Command-line installation <label id="CLIinstalltools_"> +<p> This section details the various methods for installing prerequisites +from the command line. + +<sect3>Mandriva +<p><bf>NOTE</bf>: The following instructions should be considered out of +date as of 2006-09-10. If updated instructions are not submitted by the +release of v0.21 of MythTV they will be removed. + +<bf>urpmi</bf> is the simplest tool for installation of packages from the +command line, but properly configuring it can be difficult. The +following website <url url="http://easyurpmi.zarb.org/" +name="http://easyurpmi.zarb.org/"> will allow you to choose +a mirror site and then present the command-line configuration text for that +mirror. You will most likely need to add a "Contrib" mirror to your setup. +If you add a site from the "Penguin Liberation Front", you will be able to +load the <tt>lame</tt> library without compiling from source. + +Open a shell, and execute the following. You may get +asked a number of questions regarding dependencies. It's best to answer +"YES". +<tscreen><verb> +$ su +# urpmi mysql gcc gcc-c++ freetype2-devel cdialog alsa-utils +# urpmi XFree86-devel perl +# urpmi libqt3-devel libMesaGLU1-devel +</verb></tscreen> + +<code> +NOTE for Mandriva 9.1+ users: execute the following command. + +# urpmi libqt3-mysql +</code> +However, you might get this when you execute the commands above: +<tscreen><verb> +everything already installed +</verb></tscreen> + +In that case, you're ready to move to the next <ref id="Setting_up_paths" +name="section">. Once you have completed installing the pre-requisites, +exit out of the shell and start a new one to ensure that any environment +variables setup by the installation have a chance to take effect. + +<sect3>Gentoo. +<p><bf>NOTE</bf>: MythTV does <em>not</em> run on Qt4. +If Qt has not been installed on your system: Edit +<tt>/etc/make.conf</tt> and locate the "USE" variable. If the line is +commented out, remove the comment. The line should have at least: +<tscreen><verb> +USE="mysql alsa" +</verb></tscreen> +Next you need to build Qt. If you don't plan on using the ebuilds as +described in the Gentoo section then you also need to install lame. +<tscreen><verb> +# emerge lame mysql qt +</verb></tscreen> + +If you have already installed Qt: you will need to rebuild because the +default installation doesn't include MySQL support, a requirement for MythTV. +To enable SQL support, add "mysql" to your USE variable in +<tt>/etc/make.conf</tt> and rebuild Qt by running +<tscreen><verb> +# emerge qt +</verb></tscreen> + +All the necessary files will be downloaded and built. Even on a fast machine +this may take a lot of time if you need to do a full Qt build. + +<sect3>Debian. +<p>Build-dependencies for MythTV can be satisfied by adding the following to +your <tt>/etc/apt/sources.list</tt> +<tscreen><verb> +# Christian Marillat's packages (mplayer, lame) +deb http://www.debian-multimedia.org sid main +deb-src http://www.debian-multimedia.org sid main +</verb></tscreen> +and executing: +<tscreen><verb> +# apt-get build-dep mythtv +# apt-get source mythtv --compile +</verb></tscreen> + +<sect>System Configuration Requirements for Compiling MythTV. <label +id="Setting_up_paths"> +<p>Before you compile MythTV from the current source tarball or from +<bf>subversion</bf>, you may need to modify your system configuration in a +few ways. + +In general, if you install MythTV from pre-packaged binaries for your Linux +distribution/version, you don't need to be too concerned about the issues in +this section of the HOWTO - the install script for the packages should take +care of them. However, this section is still recommended reading which may +help if the packager skipped a step in their packaging. + +<sect1>Software requirements for compiling MythTV +<sect2>General requirements +<p>MythTV is written in C++ and requires a fairly complete, but standard, +compilation environment, including a recent g++ compiler, <tt>make</tt>, and +appropriate header files for shared libraries. Any standard Linux +distribution should be able to install a suitable compilation environment +from its packaging system. Section 3.2 of this HOWTO provides some details +of how to install the required environment for many distributions. + +Subsequent sections of this chapter address the few oddities that you may +have to adjust by hand before you compile MythTV. + +The reference compilation system for MythTV is Ubuntu. + +<sect1>Shared-Library requirements for MythTV +<sect2>Modifying /etc/ld.so.conf <label id="modifying_ld.so.conf"> +<p>The runtime manager for shared libraries, <bf>/lib/ld.so</bf>, gets +information about the locations and contents of shared libraries from +<tt>/etc/ld.so.cache</tt>, a file created by <bf>ldconfig</bf> from +information in <tt>/etc/ld.so.conf</tt>. Because MythTV installs some +shared libraries in <tt>/usr/local/lib</tt>, that directory needs to be +added to the list of directories for <bf>ld.so</bf> to search when doing +runtime linking of programs, if it is not already there. +You do this, as root, by editing <tt>/etc/ld.so.conf</tt>, then +running <bf>ldconfig</bf>. There are many ways to do this; one that +works is to enter this series of commands: + +<tscreen><verb> +$ su - +# echo /usr/local/lib >> /etc/ld.so.conf +# /sbin/ldconfig +# exit +$ +</verb></tscreen> +<sect1>Environment variable requirements for MythTV +<sect2>General requirements +<sect3>QT libraries and binaries +<p>The compiler needs to be able to locate QT binaries and libraries in +order to compile MythTV. QTDIR needs to be set and the directory holding the +QT binaries needs to be added to your PATH. Your distribution may already +be making these changes as a part of the installation of the software +prerequisites detailed earlier. + +One way to do this is as follows: <label id="Checking_that_it_worked"> + +Open a shell and execute the following: +<tscreen><verb> +$ echo $PATH +/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/games:/usr/lib/qt3/bin:/home/mythtv/bin:/usr/lib/qt3/bin +$ echo $QTDIR +/usr/lib/qt3 +$ which qmake +/usr/lib/qt3/bin/qmake +</verb></tscreen> + +For Mandriva, you should see a value like <tt>/usr/lib/qt3</tt> for +<tt>QTDIR</tt> and <tt>/usr/lib/qt3/bin</tt> should be in $PATH. + +For Gentoo, you should see a value like <tt>/usr/qt/3</tt> for <tt>QTDIR</tt> +and <tt>/usr/qt/3/bin</tt> should be in $PATH. + +If you don't, do not proceed past this step until you have resolved this +error. You may need to manually specify the QTDIR and PATH at the shell +prompt before compiling. + +Also, check that there has been a link created in +<tt>/usr/lib/qt3/mkspecs</tt> (<tt>/usr/share/qt3/mkspecs</tt> for Debian) +called <tt>default</tt>. If not, you'll get errors during the compile. See +the Troubleshooting Section for more information. +<sect2>Distribution-Specific Notes +<sect3>Mandriva +<p>The following instructions work for Mandriva using +<bf>bash</bf> as the shell, and may be applicable for a distribution which +uses <tt>/etc/profile.d</tt>. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: Mandriva 10 installs a <tt>/etc/profile.d/qtdir3.sh</tt> +file, but it doesn't include the addition of the PATH variable. If you're +running Mandriva 10, don't create a <tt>mythtv.sh</tt> file as detailed +below; edit the <tt>qtdir3.sh</tt> file and add the PATH statement within +the if / fi block. +</caption> +</figure> +As root, create the following file in <tt>/etc/profile.d</tt> The example +filename is "mythtv.sh". Use what you feel is appropriate. + +Open a shell, and switch to superuser mode. + +<figure loc="here"> +<eps file="warning.eps" height="1cm"> +<img src="warning.png"> +<caption><bf>NOTE</bf>: ^D means press CTRL and d at the same time. +</caption> +</figure> +<tscreen><verb> +$ su +# cd /etc/profile.d +cat > mythtv.sh +export QTDIR=/usr/lib/qt3 +export PATH=$PATH:/usr/lib/qt3/bin +^D + +# chmod a+x mythtv.sh +# exit +$ exit +</verb></tscreen> +The last two commands are to exit out of the shell. This way, when you next +open a shell your new commands +will take effect. + +<sect2>Device Permissions <label id="devperms"> +<p>MythTV will need access to the video4linux devices on your system. By +default, your distribution may restrict access to these devices to the +logged-in user, so if you will be automatically starting +<bf>mythbackend</bf> from a script rather than an interactive terminal +session you will need to make some adjustments. + +<bf>NOTE</bf>: The following instructions are accurate for Mandriva. + +Check for a file called <tt>/etc/security/console.perms</tt>. Open the file +in your favorite text editor and look for a line that has: +<tscreen><verb> +<console> 0600 <v4l> 0600 root.video +</verb></tscreen> +and replace it with +<tscreen><verb> +<console> 0666 <v4l> 0666 root.video +</verb></tscreen> + +What we're doing is allowing read and write access to the files in the +video4linux directory. +<sect>Downloading and compiling. <label id="DownloadAndCompile"> +<p>Get MythTV from the <url url="http://www.mythtv.org" +name="http://www.mythtv.org"> web site. There are two installation methods +you may choose from. The first is to download the latest release in tarball +format and compile. The tarball release of MythTV should work on a wide +variety of systems and should be the preferred method for new users. If you +wish to use the <bf>subversion</bf> copy of MythTV you may obtain it from +<url url="http://svn.mythtv.org" name="http://svn.mythtv.org"> + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: If you are going to use <bf>subversion</bf> to +compile MythTV rather than using the distribution tarball, you <em>must</em> +join the <url url="http://www.mythtv.org/mailman/listinfo/mythtv-commits/" +name="http://www.mythtv.org/mailman/listinfo/mythtv-commits/"> and <url +url="http://www.mythtv.org/mailman/listinfo/mythtv-dev/" +name="http://www.mythtv.org/mailman/listinfo/mythtv-dev/"> mailing lists to +keep up to date with the current status of the code. Code obtained from +subversion has no guarantees regarding stability, etc. +</caption> +</figure> + +If you are in North America you will use the Schedules Direct grabber which is +built-in to MythTV. You <em>do not</em> need to install XMLTV (so you may +skip XMLTV-related instructions), but you need <bf>wget</bf> version 1.9.1 +or higher. + +Get XMLTV from <url url="http://xmltv.sourceforge.net" +name="http://xmltv.sourceforge.net">. Download the latest version (0.5.51). + +<code> +NOTE for Mandriva users: If you have added a "PLF" mirror, you may skip the +next step and type: + +# urpmi libmp3lame0 libmp3lame0-devel + +After downloading, be sure to install both: +# rpm -Uvh lame* + +</code> + +Get lame from <url url="http://lame.sourceforge.net/" +name="http://lame.sourceforge.net/">. Download the source code to v3.96.1 +by following the links from "Using" through "Download...". + +<sect1>Building LAME +<p>Open a shell and switch to the directory where you saved lame. +<tscreen><verb> +$ tar -xzf lame-3.96.1.tar.gz +$ cd lame-3.96.1 +$ ./configure +$ make +$ make test +$ su +# make install +</verb></tscreen> +Check that it worked: +<tscreen><verb> +# ls -l /usr/local/lib +-rw-r--r-- 1 root root 381706 Nov 4 14:22 libmp3lame.a +-rwxr-xr-x 1 root root 674 Nov 4 14:22 libmp3lame.la* +lrwxrwxrwx 1 root root 19 Nov 4 14:22 libmp3lame.so -> +libmp3lame.so.0.0.0* +lrwxrwxrwx 1 root root 19 Nov 4 14:22 libmp3lame.so.0 -> +libmp3lame.so.0.0.0* +-rwxr-xr-x 1 root root 360197 Nov 4 14:22 +libmp3lame.so.0.0.0* + +# exit +$ +</verb></tscreen> + +<sect1>XMLTV +<sect2>Red Hat Linux and Fedora Core: +<p>RPMs for <bf>XMLTV</bf> and all of its dependencies can be obtained from +<url url="http://ATrpms.net/name/xmltv/" +name="http://ATrpms.net/name/xmltv/">. The web page has a +list of all the dependent packages you must download and install. +<tscreen><verb> +# rpm -Uvh xmltv* perl* +</verb></tscreen> + +If you install from this location you may skip to <ref id="manually_building_mythtv" +name="Manually building MythTV">. +<sect2>Mandriva +<p>RPMs for <bf>XMLTV</bf> and all of its dependencies are located in +Mandriva's "contrib". If you have added a contrib mirror, try installing +<bf>XMLTV</bf>: +<tscreen><verb> +# urpmi xmltv xmltv-grabbers +</verb></tscreen> +If this does not work, it is possible that contrib for your Mandriva version +does not have <bf>XMLTV</bf>, so you may install the XMLTV prerequisites by typing: +<tscreen><verb> +# urpmi perl-xml-twig perl-xml-writer perl-datemanip perl-libwww-perl +</verb></tscreen> + +and skip straight to the XMLTV compilation step. + +<sect2>Manual installation +<p> +<label id="untarring_xmltv">Untar the xmltv file: +<tscreen><verb> +$ tar -xjf xmltv-0.5.51.tar.bz2 +</verb></tscreen> +Install the xmltv prerequisites. The following prerequisites are the +minimum required; when you actually start running the xmltv setup program it +may alert you to other modules that are required.: + +<tscreen><verb> +$ su +# perl -MCPAN -e shell +cpan> install XML::Twig +cpan> install Date::Manip +Date::Manip is up to date. +cpan> install LWP +cpan> install XML::Writer +cpan> exit +</verb></tscreen> + +Change to the XMLTV directory and compile it: +<tscreen><verb> +$ cd xmltv-0.5.51 +$ perl Makefile.PL +</verb></tscreen> +You can answer "N" to the tv_check, tv_pick_cgi questions. Say "yes" to +the grabber required for your location. + +You may get errors about modules not being installed. You will need to +resolve any missing dependencies at this point, or your grabber may not work +correctly. +<tscreen><verb> +$ make +$ make test +$ su +# make install +# exit +</verb></tscreen> + +<sect1>Configuring the Schedules Direct service <label id="ConfigureSD"> +<p>As of 2007-09-01, Tribune Media Services will no longer offer free guide +data. Schedules Direct is a non-profit organization which has licensed the +data to make it available to users of Freeware and Open Source applications. + +If you wish to use Schedules Direct, you'll need to establish a user +account. Go to <url url="http://www.schedulesdirect.org" +name="http://www.schedulesdirect.org"> and click on the "Membership" link. + +Once you've read and agreed to the Subscriber Agreement, Terms of Use and +Privacy Policy proceed to the lineup choices and configure your account for +your particular location and the channels that you have. This configuration +will be imported into MythTV when you first run the <bf>mythtv-setup</bf> +program. + + +<label id="manually_building_mythtv"> +<sect1>Manually building MythTV +<p>If you are going to use <bf>subversion</bf>, execute the following +instructions to obtain the latest version of MythTV: + +<tscreen><verb> +$ mkdir mythtv +$ svn co http://svn.mythtv.org/svn/trunk/ mythtv +$ cd mythtv +</verb></tscreen> + +To use a release version, you can execute: +<tscreen><verb> +$ mkdir mythtv-release-0.21 +$ svn co http://svn.mythtv.org/svn/branches/release-0-21-fixes/ mythtv-release-0.21 +$ cd mythtv-release-0.21 +</verb></tscreen> + +<bf>NOTE</bf>: Using a svn version of the code allows you to stay +up-to-date with changes. So, if there's an update to the 0.21 release and +you originally obtained it using svn, you could enter the +mythtv-release-0.21 directory and type "svn up", which will update your copy +with the fixed version from the website. You would then recompile and +install the updated 0.21 code. + +If you are using the tarball, then unpack it: +<tscreen><verb> +$ tar -xjf mythtv-0.21.tar.bz2 +$ cd mythtv-0.21 +$ ./configure +</verb></tscreen> + +If you wish to change options, run <bf>./configure --help</bf> to +see what is available and to override and automatically detected options. +See the <tt>config.log</tt> file after running <bf>configure</bf> to see +previous runs. + +To compile: +<tscreen><verb> +$ make -j 2 +</verb></tscreen> + +The MythTV compile can take advantage of multiple CPUs, SMP and +Hyperthreading. If you want to build MythTV on a multi-CPU machine (or with +<bf>distcc</bf>), specify "-j numjobs", where "numjobs" is greater than 2. +In the above example, we had two concurrent jobs executing, which is +recommended for a single CPU system. Do not set the number of jobs too +high, or your compile will actually take longer to complete than it would if +you did a "normal" build. + +If you are using <bf>distcc</bf>, and you had two other host machines (red, blue) +participating, you would do something like: +<tscreen><verb> +$ export DISTCC_HOSTS='localhost red blue' +$ make -j 6 CXX=distcc +</verb></tscreen> + +The actual speed-up, if any, is dependant on a number of factors, such as +number of CPUs / hosts, etc. The <bf>distcc</bf> documentation recommends +using a <tt>-j</tt> value of twice the number of CPUs available to keep all +of them busy. + +Some timing information. The following should only be used for +illustration; your actual results may vary. The test involves a complete +<tt>make distclean</tt> to the final binary. +<itemize> +<item>P4 3.2Ghz HT: "standard" make: 12m 49s +<item>P4 3.2Ghz HT: make -j 2: 11m 24s +</itemize> + +In the above example, we see that with a single CPU, a multi-stage +<bf>make</bf> does not significantly decrease compile time. + +Once the compile is done, switch to superuser: +<tscreen><verb> +$ su +# make install +# exit +</verb></tscreen> + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: subsequent configuration steps assume that you are within +the MythTV directory that you <tt>cd</tt>'d to above. +</caption> +</figure> + +<sect2>Enabling real-time scheduling of the display thread. +<p>MythTV supports real-time scheduling of the video output thread. There +are three ways to go about enabling this: You can use rlimits, you can use +the realtime security module, or on older systems you can SUID the +executable. Enabling real-time scheduling is optional, but can make the +video display smoother, especially if you are decoding HDTV. + +<sect3>rlimits +<p>The rlimits method is the preferred method and is included in Linux +2.6.12 and above. Unfortunately, you need PAM version 0.79 or above, which +may not be supported by your distribution yet. Assuming anyone running +<bf>mythfrontend</bf> is in the audio group and rlimits are supported, all +you need to do is place this in your <tt>/etc/security/limits.conf</tt> + +<tscreen><verb> +* - rtprio 0 +* - nice 0 +@audio - rtprio 50 +@audio - nice 0 +</verb></tscreen> + +<sect3>realtime module +<p>The second option is to use the Linux realtime kernel module. +This is will be phased out over time, but is currently supported +by many distributions that do not yet support rlimits. If you are +not using the distribution kernel you must configure your kernel +with: +<tscreen><verb> +Security options : [*] Enable different security models +Security options : [M] Default Linux Capabilties +</verb></tscreen> +You may also need to install the realtime module, using your distribution's +realtime package. Assuming the users who will be running +<bf>mythfrontend</bf> will be in the audio group you can get the GUID of a named +group like so: +<tscreen><verb> +$ grep audio /etc/group +</verb></tscreen> +If the number printed out from the grep was 18, you can now load +this module as root before starting <bf>mythfrontend</bf>: +<tscreen><verb> +# modprobe realtime gid=18 +</verb></tscreen> + +<sect3>run as root option (not safe) +<p>The final and least preferred option is to set the sticky bit +on the <bf>mythfrontend</bf> executable. This <bf>opens a security hole</bf>, +but is the only option on systems that do not support either +rlimits or the realtime module. This does not work on modern +distributions either, and is <bf><em>not recommended</em></bf> +on any system connected to the Internet. This may also make it +impossible to debug MythTV without running <bf>gdb</bf> as root. If you +would still like to do this, you just need to run this as root: +<tscreen><verb> +# chmod a+s /usr/local/bin/mythfrontend /usr/local/bin/mythtv +</verb></tscreen> + +<sect2>Frontend-only configuration <label id="frontend-only"> +<p>Since MythTV uses a client/server architecture, multiple frontend +computers can simultaneously access content on a Myth system. Live TV, +watching and scheduling recordings, etc. are all possible from multiple +frontends. + +To get a better picture of what is needed to run a frontend, note the +following: +<list> +<item>You do NOT need the MySQL server installed on your remote frontend +<item>You do NOT need XMLTV installed on your remote frontend +<item>You do NOT need to run the mythtv-setup program on +your frontend machine +</list> + +Other than the exclusion of the MySQL server and XMLTV, the MythTV +compilation procedure is the same as when you're setting up both a backend +and a frontend. However, you <em>will</em> need to install the database +access libraries. + +Once MythTV is compiled and installed: +<list> +<item> +Run the mythtv-setup program on your Master backend. Under the "General" +menu, change the IP address of the current machine (by default, "127.0.0.1") +to the real external IP address - 127.0.0.1 is the loopback address and no +external machine can access it. Change the Master Server IP setting to the +same IP address as well. +<item> +Run the mythfrontend program on your frontend machine, +and a "Database Configuration" screen should appear. +Set the "Host name" field to point to your Master backend's IP address. +</list> + +<sect1>Gentoo <label id="Gentoo_build"> +<p>Installation of MythTV on Gentoo consists of simply emerging the desired +ebuild because all of the packages are now part of the official Portage tree. +<tscreen><verb> +$ su - +# emerge --sync # make sure portage is up to date. +# vi /etc/make.conf +</verb></tscreen> +Add mysql to your USE variable. i.e. <tt>USE="mysql ...."</tt> +<tscreen><verb> +# emerge mythtv +</verb></tscreen> +<sect>MySQL.<label id="mysql"> +<p>When you install MySQL 5.x you will also want to comment +out "log-bin" in your <tt>my.cnf</tt> configuration file. This option will +quickly fill your "/var" disk partition with many gigabytes of data, +unless you are doing database replication and deleting these files regularly. +<sect1>Distribution-specific information +<sect2>Mandriva +<p>If this is the system maintaining the database, make sure that MySQL is +running and started at boot. Click on Mandriva Control +Center->System->Services, find MySQL and click the "On Boot" button and the +"Start" button if the MySQL status shows that it isn't running yet. + +<figure loc="here"> +<eps file="warning.eps" height="1cm"> +<img src="warning.png"> +<caption><bf>NOTE</bf>: There have been reports that MySQL isn't starting at boot. +If this is happening to you, try running the following commands. +</caption> +</figure> +<tscreen><verb> +$ su +# chkconfig --level 35 mysql on +# /etc/rc.d/init.d/mysql start +# exit +</verb></tscreen> + +<sect2>Red Hat Linux and Fedora Core +<p>If this is the system maintaining the database, make sure that MySQL is +running and started at boot. Click on Redhat menu>Server Settings>Services +and enter the root password when asked. Check "mysqld" and then click Start. +Click Save, then close the window. + +This can be done from the command line by typing: +<tscreen><verb> +# /sbin/chkconfig mysqld on +# /sbin/service mysqld start +</verb></tscreen> + +<sect2>Gentoo +<p>After installing MySQL you need to initialize the database by running +<bf>mysql_install_db</bf> as root. +<sect1>Setting up the initial database +<p>This step is only required on the system maintaining the database, which +may or may not be one of your MythTV boxes. If the database is on a +non-MythTV machine you'll need to copy the <tt>database/mc.sql</tt> file to it. + +To setup the initial MySQL databases: +<tscreen><verb> +$ cd database +</verb></tscreen> +<sect2>Mandriva and Red Hat Linux/Fedora Core +<p><tscreen><verb> +$ mysql -u root < mc.sql +</verb></tscreen> +<sect2>Debian 3.0 +<p><tscreen><verb> +$ mysql < mc.sql +</verb></tscreen> +<sect2>Gentoo +<p><tscreen><verb> +$ su +# mysql < /usr/share/mythtv/database/mc.sql +</verb></tscreen> +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: It is good practice to set a root password for MySQL. +Instructions for doing so can be found on MySQL's web site at <url +url="http://www.mysql.com/doc/en/Security.html" +name="http://www.mysql.com/doc/en/Security.html">. +</caption> +</figure> +<sect2>Modifying access to the MySQL database for multiple systems <label +id="modify_perm_mysql"> +<p>If you're going to have multiple systems accessing a master database, +you must grant access to the database from remote systems. By default, the +<tt>mc.sql</tt> script is only granting access to the local host. + +To allow other hosts access to your master database, you can either set it +up for no security at all, or with more granularity. Note that the "%" is +the wildcard character in MySQL. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: The "no security" option is <em>very</em> dangerous unless +you're in a controlled environment. +</caption> +</figure> +This example has no security at all, and allows access from any host. +<tscreen><verb> +$ mysql -u root mythconverg +mysql> grant all on mythconverg.* to mythtv@"%" identified by "mythtv"; +mysql> flush privileges; +</verb></tscreen> + +For a more secure setup, you can restrict which machines or subnets have +access. If you have a complete DNS system operational, you could do the +following: +<tscreen><verb> +$ mysql -u root mythconverg +mysql> grant all on mythconverg.* to mythtv@"%.mydomain.com" identified by "mythtv"; +mysql> flush privileges; +</verb></tscreen> + +Finally, if you just want to restrict by IP subnet (in this example, the +192.168.1. network): +<tscreen><verb> +$ mysql -u root mythconverg +mysql> grant all on mythconverg.* to mythtv@"192.168.1.%" identified by "mythtv"; +mysql> flush privileges; +</verb></tscreen> + +You'll also need to check that the "networking" feature of MySQL is turned +on. Check that <tt>/etc/mysql/my.cnf</tt> <em>does not</em> contain +<tt>skip-networking</tt>. If it does, remove it. Also verify that +<tt>bind-address</tt> is set to your IP address instead of +<tt>127.0.0.1</tt>. If you change either of these items, restart +<bf>MySQL</bf>. + +<bf>NOTE</bf>: Your distribution may have a customized MySQL configuration +file; in Mandriva, check <tt>/etc/sysconfig/mysqld</tt> for additional +configuration. + +<sect>Configuring Sound. +<p>If your video doesn't appear to be in-sync with your audio and you're +using an analog video capture card and a soundcard to capture audio, it +could be because you are listening to the real-time audio from your video +card rather than after it's been processed and synchronized to the video by +MythTV. Because MythTV is a personal video recorder, "Live TV" isn't really +live - to let you pause live TV, MythTV is actually encoding the video, +saving to disk, and then playing it back. This procedure puts your MythTV +"live" TV about 2 seconds behind real-time, so it's important that you're +not listening to the live audio. However, if you're having an issue where +the audio and video aren't synchronized by small but varying amount, it's +most likely because the sound driver that you're using doesn't have the +DSP_CAP_REALTIME capability. This was the case with ALSA (0.5), but not +with newer versions. See the <ref id="Troubleshooting_Audio" +name="Troubleshooting Audio"> section for more information if you're having +issues with sound. Also, ensure that no other programs are grabbing the +audio output, like <bf>arts</bf> or <bf>esd</bf>. + +What you need to do is to mute the "line-in" of your sound card and also +set it as the recording source. + +There are two ways to do this. Graphically, and from the command line. + +<sect1>Graphically setting up the mixer +<sect2>Mandriva and Red Hat Linux/Fedora Core +<p>Open Kmix by clicking K->Multimedia->Sound->Kmix for Mandriva, or +<verb>RedHat Menu>Sound & Video>Volume Control</verb> on Red Hat/Fedora. + +Click on Settings->Configure Make sure that "Tick Marks" and "Show +labels" have "X"'s in them. This will make it easier to find the correct +audio source. Click OK. + +On the mixer page, look for Line-In on your sound card. You should see +two LED's - a green one at the top, and a red one at the bottom. The green +one at the top is for muting; you want to make sure that the green LED is a +dark green, meaning that it's "off". You also want to click on the red LED +so that it turns bright red, indicating that it's "ON"; this insures that +the Line-in is used as the source. Click OK, and make sure that you save +the settings so that this is your default. + +<sect3>Using ALSA. +<p>To use ALSA, you'll need to correctly setup your +<tt>asoundrc</tt> file. Configuring this file is beyond the scope of this +HOWTO. Once ALSA is working correctly, change the output sound device in +mythfrontend->setup->Audio from <tt>/dev/dsp</tt> to <tt>ALSA:default</tt>. +This field may be edited to suit your ALSA requirements. + +<sect1>Setting the mixer from the command line +<p>If you have installed the alsa-utils package, then the <bf>amixer</bf> +program can be used to setup the mixer. The "Master" volume setting is only +required on a frontend machine to ensure that the sound channels are unmuted +and configured for outputting sound. The "Line" and "Capture" controls are +required for your sound card to actually capture audio from the external +Line-in if it's connected to an analog frame grabber. Not all sound cards +have a "Capture" control, but if yours does and you don't set it then MythTV +will not capture audio. + +<code> +Note the spelling in the following commands. +</code> +<tscreen><verb> +$ amixer set Master,0 100%,100% unmute +$ amixer set PCM,0 100%,100% unmute +$ amixer set Line,0 75%,75% mute captur +$ amixer set Capture,0 100%,100% captur +$ su +# alsactl store +# exit +$ +</verb></tscreen> + +If you have multiple sound cards, then use the <tt>-c</tt> parameter to +specify which card to adjust. Note that the first card will be "0", the +second will be "1", etc. + +That takes care of setting the volume correctly, and the ALSA startup script +will restore the volume after a reboot. If you find that your sound is +distorted, it's possible that the levels in the above examples are too high +for your particular hardware combination. Try reducing the percentages by +5-10% and checking again. Once you're satisfied, re-run the <tt>alsactl +store</tt> command. + +You may also use the <bf>alsamixer</bf> program to set the volume. If you +are using an ALSA version after 1.0.6, use <bf>alsamixer -V all</bf> First, +start <bf>alsamixer</bf> from the command line. You should start out on the +"Master" volume control slider. Use the up and down cursor to set the +master volume to around 75%. Next, use the left and right cursor keys to +move around on the screen until you find the "Line" slider. Press SPACE to +set it as the capture source, set the level to around 50-75% and press "M" +to mute it. You can now press ESC to exit out of the <bf>alsamixer</bf> +program. You can also have MythTV manage all volume and mute settings, but +this will only affect the "Master" or PCM volume, not the capture volume. See +the mythfrontend setup page for options. + +Finally, if you've performed all of the above steps, and you still don't seem to have any sound, it's possible that your video capture device is muting the audio output. +<tscreen><verb> +$ v4lctl -c /dev/video0 setattr mute off +</verb></tscreen> + +<sect>Setting up a remote control. +<p>MythTV does not have native remote control receiver and decoder software +built-in. Instead, remote control functions are implemented by cooperating +with <bf>lirc</bf>, the Linux Infrared Remote Control program. <bf>lirc</bf> +handles the IR hardware and passes keystrokes to MythTV, which then acts as +if the user had pressed the keys on the keyboard. The file +<tt>keys.txt</tt> describes the keys used to control MythTV. + +<figure loc="here"> +<eps file="warning.eps" height="1cm"> +<img src="warning.png"> +<caption><bf>NOTE</bf>: If you are running Mandriva, you may install +<bf>lirc</bf> by executing: <tt># urpmi lirc lirc-remotes</tt> and bypass +the manual compilation steps described below by jumping to the <ref +id="completing_lirc_install" name="Completing the lirc install"> section. +See the contrib/mandrake91.etc.sysconfig.lircd file for an example of how to +configure lircd. +</caption> +</figure> + +Some IR devices require a kernel recompile, and some don't. However, all at +least require having the kernel source available as a resource for the lirc +build process. + +<sect1>Gentoo +<p>To install lirc on Gentoo, all you need to do is: +<tscreen><verb> +# emerge lirc +</verb></tscreen> + +<sect1>Obtaining and compiling lirc +<p>You're going to need to download and compile <bf>lircd</bf>. Go to <url +url="http://www.lirc.org" name="http://www.lirc.org"> and download lirc; as +of 2006-01-21, the version available is 0.8.0. Grab the remotes.tar.bz2 file as +well. +<tscreen><verb> +$ tar -xjf lirc-0.8.0.tar.bz2 +$ cd lirc-0.8.0 +$ ./setup.sh +</verb></tscreen> +You're going to need to know what sort of receiver you have and where it's +connected. In the case of the Pinnacle Studio TV card, with the IR receiver +connected to COM1 (/dev/ttys0), once the configuration menu comes up, +perform the configuration by going to Driver Configuration->Other Serial +Port Devices->Pinnacle Systems Receiver->OK and on the next page select +COM1->OK. + +Each remote is different; some remote receivers connect directly to your +capture card and not to a serial port, so make sure that you've got the +correct one. + +You then click "Save Configuration and run configure" to continue. + +Make sure you read the last text generated by the configure step. It will +tell you if you require a kernel recompile, and what the name of your kernel +module will be (if necessary). For instance a home-built receiver may +require a kernel recompile, so you would be notified that you will have to +load the lirc_serial module. If you did not get any such messages skip the +kernel recompile steps below and go directly to making and installing the +lirc driver. + +Once the configuration step is complete: +<tscreen><verb> +$ make +$ su +# make install +# chmod 666 /dev/lircd +</verb></tscreen> + +At this point, if you're using a serial receiver, check that there's a +<tt>lirc</tt> device in <tt>/dev</tt>: +<tscreen><verb> +$ ls -l /dev/li* +lr-xr-xr-x 1 root root 5 Jan 27 09:00 /dev/lirc -> ttyS0 +srw-rw-rw- 1 root root 0 Jan 27 15:01 /dev/lircd= +prw-r--r-- 1 root root 0 Jan 27 09:00 /dev/lircm| +</verb></tscreen> + +As you can see, there's a link from /dev/lirc to ttyS0, a.k.a. "COM1", which is +appropriate for the Pinnacle Systems PCTV Pro. However, you may notice +something like this: +<tscreen><verb> +crw------- 1 root root 61, 0 Dec 31 1969 lirc +</verb></tscreen> +Some IR receivers (including some homebrew units) use a character device as +their data interface as opposed to a link to a serial port. If the <tt>make +install</tt> step has created a character device for you, don't replace it +with a link to a COM port. + +So, if the link or character device was not created (but should have been), +ensure that you ran the <tt>make install</tt> step as root. If it still +doesn't work, then there are three options. The first option is to re-read +the <bf>lirc</bf> documentation to determine whether your IR receiver is a +character device or should be a link to a serial port and to create the +link/character device manually. In this example, the IR device is connected +to ttyS0. If it were connected to "COM2", then use ttyS1, etc. +<tscreen><verb> +$ su +# cd /dev +# ln -sf ttyS0 lirc +# exit +$ +</verb></tscreen> + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: The above example assumes that your receiver uses the +standard serial driver. Some receivers do not, including receivers that +plug into a TV capture card. Check the lirc documentation, but it may be +necessary to replace the link created above with a character pipe: +</caption> +</figure> +<tscreen><verb> +# mknod /dev/lirc c 61 0 +</verb></tscreen> + +See the lirc documentation for additional information. The lirc +installation <em>should</em> create this for you, so manually creating it +indicates that your lirc installation may have other issues. + +The second option is to post your issue to the <em>lirc</em> list, not the +mythtv-users list. The lirc programmers will be the ones that can assist +you best. + +The third option is to dispense with lirc altogether by purchasing an IR +keyboard (various options exist, although Chicony appears to work for some +people) and a learning remote control. The IR keyboard receiver plugs into +the PS/2 keyboard port on your PC and you would train your learning remote +to emulate the various keystrokes from <tt>keys.txt</tt> of your IR +keyboard. Using this method removes lirc entirely from the picture - your +remote will be sending keypresses that your PC "sees" on the keyboard port. + +<sect1>Completing the lirc install <label id="completing_lirc_install"> +<p><figure loc="here"> +<eps file="warning.eps" height="1cm"> +<img src="warning.png"> +<caption><bf>NOTE to Mandriva 9.1 users</bf>: skip to the manual start paragraph +below. +</caption> +</figure> +<p>If the lirc configure program / compile did not mention anything about a +kernel module, then you are finished. If it did mention a kernel module, you +must edit the <tt>/etc/modules.conf</tt> file. Add this line as the first +thing in the file. It must come first, or it may not work. +<tscreen><verb> +alias char-major-61 XXX +</verb></tscreen> + +replace XXX with the name which you determined earlier, which in this +example was "lirc_serial" +<tscreen><verb> +$ su +# modprobe lirc_serial +# /sbin/ldconfig +</verb></tscreen> + +Next, we're going to manually start lircd the first time. Mandriva 9.1 +users, type: <tt># /etc/rc.d/init.d/lircd start</tt> instead of: +<tscreen><verb> +# /usr/local/sbin/lircd +</verb></tscreen> + +<bf>NOTE</bf>: Read this next section if you're not familiar with how lirc works! + +There are two separate files used by lirc, and both are required for your +remote control to do anything useful. First is the <tt>lircd.conf</tt> file. +<tt>lircd.conf</tt> tells the lirc daemon how to interpret the IR pulses +that it receives from a remote control and what name to assign to each +sequence of pulses. Without getting too involved, a particular series of +pulses may correlate to "Channel Up". The <tt>lircd.conf</tt> file will +then contain a line that looks something like this: + +<tscreen><verb> + ChannelUp 0x0000000000001020 +</verb></tscreen> + +The <tt>lircd.conf</tt> file can have multiple remote controls defined. + +The second file is <tt>lircrc</tt>, which takes the name of the button which +was pressed ("ChannelUp") in the above example, and correlates that to an +action to be performed by a program using the remote control. So in MythTV, +ChannelUp means one thing, while in <bf>mplayer</bf> it means something +different. <tt>lircrc</tt> gives you the flexibility of taking the name of +the button and having it perform different actions depending on which +program you're using at the time. + +<bf>NOTE</bf>: The definitions in <tt>lircd.conf</tt> come from the user +community, and there is no standard for the common button names. One +<tt>lircd.conf</tt> file may contain a definition for a button called +"ChannelUp", while another may contain a definition for "Chan+". Your +<tt>lircrc</tt> file must therefore be configured appropriately, or it won't +work. + +If this fails, complaining of a missing <tt>lircd.conf</tt> file, then you +must find or make one. First look for a pre-made configuration file at <url +url="http://lirc.sourceforge.net/remotes/" +name="http://lirc.sourceforge.net/remotes/">. Mandriva 9.1 users, look in +<tt>/usr/share/lirc-remotes</tt>. If you find one your remotes either on the +website or in <tt>/usr/share</tt>, download or copy the file, name it +<tt>lircd.conf</tt> and put it in your <tt>/etc</tt> directory. If you +couldn't find your remote, you must make your own <tt>lircd.conf</tt> file. + +To make your own <tt>lircd.conf</tt> file +<tscreen><verb> +$ irrecord myremote +</verb></tscreen> + +Follow the on-screen directions to train your remote and define keys. If +your remote ends up working well, you should consider submitting your +<tt>lircd.conf</tt> file back to the lirc developers. Once finished: +<tscreen><verb> +$ su +# cp myremote /etc/lircd.conf +</verb></tscreen> + +now try to start lircd again: +<tscreen><verb> +# /usr/local/sbin/lircd +</verb></tscreen> + +Now, we're going to add the commands necessary for lircd to run each time we +boot. Mandriva 9.1 users, you can execute: +<tscreen><verb> +$ su +# chkconfig --level 35 lircd on +# exit +</verb></tscreen> + +All other distributions: +<tscreen><verb> +# cd /etc/rc.d +# cat >> rc.local +echo "Starting lircd" +/usr/local/sbin/lircd +^D +# exit +$ +</verb></tscreen> + +This takes care of the lircd portion, which "listens" for the IR signals. If +everything went well, the install script for lircd put an appropriate +configuration file for your remote into <tt>/etc/lircd.conf</tt> This file +maps the buttons on the remote control to the IR pulses coming from the +receiver. + +The next step is to convert those signals into something that can be used +to control MythTV. MythTV now includes native support for lirc and can +interact directly with + +<tscreen><verb> +$ cd ~/mythtv-0.21/contrib/configfiles +$ cp lircrc.example ~/.lircrc +</verb></tscreen> +or +<tscreen><verb> +$ cp lircrc.example.pinnaclestudiopctv ~/.lircrc +</verb></tscreen> +if you've got a Pinnacle Studio PCTV remote. +<tscreen><verb> +$ irw +</verb></tscreen> +Start pressing the keys on your remote; <bf>irw</bf> will +print the name of the button as it is defined in your +<tt>/etc/lircd.conf</tt>. If you don't see anything at this point, you need +to troubleshoot further by going back to the lirc home page and investigating +from there. + +If it is working, then press <bf>CTRL-C</bf> to abort the program. Once you +know that your remote is working, you can either recompile MythTV with +native lirc support by enabling it in <bf>configure</bf> or you +need to run the <bf>irxevent</bf> program, which takes the key presses and +sends them to MythTV. If you use native lirc support, you don't need to run +<bf>irxevent</bf>. If you are going to use irxevent, then you need to run +it like this: +<tscreen><verb> +$ irxevent & +</verb></tscreen> +If <bf>irxevent</bf> isn't running, then MythTV will not respond to your remote +control unless you're using native lirc support. + +<sect1>Additional information for lirc +<p>Take a look at the lircrc.example files in the <tt>contrib/configfiles/</tt> +directory. In my case, (Pinnacle Studio card) the channel up and down functions +weren't working, due to the fact that the button names were different than +the default <tt>lircrc.example</tt> file that came with MythTV. + +The <tt>lircrc.example</tt> file has this: +<tscreen><verb> +begin + prog = irxevent + button = ChannelUp + config = Key Up CurrentWindow +end + +begin + prog = irxevent + button = ChannelDown + config = Key Down CurrentWindow +end +</verb></tscreen> +but the <tt>/etc/lircd.conf</tt> that comes in the lircd package +defines the buttons for the Pinnacle Studio PCTV as: +<tscreen><verb> + channel+ 0x0000000000000017 + channel- 0x000000000000001C +</verb></tscreen> +rather than "ChannelUp" and "ChannelDown". I added the +following to my /home/[yourusername]/.lircrc file: +<tscreen><verb> +begin + prog = irxevent + button = channel+ + repeat = 3 + config = Key Up CurrentWindow +end + +begin + prog = irxevent + button = channel- + repeat = 3 + config = Key Down CurrentWindow +end +</verb></tscreen> +which took care of basic functionality. Because the PCTV Studio remote +has additional buttons, look at the +<tt>contrib/configfiles/lircrc.example.pinnaclestudiopctv</tt> for an example of how +to define additional buttons, and how to debug potential button name +conflicts between the <tt>lircrc.example</tt> file and how <bf>your</bf> +remote defines the button names. + +By examining the button names defined in <tt>/etc/lircd.conf</tt> and using +the <bf>irw</bf> program to make sure that your remote is working, you can +create the appropriate mappings in <tt>.lircrc</tt> to get excellent remote +functionality with MythTV. + +Note the <bf>repeat =</bf> parameter. This informs the <tt>irxevent</tt> +program to pass through every third keypress. By default, <tt>lirc</tt> +will only send one keypress to the application, even if you're holding down +the key. The actual <bf>repeat =</bf> number will vary from system to +system, so experiment and see which value works best for you. + +<sect1>Configuring lirc for use with an IR blaster +<p> +<!-- By Carlos Talbot, <url url="mailto:carlos@talbot.net"> --> +Lirc has support for various IR transmitters. A popular model is the Actisys +IR-200L <url url="http://store.snapstreamstore.com/accessories.html" +name="http://store.snapstreamstore.com/accessories.html">. It was +originally designed for IRDA communication, but can be used to transmit A/V remote +control codes. By using the lirc SIR driver, this device can easily be +integrated with MythTV. I have tested this device with an AT&T DCT2000 +digital cable box but the instructions can be used to configure other IRDA +devices and A/V remotes. + +Follow the steps in the previous section. When you run setup.sh, select +option 1, driver configuration. From here select option 6, IrDA hardware. +Select your appropriate device and the corresponding serial port, then Save +configuration & run configure from the main menu. Once configure is done +type: +<tscreen><verb> +$ make +</verb></tscreen> + +Please note: unlike the Pinnacle receiver above you will be compiling lircd +in addition to a kernel module for the SIR transmitter. Depending on whether +you have your serial port driver configured as a kernel module you might see +the following message during make: +<tscreen><verb> +lirc_sir.c:56:2: warning: #warning +"******************************************" + +lirc_sir.c:57:2: warning: #warning "Your serial port driver is compiled into " + +lirc_sir.c:58:2: warning: #warning "the kernel. You will have to release the " + +lirc_sir.c:59:2: warning: #warning "port you want to use for LIRC with:" + +lirc_sir.c:60:2: warning: #warning "setserial /dev/ttySx uart none" + +lirc_sir.c:61:2: warning: #warning +"******************************************" +</verb</tscreen> + +If you do receive this statement make sure to run the <bf>setserial</bf> command +before you load the lirc_sir module. Follow this with the install: +<tscreen><verb> +$ su +# make install +</verb></tscreen> + +You will notice that lirc installs the kernel module in +<tt>/lib/modules/uname -a/misc</tt>. + +The configuration for starting <bf>lircd</bf> differs if you're going to be +sending and receiving IR versus just receiving. +<tscreen><verb> +# cd /etc/rc.d +# cat >> rc.local +echo "Starting lircd" +setserial /dev/ttySx uart none # (if required) +modprobe lirc_sir +/usr/local/sbin/lircd +^D +# exit +$ +</verb></tscreen> + +At this point you have to populate the <tt>/etc/lircd.conf</tt> file with the proper +codes for your A/V remote. You should be able to find your remote within the +lirc remote tar file located at <url +url="http://www.lirc.org/remotes.tar.bz2" +name="http://www.lirc.org/remotes.tar.bz2">. In my case I +extracted the file from remotes/motorola/DCT2000 (gi-motorola-dct2000) + +To test the lirc_sir module you can run <bf>irw</bf> to verify the codes are being +received. If everything is configured correctly +you should see something similar to the following: +<tscreen><verb> +$ irw +0000000000007ff0 00 1 gi-motorola-dct2000 +000000000000bff8 00 2 gi-motorola-dct2000 +000000000000f7f0 00 ENTER gi-motorola-dct2000 +</verb></tscreen> + +Once you've verified lirc is working you can press <bf>CTRL-C</bf> to exit +<bf>irw</bf> and configure the channel changing script. + +The path to the channel changing script will need to be entered on the +mythtv-setup screen for Input Connections. + +This csh script will be called each time MythTV needs to change the channel. +Below is a copy of the script followed by the corresponding perl script. +Make sure both are in your path. Also make sure you leave the #!/bin/csh +setting and not change it to Bourne or bash. This will create a frustrating +symptom to diagnose where MythTV cannot open /dev/device. Unlike Bourne or +bash, csh scripts automatically close parent file descriptors before they +start. +<tscreen><verb> +$ cd /usr/local/bin +# su +# cat > change_channel.csh +#!/bin/csh +echo "changing to $1" +/usr/local/bin/channel.pl $1 & +^D +# chmod a+x change_channel.csh +# exit +$ exit +</verb></tscreen> + +See <tt>contrib/channel.pl</tt> for the actual file. Copy it to +<tt>/usr/local/bin/</tt> + +The last statement within the perl script is the lirc rc command. This is +the command that transmits the code to your cable/DSS box. Make sure to have +the IRDA device within a few feet of the box. + +<sect>Configuring MythTV. <label id="Configuring_mythtv"> +<p>By this point, all of the compile-time prerequisites have been installed, +<bf>mysql</bf> is running and has had its initial database setup. It's now +time to configure MythTV. +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: If you're running Debian unstable and you have compiled +MythTV from source, you will need to install an additional package before +you will be able to run MythTV. Execute the following to install the MySQL +driver for QT. +</caption> +</figure> +<tscreen><verb> +$ su - +# apt-get install libqt3c102-mt-mysql +# exit +</verb></tscreen> +<sect1>Configuring the Master backend system +<p>Open a shell and decide where you will store your video files. This may +be one directory or multiple directories on the same or different +filesystems. There is no default directory used for new recordings, you +<bf>must</bf> create at least one storage directory and configure Myth to +use it by running <bf>mythtv-setup</bf>. If you do not do this, then MythTV +will be unable to record anything. The following example is specific for +<tt>/var/video</tt>, but the same instructions would apply for any directory +name you choose to use. See the <ref id="advancedpartitionformatting" +name="Advanced Partition Formatting"> section for hints on creating a +partition for MythTV. + +<tscreen><verb> +$ su +# mkdir /var/video +# chmod a+rwx /var/video +# exit +</verb></tscreen> + +<bf>NOTE</bf>: The last slash "/" is not required. + +<label id="storagegrouptip"> +<bf>TIP</bf>: Try not to have your video mount point on the same partition +as your root partition, which could lead to the filling up of your root +partition with video data if the mount fails. For example: + +If <tt>/var/video</tt> is created on your root partition and you then +perform a mount of another drive to this directory there won't be any +problems if everything is working the way it should. However, if the mount +fails for some reason, <tt>/var/video</tt> still exists, so MythTV will find +the directory and write files to it. If your <tt>/</tt> mount point is +space limited, <tt>/var/video</tt> will <bf>also</bf> be space limited, and +it won't take long to fill the partition. This will cause a number of +side-effects, most of them bad. Instead, create subdirectories as the +destination for the storage group. + +Your directory structure could then look something like this: +<tscreen><verb> +/mnt/video/drive1/video +/mnt/video/drive2/video +</verb></tscreen> + +Your <tt>/etc/fstab</tt> would look like this: +<tscreen><verb> +/dev/hdb1 /mnt/video/drive1 +/dev/hdc1 /mnt/video/drive2 +</verb></tscreen> + +Because the Storage Group path is <tt>/mnt/video/drive1/video</tt>, if the +mythbackend can only find <tt>/mnt/video/drive1</tt> it will <em>not</em> +write files to that share. + +After you create the desired directory or directories for storing your video +files, you will need to add them to the proper Storage Group using +<bf>mythtv-setup</bf>. This procedure is described below in the <ref +id="storagegroups" name="Storage Groups"> section. + +The first thing to configure is the Master backend system. If you are +running multiple backend systems, the Master backend will make all +decisions about which programs will be recorded on which tuners. If you +have only one backend, then it will be its own master. + +The Master backend will always choose the first available tuner in the same +order as you add cards through "mythtv-setup". In other words, the second +card you add will only be used when there are two overlapping recordings, +the third when there are three, and so on. +<!-- Remove the next part once .21 is released --> Therefore, you will want to have +the greatest amount of disk space on the Master backend because its tuner +will always be the first choice. You will then want to add your <ref +id="nonmaster_backend" name="other backends"> in the order of your +preference for recording. + +<figure loc="here"> +<eps file="warning.eps" height="1cm"> +<img src="warning.png"> +<caption><bf>NOTE</bf>: It is possible to <em>not</em> have the cards on the Master +backend be the first ones used. However, if you are new to MythTV it is +easier to configure the Master backend first before moving on to the Slaves, +at least until you become more familiar with the MythTV system. See <ref +id="advanced_backend_config" name="Advanced Backend Configurations"> for +information on configuring multiple backend systems in various ways. +</caption> +</figure> + +Because MythTV uses a database to store all configuration variables, +part of the bootstrap of MythTV is to indicate the location of the MySQL +database server. If the frontend, backend and MySQL database server are all +going to be running on the same box, you can continue to the next step. If +not, you'll need to change the Host Name in the "Database Configuration" +screen of the mythfrontend program. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: Users that have been running the frontend and the backend on +different machines have stated that they have been having issues with remote +access to the MySQL database. The following instructions may or may not +work. Add the following to <tt>/etc/my.cnf</tt> on the backend machine and +restart MySQL. +</caption> +</figure> +<tscreen><verb> +skip-innodb +set-variable=thread_stack=256k +</verb></tscreen> + +Run the setup program: +<tscreen><verb> +$ mythtv-setup +</verb></tscreen> + +The backend setup program will start and offer you a number of choices. It +is <em>strongly</em> recommended that you go through them in order. + +The first question will ask if you wish to clear out your existing +configurations for your capture cards. Initially, you should say "YES" so +that there are no surprises later. + +The next question will ask you if you wish to clear out your video source +information. You should answer "YES" to this as well. + +Once the graphical setup starts, you'll see that there are six choices + +<figure loc="here"> +<eps file="add.eps" height="1cm"> +<img src="add.png"> +<caption> +The Storage Directories feature is available only in the SVN version of MythTV. +</caption> +</figure> + +<enum> +<item>General +<item>Capture Cards +<item>Video Sources +<item>Input connections +<item>Channel Editor +<item>Storage Directories +</enum> + +Use the arrow keys to move around, and press the space bar to select which +option you wish to configure. + +<sect2>General +<p>The first screen of the General configuration deals with IP addresses of the +system that you're running mythtv-setup on and any master backend you may have. +If you've only got one machine, then the default values are fine and you can +move to the next page by pressing the space bar. If you need to move around +the screen, use the arrow keys to move focus between settings, not the +mouse. + +If you will be deploying multiple backends, or if your backend is on one +system and you're running the frontend on another machine then <em>do +not</em> use the "127.0.0.1" IP address. + +<bf>NOTE</bf>: 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 +the space bar. + +The next screen details the Host-specific Backend setup. This is where you +will set the specific directory paths for this particular backend. Make +sure that you've followed the steps at the beginning of this section and +created a directory that exists and that MythTV will have write privileges +to. When you're done, press Next to continue, taking you to the Global +Backend Setup. + +On the Global Backend Setup configure your backend with the appropriate +settings. Use the left and right arrow keys to iterate through the choices +available on each setting, and the up and down keys to move between +settings. Move to Finish when you're done and press the space bar, taking +you back to the main configuration screen. + +<sect2>Capture Cards +<p>You should have no capture cards defined, so the highlight will be on +(New Capture Card). Press space to begin. + +Choose the appropriate settings for your particular tuner. Use the arrow +keys to move around and to make your choices, and press RETURN when +complete. Pressing RETURN will take you back to the Capture Cards screen; +if you have additional capture cards in this machine, press the space bar +when the highlight is on the (New Capture Card) row to define another card. + +If you have made a mistake, you can delete a card by highlighting it and +pressing the 'D' key, or you can highlight it and press the RETURN or 'E' +key to edit it. + +Once you have no additional cards to setup, press ESC. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption> +<bf>NOTE</bf>: If you have a dual digital/analog card, such as the pcHDTV +cards and some DViCO cards, then you should not configure this as two +separate cards. Configure the digital portion as a DVB card, then click +on the "Analog Options" button within the DVB configuration panel for +the card and configure the analog portion of the card there. +</caption> +</figure> + +<sect2>Video Sources <label id="VideoSources"> +<p>When you start, the highlight should be on (New Video Source). Press the +space bar to begin. The first field asks for the name of the video source. +You may choose something easy to remember, like "Antenna" or "Cable". Once +you've chosen a name, press the down arrow to move to the next field. + +If you're in North America, change the grabber to +"SchedulesDirect.org(Internal)", then continue pressing the down arrow to +move to the next field. Fill in the username (lowercase only) and password +that you have established with Schedules Direct, then move to the "Retrieve +Listings" button and press the space bar. + +<bf>NOTE</bf>: You need <bf>wget</bf> version 1.9.1 or higher to use +Schedules Direct. + +The mythtv-setup program will contact the Schedules Direct servers and get +your account information. Once you're done, you may click the Finish button +and skip the next few paragraphs in this document since they only apply to +users that are using the external XMLTV script to get their guide data. + +If you wish to continue using the XMLTV grabber, then move to the Zip/postal +code field and put in the appropriate value. + +If you're outside of North America, then some manual interaction will be +required with XMLTV. You may need to switch from the MythTV setup program +to the console it was run on to interact with XMLTV. + +Once you have chosen your provider, press RETURN to continue. XMLTV will +now begin collecting the initial data for your location. The screen may +blank for a few seconds to several minutes, depending on the load of the +listings provider and the speed of your connection to the Internet. Be +patient! + +You will then be returned to the Video Sources screen. If you have multiple +video sources available, such as Antenna, Cable, etc, go ahead and define +them all, even if they're not all going to be physically connected to the +master backend server. Once you're done, press ESC to return to the main +screen. + +<sect2>Input Connections +<p>The final configuration item is Input Connections. On this screen, you +will associate the various video sources you defined earlier with a physical +input to a encoder card. It's entirely possible that you have multiple +tuners, and each tuner has a different input, so on this screen you let +MythTV know which device will connect to which input source. + +When you start this screen, you should see a listing of the various input +connections available on each of the Capture cards you defined earlier. For +example, you may have a capture card with a tuner, a SVideo and a Composite +connection. If you wanted to associate the tuner (a.k.a., "Television") +with an "Antenna" source you defined in Video Sources, you would move to the +<tt>/dev/videodevice (Television) -> </tt> line and press the space bar. +Using the left and right arrow keys will show you the various choices you +have already created for video source. In our case, you would use the +left/right cursor keys until "Antenna" was shown in the Video Source field. +Press down to move to the next setting. + +On the connection pane there is a "Scan for channels" button, if you are +configuring a digital source such as a DVB card, you need scan for channels +and you must do this before pressing the "Fetch channels from listings +source" button. You may scan for analog channels on an analog input, but +this is not needed. + +<!-- Ugh! Who's been editing the HOWTO? This next section needs some cleanup --> + +The other button is called "Fetch channels from listings source". As long as +you have a real listings source you should fetch channels from them for +analog channels. You can do this for digital sources as well (unless the +listing source is transmitted EIT data). If you are using XMLTV, you may need +to switch from the MythTV setup program to the console it was run on to +interact with XMLTV after pressing this button. It is possible to fetch the +channels on the command line using mythfilldatabase. But if you need to do +this, you will probably need to re-enter the MythTV setup program to +configure the "Starting channel" setting for this source->input connection. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: If you have a Hauppauge PVR-500, you must think of +it has two PVR-150's on a single PCI card. For example, if you have a +single PVR-500 card, it will appear as <tt>/dev/video0</tt> and +<tt>/dev/video1</tt>. Each <tt>/dev/video</tt> device will have a Tuner input. +</caption> +</figure> +Once you're done, press RETURN to go back to the Input Connections screen. +You would then finish associating the video sources to any other hardware +devices you have available. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: Don't add a video source to a hardware input if you don't +actually have anything connected there. For example, adding "Cable" to the +Tuner and to the Composite inputs without having something connected to +Composite will lead to blank recordings. +</caption> +</figure> + +Press ESC to return to the main menu, and press ESC again if you have no +further items to configure, thereby returning you to the command line. + +<sect2>Channel Editor +<p>The channel editor is used to globally alter channel information, +including items like hue, contrast, fine tuning and others. Users in North +America shouldn't run the channel editor until you've completed the initial +mythtv-setup and ran <bf>mythfilldatabase</bf> at least once to populate the +database. + +<sect2>Storage Groups <label id="storagegroups"> +<p> +<figure loc="here"> +<eps file="add.eps" height="1cm"> +<img src="add.png"> +<caption> +New in MythTV 0.21 +</caption> +</figure> +<sect3>Introduction. +<p> +Storage Groups are lists of directories that are used to hold MythTV +recording files giving you a flexible way to allow you to add capacity to +your MythTV system without having to use exotic solutions such as LVM, +filesystem expansion or RAID Online Capacity Expansion. You can also use +Storage Groups to organize recordings and to put recordings of a certain +type into one subdirectory. + +Storage Groups do not offer redundancy in case of hard drive failure, but +unlike LVM, if you lose a hard drive, you only lose the recordings that were +on that drive. With LVM, if you lose a hard drive, you will most likely +lose <bf>everything</bf>. + +<sect3>How to use Storage Groups. +<p> +By default, there is only one Storage Group called "Default", and it is +used for all recordings and Live TV. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption> +<bf>NOTE</bf>: You need to add at least one directory to the Default +Storage Group or else you will not be able to record anything with MythTV. +</caption> +</figure> + +For example, if you have 5 hard drives in your system, your first hard drive +could be your "boot" drive, and the remaining four could be dedicated to +media storage. You could format the drives and mount them as +<tt>/mnt/store/d2</tt>, <tt>/mnt/store/d3</tt>, <tt>/mnt/store/d4</tt> and +<tt>/mnt/store/d5</tt>. + +Within each mount point, it's <em>strongly</em> recommended that you use a +sub-directory and make that the destination path for the Storage Group. See +the <ref id="storagegrouptip" name="Tip"> in the "Configuring the Master +backend" section for additional information. + +You would then add the four subdirectories you created under the mount +points (<tt>/mnt/store/d1/video</tt>, etc) into the "Default" Storage Group. + +At recording time, if there were four simultaneous recordings, MythTV would +put one recording onto each drive. + +Or, say that you originally installed MythTV to a 80GB hard drive, and that +hard drive is now filling up. You could simply add a new drive to your +system, mount it and update the Storage Group to add additional space. + +You may create additional Storage Groups to store specific recordings in +their own directories. Storage Groups are edited via the 'Storage +Directories' section of mythtv-setup. + +You can also create multiple Storage Groups to group recordings together; +recording schedules now have an option to specify which Storage Group to +use. + +MythTV will balance concurrent recordings across the available directories +in a Storage Group in order to spread out the file I/O load. MythTV will +prefer filesystems that are local to the backend over filesystems that are +remote until the local filesystem has 2 concurrent recordings active or +other equivalent I/O, then the next recording will go to the remote +filesystem. The balancing method is based purely on I/O, Myth does not try +to balance out disk space unless a filesystem is too low on free disk space +in which case it will not be used except as a last resort. + +Storage Groups are global, but can be overridden on a slave backend by +creating a local Storage Group by running <bf>mythtv-setup</bf> on the +slave. If a problem occurs and the slave backend is unable to use the +desired Storage Group, it will fail back and try the directories defined in +the master's Storage Group. + +There's also a special 'LiveTV' Storage Group, but the directory list starts +out empty. If you add a directory to the Storage Group, it will be used +instead of putting LiveTV recordings in the Default Storage Group. This +will allow you to put your LiveTV recordings on their own filesystem, which +is similar to the old MythTV method which used a RingBuffer for LiveTV. Of +course, you don't have to do anything, and Live TV recordings will just go +into the Default Storage Group where they'll be the first programs eligible +for expiration if the system needs free space for recordings. + +Usage information for all Storage Group directories is visible on the +mythfrontend status screen as well as the mythbackend status webpage. +MythTV is smart enough to determine which directories are on shared +filesystems so it should not count free or used space multiple times if you +have more than one directory on the same filesystem. + +<sect3>Migrating to Storage Groups. +<p>Migrating to Storage groups is very simple: if you have existing +recordings in a storage directory, then the system will automatically add +that directory to the Default Storage Group. If you then add additional +directories to a storage group, the system is flexible enough to check +<em>all</em> Storage Groups for a file before deciding that it can't be +found, which means that you can use the <bf>mv</bf> command from the Unix +command line to arrange files however you'd like. + +<sect3>Advanced: Algorithm used by the Storage Group +<p>This section details the logic of the Storage Group allocation engine. + +The current load-balancing preferences (in order) are: +<itemize> +<item>Local filesystems over remote +<item>Less-busy (less weight) over more-busy (more weight) +<item>More Free Space over Less Free Space +</itemize> + +The 'business' of a filesystem is determined by weights. The following +weights are added to a filesystem if it is in use for the following things: +<itemize> +<item>recording = +10 +<item>playback = +5 (mythfrontend) +<item>comm flagging = +5 (mythcommflag) +<item>transcoding = +5 (mythtranscode) +</itemize> + +If a recording is due to end within 3 minutes, it is not counted against +the weight of a filesystem. This is done to account for the pre/post-roll +and start-early/end-late settings. + +<sect1>Post-configuration +<p>Run the <tt>mythfilldatabase</tt> program as directed. The master +backend will obtain guide data for all the video sources you defined during +setup. + +<bf>NOTE</bf>: If you are using Schedules Direct and watching the output messages +on the console or the log file it is normal to see a "401 Unauthorized" +error followed by a "200 OK" when the connection to Schedules Direct is being +established. +<tscreen><verb> +From : Sun Jun 13 05:00:00 2004 To : Mon Jun 14 05:00:00 2004 (UTC) +--02:58:01-- +http://datadirect.webservices.zap2it.com/tvlistings/xtvdService + => -' +Resolving datadirect.webservices.zap2it.com... 206.18.98.160 +Connecting to datadirect.webservices.zap2it.com[206.18.98.160]:80... +connected. +HTTP request sent, awaiting response... 401 Unauthorized +Connecting to datadirect.webservices.zap2it.com[206.18.98.160]:80... +connected. +HTTP request sent, awaiting response... 200 OK +Length: unspecified [text/xml] + + [ <=> ] 114,125 63.57K/s + +02:58:03 (63.53 KB/s) - -' saved [114125] + +Your subscription expires on 08/20/2004 12:00:00 AM +Grab complete. Actual data from Sun Jun 13 05:00:00 2004 to Mon Jun 14 +00:00:00 2004 (UTC) +</verb></tscreen> + +Once <tt>mythfilldatabase</tt> has finished, start the master server before +continuing. +<tscreen><verb> +$ mythbackend +</verb></tscreen> + +mythbackend will print information about connections and what it's doing to +the console. If you'd like to see the options that are available for +mythbackend, type <tt>mythbackend -h</tt> for help. + +As of MythTV v0.21, the available options are: +<tscreen><verb> +$ mythbackend --help +Valid options are: +-h or --help List valid command line parameters +-l or --logfile filename Writes STDERR and STDOUT messages to filename +-p or --pidfile filename Write PID of mythbackend to filename +-d or --daemon Runs mythbackend as a daemon +-v or --verbose debug-level Use '-v help' for level info +--printexpire List of auto-expire programs +--printsched Upcoming scheduled programs +--testsched Test run scheduler (ignore existing schedule) +--resched Force the scheduler to update +--nosched Do not perform any scheduling +--nojobqueue Do not start the JobQueue +--noautoexpire Do not start the AutoExpire thread +--version Version information +</verb></tscreen> + +Running mythbackend as a daemon and using the logfile option will allow you +to have mythbackend automatically start up during boot. You can follow the +steps outlined in the section called <ref id="mythbackend_autostart" +name="Automatically starting mythbackend at system boot time"> for +configuration steps. + +If you enable the <tt>-l</tt> parameter, you will want to keep your logfiles +rotated (so that they don't fill up a partition). See the section called +<ref id="logrotate" name="Automatically rotating logs"> for more +information. + +<sect1>Configuring a non-master backend <label id="nonmaster_backend"> +<p>Ensure that you've granted access to the master MySQL database for remote +backends as discussed in the section titled <ref id="modify_perm_mysql" +name="Modifying access to the MySQL database for multiple systems"> and that +you have the correct IP address for the database server in the "Database +Configuration" screen of the mythtv-setup application on this slave backend. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: Slave backends <bf>must not</bf> run a local MySQL +daemon. By default, they will connect to their local daemon rather than the +central database, causing unexpected behavior such as empty "Watch +Recordings" lists and a failure to locate the Video Sources defined on the +master backend. Modify the <tt>/usr/local/share/mythtv/mysql.txt</tt> file +on all slave backends to ensure that the <tt>DBHostName</tt> has the address +of the MySQL server. + +Caveat: You may make a slave backend the primary MySQL server, or run a +non-MythTV database on a slave backend as long as you have edited the +<tt>mysql.txt</tt> file on <bf>all</bf> systems and made it consistent. +There can be only one authoritative MySQL database in a MythTV system - +errors such as the one above ensue if backends and frontends have differing +ideas of which MySQL database they should talk to. +</caption> +</figure> + +Make sure that the IP addresses on the General setup screen are accurate. +If the slave backend can't communicate with the master backend due to IP +address misconfiguration then MythTV will not function properly. + +Configuration of a non-master backend follows the same general procedure +as that of the master backend, with the exception that you skip over the +"Video Sources" step. All possible video sources need to be defined on the +master backend system; only the master backend will query a listings +provider to obtain guide data for all the non-master backends. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: Do not run <tt>mythfilldatabase</tt> on a non-master backend. +</caption> +</figure> +<sect1>Configuring and running mythfilldatabase +<p><figure loc="here"> +<eps file="warning.eps" height="1cm"> +<img src="warning.png"> +<caption><bf>NOTE</bf>: <bf>mythfilldatabase</bf> might take a while to complete, +depending on any number of factors, most of which you can't control. It's +best to just let the program run to completion. +</caption> +</figure> +<bf>mythfilldatabase --help</bf> will give a full listing of the options +available. + +<bf>mythfilldatabase --manual</bf> is another option; the manual option will +allow you to fine tune channel frequencies and specify which channels will +be added to the database. + +<bf>mythfilldatabase --file</bf> is an option if there isn't an XMLTV grabber +for your country, but you <bf>do</bf> have an XML formatted listings file +created by some other program. + +<bf>mythfilldatabase --xawchannels</bf> is an option if you have used +<bf>xawtv</bf> to fine-tune your channels and would like to import the fine +tuning offsets into MythTV. + +<bf>mythfilldatabase --refresh-today</bf> will only pull guide data for +today (in case of late-breaking changes to the schedule). + +<!-- get more information on the manual setting --> + +<sect2>Periodically running <bf>mythfilldatabase</bf> +<p>In order to keep your database filled, <bf>mythfilldatabase</bf> should be +run once a day. + +To use MythTV's built-in capability, you'll need to run the +<bf>mythfrontend</bf> Setup option. From the mythfrontend, enter the +Setup>General screen and advance to "Mythfilldatabase", the fourth screen. +Select the checkbox, then complete the options as you see fit. The +<bf>mythbackend</bf> program will now run <bf>mythfilldatabase</bf> for you. + +<sect1>Grabbing channel icons for Schedules Direct users +<p>While the Schedules Direct TV listings service has several advantages, it +does not support grabbing logo icons for the stations you receive. However, +there are utilities provided with MythTV which you may use to grab your +initial set of icons and to keep them updated if your lineups change. + +First, you need to generate or obtain an XML file with the information for +your stations. + +If you have XMLTV software installed, there is a perl script in MythTV's +<tt>contrib/</tt> directory which will generate this file for you. Run the +command: +<tscreen><verb> +$ perl mkiconmap.pl +</verb></tscreen> + +You will be asked for your zip code and the service that you use. If there +are no errors, the <tt>iconmap.xml</tt> file that you need for the next step +will be created. + +If you do not have XMLTV software installed and do not want to install it +for the sake of this minor task, there is a generic +<tt>contrib/master_iconmap.xml</tt> which you can copy and use but this may +not be as complete as using the specific information for your service. + +Once you have an <tt>iconmap.xml</tt> file, add the icon information to your +database and grab any new icons with the command: +<tscreen><verb> +$ mythfilldatabase --import-icon-map iconmap.xml --update-icon-map +</verb></tscreen> + +<sect>Configuring mythfrontend. +<p>Once you have completed configuration of your backend systems, the next +step is to configure the frontend client. + +When you start mythfrontend for the first time, it will attempt to connect +to a configuration database on the local machine. If there is none, a +"Database Configuration" screen will appear, and you will need to fill in +some details. The "Host name" field needs the backend or database server's +IP address or DNS name, and the User or password fields may need to be set +to match your database user accounts. After editing those fields, press +Enter twice to write these configurations on your local machine, and attempt +to connect to the database. If you make any mistakes, the screens will pop +up again. + +Now that mythfrontend has started up, you should have a number of +buttons/choices. Before doing anything, go to TV, then to Setup and +configure the frontend client. +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: You should go through the various setup screens in +mythfrontend before using any other modules to ensure that the the database +is correctly initialized. +</caption> +</figure> +<sect1>General +<p>The General screen has configuration items that don't really fit anywhere +else. The first few configuration items ask you to indicate the number of +seconds to record before or after a program, which is useful if the +broadcast network or your system clock are out of sync and will help prevent +you missing the beginning or end of a program. + +To change the value, use the left and right arrow keys to increment and +decrement the number of seconds. When you're satisfied with the result, use +the down arrow to put the input focus on the Next button or press RETURN to +continue to the next page. + +The next page has a number of options to do with how channels are displayed +on your system. The help text will give you more information. Move the +focus to Next and press the space bar to continue. + +The last General page sets up some final configuration items. See the help +text for more information. + +<sect1>Appearance +<p>This set of screens is mostly concerned with how MythTV will look on your +system. From here, you can choose different themes and set the resolution +of your system. + +<sect1>Program Guide +<p>Fairly self explanatory. Note that the alternate program guide does not +use the same font settings as defined in Appearance, so if the EPG is +unreadable this is where you make the adjustments to fonts, number of +elements displayed, etc. + +<sect1>Playback <label id="deinterlace_"> +<p>The one configuration item which may cause problems on your system is the +"Deinterlace playback" setting. MythTV uses a linear blend algorithm for +deinterlacing, which will improve how the image looks on your screen. +Deinterlacing requires that your processor support SSE. (Streaming SIMD +Extensions, aka "MMX2"). Early Intel Celeron (those that don't use the +Coppermine 0.18um core and are usually <600MHz), Pentium Pro and Pentium II +CPUs do not have SSE, so make sure you haven't enabled deinterlacing if +your processor doesn't support it. If you enable it, and your processor +doesn't support SSE, you will get "Illegal Instruction" errors. + +To determine if you've got SSE on an Intel processor, you can: +<tscreen><verb> +$ cat /proc/cpuinfo +[snip] +flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca +cmov pat pse36 mmx fxsr sse +</verb></tscreen> + +Notice the <bf>sse</bf> at the end of the line - this tells you that this +processor will be able to deinterlace correctly. + +On an AMD processor, look for "3dnow" in the cpuinfo line; "3dnow" is AMD's +implementation of SSE instructions, so if your processor has 3dnow you +shouldn't have any issues with deinterlacing. +<sect2>Video Filters +<!-- Submitted by Bruce Markey --> +<p>MythTV provides a means of employing video filters while recording and +during playback. These filters can be used to improve or modify the video +image, including hiding the effects of an interlaced image or reducing the +impact of noise in a poor video signal. The following is a brief +introduction to introduce you to the filters that are available in MythTV +version 0.20 and higher. +<sect2>Applying filters +<p>One or more filters can be included in a "filter chain". The filters to +be used are identified in a "filter string". A filter string is a group of +filter names and parameters separated by commas. To include parameters, the +filter name is followed by "=" and the parameter information. There should +be no spaces in the filter string. Here is an example filter string: + +With parameters: <tt>kerneldeint=10:1,denoise3d=12</tt> + +Without: <tt>kerneldeint,denoise3d</tt> + +Recording filters are set for each individual channel. These may be used +when encoding in software (MPEG-4, RTjpeg) but do not apply when using a +capture card with hardware encoding such as those supported by the ivtv +driver, DVB, HDTV or MJPEG cards. You can run MythTV's "setup" program and +select the "Channel Editor". On the first page for each channel, you can +enter a filter string in the box titled "Video filters". If you are running +"mythweb" on your web server, you can click on "Settings" then "Channels" +and enter filter strings in the "videofilters" column. + +Playback filters are per-host and apply to any recording you watch from the +frontend where filters have been applied. Playback filtering can only +work with software decoding so the viaslice, xvmc, and ivtv outputs ignore +filters entirely. From "mythfrontend" go to Setup->TV Settings->Playback. +Enter your filter string in the box titled "Custom Filters". + +<sect2>Currently Available Filters +<p>"Deinterlace Playback" checkbox. + +This implements special behavior needed for the "bobdeint" filter but can +also be used to choose any of the deinterlace filters. If you prefer, you +may leave this unchecked and include any of the deinterlace filters, other +than "bobdeint", in your custom filter chain. + +o The "invert" filter + +Invert ignores any parameters and inverts the pixel values of the video +frames. In other words, a negative image. This would rarely be useful but +may be a good example to verify that your filter strings take effect. + +o The "linearblend" filter + +It is a simple deinterlacing filter that ignores parameters and works by +blending adjacent lines. It replaces combing in interlaced video with a +less distracting "ghost" image. + +o The "bobdeint" filter + +This filter splits the interlaced image into two separate fields that +can be line doubled then displayed at twice the frame rate. If the +display is at the same refresh rate as the recording (59.92Hz NTSC or +50Hz PAL) this will cause each refresh to show objects in motion in +a new position with no jagged edges. However, if the display is not +synchronous, it will cause flickering or the appearance of the picture +moving up and down by one line. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: This filter requires the frame rate to be doubled +and therefore can only be used with the "Deinterlace Playback" checkbox. +Do not include this in your filter chain. +</caption> +</figure> + +o The "kerneldeint" filter + +Kerneldeint is a more complex deinterlacing filter which applies a filter +kernel using input from several lines. It generally removes combing without +a "ghost" image, sometimes leaving a faint outline of the image from the +other field. It is considered to be less distracting to watch than +linearblend or no filter at all. It accepts one or two integer parameters +separated by a colon. + +The first parameter is the filter threshold and defaults to 12. Adjacent +lines differing by more than the threshold value are filtered. The second +option defaults to 0. If set to a non-zero value, it will cause the filter +to skip chroma, and filter only the luminance. It may be useful on some +capture cards which do not capture the chroma fields of interlaced video +correctly. + +o The "onefield" filter + +This is a simple one-field deinterlacing filter that uses only one field of +the interlaced video. By default it keeps the top field, though passing the +parameter "bottom" will cause it to keep the bottom field instead. + +This filter is primarily useful for those who display 1080i HDTV signals +with a video mode that has 540 pixels vertically. The advantage over other +deinterlacing filters is that scenes with motion never show combing or +ghosting. + +o The "adjust" filter + +This filter adjusts the digital values for luma and chroma to ensure that +they will fall within the ranges specified in the ITU-R601 standard. By +default, this corrects a known problem for the luma range used by bt8x8 +chips which causes video to look washed out. If parameters are passed, there +need to be exactly six. However, passing a single parameter of "-1" will +disable the filter. + +1: luma minimum input value (int) +2: luma maximum input value (int) +3: luma gamma correction (float) +4: chroma minimum input value (int) +5: chroma maximum input value (int) +6: chroma gamma correction (float) + +The default bt8x8 correction values are equivalent to +"16:253:1.0:2:253:1.0". Output ranges are fixed at ITU-R601 values (16-235 +luma, 16-240 chroma). + +<bf>NOTE</bf>: If it is not already specified in the filter chain, this +filter will be automatically applied when recording with the "bttv" driver. + +o The "quickdnr" filter + +A fast temporal denoiser. This can take 1, 2 or 4 parameters, each being a +value from "0" for the least filtering to "255" for the greatest filtering. +With one parameter, the filter will compute the values it should use for all +of its variables. Two parameters will set the filter strength for luma and +chroma independently. If you are interested in how the algorithm works, you +may examine the source code to see how four parameter are used. + +o The "denoise3d" filter + +A slower denoiser that applies a spatial and temporal low-pass filter. The +spatial filter can remove some noise that quickdnr can't, but a more +powerful CPU is needed. This filter accepts 3 float parameters: + +<itemize> +<item>luma spatial filter strength +<item>chroma spatial filter strength +<item>luma temporal filter strength +</itemize> + +Reasonable defaults will be selected for omitted parameters. The chroma +temporal filter strength is calculated from the other filter strengths. + +o The "crop" filter + +Covers edges of video with black bars. This helps improve video quality +when the edges of the frame are distorted. By default, this removes 16 +pixels from each edge. This can optionally take four parameters representing +top:left:bottom:right. The number times 16 is the number of pixels to remove +so, for example, the default is "=1:1:1:1". + +o The "forceyv12" and "forceyuv422p" filters + +These force the filter manager to use the given format. You can use one of +these at the head of a filter chain to change the capture format. The most +likely use would be forceyuv422p to use YUV422P capture on cards with known +chroma interlacing problems with YV12. + +There are some filters included in the MythTV source code that should +not be used: + +o The "forcergb24" and "forceargb32" filters + +The two RGB formats should not be used because there is no conversion filter +for them yet. + +o The "convert" filter + +It exists but don't use it. The filter manager uses this filter +automatically when it is unable to match the input/output formats of two +adjacent filters. + +o The "postprocess" filter + +While this exists in MythTV source code, it is currently not recommended for +use. + +<sect2>Usage Considerations +<p>There are trade-offs to consider when deciding if it would be wise to use +a filter. Any processing will modify the original image so you should assess +if the filter has made a noticeable improvement to the picture in order to +justify the impact of the processing. Adding any filter will inherently +increase CPU usage. The impact can vary dramatically depending on your CPU +type and speed, the resolution of the recording, which filters you are using +and other factors. You can only determine what is right for you through +experimentation. However, as a starting point, here are some filter strings +that you may find useful: + +For typical broadcast stations: "kerneldeint,quickdnr" + +For stations with poor signal quality: "linearblend,denoise3d=12" + +For synchronous TV-out: check Deinterlace with "Bob (2x framerate)" + +<sect1>Recording <label id="Recording"> +<p>Depending on your capture card, MythTV offers different video encoders. +The following types of hardware encoding cards are supported: +<itemize> +<item>MJPEG - Zoran-based cards; see <url url="http://mjpeg.sourceforge.net" name="http://mjpeg.sourceforge.net"> +<item>MPEG-2 - iTVC15/16 based cards (Hauppauge PVR-250/PVR-350); see <url +url="http://ivtvdriver.org" name="http://ivtvdriver.org"> +<item>HDTV - pcHDTV cards; see <url url="http://pchdtv.com" name="http://pchdtv.com"> and +the Air2PC-ATSC-PCI see <url +url="http://www.cyberestore.com/product_info.php?cPath=28&products_id=103" +name="http://www.cyberestore.com/product_info.php?cPath=28&products_id=103"> +<item>DVB - cards supporting DVB; see <url url="http://linuxtv.org" name="http://linuxtv.org"> +</itemize> +For cards without hardware encoding capabilities (all cards supported by +V4L not listed above), Myth includes two methods for software encoding: +RTjpeg and MPEG-4. RTjpeg has significantly fewer CPU demands than MPEG-4, +but it generates larger files than MPEG-4 for a given recording. + +For DVB and HDTV cards, no further configuration is required after +setting up the card using the 'mythtv-setup' program. +For all other cards, configuration is done through MythFrontend. +Selecting 'Recording Profiles' from the 'TV Settings' screen will list +the profiles currently available for the cards in your system. +Depending on what types of cards you have installed you may see: +<tscreen><verb> +(Create new profile group) +Software Encoders +Hardware MPEG Encoders +Hardware MJPEG Encoders +Transcoders +</verb></tscreen> +The '(Create new profile group)' option will allow you to create custom +profiles in case you have multiple backends. Note that custom profiles +are per backend and card type. If you have 2 MPEG-2 encoders in a given +backend system, creating a custom profile will affect both of them. This +option should not be needed otherwise. + +The 'Transcoders' group is a little different from the others. Selecting +this group will result in a menu with the following options: 'RTjpeg/MPEG-4' +and 'MPEG-2'. These types indicate what transcoder options will be used for +a given input type (i.e. the 'MPEG-2' settings would be used to transcode +MPEG-2 files into MPEG-4. The source of the MPEG-2 stream (DVB, HDTV, or +PVR-x50) does not matter. Configuration of the options is the same as below +(although any resolution settings will be ignored). + +Selecting any of the other options will show a new screen with a list of +four profiles: +<itemize> +<item>Default +<item>Live TV +<item>Low Quality +<item>High Quality +</itemize> + +The Default profile will be used for any recording which does not otherwise +have a specific profile assigned. The 'Live TV' profile will be used when +watching TV. The remaining two profiles are available for customizing to +allow for more precise control over what quality is used for a given +program. + +Selecting a profile will allow you to adjust the relevant options for that +card. The most significant setting is the recording resolution, but you can +also choose encoding format, audio format, and tweak other encoder specific +properties. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: although the width and height can be changed to almost +anything, if you start MythTV and don't see video or you get "segmentation +fault" errors, it is likely that the video4linux (v4l) subsystem did not +like the height and width parameters specified. It's best to leave the +default as-is until you're sure that MythTV is operational. +</caption> +</figure> + +See the <ref id="capture_resolution_" name="What capture resolution should I +use? How does video work?"> section for more information. + +<sect1>Xbox Frontends +<p>MythTV is able to control the LED on the Xbox to indicate backend +recording status. + +To control the LED, you will need the <bf>blink</bf> program from the +xbox-linux project, which is installed as <tt>/bin/led</tt> on GentooX. On +Xebian (the new Ed's Debian) you must install it yourself. On other +distributions it may or may not be installed as a program called +<bf>blink</bf> and should be located in your path. (Type <tt>which +blink</tt> to see if the program is available.) If you do not have +<bf>blink</bf>, you may obtain it from the Xbox-Linux project site at <url +url="http://xbox-linux.sf.net/" name="http://xbox-linux.sf.net/">. The +program you need is part of the <tt>eds_i2c_staff</tt> module in CVS. Note +the spelling. + +Once you have installed <bf>blink</bf> you will need to set permissions. +<bf>blink</bf> needs write permission to the i2c device to function +properly. There are three methods to accomplish this. First, you could run +<tt>mythfrontend</tt> as root, which is the simplest method, but could +potentially be a security risk. Next, you may make the <bf>blink</bf> +binary setuid root, which allows non-privileged users to run a program with +root capability. This is done by typing the command: +<tscreen><verb> +$ su +# chmod u+s /path/to/blink +</verb></tscreen> +The final technique would be to set the <tt>/dev/i2c/0</tt> device read/write +for all users, but this is the least preferred method. + +Now it's time to setup MythTV for Xbox hardware. Enter Setup -> General. +On the second page check the 'Enable Xbox Hardware' option. Upon reentering +the settings, you should have a new option named 'Xbox'. Within this option +you may select the distribution, LED colors for recording and the update +interval. If you select GentooX as the distribution <bf>led</bf> will be +used as the <bf>blink</bf> binary name, otherwise, <bf>blink</bf> is used. +Colors should be self explanatory. The update interval determines how often +the frontend should poll the backend to determine if the status has changed. + +<sect>Using MythTV. +<p><figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption> +<bf>NOTE to Red Hat/Fedora 4 users</bf>: Red Hat Linux and Fedora Core ship +with Gnome as the default desktop environment. However, Gnome seems to have +issues with window focus and window switching which sometimes cause +mythfrontend to obscure the video. KDE does not seem to have any such +issues. Therefore you will need to switch to KDE by selecting +RedHatMenu>Extras>System Settings>Desktop Switching Tool and choose "KDE". + +<bf>NOTE to Fedora Core 5 and 6 users</bf>: Fedora 5 and 6 no longer have +this tool in the Menu. Use "switchdesk KDE" from a command line. Read "man +switchdesk" for further information about changing to other desktop +environments. +</caption></figure> +<sect1>Keyboard commands +<p>The <tt>keys.txt</tt> file describes what the various keyboard commands are. +If you have loaded mythweb, you may change the default keys to your liking. +<sect2>mythfrontend +<p> +<table loc=p> +<tabular ca="rll"> +Arrow keys | used to move the highlight point around @ +ALT-F4 | exit out of the application @ +Space/Enter | take action on the item under the highlight point @ +P | play in both "Watch a Recording" and "Delete a Recording" @ +D | delete in both "Watch a Recording" and "Delete a Recording" @ +U | to view details for the currently selected show on the Watch + or Delete screens, EPG, "Program Finder", "Fix Scheduling + Conflicts" and search results screens @ +O | to list the upcoming episodes for the currently selected show + on the EPG, "Program Finder", "Program Recording Priorities", + "Fix Scheduling Conflicts" or search results screens @ +I | edit recording options from the EPG, "Program Finder", + "Program Recording Priorities", or "Fix Scheduling Conflicts" + screens. From the Playback and Delete screens, 'I' presents + options for recorded shows such as Auto Expire or Stop Recording. + Pressing 'I' while on the Recording Options screen will take you + to the Advanced Recording Options screen. +</tabular> +</table> +<sect2>Watching TV or a recording +<p> +<table loc=p> +<tabular ca="rll"> +Up or down | keys change the channel @ +num pad | Type a number to enter a channel number or jump amount (HHMM format) @ +P | pause / play. You may also add an explicit keybinding for 'Play' through + MythWeb, returning you to normal speed if you are in slow motion, rewind + fast forward or pause mode. @ +C | change inputs on TV Tuner card @ +ESC | quits @ +I | puts the On-screen Display up again. During playback, 'I' toggles + between position and show description info. If a jump amount is + entered, jump to that position. @ +M | brings up the electronic program guide (Grid) -- see the EPG section @ +Page Up | jump back the configured number of minutes (default is 10) @ +Page Down | jump ahead the configured number of minutes (default is 10) @ +End or Z | skip to next commercial break marker @ +Home or Q | skip back to previous commercial break marker @ +T | toggle close caption support + Pressing 0-9 (preferably 3 times) + T changes teletext page and turns on teletext. @ +F | rotate between the various Picture Adjustments (Colour, Hue, etc.) + While Picture Adjustment is on-screen, use Left and Right arrows to + adjust. These settings adjust the look of the video playback, and are + independent of the G-key settings used at record-time. @ +[ or F10 | decrease volume @ +] or F11 | increase volume @ +| or F9 | toggle mute @ +/ | jump to the next "favorite" channel @ +? | mark/unmark the current channel as a "favorite" @ +U | increase the play speed @ +J | decrease the play speed @ +A | Adjust time stretch (speed up or slow down normal play of audio and video @ +W | cycle through zoom and fill modes: 4:3 aspect ratio, 16:9, 4:3 Zoom + (like Pan and Scan), 16:9 Zoom, and 16:9 Stretch (eliminates black + sidebars in TV signal) @ +F8 | toggle the sleep timer 30m->1hr->1hr30m->2hr->Off @ +CTRL-B | Jump to the beginning of the recording / ringbuffer @ ++ | Switch between audio streams @ +Left | (if a jump amount is entered) to jump back that amount @ +Right | (if a jump amount is entered) to jump ahead that amount @ + | @ + | @ + | <bf>Without the stickykeys option selected</bf> @ +Left | rewind the configured number of seconds (default is 5) @ +Right | fast forward the configured number of seconds (default is 30) @ +< | starts rewind mode as if stickykeys are selected @ +> | starts fast forward mode as if stickykeys are selected @ + | @ + | @ + | <BF>With Stickykeys option selected</BF> @ +Right | starts fast forward mode @ +Left | starts rewind mode @ + | @ + | @ + | <bf>In fast forward or rewind mode:</bf> @ +Left/Right | increases the ff/rew speed @ +0 | plays at normal speed, but leaves the time indicator on screen @ +1 or 2 | plays back more slowly than normal ff/rew speed (1 is slowest) @ +3 | plays back at normal ff/rew speed @ +4-9 | plays back faster than normal ff/rew speed (9 is fastest) @ +Space | exits fast forward or rewind mode @ + | @ + | @ + | <bf>While video is paused:</bf> @ +Left | rewind 1 frame @ +< | rewind 1 second @ +Right | advance 1 frame @ +> | advance 1 second +</tabular> +</table> +<sect2>Watching TV only +<p> +<table loc=p> +<tabular ca="rll"> +G | rotate between the various Picture Adjustments (Colour, Hue, etc.) + for recording. These values affect the look of the resulting .nuv + file, and are independent of the playback picture settings. While + Picture Adjustment is on-screen, use Left and Right arrows to adjust. @ +H | Channel history. Each repeat steps back through the previous channels. @ +O | Turns on 'Browse' mode, allowing user to browse channels and program + info while watching current show FullScreen. @ +Y | switch between multiple capture cards. <bf>NOTE</bf>: + you will lose your LiveTV buffer on your current card. Useful + for different-sourced cards (such as Dish Network on one, HDTV over-the-air on another card.) @ +</tabular> +</table> +<sect2>LiveTV Browse Mode +<p> +<table loc=p> +<tabular ca="rll"> +Left | browse program prior to current listed program @ +Right | browse program following current listed program @ +Up | browse program on channel above current listed channel/program @ +Down | browse program on channel below current listed channel/program @ +/ | browse program on next favorite channel @ +0-9 | enter a channel number to browse @ +Space/Enter | change channel to channel of current listed program @ +R/r | Toggle recording of current program (cycles through types) @ +ESC/O | Exit Browse mode +</tabular> +</table> +<sect2>Playback Recording Zoom Mode +<p> +<table loc=p> +<tabular ca="rll"> +Left | Move video to Left @ +Right | Move video to Right @ +Up | Move video Up @ +Down | Move video Down @ +PageUp | Zoom In @ +PageDown | Zoom Out @ +Space/Enter | Exit Zoom mode leaving picture at current size and position @ +ESC | Exit Zoom mode and return to original size +</tabular> +</table> +<sect2>If you have two or more tuner cards +<p> +<table loc=p> +<tabular ca="rll"> +V | toggle Picture-in-picture on or off @ +B | toggles the window focus (lets you change channels on the PiP window) @ +N | swaps the two channels by changing channels on both cards +</tabular> +</table> +<sect2>Watching a recording only +<p> +<table loc=p> +<tabular ca="rll"> +Space/Enter | set a bookmark at that point. Next time you start the + recording, you will automatically jump forward to this point + and clear the bookmark. @ +X | queues the current recording for transcoding @ +O | brings up menu to allow toggling settings such as Commercial + Auto-Skip, Auto-Expire, etc. @ +D | exits the current recording and displays the Delete menu @ +E or M | enters/exits edit mode. @ + | @ + | @ + | <bf>In edit mode</bf> @ +Left/Right | move forward and backward @ +Up/Down | alter the amount of time you jump forward and backward. + Increments are: nearest cutpoint, nearest video keyframe, 1 + frame, 0.5 seconds, 1 second, 20 seconds, 1 minute, 5 minutes, + and 10 minutes. @ +PageUp/PageDown | move forward and backward to the nearest cut point @ +< or > | move forward or backward by 10 times the normal jump amount @ +Space/Enter | allows you to set or delete a cut point @ +Z | loads the commercial skip list (if one exists) into the cutlist @ +C or Q | clear all cut points in the cutlist @ +I | Inverts the cutlist +</tabular> +</table> +<sect2>EPG +<p> +<table loc=p> +<tabular ca="rll"> +Arrows | are used to move the highlighted program point around @ +A, D, S, W | perform the same as left, right, down and up @ +PageUp/PageDown | move the channel list up or down a page @ +Home/End | move the highlight left or right by one day @ +Ctrl+Left or < | move the highlight left by one page @ +Ctrl+Right or > | move the highlight right by one page @ +9, 3, 7, 1 | (like a numeric keypad) perform the same as PageUp, PageDown, + Home and End @ +I | bring up more information about a show, and allow you to + schedule a recording. If you select "Record this showing" + while watching Live TV you can "Instant Record" a program. @ +Space/Enter | allow you resolve conflicts or change overrides. If the + program is not already scheduled to record, it will instead act like + pressing 'I'. @ +M | when on a channel will change to that channel @ +ESC or C | exits without changing the channel @ +R | change the current item from Recording/Not-Recording. + Successive keypresses cycle through the scheduled recording + type list. @ +X | change the channel to the currently selected channel without + leaving the EPG (Most useful in the alternate EPG) @ +? | mark/unmark the current channel as a "favorite" @ +/ or 4 | toggle the guide listing between all channels and filtered + "favorites" +</tabular> +</table> +<sect2>Setting Program or Channel Recording Priorities +<p> +<table loc="l"> +<tabular ca="rll"> +Right | increases priority value @ +Left | decreases priority value @ +1 | sorts by title @ +2 | sorts by priority @ +Home/End | toggle sort priority @ +I | edit recording options @ +ESC | commits changes and exits +</tabular> +</table> +<sect2>Viewing Scheduled Recordings/Resolving Conflicts +<p> +<table loc=p> +<tabular ca="rll"> +1 | show all recordings @ +2 | show only important recordings @ +Home/End | toggle show showing all/important @ +I | edit recording options @ +Space/Enter | resolve conflict or override +</tabular> +</table> +<sect2>Viewing Search Listings +<p> +<table loc=p> +<tabular ca="rll"> +Home | change to the previous view if applicable @ +End | change to the next view if applicable @ +M | select another view if applicable. In the + title and description search popup, press + M again to edit or delete the selected view. +</tabular> +</table> +<sect2>Recording Profiles Setup Screen +<p> +<table loc=p> +<tabular ca="rll"> +D | on a custom profile group displays a popup to delete the group@ +</tabular> +</table> +<sect2>Recording Groups +<p>In the Watch Recordings screen, Recording Groups allow you to separate +programs into user-defined categories, such as "Kids", "Alice", "Bob", etc. +This can be used to reduce clutter, or to segregate content if you use the +PIN function. +<table loc=p> +<tabular ca="rll"> +M | change the view or to set a group password @ +I | move a program from one Recording Group to another +</tabular> +</table> +<sect2>Watch Recordings Screen +<p> +<table loc=p> +<tabular ca="rll"> +1 or F1 | Meaning of the icons @ +/ | Tags a recording. Tagged recordings can be played + either in order or shuffled and deleted as a group. + You can also change the recording group for several + recordings at once by tagging them and using the + Menu (m) button, selecting "Playlist options", + then "Change Recording Group". @ +? | Clear the tagged list. +</tabular> +</table> +<sect2>Remote Controls +<p> +If you are using MythTV with just a remote control then it is suggested that you +map the remote control keys as described below. Your remote control may not +have the same set of keys as those named below, the names are only a suggestion +that roughly correspond to the function. +<p> +If you are adding new key bindings to the program then consideration of this +suggested list will help users with remote controls. +<p> +This list assumes a minimal remote control that only has 20 keys, nearly all +features can be used with this configuration. If you have more keys then you +can access all of the features. With only 16 keys most features are usable. +<table loc=p> +<tabular ca="rll"> +REMOTE CONTROL | LIRC KEYSTROKE | FUNCTION @ +0 - 9 | 0 - 9 | channel selection, EPG navigation, ff/rew speed setting (with stickykeys) @ +Left Arrow | Left | scroll left, rewind @ +Right Arrow | Right | scroll right, fast forward @ +Up Arrow | Up | scroll up, channel change up @ +Down Arrow | Down | scroll down, channel change down @ +Select / OK / Play | Space | Select item, play (with stickykeys) set bookmark @ +Cancel | Escape | Cancel, quit playback @ +Menu | m | EPG (from watching TV) edit (from playback). @ +Pause | p | Pause @ +Other key 1 | i | Information @ +Other key 2 | c | Change tuner card input +</tabular> +</table> + +<sect1>Using themes with MythTV +<p>MythTV is "themeable", meaning that the visual appearance of the program +can be modified by the user without re-compiling or altering the program +functionality. Download the MythThemes tarball from the website and untar it: + +<tscreen><verb> +$ tar -xjf myththemes-0.21.tar.bz2 +$ cd ~/myththemes-0.21 +$ qmake myththemes.pro +$ su - +# make install +# exit +$ +</verb</tscreen> + +The theme will now be available in the mythfrontend Appearance section. + +<sect1>Adding DishTV information to the database +<p>A script for adding Pay Per View information into the MythTV database for +DishTV subscribers is available at <url url="http://www.mythppv.com/" +name="http://www.mythppv.com/">. + +<sect1>Adding support for an external tuner +<p>MythTV supports changing the channel on an external tuner. If you have +an external tuner, such as a DirecTV or digital cable set top box, you +should add <tt>/usr/local/bin/changechannel</tt> to your Input Connections in the +mythbackend configuration GUI. + +However, there is not <bf>changechannel</bf> program per-se, because this is +going to be dependent on what sort of external tuner you have. Look in the +<tt>contrib/channel_changers</tt> directory for a number of programs and +scripts which may be used to change channels. Once you find one which +works, copy it to <tt>/usr/local/bin/changechannel</tt>. + +Feel free to browse some of what sort of hardware is available at <url +url="http://store.snapstream.com/accessories.html" +name="http://store.snapstream.com/accessories.html">, or if you wish to +assemble your own, rather than purchase, the following may be helpful: <url +url="http://www.dtvcontrol.com/" name="http://www.dtvcontrol.com/"> for +cable pinouts. + +<sect1>Using Shutdown/Wakeup +<p>What does the MythTV Shutdown/Wakeup function do? The scheduler on the +Master backend (MBE) keeps track of the idle status of the entire MythTV +system, including the Slave backends (SBE). If it considers the system to be +idle, and thus ready to shutdown, it sets the wakeuptime to the time of the +next recording and then proceeds to shut down all Slave backends and then +itself. Once it is time to begin recording, the Master backend and the Slave +Backends are automatically woken up. This system allows MythTV to record +like a normal VCR, thereby conserving power when not in active use. + +In order to use the Shutdown/Wakeup function there must be some method of +waking up the Master backend. There are any number of solutions, but we +will discuss in detail two possibilities: + +<itemize> +<item>Use another server that runs 24/7 and have it send a WakeOnLAN (WOL) +packet to wake the Master backend. This assumes that you have the WOL tools +installed, and that your Master backend motherboard supports WOL. +<item>Use your motherboard's BIOS wakeup capability. You'll need a motherboard +that supports BIOS wakeup, and some tools. Two that work are: <url +url="http://sourceforge.net/projects/nvram-wakeup" +name="http://sourceforge.net/projects/nvram-wakeup"> and <url +url="http://www.malloc.de/tools/wakeup_clock.html" +name="http://www.malloc.de/tools/wakeup_clock.html"> +</itemize> + +<sect2>A deeper look into the operation +<p>The scheduler keeps track of the idle status of the MythTV system. To +determine whether or not the MythTV system is idle, the following conditions +must be met for a period of time defined in the "Idle timeout (secs)" +parameter. +<itemize> +<item>no client is connected to the server +<item>no recording (neither LiveTV nor a regular recording) is currently taking place +<item>no recording starts within a definable amount of time ("Max. wait for recording (min)") +<item>the "pre Shutdown check-command" returns 0 +</itemize> + +If we get to this idle state the Master backend will set the wakeuptime using the "Set +wakeuptime command", which is the same for WOL and BIOS wakeup. The Master backend will +then shut down the Slave backends and itself using the "Server halt command". + +One caveat is that the scheduler tries to guess if the Master backend was started by a +wakeup call or by the user. If it thinks it was woken up by a user, it +blocks shutdown until a client connects to the Master backend, after which it will +behave as described above. To disable this feature, unset "Block shutdown +before client connected" in the mythfrontend Setup->Setup->General screen. + +Once it is time to startup the system, the Master backend is woken up first and will +wakeup the Slave backends using the "Wake command for slaves". At this time, there is +no support for starting only the required Slave backend, so all Slave backends will startup. + +<sect2>Setting up the MythTV side of this extension. +<p>There are a number of options that are used to control the Shutdown / +Wakeup feature. + +Shutdown/Wakeup Options: +<itemize> +<item>"Idle timeout (secs)" is the time the server waits while idle until a +shutdown occurs. +<item>"Max. wait for recording (min)" is the time the Master backend waits for a recording +without shutting down. For example, this would be used to prevent a 10 +minute system shutdown if a recording is set to start 15 minutes from now. +<item>"Startup before rec. (secs)" Sets how long before a programmed +recording the MythTV system will be woken up. This should be roughly be the +time your systems need to bootup, and if you have Slave backends, you'll +need to ensure this value is long enough for all your machines to perform +their bootup cycle. +<item>"Wakeup time format" is the format of the wakeup time that is given in +the "Set wakeuptime command" as a parameter "$time". You need to set this +according to your wakeup mechanism. If you need seconds since the epoch +(1970-01-01) set the "Wakeup time format" to "time_t". +<item>"Set wakeuptime command" is the command executed to set the new wakeuptime. +<item>"Server Halt Command" is the command executed to shutdown the Master +backend and the Slave backends. +<item>"pre Shutdown check-command" is used to give a +"Go/NO-GO" decision from a non-MythTV source. This command is executed +immediately before the shutdown would occur. The return value is use to make +the following choices: +<itemize> +<item>If it returns a "0" the shutdown will occur as scheduled. +<item>If it returns a "1" the "idle timeout" will be reset and the system +waits again for the timeout. +<item>If it returns a "2" the entire shutdown sequence is reset. This means +that a new client connect is needed before a shutdown occurs, unless you have +the "Wait for client connect" setting disabled, in which case this is the same as +returning "1". An example of a use for this return value is to prevent the shutdown +if a user is currently logged in, or if a specific program (i.e. transcode, +automatic updates, etc.) is currently running. If you don't need it, leave +the field blank. +</itemize> +</itemize> + +The "WakeOnLan settings": +These settings have nothing to do with using BIOS or WOL wakeup, they are +the same for both. +<itemize> +<item>"Master backend" This setting defines timings for the frontends to +wakeup the Master backend using WOL. Useful if your frontend can emit a WOL +packet so you don't need to physically go to the Master backend if you're +trying to watch TV. +<item>"Reconnect wait time (secs)" is the time the frontend waits after +executing the "Wake command" before attempting to retry the connection. This +should be roughly the amount of time your Master backend needs for bootup. +Set to "0" to disable. The frontends will retry to connect for "Count of +reconnect tries" times before giving up. +<item>"Wake command for slaves" is the <em>one</em> command executed to wake +your Slave backends. This should be a script that contains the calls to +wakeup all Slave backend systems. +</itemize> + +<sect3>Using WOL to wake your Master backend. +<p>To use WOL to wake your Master backend you will need a WOL capable Master +backend, a machine that runs 24/7 which can execute an at-job and nc (netcat) +on the Master backend. I use some little bash scripts to make my DSL router +wakeup my mythbox if required. + +Replace $SERVER and $PORT with your own settings! +On my Master backend I have a script that gets called as 'setwakeuptime command' which +looks like the following: +<tscreen><verb> +#! /bin/sh +echo $@ | nc $SERVER $PORT +</verb></tscreen> +This simply cats the parameters (that is $time) to my 24/7 server. On my +$SERVER I have (x)inetd listening on $PORT starting a little script which +cares about setting the at-job. The following additions are necessary on the +$SERVER: + +If you use <bf>inetd</bf>: +<p>In <tt>/etc/inetd.conf</tt> add: +<tscreen><verb> +mythwake stream tcp nowait mythtv /usr/sbin/tcpd /usr/local/bin/mythwake +</verb></tscreen> +If you use <bf>xinetd</bf>, save the following as <bf>mythwake</bf> in your +<tt>/etc/xinet.d/</tt> directory: +<tscreen><verb> +service mythwake + { + socket_type = stream + wait = no + user = mythtv + protocol = tcp + id = mythwake + server = /usr/local/bin/mythwake + } +</verb></tscreen> +and add the following to <tt>/etc/services</tt>: +<tscreen><verb> +mythwake $PORT/tcp +</verb></tscreen> + +Finally, <tt>/usr/local/bin/mythwake</tt> looks like: +<tscreen><verb> +#! /bin/bash +#this should be a command to wake your server +WAKECMD="#!/bin/sh\n /usr/local/bin/wakeMBE" +#first we need to delete all wake jobs in queue +for JOB in atq | cut -f 1 ; do + atrm $JOB; +done +#now we read the date from 'nc' +read date; +#now set the atjob +echo -e "$WAKECMD" | at $date ; +</verb></tscreen> +<bf>SECURITY WARNING</bf>: +Be sure to secure $SERVER:$PORT from untrusted networks, because this +allows 3rd parties to run arbitrary code on your server! + +<sect3>Using BIOS wakeup to wake your Master backend. +<p>Since I don't use this, I cannot say much about this. If your motherboard +supports any wakeup tool you have to call that tool as "Set wakeuptime +command" with the "Wakeup time format" suitable for that tool. +<sect2>Wakeup the MySQL server using WOL +<p>If your MySQL server and your Master backend are not on the same machine, +you can have the Master backend wake your MySQL server using WOL. You will +find the settings for this in the second page of the mythtv-setup program, +or at the end of <tt>mysql.txt</tt>. The meanings are the same as +discussed in "The WakeOnLan settings" above. + +<sect2>Tips/Tricks: +<p>If, for example, one of the Slave backends is also your desktop computer, +you could simply use a little script as 'server halt command' which first +calls <tt>/sbin/shutdown -t TIMEOUT</tt> where TIMEOUT is a value sufficient +for you to react. You could then popup a window using *dialog, asking for +permission to shutdown. If you cancel the shutdown, simply call +<tt>/sbin/shutdown -c</tt>. + +If you get "nvram-wakeup: /dev/rtc: Device or resource busy" your +set-wakeuptime-script should stop the program that uses <tt>/dev/rtc</tt> before +setting the wakeuptime. +<sect1>Controlling the mythfrontend via telnet +<p>To use this feature you must first enable it in Settings>General>General + +The network control listens on port 6546, as demonstrated below: + +<tscreen><verb> +$ telnet basement 6546 +Connected to basement. +Escape character is '^]'. +MythFrontend Network Control +Type 'help' for usage information +--------------------------------- +# help +Valid Commands: +--------------- +jump - Jump to a specified location in Myth +key - Send a keypress to the program +play - Playback related commands +query - Queries +exit - Exit Network Control + +Type 'help COMMANDNAME' for help on any specific command. + +# help jump +Usage: jump JUMPPOINT + +Where JUMPPOINT is one of the following: +channelpriorities - Channel Recording Priorities +channelrecpriority - Channel Recording Priorities +deletebox - TV Recording Deletion +deleterecordings - TV Recording Deletion +guidegrid - Program Guide +livetv - Live TV +livetvinguide - Live TV In Guide +mainmenu - Main Menu +...snip... +# exit +$ +</verb></tscreen> + +Please note that this feature only allows one connection at a time, so any +new connections will automatically terminate prior ones. + +<sect>Scheduling Recordings. +<p>The MythTV master backend is responsible for managing the schedule for +all TV tuner cards on the master and any slave. Its job is to search the TV +listing for the shows you have requested and assign recordings to the TV +tuner cards. If none of the shows that you've chosen overlap, it simply +records all of them. However, if there are shows where the beginning +and end times overlap, the scheduler follows rules that you've specified or +makes logical decisions about what would be best if you haven't expressed your +preference. Further, the "Upcoming Recordings" page allows you make specific +decisions about what you really do and don't want to record. + +<sect1>Record Types +<p>When you choose a show that you would like to record from the +Options Page, there are eight different types of rules to help the +scheduler find which showings you would like to record. + +<itemize> +<item>Single Record -- record only this title at this specific time and +this station. This is the best way to be sure that a certain showing will +be recorded. However, if the TV listings change and the show is not broadcast +at that time, the show will not be recorded but will be marked as Not Listed +to let you know that you should investigate. + +<item>Find One -- this will record a title once from any of the times +that appear in the TV listings. This is useful for recording a movie +or special that has multiple showings because it allows the scheduler +to choose one that doesn't conflict. It is not a good choice for +recording a single episode of a series because it records the first +available showing of the title without regard to the episode +information. + +<item>Record Weekly -- this records a show whenever the title is listed +on the same channel, weekday and time. Note that if the TV station +changes the schedule for a special episode, it would not be +recorded. However, you can add a Single record for the special +episode. If there are no matching showings in the TV listings, +a Not Listed item will be added to your schedule for the next +time slot to let you know that you should investigate. + +<item>Find Weekly -- this will record a title once per week from any +of the times that appear in the TV listings beginning from the time of +the showing that was selected when the rule was set. This is useful +for news, current events or other programs where the same episode is +shown several times each week but the listings may not include +descriptive information. This may not be a good choice if there are +different episodes shown during the week. + +<item>Record Daily -- this records a show whenever the title is listed +for the time and station on any day of the week. Here again, a show +will not be recorded if the time was altered by the station. If there +are no matching showings in the TV listings, a Not Listed item will be +added to your schedule for the next time slot to let you know that you +should investigate. + +<item>Find Daily -- this will record a title once per day from any +of the times that appear in the TV listings beginning from the time of +the showing that was selected when the rule was set. This is useful +for news, current events or other programs where the same episode is +shown several times each day but the listings may not include +descriptive information. This may not be a good choice if there are +different episodes shown during the day. + +<item>Channel Record -- records one showing of each unique episode from +any of the times the title is listed on this station. This is perhaps +the most common rule to use for most shows. + +<item>Record All -- records one showing of each unique episode from +any of the times this title is listed on any channel. This can be +useful if a station has sister stations where shows are rebroadcast +allowing the scheduler to record rebroadcasts on the other station +when the original airing cannot be recorded. +</itemize> + +<sect1>Scheduling Options +<sect2>Priority +<p>By default, all shows you select have equal value to the +scheduler. There are a set of rules to make good choices when +two or more shows are in conflict. However, priority values let the +scheduler know what you prefer so that it can set the schedule based +on your preferences. + +Initially, recording rule priority values are set to zero. You may choose +to leave everything at "0" and let the scheduler follow rules to guess +what you might prefer when there are conflicts. However, if you have +one or two favorite shows, you may want to increase the priority +value so the scheduler will know that you would prefer recording +these over other shows. You might use certain values to rate shows +so that all favorites are 2. good shows are 1 and extra 'filler' +shows are all -1 for example. You could sort each title on the "Set +Priorities" page to have a unique value so the scheduler can know +which show you'd prefer versus any other show. The choice and style +are entirely up to you. However, the more information you give to +the scheduler, the more likely it will make the choices you would +prefer in the first place. + +The scheduler choices are based on the total priority for a showing by +adding up all priority factors that match the showing. By default, most +of these factors are "0" but you may use any combination to express your +likes and needs. + +<itemize> +<item>Per record rule -- this is the "priority" selection in the "Scheduling +Options" section of the options page and this value is included for any +showings that match the recording rule. You may choose to only use these +values and not use the other factors for the sake of simplicity and clarity. +<item> +Per record type -- Setup->TV Settings->Recording Priorities->General allows +you to add to the priority based on the type. It may make sense to increase +the value for "Single" so that by default they have an extra advantage over +other shows. The default is +1. You may want to decrease the value for Find +rules so that they will be less likely to interfere with regularly scheduled +shows and will be more likely to record in a non-conflicting time instead. +The default is -1. +<item> +Per channel -- Setup->TV Settings->Recording Priorities->Channel Priorities +can be useful if you believe that you prefer any of the shows on certain +channels. This would give all shows on a channel an advantage by default. +<item> +Input priority -- in the "mythtv-setup" program, the "Input Connections" +section allows you to add additional priority in the "Input priority". +This is simply another priority factor but has an interesting effect. If a +card input has a higher value than the other cards, the scheduler will see +that you would rather record showings of episodes on this input rather than a +showing on other inputs. If you have multiple cards of different quality, +you may want to set input priority to encourage the scheduler to record +shows on your best card(s) whenever possible. This can also be useful if you +have multiple video sources which include the same stations. For example, +with digital and analog cable you could increase the digital cable input +preference by 1 to tell the scheduler that you want to record from the +digital channel whenever possible but the channel on the analog input could +still be used when the digital input is busy. +<item> +Custom Priority -- this allows you to add any specialized factors you +would like in order to influence scheduling decisions. See the +<ref id="Custom Priority" name="Custom Priority"> section below. +</itemize> +For any single showing of any show you've chosen to record, these factors +are added together to find the "total priority". This is the priority that +the scheduler uses to decide which showings are given the first choice when +filling in the schedule. + +The scheduling priority of a show may also be used to determine +auto-expiration of recordings when disk space gets full (see <ref +id="Auto-Expire" name="Auto-Expire">, below). + +<sect2>Duplicates +<p>Singles will record without regard to duplicate matching. + +<p>The standard recurring methods of All, Channel, Weekly and Daily use the +descriptive information in the TV listings to try to record only one showing +of each unique episode. However, This goal is sometimes complicated by the +fact that the stations may not include a description for a specific episode +but use a generic description for the series instead. When there is a +generic description, the default behavior is to assume that it may be an +episode that you have not seen and to record it for you. One of the +duplicate matching options is "Record new episodes only". If this is +selected, listing that have an original air date of more than 14 days +earlier are considered repeats and are not eligible to record. Generally, +generic episodes will be marked as repeats also. + +<p>Because of generic episodes and other situations, MythTV offers an +alternative approach where shows may be recorded by choosing from multiple +showings even when the descriptive information is not reliable. All of the +"Find" record types look for matching titles in the listings. If there is a +showing with specific episode information and that episode has recorded +before, that showing is marked as previously or currently recorded. The +scheduler will then choose to record the earliest non-conflicting showing +from any of other remaining showings regardless of the descriptive +information. Generally, Find One is most useful for movies or specials and +the Find Daily and Find Weekly rules are best for news or current events +shows that are repeated. However, these may be useful in other situations +where the standard recording rules may not work correctly. + +<sect2>Conflicts +<p>As you add more shows that you would like to record, the scheduler +will eventually encounter conflicts. If there are two shows at the +same time and you have two or more TV tuner cards, both shows will +record. However, if there are more shows than cards, the scheduler +will have to decide what it thinks it should not record based on the +information you have given. If you see an unexpected situation you +are not "stuck" with the scheduler's choice. You can still tell the +scheduler exactly which shows you do want to record and/or don't +want to record in any situation. + +<sect2>Scheduling decisions +<p>Here are the actual decisions made by the scheduler as it fills in the +schedule. + +<itemize> +<item>Currently recording beats not currently recording -- A recording +in progress can not be moved to another input or time so it "wins" +its current timeslot. + +<item>Single, Daily, or Weekly rules with no match are marked Not Listed -- +If these or Overrides do not match the current listings because the +listings have changed, they are added to the schedule and marked to +indicate that they will not record. + +<item>Rules that could record beat rules that can not record a showing -- +If two rules match the same showing of a program, a rule marked as inactive +or a showing marked as a repeat, for example, yield to the other rule. + +<item>More specific record type is used in place of less specific -- If +two rules match the same showing of a program, preference is given to +Don't Record then Override, Single, Find One, Record Weekly, Find Weekly, +Record Daily, Find Daily, Channel and finally All. + +<item>Higher total priority beats lower total priority -- This is the +core of the scheduling process. Episodes of the highest priority show +are placed on the first available input followed by the next highest +priority show and so on. + +<item>Future start time beats past start time -- If there is an +episode in progress and also a later showing of the same episode, it +is better to record the complete episode. If there isn't another +showing, it will start recording immediately to record the remaining +portion. This should only happen if you add a new rule while the show +is in progress or if the master backend is started after the start time +of a scheduled show. + +<item>More specific record type beats less specific record type -- If +two shows are on at the same time and have the same total priority but +different types they will be sorted by Single then Find One, Record +Weekly, Find Weekly, Record Daily, Find Daily, Channel and finally +All. This only applies if the priorities are the same. + +<item>If both start times have passed, later start time beats earlier start +time -- This attempts to miss the least amount of time. + +<item>If neither start time has passed, earlier start time beats later +start time -- This helps assure that the earliest showing of an episode +has the advantage. + +<item>Lower input id beats higher input id -- The scheduler fills in +open time slots on the first available input for the video source. The +next input is used when there is another show already placed for the +card of the first input. + +<item>Older record rule beats newer record rule -- If two shows are still +equal after all of these other checks, the show whose record rule was added +first is preferred over a more recent addition. + +<item>Postpone showings to resolve conflicts -- If Reschedule Higher +Priorities is set or if a conflict has the same priority as a show +that was scheduled at the same time, the scheduler will check to see +if a scheduled show can be moved to another input or later matching +showing without creating a new conflict so that the conflicting show +can be scheduled to record. + +</itemize> + +<sect2>Reschedule Higher Priorities + +<p>Setup->TV Settings->Recording Priorities->General has a checkbox for +"Reschedule Higher Priorities" which tells the scheduler to try to be a +little smarter in certain situations. If this is checked, the scheduler will +look for situations where a show cannot record because all inputs for the +channel are used for higher priority shows. It will check to see if any of +the other shows could be recorded at another time so that the conflicting +show can be recorded in its place. + +Generally, this is a good strategy but there are tradeoffs. If a higher +priority show is postponed, you will not get to watch it until it is +recorded in the later timeslot. There is also a risk that the TV listings +may change and the later showing may go away. In this rare case the higher +priority show may never record. On the other hand, if you do not use this +option you will miss recording some lower priority shows unnecessarily +unless you manually make similar changes. + +By using Reschedule Higher Priorities, the scheduler will do a better job of +recording as many of your shows as possible when left unattended. It will +also be easy to see that shows have been marked to record at a later time. +You can then decide for yourself when you would prefer to record the first +showing by clicking "Record anyway". + +<sect2>Controlling Your Schedule +<p>The Manage Recordings->Upcoming Recordings page is your control center +for the MythTV scheduler. Unlike other DVR systems, this one page gives you +all of the information and tools you need to see all of your alternatives +and make whatever adjustments you desire. + +The upper half of the screen has a scrollable box listing items that match +your record rules sorted by time. The lower half shows the details for the +highlighted item. There are two 'views' available. Press "1" to include all +of the items that match record rules even if they do not need to be +recorded. Press "2" to focus on just the things that will record and items +that may need your attention. The message in the upper right-hand corner +will remind you when there are conflicts that would prevent one or more +shows from being recorded. + +The items in the list are colored in the record color for things that +will record, white for things that may need attention, gray for those +that do not need to record and yellow when there is a time conflict. +Items at the top of the list may also be highlighted indicating that the +recording is in progress. + +Along with the channels, start times and titles, the right-hand column has +a status code. Numbers indicate which card number has been assigned to +record the show. Letters are used to indicate the reason that something +will not be recorded. Just below the box is a short status message for the +highlighted item that indicates the type of record rule that was matched, +the "total priority" for this showing and a one or two word explanation of +the status code. If you press SELECT, you will see more information about +the status. + +There are a few status codes that may require your attention. "C" indicates +that there are more overlapping shows to record than there are TV tuners to +record them. "L" indicates that the scheduler found that it may be better to +record a later showing of this episode. These states happen as a result of +your choices and should normally reflect your preferences. However, you may +notice situations where you would like to modify the scheduler's initial +choices. + +The first thing you can do is to highlight an item and press INFO to +see the recording options page. From this page you can change the +record rule type, the duplicate matching rules, or raise or lower the +priority to resolve whatever problem you noticed. + +Additionally, you can treat any individual showing as an exception that you +do want to record or don't want to record. To use these "override" features, +highlight the item and press SELECT. You will see a message explaining the +current status and at least an "OK" button to exit without making changes. + +For items scheduled to record, there will be a button for "Don't record" +which will prevent recording this showing but will still allow the same +episode to record in the future. If there is episode description +information, you may also see a button for "Never record". This prevents +recording this showing and tells MythTV to remember that this is an episode +that you've seen or don't need to see if it is ever in the TV listings +again. + +For items that are not scheduled to record, the message will describe the +reason and in the case of "C" or "L" it will include a list of the shows +that are scheduled to record instead. For any item that could potentially be +recorded there will be buttons for "Edit Options" and "Add Override". "Edit +Options" will allow you to change the options for the existing record rule +such as raising the priority so that the show will record. These changes +would apply to this and all future showings that match this record rule. +"Add Override" will allow you to set options that apply to the specific +showing without affecting the recurring record rule. + +If you return to an override page after an override has already been set, +you will also see a "Clear Override" to undo your changes. This option makes +it very easy to try out some "what if" attempts when deciding on your best +strategy in a difficult situation. + +For a recording in progress, there will be a "Change Ending Time" button. +This will take you to the options page for a Single or Override or create +an Override if it is a recurring rule. Here you can go to the Recording +Options section to change the program end time offset. If you extend the +end time so that it overlaps upcoming recordings, the schedule will change +to accommodate the new end time. This may cause a conflict or later showing +even for a show with higher priority. Therefore, it is a good idea to +check your schedule after changing the end time of a recording in +progress. + +<sect1>Storage Options +<sect2>Recording Profile +<p>Each recording rule can be configured with a different recording +profile. For example, colorful cinematography can be configured with a +"High Quality" profile, while 'talking heads' interviews shows can be +configured with a "Low Quality" profile. These recording profiles need to +be configured before using them (see <ref id="Recording" name="Recording">, +above). + +<sect2>Recording Group <label id="Recording Group"> +<p>For organization of the "Watch Recordings" screen and the MythWeb +interface, recordings can be assigned into "recording groups". + +<sect2><ref id="storagegroups" name="Storage Groups"> +<p>This allows you to select any special "Storage Groups" you may have +created to determine where recordings from this rule should be stored +on your disks. The "Default" storage group is always available. + +<sect2>Playback Group <label id="Playback Group"> +<p>This selects a set of pre-configured playback parameters which can be +created and edited in Setup->TV Settings->Playback Groups. When the +recording is played, the values from this playback group will be +used. This allows you to choose a default time stretch value, skip and +jump amounts appropriate for this type of television program. + +<sect2>Auto-Expire <label id="Auto-Expire"> +<p>MythTV will "autoexpire" old recordings to make room for new recordings +when disk space gets filled up. This option can be set to "Don't allow +auto expire" to prevent these recordings from being automatically deleted +when disk space fills up. + +<p>The default setting is for all scheduled recordings to be eligible +for auto-expiration; this can be changed in the Settings->TV +Settings->General page by manipulating the "Auto Expire Default" +checkbox. + +<p>The default auto-expire policy is "Oldest Show First"; the oldest +recordings are deleted first. The "Lowest Priority First" method +chooses to expire the lowest-priority recordings first. + +<sect2>Episode Limit +<p>An episode limit can also be configured to limit the maximum number +of episodes recorded of a single series, to restrict that series' disk +usage. If this is set, you can further decide what to do when this +limit is reached; either stop recording that series, or to delete the +oldest episodes in favor of the new ones. + +<sect1>Post Recording Processing +<sect2>Commercial Flagging +<p>Select whether or not to automatically flag commercials for these +recordings. Commercial Flagging parameters can be set in +Setup->TV Settings->General. + +<sect2>Transcoding +<p>Select whether or not to automatically transcode recordings to save +disk space. Before using this, you must first enable auto-transcode in +the recording profile and configure the transcoding parameters; see +<ref id="Recording" name="Recording">, above. + +<sect2>User Jobs +<p>User Jobs allow you to configure up to 4 custom commands to run on +recordings. They can be configured in mythtv-setup. The following +tokens have special meaning when used in the User Job commands: + +<itemize> +<item>%DIR% - the directory component of the recording's filename +<item>%FILE% - the filename component of the recording's filename +<item>%TITLE% - the title of the recording (e.g., name of the series) +<item>%SUBTITLE% - the subtitle of the recording (e.g., name of the +episode) +<item>%DESCRIPTION% - description text for the recording (from guide +data) +<item>%HOSTNAME% - the backend making the recording +<item>%CATEGORY% - the category of the recording (from guide data) +<item>%RECGROUP% - the <ref id="Recording Group" name="recording +group"> +<item>%CHANID% - the MythTV channel ID making the recording +<item>%STARTTIME% - the recording start time (YYYYMMDDhhmmss) +<item>%ENDTIME% - the recording end time (YYYYMMDDhhmmss) +<item>%STARTTIMEISO% - the recording start time in ISO 8601 format +(YYYY-MM-DDTHH:MM:SS) +<item>%ENDTIMEISO% - the recording end time in ISO 8601 format +<item>%PROGSTART% - the recording's start time (from guide data; +YYYYMMDDhhmmss) +<item>%PROGEND% - the recording's end time (from guide data) +<item>%PROGSTARTISO%, %PROGENDISO% - the recording's start and end +time in ISO 8601 format. +</itemize> + +<sect1>Advanced Recording Options +<sect2>Creating Power Search rules with Custom Record +<p> +MythTV's "Custom Record" feature gives you unlimited control for creating +specialized search recording rules to meet your needs. It allows you to +choose your criteria to search for matching shows based on any of the +information in the program listings, channel information, time functions and +more. This goes beyond the capabilities of any other DVR system and it is +unlikely that this level of scheduling customization will ever be available +in any commercial DVR system. + +<sect2>Getting Started +<p> +Go to Schedule Recordings->Custom Record. This page, helps you build a +database search one clause at a time. Each added clause further limits +which showings will be matched in the TV listings. You can test the +search at any time and when you are done, you can save your search as a +recording rule. + +To familiarize yourself with how you can create custom rules, create a +simple rule to record "Nova" only in primetime. + +The first item at the top of the page allows you to edit an existing rule +or create a new rule. Leave it on "<New rule>". Arrow down to the +third item which says "Match an exact title". Right and left arrows would +allow you to select any of several prefabricated pieces or full examples +but leave it on the default for now. Arrow down to "Add this example +clause" and press SELECT (Enter or Space on a keyboard). The large text +box should now show: +<tscreen><verb> + program.title = 'Nova' +</verb></tscreen> +As you have probably guessed, this says that we want to search for all +programs with the title "Nova" regardless of the time, day, channel, etc. + +If you do not receive a PBS station that carries "Nova" or would like to use +another title, edit the title by pressing the down arrow to highlight the +text box and right arrow over the the word "Nova". If you are using a +keyboard you can simply delete the four letters and type a different title +between the quotes. With a remote control, you can do 'cell phone' style +text entry with the number pad. The delete key is the "X" in the grouping +for "1", zero is grouped with "9" and "0" acts as the "Caps Lock" key. You +can press ENTER in the text box to popup a virtual keyboard. + +Note: the text box honors many familiar Emacs control keys. It is also +possible to cut and paste text into the text box so you can edit with a +favorite editor or insert a rule sent in email or from other sources. + +In any case, choose a title that is shown both in primetime and late night +or daytime. Next, click the "Test" button. You should see a list of the +upcoming episodes for "Nova" just as if you had clicked the Upcoming +button for "Nova" elsewhere in MythTV. + +Press ESC to go back to the Custom Record page. Move to the example +selector then press the right or left arrows until you find "Only in +primetime". Click "Add this example clause". You should now see: +<tscreen><verb> + program.title = 'Nova' + AND HOUR(program.starttime) >= 19 + AND HOUR(program.starttime) < 23 +</verb></tscreen> +Click "Test". You should now see a shorter list with only the showings that +begin between 7PM and 11PM. To create a rule for this, press ESC to go back +to the custom page and move to "Rule Name:" then type "Nova" or anything +else you would like. This is only a label and will not affect the search +results. Once a name has been entered, the "Record" button will light up. +Click this to enter the recording options page. If you named it "Nova" the +title will say "Nova (Power Search)". Set whatever options you would like +then click "Save these settings". You now have a special rule to record +"Nova" but only when it is shown in primetime. + +You can make further modifications to this rule by returning to the Custom +Record page then press the right or left arrow keys on "Edit Rule:" until +you find "Nova". You can experiment and test but the saved rule will not +be updated until you click "Record" then "Save these settings". + +To remove this, or any other rule, you can go to the "Recording Priorities" +page, arrow down to the title, press Enter and change the the recording type +to "Do not record this program" then "Save these settings". + +<sect2>How it Works +<p> +MythTV stores TV program information in a database and uses the Structured +Query Language (SQL) to access the data. Information about each TV program +is stored in the 'program' table and information about each TV station you +receive is stored in 'channel'. These two tables are used in the scheduler +queries and their columns are available to be used in your rules. The rules +you create are stored in 'record'. + +Normal rules in MythTV simply match the title in the rule with the titles +in the 'program' table. MythTV also has search rules for "Titles", +"Keywords" and "People". These store the key phrase in the description +column of the rule and includes them in specialized SQL replacements for +the normal title check. There is also a type called "Power Search" which +takes the raw SQL in the description as the replacement for title +matching. + +Custom Record is a tool to help you build valid SQL for Power Search rules. +You do not need to be a SQL expert to use Custom Record because the +examples are known to work correctly and are usually self-explanatory so you +can choose the pieces you need then modify them. Many powerful solutions to +unique problems are possible by combining the examples. With some creativity +and some knowledge of SQL, the possibilities are limitless. + +<sect2>Common Tricks and Tips +<p> +The example clauses marked "complete example" are actual rules that have +been used to address specific problems. You may find that some of these +are useful for you as-is or with slight modifications. These show off how +powerful custom rules can be but there are also several simple idioms that +you may find useful for many of the shows you would like to record. + +Wait for a known title -- If there is a movie that you anticipate will be +televised in the coming months but is not yet in the listings, you can +select "Match an exact title", edit the movie title, click "Record" then +choose "Record one showing of this title". The rule will wait weeks, months +or years until this title shows up in your listings then it will record one +showing. These rules have no impact on the scheduler throughout the day and +only take a tiny fraction of a second when the master backend starts or when +the listings are updated. + +Silence series out of season -- "Celebrity Poker Showdown", for example, +will have new episodes for a while then long periods where reruns are shown +dozens of times per week. By checking the previously shown flag you can +create a rule that will only match new episodes. Therefore, your schedule +won't be polluted with dozens of entries marked as "Repeat" or "Previously +Recorded". +<tscreen><verb> + program.title = "Celebrity Poker Showdown" + AND program.previouslyshown = 0 +</verb></tscreen> +This allows you to keep rules for your favorite shows that are dormant while +out of season but will spring back to life when new episodes appear. + +Choose showings on certain days -- Several cable stations will show their +highest rated shows a dozen on more times per week. However, the scheduler +only needs two or three choices to do a good job of making a flexible +choice. +<tscreen><verb> + program.title LIKE "Celebrity Fit Club%" + AND DAYNAME(program.starttime) = "Sunday" +</verb></tscreen> +This says to choose any showing of an episode that hasn't been recorded +when it appears on Sunday. This prevents all the other showings during the +week from being listed in the schedule. + +Notice the word "LIKE" and the "%" at the end. This does wildcard matching +so that this would match even if the title ended with "2". "III" or +":Revenge of the Snapple Lady". This can be useful where the title may +change from one season to the next like "Survivor: %", "Big Brother%" or +"The Amazing Race%". + +<sect2>Working with SQL +<p> +As you experiment, it is possible that you may misplace a quote or mistype a +word. If there is a mistake when you press "Test" or "Record" you will see +an error message returned from the database. This will usually give you a +good idea about what needs to be fixed. However, for more subtle MySQL +syntax errors, you can find more information in the documentation at <url +url="http://dev.mysql.com/doc/mysql/en/" +name="http://dev.mysql.com/doc/mysql/en/">. This contains a lot of +information that can be useful for Power Search rules such as the "Date and +Time Functions". There are many other good resources for SQL on the Web. + +While the example clauses demonstrate how to use many of the data columns, +you can get a more complete list of all the columns that are available by +using a MySQL client program: +<tscreen><verb> +$ mysql -u mythtv -pmythtv mythconverg +mysql> describe program; +mysql> describe channel; +</verb></tscreen> +This will show the names of all of the columns along with their type and +default value. Most are easy to understand but a few need some explanation +in order to use them effectively with Power Search. +<itemize> +<item>"program.category_type" holds one of these exact four strings: "movie", +"series", "sports" or "tvshow". + +<item>"program.airdate" is a string representing the year of release for +movies and may have no meaning for other types of shows. + +<item>"program.stars" is a floating point number from 0.0 to 1.0. On a +four star scale, 1.0 would be four stars, 0.75 would be three stars and so +on. + +<item>"program.originalairdate" if provided is the date when a show +was, or will be, first televised. This may be useful for finding +episodes before or after a certain date such as finding just the +original series of "Battlestar Galactica". + +<item>"program.previouslyshown" is a column created by MythTV to try to +determine if a showing is more than 14 days after its original air date or +if the show was marked as a repeat and did not have a date for the first +airing. If this is "0" it usually means that this is a brand new show or a +rebroadcast within the first two weeks. + +<item>"program.generic" is a column created by MythTV to try mark +showings for a series where the specific episode information is not +included. When these generic showings appear, it is impossible for the +system to determine if they are repeats of the same episode(s) or if +they are all different episodes. + +<item>"program.first" is a column created by MythTV to mark the first +showing in the current listings for each episode, movie or special. +Choosing to match only the "first" showing can be useful for sports +that are brodcast live then repeated. + +<item>"program.last" is a column created by MythTV to mark the last +showing in the current listings for each episode, movie or special. +If a showing is marked both "first" and "last" then it is the only +showing of that program in the current TV listings. + +<item>"program.programid" is the Tribune Media Service database record +identifier for each program description. In general, these start with a two +letter prefix, MV, EP, SP or SH that correspond to the +"program.category_type". For most, the last four digits are "0000" except +EP where the last four digits are the episode number in the series. Note +that these are generated by TMS and not the show's producers but they are +usually in the same order as the original air dates for the episodes. + +<item>"program.videoprop" also "audioprop" and "subtitletypes". +These columns contain bit flags for a variety of attributes that +may be associated with a program. These are filled with information +offered by the TV listings provider. However, your listings source +will not have information for all of the available flags. Therefore, +some of these may not be useful for your search rules. This information +is organized in "sets" and the MySQL function FIND_IN_SET() can be used +to test for any of these flags. For example: +<tscreen><verb> +FIND_IN_SET('SURROUND', program.audioprop) > 0 +</verb></tscreen> +would be true for the programs where the surround sound bit is present. +To see all of the available attribute names: +<tscreen><verb> +$ mysql -u mythtv -pmythtv mythconverg +mysql> SHOW COLUMNS FROM program LIKE '%prop'\G +mysql> SHOW COLUMNS FROM program LIKE 'subtitletypes'\G +</verb></tscreen> +</itemize> +Finally, if you are doing something very experimental and a column is not +giving you the results you had anticipated, you can always check the MythTV +source code to see exactly how a column is used. The open source for MythTV +is available from <url url="http://www.mythtv.org/" +name="http://www.mythtv.org/"> . + +<sect1>Scheduling with more than one Input +<p> + +MythTV is designed to allow recording television programs from one or more +service providers, or video source, on one or more video input from each +provider. Some inputs may not be allowed to record at the same time as +each other while others may record simultaneously. + +A television station may be broadcast on more than one channel from one +provider or may be available on channels from two or more providers. If a TV +station is available from more than one source, the video quality or type of +broadcast may differ. Therefore, MythTV allows you to control how you would +like the scheduler to select the best channel and input for a show which is +available on more than one input or more than one channel. + +<sect2>Mutually Exclusive Inputs +<p> +A single TV capture card may have video connections to more than +one of its inputs and each input may be from a different service. The card +may only be allowed to record from one of these inputs at one time because +there is only one encoder on the card that actually captures the content. + +<figure loc="here"> +<eps file="BlockDiagramofavideocapturedevice.eps" height="1cm"> +<img src="BlockDiagramofavideocapturedevice.png"> +<caption> +</caption> +</figure> + +These are mutually exclusive meaning that only one input or the other +may record at a given time but not both. + +Usually, inputs on different cards can record at the same time +but two or more inputs on the same card cannot. However, there are cases +where inputs on different cards should not be allowed to record at the +same time, for example, a firewire card and s-video analog card connected +to the same set top cable box. + +<tscreen><verb> +| +| coax +--------------+ firewire ------------------+ +| .-=|Cable Provider|=------------=| Card 1 input 1 | HDTV +| | |HD/Cable STB |=--. +-----|||||||||||| +| | +--------------+ | s-video ------------------+ +| | `---------=| input 2 | Digital +|wall | coax | Card 2 | +|=---=^=------------------------------=| input 3 | Cable +| +-----|||||||||||| +</verb></tscreen> + +Input 1 and input 2 receive content from the same set top box and the +channels can not be tuned independently. Therefore only one of these two +inputs should be used at any given time. The solution is to create an "Input +Group" with <bf>mythtv-setup</bf> in "Input connections". Including these +two inputs in the same Input Group will tell the scheduler that these are +mutually exclusive and may not record at the same time. Inputs 2 and 3 are +automatically mutually exclusive because they are on the same card so there +is no need to create an Input Group for these inputs. + +Cards such as the Hauppauge PVR-500 are able to record as two cards +simultaneously because it has two MPEG-2 encoders and each encoder appears +as a separate device. DVB cards may be allowed to capture content from more +than one channel at a time if the channels are in the same MUX. + +<sect2>Stations, Channels and Video Sources +<p> +Although we may be accustomed to thinking of a broadcast station and its +channel number as being synonymous, stations and channels are very different +things. A "station" is in a building with wires and employees. A "channel" +is a carrier frequency or digital ID that carries a broadcast stream. The +same TV station may be broadcast over different frequencies in different +cities or by different providers in the same city. The same frequency will +carry different stations in different cities. In the digital realm of DVB +and ATSC (HDTV), it is even possible for a single frequency to carry +multiple program streams but each of these streams of content are actually +different channels that the receiving devices can 'tune' to independently. + +<itemize> +<item>Station: building +<item>Channel: frequency +</itemize> + +In MythTV, a "video source" is a set of channels from a provider, or over +the air, that can be received by an input. The set defines the channels and +the broadcasters primarily associated with each of those channels. If you +have more than one device or cable from the same provider connected to more +than one card and input, you only need to create one video source in +mythtv-setup then associate that one source with each of these connected +inputs. This will let your MythTV system know that the same channels and +their TV listings are available to be recorded from any of these inputs. + +For example. A MythTV system may have two capture cards. Both have a cable +connected to the coaxial connectors. These cables carry the local cable TV +service. In mythtv-setup, the user should create one "Video source" called +"Cable", for example. Under "Input connections", "Cable" should be +associated with each of the two tuner inputs. The scheduler will then know +that any program on one of the channels from the "Cable" source could be +recorded by either card from the card's tuner input. + +You need to create a different video source for each provider or service +that has a different set of channels. Each input with a connection to that +service should be associated with the video source for that service so the +system will know which set of channels are available for each of your active +inputs. + +Let's say that this user also has one digital cable set top box. The digital +cable service carries channels that are not available over basic cable. The +user would create another source called "Digital". This set top box is +connected to the second card by S-Video so under "Input connections", +"Digital" is associated with the S-Video input of card 2. The system would +then know that programs on channels from the Digital source can only be +recorded from this input. Further, the scheduler understands that it can +only record one show at a time from card 2 so it can assign Cable or Digital +shows to the card but not both at the same time. + +Some TV stations may be broadcast over a channel from the Cable source and +also broadcast over a channel from the Digital source. Note that two +channels carrying the same primary station may not have the same TV listings +due to carrying the primary station part time, including local programming +exclusive to one of the channels, the channels may be in different +timezones, etc. Listings information must be associated with each channel +even if two or more channels report that they carry the same station. + +<sect2>Order of Inputs +<p> +By default the scheduler chooses the first (lowest numbered) input which has +a showing of the scheduled program as it fills the schedule. If a lower +priority show is on at the same time as a higher priority show that has been +assigned to input 1, then input 2 will be used next and so on. Therefore, +configure your best card and input first and next best card and input +second. There may be differences in the type or brand of capture card, +signal quality from the cable, system resources such as disk space, CPU, +etc. By configuring your best input first, more recordings, and your highest +priority recordings, will use that input. + +A common situation is that a newer and better card is added last. For +example, you may initially setup your system with two analog cable cards and +then add a HDTV card. If NBC is on a cable channel and "The Apprentice" is +shown in HDTV on an NBC HD channel, the scheduler would still prefer analog +inputs 1 and 2 over the new HD input 3. + +So, if you'd like the scheduler to prefer a new source, the simplest thing +is to run <bf>mythtv-setup</bf> and "Delete all capture cards" then enter +your cards and inputs in your preferred order. This will not remove your +sources and channels - you want to keep those and only renumber your cards +and inputs. In this example, once the changes have been made and the Master +Backend is restarted, the scheduler would then choose "The Apprentice" in HD +on the new input 1 and only use the analog inputs (now numbered 2 and 3) +when the HDTV input was occupied with another show. + +<sect2>Matching Callsigns +<p> +If a recording rule is a type that can record from any channel, "The +Apprentice" would match for any channel that shows episodes which may +include CNBC or BRAVO. However, for Single, Timeslot, Weekslot or Channel +rules, "The Apprentice" would only match showings on the selected station as +identified by the "callsign". For example, KVBC is an NBC affiliate on +channel 3. Channel 733 is KVBCDT which is HDTV over cable from the same +station. If a Single record rule was set for "The Apprentice" on KVBC +channel 3, it could not record this showing from KVBCDT on 733. If 733 was +chosen when the rule was saved, channel 3 could not be used to record. + +However, the "Channel Editor" in mythtv-setup can be used to change the +Callsign for channel 733 to "KVBC". MythTV would then understand that both +of these channels are from the same broadcast station. Assuming the HDTV +input was input number "1", "The Apprentice" would record on 733. If, +however, this HDTV input already had a higher priority show assigned to it +in that time slot, "The Apprentice" would be assigned to KVBC channel 3 on +input 2. + +Having two channels with the same callsign may affect how program +information is shown in mythfrontend. If two sources have the same callsign +and channel number, the program guide and program lists will only show one +instance of the channel number and callsign. If the same callsign is on two +different channel numbers, both will be shown and if two sources have +different callsigns with the same channel number, both of those will be +shown. + +Continuing with the example above, the Electronic Program Guide would +include rows for both "3 KVBC" and "733 KVBC". If channel 3 KVBC was also +included in the Digital cable source, the EPG would still include just one +line for "3 KVBC" even though there are two different channels, Cable and +Digital, with this identification. Regardless of how these are displayed and +which "KVBC" channel you select to add a rule to record "The Apprentice", +the scheduler will pick the best channel, source and input to record "The +Apprentice" on "KVBC". + +<sect2>Using Priorities to Prefer an Input +<p> +The fundamental concept to keep in mind is that the MythTV scheduler will +choose the lowest numbered input available when showings have the same +priority. If there are factors that cause two showings of the same show to +have different priorities then the higher priority showing will be +considered before the showings with lower priority. + +<sect2>Input Priority +<p> +"Input Connections" in mythtv-setup includes a box to set "Input priority" +which defaults to "0". If a value is set, that amount will be added to the +"total priority" for showings on that input. This can be used to influence +using favored cards or not using less favored cards unless necessary. + +Let's say the "The Apprentice" is on at 8:00pm with a priority of 3. "Who +Cares" is -2 and an episode is shown at 8:00pm then repeated at 11:00pm. The +scheduler would assign "The Apprentice" to card 1 and "Who Cares" to card 2 +at 8:00pm. If the input priority for the input on card 2 was changed to -1, +"Who Cares" would have a total priority of -2 for showings on card 1 and -3 +for showings on card 2. The scheduler would assign "The Apprentice" to card +1 at 8:00pm and "Who Cares" to card 1 at 11:00pm when the better card is +available. If there was another higher priority show at 11pm, the next best +choice for "Who Cares" would be card 2 at 8pm with the priority -3. + +Card 1 and 2 have input priority "0": + +<figure loc="here"> +<eps file="Card1 Pri 0 Card2 Pri 0.eps" height="1cm"> +<img src="Card1 Pri 0 Card2 Pri 0.png"> +<caption> +</caption> +</figure> + +<tscreen><verb> + Time Title Priority Card Status + 8:00 The Apprentice +3 1 Will Record + 8:00 Who Cares -2 2 Will Record +11:00 Who Cares -2 1 Earlier Showing +</verb></tscreen> + +Card 2 with input priority "-1": + +<figure loc="here"> +<eps file="Card1 Pri 0 Card2 Pri -1.eps" height="1cm"> +<img src="Card1 Pri 0 Card2 Pri -1.png"> +<caption> +</caption> +</figure> + +<tscreen><verb> + Time Title Priority Card Status + 8:00 The Apprentice +3 1 Will Record + 8:00 Who Cares -3 2 Later Showing +11:00 Who Cares -2 1 Will Record +</verb></tscreen> + +Card 2 at "-1" but higher priority shows at both 8 P.M. and 11 P.M.: + +<figure loc="here"> +<eps file="Card1 Pri 0 Card2 Pri -1-TDS.eps" height="1cm"> +<img src="Card1 Pri 0 Card2 Pri -1-TDS.png"> +<caption> +</caption> +</figure> + +<tscreen><verb> + Time Title Priority Card Status + 8:00 The Apprentice +3 1 Will Record + 8:00 Who Cares -3 2 Will Record +11:00 The Daily Show +1 1 Will Record +11:00 Who Cares -3 2 Earlier Showing +</verb></tscreen> + +Note the two different effects, each of which may be what you desire +depending on circumstance. If input priorities are equal, shows will record +at the earliest time if any input is available. If input priorities differ, +shows may be postponed to a later time in order to record on the best input. + +<sect2>Channel Priority +<p> +Priority can be added for individual channels (remember, frequencies from a +video source, not stations). This can be used to tell the system that you +generally prefer the content of the station on a channel over the formats of +other stations. You may want to raise the priority for ESPN, SciFi, Comedy +Central or lower the priority for CSPAN, CourtTV, etc. If the same station +is on two different channels, you can use channel priority to have the same +effect for these channels as input priority would have for whole inputs. + +For example, say CNN is on analog channel 20 and there is an HD CNN on 750. +You may not want to tie up the HD input for news originating in standard +definition. Under TV Settings->Recording Priorities->Channel Priorities you +could set channel 750 to -1. The scheduler would then prefer to record CNN +shows on any analog channel 20 before considering using 750 only when there +are no analog inputs available. + +<sect2>Preferred Input +<p> +For an even finer grain of control, there is a per rule option to specify +which input should be preferred for showings that match the rule. By +default, this adds +2 to the priority for showings on the specified input. + +For illustration, let's say there will be a Space Shuttle launch on CNN that +will be broadcast in high definition. Adding a rule to record the launch +with priority "0" should default to channel 20 on input 2. Channel 750 would +have this at -1 due to the channel priority set in the previous example. If +on the recording options page for this rule, the "Scheduling Options" had +the input set to prefer the HD input on card 1, then the showing on channel +750 for this input would be increased in value by +2 for a total of +1 and +would be the best choice for this launch coverage. While this one rule +would prefer the HD input with channel 750, all other rules that match shows +on CNN would still prefer channel 20. + +Note that this will not work properly if the preferred input priority does +not out weigh differences in input and channel priorities. The value of the +priority boost when this option is chosen defaults to +2 but can be modified +in TV Settings->Recording Priorities->Set Recording Priorities. + +<sect2>HDTV Priority +<p> +In the preceeding fictious example, the Space Shuttle launch is broadcast in +high definition and a preferred input is selected to give preference to the +HD input. However, TV listings from zap2it.com through the DataDirect +service may allow this to work without having to use this per rule option. + +In Settings->Recording Priorities->Set Recording Priorities there is an +option for "HDTV Recording Priority". This value will be added automatically +if the listings for the show have the "hdtv" flag set. DataDirect will set +this flag for shows known to be broadcast in HDTV on HD channels. However, +the flag is not set for standard definition channels. This is another +example of the listings being different for the same station on a different +channel. If the HDTV priority is set to "+2", the shuttle launch would +automatically have a total priority of +1 so that channel 750 would be +preferred over channel 20 for this HDTV broadcast. + +Channel "750 CNN" at priority "-1" and HDTV broadcast priority at "+2": + +<figure loc="here"> +<eps file="Card1 HDTV Card2 Cable.eps" height="1cm"> +<img src="Card1 HDTV Card2 Cable.png"> +<caption> +</caption> +</figure> + +<sect2>Custom Priority <label id="Custom Priority"> +<p> +<figure loc="here"> +<eps file="add.eps" height="1cm"> +<img src="add.png"> +<caption> +New for MythTV 0.21</caption> +</figure> + +While Input, Channel, and HDTV Priority can be used for indicating a +preference for certain programs and inputs, there may be circumstances that +cannot be resolved easily with these standard features. MythTV version 0.21 +includes a feature for "power priority". The Custom Priority editor in +mythfrontend's "TV Settings" screen is similar to Custom Record, however, +Custom Priority allows you to create specialized power priority factors to +influence scheduling decisions. + +For example, the 'program.closecaptioned' flag can be used in a +similar way as the 'program.hdtv' flag. + +<tscreen><verb> +Priority Rule Name: Closed Captioned priority +Priority Value: 2 +program.closecaptioned > 0 +</verb></tscreen> + +This will raise the priority of shows marked with "CC" over those that are +not by applying the "Priority Value" whenever the SQL fragment evaluates to +true. If the expression evaluates to false for a showing, the "Priority +Value" is not applied. + +<tscreen><verb> +Priority Rule Name: Priority when shown once +Priority Value: 1 +program.first > 0 AND program.last > 0 +</verb></tscreen> + +The "first" and "last" flags for an episode will only be set for the +same showing when there is only one showing of that episode in the +current TV listings. This rule would raise the priority in these cases +so that these shows would have an advantage to record in their only +available time slot. + +<tscreen><verb> +Priority Rule Name: Input 1 signal quality +Priority Value: -1 +cardinput.cardinputid = 1 AND +channel.channum IN (3, 5, 39, 66) +</verb></tscreen> + +A common issue with two or more analog capture cards is that one of +the cards may have more interference on some channels than the same +channels on other cards. This example gives a disadvantage to the +channels in this list but only for the first input. Therefore, a show +on channel 39 would choose input 2 or 3 if possible but for channels +not in this list, input 1 is still the first choice. + +The Custom Priority editor includes many example fragments and complete +examples that can be used or you can create your own to suit your needs. + +<sect>MythPlugins. <label id="mythplugins_"> +<p>MythTV has a rich set of plugins available. Once you have downloaded +the tarball, untar it and run the <bf>configure</bf> script: + +<tscreen><verb> +$ tar -xjf mythplugins-0.21.tar.bz2 +$ cd mythplugins-0.21 +$ ./configure --help + +Usage: configure [options] +Options: [defaults in brackets after descriptions] +NB: all --enable-* options can be reversed with --disable-* + +Generic options: + --help print this message + --enable-all Enable all options + --enable-opengl enable OpenGL (Music and Gallery) [default=no] + +MythBrowser related options: + --enable-mythbrowser build the mythbrowser plugin [default=yes] + +MythDVD related options: + --enable-mythdvd build the mythdvd plugin [default=yes] + --enable-transcode enable DVD ripping and transcoding [default=no] + --enable-vcd enable VCD playing [default=no] + +MythGallery related options: + --enable-mythgallery build the mythgallery plugin [default=yes] + --enable-exif enable reading of EXIF headers [default=no] + +MythGame related options: + --enable-mythgame build the mythgame plugin [default=yes] + +MythMusic related options: + --enable-mythmusic build the mythmusic plugin [default=yes] + --enable-fftw enable fftw visualizers [default=no] + --enable-sdl use SDL for the synaesthesia output [default=no] + --enable-aac enable AAC/MP4 audio file decompression [default=no] + +MythNews related options: + --enable-mythnews build the mythnews plugin [default=yes] + +MythPhone related options: + --enable-mythphone build the mythphone plugin [default=yes] + --enable-festival enable festival TTS Engine [default=no] + +MythVideo related options: + --enable-mythvideo build the mythvideo plugin [default=yes] + +MythWeather related options: + --enable-mythweather build the mythweather plugin [default=yes] +</verb></tscreen> + +The sections detailing configuration of the plugins assume that you are +already in the <tt>~/mythplugins-0.21/</tt> directory. + +Note that a single <bf>configure</bf> script now does configuration for all +modules. By default, it will compile all modules. If you do not wish to +compile a module, either because it is of no use to you, or you do not have +the prerequisites, the simplest course of action is to go through the +various sections below, satisfying the prerequisites, and then compile all +modules at once. + +For example, you would only like to compile and install MythGallery and +MythMusic. For MythGallery, you would like to use the EXIF data in the .JPG +file to present additional information onscreen. For MythMusic, you would +like to enable support for the opengl and FFT visualizations. The command +line would look like: + +<tscreen><verb> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-opengl --enable-mythgallery --enable-exif --enable-mythmusic --enable-fft +$ qmake mythplugins.pro +$ make +$ su - +# make install +# exit +$ +</verb></tscreen> + +For simplicity, the examples below will disable compilation of all other +modules other than the one being discussed. + +<sect>MythWeb. +<p>MythWeb allows you to use a web page to control various aspects of your +MythTV system. MythWeb is a separate application, but it's dependent on +MythTV being installed and operational. + +<sect1>Installation and prerequisites + +<p>Mythweb is a part of the <bf>mythplugins</bf> package. See <ref +id="mythplugins_" name="MythPlugins"> for instructions on downloading the +tarball. The next step depends on whether your distribution has a web server +and if you have PHP support. + +<sect2>Mandriva +<p>Mandriva has <bf>apache</bf> and <bf>PHP</bf> pre-packaged, so +installation is quite simple. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: Mandriva 9.1 users, perform the following: +</caption> +</figure> +<tscreen><verb> +# urpmi apache2 apache2-mod_php php-mysql +# chkconfig --level 345 httpd on +# /etc/rc.d/init.d/httpd restart +</verb></tscreen> + +<sect1>Completing the installation +<p> +<tscreen><verb> +$ cd ~/mythplugins-0.21/mythweb +$ su +# mkdir /var/www/html/mythweb +# cp -r . /var/www/html/mythweb +# exit +$ +</verb></tscreen> + +By default, MythWeb uses an Apache <tt>.htaccess</tt> file to restrict +access to the website and to configure some variables. + +To create the password file for Apache (if your system doesn't already have +one), you could do something like this: +<tscreen><verb> +# cd /var/www +# htpasswd -c htpasswd mythtv +New password: +Re-type new password: +Adding password for user mythtv +</verb></tscreen> + +See the man page for <bf>htpasswd</bf> for more examples. + +To access the web page, open a web browser and use <bf>http://[name or ip +address]/mythweb/</bf> + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: Make sure that you have a trailing slash on the URL, +otherwise you will get a <tt>404 Page not Found</tt> error. +</caption> +</figure> +<sect1>Resetting the key binding table +<p>MythWeb allows you to configure which keys are bound to which actions +within MythTV. If you'd like to reset this back to the default, execute the +following command: +<tscreen><verb> +$ echo "delete from keybindings ;" | mysql -u mythtv -pmythtv mythconverg +</verb></tscreen> +<sect1>Resetting the theme. +<p>If you find yourself wedged into a theme that isn't working, open your +web browser and go to site: +<tt>http://mythweb_name_or_ip_address/mythweb/settings.php?RESET_THEME=yes</tt> +<sect>MythGallery. +<p>MythGallery is a photo and slideshow application. MythGallery is a +separate application, but it's dependent on MythTV being installed and +operational. +<sect1>Installation and prerequisites + +<p>MythGallery is a part of the <bf>mythplugins</bf> package. See <ref +id="mythplugins_" name="MythPlugins"> for instructions on downloading the +tarball. + +There are a number of transitions available, some requiring OpenGL +support. You will also need to install a TIFF library. Under Mandriva, you +would perform the following command: +<tscreen><verb> +# urpmi libtiff3-devel +</verb></tscreen> +Once you have satisfied the prerequisites for your distribution, install the application: +<tscreen><verb> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-opengl --enable-mythgallery +$ qmake mythplugins.pro +$ make +# su +# make install +# exit +$ +</verb></tscreen> +The configuration for MythGallery is accessed through the main Setup option +in mythfrontend. Make sure you set your pictures directory to wherever +you're storing your photos. + +The controls for MythGallery can be found in the README that comes with the +application. +<sect1>Using MythGallery +<p>When you first start MythGallery, you will see a thumbnail view of any +folders and pictures in the Gallery Directory you specified in setup. If +this is the first time you have accessed this directory, the thumbnails will +be generated on the fly. If the Gallery Dir is writable, these thumbnails +will be cached thus speeding up future access. On the left is a greyed-out +menu of options. + +Use the arrow keys to select a folder or picture to open/view with the +Select key, or use the Menu key to toggle access the menu on the left. The +menu options are as follows: +<itemize> +<item> Slideshow - Will cycle through all the pictures in the current folder. +The currently selected item must be a picture (not a folder) for this to +work. It does not currently traverse subfolders. +<item> Rotate CW - Rotate the current image 90 degrees in the clockwise +direction. This change persists if the current directory is writable. +<item> Rotate CCW - As above except the direction of rotation is counter(anti) +clockwise. +<item> Import - Import pictures into your Gallery Dir. This option is +described in the next section. +<item> Settings - Access the MythGallery settings screen. +</itemize> +<sect1>Importing Pictures +<p>The import path in the setup dialog is a colon separated list of +directories and/or executable files. When the import key is pressed, a new +directory (the destination directory) under the current directory will be +created and the import path will be searched. If the item in the import +path is a directory (the source directory), the contents of that directory +will be copied to the destination directory. If you would like the source +directory to be that of a removable device, it might be a good idea to use +autofs. See the automount howto at <url url="www.linuxdoc.org" +name="www.linuxdoc.org"> for info on how to get it working. + +If the item in the import path is an executable file, MythGallery will +attempt to execute it with the destination directory as its sole argument. +Be careful when using executable scripts that the script runs unattended +(doesn't need user intervention) and returns properly, otherwise it could +create the appearance of MythGallery hanging (e.g. running +<bf>smbclient</bf> and prompting for password). Also be sure that scripts +have executable permissions set. + +Here is an example script that a user may want to run +on import: +<tscreen><verb> +#!/bin/csh + +if ($#argv == 0) then + echo "Usage: $0 dest_dir" + exit +endif + +cd $argv[1] + +# get stuff over the network +wget http://www.somesite.dom/dir/file1.jpg +wget http://www.somesite.dom/dir/file2.jpg +wget http://www.somesite.dom/dir/file3.jpg + +# stuff that requires manual module loading and/or fs mounting +modprobe camera_module +mount /dev/camera /mnt/camera +cp /mnt/camera/* $argv[1] +umount /mnt/camera +rmmod camera_module + +# perform some processing +foreach pname (`ls *.jpg`) + jpegtran -flip vertical $pname > $pname.new + mv $pname.new $pname +end +</verb></tscreen> + +<sect>MythGame. +<!-- Install instructions by Hary Wilke (harywilke at yahoo.com --> +<p>MythGame can used as a frontend to start any emulator that your host OS +runs. This is an example of how to set up xmame on Linux. +<url url="http://www.mameworld.net/" name="http://www.mameworld.net/"> is +an excellent resource for all things mame. + +Installation overview: +<enum> +<item>Setup directory structure +<item>Download and install xmame +<item>Download and place extra files (artwork/catver.ini/etc..) +<item>Download and install MythGame plugin +<item>Setup xmame in MythGame +<item>Hints +</enum> +<sect1>Setup Directory Structure +<p>To keep things organized, create the following directories for <bf>xmame</bf> to use +in <tt>/usr/local/share/xmame</tt>: hiscore, roms, and snaps. + +<tscreen><verb> +$ mkdir -p /usr/local/share/xmame/{highscore,roms,snaps} +</verb></tscreen> + +<sect1>Download and Install xmame +<p><bf>NOTE</bf>: There may be pre-packaged versions of <bf>xmame</bf> +available for your distribution. Check <url +url="http://x.mame.net/download.html" +name="http://x.mame.net/download.html"> for the latest version. + +Download the source to <bf>xmame</bf> from <url +url="http://x.mame.net/download/xmame-0.103.tar.bz2" +name="http://x.mame.net/download/xmame-0.103.tar.bz2"> + +<tscreen><verb> +$ wget http://x.mame.net/download/xmame-0.103.tar.bz2 +$ tar -xjf xmame-0.103.tar.bz2 +$ cd xmame-0.103 +</verb></tscreen> + +Edit the Makefile with your favorite editor. Adjust the options as required for your system. +<tscreen><verb> +$ joe Makefile +</verb></tscreen> + +Then make and install xmame +<tscreen><verb> +$ make +$ su +(enter password) +# make install +# exit +</verb></tscreen> + +After <bf>mame</bf> has been installed, we need to create some defaults. +<tscreen><verb> +$ mkdir ~/.xmame +$ cp docs/xmamerc.dist ~/.xmame/xmamerc +</verb></tscreen> + +Because some ROMS work better with different display toolkits, or possibly +even older versions of xmame, it's convenient to keep all of your +<bf>xmame</bf> binaries and to rename them to include the version number. +MythGame allows you to match individual roms to preferred binaries. + +<tscreen><verb> +$ su +(enter password) +# mv /usr/local/bin/xmame.x11 /usr/local/bin/xmame-0.103.x11 +# exit +</verb></tscreen> + +<bf>NOTE</bf>: Depending on how you compiled <bf>xmame</bf>, you may have +<bf>xmame.X11</bf>, <bf>xmame.SDL</bf> or <bf>xmame.xgl</bf> based on what +display toolkit you used. Also, you may need to remove and recreate +<tt>xmamerc</tt> after upgrading since some of the default options may have +changed. + +Edit <tt>~/.xmame/xmamerc</tt> to include your paths. +<tscreen><verb> +### Fileio Related ### +rompath /usr/local/share/xmame/roms +snapshot_directory /usr/local/share/xmame/snaps +cheat_file /usr/local/share/xmame/cheat.dat +hiscore_file /usr/local/share/xmame/hiscore.dat +hiscore_directory /usr/local/share/xmame/hiscore +history_file /usr/local/share/xmame/history.dat +mameinfo_file /usr/local/share/xmame/mameinfo.dat +</verb></tscreen> + +Confirm that <bf>xmame</bf> works before running it inside MythTV. Place +your ROM in the <tt>/usr/local/share/xmame/roms</tt> directory you created +earlier. + +<bf>NOTE</bf>: There are three public domain ROM sets available at +<url url="http://www.mame.net/downmisc.html" name="http://www.mame.net/downmisc.html"> + +Launch <bf>xmame</bf> with your game of choice. In this example, we are using Gauntlet. +<tscreen><verb> +$ xmame gauntlet +</verb></tscreen> + +Some basic <bf>mame</bf> keyboard commands: +<tscreen><verb> +5 = Insert coin +1 = Player 1 start +arrow keys = movement +left control = button 1 +left alt = button 2 +SPACE = button 3 +ESC = exit +TAB - menu +~ to adjust Volume + < and > +</verb></tscreen> + +<sect1>Download extra files +<p>The following files allow you to add extra functionality. Place them +into <tt>/usr/local/share/xmame</tt> + +- <tt>catver.ini</tt> is a catalog of categories and versions of popular mame ROMs. +<p>Useful for keeping large libraries of ROMs organized. + +It may be downloaded from <url url="http://www.catver.com" +name="http://www.catver.com"> or <url url="http://www.mameworld.net/catlist" +name="http://www.mameworld.net/catlist"> + +- Screenshots aka "snaps" +<p>These may be downloaded from <url +url="http://www.classicgaming.com/mame32qa/" +name="http://www.classicgaming.com/mame32qa/"> + +Screenshots are displayed when you are browsing your ROMS in <bf>mythgame</bf>. +Unzip and place them in <tt>/usr/local/share/xmame/snaps</tt> + +- <tt>history.dat</tt> +<p>Download from <url url="http://www.arcade-history.com/" +name="http://www.arcade-history.com/"> +This file fills in a bit of background about each ROM. + +- <tt>hiscore.dat</tt> +<p>Download from <url url="http://www.mameworld.net/highscore/" +name="http://www.mameworld.net/highscore/"> + +- Cheats +<p>Download from <url url="http://cheat.retrogames.com/" +name="http://cheat.retrogames.com/"> + +<sect1>Download and Install MythGame. +<p><bf>MythGame</bf> is part of the mythplugins package. See the instructions +in the <ref id="DownloadAndCompile" name="Downloading and Compiling"> +section to obtain mythplugins. + +Switch to the mythplugins directory: +<tscreen><verb> +$ cd ~/mythplugins-0.21 +</verb></tscreen> + +Compile and install mythgame: +<tscreen><verb> +$ ./configure --disable-all --enable-mythgame +$ qmake mythplugins.pro +$ make +$ su +(enter password) +# make install +# exit +</verb></tscreen> + +<sect1>Setup xmame in MythGame +<p>Start <bf>mythfrontend</bf> and navigate to Utilities/Setup > Setup > Media +Settings > Game Settings > Game Players. Select <tt>(New Game Player)</tt>. + +To set up a new player for xmame enter the following: + +<tscreen><verb> +Player Name: xmame-0.103.x11 (Name by which you want your emulator or game called) +Type: xmame (This is used for display purposes only and does not affect the function of your system) +Command: xmame-0.103.x11 -vidmod 1 -fullscreen (Path and name of binary + any optional parameters) +Rom Path: /usr/local/share/xmame/roms (This tells MythGame what directories to scan for roms to be used with this emulator) +ScreenShots: /usr/local/share/xmame/snaps (This tells MythGame what directories to scan for snapshots to be used with these roms) +Working Directory: (Directory to change to before launching game or emulator. Blank in our case ignores this setting) +File Extensions: (List of all file extension to be used for this emulator. Blank menas any file under the Rom Path) +[] Allow games to span multiple roms/disks (will treat game.1.rom game.2.rom game.3.rom as one game) +</verb></tscreen> + +<sect1>Hints: +<p> +<itemize> +<item>Rom name before options: %s can be used as a standin for rom names on the command line. +<item>Multiple disk/rom games: %d1 %d2 etc can be used as standins for multiple disc games on the command line. +<item>Associating a rom with an emulator: Browse to the desired rom and press 'M' to enter the settings page for that rom. +<item>Assign a Game Favorite Status: Browse to the desired game and press "/". +</itemize> + +<sect>MythMusic. +<p>MythMusic has a number of prerequisites that must be satisfied before it +is operational. Depending on your distribution, some of these prerequisites can +be satisfied through the various package managers. If your distribution doesn't +offer pre-compiled versions of the software below, then follow the generic +instructions for manually compiling and installing the software. + +The prerequisites for MythMusic are: +<itemize> +<item>MAD +<item>taglib +<item>libogg and libvorbis +<item>FLAC +<item>libcdaudio +<item>CDParanoia +</itemize> + +<sect1>Manual installation of prerequisites +<p>These instructions are for distributions which don't have pre-compiled +versions of the software necessary to run MythTV. + +Download MAD from <url url="http://www.underbit.com/products/mad" +name="http://www.underbit.com/products/mad"> and install: + +<tscreen><verb> +$ tar -xzf mad-0.15.1b.tar.gz +$ cd mad-0.15.1b +$ ./configure +$ make +$ su +# make install +# exit +</verb></tscreen> + +Download TagLib from <url url="http://developer.kde.org/~wheeler/taglib.html" +name="http://developer.kde.org/~wheeler/taglib.html"> and install: + +<tscreen><verb> +$ tar -xzf taglib-1.4.tar.gz +$ cd taglib-1.4 +$ ./configure +$ make +$ su +# make install +# exit +</verb></tscreen> + +Download libogg and libvorbis from <url url="http://www.xiph.org/downloads" +name="http://www.xiph.org/downloads"> and install in a similar manner +to the above packages. + +Download FLAC from <url url="http://flac.sourceforge.net" +name="http://flac.sourceforge.net"> and install: +<tscreen><verb> +$ tar -xzf flac-1.1.2.tar.gz +$ cd flac-1.1.2 +$ ./configure +$ make +$ su +# make install +# exit +$ +</verb></tscreen> + +Download libcdaudio from <url name="http://libcdaudio.sourceforge.net" +url="http://sourceforge.net/project/showfiles.php?group_id=27134"> and +install: +<tscreen><verb> +$ tar -xzf libcdaudio-0.99.12p2.tar.gz +$ cd libcdaudio-0.99.12p2 +$ ./configure +$ make +$ su +# make install +# exit +$ +</verb></tscreen> + +Download cdparanoia from <url name="http://www.xiph.org/paranoia/down.html" +url="http://www.xiph.org/paranoia/download/cdparanoia-III-alpha9.8.src.tgz">. +<tscreen><verb> +$ tar -xzf cdparanoia-III-alpha9.8.src.tgz +$ cd cdparanoia-III-alpha9.8 +$ ./configure +$ make +$ su +# make install +# cd /usr/lib +# ln -sf libcdda_interface.so.0.9.8 libcdda_interface.so +# ln -sf libcdda_paranoia.so.0.9.8 libcdda_paranoia.so +# exit +$ +</verb></tscreen> + +<sect1>Mandriva +<p>Mandriva has a number of the prerequisites available on the +installation CD. Some of the software you're going to need will have to be +obtained from the "contrib" or "cooker" development repositories. +Applications downloaded from "cooker" come from the development branch, so +there may be issues with some software. It isn't recommended that you mix +cooker and release-level software. + +<p><bf>urpmi</bf> is the simplest tool for installation of packages from the +command line. The difficult part is the configuration, but this has been +made easier at the following website: <url +url="http://addmedia.linuxfornewbies.org/" +name="http://addmedia.linuxfornewbies.org/"> The website will allow +you to choose a mirror site and then present the command-line configuration +text for that mirror. You will most likely need to add a "Contrib" mirror +to your setup. Once you have done that, you can proceed. If <bf>urpmi</bf> +prompts you about other modules that need to be installed to satisfy +dependencies, say "Yes". + +<tscreen><verb> +# urpmi libmad0 libmad0-devel libflac4 libflac4-devel libcdaudio1 cdparanoia +# urpmi libcdda0 libcdda0-devel libvorbis0 libvorbis0-devel +# urpmi libcdaudio1-devel libid3tag0 libid3tag0-devel +</verb></tscreen> + +<sect2>Additional options with MythMusic +<p>Additional visualizations have been added to MythMusic. If you wish to +use these, there are some prerequisites you must install prior to compiling. + +<itemize> +<item>fftw +<item>OpenGL +<item>SDL +</itemize> + +<tt>fftw</tt> may be obtained from <url url="http://www.fftw.org/" +name="http://www.fftw.org/">. In Mandriva it may be installed by +typing: +<tscreen><verb> +# urpmi libfftw2 libfftw2-devel +</verb></tscreen> + +<tt>OpenGL</tt> should be installed on practically all distributions. +However, you will need the devel module. In Mandriva it may be +installed by typing: +<tscreen><verb> +# urpmi libMesaGLU1-devel +</verb></tscreen> + +<tt>SDL</tt> may be obtained from <url url="http://www.libsdl.org" +name="http://www.libsdl.org">. In Mandriva it may be installed by +typing: +<tscreen><verb> +# urpmi libSDL1.2 libSDL1.2-devel +</verb></tscreen> + +<sect1>Red Hat Linux 9 +<p>Red Hat provides packages for several of the prerequisites, making +installation very simple. Of the prerequisites, Red Hat provides +packages for Vorbis, cdparanoia, SDL, and OpenGL (which you probably +already have installed). To install these all at once, simply type (all on +the same line): +<tscreen><verb> +$ up2date --solvedeps libvorbis libvorbis-devel vorbis-tools cdparanoia-devel cdparanoia-libs cdparanoia SDL-devel SDL +</verb></tscreen> + +If you get the following message: "None of the packages you requested +were found, or they are already updated" it probably means you already +have all of those packages installed. + +You must install the remaining packages, (MAD, FLAC, libcdaudio and +optionally fftw) manually following the installation directions above. When +installing fftw do not use the rpm package offered on the website because it +will cause an error, so use the source package instead. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: you can use the instructions given at the <ref id="atrpms" +name="automated installation section"> to install all of MythMusic in one +step. +</caption> +</figure> +<sect1>Compiling MythMusic +<p>Once all the prerequisites have been installed, you can proceed with +compiling MythMusic. + +<tscreen><verb> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-mythmusic --enable-fftw --enable-sdl --enable-aac +$ qmake mythplugins.pro +$ make +$ su +# make install +# exit +</verb></tscreen> + +<sect1>Configuring MythMusic +<p>Configuration of MythMusic occurs in two places. The main mythfrontend +Setup is for global MythMusic configuration. Go to the +Setup/MythMusic/General Setup screen and adjust it for your particular +configuration. + +The second configuration screen is within the MythMusic program and will +allow you rescan your music library, etc. + +Here's some explanation about the Ignore_ID3 and The NonID3FileNameFormat: + +If Ignore_ID3 is set to TRUE, MythMusic will try to determine the +Genre, Artist, Album, Track Number, and Title from the filename of the +mp3 file. The NonID3FileNameFormat variable should be set to the +directory/file format where the mp3 files are stored. For instance, I +store mine in the above shown Genre/Artist/Album/Track format. MythMusic +will then use this information to fill in the proper fields when it +populates the musicmetadata table rather than searching for an ID3 tag in +the mp3 file. + +The files can be laid out in any format, such as: + +Genre/Artist/Album/Title +Artist/Genre/Album/Title +Artist/Album/Title (with Genre left as Unknown) + +The track number is optional but can be specified with the title by using +the TRACK_TITLE keyword instead of TITLE. If TRACK_TITLE is used, +then the filename can have a space, hyphen, or underscore separating the +track number from the track title. Keywords are case insensitive, so if +you specify GENRE it's the same as Genre in the format field. + +The Ignore_ID3 option does not disable the code that determines the track +length, just the portion that tries to read ID3 info. + +<sect1>Using MythMusic +<p>MythMusic is fairly simple to use. It is recommended that you insert the +CD before selecting "Import CD". You should also ensure that your system +doesn't try to automount the CD and begin playing it automatically. + +<!-- +Next stuff is from a message by jasonmiller [jasonmiller@micron.com] +with additional comments by Thor +--> +Here's some information on playlist management: + +Q: How do I create a new playlist? +A: Using the MythMusic "Select Music" menu option, setup the playlist as you +normally would by adding songs or other playlists as needed. When you are +ready to save the new playlist, highlight "Active Play Queue" at the bottom +of the selection tree and hit the "i" key. This will pop up a menu allowing +you to name and save the new playlist. You can also hit Enter to bring up +the popup on the Active Play Queue. This does not work on the playlists +above, as Enter is obviously bound to checking/unchecking the boxes. Any +number (i.e. keypad on remote) will also bring up the menu in both cases. + +Q: How do I enter the playlist name in the text field without a keyboard? +A: Use the keypad number keys (bound to your remote) to select letters +quasi-cell phone style. Keys 2-9 work pretty much like any cell phone text +entry. 1 cycles through a few special characters, delete, and space. 0 is +like a CAPS LOCK. Hard to describe, fairly easy to use. You will soon be +able to specify the cycle timing in a Setup screen. You can type fairly +quickly through a combination of jumping around the number keys AND hitting +a non-number key (right arrow is particularly good for this) to force the +current character. + +Q: How do I edit a playlist? +A: Highlight the playlist in the selection tree and hit the "i" key then +select "Move to Active Play Queue" in the popup. You can now modify the +"Active Play Queue" like normal, adding songs and playlists by selecting +them from the song tree. When you are done, highlight the "Active Play +Queue" in the selection tree and hit the "i" key then select "Save Back to +Playlist Tree". And whatever you were editing as your Active Queue before +you moved an existing playlist "on top" of Active reappears. Think of Active +has having a push on, pop off capability, but with a depth of only 1. + +Q: How do I delete an item from a playlist? +A: Highlight the item in the selection tree and hit the "d" key. + +Q: How do I rearrange the songs in my playlist? +A: Highlight a song and hit the "space" bar, the song will now have pair of +red arrows in front of it. Use the up and down arrow keys to move it around +in the playlist. When you have it where you want it, hit the "space" bar +again. + +Q: How do I delete a playlist? +A: Highlight the playlist in the selection tree and hit the "i" key then +select "Delete this Playlist" from the popup. + +<sect1>Troubleshooting MythMusic +<p>You may run into errors when running MythMusic. +<sect2>When I run MythMusic and try and look up a CD, I get an error message +<p>The full text of the message will say: + +databasebox.o: Couldn't find your CD. It may not be in the freedb database. +More likely, however, is that you need to delete ~/.cddb and ~/.cdserverrc +and restart mythmusic. Have a nice day. + +If you get this message, you should go to the home directory of whatever +user MythMusic is running as and type: +<tscreen><verb> +rm .cdserverrc +rm -rf .cddb/ +</verb></tscreen> + +These files aren't automatically deleted because of a conscious design +decision by the author that programs that automatically delete things are +bad. + +The files are used to locally cache CD lookups. If you are re-inserting +CDs, your machine will not actually have to go out to the Internet to +determine what is on them. However, the URL used to access the freedb +database has recently changed, so the stale information in the files from +previous runs of MythMusic would cause the error above. Once the files have +been deleted the stale information will be gone and your local database +will be rebuilt as you use CDs. + +<sect>MythWeather. +<p> +MythWeather is a part of the <bf>mythplugins</bf> package. See <ref +id="mythplugins_" name="MythPlugins"> for instructions on downloading the +tarball. + +<tscreen><verb> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-mythweather +$ qmake mythplugins.pro +$ make +$ su +# make install +# exit +</verb></tscreen> + +MythWeather uses MSNBC.com as its source for weather data and weather.com +for its radar image. + +These are the keyboard commands for MythWeather: +<tscreen><verb> +Left Key Goes back one page, and extends the time spent + on the page you are on. +Right Key Goes forward one page, see above. +Space Pause, wait on the current page until space is hit + again. +Numeric Keys You can check other weather by keying in other ZIP codes. +Enter Key Switch between Celsius and Fahrenheit. Can also + be used a way to force a data update. +"m" Key Resets the location to the database default, then updates the data. +"i" Enter / Save settings +ESC Exit the settings screen without saving / Exit the program +</verb></tscreen> + +MythWeather also has an "Aggressiveness" setting. This affects how long +MythWeather waits for data from the msnbc.com website before timing out. If +you are on a slow connection, or have a slow DNS, or MythWeather just +doesn't seem to be working and you've already tried everything else, then +try increasing the aggressiveness level parameter. This parameter is +inverse; a higher number actually means that MythWeather will be less +aggressive, and will therefore wait longer before timing out. + +MythWeather will print debugging information on the terminal. If you wish +to see additional debugging information while MythWeather is running, run +mythweather from the command line with as <tt>mythweather --debug</tt> + +You may also force mythweather to re-run the configuration by starting it on +the command line as <tt>mythweather --configure</tt>. These two options are +mutually exclusive. + +<sect>MythVideo. +<p>MythVideo is a part of the <bf>mythplugins</bf> package. See <ref +id="mythplugins_" name="MythPlugins"> for instructions on downloading the +tarball. + +MythVideo will allow you to use an external program to watch media files +that are not directly supported by MythTV. + +<tscreen><verb> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-mythvideo +$ qmake mythplugins.pro +$ make +$ su +# make install +# exit +</verb></tscreen> + +See MythVideo's <tt>README</tt> file for additional information. + +<sect>MythDVD. +<p>MythDVD is a part of the <bf>mythplugins</bf> package. See <ref +id="mythplugins_" name="MythPlugins"> for instructions on downloading the +tarball. MythDVD is an application which rips DVDs and makes them available for +use with MythVideo. You may also transcode the DVD content from MPEG-2 to +other formats which should greatly reduce the amount of space the DVD +material takes up on your hard drive. + +MythDVD has a number of prerequisites to enable transcoding functionality. +If you only wish to play DVDs rather than convert them to something like +MPEG-4 or xvid you may skip the prerequisite installation step. + +<sect1>Manual Compilation of Prerequisites +<p> +<sect1>Pre-compiled binaries +<p>Mandriva users may install the prerequisites this way: +<tscreen><verb> +# urpmi libdvdread3 libdvdread3-devel a52dec liba52dec-devel +# urpmi mplayer ogle xine +</verb></tscreen> +Assuming that you've added a PLF mirror, you may also load the rest of the +prerequisites using the following command: +<tscreen><verb> +# urpmi xvid xvid-devel fame libfame0.9-devel transcode libdvdcss +</verb></tscreen> + +In the example below, we have enabled support for transcoding and for VCD +playing. You may remove these options if you don't need them. +<tscreen><verb> +$ cd ~/mythplugins-0.20 +$ ./configure --disable-all --enable-mythdvd --enable-transcode --enable-vcd +$ qmake mythplugins.pro +$ make +$ su +# make install +</verb></tscreen> +<sect1>Running the Myth Transcoding Daemon +<p>Transcoding ("ripping") a DVD requires you to run the Myth Transcoding +Daemon (mtd). To ensure that mtd is configured correctly, you should first +test it at the command line. +<tscreen><verb> +$ mtd -n +</verb></tscreen> +The last line of text should show something like: +<tscreen><verb> +mtd is listening on port 2342 +</verb></tscreen> +This indicates that mtd is ready for use. Once you've successfully +tested mtd in the foreground, type <bf>CTRL-C</bf> to stop mtd. You may +then start it as a background (daemon) process. +<tscreen><verb> +$ mtd -d +</verb></tscreen> + +Running mtd as a daemon will allow you to automatically start it during the +boot process. For example, you may add <tt>mtd -d</tt> to your +<tt>rc.local</tt> file, or you can adjust the script/steps outlined in the +section called <ref id="mythbackend_autostart" name="Automatically starting +mythbackend at system boot time"> to start mtd instead of mythbackend. + +<sect>MythNews. +<p>MythNews is a part of the <bf>mythplugins</bf> package. See <ref +id="mythplugins_" name="MythPlugins"> for instructions on downloading the +tarball. MythNews is a RSS reader. +<tscreen><verb> +$ cd ~/mythplugins-0.21 +$ ./configure --disable-all --enable-mythnews +$ qmake mythplugins.pro +$ make +$ su +# make install +</verb></tscreen> + +<sect>Troubleshooting. +<sect1>Compiling +<sect2>Compile errors +<p>Some compile errors are worse than others. If you get an error that +doesn't abort the compilation, and says something like: +<tscreen><verb> +cc1plus: warning: changing search order for system directory +"/usr/local/include" +cc1plus: warning: as it has already been specified as a non-system +directory +</verb></tscreen> +then it shouldn't be a problem. + +If you get an error like <tt>/usr/bin/ld: cannot find -lXext</tt>, the +compiler is telling you that you don't have XFree86-devel installed, or that +your distribution hasn't set it up correctly. This needs to be fixed before +MythTV will compile. + +<sect2>make: *** No rule to make target /usr/lib/qt3/mkspecs/default/qmake.conf', needed by Makefile'. Stop. +<label id="mkspecs_error"> +<p>This error happens when there's a missing link in the +<tt>/usr/lib/qt3/mkspecs</tt> directory. There are two ways to fix this +error: + +1. Create the link manually: +<tscreen><verb> +$ su +# cd /usr/lib/qt3/mkspecs +# ln -sf linux-g++ default +</verb></tscreen> +and then restart the compile, + +or + +2. Run <bf>qmake mythtv.pro</bf> in the mythtv directory. Rerunning +<bf>qmake</bf> will create a new Makefile for you, however this still +doesn't fix the root cause of the issue, which is that your distribution +didn't create the symlink for you when the qt3 package was installed. The +first choice is the better solution. + +<sect2>make: *** No rule to make target /mkspecs/default/qmake.conf', needed by Makefile'. Stop. +<p>You didn't set your <tt>QTDIR</tt>. Re-read the section on <ref +id="Setting_up_paths" name="Setting up paths">. + +<sect2>Internal Segmentation Fault. +<p>This is most likely to be caused by an overheating processor rather than +an actual programming fault within gcc. + +<sect1>Debugging <label id="debugging"> +<sect2>MythTV segfaults +<sect2>MythTV isn't doing anything +<sect2>Debugging with GDB +<p>Without details, the developers will not be able to determine if you have +discovered a genuine code-bug, or if the problem is with your system. In +order to determine what's going on, you must recompile MythTV with debugging +support and run MythTV within <bf>gdb</bf>, the GNU debugger. +Note that, on OS X, some data is provided without going through these steps. +See ~/Library/Logs/CrashReporter/MythFrontend.crash.log + +Re-run the <bf>configure</bf> script and add <tt>--compile-type=debug</tt> +to any previous configuration options you may have used. Check the +<tt>config.log</tt> file if you have forgotten. + +Now, you need to clear out the old versions of the software to ensure that +you're running with the debugging code, then compile and install. +<tscreen><verb> +$ make distclean +$ ./configure --compile-type=debug +$ make +$ su +# make install +# exit +</verb></tscreen> + +At this point, you now have debug-enabled software ready. To make sure that +you don't forget to type a command required for debugging, it's best to +setup a <tt>gdbcommands</tt> file. This will be read by <bf>gdb</bf> when it's +started. +Put the following into <tt>gdbcommands</tt> in your home directory: + +<tscreen><verb> +handle SIGPIPE nostop noprint +handle SIG33 nostop noprint +set logging on +set pagination off +set args -l myth.log -v record,channel,siparser +run +thread apply all bt full +set logging off +</verb></tscreen> + +Let's assume that the problem you're having is in <bf>mythbackend</bf>. + +<tscreen><verb> +$ gdb mythbackend -x gdbcommands +GNU gdb 6.3-debian +Copyright 2004 Free Software Foundation, Inc. +GDB is free software, covered by the GNU General Public License, and you are +welcome to change it and/or distribute copies of it under certain conditions. +Type "show copying" to see the conditions. +There is absolutely no warranty for GDB. Type "show warranty" for details. +This GDB was configured as "i386-linux".Using host libthread_db library "/lib/tls/libthread_db.so.1". +[Thread debugging using libthread_db enabled] +</verb></tscreen> + +<bf>gdb</bf> will automatically read the commands that you've placed in the +<tt>gdbcommands</tt> file and begin running the program you specified on the +command line. + +If the program appears to be locked up, press CTRL-C to create the backtrace +file. + +All of the output from <tt>gdb.txt</tt> should be posted to the mythtv-dev +mailing list, along with the steps you followed to get the program to crash. + +<bf>NOTE</bf>: If you're trimming the <tt>gdb.txt</tt> file to remove +extraneous information from the beginning of the file, make sure you include +at least 10 lines <em>prior</em> to the point where the backtrace actually +begins. This ensures that there is some context to the backtrace, and so +that it's possible to see what exactly caused the segfault. + +<bf>gdb</bf> has a number of options, read the <tt>man</tt> page for more +information. + +Using the <tt>gdbcommands</tt> file in conjunction with a <bf>while</bf> loop +will ensure that <bf>gdb</bf> creates a trace file and then restarts: + +<tscreen><verb> +$ while true; do date >> gdb.txt; gdb mythbackend -x gdbcommands; done; +</verb></tscreen> + +<bf>NOTE</bf>: To exit this loop you will need to kill the while loop. + +If you're trying to troubleshoot and you can't get back to the <bf>gdb</bf> window +for some reason, it may be easier to use two systems or to start +mythfrontend from the text console. + +If you're going to troubleshoot from a remote system, connect to the machine +that you're going to test using <bf/ssh</> or <bf>telnet</bf>. Next, type +<tt>$ export DISPLAY=localhost:0.0</tt>. This will allow the graphics to be +displayed on the X console (usually ALT-F6 or ALT-F7) and still give you +output and control of <bf>mythfrontend</bf>, either from the <bf>ssh</bf> +session, or by switching back to the text console by pressing CTRL-ALT-F1. +You can now continue troubleshooting using <bf>gdb</bf> as detailed in the +instructions. + +<sect2>MythTV is crashing your system +<p>When run as a non-privileged user, MythTV <em>can not</em> crash your +system. If your system is crashing when you run MythTV, then you have some +issue with the drivers for your capture card or other hardware, or the CPU +fan has fallen off/broken and your system is overheating when asked to +perform a CPU intensive task like encoding video. + +If you are running as root, which is <bf>strongly discouraged</bf>, it is +possible that your system may crash due to the real-time thread using all +available CPU. You will not be able to interrupt the process, so for all +intents and purposes your computer will have crashed. + +<sect1>Installing +<sect2>When trying to run mythtv-setup, you get an error like this: +"mythtv-setup: error while loading shared libraries:" +<p>You didn't add <tt>/usr/local/lib</tt> to <tt>/etc/ld.so.conf</tt>. See the +section on modifying <ref id="modifying_ld.so.conf" name="/etc/ld.so.conf">. + +<sect1>Using +<sect2>No programs are displayed in "Watch Recordings" +<p>This situation occurs most often with a system that acts as a frontend +and a slave backend. MythTV supports system-global and user-specific +configuration files, with user-configuration files taking precedence. 99% +of the configuration for MythTV is in the MySQL database, but MythTV still +needs to know where the MySQL server is running. This information is in the +<tt>mysql.txt</tt> file. By default, it will be installed to +<tt>/usr/local/share/mythtv</tt>, but a copy placed into <tt>~/.mythtv</tt> +will over-ride the global configuration. + +You must ensure that there aren't multiple, conflicting versions of this +file on your system! +<tscreen><verb> +$ locate mysql.txt +/usr/local/share/mythtv/mysql.txt +/home/mythtv/.mythtv/mysql.txt +$ +</verb></tscreen> + +As you can see, in this example there are two <tt>mysql.txt</tt> files. If +they are not identical, then there may be unintended consequences. + +You may also see this error if you completely fill the <tt>/var</tt> +partition. The most likely <em>mythtv-related</em> reason for this is an +overly large mythbackend or mythfrontend log file in <tt>/var/log</tt>. If +you have logging enabled for the backend, and myth runs for weeks at a time, +this may creep up and surprise you. Note that many system processes also +write to <tt>/var</tt> and the system may not boot if it is unable to write +to <tt>/var</tt> due to a full partition. + +<sect2>MySQL not connecting correctly +<p>Your <bf>MySQL</bf> installation may have networking turned off. +Check that <tt>/etc/mysql/my.cnf</tt> <em>does not</em> contain +<tt>skip-networking</tt>. If it does, remove it. Also verify that +<tt>bind-address</tt> is set to your IP address instead of +<tt>127.0.0.1</tt>. If you change either of these items, restart +<bf>MySQL</bf>. + +<sect2>MySQL database is corrupt +<p>If you have reason to believe that your MySQL database is corrupt, +execute the following commands to attempt to repair it. + +<bf>NOTE</bf>: Ensure that there are no programs accessing the database +while you attempt to repair it. Make sure that all backend and frontend +programs have exited. + +<tt>mysqlcheck -r -umythtv -p<password> mythconverg</tt> + +<sect2>Using a MPEG-2 encoder card and the video appears "jittery" +<sect2>Using a MPEG-2 encoder card and the video is jumping up and down +<p>This is a different problem than the one discussed in the previous +section. Currently, the ivtv driver or firmware appear to have some issues +if the vertical capture resolution is not the full screen height. If you +are having a jitter problem then ensure that you are capturing either 480 +lines (for NTSC) or 576 lines (for PAL). The default capture profiles may +need to be edited for your setup. Go to Settings->TV Settings->Recording +Profiles and adjust the <bf>Default</bf> and <bf>Live TV</bf> options to +480 or 576 from their defaults. + +<sect2>Screen goes blank but returns when mouse is moved or keyboard is used +<p>This is due to DPMS, the Display Power Management System, which is used +to save power by turning off your monitor when the system decides that it's +not being used or due to a screensaver that has defaulted to a blank screen. +MythTV now has DPMS support built-in, and should intelligently handle the +screen. Continue reading if you wish to override DPMS and force it off. + +Since it's likely that watching TV will not generate keyboard or mouse +events for a time, you need to turn off DPMS and the screensaver. There are +a few ways to do this. You may also need to check your BIOS for power +saving modes and disable screen blanking there as well. + +Edit your <tt>/etc/X11/XF86Config-4</tt> or <tt>/etc/X11/xorg.conf</tt> +file, and look for: +<tscreen><verb> +Section "ServerFlags" + #DontZap # disable <Ctrl><Alt><BS> (server abort) + #DontZoom # disable <Ctrl><Alt><KP_+>/<KP_-> (resolution switching) + AllowMouseOpenFail # allows the server to start up even if the mouse doesn't work + + Option "blank time" "0" + Option "standby time" "0" + Option "suspend time" "0" + Option "off time" "0" + Option "NoPM" "1" +EndSection +</verb></tscreen> + +Also, look for: +<tscreen><verb> +Section "Device" + Identifier "device1" + VendorName "nVidia Corporation" + BoardName "NVIDIA GeForce 256 (generic)" + Driver "nv" + Option "DPMS" +EndSection +</verb></tscreen> + +In this case, you would need to either delete the <tt>Option "DPMS"</tt> +line, or change it to <tt># Option "DPMS"</tt> to comment it out. The next +time you start XFree this change will take effect. + +Finally, check: +<tscreen><verb> +Section "Monitor" + Identifier "monitor1" + VendorName "Plug'n Play" + HorizSync 30-85 + VertRefresh 50-160 + + # Sony Vaio C1(X,XS,VE,VN)? + # 1024x480 @ 85.6 Hz, 48 kHz hsync + ModeLine "1024x480" 65.00 1024 1032 1176 1344 480 488 494 563 -hsync -vsync + + # TV fullscreen mode or DVD fullscreen output. + # 768x576 @ 79 Hz, 50 kHz hsync + ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630 + + # 768x576 @ 100 Hz, 61.6 kHz hsync + ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616 +EndSection +</verb></tscreen> + +Ensure that there isn't an <tt>Option "DPMS"</tt> in the Monitor +configuration. + +You can also turn off DPMS from the Command Line, but this will not survive +a reboot. +<tscreen><verb> +$ xset -dpms +</verb></tscreen> + +Using <tt>xset +dpms</tt> will turn it back on. + +Another technique to try, which will turn off the screensaver: +<tscreen><verb> +$ xset s off +</verb></tscreen> +You may also combine the command to turn off DPMS and the screensaver: +<tscreen><verb> +$ xset -dpms s off +</verb></tscreen> + +Finally, depending on your distribution, you may be able to turn it off from +within the control panel. +<sect1>Miscellaneous +<sect2>mythfilldatabase failing +<p>If mythfilldatabase suddenly appears to be failing, there are at least +two things to check. + +First, if you are in North America, ensure that your DataDirect subscription +is still valid, otherwise, check to see what version of XMLTV you're +running and that it's the latest version. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: It is highly recommended that you run the latest +version of XMLTV available. Your listings provider may have made changes +which negatively impact XMLTV. +</caption> +</figure> + +<sect2>Fast CPU, choppy or jittery video <label id="Setting_DMA"> +<p>First, you should check that your kernel has been enabled for DMA: +<tscreen><verb> +[mythtv@pvr mythtv]$ dmesg |grep DMA + ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA + ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio +hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63, UDMA(33) +hdb: 80043264 sectors (40982 MB) w/2048KiB Cache, CHS=4982/255/63, UDMA(33) +</verb></tscreen> + +From the listing above, you can see that hda, hdb and hdc are set for DMA, +and hdd is set for pio. If your kernel is not reporting DMA being enabled, +you may need to recompile your kernel. Check your motherboard's chipset +(look in the "ATA/IDE/MFM/RLL support" section in "make menuconfig") for more +information. + +Next, check that the hard drive has DMA enabled. Use the <bf>hdparm</bf> +program to check and enable DMA. +<tscreen><verb> +# hdparm -d /dev/hd? +</verb></tscreen> will tell you the DMA status for your hard drives. If you run +<bf>hdparm</bf> with the <tt>-d1</tt> parameter, it will turn DMA on. + +<!-- Next section adopted from a post by Dwaine Garden +dwainegarden@rogers.com to the mailing list. --> + +You may also setup your PC to do this at boot time, either by adding the +command to your <tt>/etc/rc.local</tt> file, or by adding files to +/etc/sysconfig. + +On Mandriva and other distributions, if you install <bf>hdparm</bf> from an RPM you +will most likely get a <tt>/etc/sysconfig/harddisks</tt> file installed. +This file will be parsed by the <tt>/etc/rc.sysinit</tt> script. If you use +the default <tt>harddisks</tt> file, your changes will affect all IDE devices +(including CD ROMs). If you wish to use different parameters for various +devices, rename and/or copy the file to <tt>harddiskhda</tt>, +<tt>harddiskhdb</tt>, etc. Edit the file to your liking and on the next +reboot your setting will be preserved. + +<sect2>Frontend appears to be slow at jumping / seeking. +<sect2>On-screen Display shows incorrect program length. +<p>This may occur when MythTV doesn't have an accurate seek table. Run +<bf>mythcommflag --rebuild</bf> + +<sect2>Troubleshooting audio <label id="Troubleshooting_Audio"> +<!-- By Bruce Markey --> +<p> +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: the following instructions do not apply to PVR-250/350 +encoders; the MPEG-2 file will have the audio embedded in the stream so it +is not accessible using <tt>/dev/dsp</tt>. +</caption> +</figure> + +Audio appears to be one of the bigger issues that users run into on the +mailing list. If the audio isn't configured correctly, then MythTV will +often appear to hang, when in fact it is trying to manipulate the audio +subsystem and failing. You may or may not receive error messages indicating +that the source of the error is the audio subsystem. + +You can not use <bf>xawtv</bf> to determine if your audio is working +correctly, since <bf>xawtv</bf> is simply using the analog sound patched +through line-in to line-out. It doesn't need to digitize the sound unless +you are using the recording function. + +A better test to verify that sound will work for MythTV (and recording with +<bf>xawtv</bf> for that matter) is to startup <bf>xawtv</bf>, mute the +line-in then run <tt>aplay /dev/dsp</tt>. You should hear the recorded audio +slightly delayed behind the real-time video. You should see messages about +"underrun". These can be ignored but they do confirm that the driver is +loaded and there is an active device. Once this test succeeds, MythTV +should work correctly because it writes to and read from /dev/dsp in +the same way that <bf>aplay</bf> does. + +To record audio along with video the audio signal must be digitized by a DSP +so that the audio data can be stored in a file. On playback, the audio data +is written to /dev/dsp and converted back to an analog signal. This analog +signal should then be sent to your speakers. Here is what is needed in +<bf>alsamixer</bf>. If you are using an ALSA version after 1.0.6, use +<bf>alsamixer -V all</bf>: + +CAPTUR source - the analog source to be sent to the DSP. This should be set +to the input source from the tuner card to the sound card. In most cases +this is Line but this could also be Aux, CD, Mic, etc., depending on how you +connect the input cable. This source should be muted to prevent patching +through the analog sound. The volume of this source will not affect the +record level. + +Capture mixer - this sets the level for the analog to digital recording. +While a volume of 100% is recommended for testing, distortion may occur. +Lowering this level to 75% to 85% may result in better audio quality. +"Capture" should be marked as the CAPTUR destination. + +PCM mixer - this sets the level for the digital to analog playback. While a +volume of 100% is recommended for testing, distortion may occur. Lowering +this level to 75% to 85% may result in better audio quality. + +Master mixer - sets the level for the analog signal sent to line-out or the +speakers. + +You may also want to ensure that <tt>/dev/dsp</tt> , or whatever device file +is being used, hasn't already been grabbed by another process, like +<bf>esd</bf> or <bf>artsd</bf>. If the device file isn't available, then +MythTV won't work. You may wish to run <bf>configure</bf> and enable +support for these. + +If you wish to see what application is grabbing a resource, you can use the +<tt>fuser</tt> command: +<tscreen><verb> +# fuser -v /dev/dsp +</verb></tscreen> + +To disable aRts in KDE, go to KDE->Control Center->Sound->Sound System and +uncheck the "Start aRts soundserver on KDE startup" box. Run <tt># killall +artsd</tt> from the command line to stop the artsd program. + +If you're using multiple sound cards and multiple tuners, use <tt>alsamixer +-c 1</tt> to work with the second sound card. The first card is #0, the +second card is #1, etc. + +<sect2>Mythbackend reports that your card is not reporting full duplex capabilities +<sect2>The mythbackend program told me to look at this section +<p>mythbackend does a check to see if your sound device is capable of full +duplex operation. If it's not, it's most likely that you're going to run +into issues when you try to record and play sound at the same time. If your +backend is a separate machine than your frontend, then there's no problem, +since you're only going to be doing one thing at a time with the card. +Likewise, if you're running the frontend and backend on the same machine, +but you're using btaudio or a hardware encoder card such as the Hauppauge +PVR-250, DVB cards or HDTV capture cards as your recording source and you're +only using the playback function of your sound card, then you also shouldn't +have an issue, since the sound card isn't being asked to perform two +functions at once. + +If you can't get your sound card to go full-duplex and need it to, then check +your distribution for updated sound drivers. If your sound card is not +capable of full-duplex operation, either because the drivers don't support +it, or it has been designed that way, then you're pretty much out of luck +and will either need to purchase a new sound card, or will need to get +btaudio <ref id="btaudio" name="operational">. + +<sect2>My remote doesn't work / works sometimes and not others / "ghost" keypresses +<p>This can be due to a number of factors. The simplest case is the +"ghost" keypresses. For me, it was due to compact fluorescent lights in +the same room as the IR receiver, which the receiver was picking up as +keypresses. Once the lights were switched to incandescent bulbs, the ghost +went away. + +You may have an issue with <bf>lirc</bf> misinterpreting IR commands from a +different remote. I also have an issue where the TiVo "Peanut" remote will +eventually cause <bf>lircd</bf> to stop responding; even though <bf>lircd</bf> +is configured for the Pinnacle Systems remote, the TiVo remote IR patterns +are being seen by the IR receiver. + +If your remote has been properly configured, and <bf>irw</bf> and +<bf>irxevent</bf> are working correctly, then it's highly likely that your +window manager is not giving focus correctly to the various Myth programs as +they run. The following window managers are known to work correctly: + +<itemize> +<item>fvwm +<item>blackbox (using "Sloppy Focus" and "Focus New Windows") +</itemize> + +<bf>NOTE</bf>: You do not need to use <bf>irxevent</bf> if you are using +MythTV's native LIRC support, so the window manager focus issue does not +apply in that case. + +<sect2>Where's "canada-cable"? +<sect2>Channels are off by one +<p>There is no such thing as "Canada Cable"; Canada uses the same +frequencies as the United States. "Canada Cable" was a hack that some +people used when they would discover that their channels were off-by-one, +i.e. when tuning to channel 42, they might get channel 41 or 43. This is +actually due to the tuner on the video capture device being mis-detected. +You must manually specify the tuner type in your <tt>/etc/modules.conf</tt>. +See the video4linux mailing list (<url +url="https://listman.redhat.com/mailman/listinfo/video4linux-list" +name="https://listman.redhat.com/mailman/listinfo/video4linux-list">) for +more information. + +<sect2>Mythweb is showing a db_open error when I connect to it +<!-- Fix by Chris Ripp [chris@ripp.net] post to mailing list --> +<p>Find your <tt>php.ini</tt> file. Make sure you've got a line in it like this: + +<tt>extension=mysql.so</tt> + +Restart <bf>apache</bf> for it to take effect. + +<sect2>Mouse pointer disappears when placed over the MythTV windows +<p>This is the intended behavior. The MythTV interface is meant for use +with a remote control or a keyboard. + +<sect2>What does "strange error flushing buffer" mean on the console? +<p>Nothing, really. It's just lame (the mp3 encoder) complaining for some +obscure reason. This seems to be fixed in more recent versions of the +libmp3lame library. + +<sect2>Can't change the channel when watching Live TV. +<p>Something's wrong with your program database. Did mythfilldatabase run +with no major errors? Or, MythTV may not have permissions to the +appropriate video4linux devices. See the section titled <ref id="devperms" +name="Device Permissions"> for an example. + +<sect2>Screen goes black when you try to play something +<p>MythTV prints error and status messages to the shell that was used to +start the application. If nothing seems to be happening when you try to +view a program, try switching back to the shell and look for error messages +there, or, if you're running from a startup script, check the log file. + +<sect2>Poor performance with NVidia cards and XvMC +<p>XvMC is a NVidia driver feature which is supposed to help with decoding +video. Users have reported that rather than speeding up their video it +appears to be doing the opposite. You may want to check that your color +depth is set for 24bpp. + +<sect2>Computer is loading a media player application when you insert a CD or DVD +<p>You need to disable any sort of auto-running media player in your +environment, otherwise MythDVD or MythMusic will not be able to work +properly. + +In KDE, you may want to perform the following: +<tscreen><verb> +$ rm ~/.kde/Autostart/Autorun.desktop +</verb></tscreen> +<sect>Miscellaneous. +<sect1>I'd like to watch the files without using MythTV / I'd like to convert the files to some other format +<p>First, check if the <bf>mytharchive</bf> plugin does what you want. If not, then +read on: + +MythTV comes with a utility called <bf>mythtranscode</bf> which can +decode nuv files into raw format for use with other applications. This +command-line utility was not designed to be used by the end-user, but +instead to be called by other applications or scripts. Programs like +<bf>nuvexport</bf> (<url url="http://forevermore.net/myth/" +name="http://forevermore.net/myth/">) are better suited for the end user. +However, since <bf>mythtranscode</bf> can be a useful tool, directions on +using it follow. + +<bf>mythtranscode</bf> creates raw streams, which means that they do not +contain any container information such as resolution, frame-rate, or audio +sampling rate. In order to process the output, you must supply this +information to the processing utility. <bf>mythtranscode</bf> provides the +relevant information on STDOUT. + +There are two modes in which <bf>mythtranscode</bf> can create raw streams. +The first has no synchronization and assumes that the processing utility +will read audio and video at a constant rate. This method is useful when a +single application will be processing the raw output, such as +<bf>mencoder</bf> or <bf>ffmpeg</bf>. The second method assumes that two +separate applications will be processing the audio and video streams +independently, and there is no rate control between them which means that +the two programs don't coordinate their efforts to maintain synchronization. + +<sect2>mythtranscode example +<p>First, start <bf>mythtranscode</bf>. You will need to determine the +channel and the start time manually. +<tscreen><verb> +$ mythtranscode --chanid 1036 --starttime 2003-10-20T15:30:00 --profile \ +autodetect --fifodir . & +</verb></tscreen> + +When <bf>mythtranscode</bf> begins executing, it will create two FIFOs +("audout" and "vidout") in the directory specified (in this case ".", +meaning the current directory) and will print out information about the +video stream. + +The next step is to start the processing application. The following assumes +that the stream is NTSC 640x480 with 32Kbps audio. + +To use <bf>mencoder</bf> you would enter a command like: +<tscreen><verb> +mencoder -audiofile audout -audio-demuxer 20 -rawaudio rate=32000 \ +-rawvideo on:w=640:h=480:fps=29.97 -ovc lavc -oac mp3lame -o out.avi \ +vidout +</verb></tscreen> + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: You must use mencoder 1.0PRE1 or later. <bf>mencoder</bf> +version 0.9x <em>WILL NOT WORK!</em> +</caption> +</figure> +Using ffmepg: +<tscreen><verb> +ffmpeg -f u16le -ar 32000 -ac 2 -i audout -f rawvideo -s 640x480 -r 29.97 \ +-i vidout -vcodec mpeg4 -b 2000 -acodec mp3 -ab 128 out.avi +</verb></tscreen> + +Or to play directly using mplayer (again 1.0PRE1 or later is needed): +<tscreen><verb> +mplayer -audiofile audout -audio-demuxer 20 -rawaudio rate=32000 \ +-rawvideo on:w=640:h=480:fps=29.97 vidout +</verb></tscreen> + +If you wanted to write the raw data to separate audio and video files for +later processing, the following would work (note the use of --fifosync +for rate-control): +<tscreen><verb> +$ mythtranscode --chanid 1036 --starttime 2003-10-20T15:30:00 \ +--profile autodetect --fifodir . --fifosync & +$ cat audout > audio.raw & +$ cat vidout > video.yuv +</verb></tscreen> + +<sect1>Using a different window manager +<p>MythTV is not dependent on any particular window manager. If you wish to +run a lightweight window manager, the <tt>contrib/configfiles/</tt> directory has an +example of a <tt>.twmrc</tt> and <tt>.fvwmrc</tt> file you may use. + +<sect1>What capture resolution should I use? How does video work? +<label id="capture_resolution_"> +<!-- Lots of the following is from a Bruce Markey mailto:bjm@lvcm.com post +to the mailing list, 2003-01-21. Updated 2005-02-09 bjm --> +<p>While MythTV allows you to set various GUI and capture resolutions, not +all combinations make sense. + +First, analog video signals have a defined vertical resolution. In NTSC, +the video standard specifies that there are 525 vertical scan lines. Once +the "extra" lines are removed (they're used to synchronize the video signal, +and encode closed captioning data), you have 480 horizontal lines stacked +vertically. + +In PAL, there are 625 "raw" lines of resolution, with a net of 576 +horizontal lines stacked vertically. + +Horizontally, the maximum value allowed for a Bt8X8 chip is 720. However, +due to limitations in the chip and other limitations of broadcast +television, there may not be a noticeable improvement in image quality +beyond 400 or 500 pixels. + +With this in mind, there are certain commonly accepted values for +resolution. While other values may be accepted for the vertical +resolution, they will cause scan lines to be repeated or dropped. + +From "best" to "worst", in NTSC: +<itemize> +<item>720x480 "DVD" resolution. ReplayTV High and medium resolution +<item>704x480 DVD standalone recorder standard resolution +<item>640x480 4:3 +<item>544x480 TiVo Best resolution +<item>480x480 SuperVCD (SVCD) Video CD resolution, TiVo High resolution +<item>352x480 ReplayTV "Standard" quality, TiVo Basic and Medium resolution, DVD "LP" resolution +<item>320x480 +<item>544x240 +<item>480x240 +<item>352x240 Video CD (VCD) resolution +<item>320x240 +</itemize> + +As you can see, the lower quality values are half of the better ones. +720x240 is possible, but isn't a good tradeoff relative to the number of +vertical lines lost. In a PAL country, the you would use values like +720x576 or x288. + +The higher resolutions will be more CPU intensive if you're using software +encoding (PVR-250/350 will have minimal host CPU impact even if you're using +720x480). If the CPU is overtaxed, frames will be dropped causing uneven +motion. You will likely see the best results at resolutions which average at +least 10% CPU idle time. You can use system tools such as <tt>top</tt> or +<tt>sar</tt> to check the CPU % idle while recording. If the CPU average +usage is consistently exceeding 90%, frames will need to be dropped during +peak times when more than 100% of the available CPU would be needed to +process all of the frames. + +If you'd like to read more on this, go to the vcdhelp website at <url +url="http://www.vcdhelp.com/forum/userguides/94382.php" +name="http://www.vcdhelp.com/forum/userguides/94382.php">. + +<sect1>MythTV GUI and X Display Sizes +<p>MythTV is designed to be run as dedicated full screen TV application +but can also be run as a desktop application on a computer monitor. Here +are a few consideration for configuring sizes to best suit you needs. + +<sect2>X Dimensions +<p>For output to a Television, common resolutions are 640x480, 800x600, and +some rare devices support 1024x768. Generally, higher resolutions are +better. However, you may find that you prefer the picture quality at one of +the lower resolutions. Everything in MythTV is scalable and should 'fit' +regardless of the resolution you choose. + +Edit your X configuration file, usually <tt>/etc/X11/XF86Config-4</tt> for +XFree, or <tt>/etc/X11/xorg.conf</tt> for Xorg, so that the resolution you +want to use is listed first in the lists under "Screen". If this resolution +is higher than the resolutions supported by your output device, you will see +a 'panning' effect where moving the mouse to the edge will scroll around a +desktop area which is larger than the display size. If this happens, edit +your X configuration file to match the display size then restart X. + +<sect2>MythTV Dimensions +<p>From "mythfrontend" go to Setup->Appearance. +The default for the height and width is "0" - this will cause +MythTV to automatically size itself to full screen. + +If the MythTV GUI width and height are not 0, mythfrontend uses these GUI +dimensions and is anchored to the upper left corner of the X Desktop. If +the GUI X and/or Y are not 0, the upper left corner is positioned at the +specified coordinates. If the "Run the frontend in a window" box is checked, +the window will have a frame and can then be dragged to any position on the +desktop. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: When the GUI is full screen, you may see windows rapidly +flipping on top of each other. If this happens you will need to set your +window manager to 'Click to Focus' for windows to stack properly. +</caption> +</figure> +The fonts for the GUI and OSD will scale to whatever sizes you use. Most +font sizes can be changed in setup selections or in the .xml files under +<tt>/usr/local/share/mythtv/</tt> . Make sure to use fonts large enough +to be read on a TV screen from a distance. + +The full screen TV size is based on the X display size. For Xinerama, you +can specify a screen in Setup->General. The TV picture will be stretched +to fit the entire GUI area regardless of the <ref id="capture_resolution_" +name="capture resolutions"> used. However, during playback, the "W" key can +to used to correct differences between 16:9 and 4:3. + +<sect2>Overscan Dimensions +<p>Because picture edges can be ragged and screen edges aren't straight, +Television is designed to project an image larger than the physical screen. +This is called "overscan". Underscan is fitting the entire image inside the +screen. Underscan is useful for computer monitors so that toolbars and +scrollbars at the edges can be seen. + +For best results, match the X display area as close as possible to the edges +of the physical screen. This can only be adjusted by your tv-out device or +by the settings for the television set. Many sets have these adjustments in +a 'service mode'. If you cannot make these adjustments, there will be black +borders around the edges of the X desktop, MythTV GUI and TV playback. + +MythTV has settings for "Overscan" in Setup->Playback. These can not, and do +not, cause the image to display beyond the edge of the X display area. The +purpose of these settings are to cut off rough edges and to expand the image +so that objects will appear to be the same size as a normal overscanned TV +picture. + +<sect1>Saving or restoring the database <label id="backupdb"> +<p>See the <bf>mysqldump</bf> manpage for more information. +<tscreen><verb> +$ mysqldump -u mythtv -pmythtv mythconverg -c > mythtv_backup.sql +</verb></tscreen> + +To restore: (assuming that you've dropped the database) +<tscreen><verb> +$ mysql -u root +mysql>create database mythconverg; +mysql>exit +$ mysql -u mythtv -pmythtv mythconverg < mythtv_backup.sql +</verb></tscreen> + +You may need to alter the MySQL permissions if this database is being shared +with multiple systems. See the <ref id="modify_perm_mysql" name="Modifying +access to the MySQL database for multiple systems"> section for more +information. + +<sect1>Deleting the MySQL database +<p><figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: Performing this step will remove the entire database. +You will lose all of your settings and will need to re-run the mc.sql script +to setup the database structure before running the mythtv-setup program. +</caption> +</figure> +<tscreen><verb> +$ mysql -u root +mysql> drop database mythconverg; +mysql> quit +</verb></tscreen> + +<sect1>Moving your data to new hardware +<p>This assumes that you will be moving your data to newer / bigger hardware +and don't want to lose your programs. + +The first step is to create a database backup as demonstrated in an earlier +section. + +Next, you will extract only the data that is relevant to the programs: +<tscreen><verb> +$ grep "INSERT INTO record " mythtv_backup.sql > restore.sql +$ grep "INSERT INTO recorded " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO oldrecorded " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO recordedprogram " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO recordedrating " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO recordedmarkup " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO recordedseek " mythtv_backup.sql >> restore.sql +</verb></tscreen> + +<bf>NOTE</bf>: Newer versions of <bf>mysqldump</bf> place backticks around +the table names. Backticks are not the same as apostrophes! On a typical +North American keyboard, backticks are located to the left of the "1" key, +on the same key as the tilde. Also, because the <bf>bash</bf> shell may try +to interpret the backticks, make sure you use a \ before each one. + +If your <tt>restore.sql</tt> file is empty, you'll need to re-run the +commands like this: +<tscreen><verb> +$ grep "INSERT INTO \`record\` " mythtv_backup.sql > restore.sql +$ grep "INSERT INTO \`recorded\` " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO \`oldrecorded\` " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO \`recordedprogram\` " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO \`recordedrating\` " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO \`recordedmarkup\` " mythtv_backup.sql >> restore.sql +$ grep "INSERT INTO \`recordedseek\` " mythtv_backup.sql >> restore.sql +</verb></tscreen> + +Note the space after the table name and the ">>" to append to the file for +all but the first <bf>grep</bf>. "recordedmarkup" and "recordedseek" are +huge and there may be hundreds of thousands of lines if you had lots of +hours of recordings. + +After you have moved the data files to the new hardware, configure MythTV +using the <bf>mythtv-setup</bf> program as you normally would with a +standard MythTV installation. + +At this point we will restore the information about your programs back into +the database: +<tscreen><verb> +$ mysql -u mythtv -pmythtv mythconverg < restore.sql +</verb></tscreen> + +After successful insertion of the data you may delete the +<tt>restore.sql</tt> file. + +<sect1>btaudio <label id="btaudio"> +<p>btaudio allows you to obtain the audio data from your tuner card directly +over the PCI bus without using a sound card. This is useful if you would +like to use multiple tuner cards in a system without adding a sound card for +each one, or if your existing sound card is not capable of full-duplex +operation. + +In order to use btaudio, your tuner card will need certain hardware +installed on it, and that hardware must be wired correctly. The chip that +will allow you to use the btaudio module is the MSP34xx. However, having a +MSP34xx is no guarantee that you will be able to use the btaudio module. + +As of 2003-03-31, this is the current list of cards and their status: +Works with btaudio: + +<itemize> +<item>Hauppauge WinTV-radio with dbx-TV stereo, model 401 +<item>Hauppauge WinTV-Theater, model 495, 498 (Europe) +<item>ATI TV Wonder +</itemize> + +The following cards do not work: +<itemize> +<item>Pinnacle Studio PCTV Pro - note: this has a MSP34xx, but it's not +wired correctly to the BT878 chip. +<item>ATI TV Wonder VE +<item>Leadtek Winfast 2000 XP (PAL, UK and NTSC) +<item>I/O Magic PC-PVR. No MSP34xx chip. +</itemize> + +The following cards have been reported to work, but have issues: +<itemize> +<item>Avermedia AVerTV Studio (no digital DSP output, "whiney noise" on +analog) +</itemize> + +Once btaudio loads, it should register additional <tt>/dev/dsp</tt> and +<tt>/dev/mixer</tt> devices. Typing <tt>$ dmesg</tt> will let you know +what's going on. + +<sect1>Removing unwanted channels +<p>If <bf>mythfilldatabase</bf> grabbed a channel which you do not want to +include in your TV listings, you can remove the entries from the grabber +configuration and the MySQL database. This often happens with premium +channels; for example, HBO or Showtime may be available on your cable TV +system, but is scrambled because you're not a subscriber to that channel. +Since you can never watch it, you want to get rid of it. + +If you are using the DataDirect service, login to your account at +<url url="http://labs.zap2it.com/" name="http://labs.zap2it.com/"> to +modify your lineup. Uncheck the boxes for any unwanted channels, and they +will no longer be included in your download. + +If you are using a grabber from XMLTV, comment out the channel from the +<tt>~/.mythtv/<sourcename>.xmltv</tt> file by inserting the word "not +" (including the space) in front of the unwanted entry. This will prevent +<bf>xmltv</bf> from grabbing future listings. + +Next, delete the unwanted item from the channel table so that it will not +appear in the EPG or when changing channels. To delete the data from the +database we need to perform some steps. First, assuming that HBO is channel +15, we need to find out the internal <tt>chanid</tt> used by MySQL: +<tscreen><verb> +$ mysql -u root mythconverg +mysql> select chanid from channel where channum=15; ++--------+ +| chanid | ++--------+ +| 1015 | ++--------+ +1 row in set (0.00 sec) +mysql> delete from channel where chanid = 1015; +</verb></tscreen> + +Old program data will be removed over the course of a week. However, you may +want to immediately delete any current program listings for the channel that +has been removed: +<tscreen><verb> +$ mysql -u root mythconverg +mysql> delete from program where chanid = 1015; +</verb></tscreen> + +<sect1>NFS +<p>You may want to use a central server to store your files. + +On the host machine, (in this case, the hostname is "masterbackend") you'll +want to edit your <tt>/etc/exports</tt> file and use something like: +<tscreen><verb> +/var/video (rw) +</verb></tscreen> + +To export the <tt>/var/video</tt> directory with read / write privileges. + +On the "slave" machine, you'll want to edit the <tt>/etc/fstab</tt> file and +add something like: +<tscreen><verb> +masterbackend:/var/video /var/video nfs rsize=8192,wsize=8192,hard,intr,nfsvers=3,actimeo=0 +</verb></tscreen> + +Then run <tt># mount -a</tt> to re-read the file to mount the file system. + +In this case, the source is a machine called "masterbackend" which is +exporting the directory "/var/video", which we're mounting locally at +"/var/video". The rsize and wsize options are used to increase the +performance of NFS; "hard,intr" is there because that's the recommendation +of the NFS-HOWTO, the nfsvers is required for filesizes over 2GB and actimeo +is used to turn off file attribute caching. Attribute caching for a shared +media point causes problems; you always want to see the latest state of the +directory and files. See <url +url="http://www.mythtv.org/wiki/index.php/Optimizing_Performance" +name="http://www.mythtv.org/wiki/index.php/Optimizing_Performance"> for +additional information regarding performance optimization. + +<sect1>Automatically starting mythfrontend at system boot time +<p>Here's an example submitted to the mythtv-dev list by Pat Pflaum +<url url="mailto:pat@netburp.com" name="mailto:pat@netburp.com"> using fvwm: +<tscreen><verb> +$ cat > .xinitrc +fvwm & +mythfrontend +^D +$ cat > .fvwmrc +Style myth* NoTitle, NoHandles, Sticky, WindowListSkip, SloppyFocus, GrabFocus, BorderWidth 0 +^D +$ +</verb></tscreen> + +The following also works with blackbox: +<tscreen><verb> +$ cat > .xinitrc +xset -dpms s off & +irxevent & +mythfrontend & +blackbox +</verb></tscreen> + +Make sure that your <tt>.blackboxrc</tt> file has: +<tscreen><verb> +session.screen0.focusNewWindows: True +session.screen0.focusModel: SloppyFocus +</verb></tscreen> in it. + +<label id="mythbackend_autostart"> +<sect1>Automatically starting mythbackend at system boot time +<sect2>Red Hat And Mandriva +<p>Here's a method for automatically starting mythbackend submitted by Mike +Thomson (<url url="mailto:linux@m-thomson.net" name="mailto:linux@m-thomson.net">) and Stu Tomlinson (<url +url="mailto:stu@nosnilmot.com" name="mailto:stu@nosnilmot.com">). + +Copy the files from the MythTV <tt>contrib</tt> directory or from Mike's web +site (<url url="http://m-thomson.net/mythtv/" +name="http://m-thomson.net/mythtv/">) as follows: + +<tt>etc.rc.d.init.mythbackend</tt> should be made executable and copied to +<tt>/etc/rc.d/init.d/</tt>: +<tscreen><verb> +$ cd contrib +$ su +# chmod a+x etc.rc.d.init.d.mythbackend +# cp etc.rc.d.init.d.mythbackend /etc/rc.d/init.d/mythbackend +</verb></tscreen> + +<tt>etc.sysconfig.mythbackend</tt> should be copied to +<tt>/etc/sysconfig/</tt>: +<tscreen><verb> +$ cd contrib +$ su +# cp etc.sysconfig.mythbackend /etc/sysconfig/mythbackend +</verb></tscreen> + +Edit <tt>/etc/sysconfig/mythbackend</tt> if you want to change the defaults +(the userid that should start mythbackend, location of the logfile and (if +required) the name and location of the mythbackend binary). + +Use <bf>chkconfig</bf> to make sure the script is called when +entering runlevels 3, 4 or 5: +<tscreen><verb> +$ su +# chkconfig --level 345 mythbackend on +# exit +$ +</verb></tscreen> + +<label id="logrotate"> +<sect3>Log files +<p>By default, the log file for mythbackend will be written to +<tt>/var/tmp/mythbackend.log</tt>. This has been tested and is known to work +on Mandriva and Red Hat, but many people prefer to place logs under +<tt>/var/log/</tt>. + +To do this, create a group called <tt>mythtv</tt> (or anything you prefer) +and add your usual MythTV users to that group. If you changed the user that +starts mythbackend from the default of root you <em>must</em> perform this +step. + +Create the directory <tt>/var/log/mythtv</tt> and set its +permissions as follows: +<tscreen><verb> +$ su +# mkdir /var/log/mythtv +# chown root:mythtv /var/log/mythtv +# chmod 0775 /var/log/mythtv +# exit +$ ls -ld /var/log/mythtv +drwxrwxr-x 2 root mythtv 4096 Apr 28 21:58 /var/log/mythtv/ +$ +</verb></tscreen> + +<!-- From an email by chris at cpr.homelinux.net on 2006-09-01 --> +Create a <tt>mythtv</tt> file in <tt>/etc/logrotate.d</tt>: +<tscreen><verb> +$ su +# cat > /etc/logrotate.d/mythtv +# Set default values for all log files first... + +# Rotate the logs once a week, or more frequently if they +# exceed 10Mb in size (size is checked daily). +weekly +size 10M + +# 'copytruncate' is used for logs generated by +# currently-running programs that should not be restarted +# (and can't be signalled to start a new log) after the +# rotation. It duplicates the existing log file and then +# sets the length of the existing file to 0. The only time +# this would break would be if the program writing the log +# was using lseek. +copytruncate + +# After rotating the files, leave the most recent rotated +# copy alone but gzip everything else to save space. +compress +delaycompress + +# If a log isn't present then don't worry about it. +missingok + +# Don't rotate an empty file. +notifempty + +# end of the global options + +/var/log/mythtv/mythbackend.log /var/log/mythtv/mythfrontend.log { + # Keep logs until they are 2 months old or the number of + # logs reaches 12. If the log files stay small, the age will + # kick in first and you'll only have 8 log files. If they + # get larger than 10Mb then you won't keep all 60 days. + rotate 12 + maxage 60 +} + +# Different options for mythfilldatabase: +/var/log/mythtv/mythfilldatabase.log { + rotate 2 +} +^D +# +</verb></tscreen> + +<sect3>Mandriva +<p>Mandriva adds one more twist in the form of the <tt>msec</tt> utility, +which runs regularly and (at the default or any higher security level) sets +permissions on many files, including those under <tt>/var/log</tt>. + +To tell msec about the MythTV log files and their directory, you need to +edit the <tt>/etc/security/msec/perm.local</tt> file to include the +following: +<tscreen><verb> +# /etc/security/msec/perm.local +# Local overrides to the msec program +# +# Full file path user.group permissions +/var/log/mythtv/ root.mythtv 775 +/var/log/mythtv/* root.mythtv 664 +</verb></tscreen> + +A copy of the above has been included in the contrib/ directory. You may +add it by typing: +<tscreen><verb> +$ cd contrib +$ su +# cat etc.security.msec.perm.local >> /etc/security/msec/perm.local +# exit +</verb></tscreen> + +Finally run the <tt>msec</tt> tool to check and implement your +changes. +<tscreen><verb> +$ su +# msec +# exit +$ +</verb></tscreen> + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: msec can only <em>reduce</em> the permissions of files, so if +you don't get the results you expect, check that you're not asking +<tt>msec</tt> to add missing permissions to the files or directories you +created. +</caption> +</figure> +<sect2>Gentoo +<p>The portage file for MythTV has scripts that will allow you to run +mythbackend at startup. + +To run mythbackend as a daemon which starts at boot time: +<tscreen><verb> +# rc-update add mythbackend default +</verb></tscreen> +To stop mythbackend as a daemon: +<tscreen><verb> +# /etc/init.d/mythbackend stop +</verb></tscreen> + +To obtain a list of options: +<tscreen><verb> +# /etc/init.d/mythbackend +</verb></tscreen> + +<sect1>Advanced Backend Configurations <label id="advanced_backend_config"> +<p>MythTV is flexible in the way that you define multiple backend tuner +configurations. The only hard-and-fast rule is that the Master backend +<em>must</em> have a capture device defined, but shouldn't imply that the +capture device in the Master backend must be the first capture card defined in the +database. + +One example of an advanced configuration is the round-robin scheme. Rather +than defining all of the cards on the master, you could first go into +mythtv-setup on the master to define globals such as the general configuration +and the channel lineup but not the host-specific configuration item like the +capture card. In this example, we will use a 4 tuner configuration, where two +slaves have one card each and the master has two. +<enum> +<item>Add the first capture card on one of the slaves. Complete the +configuration, connecting the input source to the card. This will get +cardid #1 in the database. Exit mythtv-setup. +<item>Configure the first capture card on the master backend. This will get +cardid #2 in the database. Exit mythtv-setup. +<item>Configure the first capture card on the second slave. This will be +cardid #3 in the database. Exit mythtv-setup. +<item>Configure the second capture card on the master backend. This will +get cardid #4 in the database. Exit mythtv-setup. +</enum> + +Using this scheme, the master backend will not use both capture cards until +one of the following happens: +<itemize> +<item>There are four recordings scheduled for the same time +<item>Both slaves are unavailable +</itemize> + +The scheduler in MythTV checks whether an encoder is available; if a slave +backend isn't running, its encoder isn't available, so the scheduler will +look for the next available encoder. This makes MythTV very flexible; slave +tuners can come and go, and as long as there are enough tuners for what +you'd like to record it doesn't matter which tuner in particular is going to +be used. + +Using this round-robin scheme along with a shared storage directory like +NFS and enabling the Master Backend Override setting will allow you to view +content even if the slave backend that recorded a program is not available. + +<sect1>Using the transcoder +<!-- Aran Cox, spin667 at mchsi.com --> +<p>MythTV's built-in transcoder re-encodes recordings from one codec to +another. The transcoder has three primary uses; it can transcode MPEG-2 +files captured using a hardware encoder (PVR cards, DVB cards, ATSC HD, +etc.) to MPEG-4, it can be used to transcode RTjpeg files (usually only used +on systems that can not real-time encode to MPEG-4 using a framegrabber) to +MPEG-4, and finally it can be used to remove commercials from a MPEG-2 file +while leaving the file in MPEG-2 format. + +When MythTV transcodes a file to MPEG-4 or RTjpeg the resulting file format +is NuppelVideo (nuv). NuppelVideo is a container which provides a method of +keeping the audio and video in sync throughout the recording, which is why +it is used instead of the <tt>.avi</tt> format. You may have difficulty +playing <tt>.nuv</tt> files in non-MythTV systems. + +<!-- If +you want something more portable you can look at some of the other sections +in this HOWTO. --> + +The original file is removed when the transcoding process is complete. +Unless you're sure that you will be satisfied with the result you may want +to enable the <bf>mythtv-setup</bf> option which causes <bf>mythbackend</bf> +to keep the original file after transcoding. This option is on the second +page of the General section in mythtv-setup. Enabling this allows you to +compare the two files and restore the original if you like. Outside of the +initial setup phase it usually isn't necessary to leave this option enabled. +A recording can be transcoded in two ways: + +<itemize> +<item>Automatically transcode the file once it has completed +recording.</item> +<item>Manually choosing to transcode a recording, usually after +importing a cutlist or manually marking commercials to be +removed.</item> +</itemize> + +The second method can be used on files that have already been transcoded (or +files which were are already in the desired format), so only the frames +immediately following a cut section will be re-encoded, resulting in a +minimal loss of quality when removing commercials with the added benefit of +being extremely quick. + +The current transcoding system has a lot flexibility, but there are +a number of steps involved in setting it up. In order to +automatically transcode a given recording you must do the following: +<enum> +<item>Configure recording profile for your capture source and enable +transcoding on one or more profiles.</item> +<item>Configure one or more transcoding profiles.</item> +<item>Create or alter existing scheduled recordings to enable +transcoding for that recording.</item> +</enum> + +<sect2>Configuring Recording Profiles to Allow Transcoding + +<p>Enter the Utilities/Setup > Setup > TV Settings > Recording Profiles +section in <bf>mythfrontend</bf>. Choose the option that corresponds to +your capture source (ignore the Transcoders for now.) Choose the quality +profile you are interested in using for transcoding. Ensure that "Enable +auto-transcode after recording" is checked. <!-- This option might ought to +be called "allow auto-transcode" as we'll soon see though. You might want to +verify that the other settings for this profile are correct while your here. +--> + +<sect2>Configure Transcoding Profiles + +<p>Enter the Recording Profiles > Transcoders menu. There are three quality +settings to choose from and a two special Autodetect settings. Later, when +scheduling recordings you'll have to choose one of Autodetect, High, Medium, +and Low Quality transcode settings in addition to the recording profile we +set up above. If you choose the Autodetect transcoding profile for a +recording, MythTV will use the "Autodetect from RTjpeg/MPEG-4" profile for +recordings which are RTjpeg/MPEG-4 files. Otherwise, it will use the +"Autodetect from MPEG-2" profile provided it's an MPEG-2 recording. If you +choose one of the others (High, Medium, Low) it will use the settings in +that profile regardless of the codec of the original recording. + +There are a number of options for transcoding but the simplest is to enable +lossless transcoding (the first option) which subsequently removes all other +options. Enabling lossless encoding simply removes commercials (if you've +marked them) and attempts to clean up MPEG-2 streams. Note that with this +option MythTV will not apply any sort of filters and will only attempt to +normalize the stream into something cleaner and less likely to have trouble +with other less forgiving MPEG-2 hardware/software (including players, video +editors, etc.) + +If you enable resizing of the recording the next page has the settings for +choosing the final resolution. MythTV will scale the video as appropriate, +not crop it to this resolution. + +The final two pages allow configuration of the video and audio codecs. +Although RTjpeg is an option for video codec there is no reason to transcode +<em>to</em> this format because it will produce larger files than MPEG-4 and +the recording will take <em>more</em> CPU power to play back. The MPEG-4 +settings are described in the documentation for the <bf>ffmpeg</bf> project +at <url url="http://ffmpeg.sourceforge.net/ffmpeg-doc.html" +name="http://ffmpeg.sourceforge.net/ffmpeg-doc.html">. It's a matter of +trial and error to discover which settings achieve a good compromise between +size and quality. + +If you wish to return to the default settings, they are Bitrate: 2200-2500, +MaxQ: 2, MinQ: 15, MaxQDiff: 3, and "Scale bitrate for frame size" is +enabled. The other options are unchecked. <!-- If you're getting weird +results from MPEG-4 transcoding try setting as above and go from there. --> + +<sect2>Create/Alter Scheduled Recordings to Enable Transcoding + +<p>Transcoding is actually enabled on a per-recording basis. Two things +must be true before any given recording will be auto-transcoded, however. +The first is that the recording must have been made with a recording profile +that has auto-transcode enabled. Under "Storage Options" for the recording +you must set the "Record using the "X" profile" to the profile you +configured in the first step. In addition, under the "Post Recording +Options" section of the recording you must also set "Transcode new +recordings." This is also where you specify the Transcoding profile to use +(Auto, High, Medium, Low.) + +It may not be obvious from above but the flexibility of this system is +primarily to make it possible to auto-transcode a show recorded via one +source (ie: pcHDTV 3000), and not transcode that same show if it's recorded +on another kind of card (ie: PVR-250.) There are other uses however. You +could have a PVR-250 and a V4L card. You may want to transcode the MPEG-2 +from the PVR-250 but there is no need to transcode the recordings made with +the V4L card, as it's already likely to be MPEG-4. + +As an example, you could configure the Default profile for "Hardware DVB +Encoders" (the profile group used for DVB cards, including ATSC cards like +the pcHDTV 3000) to "Enable auto-transcoding". In the Default profile for +MPEG-2 Encoders (PVR cards) you'd leave "Enable auto-transcoding" unchecked. +For programs that are available on both kinds of cards you'd set the +recording profile to Default and enable auto-transcoding in the record +settings. Then you pick your transcoding profile. The result is that when +a program is recorded on your DVB card, it will get transcoded. When it +plays on a channel available via your PVR card, it won't be. + +<sect2>Manual Transcoding + +<p>Manually transcoding is activated while watching a show by hitting 'x', +from the OSD menu by choosing the Transcode option, or by choosing Job +Options/Transcode from the info menu from the Watch or Delete +Recordings screens. + +The transcoding profile used for manual transcoding is whatever was set when +the recording was originally configured, even if you didn't enable +auto-transcoding. The only way to change what transcoding profile will be +used is to alter the transcoder column in the recorded table in the +database. The transcoder column contains a number which corresponds with +the id column in the recordingprofiles table. You can find out the id +number for each profile in the transcoder group with an SQL command like: + +<tscreen><verb> +mysql> select r.* from recordingprofiles r,profilegroups p where p.name='Transcoders' and p.id=r.profilegroup; ++----+----------------+------------+------------+--------------+ +| id | name | videocodec | audiocodec | profilegroup | ++----+----------------+------------+------------+--------------+ +| 21 | RTjpeg/MPEG4 | MPEG-4 | MP3 | 6 | +| 22 | MPEG2 | MPEG-4 | MP3 | 6 | +| 27 | High Quality | MPEG-4 | MP3 | 6 | +| 28 | Medium Quality | MPEG-4 | MP3 | 6 | +| 29 | Low Quality | MPEG-4 | MP3 | 6 | ++----+----------------+------------+------------+--------------+ +5 rows in set (0.01 sec) + +mysql> +</verb></tscreen> + +Armed with the knowledge of what the profile ID's are you can also choose to +run mythtranscode from the command line and explicitly specify the transcoder +profile. Run <tt>mythtranscode --help</tt> for usage information. + +<sect1>Changing your hostname +<!-- Edited instructions from a post by Alan Snyder ax763 at yahoo.com --> +<p>If you need to change the name of the computers used with MythTV you'll +need to perform a sequence of steps. There are a number of pieces of +information that MythTV keeps track of which are tied to the hostname of the +box, so changing the hostname involves altering the name in the +operating system and in the MySQL database. In the examples below, the old +name of the system was "frontend1" and we're going to change it to +"kidsroom". + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: Changing the hostname using direct SQL update commands will +break things. You <em>MUST</em> use this indirect method. +</caption> +</figure> + +1. Stop all backends. If you run <bf>mythbackend</bf> from a terminal +session, press control-c. If your backends are started with an init +script, you would do something like the following: +<tscreen><verb> +$ su +# /etc/init.d/mythbackend stop +</verb></tscreen> + +2. Change the hostname. + +For Red Hat and derived distributions, edit the +<tt>/etc/sysconfig/network</tt> file. Look for +<tt>HOSTNAME=frontend1</tt> and change this to +<tt>HOSTNAME=kidsroom</tt> or whatever you'll be using. For other +distributions, refer to the documentation, such as the +<verb>hostname(1)</verb> man page. + +<p> +To alter the +hostname in the current session, run: +<tscreen><verb> +# hostname kidsroom +</verb></tscreen> + +3. Dump the database. +<tscreen><verb> +$ mysqldump -u mythtv -pmythtv mythconverg -c > mythtv_backup.sql +</verb></tscreen> + +4. Rename the host in the database. First, ensure that the new hostname +you'll be using isn't already in the database. +<tscreen><verb> +$ grep kidsroom mythtv_backup.sql +</verb></tscreen> +Now we're actually going to change the name. The following should all be +typed on the same line: +<tscreen><verb> +$ cat mythtv_backup.sql | sed s/\'frontend1\'/\'kidsroom\'/g >> mythtv_restore.sql +</verb></tscreen> +If you don't feel comfortable using <bf>sed</bf>, you can open the +<tt>mythtv_backup.sql</tt> file in a text editor and perform a global search +and replace. When saving the file, make sure you use the new name, +<tt>mythtv_restore.sql</tt> or the rest of the steps below will fail. + +5. Drop and recreate the database. +<tscreen><verb> +$ mysql -u root +mysql>drop database mythconverg; +mysql>create database mythconverg; +mysql>exit +</verb></tscreen> + +6. Restore the database using your edited version. +<tscreen><verb> +$ mysql -u mythtv -pmythtv mythconverg < mythtv_restore.sql +</verb></tscreen> + +If you are running slave backends or frontends, don't forget to re-enable +access as detailed in <ref id="modify_perm_mysql" name="Modifying access to +the MySQL database for multiple systems">. + +7. Start the backends. If you use init scripts, do the following, otherwise +start them from terminal consoles. +<tscreen><verb> +# /etc/init.d/mythbackend start +</verb></tscreen> + +8. Quit and restart all frontends. Delete the <tt>mythtv_backup.sql</tt> +and <tt>mythtv_restore.sql</tt> files. + +<sect1>Can I run MythTV on my TiVo? +<sect1>Can I run MythTV on my ReplayTV? +<p>No. + +While it is true that the TiVo runs the Linux kernel, and TiVo has released +their changes to the kernel under the GPL, the TiVo is <em>not</em> a +general-purpose computer, and there is no programming information available +for the custom hardware contained within a TiVo. TiVo is under no +obligation to release the source code to their <em>application</em>. + +The ReplayTV runs VxWorks, a Real Time Operating System from Wind River +Systems. +<sect1>Can a wireless connection be used between the frontend and the backend? +<p>Yes, assuming that your wireless connection has sufficient bandwidth to +maintain the datarate between the frontend and the backend. 802.11b should +be sufficient if the encoded bitrate of the content is less than the +datarate of your wireless connection, which in the case of 802.11b would be +approximately 4 Mbps. (The advertised rate of 11Mbps gives an actual +throughput of 4 Mbps.) 802.11a and 802.11g, if operating in their high-speed +modes, or proprietary 802.11b "Turbo" schemes should be adequate. Multiple +wireless frontends, poor signal strength or other factors can severely +impact the viewing experience on the frontend. + +<sect1>How can I burn shows that I have recorded to a DVD? +<p>Use the mytharchive plugin. + +<sect1>Using the DBoxII within MythTV +<p>The configuration of the DBoxII for use within MythTV is tricky (as of +May 16 2005), that's why it's covered here. Your DBoxII has to be running +linux and the Neutrino GUI instead of the stock BetaNova firmware. For +further information, please refer to <url url="http://www.tuxbox.org" +name="http://www.tuxbox.org">. Additionally, you need to enable the SPTS +mode in Neutrino. + +<itemize> +<item>Add a new "Capture Card" in the setup. The "Card type" is "DBOX2 Input", +the other values have to be adjusted according to your setup. +The default values, except for the "DBOX2 host ip", should work fine. +<item>Define a new video source. It doesn't need to be configured, +you just need to define it. MythTV grabs the EPG from the DBoxII. +<item>Connect the DBoxII to the newly defined input source in "input connections". +<item>Since channel scanning is not implemented yet, you need to define channels +in the "Channel Editor". Make sure that you use the same value for +"Channel Name" as on the DBoxII. You can get a list of available +channels from the web interface of Neutrino at http://ip-of-your-box:80/. +Associate the channel with your new video source and repeat when needed. +</itemize> + +You may leave the Setup now and proceed as usual. + +<sect1>What do the icons on the Watch Recordings screen mean? +<p>Press "1" or F1 to get a popup. +<sect1>What do the letters mean when I change channels? +<p>These letters let you know what's going on with the backend as it tries +to tune to a channel. + +Lower case = seen + +Upper Case = seen & good +<itemize> +<item>l/L = Lock : This could be seen by PVR-250/BTTV users +<item>a/A = PAT : Any recording transmitted in MPEG +<item>m/M = PMT : Any recording transmitted in MPEG +<item>g/G = MGT : ATSC only +<item>v/V = VCT : ATSC only +<item>n/N = NIT : DVB only +<item>s/S = SDT : DVB only +</itemize> +<sect1>What is the difference between the various Hauppauge PVR models? +<p>This is covered in the hardware section, and extensively covered on the +Hauppauge website. (<url +url="http://www.hauppauge.com/pages/compare_pvr.html" +name="http://www.hauppauge.com/pages/compare_pvr.html">) Please check the +Hauppauge website for the most accurate information. + +A PVR-150 comes in a number of versions: +<itemize> +<item>The PVR-150 (Model 1045) is the retail kit. It comes with a remote +control and an IR Blaster. It does not have a radio tuner. +<item>The PVR-150 MCE (Model 1042) will usually come in a plain white box and is +sold as an OEM device. It does not come with a remote control, since it's +usually used as the second, third, etc capture device. +<item>The PVR-150 MCE Kit (Model 1062) does not have a radio tuner and +comes with a Microsoft Media Center remote control instead of Hauppauge's. +<item>The PVR-150 low profile (Model 1086) is a low-profile card. It has a +radio tuner and is approximately half the height of a standard card. +However, it comes with a low-profile PCI bracket, so it is not suitable for +use in a standard PCI slot without removing the bracket, which may not be +worth the trouble. +</itemize> + +A PVR-250 (Model 980) is a retail kit which comes with an IR receiver and a +remote control. + +The PVR-250 MCE (Model 975) contains a FM radio tuner. The PVR-250 MCE does +not contain a IR receiver or a remote. + +The PVR-250 Rev 1 contained an MPEG-2 decoder. However, this function was +not connected to any output jacks, and there doesn't appear to be any way to +pull decoded video from the card, so it's a fairly useless feature. + +The PVR-350 (model 990) has the features of the PVR-250 as well as being +able to decode MPEG-2. The encode and decode functions may be used +simultaneously. The MPEG-2 decoder function gives superior video quality +compared to what you'll find on a standard video card. However, the decoder +function is only available once Linux has started, so you will not see any +boot-time messages. Also, the card is not capable of resolutions higher +than 720x480, so it cannot be used with HDTV. Make a conscious decision +(and ask for advice on the mailing list) that you want to tradeoff potential +HDTV use in the future compared to video quality. + +The X-driver for the PVR-350 support playback using Xv efficiently but does +not support any other 2D or 3D acceleration. For some application this may +place a large load on the host CPU, some will run without any problem and +others (mplayer, xine, xmame etc.) should be configured to utilize the Xv +interface. + +Note that for the PVR-350 there are some <ref id="PVR-350" name="considerations"> +regarding the way audio is handled. + +The PVR-500 is a dual-encoder version of the PVR-150 card, so you can +simultaneously record two different programs at the same time, because there +are two encoder chips on the PCI card. Hauppuage has also installed an +onboard splitter, so you can use one COAX to feed both tuners. Current +versions of the PVR-500 should come with an adapter to allow you to connect +a second S-Video or composite input, but this will take up a second PCI +slot. Early adopters may need to purchase this item separately. + +<sect1>Changing channels on an external Set Top Box +<p>If you need to use an external Set Top Box (STB), such as for satellite +TV or for digital cable you will need some way for MythTV to tell the STB to +switch to a new channel. There are several methods: +<enum> +<item>Use an IR blaster. An IR blaster is an infrared transmitter connected +to your computer. When MythTV needs to change channels it will send IR +pulses, thereby emulating a remote control. +<item>Use a direct serial connection. Some STB's have a serial port on the +back, although it may not look like a serial port. It may look like a phone +jack, or a strange VGA connector. It may be labeled "Low Speed Data". A +direct serial connection is more reliable than an IR blaster. Not all STB's +that have a Low Speed Data port have it enabled; you may need to convince +your service provider to turn it on. Stating that you have a Tivo may help; +the Tivo has a direct-connect capability. +<item>Use a firewire connection. There is a <tt>6200ch.c</tt> in the MythTV +contrib directory which may work for you. +</enum> +<sect1>Configuring one machine to flag all commercials +<p>Commercial flagging can be CPU intensive. By default, the backend that +created a recording is the one which will flag commercials. You may wish to +use a different machine to run commercial flagging. + +On the slower machine: + +Start the mythtv-setup program. Advance through the pages until you get to +the Job Queue page. Turn off the setting that says "Allow Commercial +Detection jobs", thereby preventing any commercial flagging jobs from +running on this machine. + +Next, make sure that "Run Jobs only on original recording host" is turned +OFF so that new jobs are allowed to run anywhere. + +Restart <bf>mythbackend</bf> since it only reads this setting when it starts +up. + +On the faster machine: + +Start the <bf>mythtv-setup</bf> program. Advance through the pages until +you get to the Job Queue page. Ensure that "Allow Commercial Detection +jobs" is turned ON for this machine. + +Run <bf>mythjobqueue</bf>. <bf>mythjobqueue</bf> will examine the JobQueue +and run any jobs it finds. <bf>mythjobqueue</bf> should be left running so +that it will pick up any new commercial flagging jobs that are added to the +queue, otherwise new jobs will be added to the queue and your programs won't +be flagged until you run manually run <bf>mythjobqueue</bf>. + +Using this technique it's possible to add commercial flagging machines as +needed, even on systems that aren't running a backend. It's also possible +to run the commercial flagger in a virtual machine environment such as +VMWare. + +<sect>Example Configurations. +<sect1>Logical Volume Manager (LVM) <label id="LVM"> +<!-- Contributed by Martin Smith martin at spamcop.net --> +<!-- XXXXX REMOVE ME FOR 0.22 --> +<p>LVM greatly increases the flexibility you have in managing your storage +than traditional physical partitions. This section will provide some brief +notes on how to use LVM to create storage space for your video files and how +to add additional disk space in the future. There's lots more that can be +done with LVM, so check the LVM HOWTO <url +url="http://tldp.org/HOWTO/LVM-HOWTO/" +name="http://tldp.org/HOWTO/LVM-HOWTO/"> document for details. + +<p><figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption> +<bf>NOTE</bf>: If you are running MythTV 0.21 and you are using LVM to +create one large filesystem to store your recordings, it's no longer +recommended that you go the LVM route. The preferred solution is to use <ref +id="storagegroups" name="Storage Groups">. They're more flexible and less +likely to lose all of your recordings if you have a drive failure. +</caption> +</figure> + +If you don't understand how to partition a drive, or how to change the +partition type you should stop and look at documentation on how to perform +these steps. + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption> +<bf>BIG FAT WARNING</bf>: Using an incorrect parameter can make your files +inaccessible, prevent your computer from booting, etc. Be careful! +</caption> +</figure> + +Make sure your kernel configuration includes LVM support or that it's +available as a module. Today, most vendors include this by default. You'll +also want to ensure that you have a copy of the LVM utilities; check your +distribution, or get the latest versions from <url +url="http://www.sistina.com/products_lvm.htm" +name="http://www.sistina.com/products_lvm.htm"> and build them manually. + +Check that the <bf>vgscan</bf> program is being run at some point during +your boot sequence - most distributions do this by default. Look for a +message during boot up that looks like this: <tt>vgscan -- reading all +physical volumes (this may take a while...)</tt> If you don't see any +messages during boot, you may need to install a LVM init script or confirm +that you have all of the LVM packages installed from your distribution. + +LVM uses a few concepts you should be familiar with before starting. +<itemize> +<item>PV (Physical Volume). The actual partition on the hard drive. +<item>VG (Volume Group). The aggregation of all the PVs make a VG. +<item>LV (Logical Volume). Subdivision of the pool of space available in +the VG into individual chunks, like /usr, /var/video, etc. +</itemize> + +The following example assumes that you want to create a LVM partition from a +chunk of space in /dev/hda5, using a reiserfs filesystem and mounted on +/var/video. You later decide to extend this filesystem by adding a new disk: +/dev/hdb. + +You need to create at least one LVM partition for a physical volume. Use +<bf>fdisk</bf> or your favorite partition editor to set the type to LVM +(0x8e). If you're using an entire disk, create one big partition rather than +using the device itself. e.g. use /dev/hdb1 not /dev/hdb. + +In the following example, you have a 15GB disk. The first 6GB are set as +your boot partition. <tt>/dev/hda2</tt> was added as an extended partition, +and within that partition you created the <tt>/dev/hda5</tt> linux (ext2) +partition. + +<tscreen><verb> +# fdisk /dev/hda + +The number of cylinders for this disk is set to 1823. +There is nothing wrong with that, but this is larger than 1024, +and could in certain setups cause problems with: +1) software that runs at boot time (e.g., old versions of LILO) +2) booting and partitioning software from other OSs + (e.g., DOS FDISK, OS/2 FDISK) + +Command (m for help): p + +Disk /dev/hda: 15.0 GB, 15000330240 bytes +255 heads, 63 sectors/track, 1823 cylinders +Units = cylinders of 16065 * 512 = 8225280 bytes + + Device Boot Start End Blocks Id System +/dev/hda1 * 1 764 6136798+ 83 Linux +/dev/hda2 765 1823 8506417+ 5 Extended +/dev/hda5 765 1823 8506417 83 Linux + +Command (m for help): t +Partition number (1-6): 5 +Hex code (type L to list codes): 8e + +Command (m for help): p + +Disk /dev/hda: 15.0 GB, 15000330240 bytes +255 heads, 63 sectors/track, 1823 cylinders +Units = cylinders of 16065 * 512 = 8225280 bytes + + Device Boot Start End Blocks Id System +/dev/hda1 * 1 764 6136798+ 83 Linux +/dev/hda2 765 1823 8506417+ 5 Extended +/dev/hda5 765 1823 8506417 8e Linux LVM + +Command (m for help): w + +# +</verb></tscreen> + +Create the LVM physical volume from the partitions (repeat if you have +multiple partitions to use): +<tscreen><verb> +# pvcreate /dev/hda5 +</verb></tscreen> +Create a LVM volume group out of this physical volume called "VGforMyth" that is +allocated in chunks that are a multiple of 64MB +<tscreen><verb> +# vgcreate VGforMyth -s 64m /dev/hda5 +</verb></tscreen> +Create a logical volume of 5GB called "video" and then create the reiserfs +filesystem and mount it: +<tscreen><verb> +# lvcreate --name video --size 5G VGforMyth +# mkreiserfs /dev/VGforMyth/video +# mount /dev/VGforMyth/video /var/video +</verb></tscreen> +Now create a 3GB volume for mythmusic files if you like: +<tscreen><verb> +# lvcreate --name music --size 3G VGforMyth +# mkreiserfs /dev/VGforMyth/music +# mount /dev/VGforMyth/music /var/music +</verb></tscreen> +Display the volume group status: +<tt># vgdisplay -v</tt> + +Now, lets suppose you want to add a 60GB hard disk to the system as hdb and +allocate 50GB of it to video storage. + +First, create a single partition /dev/hdb1 covering the whole disk and make +it type 0x8e using your partition editor. + +<tt># fdisk /dev/hdb</tt> +.... create partition, set type, save and reboot if it says you have to + +Create the new LVM physical volume: + +<tt># pvcreate /dev/hdb1</tt> + +Add the new physical volume to the volume group: + +<tt># vgextend VGforMyth /dev/hdb1</tt> + +<figure loc="here"> +<eps file="stop.eps" height="1cm"> +<img src="stop.png"> +<caption><bf>NOTE</bf>: You may get errors at this point stating that there are no +physical volumes available for adding to the LV, even though you know for a +fact that there are. You may need to specify the physical volume in the +<tt>/dev/ide/host/bus/target/lun/etc</tt> format. +</caption> +</figure> +Once you've completed one of the following two procedures, use <bf>df</bf> +to check that you've got more space. + +Make the logical volume used for video bigger: + +<tt># lvextend --size +50G /dev/VGforMyth/video</tt> +<sect2>ReiserFS +<p>Unmount, resize and remount the filesystem. Technically, you don't need to +unmount and remount the ReiserFS. +<tscreen><verb> +# umount /var/video +# resize_reiserfs /dev/VGforMyth/video +# mount /dev/VGforMyth/video /var/video +</verb></tscreen> + +<sect2>ext2 or ext3 +<p>LVM comes with a program called <bf>resize2fs</bf>. + +Unmount, resize and remount the filesystem. The filesystem <em>must</em> be +unmounted during this procedure. +<tscreen><verb> +# umount /var/video +# resize2fs --size +50G /dev/VGforMyth/video +# mount /dev/VGforMyth/video /var/video +</verb></tscreen> +<sect2>xfs +<p>XFS does not need to be unmounted to extend the size: +<tscreen><verb> +# xfs_growfs /var/video +</verb></tscreen> +<sect1>Advanced Partition Formatting <label +id="advancedpartitionformatting"> +<p>The partitions that your distribution sets up for you may not be +optimized for large files. Using LVM in conjunction with the following +techniques can be quite useful. + +Unlike a typical filesystem, a MythTV video partition is usually a very +large filesystem filled with a fairly small number of large files. +Filesystem I/O is usually not an issue, even in multi-tuner and/or +multi-frontend setups. + +There is however, one aspect of filesystem performance that can have a +bearing on the performance of MythTV. In Linux, deleting a file will +utilize I/O bandwidth until the deletion has been completed. If deleting +the file takes long enough, the video capture buffer may overrun, thereby +resulting in dropped frames. Some filesystems are faster at deleting files +than others and, for multi-gigabyte MythTV video files, these differences +can be significant. + +Fortunately, there are published tests (<url +url="http://aurora.zemris.fer.hr/filesystems/big.html" +name="http://aurora.zemris.fer.hr/filesystems/big.html">) that provide +insight into filesystem performance under conditions relevant to MythTV +usage. In addition, some limited testing (archived at <url +url="http://www.gossamer-threads.com/lists/mythtv/users/52672" +name="http://www.gossamer-threads.com/lists/mythtv/users/52672">) +with very large files (10 gigabytes) was reported in the MythTV Users +mailing list. + +<sect2>Ext2 +<p>Ext2 was the defacto standard Linux filesystem for many years. It is +stable, provides good I/O performance and can quickly delete large files. +The primary disadvantage of Ext2 is that it is not a journaling filesystem, +so a file system consistency check (fsck, which is normally only performed +after a system crash) can take many hours on a filesystem the size of a +typical MythTV partition. + +<sect2>Ext3 +<p>Ext3 is Ext2 with a journal, so your biggest gain is that in case of a +crash and reboot you won't have to wait very long for your partition to be +remounted. + +There are options available when formatting an Ext3 partition, as in: +<tscreen><verb> +# mkfs.ext3 -T largefile4 /dev/hdb1 +</verb></tscreen> + +This example assumes that <tt>/dev/hdb1</tt> has already been created using +<bf>fdisk</bf>. If you're using LVM, <tt>/dev/hdb1</tt> may be something like +<tt>/dev/VGforMyth/video</tt>. + +The "-T largefile4" option creates one inode per 4 megabytes, which can +provide a few percent more storage space. However, tests indicate that +using the "-T largefile4" option can drastically increase the amount of time +required to delete a large file and thus it should only be used with encoder +settings that produce small video files (YMMV). + +You can check on your filesystem using the <bf>dumpe2fs</bf> program. See +the man page for details. +<sect2>ReiserFS +<p>The Reiser filesystem is another journaling filesystem commonly +distributed with Linux. It is known to be an extremely efficient filesystem +and it especially excels at managing partitions containing a large number of +small files. However, tests indicate it is not the fastest at deleting very +large files. For that reason, it may not be the best choice when using +encoder bitrates that produce very large files. + +<sect2>JFS +<p>JFS (Journaling File System) is a journaling filesystem originally +developed by IBM for AIX which was later released as open source. While not +as common as Ext3 or ReiserFS, it is distributed with RedHat 9 (RH9), Fedora +Core and Mandriva as well as other distros. According to tests, JFS is the +file deletion speed king, deleting virtually any file in under one second, +even files as large as 10 gigabytes. + +<sect2>XFS +<p>XFS is a journaling file system originally developed by SGI for Irix, and +later released as open source. While not a part of the default RedHat Linux +9 or Fedora Core installation (although it is a part of Mandriva and Fedora +Core 2+), it can be easily installed via ATrpms. XFS provides deletion +speeds for large files only slightly slower than JFS. According to the test +results shown at (<url +url="http://aurora.zemris.fer.hr/filesystems/big.html" +name="http://aurora.zemris.fer.hr/filesystems/big.html">), XFS provide +higher I/O rates than JFS, albeit at a higher CPU loading. This may cause +issues if you do not have the spare CPU capacity to handle XFS, potentially +leading to dropped frames. + +<label id="migratingtoSD"> +<!-- Mostly from a post by Bruce Markey --> +<sect1>Migrating from DataDirect Labs to Schedules Direct + +<p>MythTV v0.20.2 or later is required to natively support Schedules Direct. +Code has been included to make the transition as simple as possible. + +<bf>You do not need to delete your existing video sources or add new ones!</bf> + +The following steps should work for most users: +<itemize> +<item>Create a Schedules Direct account and use the same information as your +existing lineups at Zap2It Labs. Do not add or delete channels at this +time. +<item>Shut down any running <bf>mythfrontend</bf> and <bf>mythbackend</bf> programs. +<item>Perform a backup of your existing database. See <ref id="backupdb" +name="Saving or restoring the database"> for instructions. +<item>Run <bf>mythtv-setup</bf> -> Video Sources. Change the grabber to +Schedules Direct, update the username and password fields with the account +information you created at Schedules Direct and select "Retrieve Lineups". +Click Finish. +<item>Exit <bf>mythtv-setup</bf> and run <bf>mythfilldatabase</bf>. Check +if there were any errors. +<item>Restart your <bf>mythbackend</bf> and <bf>mythfrontend</bf> programs. +</itemize> + +<sect1>Caching support for Schedules Direct +<p>MythTV 0.20.2 or later supports caching of downloaded information from +Schedules Direct, so devices that share a common source do not require +multiple downloads. + +Before beginning, perform a backup of your existing database. See <ref +id="backupdb" name="Saving or restoring the database"> for instructions. + +In the following scenario, assume that you have the following: +<enum> +<item>A PVR-150 MPEG-2 encoder card connected directly to a CATV source. +<item>A PVR-250 MPEG-2 encoder card connected via S-Video to a CATV Set Top Box. +</enum> + +What we are going to do is to create a single lineup at Schedules Direct and +then create two Video Sources which use the same login information but have +different channels associated with them. + +On your Schedules Direct account, create a lineup that has all of the +channels that you can receive. Because we have a Set Top Box (STB), choose +a Digital lineup. Yes, this means that you may have 900 channels in this +lineup, but that's OK. + +Use the Schedules Direct channel editor and unselect any channels that you +can't tune without the STB. This will usually be channels higher than 125, +but check your CATV provider lineup if you're not sure. Once you've +deselected them (using a click on the first channel you can't receive and +then a shift-click on the last channel you can't receive will deselect all +the channels in between those two.) click the Save Changes button at the +bottom of the screen. + +In <bf>mythtv-setup</bf>, create a Video Source with an appropriate name. +"SD-Analog Only" will be used in this example. Click "Retrieve Lineups" +and select the digital lineup you just created at Schedules Direct. + +Click "Finish" to return to the Video sources selector and then press the +ESC key to go back to the main screen. + +Now choose Input Connections. Select the PVR-150 which is connected +directly to the CATV. Set the Video Source to "SD-Analog Only" and click +"Fetch channels from listings source". + +Set the start channel to an appropriate value. + +<bf>NOTE</bf>: There is a bug where the "Fetch" command may not work; you +can tell that the Fetch did not retrieve any channels in one of two ways: in +the text-mode console, you will see a connection to Schedules Direct, but it +doesn't appear to retrieve any channel information: +<tscreen><verb> +2007-08-25 15:03:05.526 New DB DataDirect connection +2007-08-25 15:03:05.526 Connected to database 'mythconverg' at host: localhost +2007-08-25 15:03:05.536 DataDirect: Your subscription expires on 11/23/2007 01:12:10 PM +2007-08-25 15:03:05.707 New DB connection, total: 3 +2007-08-25 15:03:05.707 Connected to database 'mythconverg' at host: localhost +2007-08-25 15:03:05.708 sourceid 2 has lineup type: CableDigital +2007-08-25 15:03:06.623 Data fetching complete. +2007-08-25 15:03:06.624 DataDirect: Deleting temporary files +</verb></tscreen> + +or, the "Please add channels to this source" message in the "Starting +channel" field stays on the screen. + +If either of these happens, save the information on this screen by clicking +the "Finish" button. Exit back to the Input connections screen by pressing +ESC, then select this Input Connection again. This time the Fetch will work +and the "Please add channels to this source" message will disappear. + +If you look at the text-mode console, you'll see this if the channel +retrieval is working: +<tscreen><verb> +2007-08-25 15:04:32.437 New DB DataDirect connection +2007-08-25 15:04:32.437 Connected to database 'mythconverg' at host: localhost +2007-08-25 15:04:32.447 DataDirect: Your subscription expires on 11/23/2007 01:12:10 PM +2007-08-25 15:04:32.622 New DB connection, total: 3 +2007-08-25 15:04:32.622 Connected to database 'mythconverg' at host: localhost +2007-08-25 15:04:32.623 sourceid 2 has lineup type: CableDigital +2007-08-25 15:04:33.418 DataDirect: Adding channel 41 'AMC' (AMC). +2007-08-25 15:04:33.422 DataDirect: Adding channel 32 'A & E Network' (AETV). +2007-08-25 15:04:33.425 DataDirect: Adding channel 66 'Black Entertainment Television' (BET). +2007-08-25 15:04:33.427 DataDirect: Adding channel 180 'Bravo' (BRAVO). +2007-08-25 15:04:33.430 DataDirect: Adding channel 51 'ABC Family' (FAM). +2007-08-25 15:04:33.432 DataDirect: Adding channel 146 'Country Music Television' (CMTV). +2007-08-25 15:04:33.435 DataDirect: Adding channel 39 'CNBC' (CNBC). +2007-08-25 15:04:33.437 DataDirect: Adding channel 36 'Cable News Network' (CNN). +2007-08-25 15:04:33.440 DataDirect: Adding channel 35 'CNN Headline News' (CNNH). +</verb></tscreen> + +Repeat the Input Connection configuration for any other capture devices that +are connected directly to the CATV system. You do not need to click Fetch +once you've done one successful download of the channel information - the +Starting channel should be automatically populated. + +Go back to Schedules Direct and re-enable the channels that you had +previously deselected, then click Save Changes. + +Create a new Video Source, here called "SD-All Digital Channels". Perform +the same "Retrieve Listings" you did before. + +Go back to the Input Connections screen, select the PVR-250 which is +connected to the STB, assign the "SD-All Digital Channels" video source and +perform a retrieve channels. This will pull down the complete channel +listing, but only for <em>this</em> device. + +When <bf>mythfilldatabase</bf> runs, it will cache the "big" download which +is appropriate for the STB, and then copy the information to the channels +that can only be accessed without the STB. But by default +<bf>mythfilldatabase</bf> is going to notice that the "Analog only" video +source is missing the channels that are in the Digital lineup you created at +Schedules Direct, so we need to override the addition of new channels. + +When you run <bf>mythfilldatabase</bf> to populate your database, you'll +need to run it like this: + +<tscreen><verb> +$ mythfilldatabase --remove-new-channels +</verb></tscreen> + +You will also need to modify how the <bf>mythbackend</bf> calls +<bf>mythfilldatabase</bf> when it performs its automatic listings update. + +In <bf>mythfrontend</bf>, select "Setup" -> "General". + +Continue press ENTER until you reach the Mythfilldatabase configuration +screen. In the "mythfilldatabase Arguments" field, type +--remove-new-channels + +then press the TAB key until you reach Finish, then press ENTER to save. +You can then press ESC until you return to the main screen. +</article> +<!-- Revision History + +v0.21.00, 2008-03-10. Initial version for 0.21. Update link to ATSC +devices. Add note that ivtv driver is in kernel. Add note that xbox +mini-distribution site appears dead. Update information on HVR-1600. +Update minimum MySQL version. +v0.21.01, 2008-06-03. Add mythbuntu. +v0.21.02, 2008-06-04. Update minimyth link. +--> + +<!-- +To create documentation, run "make" in the docs/ subdirectory +--> + +<!-- Basic Style Guide for the HOWTO. + +Paths are specified with <tt> + +Program names are specified with <bf> + +Use full close tags, such as </tt> rather than the "/>" shortcut. + +For a URL link, the url= and name= should be the same. This ensures that +users who are reading the text version of the document will see what the URL +is. + +For "Notes", the format is <bf>NOTE</bf>: text here. + +label id's must be contained on one line. If they break across the right +margin the wrapped text will be considered as text and not a destination. + +Don't make a section "a" if there's no section "b". Same for numbers; no +number 1 if there's no number 2, etc. + +Itemized and enumerated items should be full sentences, and should end with +a period. + +All major sections end with a period; subsections don't. + +Dates must be in ISO8601 format YYYY-MM-DD. + +--> diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO.txt b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO.txt new file mode 100644 index 0000000..f89175c --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/mythtv-HOWTO.txt @@ -0,0 +1,9235 @@ + Installing and using MythTV + Robert Kulagowski, mailto:rkulagow@rocketmail.com + <mailto:rkulagow@rocketmail.com> + 2008-06-04, v0.21.02 + + Initially, installation of MythTV seems like a huge task. There are + lots of dependencies, and various distributions seem to do the same + thing different ways. This document will attempt to give general + installation instructions, as well as including distribution-specific + instructions where necessary. + ______________________________________________________________________ + + Table of Contents + + + + 1. First things first. + 1.1 What is MythTV? + 1.2 QuickStart + 1.3 Upgrading from previous versions + 1.4 How to obtain this document / PDF versions of this document + 1.5 Books about MythTV + 1.6 Document conventions + 1.7 Mailing lists / getting help + 1.8 IRC + 1.9 Bug database + 1.10 Contributing to this document + + 2. Introduction. + 3. Checking prerequisites. + 3.1 Hardware + 3.1.1 CPU Type and Speed + 3.1.2 Memory + 3.1.3 Hard Disk(s) + 3.1.4 Filesystems + 3.1.5 Video Capture Device + 3.1.5.1 Frame Grabbers. + 3.1.5.2 Hardware MPEG-2 encoders. + 3.1.5.3 DVB capture cards. + 3.1.5.4 HDTV. + 3.1.5.5 Firewire. + 3.1.5.6 DBoxII or other devices running Neutrino + 3.1.5.7 USB Capture Devices. + 3.1.5.8 IP Recorder (RTSP, RTS, UDP) + 3.1.6 Hardware known NOT to work and other issues + 3.1.7 Sound card + 3.1.8 Video Display Card + 3.1.9 Cards with TV-out + 3.1.9.1 ATI + 3.1.9.2 NVIDIA + 3.1.9.3 Hauppauge PVR-350 + 3.1.9.4 Other Options + 3.1.10 External Adapters + 3.2 Software + 3.2.1 Pre-compiled packages + 3.2.1.1 Red Hat Linux / Fedora Core + 3.2.1.2 Mandriva + 3.2.1.3 Debian + 3.2.2 Manual installation + 3.2.3 Command-line installation + 3.2.3.1 Mandriva + 3.2.3.2 Gentoo. + 3.2.3.3 Debian. + + 4. System Configuration Requirements for Compiling MythTV. + 4.1 Software requirements for compiling MythTV + 4.1.1 General requirements + 4.2 Shared-Library requirements for MythTV + 4.2.1 Modifying /etc/ld.so.conf + 4.3 Environment variable requirements for MythTV + 4.3.1 General requirements + 4.3.1.1 QT libraries and binaries + 4.3.2 Distribution-Specific Notes + 4.3.2.1 Mandriva + 4.3.3 Device Permissions + + 5. Downloading and compiling. + 5.1 Building LAME + 5.2 XMLTV + 5.2.1 Red Hat Linux and Fedora Core: + 5.2.2 Mandriva + 5.2.3 Manual installation + 5.3 Configuring the Schedules Direct service + 5.4 Manually building MythTV + 5.4.1 Enabling real-time scheduling of the display thread. + 5.4.1.1 rlimits + 5.4.1.2 realtime module + 5.4.1.3 run as root option (not safe) + 5.4.2 Frontend-only configuration + 5.5 Gentoo + + 6. MySQL. + 6.1 Distribution-specific information + 6.1.1 Mandriva + 6.1.2 Red Hat Linux and Fedora Core + 6.1.3 Gentoo + 6.2 Setting up the initial database + 6.2.1 Mandriva and Red Hat Linux/Fedora Core + 6.2.2 Debian 3.0 + 6.2.3 Gentoo + 6.2.4 Modifying access to the MySQL database for multiple systems + + 7. Configuring Sound. + 7.1 Graphically setting up the mixer + 7.1.1 Mandriva and Red Hat Linux/Fedora Core + 7.1.1.1 Using ALSA. + 7.2 Setting the mixer from the command line + + 8. Setting up a remote control. + 8.1 Gentoo + 8.2 Obtaining and compiling lirc + 8.3 Completing the lirc install + 8.4 Additional information for lirc + 8.5 Configuring lirc for use with an IR blaster + + 9. Configuring MythTV. + 9.1 Configuring the Master backend system + 9.1.1 General + 9.1.2 Capture Cards + 9.1.3 Video Sources + 9.1.4 Input Connections + 9.1.5 Channel Editor + 9.1.6 Storage Groups + 9.1.6.1 Introduction. + 9.1.6.2 How to use Storage Groups. + 9.1.6.3 Migrating to Storage Groups. + 9.1.6.4 Advanced: Algorithm used by the Storage Group + 9.2 Post-configuration + 9.3 Configuring a non-master backend + 9.4 Configuring and running mythfilldatabase + 9.4.1 Periodically running mythfilldatabase + 9.5 Grabbing channel icons for Schedules Direct users + + 10. Configuring mythfrontend. + 10.1 General + 10.2 Appearance + 10.3 Program Guide + 10.4 Playback + 10.4.1 Video Filters + 10.4.2 Applying filters + 10.4.3 Currently Available Filters + 10.4.4 Usage Considerations + 10.5 Recording + 10.6 Xbox Frontends + + 11. Using MythTV. + 11.1 Keyboard commands + 11.1.1 mythfrontend + 11.1.2 Watching TV or a recording + 11.1.3 Watching TV only + 11.1.4 LiveTV Browse Mode + 11.1.5 Playback Recording Zoom Mode + 11.1.6 If you have two or more tuner cards + 11.1.7 Watching a recording only + 11.1.8 EPG + 11.1.9 Setting Program or Channel Recording Priorities + 11.1.10 Viewing Scheduled Recordings/Resolving Conflicts + 11.1.11 Viewing Search Listings + 11.1.12 Recording Profiles Setup Screen + 11.1.13 Recording Groups + 11.1.14 Watch Recordings Screen + 11.1.15 Remote Controls + 11.2 Using themes with MythTV + 11.3 Adding DishTV information to the database + 11.4 Adding support for an external tuner + 11.5 Using Shutdown/Wakeup + 11.5.1 A deeper look into the operation + 11.5.2 Setting up the MythTV side of this extension. + 11.5.2.1 Using WOL to wake your Master backend. + 11.5.2.2 Using BIOS wakeup to wake your Master backend. + 11.5.3 Wakeup the MySQL server using WOL + 11.5.4 Tips/Tricks: + 11.6 Controlling the mythfrontend via telnet + + 12. Scheduling Recordings. + 12.1 Record Types + 12.2 Scheduling Options + 12.2.1 Priority + 12.2.2 Duplicates + 12.2.3 Conflicts + 12.2.4 Scheduling decisions + 12.2.5 Reschedule Higher Priorities + 12.2.6 Controlling Your Schedule + 12.3 Storage Options + 12.3.1 Recording Profile + 12.3.2 Recording Group + 12.3.3 ANAME CDATA Storage Groups(REF)REF + 12.3.4 Playback Group + 12.3.5 Auto-Expire + 12.3.6 Episode Limit + 12.4 Post Recording Processing + 12.4.1 Commercial Flagging + 12.4.2 Transcoding + 12.4.3 User Jobs + 12.5 Advanced Recording Options + 12.5.1 Creating Power Search rules with Custom Record + 12.5.2 Getting Started + 12.5.3 How it Works + 12.5.4 Common Tricks and Tips + 12.5.5 Working with SQL + 12.6 Scheduling with more than one Input + 12.6.1 Mutually Exclusive Inputs + 12.6.2 Stations, Channels and Video Sources + 12.6.3 Order of Inputs + 12.6.4 Matching Callsigns + 12.6.5 Using Priorities to Prefer an Input + 12.6.6 Input Priority + 12.6.7 Channel Priority + 12.6.8 Preferred Input + 12.6.9 HDTV Priority + 12.6.10 Custom Priority + + 13. MythPlugins. + 14. MythWeb. + 14.1 Installation and prerequisites + 14.1.1 Mandriva + 14.2 Completing the installation + 14.3 Resetting the key binding table + 14.4 Resetting the theme. + + 15. MythGallery. + 15.1 Installation and prerequisites + 15.2 Using MythGallery + 15.3 Importing Pictures + + 16. MythGame. + 16.1 Setup Directory Structure + 16.2 Download and Install xmame + 16.3 Download extra files + 16.4 Download and Install MythGame. + 16.5 Setup xmame in MythGame + 16.6 Hints: + + 17. MythMusic. + 17.1 Manual installation of prerequisites + 17.2 Mandriva + 17.2.1 Additional options with MythMusic + 17.3 Red Hat Linux 9 + 17.4 Compiling MythMusic + 17.5 Configuring MythMusic + 17.6 Using MythMusic + 17.7 Troubleshooting MythMusic + 17.7.1 When I run MythMusic and try and look up a CD, I get an error message + + 18. MythWeather. + 19. MythVideo. + 20. MythDVD. + 20.1 Manual Compilation of Prerequisites + 20.2 Pre-compiled binaries + 20.3 Running the Myth Transcoding Daemon + + 21. MythNews. + 22. Troubleshooting. + 22.1 Compiling + 22.1.1 Compile errors + 22.1.2 make: *** No rule to make target /usr/lib/qt3/mkspecs/default/qmake.conf', needed by Makefile'. Stop. + 22.1.3 make: *** No rule to make target /mkspecs/default/qmake.conf', needed by Makefile'. Stop. + 22.1.4 Internal Segmentation Fault. + 22.2 Debugging + 22.2.1 MythTV segfaults + 22.2.2 MythTV isn't doing anything + 22.2.3 Debugging with GDB + 22.2.4 MythTV is crashing your system + 22.3 Installing + 22.3.1 When trying to run mythtv-setup, you get an error like this: "mythtv-setup: error while loading shared libraries:" + 22.4 Using + 22.4.1 No programs are displayed in "Watch Recordings" + 22.4.2 MySQL not connecting correctly + 22.4.3 MySQL database is corrupt + 22.4.4 Using a MPEG-2 encoder card and the video appears "jittery" + 22.4.5 Using a MPEG-2 encoder card and the video is jumping up and down + 22.4.6 Screen goes blank but returns when mouse is moved or keyboard is used + 22.5 Miscellaneous + 22.5.1 mythfilldatabase failing + 22.5.2 Fast CPU, choppy or jittery video + 22.5.3 Frontend appears to be slow at jumping / seeking. + 22.5.4 On-screen Display shows incorrect program length. + 22.5.5 Troubleshooting audio + 22.5.6 Mythbackend reports that your card is not reporting full duplex capabilities + 22.5.7 The mythbackend program told me to look at this section + 22.5.8 My remote doesn't work / works sometimes and not others / "ghost" keypresses + 22.5.9 Where's "canada-cable"? + 22.5.10 Channels are off by one + 22.5.11 Mythweb is showing a db_open error when I connect to it + 22.5.12 Mouse pointer disappears when placed over the MythTV windows + 22.5.13 What does "strange error flushing buffer" mean on the console? + 22.5.14 Can't change the channel when watching Live TV. + 22.5.15 Screen goes black when you try to play something + 22.5.16 Poor performance with NVidia cards and XvMC + 22.5.17 Computer is loading a media player application when you insert a CD or DVD + + 23. Miscellaneous. + 23.1 I'd like to watch the files without using MythTV / I'd like to convert the files to some other format + 23.1.1 mythtranscode example + 23.2 Using a different window manager + 23.3 What capture resolution should I use? How does video work? + 23.4 MythTV GUI and X Display Sizes + 23.4.1 X Dimensions + 23.4.2 MythTV Dimensions + 23.4.3 Overscan Dimensions + 23.5 Saving or restoring the database + 23.6 Deleting the MySQL database + 23.7 Moving your data to new hardware + 23.8 btaudio + 23.9 Removing unwanted channels + 23.10 NFS + 23.11 Automatically starting mythfrontend at system boot time + 23.12 Automatically starting mythbackend at system boot time + 23.12.1 Red Hat And Mandriva + 23.12.1.1 Log files + 23.12.1.2 Mandriva + 23.12.2 Gentoo + 23.13 Advanced Backend Configurations + 23.14 Using the transcoder + 23.14.1 Configuring Recording Profiles to Allow Transcoding + 23.14.2 Configure Transcoding Profiles + 23.14.3 Create/Alter Scheduled Recordings to Enable Transcoding + 23.14.4 Manual Transcoding + 23.15 Changing your hostname + 23.16 Can I run MythTV on my TiVo? + 23.17 Can I run MythTV on my ReplayTV? + 23.18 Can a wireless connection be used between the frontend and the backend? + 23.19 How can I burn shows that I have recorded to a DVD? + 23.20 Using the DBoxII within MythTV + 23.21 What do the icons on the Watch Recordings screen mean? + 23.22 What do the letters mean when I change channels? + 23.23 What is the difference between the various Hauppauge PVR models? + 23.24 Changing channels on an external Set Top Box + 23.25 Configuring one machine to flag all commercials + + 24. Example Configurations. + 24.1 Logical Volume Manager (LVM) + 24.1.1 ReiserFS + 24.1.2 ext2 or ext3 + 24.1.3 xfs + 24.2 Advanced Partition Formatting + 24.2.1 Ext2 + 24.2.2 Ext3 + 24.2.3 ReiserFS + 24.2.4 JFS + 24.2.5 XFS + 24.3 Migrating from DataDirect Labs to Schedules Direct + 24.4 Caching support for Schedules Direct + + + + ______________________________________________________________________ + + [1m1. First things first.[0m + + + + [1mNOTE[22m: Please note that I, Robert Kulagowski, am [4mNOT[24m the + author/programmer of the MythTV application! I can not give you + personalized installation support. If you are having issues + installing MythTV you should examine the archives, or post your + question to the MythTV-users mailing list. If you send me "Does + MythTV work with 'X'"? messages - I will simply instruct you to ask + your question on the mythtv-users mailing list. + + [1m1.1. What is MythTV?[0m + + MythTV is a GPL licensed suite of programs that allow you to build the + mythical home media convergence box on your own using Open Source + software and operating systems. MythTV is known to work on Linux and + Mac OS X (PowerPC and Intel). It does not run on Windows. + + MythTV has a number of capabilities. The television portion allows + you to do the following: + + +o You may pause, fast-forward and rewind live Television. + + +o You may install multiple video capture cards to record more than + one program at a time. + + +o You can have multiple servers (called "backends"), each with + multiple capture cards in them. All scheduling is performed by the + Master backend, which arbitrates which recording will be performed + by each device. All recording requests are managed by the Master + backend, so you can schedule a recording from any client. + + +o You can have multiple clients (called "frontends" in MythTV + parlance), each with a common view of all available programs. Any + client can watch any program that was recorded by any of the + servers, assuming that they have the hardware capabilities to view + the content; a low-powered frontend will not be able to watch HDTV, + for example. Clients can be diskless and controlled entirely by a + remote control. + + +o You may use any combination of standard analog capture card, + MPEG-2, MJPEG, DVB, HDTV, USB and firewire capture devices. With + appropriate hardware, MythTV can control set top boxes, often found + in digital cable and satellite TV systems. + + +o Program Guide Data in North America is downloaded from + schedulesdirect.org, a non-profit organization which has licensed + data from Tribune Media Services. This service provides almost two + weeks of scheduling information. Program Guide Data in other + countries is obtained using XMLTV. MythTV uses this information to + create a schedule that maximizes the number of programs that can be + recorded if you don't have enough tuners. + + +o MythTV implements a UPNP server, so a UPNP client should + automatically see content from your MythTV system. + + Other modules in MythTV include: + + +o MythArchive, a tool to create DVDs + + +o MythBrowser, a web browser + + +o MythControls, an application to configure your remote control + + +o MythFlix, a Netflix module + + +o MythGallery, a picture-viewing application + + +o MythGame + + +o MythMusic, a music playing / ripping application which supports MP3 + and FLAC + + +o MythNews, a RSS news grabber + + +o MythPhone, phone and videophone using SIP. + + +o MythVideo, DVD ripper and a media-viewer for content not created + within MythTV + + +o MythWeather + + +o MythWeb, which allows you to control your MythTV system using a web + browser. With MythWeb, you can schedule and delete recordings, + change keybindings and more. With proper security, you may even + schedule a program over the Internet and have it immediately acted + on by the Master backend. + + [1m1.2. QuickStart[0m + + Custom mini-distributions are available to make it easier to install + MythTV. A mini-distribution removes many of the "general purpose" + workstation / server software packages that may be installed by + default if you use one of the big-name OS packages. + + See http://mysettopbox.tv <http://mysettopbox.tv> if you'd like to + install a custom version of Knoppix optimized for MythTV. + + See http://www.minimyth.org <http://www.minimyth.org> if you'd like to + install MythTV onto a diskless system. + + See http://bit.blkbk.com <http://bit.blkbk.com> if you'd like to + install MythTV on a Xbox. [1mNOTE[22m: Site appears unmaintained. + + See http://wilsonet.com/mythtv/ <http://wilsonet.com/mythtv/> for + instructions tailored to RedHat's Fedora Core distribution. + + See http://www.mythbuntu.org <http://www.mythbuntu.org> if you'd like + to install a customized version of Ubuntu optimized for MythTV. + + There is a MythTV wiki at http://wiki.mythtv.org + <http://wiki.mythtv.org>. + + If you are installing this version for Schedules Direct support, + please see the ``Migrating from DataDirect Labs to Schedules Direct'' + section for additional information. + + + [1m1.3. Upgrading from previous versions[0m + + The upgrade from previous versions should be transparent. Any changes + to the database structure should be applied automatically. + + It is [4mstrongly[24m recommended that you back up your database before + installing a new version of MythTV. + + See ``Saving or Restoring the database'' for instructions. + + + [1m1.4. How to obtain this document / PDF versions of this document[0m + + This HOWTO document is maintained at the primary MythTV website: + http://www.mythtv.org <http://www.mythtv.org> by Robert Kulagowski + <mailto:rkulagow@rocketmail.com>. + + This document is available as a single-page HTML document at + http://www.mythtv.org/docs/mythtv-HOWTO-singlehtml.html + <http://www.mythtv.org/docs/mythtv-HOWTO-singlehtml.html> or as a PDF + at http://www.mythtv.org/docs/mythtv-HOWTO.pdf + <http://www.mythtv.org/docs/mythtv-HOWTO.pdf>. + + This HOWTO is for MythTV v0.21 + + Release notes for this version may be found in the MythTV Wiki at + http://www.mythtv.org/wiki/index.php/Release_Notes_-_0.21 + <http://www.mythtv.org/wiki/index.php/Release_Notes_-_0.21> + + + [1m1.5. Books about MythTV[0m + + If you would like to purchase a book specifically about MythTV: + + + +o Hacking MythTV, ISBN 978-0470037874 by Wilson, Tittel, Wright and + Korelc + + +o Practical MythTV: Building a PVR and Media Center PC, ISBN + 978-1590597798 by Smith and Still + + + [1m1.6. Document conventions[0m + + The following conventions are used throughout this document. + [1mboldface [22m- used for program names. + typewriter - used for program paths. + [4memphasis[24m - Pay attention here. + + + + Pay more attention. + + + + Ignore at your own peril. + + + + Feature that has been added to SVN (subversion, a revision control system) + but is not available in the current release. + + + + [1m1.7. Mailing lists / getting help[0m + + It's recommended that you join the user list at + http://www.mythtv.org/mailman/listinfo/mythtv-users + <http://www.mythtv.org/mailman/listinfo/mythtv-users>. The developer + list is at http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev + <http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev>. Please keep + the developer list strictly for development-related issues. + + Searchable archives for the lists are available at + http://www.gossamer-threads.com/lists/mythtv/ <http://www.gossamer- + threads.com/lists/mythtv/>. + + + [1m1.8. IRC[0m + + There are two IRC channels dedicated to MythTV which can be found on + irc.freenode.net + + +o mythtv + + +o mythtv-users + + The mythtv channel is where the developers discuss code. It is [4mnot[24m a + user-support channel. Please don't ask non-development related + questions there. + + + + Really. Even if there's no one in the mythtv-users IRC group or everyone + seems to be ignoring you. + + + [1m1.9. Bug database[0m + + If you feel you need to contribute to a bug database, use the MythTV + bug ticketing system at http://svn.mythtv.org/trac + <http://svn.mythtv.org/trac>. + + Good entries will contain the following: + + 1. Qt version + + 2. Linux distribution + + 3. gcc version + + 4. the last entry in config.log to detail how you compiled + + 5. MythTV version numbers ([4me.g.[24mfrom mythfrontend --version) + + 6. Hardware + + 7. How you are able to reproduce the bug + + See the instructions on how to debug in ``Section 22''. + + The bug database is not a chat room, so restrict your entries to what + is relevant. It's also not a repository of feature requests; a + feature request without an accompanying patch file to implement that + feature will be quickly closed. There is a feature wishlist on the + wiki at http://www.mythtv.org/wiki/index.php/Feature_Wishlist + <http://www.mythtv.org/wiki/index.php/Feature_Wishlist>. There is no + guarantee that anything on the wishlist will ever get code written to + implement it. + + If a developer closes out your bug, it's likely you didn't provide + enough information. Don't re-open a bug without providing additional + information. + + + [1m1.10. Contributing to this document[0m + + Contributions to the HOWTO are welcome, especially if you find a + grammatical or spelling error, or if the wording of something is just + plain confusing. + + If you'd like to make a new contribution, create a ticket at + http://svn.mythtv.org/trac <http://svn.mythtv.org/trac> and click "New + Ticket". The type should be set to "patch" and the owner set to + "rkulagow" to ensure that I see your contribution. + + Please send it as either SGML or as plain text. [4mNO[24m [4mHTML[24m. The source + used to create the HOWTO is in SGML / Linuxdoc. Do not be afraid of + SGML! A quick look at the source of this HOWTO will show that it is + not difficult, because there aren't that many tags to worry about, so + at least [4mtry[24m to submit as SGML. See the Linuxdoc HOWTO at + http://www.tldp.org/HOWTO/Howtos-with-LinuxDoc.html + <http://www.tldp.org/HOWTO/Howtos-with-LinuxDoc.html> for information + on the linuxdoc format itself, or look at the mythtv-HOWTO.sgml file + as an example. + + To create the actual patch, run [1mdiff -u origfilename newfile >[0m + [1mdoc.patch [22mand attach your contribution to the trac ticket. + + + [1m2. Introduction.[0m + + This HOWTO document will focus on manually building MythTV in a North + American environment. If you have installation instructions for a + different region or Linux distribution, please send them to the author + so that it can be included in other versions of this document. + + + [1m3. Checking prerequisites.[0m + + You must ensure that any firewalls (either hardware, or a software + firewall installed by your distribution) will not block access to the + ports that will be used by the MythTV clients and servers on the + "inside" LAN. The ports for MySQL (TCP port 3306) and mythbackend + (TCP ports 6543 and 6544) must be open. It is [4mstrongly[24m recommended + that you do [4mnot[24m expose the MythTV and MySQL ports to the Internet or + your "Outside" LAN. + + + [1m3.1. Hardware[0m + + Hardware selection is a complex topic, one this HOWTO will only + discuss briefly and in general terms. The following subsections offer + some general guidance but stop short of offering specific + recommendations. + + For a good MythTV experience, you must understand that MythTV + exercises your hardware more than a typical desktop. Encoder cards + generate DMA across the PCI bus. The CPU is busy encoding / decoding + video. Hard drives are constantly reading and writing data. Building a + MythTV system on older / "spare" hardware may be an exercise in + frustration and can waste many hours of valuable time. + + For more detail about actual configurations that others have used, + Mark Cooper has setup a hardware database at + http://pvrhw.goldfish.org/ <http://pvrhw.goldfish.org/>. The website + will let you browse what other users have reported as their hardware + configuration, and how happy they are with the results. + + If you have specific questions about the suitability of specific + hardware choices, you can consult the archives of the mythtv-users + mailing list at http://www.gossamer-threads.com/lists/mythtv/ + <http://www.gossamer-threads.com/lists/mythtv/> or post a question to + the list. + + [1m3.1.1. CPU Type and Speed[0m + + Selection of CPU type and speed is one of the trickiest elements of + hardware selection, mainly because there are so many tradeoffs which + can be made. For example, if you have plenty of CPU, you can use + higher bitrates or capture sizes, etc. + + MythTV has two modes of operation. First, it can function as a + software video encoder, which means that it uses a fairly generic + "dumb" video capture card to get frames of video, encodes them using + the CPU on your motherboard and writes them to disk. High-end video + capture cards and devices like the TiVo and ReplayTV have dedicated + encoder chips which use specialized hardware to convert the video + stream to the MPEG-2 format without using the motherboard CPU. The + main CPU has the responsibility of running the Operating System and + reading and writing the encoded frames to the disk. These tasks have + fairly low CPU requirements compared to encoding video, which is why a + device like a Series 1 TiVo can run with only 16MB of RAM and a 54MHz + CPU. + + There are many variables that go into the question: "How fast a CPU do + I need to run MythTV"? Obviously, the faster your CPU, the better + your experience will be with MythTV. If you are using the software + MPEG-4 encoder and performing the "Watch TV" function, where the CPU + is both encoding and decoding video simultaneously to allow Pause, + Fast Forward and Rewind functions for live TV requires more CPU then + just encoding or decoding. MythTV also supports multiple encoder + cards in a single PC, thereby increasing the CPU requirements if you + plan on simultaneously encoding multiple programs. As a general + guideline, plan on 1GHz per encoder if you are doing software-based + encoding, less if you are using a hardware-based encoder. + + Here are a few data points: + + +o A PIII/733MHz system can encode one video stream using the MPEG-4 + codec using 480x480 capture resolution. This does not allow for + live TV watching, but does allow for encoding video and then + watching it later. + + +o A developer states that his AMD1800+ system can [1malmost [22mencode two + MPEG-4 video streams and watch one program simultaneously. + + +o A PIII/800MHz system with 512MB RAM can encode one video stream + using the RTjpeg codec with 480x480 capture resolution and play it + back simultaneously, thereby allowing live TV watching. + + +o A dual Celeron/450MHz is able to view a 480x480 MPEG-4/3300kbps + file created on a different system with 30% CPU usage. + + +o A P4 2.4GHz machine can encode two 3300Kbps 480x480 MPEG-4 files + and simultaneously serve content to a remote frontend. + + The second mode of operation is where MythTV is paired with a + hardware-based video encoder, such as a Matrox G200 or a Hauppauge + WinTV-PVR-150/250/350/500. In this mode, because the video encoding + is being done by a dedicated video processor, the host CPU + requirements are quite low. See the ``Video Capture Device'' section + for details. + + The price differential between a frame grabber and a card that + implements hardware MPEG-2 encoding, such as the Hauppauge PVR-x50 + series, is now less than $30 US. Primary development in MythTV has + transitioned to supporting MPEG-2 capture devices and HDTV, so if + given the option, go with the hardware MPEG-2 encoder. + + If you have a Via M10000 series or a Hauppauge PVR-350, MythTV can use + the hardware-based video decoder for playback, which further reduces + CPU requirements. + + + [1m3.1.2. Memory[0m + + A MythTV host that is both a backend and a frontend and using software + encoding with a single capture card should run adequately in 256MB of + RAM. Additional RAM above 256MB will not necessarily increase + performance, but may be useful if you are running multiple encoders. + + + [1m3.1.3. Hard Disk(s)[0m + + Encoded video takes up a lot of hard disk space. The exact amount + depends on the encoding scheme, the size of the raw images and the + frames per second, but typical values for MythTV range from 700 + megabytes/hour for MPEG-4, 2 GB/hour for MPEG-2 and RTjpeg and 7 + GB/hour for ATSC HDTV. + + + + [1mNOTE[22m: You [4mmust[24m use DMA for hard drive access to prevent + choppy or jittery video. Not all distributions enable DMA at boot + time. See the Troubleshooting Section for ``instructions'' on how to + do this. + + Writing video to disk is sensitive to timing issues; RTjpeg requires + less CPU with the tradeoff being larger files and needing to write to + the disk faster. MPEG-4 requires more CPU, but the files are smaller. + At the default resolution, MPEG-2 creates the largest files of all + with almost no CPU impact. + + See the Troubleshooting ``section'' for more information. + + + [1m3.1.4. Filesystems[0m + + MythTV creates large files, many in excess of 4GB. You [4mmust[24m use a 64 + or 128 bit filesystem. These will allow you to create large files. + Filesystems known to have problems with large files are FAT (all + versions), and ReiserFS (versions 3 and 4). + + Because MythTV creates very large files, a filesystem that does well + at deleting large files is important. Numerous benchmarks show that + XFS and JFS do very well at this task. You are [4mstrongly[24m encouraged to + consider one of these for your MythTV filesystem. JFS is the absolute + best at deletion, so you may want to try it if XFS gives you problems. + MythTV .21 incorporates a "slow delete" feature, which progressively + shrinks the file rather than attempting to delete it all at once, so + if you're more comfortable with a filesystem such as ext3 (whose + delete performance for large files isn't that good) you may use it + rather than one of the known-good high-performance file systems. + There are other ramifications to using XFS and JFS - neither offer the + opportunity to shrink a filesystem; they may only be expanded. + + + + [1mNOTE[22m: You [4mmust[24m [4mnot[24m use ReiserFS v3 for + your recordings. You will get corrupted recordings if you do. + + Because of the size of the MythTV files, it may be useful to plan for + future expansion right from the beginning. If your case and power + supply have the capacity for additional hard drives, read through the + ``LVM'' and ``Advanced Partition Formatting'' sections for some + pointers. + + + [1m3.1.5. Video Capture Device[0m + + In order to capture video, MythTV will need one or more video capture + devices with Linux drivers. There are a number of classes of hardware + available for capturing video. + + [1m3.1.5.1. Frame Grabbers.[0m + + This class of card is the simplest and is usually the cheapest. There + is no on-board encoding of the analog video; hardware known as a + Digital-Analog Converter (DAC) takes the video and presents it to the + computer in an essentially raw digital form. + + For a list of video capture cards known to work with Linux, please see + /usr/src/linux/Documentation/video4linux/bttv for a partial listing; + even if your specific card is not listed, it may be that the vendor is + actually using a standard reference design and placing their own name + on it. See the video4linux mailing list + (https://listman.redhat.com/mailman/listinfo/video4linux-list + <https://listman.redhat.com/mailman/listinfo/video4linux-list>) for + more information and for specific hardware questions. + + The most common inexpensive cards available use the Bt848, Bt878 or + CX2388x series of video capture chips; examples are the "Hauppauge + WinTV Go" card and the "AverTV Desktop PVR" card, both of which use + the bttv kernel module. + + + ______________________________________________________________________ + NOTE: The ATI TV Wonder series and the ATI All-in-Wonder series of cards + are not the same. The All-in-Wonder cards will not work with MythTV. + ______________________________________________________________________ + + + + [1mNOTE[22m: The ATI All-in-Wonder cards (which are not the same + as the ATI TV Wonder, TV Wonder VE or TV Wonder Pro) [4mwill[24m [4mnot[24m work as + a MythTV capture device because the GATOS http://gatos.sourceforge.net + <http://gatos.sourceforge.net> drivers that are available provide only + a limited subset of the V4L API. The TV Wonder series of cards are + supported by the Bt8x8 Video4Linux driver. + + After you have installed a suitable capture device, you can check that + the kernel sees it with lspci. Look for an entry labeled "Multimedia + video controller". To get more detailed information about the card, + use lspci -v or lspci -vv. Ensure that your system is loading the + bttv modules by typing: + + + # lsmod |grep bttv + + + + You want to see the bttv module listed. + + [1m3.1.5.2. Hardware MPEG-2 encoders.[0m + + While inexpensive video-capture cards simply capture raw frames, + leaving encoding to software, some higher-end cards incorporate + hardware-based encoding. Using either a G200 MJPEG encoder card, or a + MPEG-2 encoder card supported by the IvyTV project + http://ivtvdriver.org <http://ivtvdriver.org/> such as the Hauppauge + PVR-150/250/350/500, Avermedia M179, Hauppauge "Freestyle" or Yuan + M600 cards will allow you to use dedicated hardware encoders rather + than your CPU. (The PVR-350 can simultaneously be used as an output + device.) Using the on-board MPEG-2 encoder greatly reduces the CPU + requirements for encoding. + + The ivtv driver was incorporated into the Linux kernel starting at + v2.6.22. + + There is a Beta driver for the HVR-1600 card at + http://www.ivtvdriver.org/index.php/Cx18 + <http://www.ivtvdriver.org/index.php/Cx18> + + [1mNOTE[22m: Motherboards with the Via chipset are notoriously bad with DMA + and have caused numerous issues with ivtv, including hard locks. See + the ivtv website http://ivtvdriver.org <http://ivtvdriver.org> for the + latest information on what works and what doesn't. + + Here are some data points for encoding: + + +o A Celeron 450 uses 2% CPU for encoding a 480x480 16Mbps MPEG-2 + stream. + + Here are some data points for decoding: + + + +o An Athlon 1800XP can decode a 720x480 8Mbps MPEG-2 file using 10% + CPU + + +o An Athlon 1GHz can decode a 720x480 16Mbps MPEG-2 file using 30-50% + CPU, can decode a 480x480 16Mbps MPEG-2 using 30% CPU and + approximately 30% for Live TV at 416x480. + + +o A P3-550 can decode a 480x480 16Mbps MPEG-2 file with 55% CPU. + + +o A Celeron 450 (no SSE) can decode a 480x480 16Mbps MPEG-2 file with + 80% CPU. + + + [1m3.1.5.3. DVB capture cards.[0m + + DVB is a video standard primarily found in Europe (where it comes in + DVB-C, DVB-T and DVB-S varieties for Cable, Terrestrial and Satellite) + and is also used as the programming interface for HDTV capture cards + in Linux. To see if your DVB card is supported, see the list of cards + in the "Supported Hardware" section of the DVB Wiki at + http://www.linuxtv.org/wiki/index.php/Main_Page + <http://www.linuxtv.org/wiki/index.php/Main_Page> for more + information. + + In the United States, you may use a card such as the TwinHan to obtain + unencrypted Free-To-Air satellite channels. See + http://www.lyngsat.com/ <http://www.lyngsat.com/> for the types of + content which is available. + + + [1m3.1.5.4. HDTV.[0m + + There are a number of HDTV cards with Linux drivers which are known to + operate in the United States; a complete list of cards with DVB + drivers can be found at + http://www.linuxtv.org/wiki/index.php/ATSC_Devices + <http://www.linuxtv.org/wiki/index.php/ATSC_Devices> Some cards + support capture of unencrypted digital cable TV (utilizing QAM256), + others will only work with Over The Air (aka "OTA") signals captured + with an antenna (with 8VSB). + + Cards that have been reported to work include: + + +o pcHDTV HD-2000, Air2PC PCI rev 1-3 (8VSB only) + + +o SiliconDust HDHomeRun (8VSB, QAM256) + + +o pcHDTV HD-3000/5500 (8VSB, QAM256) + + +o Air2PC HD-5000 (8VSB, QAM256) + + +o DViCO Fusion HDTV Lite/Gold 5 (8VSB, QAM256) + + [1mNOTE[22m: There are no known consumer-level capture devices which will + allow you to capture the HDTV output (DVI, HDMI, VGA, YPbPr / + Component) from a set-top box commonly found with digital cable + systems or satellite systems. [4mNone[24m of the capture devices listed above + perform any encoding; they merely allow your computer to save a copy + of a HDTV stream which has already been converted to MPEG-2 at the + broadcast facility. + + [1mNOTE:[22m: All of the cards listed above (except for the HD-2000 and + HDHomeRun) should be configured as DVB cards. The HD-2000 can be + configured as a pcHDTV card if you use the V4L drivers from + http://www.pchdtv.com <http://www.pchdtv.com> and use Linux kernel + 2.6.9 or earlier. With kernel 2.6.10 and higher it must be configured + as a DVB card, but you lose access to the second antenna input in ATSC + mode. The HDHomeRun should be configured as two HDHomeRun cards, one + for each tuner. + + To playback HDTV content, plan on a powerful CPU. "How powerful?" + depends on a number of factors, such as the capture resolution, + whether the video is progressive or interlaced, and whether your + display card has hardware-assist support for Linux. + + The Simple Answer: Once you are in the 3.2 Ghz P4-class of CPU you + should have no issues with viewing HDTV. + + + The Complicated Answer: + + For 720p content (1280x720), a 2.4GHz P4 should be sufficient. + + For 1920x1080i->1920x1080p with the better deinterlacing methods done + in real time a 2.4GHz CPU is taxed, but should work if you use "Bob + and Weave" deinterlacing, or if you have an NVIDIA card with MPEG-2 + hardware acceleration. If you enable the hardware acceleration, you + may be able to use a 1.8GHz processor. + + + [1m3.1.5.5. Firewire.[0m + + You may use the Firewire output of the Motorola DCT6200 or the SA3250. + If your provider uses 5C encryption on a particular channel, you won't + be able to get any content. + + + [1m3.1.5.6. DBoxII or other devices running Neutrino[0m + + You may use the Ethernet port of an DBoxII or a similar device to + capture MPEG2. Your set top box has to be running the Neutrino GUI. + + + [1m3.1.5.7. USB Capture Devices.[0m + + The Plextor ConvertX PVR devices are supported through Linux drivers + available from http://www.plextor.com/english/support/LinuxSDK.htm + <http://www.plextor.com/english/support/LinuxSDK.htm>. MythTV uses the + Plextor to capture hardware encoded MPEG-4, so the host CPU + requirements are low. + + Hauppauge WinTV-PVR-USB2 (driver available at + http://www.isely.net/pvrusb2/ <http://www.isely.net/pvrusb2/>) + emulates a PVR-x50 card. + + + [1m3.1.5.8. IP Recorder (RTSP, RTS, UDP)[0m + + MPEG-2, MPEG-4 and H.264 internet TS stream recording is supported + using the IPTV recorder in MythTV. This recorder expects the channels + to be supplied as a m3u playlist. If your DSL/Fiber provider supplies + television service, but does not provide a m3u playlist for the + channels, you can construct one for your own use. You do not need to + download it from the same server as the streams themselves, and can + also read it from a file if this is more convenient. + + [1mNOTE[22m: Some DSL providers only allow you to use one recorder at a time, + so you may need to limit yourself to one recorder in MythTV and turn + off any set top box the cable provider sold or rented to you with your + service. This limitation is independent of the bandwidth you have + purchased. + + + [1m3.1.6. Hardware known NOT to work and other issues[0m + + + +o Hauppauge WinTV-D or -HD (no driver) + + +o Hauppauge WinTV-USB series + + +o Hauppauge WinTV-PVR-usb (model 602), or WinTV-PVR-PCI (model 880) + cards (no driver - this is not the PVR-250/350 series of cards + supported by the IvyTV driver) + + + +o ATI All-in-Wonder series + + + [1m3.1.7. Sound card[0m + + The system needs a sound card or an on-board equivalent on the + motherboard to play back and in most cases, to record sound. Any sound + card that can be operated by the ALSA (Advanced Linux Sound + Architecture) kernel modules will work with MythTV. However, some + cards and drivers will provide better quality or compatibility than + others. In particular, many audio devices included on motherboards + can be problematic. + + The usual practice for capturing the audio associated with the video + is to run a cable from an audio output on the video capture card to + the Line input on a sound card. However, some video capture cards + provide on-board audio capabilities that work with the kernel btaudio + module instead, thereby eliminating the need for a cable. This is + useful if you will be using multiple capture cards in a single + chassis, since each capture card will not need its own sound card. + Note that a separate sound card is still required for playback when + using btaudio, and that often the audio recorded in this way will be + mono only. See the ``btaudio'' section for more information. + + + + [1mNOTE[22m: Analog video capture cards are the only ones which + require a soundcard for capturing audio. DVB, HDTV, and other + hardware encoder cards all provide a combined audio / video stream. + + + + [1mNOTE[22m: Plugging a Line-level device into the Mic input is + not recommended. Line-level devices have higher voltages and can + damage the sound card. In addition, even if it doesn't break your + card, you will be getting Mono sound. See the Linux MP3 HOWTO at + http://www.tldp.org/HOWTO/MP3-HOWTO.html + <http://www.tldp.org/HOWTO/MP3-HOWTO.html> for additional information. + + + [1m3.1.8. Video Display Card[0m + + MythTV will work with just about any video card. However, it is + highly recommended that you use a card which supports XVideo (XV) + extensions. If your card does not support XV, color conversion and + scaling will be performed by your CPU rather than the video card. + This is very CPU and memory intensive and will often result in dropped + frames and a corresponding degradation of quality. Check the X + documentation for details if you are uncertain about your preferred + card. You may also run xvinfo; look for your video card to be listed + as one of the adapters. + + + If you want to use MythTV with a standard television, you will need a + physical connection from your video card to your TV set, which can + either be a TV-out port on the card itself or an external adapter that + converts the VGA signal to an appropriate video signal. "Appropriate" + depends on a number of factors, such as video standard (NTSC vs. PAL), + the type of input connection (Composite vs. SVideo), etc. + + Note that with some video cards and X drivers, XVideo extensions are + only supported on the VGA output, and not on the TV output. + + + [1m3.1.9. Cards with TV-out[0m + + The next section deals with a number of cards that are known to have + TV-out ports. The list is unlikely to be complete, so if you know of + others, please post a message to the mythtv-users mailing list so the + information can be included in future versions of the HOWTO. The list + is organized by manufacturer. + + Reports here are based on what users of the cards have posted on the + mythtv-users mailing list, so if you need configuration details, + please search the archives at http://www.gossamer- + threads.com/lists/mythtv/ <http://www.gossamer- + threads.com/lists/mythtv/> using the card name in your search string. + + + [1m3.1.9.1. ATI[0m + + ATI makes many cards with TV-out capability, but only offers Linux + drivers for Radeon 8500 and above cards. See the Drivers and Software + section of http://www.ati.com <http://www.ati.com/> for the driver and + additional information. + + The enhanced ati.2 X driver created by the GATOS + http://gatos.sourceforge.net <http://gatos.sourceforge.net> project + offers some support for TV-out on other ATI cards, but only in its + "experimental" version, available through CVS. There have been reports + from people who say they have made this driver work with one or + another ATI card. For example, Bruce Markey <mailto:bjm@lvcm.com> + writes (on the mythtv-users mailing list): "I got this to work. You + can quote me on that. I've used TV-out on several models of ATI cards + both All-In-Wonder and regular cards with TV-out." See the + "Adventurous Setup" section of + http://gatos.sourceforge.net/watching_tv.php + <http://gatos.sourceforge.net/watching_tv.php> for details. Also see + http://www.retinalburn.net/linux/tvout.html + <http://www.retinalburn.net/linux/tvout.html> for more information. + + + [1m3.1.9.2. NVIDIA[0m + + Some NVIDIA cards with TV-out can be run using the standard nv driver + in X, combined with the userspace application [1mnvtv [22mto control the TV- + out port. See http://sourceforge.net/projects/nv-tv-out/ + <http://sourceforge.net/projects/nv-tv-out/> for details. Recent + versions of the NVIDIA driver have better support for overscan and + other features useful with TV-Out, so the [1mnvtv [22mapplication may not be + required. + + Some NVIDIA cards can be run with a proprietary NVIDIA X driver made + available by NVIDIA. See http://www.nvidia.com/object/unix.html + <http://www.nvidia.com/object/unix.html> for more information. + + [1mNOTE[22m: It's strongly recommended that you use the proprietary NVIDIA + drivers; they have excellent support for XvMC and ship with a good + configuration utility. XvMC provides MPEG-2 hardware acceleration, + which is important if you want to display HDTV. + + + [1m3.1.9.3. Hauppauge PVR-350[0m + + MythTV supports the TV-out and MPEG-2 decoder functions in the IvyTV + driver. + The PVR-350 is unique amongst the Hauppauge PVR-x50 cards in that it + also supports audio output, but you need to connect that audio output + to something. There are two courses of action you may take: + + 1. Take the audio output from the PVR-350 and plug it into an input on + a sound card on your machine. You may then use MythTV's internal + audio controls. + + 2. Take the audio output from the PVR-350 and connect it directly to + your television / audio system. You must indicate that you are + using external audio control on the PVR-350 setup page. + + + [1m3.1.9.4. Other Options[0m + + Some devices with on-board TV-out capability, such as Xboxes converted + to Linux and some laptops can be used as MythTV frontends to display + on a television screen. Please consult the mythtv-users mailing list + for messages that report the details of these special arrangements. + + + [1m3.1.10. External Adapters[0m + + External adapters convert standard VGA output to a form suitable for + display on a television. The output format varies by region, since + different countries have different TV standards. People on the mythtv- + users list have mentioned these adapters: + + + +o AITech Web Cable Plus, powered by external transformer or takes + power from PS/2 keyboard connector, support resolutions up to + 1024x768, outputs composite and SVideo, provides position + adjustment. + + +o Averkey lite, powered by a USB port, has Composite, SVideo, YPbPr + outputs; pan, brightness, overscan/underscan controls; supports up + to 1024x768 outputs; and supports PAL and NTSC. + + +o ADS TV Elite XGA + + +o AverKey iMicro (comments are generally favorable) + + +o AITech Web Cable (comments are generally unfavorable, different + than the "Plus" version above) + + +o TVIEW Gold (mentioned once, favorably) + + + [1m3.2. Software[0m + + There are a few ways of installing programs on Linux systems; you can + either use a pre-compiled package, or install from a tarball after + satisfying any prerequisites. + + + + [1mNOTE[22m: you must have the MySQL database software installed on a + system to store the master database. This does not necessarily mean + that MySQL must run on one of the MythTV boxes. The minimum MySQL + version is 5.0. + + + + [1m3.2.1. Pre-compiled packages[0m + + A number of people have created pre-compiled packages for MythTV that + may make your installation easier. + + + + [1mBIG FAT WARNING[22m: This HOWTO assumes that you have [4mnot[0m + installed MythTV from a package. All example command lines and file + locations are based on the MythTV tarball defaults. Some packagers + have modified the filenames, binaries and file locations to match what + is commonly found in that distribution. Any issues with MythTV + installed via a pre-compiled package [1mMUST [22mbe raised with the packager. + + If you use any of the pre-compiled packages you may not need to + perform any additional configuration steps in this HOWTO. The next + logical step is ``configuring MySQL'', which you may or may not have + to perform. See your package documentation. + + + [1m3.2.1.1. Red Hat Linux / Fedora Core[0m + + The definitive documentation on installing MythTV on Red Hat Linux / + Fedora Core can be found in Jarod Wilson's (mailto:jcw@wilsonet.com + <mailto:jcw@wilsonet.com>) HOWTO at http://wilsonet.com/mythtv/ + <http://wilsonet.com/mythtv/> Just like 3rd-party packages, any 3rd- + party documentation problems should be brought up with the 3rd-parties + (maintainer, lists, bugzillas etc.). The installation instructions + which follow should be used as a guide only; refer to Jarod's guide. + + Red Hat Linux and Fedora Core packages for MythTV and all of its add- + on modules and some themes have been packaged by + mailto:Axel.Thimm@ATrpms.net <mailto:Axel.Thimm@ATrpms.net> and are + available at http://ATrpms.net/topic/multimedia/ + <http://ATrpms.net/topic/multimedia/>. All of the prerequisites for + MythTV (such as XMLTV) are available as RPM packages. If you have + problems with the RPMs, please contact the ATrpms lists at + http://lists.ATrpms.net/ <http://lists.ATrpms.net/> or file a bug + against http://bugzilla.ATrpms.net/ <http://bugzilla.ATrpms.net/>. + + Given the large number of dependent RPMs you are advised to use tools + like apt or yum for automatic retrieval and installation of the + required RPMs. (http://ATrpms.net/install.html + <http://ATrpms.net/install.html>) In this case a special meta-package + called mythtv-suite will allow you to install all of MythTV and its + add-ons, plus all dependencies. + + If you don't have [1mapt [22mor [1myum [22mon your machine, download and install the + atrpms-kickstart package from http://ATrpms.net/name/atrpms-kickstart/ + <http://ATrpms.net/name/atrpms-kickstart/>. Install the package with: + + + # rpm -Uvh atrpms-kickstart* + + + + Then run: + + + + # apt-get update + # apt-get dist-upgrade + # apt-get update + + + + And finally: + + + # apt-get install mythtv-suite + + + + These steps however, do NOT perform the installation of any drivers + required for [1mALSA[22m, capture cards, [1mlirc kernel modules[22m, etc., nor do + they set up your MythTV database. Check http://ATrpms.net/topic/multi- + media/ <http://ATrpms.net/topic/multimedia/> for the drivers you need. + + + [1m3.2.1.2. Mandriva[0m + + Thac has created RPMs for MythTV for Mandriva which may be obtained + from http://rpm.nyvalls.se/ <http://rpm.nyvalls.se/> If you have + problems with the RPMs, please send him email directly at + thac@nyvalls.se <thac@nyvalls.se>. + + [1m3.2.1.3. Debian[0m + + Debian packages for MythTV and most of its add-on modules are + maintained by Christian Marillat mailto:marillat@free.fr + <mailto:marillat@free.fr> and are available at http://www.debian- + multimedia.org/ <http://www.debian-multimedia.org/>. Installation + instructions can be found on those pages as well. All of the + prerequisites for MythTV are available as Debian packages, most of + them from the official Debian archive. + + If you have followed the instructions on the above page you should + have added + + + deb-src http://www.debian-multimedia.org sid main + + + + to your /etc/apt/sources.list file. Running [1mapt-get update [22mand then + executing [1mapt-get build-dep mythtv [22mshould install all the pre- + requisites required to compile MythTV. + + + + [1mNOTE[22m: Due to the requirement for Qt 3.3+, there are no packages for + Debian woody/stable. + + + The Debian packages are configured such that MythTV programs should be + run as the mythtv user, which is automatically created during + installation. This user has access to write new recordings to disk in + the default directory, read and write the database, access the audio + and video devices, and everything else that MythTV needs to do. + + See /usr/share/doc/[4mpackagename[24m/README.Debian for more information, + including copies of the MythTV documentation. The mythtv-doc package + contains a copy of this HOWTO in /usr/share/doc/mythtv-doc. + + [1m3.2.2. Manual installation[0m + + You may use the graphical tools that come with your distribution, or + you can use command-line utilities. Either system will get the job + done, and it all depends on your comfort level with Linux. + + In order to compile MythTV, we need to make sure that the software it + needs is installed. This list includes [1mmysql[22m, [1mgcc[22m, [1mfreetype2-devel[22m, + [1mxorg-xserver-devel[22m, [1mqt-devel [22mand [1mlame[22m. If you're going to use a + remote control with MythTV, you're going to need the [1mcdialog [22mpackage + in order to compile [1mlircd [22mif your distribution doesn't have a pre- + packaged [1mlirc[22m. If you are using [1mXMLTV [22mas a grabber, you will need + [1mperl[22m. + + + ______________________________________________________________________ + NOTE: Qt v3.3 or higher is required. + + NOTE: MythTV DOES NOT WORK with Qt4. + + NOTE: If you are going to be using RPMs to install various + components, you should be aware that not all packages include the necessary + headers for compiling. If you're having trouble compiling, ensure + that you've installed the -devel version of a prerequisite. + ______________________________________________________________________ + + + + [1m3.2.3. Command-line installation[0m + + This section details the various methods for installing prerequisites + from the command line. + + + [1m3.2.3.1. Mandriva[0m + + [1mNOTE[22m: The following instructions should be considered out of date as + of 2006-09-10. If updated instructions are not submitted by the + release of v0.21 of MythTV they will be removed. + + [1murpmi [22mis the simplest tool for installation of packages from the + command line, but properly configuring it can be difficult. The + following website http://easyurpmi.zarb.org/ + <http://easyurpmi.zarb.org/> will allow you to choose a mirror site + and then present the command-line configuration text for that mirror. + You will most likely need to add a "Contrib" mirror to your setup. If + you add a site from the "Penguin Liberation Front", you will be able + to load the lame library without compiling from source. + + Open a shell, and execute the following. You may get asked a number of + questions regarding dependencies. It's best to answer "YES". + + + $ su + # urpmi mysql gcc gcc-c++ freetype2-devel cdialog alsa-utils + # urpmi XFree86-devel perl + # urpmi libqt3-devel libMesaGLU1-devel + + + + ______________________________________________________________________ + NOTE for Mandriva 9.1+ users: execute the following command. + + # urpmi libqt3-mysql + ______________________________________________________________________ + + + However, you might get this when you execute the commands above: + + + everything already installed + + + + In that case, you're ready to move to the next ``section''. Once you + have completed installing the pre-requisites, exit out of the shell + and start a new one to ensure that any environment variables setup by + the installation have a chance to take effect. + + + [1m3.2.3.2. Gentoo.[0m + + [1mNOTE[22m: MythTV does [4mnot[24m run on Qt4. If Qt has not been installed on + your system: Edit /etc/make.conf and locate the "USE" variable. If the + line is commented out, remove the comment. The line should have at + least: + + + USE="mysql alsa" + + + + Next you need to build Qt. If you don't plan on using the ebuilds as + described in the Gentoo section then you also need to install lame. + + + # emerge lame mysql qt + + + + If you have already installed Qt: you will need to rebuild because the + default installation doesn't include MySQL support, a requirement for + MythTV. To enable SQL support, add "mysql" to your USE variable in + /etc/make.conf and rebuild Qt by running + + + # emerge qt + + + + All the necessary files will be downloaded and built. Even on a fast + machine this may take a lot of time if you need to do a full Qt build. + + + [1m3.2.3.3. Debian.[0m + + Build-dependencies for MythTV can be satisfied by adding the following + to your /etc/apt/sources.list + + + + # Christian Marillat's packages (mplayer, lame) + deb http://www.debian-multimedia.org sid main + deb-src http://www.debian-multimedia.org sid main + + + + and executing: + + + # apt-get build-dep mythtv + # apt-get source mythtv --compile + + + + [1m4. System Configuration Requirements for Compiling MythTV.[0m + + Before you compile MythTV from the current source tarball or from + [1msubversion[22m, you may need to modify your system configuration in a few + ways. + + In general, if you install MythTV from pre-packaged binaries for your + Linux distribution/version, you don't need to be too concerned about + the issues in this section of the HOWTO - the install script for the + packages should take care of them. However, this section is still + recommended reading which may help if the packager skipped a step in + their packaging. + + + [1m4.1. Software requirements for compiling MythTV[0m + + [1m4.1.1. General requirements[0m + + MythTV is written in C++ and requires a fairly complete, but standard, + compilation environment, including a recent g++ compiler, make, and + appropriate header files for shared libraries. Any standard Linux + distribution should be able to install a suitable compilation + environment from its packaging system. Section 3.2 of this HOWTO + provides some details of how to install the required environment for + many distributions. + + Subsequent sections of this chapter address the few oddities that you + may have to adjust by hand before you compile MythTV. + + The reference compilation system for MythTV is Ubuntu. + + + [1m4.2. Shared-Library requirements for MythTV[0m + + [1m4.2.1. Modifying /etc/ld.so.conf[0m + + The runtime manager for shared libraries, [1m/lib/ld.so[22m, gets information + about the locations and contents of shared libraries from + /etc/ld.so.cache, a file created by [1mldconfig [22mfrom information in + /etc/ld.so.conf. Because MythTV installs some shared libraries in + /usr/local/lib, that directory needs to be added to the list of + directories for [1mld.so [22mto search when doing runtime linking of + programs, if it is not already there. You do this, as root, by + editing /etc/ld.so.conf, then running [1mldconfig[22m. There are many ways to + do this; one that works is to enter this series of commands: + + + + $ su - + # echo /usr/local/lib >> /etc/ld.so.conf + # /sbin/ldconfig + # exit + $ + + + + [1m4.3. Environment variable requirements for MythTV[0m + + [1m4.3.1. General requirements[0m + + [1m4.3.1.1. QT libraries and binaries[0m + + The compiler needs to be able to locate QT binaries and libraries in + order to compile MythTV. QTDIR needs to be set and the directory + holding the QT binaries needs to be added to your PATH. Your + distribution may already be making these changes as a part of the + installation of the software prerequisites detailed earlier. + + One way to do this is as follows: + + Open a shell and execute the following: + + + $ echo $PATH + /usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/games:/usr/lib/qt3/bin:/home/mythtv/bin:/usr/lib/qt3/bin + $ echo $QTDIR + /usr/lib/qt3 + $ which qmake + /usr/lib/qt3/bin/qmake + + + + For Mandriva, you should see a value like /usr/lib/qt3 for QTDIR and + /usr/lib/qt3/bin should be in $PATH. + + For Gentoo, you should see a value like /usr/qt/3 for QTDIR and + /usr/qt/3/bin should be in $PATH. + + If you don't, do not proceed past this step until you have resolved + this error. You may need to manually specify the QTDIR and PATH at the + shell prompt before compiling. + + Also, check that there has been a link created in /usr/lib/qt3/mkspecs + (/usr/share/qt3/mkspecs for Debian) called default. If not, you'll get + errors during the compile. See the Troubleshooting Section for more + information. + + [1m4.3.2. Distribution-Specific Notes[0m + + [1m4.3.2.1. Mandriva[0m + + The following instructions work for Mandriva using [1mbash [22mas the shell, + and may be applicable for a distribution which uses /etc/profile.d. + + + + [1mNOTE[22m: Mandriva 10 installs a /etc/profile.d/qtdir3.sh + file, but it doesn't include the addition of the PATH variable. If + you're running Mandriva 10, don't create a mythtv.sh file as detailed + below; edit the qtdir3.sh file and add the PATH statement within the + if / fi block. As root, create the following file in /etc/profile.d + The example filename is "mythtv.sh". Use what you feel is appropriate. + + Open a shell, and switch to superuser mode. + + + + [1mNOTE[22m: ^D means press CTRL and d at the same time. + + + $ su + # cd /etc/profile.d + cat > mythtv.sh + export QTDIR=/usr/lib/qt3 + export PATH=$PATH:/usr/lib/qt3/bin + ^D + + # chmod a+x mythtv.sh + # exit + $ exit + + + + The last two commands are to exit out of the shell. This way, when you + next open a shell your new commands will take effect. + + + [1m4.3.3. Device Permissions[0m + + MythTV will need access to the video4linux devices on your system. By + default, your distribution may restrict access to these devices to the + logged-in user, so if you will be automatically starting [1mmythbackend[0m + from a script rather than an interactive terminal session you will + need to make some adjustments. + + [1mNOTE[22m: The following instructions are accurate for Mandriva. + + Check for a file called /etc/security/console.perms. Open the file in + your favorite text editor and look for a line that has: + + + <console> 0600 <v4l> 0600 root.video + + + + and replace it with + + + <console> 0666 <v4l> 0666 root.video + + + + What we're doing is allowing read and write access to the files in the + video4linux directory. + + [1m5. Downloading and compiling.[0m + + Get MythTV from the http://www.mythtv.org <http://www.mythtv.org> web + site. There are two installation methods you may choose from. The + first is to download the latest release in tarball format and compile. + The tarball release of MythTV should work on a wide variety of systems + and should be the preferred method for new users. If you wish to use + the [1msubversion [22mcopy of MythTV you may obtain it from + http://svn.mythtv.org <http://svn.mythtv.org> + + + + [1mNOTE[22m: If you are going to use [1msubversion [22mto + compile MythTV rather than using the distribution tarball, you [4mmust[0m + join the http://www.mythtv.org/mailman/listinfo/mythtv-commits/ + <http://www.mythtv.org/mailman/listinfo/mythtv-commits/> and + http://www.mythtv.org/mailman/listinfo/mythtv-dev/ + <http://www.mythtv.org/mailman/listinfo/mythtv-dev/> mailing lists to + keep up to date with the current status of the code. Code obtained + from subversion has no guarantees regarding stability, etc. + + If you are in North America you will use the Schedules Direct grabber + which is built-in to MythTV. You [4mdo[24m [4mnot[24m need to install XMLTV (so you + may skip XMLTV-related instructions), but you need [1mwget [22mversion 1.9.1 + or higher. + + Get XMLTV from http://xmltv.sourceforge.net + <http://xmltv.sourceforge.net>. Download the latest version (0.5.51). + + + ______________________________________________________________________ + NOTE for Mandriva users: If you have added a "PLF" mirror, you may skip the + next step and type: + + # urpmi libmp3lame0 libmp3lame0-devel + + After downloading, be sure to install both: + # rpm -Uvh lame* + ______________________________________________________________________ + + + + Get lame from http://lame.sourceforge.net/ + <http://lame.sourceforge.net/>. Download the source code to v3.96.1 + by following the links from "Using" through "Download...". + + + [1m5.1. Building LAME[0m + + Open a shell and switch to the directory where you saved lame. + + + $ tar -xzf lame-3.96.1.tar.gz + $ cd lame-3.96.1 + $ ./configure + $ make + $ make test + $ su + # make install + + + + Check that it worked: + + + + # ls -l /usr/local/lib + -rw-r--r-- 1 root root 381706 Nov 4 14:22 libmp3lame.a + -rwxr-xr-x 1 root root 674 Nov 4 14:22 libmp3lame.la* + lrwxrwxrwx 1 root root 19 Nov 4 14:22 libmp3lame.so -> + libmp3lame.so.0.0.0* + lrwxrwxrwx 1 root root 19 Nov 4 14:22 libmp3lame.so.0 -> + libmp3lame.so.0.0.0* + -rwxr-xr-x 1 root root 360197 Nov 4 14:22 + libmp3lame.so.0.0.0* + + # exit + $ + + + + [1m5.2. XMLTV[0m + + [1m5.2.1. Red Hat Linux and Fedora Core:[0m + + RPMs for [1mXMLTV [22mand all of its dependencies can be obtained from + http://ATrpms.net/name/xmltv/ <http://ATrpms.net/name/xmltv/>. The web + page has a list of all the dependent packages you must download and + install. + + + # rpm -Uvh xmltv* perl* + + + + If you install from this location you may skip to ``Manually building + MythTV''. + + [1m5.2.2. Mandriva[0m + + RPMs for [1mXMLTV [22mand all of its dependencies are located in Mandriva's + "contrib". If you have added a contrib mirror, try installing [1mXMLTV[22m: + + + # urpmi xmltv xmltv-grabbers + + + + If this does not work, it is possible that contrib for your Mandriva + version does not have [1mXMLTV[22m, so you may install the XMLTV prerequi- + sites by typing: + + + # urpmi perl-xml-twig perl-xml-writer perl-datemanip perl-libwww-perl + + + + and skip straight to the XMLTV compilation step. + + + [1m5.2.3. Manual installation[0m + + Untar the xmltv file: + + + $ tar -xjf xmltv-0.5.51.tar.bz2 + + Install the xmltv prerequisites. The following prerequisites are the + minimum required; when you actually start running the xmltv setup pro- + gram it may alert you to other modules that are required.: + + + + $ su + # perl -MCPAN -e shell + cpan> install XML::Twig + cpan> install Date::Manip + Date::Manip is up to date. + cpan> install LWP + cpan> install XML::Writer + cpan> exit + + + + Change to the XMLTV directory and compile it: + + + $ cd xmltv-0.5.51 + $ perl Makefile.PL + + + + You can answer "N" to the tv_check, tv_pick_cgi questions. Say "yes" + to the grabber required for your location. + + You may get errors about modules not being installed. You will need + to resolve any missing dependencies at this point, or your grabber may + not work correctly. + + + $ make + $ make test + $ su + # make install + # exit + + + + [1m5.3. Configuring the Schedules Direct service[0m + + As of 2007-09-01, Tribune Media Services will no longer offer free + guide data. Schedules Direct is a non-profit organization which has + licensed the data to make it available to users of Freeware and Open + Source applications. + + If you wish to use Schedules Direct, you'll need to establish a user + account. Go to http://www.schedulesdirect.org + <http://www.schedulesdirect.org> and click on the "Membership" link. + + Once you've read and agreed to the Subscriber Agreement, Terms of Use + and Privacy Policy proceed to the lineup choices and configure your + account for your particular location and the channels that you have. + This configuration will be imported into MythTV when you first run the + [1mmythtv-setup [22mprogram. + + + + [1m5.4. Manually building MythTV[0m + + If you are going to use [1msubversion[22m, execute the following instructions + to obtain the latest version of MythTV: + + + + $ mkdir mythtv + $ svn co http://svn.mythtv.org/svn/trunk/ mythtv + $ cd mythtv + + + + To use a release version, you can execute: + + + $ mkdir mythtv-release-0.21 + $ svn co http://svn.mythtv.org/svn/branches/release-0-21-fixes/ mythtv-release-0.21 + $ cd mythtv-release-0.21 + + + + [1mNOTE[22m: Using a svn version of the code allows you to stay up-to-date + with changes. So, if there's an update to the 0.21 release and you + originally obtained it using svn, you could enter the mythtv- + release-0.21 directory and type "svn up", which will update your copy + with the fixed version from the website. You would then recompile and + install the updated 0.21 code. + + If you are using the tarball, then unpack it: + + + $ tar -xjf mythtv-0.21.tar.bz2 + $ cd mythtv-0.21 + $ ./configure + + + + If you wish to change options, run [1m./configure --help [22mto see what is + available and to override and automatically detected options. See the + config.log file after running [1mconfigure [22mto see previous runs. + + To compile: + + + $ make -j 2 + + + + The MythTV compile can take advantage of multiple CPUs, SMP and + Hyperthreading. If you want to build MythTV on a multi-CPU machine + (or with [1mdistcc[22m), specify "-j numjobs", where "numjobs" is greater + than 2. In the above example, we had two concurrent jobs executing, + which is recommended for a single CPU system. Do not set the number + of jobs too high, or your compile will actually take longer to + complete than it would if you did a "normal" build. + + If you are using [1mdistcc[22m, and you had two other host machines (red, + blue) participating, you would do something like: + + + + $ export DISTCC_HOSTS='localhost red blue' + $ make -j 6 CXX=distcc + + + + The actual speed-up, if any, is dependant on a number of factors, such + as number of CPUs / hosts, etc. The [1mdistcc [22mdocumentation recommends + using a -j value of twice the number of CPUs available to keep all of + them busy. + + Some timing information. The following should only be used for + illustration; your actual results may vary. The test involves a + complete make distclean to the final binary. + + +o P4 3.2Ghz HT: "standard" make: 12m 49s + + +o P4 3.2Ghz HT: make -j 2: 11m 24s + + In the above example, we see that with a single CPU, a multi-stage + [1mmake [22mdoes not significantly decrease compile time. + + Once the compile is done, switch to superuser: + + + $ su + # make install + # exit + + + + [1mNOTE[22m: subsequent configuration steps assume that you are within + the MythTV directory that you cd'd to above. + + + [1m5.4.1. Enabling real-time scheduling of the display thread.[0m + + MythTV supports real-time scheduling of the video output thread. There + are three ways to go about enabling this: You can use rlimits, you can + use the realtime security module, or on older systems you can SUID the + executable. Enabling real-time scheduling is optional, but can make + the video display smoother, especially if you are decoding HDTV. + + + [1m5.4.1.1. rlimits[0m + + The rlimits method is the preferred method and is included in Linux + 2.6.12 and above. Unfortunately, you need PAM version 0.79 or above, + which may not be supported by your distribution yet. Assuming anyone + running [1mmythfrontend [22mis in the audio group and rlimits are supported, + all you need to do is place this in your /etc/security/limits.conf + + + + * - rtprio 0 + * - nice 0 + @audio - rtprio 50 + @audio - nice 0 + + + [1m5.4.1.2. realtime module[0m + + The second option is to use the Linux realtime kernel module. This is + will be phased out over time, but is currently supported by many + distributions that do not yet support rlimits. If you are not using + the distribution kernel you must configure your kernel with: + + + Security options : [*] Enable different security models + Security options : [M] Default Linux Capabilties + + + + You may also need to install the realtime module, using your distribu- + tion's realtime package. Assuming the users who will be running [1mmyth-[0m + [1mfrontend [22mwill be in the audio group you can get the GUID of a named + group like so: + + + $ grep audio /etc/group + + + + If the number printed out from the grep was 18, you can now load this + module as root before starting [1mmythfrontend[22m: + + + # modprobe realtime gid=18 + + + + [1m5.4.1.3. run as root option (not safe)[0m + + The final and least preferred option is to set the sticky bit on the + [1mmythfrontend [22mexecutable. This [1mopens a security hole[22m, but is the only + option on systems that do not support either rlimits or the realtime + module. This does not work on modern distributions either, and is [4mnot[0m + [4mrecommended[24m on any system connected to the Internet. This may also + make it impossible to debug MythTV without running [1mgdb [22mas root. If you + would still like to do this, you just need to run this as root: + + + # chmod a+s /usr/local/bin/mythfrontend /usr/local/bin/mythtv + + + + [1m5.4.2. Frontend-only configuration[0m + + Since MythTV uses a client/server architecture, multiple frontend + computers can simultaneously access content on a Myth system. Live + TV, watching and scheduling recordings, etc. are all possible from + multiple frontends. + + To get a better picture of what is needed to run a frontend, note the + following: + + You do NOT need the MySQL server installed on your remote frontend + + You do NOT need XMLTV installed on your remote frontend + + You do NOT need to run the mythtv-setup program on your frontend + machine + + Other than the exclusion of the MySQL server and XMLTV, the MythTV + compilation procedure is the same as when you're setting up both a + backend and a frontend. However, you [4mwill[24m need to install the + database access libraries. + + Once MythTV is compiled and installed: + + Run the mythtv-setup program on your Master backend. Under the + "General" menu, change the IP address of the current machine (by + default, "127.0.0.1") to the real external IP address - 127.0.0.1 is + the loopback address and no external machine can access it. Change the + Master Server IP setting to the same IP address as well. + + Run the mythfrontend program on your frontend machine, and a "Database + Configuration" screen should appear. Set the "Host name" field to + point to your Master backend's IP address. + + + [1m5.5. Gentoo[0m + + Installation of MythTV on Gentoo consists of simply emerging the + desired ebuild because all of the packages are now part of the + official Portage tree. + + + $ su - + # emerge --sync # make sure portage is up to date. + # vi /etc/make.conf + + + + Add mysql to your USE variable. i.e. USE="mysql ...." + + + # emerge mythtv + + + + [1m6. MySQL.[0m + + When you install MySQL 5.x you will also want to comment out "log-bin" + in your my.cnf configuration file. This option will quickly fill your + "/var" disk partition with many gigabytes of data, unless you are + doing database replication and deleting these files regularly. + + [1m6.1. Distribution-specific information[0m + + [1m6.1.1. Mandriva[0m + + If this is the system maintaining the database, make sure that MySQL + is running and started at boot. Click on Mandriva Control + Center->System->Services, find MySQL and click the "On Boot" button + and the "Start" button if the MySQL status shows that it isn't running + yet. + + + + [1mNOTE[22m: There have been reports that MySQL isn't starting at boot. + If this is happening to you, try running the following commands. + + + $ su + # chkconfig --level 35 mysql on + # /etc/rc.d/init.d/mysql start + # exit + + + + [1m6.1.2. Red Hat Linux and Fedora Core[0m + + If this is the system maintaining the database, make sure that MySQL + is running and started at boot. Click on Redhat menu>Server + Settings>Services and enter the root password when asked. Check + "mysqld" and then click Start. Click Save, then close the window. + + This can be done from the command line by typing: + + + # /sbin/chkconfig mysqld on + # /sbin/service mysqld start + + + + [1m6.1.3. Gentoo[0m + + After installing MySQL you need to initialize the database by running + [1mmysql_install_db [22mas root. + + [1m6.2. Setting up the initial database[0m + + This step is only required on the system maintaining the database, + which may or may not be one of your MythTV boxes. If the database is + on a non-MythTV machine you'll need to copy the database/mc.sql file + to it. + + To setup the initial MySQL databases: + + + $ cd database + + + + [1m6.2.1. Mandriva and Red Hat Linux/Fedora Core[0m + + + + $ mysql -u root < mc.sql + + + + [1m6.2.2. Debian 3.0[0m + + + + $ mysql < mc.sql + + + + [1m6.2.3. Gentoo[0m + + + + $ su + # mysql < /usr/share/mythtv/database/mc.sql + + + + [1mNOTE[22m: It is good practice to set a root password for MySQL. Instruc- + tions for doing so can be found on MySQL's web site at + http://www.mysql.com/doc/en/Security.html <http://www.mysql.com/doc/en/Security.html>. + + [1m6.2.4. Modifying access to the MySQL database for multiple systems[0m + + If you're going to have multiple systems accessing a master database, + you must grant access to the database from remote systems. By + default, the mc.sql script is only granting access to the local host. + + To allow other hosts access to your master database, you can either + set it up for no security at all, or with more granularity. Note that + the "%" is the wildcard character in MySQL. + + + + [1mNOTE[22m: The "no security" option is [4mvery[24m dangerous unless + you're in a controlled environment. This example has no security at + all, and allows access from any host. + + + $ mysql -u root mythconverg + mysql> grant all on mythconverg.* to mythtv@"%" identified by "mythtv"; + mysql> flush privileges; + + + + For a more secure setup, you can restrict which machines or subnets + have access. If you have a complete DNS system operational, you could + do the following: + + + $ mysql -u root mythconverg + mysql> grant all on mythconverg.* to mythtv@"%.mydomain.com" identified by "mythtv"; + mysql> flush privileges; + + + + Finally, if you just want to restrict by IP subnet (in this example, + the 192.168.1. network): + + + $ mysql -u root mythconverg + mysql> grant all on mythconverg.* to mythtv@"192.168.1.%" identified by "mythtv"; + mysql> flush privileges; + + You'll also need to check that the "networking" feature of MySQL is + turned on. Check that /etc/mysql/my.cnf [4mdoes[24m [4mnot[24m contain skip- + networking. If it does, remove it. Also verify that bind-address is + set to your IP address instead of 127.0.0.1. If you change either of + these items, restart [1mMySQL[22m. + + [1mNOTE[22m: Your distribution may have a customized MySQL configuration + file; in Mandriva, check /etc/sysconfig/mysqld for additional + configuration. + + + [1m7. Configuring Sound.[0m + + If your video doesn't appear to be in-sync with your audio and you're + using an analog video capture card and a soundcard to capture audio, + it could be because you are listening to the real-time audio from your + video card rather than after it's been processed and synchronized to + the video by MythTV. Because MythTV is a personal video recorder, + "Live TV" isn't really live - to let you pause live TV, MythTV is + actually encoding the video, saving to disk, and then playing it back. + This procedure puts your MythTV "live" TV about 2 seconds behind real- + time, so it's important that you're not listening to the live audio. + However, if you're having an issue where the audio and video aren't + synchronized by small but varying amount, it's most likely because the + sound driver that you're using doesn't have the DSP_CAP_REALTIME + capability. This was the case with ALSA (0.5), but not with newer + versions. See the ``Troubleshooting Audio'' section for more + information if you're having issues with sound. Also, ensure that no + other programs are grabbing the audio output, like [1marts [22mor [1mesd[22m. + + What you need to do is to mute the "line-in" of your sound card and + also set it as the recording source. + + There are two ways to do this. Graphically, and from the command + line. + + + [1m7.1. Graphically setting up the mixer[0m + + [1m7.1.1. Mandriva and Red Hat Linux/Fedora Core[0m + + Open Kmix by clicking K->Multimedia->Sound->Kmix for Mandriva, or + + RedHat Menu>Sound & Video>Volume Control + + + + Click on Settings->Configure Make sure that "Tick Marks" and "Show + labels" have "X"'s in them. This will make it easier to find the + correct audio source. Click OK. + + On the mixer page, look for Line-In on your sound card. You should + see two LED's - a green one at the top, and a red one at the bottom. + The green one at the top is for muting; you want to make sure that the + green LED is a dark green, meaning that it's "off". You also want to + click on the red LED so that it turns bright red, indicating that it's + "ON"; this insures that the Line-in is used as the source. Click OK, + and make sure that you save the settings so that this is your default. + + + [1m7.1.1.1. Using ALSA.[0m + + To use ALSA, you'll need to correctly setup your asoundrc file. + Configuring this file is beyond the scope of this HOWTO. Once ALSA is + working correctly, change the output sound device in + mythfrontend->setup->Audio from /dev/dsp to ALSA:default. This field + may be edited to suit your ALSA requirements. + + + [1m7.2. Setting the mixer from the command line[0m + + If you have installed the alsa-utils package, then the [1mamixer [22mprogram + can be used to setup the mixer. The "Master" volume setting is only + required on a frontend machine to ensure that the sound channels are + unmuted and configured for outputting sound. The "Line" and "Capture" + controls are required for your sound card to actually capture audio + from the external Line-in if it's connected to an analog frame + grabber. Not all sound cards have a "Capture" control, but if yours + does and you don't set it then MythTV will not capture audio. + + + ______________________________________________________________________ + Note the spelling in the following commands. + ______________________________________________________________________ + + + + $ amixer set Master,0 100%,100% unmute + $ amixer set PCM,0 100%,100% unmute + $ amixer set Line,0 75%,75% mute captur + $ amixer set Capture,0 100%,100% captur + $ su + # alsactl store + # exit + $ + + + + If you have multiple sound cards, then use the -c parameter to specify + which card to adjust. Note that the first card will be "0", the + second will be "1", etc. + + That takes care of setting the volume correctly, and the ALSA startup + script will restore the volume after a reboot. If you find that your + sound is distorted, it's possible that the levels in the above + examples are too high for your particular hardware combination. Try + reducing the percentages by 5-10% and checking again. Once you're + satisfied, re-run the alsactl store command. + + You may also use the [1malsamixer [22mprogram to set the volume. If you are + using an ALSA version after 1.0.6, use [1malsamixer -V all [22mFirst, start + [1malsamixer [22mfrom the command line. You should start out on the "Master" + volume control slider. Use the up and down cursor to set the master + volume to around 75%. Next, use the left and right cursor keys to + move around on the screen until you find the "Line" slider. Press + SPACE to set it as the capture source, set the level to around 50-75% + and press "M" to mute it. You can now press ESC to exit out of the + [1malsamixer [22mprogram. You can also have MythTV manage all volume and + mute settings, but this will only affect the "Master" or PCM volume, + not the capture volume. See the mythfrontend setup page for options. + + Finally, if you've performed all of the above steps, and you still + don't seem to have any sound, it's possible that your video capture + device is muting the audio output. + + + $ v4lctl -c /dev/video0 setattr mute off + + + + [1m8. Setting up a remote control.[0m + + MythTV does not have native remote control receiver and decoder + software built-in. Instead, remote control functions are implemented + by cooperating with [1mlirc[22m, the Linux Infrared Remote Control program. + [1mlirc [22mhandles the IR hardware and passes keystrokes to MythTV, which + then acts as if the user had pressed the keys on the keyboard. The + file keys.txt describes the keys used to control MythTV. + + + + [1mNOTE[22m: If you are running Mandriva, you may install + [1mlirc [22mby executing: # urpmi lirc lirc-remotes and bypass the manual + compilation steps described below by jumping to the ``Completing the + lirc install'' section. See the contrib/mandrake91.etc.sysconfig.lircd + file for an example of how to configure lircd. + + Some IR devices require a kernel recompile, and some don't. However, + all at least require having the kernel source available as a resource + for the lirc build process. + + + [1m8.1. Gentoo[0m + + To install lirc on Gentoo, all you need to do is: + + + # emerge lirc + + + + [1m8.2. Obtaining and compiling lirc[0m + + You're going to need to download and compile [1mlircd[22m. Go to + http://www.lirc.org <http://www.lirc.org> and download lirc; as of + 2006-01-21, the version available is 0.8.0. Grab the remotes.tar.bz2 + file as well. + + + $ tar -xjf lirc-0.8.0.tar.bz2 + $ cd lirc-0.8.0 + $ ./setup.sh + + + + You're going to need to know what sort of receiver you have and where + it's connected. In the case of the Pinnacle Studio TV card, with the + IR receiver connected to COM1 (/dev/ttys0), once the configuration + menu comes up, perform the configuration by going to Driver Configura- + tion->Other Serial Port Devices->Pinnacle Systems Receiver->OK and on + the next page select COM1->OK. + + Each remote is different; some remote receivers connect directly to + your capture card and not to a serial port, so make sure that you've + got the correct one. + + You then click "Save Configuration and run configure" to continue. + + Make sure you read the last text generated by the configure step. It + will tell you if you require a kernel recompile, and what the name of + your kernel module will be (if necessary). For instance a home-built + receiver may require a kernel recompile, so you would be notified that + you will have to load the lirc_serial module. If you did not get any + such messages skip the kernel recompile steps below and go directly to + making and installing the lirc driver. + + Once the configuration step is complete: + + + $ make + $ su + # make install + # chmod 666 /dev/lircd + + + + At this point, if you're using a serial receiver, check that there's a + lirc device in /dev: + + + $ ls -l /dev/li* + lr-xr-xr-x 1 root root 5 Jan 27 09:00 /dev/lirc -> ttyS0 + srw-rw-rw- 1 root root 0 Jan 27 15:01 /dev/lircd= + prw-r--r-- 1 root root 0 Jan 27 09:00 /dev/lircm| + + + + As you can see, there's a link from /dev/lirc to ttyS0, a.k.a. "COM1", + which is appropriate for the Pinnacle Systems PCTV Pro. However, you + may notice something like this: + + + crw------- 1 root root 61, 0 Dec 31 1969 lirc + + + + Some IR receivers (including some homebrew units) use a character + device as their data interface as opposed to a link to a serial port. + If the make install step has created a character device for you, don't + replace it with a link to a COM port. + + So, if the link or character device was not created (but should have + been), ensure that you ran the make install step as root. If it still + doesn't work, then there are three options. The first option is to + re-read the [1mlirc [22mdocumentation to determine whether your IR receiver + is a character device or should be a link to a serial port and to + create the link/character device manually. In this example, the IR + device is connected to ttyS0. If it were connected to "COM2", then + use ttyS1, etc. + + + $ su + # cd /dev + # ln -sf ttyS0 lirc + # exit + $ + + + + [1mNOTE[22m: The above example assumes that your receiver uses the + standard serial driver. Some receivers do not, including receivers + that plug into a TV capture card. Check the lirc documentation, but + it may be necessary to replace the link created above with a character + pipe: + + + # mknod /dev/lirc c 61 0 + + + + See the lirc documentation for additional information. The lirc + installation [4mshould[24m create this for you, so manually creating it + indicates that your lirc installation may have other issues. + + The second option is to post your issue to the [4mlirc[24m list, not the + mythtv-users list. The lirc programmers will be the ones that can + assist you best. + + The third option is to dispense with lirc altogether by purchasing an + IR keyboard (various options exist, although Chicony appears to work + for some people) and a learning remote control. The IR keyboard + receiver plugs into the PS/2 keyboard port on your PC and you would + train your learning remote to emulate the various keystrokes from + keys.txt of your IR keyboard. Using this method removes lirc entirely + from the picture - your remote will be sending keypresses that your PC + "sees" on the keyboard port. + + + [1m8.3. Completing the lirc install[0m + + + + [1mNOTE to Mandriva 9.1 users[22m: skip to the manual start paragraph + below. + + If the lirc configure program / compile did not mention anything about + a kernel module, then you are finished. If it did mention a kernel + module, you must edit the /etc/modules.conf file. Add this line as the + first thing in the file. It must come first, or it may not work. + + + alias char-major-61 XXX + + + + replace XXX with the name which you determined earlier, which in this + example was "lirc_serial" + + + $ su + # modprobe lirc_serial + # /sbin/ldconfig + + + + Next, we're going to manually start lircd the first time. Mandriva + 9.1 users, type: # /etc/rc.d/init.d/lircd start instead of: + + + # /usr/local/sbin/lircd + + + + [1mNOTE[22m: Read this next section if you're not familiar with how lirc + works! + + There are two separate files used by lirc, and both are required for + your remote control to do anything useful. First is the lircd.conf + file. lircd.conf tells the lirc daemon how to interpret the IR pulses + that it receives from a remote control and what name to assign to each + sequence of pulses. Without getting too involved, a particular series + of pulses may correlate to "Channel Up". The lircd.conf file will + then contain a line that looks something like this: + + + + ChannelUp 0x0000000000001020 + + + + The lircd.conf file can have multiple remote controls defined. + + The second file is lircrc, which takes the name of the button which + was pressed ("ChannelUp") in the above example, and correlates that to + an action to be performed by a program using the remote control. So + in MythTV, ChannelUp means one thing, while in [1mmplayer [22mit means + something different. lircrc gives you the flexibility of taking the + name of the button and having it perform different actions depending + on which program you're using at the time. + + [1mNOTE[22m: The definitions in lircd.conf come from the user community, and + there is no standard for the common button names. One lircd.conf file + may contain a definition for a button called "ChannelUp", while + another may contain a definition for "Chan+". Your lircrc file must + therefore be configured appropriately, or it won't work. + + If this fails, complaining of a missing lircd.conf file, then you must + find or make one. First look for a pre-made configuration file at + http://lirc.sourceforge.net/remotes/ + <http://lirc.sourceforge.net/remotes/>. Mandriva 9.1 users, look in + /usr/share/lirc-remotes. If you find one your remotes either on the + website or in /usr/share, download or copy the file, name it + lircd.conf and put it in your /etc directory. If you couldn't find + your remote, you must make your own lircd.conf file. + + To make your own lircd.conf file + + + $ irrecord myremote + + + + Follow the on-screen directions to train your remote and define keys. + If your remote ends up working well, you should consider submitting + your lircd.conf file back to the lirc developers. Once finished: + + + $ su + # cp myremote /etc/lircd.conf + + + + now try to start lircd again: + + + # /usr/local/sbin/lircd + + + + Now, we're going to add the commands necessary for lircd to run each + time we boot. Mandriva 9.1 users, you can execute: + + + $ su + # chkconfig --level 35 lircd on + # exit + + + + All other distributions: + + + # cd /etc/rc.d + # cat >> rc.local + echo "Starting lircd" + /usr/local/sbin/lircd + ^D + # exit + $ + + + + This takes care of the lircd portion, which "listens" for the IR + signals. If everything went well, the install script for lircd put an + appropriate configuration file for your remote into /etc/lircd.conf + This file maps the buttons on the remote control to the IR pulses + coming from the receiver. + + The next step is to convert those signals into something that can be + used to control MythTV. MythTV now includes native support for lirc + and can interact directly with + + + + $ cd ~/mythtv-0.21/contrib/configfiles + $ cp lircrc.example ~/.lircrc + + + + or + + + $ cp lircrc.example.pinnaclestudiopctv ~/.lircrc + + + + if you've got a Pinnacle Studio PCTV remote. + + + $ irw + + + Start pressing the keys on your remote; [1mirw [22mwill print the name of the + button as it is defined in your /etc/lircd.conf. If you don't see any- + thing at this point, you need to troubleshoot further by going back to + the lirc home page and investigating from there. + + If it is working, then press [1mCTRL-C [22mto abort the program. Once you + know that your remote is working, you can either recompile MythTV with + native lirc support by enabling it in [1mconfigure [22mor you need to run the + [1mirxevent [22mprogram, which takes the key presses and sends them to + MythTV. If you use native lirc support, you don't need to run + [1mirxevent[22m. If you are going to use irxevent, then you need to run it + like this: + + + $ irxevent & + + + + If [1mirxevent [22misn't running, then MythTV will not respond to your remote + control unless you're using native lirc support. + + + [1m8.4. Additional information for lirc[0m + + Take a look at the lircrc.example files in the contrib/configfiles/ + directory. In my case, (Pinnacle Studio card) the channel up and down + functions weren't working, due to the fact that the button names were + different than the default lircrc.example file that came with MythTV. + + The lircrc.example file has this: + + + begin + prog = irxevent + button = ChannelUp + config = Key Up CurrentWindow + end + + begin + prog = irxevent + button = ChannelDown + config = Key Down CurrentWindow + end + + + + but the /etc/lircd.conf that comes in the lircd package defines the + buttons for the Pinnacle Studio PCTV as: + + + channel+ 0x0000000000000017 + channel- 0x000000000000001C + + + + rather than "ChannelUp" and "ChannelDown". I added the following to + my /home/[yourusername]/.lircrc file: + + + + begin + prog = irxevent + button = channel+ + repeat = 3 + config = Key Up CurrentWindow + end + + begin + prog = irxevent + button = channel- + repeat = 3 + config = Key Down CurrentWindow + end + + + + which took care of basic functionality. Because the PCTV Studio + remote has additional buttons, look at the contrib/configfiles/lir- + crc.example.pinnaclestudiopctv for an example of how to define addi- + tional buttons, and how to debug potential button name conflicts + between the lircrc.example file and how [1myour [22mremote defines the button + names. + + By examining the button names defined in /etc/lircd.conf and using the + [1mirw [22mprogram to make sure that your remote is working, you can create + the appropriate mappings in .lircrc to get excellent remote + functionality with MythTV. + + Note the [1mrepeat = [22mparameter. This informs the irxevent program to + pass through every third keypress. By default, lirc will only send + one keypress to the application, even if you're holding down the key. + The actual [1mrepeat = [22mnumber will vary from system to system, so + experiment and see which value works best for you. + + + [1m8.5. Configuring lirc for use with an IR blaster[0m + + Lirc has support for various IR transmitters. A popular model is the + Actisys IR-200L http://store.snapstreamstore.com/accessories.html + <http://store.snapstreamstore.com/accessories.html>. It was originally + designed for IRDA communication, but can be used to transmit A/V + remote control codes. By using the lirc SIR driver, this device can + easily be integrated with MythTV. I have tested this device with an + AT&T DCT2000 digital cable box but the instructions can be used to + configure other IRDA devices and A/V remotes. + + Follow the steps in the previous section. When you run setup.sh, + select option 1, driver configuration. From here select option 6, IrDA + hardware. Select your appropriate device and the corresponding serial + port, then Save configuration & run configure from the main menu. Once + configure is done type: + + + $ make + + + + Please note: unlike the Pinnacle receiver above you will be compiling + lircd in addition to a kernel module for the SIR transmitter. + Depending on whether you have your serial port driver configured as a + kernel module you might see the following message during make: + + + + lirc_sir.c:56:2: warning: #warning + "******************************************" + + lirc_sir.c:57:2: warning: #warning "Your serial port driver is compiled into " + + lirc_sir.c:58:2: warning: #warning "the kernel. You will have to release the " + + lirc_sir.c:59:2: warning: #warning "port you want to use for LIRC with:" + + lirc_sir.c:60:2: warning: #warning "setserial /dev/ttySx uart none" + + lirc_sir.c:61:2: warning: #warning + "******************************************" + + + + If you do receive this statement make sure to run the [1msetserial[0m + command before you load the lirc_sir module. Follow this with the + install: + + + $ su + # make install + + + + You will notice that lirc installs the kernel module in + /lib/modules/uname -a/misc. + + The configuration for starting [1mlircd [22mdiffers if you're going to be + sending and receiving IR versus just receiving. + + + + # cd /etc/rc.d + # cat >> rc.local + echo "Starting lircd" + setserial /dev/ttySx uart none # (if required) + modprobe lirc_sir + /usr/local/sbin/lircd + ^D + # exit + $ + + + + At this point you have to populate the /etc/lircd.conf file with the + proper codes for your A/V remote. You should be able to find your + remote within the lirc remote tar file located at + http://www.lirc.org/remotes.tar.bz2 + <http://www.lirc.org/remotes.tar.bz2>. In my case I extracted the file + from remotes/motorola/DCT2000 (gi-motorola-dct2000) + + To test the lirc_sir module you can run [1mirw [22mto verify the codes are + being received. If everything is configured correctly you should see + something similar to the following: + + + $ irw + 0000000000007ff0 00 1 gi-motorola-dct2000 + 000000000000bff8 00 2 gi-motorola-dct2000 + 000000000000f7f0 00 ENTER gi-motorola-dct2000 + + Once you've verified lirc is working you can press [1mCTRL-C [22mto exit [1mirw[0m + and configure the channel changing script. + + The path to the channel changing script will need to be entered on the + mythtv-setup screen for Input Connections. + + This csh script will be called each time MythTV needs to change the + channel. Below is a copy of the script followed by the corresponding + perl script. Make sure both are in your path. Also make sure you + leave the #!/bin/csh setting and not change it to Bourne or bash. This + will create a frustrating symptom to diagnose where MythTV cannot open + /dev/device. Unlike Bourne or bash, csh scripts automatically close + parent file descriptors before they start. + + + $ cd /usr/local/bin + # su + # cat > change_channel.csh + #!/bin/csh + echo "changing to $1" + /usr/local/bin/channel.pl $1 & + ^D + # chmod a+x change_channel.csh + # exit + $ exit + + + + See contrib/channel.pl for the actual file. Copy it to + /usr/local/bin/ + + The last statement within the perl script is the lirc rc command. This + is the command that transmits the code to your cable/DSS box. Make + sure to have the IRDA device within a few feet of the box. + + + [1m9. Configuring MythTV.[0m + + By this point, all of the compile-time prerequisites have been + installed, [1mmysql [22mis running and has had its initial database setup. + It's now time to configure MythTV. + + + + [1mNOTE[22m: If you're running Debian unstable and you have compiled + MythTV from source, you will need to install an additional package + before you will be able to run MythTV. Execute the following to + install the MySQL driver for QT. + + + $ su - + # apt-get install libqt3c102-mt-mysql + # exit + + + + [1m9.1. Configuring the Master backend system[0m + + Open a shell and decide where you will store your video files. This + may be one directory or multiple directories on the same or different + filesystems. There is no default directory used for new recordings, + you [1mmust [22mcreate at least one storage directory and configure Myth to + use it by running [1mmythtv-setup[22m. If you do not do this, then MythTV + will be unable to record anything. The following example is specific + for /var/video, but the same instructions would apply for any + directory name you choose to use. See the ``Advanced Partition + Formatting'' section for hints on creating a partition for MythTV. + + + + $ su + # mkdir /var/video + # chmod a+rwx /var/video + # exit + + + + [1mNOTE[22m: The last slash "/" is not required. + + + [1mTIP[22m: Try not to have your video mount point on the same partition as + your root partition, which could lead to the filling up of your root + partition with video data if the mount fails. For example: + + If /var/video is created on your root partition and you then perform a + mount of another drive to this directory there won't be any problems + if everything is working the way it should. However, if the mount + fails for some reason, /var/video still exists, so MythTV will find + the directory and write files to it. If your / mount point is space + limited, /var/video will [1malso [22mbe space limited, and it won't take long + to fill the partition. This will cause a number of side-effects, most + of them bad. Instead, create subdirectories as the destination for + the storage group. + + Your directory structure could then look something like this: + + + /mnt/video/drive1/video + /mnt/video/drive2/video + + + + Your /etc/fstab would look like this: + + + /dev/hdb1 /mnt/video/drive1 + /dev/hdc1 /mnt/video/drive2 + + + + Because the Storage Group path is /mnt/video/drive1/video, if the + mythbackend can only find /mnt/video/drive1 it will [4mnot[24m write files to + that share. + + After you create the desired directory or directories for storing your + video files, you will need to add them to the proper Storage Group + using [1mmythtv-setup[22m. This procedure is described below in the + ``Storage Groups'' section. + + The first thing to configure is the Master backend system. If you are + running multiple backend systems, the Master backend will make all + decisions about which programs will be recorded on which tuners. If + you have only one backend, then it will be its own master. + + + The Master backend will always choose the first available tuner in the + same order as you add cards through "mythtv-setup". In other words, + the second card you add will only be used when there are two + overlapping recordings, the third when there are three, and so on. + Therefore, you will want to have the greatest amount of disk space on + the Master backend because its tuner will always be the first choice. + You will then want to add your ``other backends'' in the order of your + preference for recording. + + + + [1mNOTE[22m: It is possible to [4mnot[24m have the cards on the Master + backend be the first ones used. However, if you are new to MythTV it + is easier to configure the Master backend first before moving on to + the Slaves, at least until you become more familiar with the MythTV + system. See ``Advanced Backend Configurations'' for information on + configuring multiple backend systems in various ways. + + Because MythTV uses a database to store all configuration variables, + part of the bootstrap of MythTV is to indicate the location of the + MySQL database server. If the frontend, backend and MySQL database + server are all going to be running on the same box, you can continue + to the next step. If not, you'll need to change the Host Name in the + "Database Configuration" screen of the mythfrontend program. + + + + [1mNOTE[22m: Users that have been running the frontend and the backend on + different machines have stated that they have been having issues with + remote access to the MySQL database. The following instructions may + or may not work. Add the following to /etc/my.cnf on the backend + machine and restart MySQL. + + + skip-innodb + set-variable=thread_stack=256k + + + + Run the setup program: + + + $ mythtv-setup + + + + The backend setup program will start and offer you a number of + choices. It is [4mstrongly[24m recommended that you go through them in + order. + + The first question will ask if you wish to clear out your existing + configurations for your capture cards. Initially, you should say + "YES" so that there are no surprises later. + + The next question will ask you if you wish to clear out your video + source information. You should answer "YES" to this as well. + + + Once the graphical setup starts, you'll see that there are six choices + + + + The Storage Directories feature is available only in the SVN version + of MythTV. + + + 1. General + + 2. Capture Cards + + 3. Video Sources + + 4. Input connections + + 5. Channel Editor + + 6. Storage Directories + + Use the arrow keys to move around, and press the space bar to select + which option you wish to configure. + + + [1m9.1.1. General[0m + + The first screen of the General configuration deals with IP addresses + of the system that you're running mythtv-setup on and any master + backend you may have. If you've only got one machine, then the + default values are fine and you can move to the next page by pressing + the space bar. If you need to move around the screen, use the arrow + keys to move focus between settings, not the mouse. + + If you will be deploying multiple backends, or if your backend is on + one system and you're running the frontend on another machine then [4mdo[0m + [4mnot[24m use the "127.0.0.1" IP address. + + [1mNOTE[22m: 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 the space bar. + + The next screen details the Host-specific Backend setup. This is + where you will set the specific directory paths for this particular + backend. Make sure that you've followed the steps at the beginning of + this section and created a directory that exists and that MythTV will + have write privileges to. When you're done, press Next to continue, + taking you to the Global Backend Setup. + + On the Global Backend Setup configure your backend with the + appropriate settings. Use the left and right arrow keys to iterate + through the choices available on each setting, and the up and down + keys to move between settings. Move to Finish when you're done and + press the space bar, taking you back to the main configuration screen. + + + [1m9.1.2. Capture Cards[0m + + You should have no capture cards defined, so the highlight will be on + (New Capture Card). Press space to begin. + + Choose the appropriate settings for your particular tuner. Use the + arrow keys to move around and to make your choices, and press RETURN + when complete. Pressing RETURN will take you back to the Capture + Cards screen; if you have additional capture cards in this machine, + press the space bar when the highlight is on the (New Capture Card) + row to define another card. + + If you have made a mistake, you can delete a card by highlighting it + and pressing the 'D' key, or you can highlight it and press the RETURN + or 'E' key to edit it. + + Once you have no additional cards to setup, press ESC. + + + + [1mNOTE[22m: If you have a dual digital/analog card, such as the pcHDTV + cards and some DViCO cards, then you should not configure this as two + separate cards. Configure the digital portion as a DVB card, then + click on the "Analog Options" button within the DVB configuration + panel for the card and configure the analog portion of the card there. + + + [1m9.1.3. Video Sources[0m + + When you start, the highlight should be on (New Video Source). Press + the space bar to begin. The first field asks for the name of the + video source. You may choose something easy to remember, like + "Antenna" or "Cable". Once you've chosen a name, press the down arrow + to move to the next field. + + If you're in North America, change the grabber to + "SchedulesDirect.org(Internal)", then continue pressing the down arrow + to move to the next field. Fill in the username (lowercase only) and + password that you have established with Schedules Direct, then move to + the "Retrieve Listings" button and press the space bar. + + [1mNOTE[22m: You need [1mwget [22mversion 1.9.1 or higher to use Schedules Direct. + + The mythtv-setup program will contact the Schedules Direct servers and + get your account information. Once you're done, you may click the + Finish button and skip the next few paragraphs in this document since + they only apply to users that are using the external XMLTV script to + get their guide data. + + If you wish to continue using the XMLTV grabber, then move to the + Zip/postal code field and put in the appropriate value. + + If you're outside of North America, then some manual interaction will + be required with XMLTV. You may need to switch from the MythTV setup + program to the console it was run on to interact with XMLTV. + + Once you have chosen your provider, press RETURN to continue. XMLTV + will now begin collecting the initial data for your location. The + screen may blank for a few seconds to several minutes, depending on + the load of the listings provider and the speed of your connection to + the Internet. Be patient! + + + You will then be returned to the Video Sources screen. If you have + multiple video sources available, such as Antenna, Cable, etc, go + ahead and define them all, even if they're not all going to be + physically connected to the master backend server. Once you're done, + press ESC to return to the main screen. + + + [1m9.1.4. Input Connections[0m + + The final configuration item is Input Connections. On this screen, + you will associate the various video sources you defined earlier with + a physical input to a encoder card. It's entirely possible that you + have multiple tuners, and each tuner has a different input, so on this + screen you let MythTV know which device will connect to which input + source. + + When you start this screen, you should see a listing of the various + input connections available on each of the Capture cards you defined + earlier. For example, you may have a capture card with a tuner, a + SVideo and a Composite connection. If you wanted to associate the + tuner (a.k.a., "Television") with an "Antenna" source you defined in + Video Sources, you would move to the /dev/videodevice (Television) -> + line and press the space bar. Using the left and right arrow keys + will show you the various choices you have already created for video + source. In our case, you would use the left/right cursor keys until + "Antenna" was shown in the Video Source field. Press down to move to + the next setting. + + On the connection pane there is a "Scan for channels" button, if you + are configuring a digital source such as a DVB card, you need scan for + channels and you must do this before pressing the "Fetch channels from + listings source" button. You may scan for analog channels on an analog + input, but this is not needed. + + + The other button is called "Fetch channels from listings source". As + long as you have a real listings source you should fetch channels from + them for analog channels. You can do this for digital sources as well + (unless the listing source is transmitted EIT data). If you are using + XMLTV, you may need to switch from the MythTV setup program to the + console it was run on to interact with XMLTV after pressing this + button. It is possible to fetch the channels on the command line using + mythfilldatabase. But if you need to do this, you will probably need + to re-enter the MythTV setup program to configure the "Starting + channel" setting for this source->input connection. + + + + [1mNOTE[22m: If you have a Hauppauge PVR-500, you must think of + it has two PVR-150's on a single PCI card. For example, if you have a + single PVR-500 card, it will appear as /dev/video0 and /dev/video1. + Each /dev/video device will have a Tuner input. Once you're done, + press RETURN to go back to the Input Connections screen. You would + then finish associating the video sources to any other hardware + devices you have available. + + + + [1mNOTE[22m: Don't add a video source to a hardware input if you don't + actually have anything connected there. For example, adding "Cable" + to the Tuner and to the Composite inputs without having something + connected to Composite will lead to blank recordings. + + Press ESC to return to the main menu, and press ESC again if you have + no further items to configure, thereby returning you to the command + line. + + + [1m9.1.5. Channel Editor[0m + + The channel editor is used to globally alter channel information, + including items like hue, contrast, fine tuning and others. Users in + North America shouldn't run the channel editor until you've completed + the initial mythtv-setup and ran [1mmythfilldatabase [22mat least once to + populate the database. + + + [1m9.1.6. Storage Groups[0m + + + + New in MythTV 0.21 + + [1m9.1.6.1. Introduction.[0m + + Storage Groups are lists of directories that are used to hold MythTV + recording files giving you a flexible way to allow you to add capacity + to your MythTV system without having to use exotic solutions such as + LVM, filesystem expansion or RAID Online Capacity Expansion. You can + also use Storage Groups to organize recordings and to put recordings + of a certain type into one subdirectory. + + Storage Groups do not offer redundancy in case of hard drive failure, + but unlike LVM, if you lose a hard drive, you only lose the recordings + that were on that drive. With LVM, if you lose a hard drive, you will + most likely lose [1meverything[22m. + + + [1m9.1.6.2. How to use Storage Groups.[0m + + By default, there is only one Storage Group called "Default", and it + is used for all recordings and Live TV. + + + + [1mNOTE[22m: You need to add at least one directory to the Default + Storage Group or else you will not be able to record anything with + MythTV. + + For example, if you have 5 hard drives in your system, your first hard + drive could be your "boot" drive, and the remaining four could be + dedicated to media storage. You could format the drives and mount them + as /mnt/store/d2, /mnt/store/d3, /mnt/store/d4 and /mnt/store/d5. + + Within each mount point, it's [4mstrongly[24m recommended that you use a sub- + directory and make that the destination path for the Storage Group. + See the ``Tip'' in the "Configuring the Master backend" section for + additional information. + + + You would then add the four subdirectories you created under the mount + points (/mnt/store/d1/video, etc) into the "Default" Storage Group. + + At recording time, if there were four simultaneous recordings, MythTV + would put one recording onto each drive. + + Or, say that you originally installed MythTV to a 80GB hard drive, and + that hard drive is now filling up. You could simply add a new drive + to your system, mount it and update the Storage Group to add + additional space. + + You may create additional Storage Groups to store specific recordings + in their own directories. Storage Groups are edited via the 'Storage + Directories' section of mythtv-setup. + + You can also create multiple Storage Groups to group recordings + together; recording schedules now have an option to specify which + Storage Group to use. + + MythTV will balance concurrent recordings across the available + directories in a Storage Group in order to spread out the file I/O + load. MythTV will prefer filesystems that are local to the backend + over filesystems that are remote until the local filesystem has 2 + concurrent recordings active or other equivalent I/O, then the next + recording will go to the remote filesystem. The balancing method is + based purely on I/O, Myth does not try to balance out disk space + unless a filesystem is too low on free disk space in which case it + will not be used except as a last resort. + + Storage Groups are global, but can be overridden on a slave backend by + creating a local Storage Group by running [1mmythtv-setup [22mon the slave. + If a problem occurs and the slave backend is unable to use the desired + Storage Group, it will fail back and try the directories defined in + the master's Storage Group. + + There's also a special 'LiveTV' Storage Group, but the directory list + starts out empty. If you add a directory to the Storage Group, it + will be used instead of putting LiveTV recordings in the Default + Storage Group. This will allow you to put your LiveTV recordings on + their own filesystem, which is similar to the old MythTV method which + used a RingBuffer for LiveTV. Of course, you don't have to do + anything, and Live TV recordings will just go into the Default Storage + Group where they'll be the first programs eligible for expiration if + the system needs free space for recordings. + + Usage information for all Storage Group directories is visible on the + mythfrontend status screen as well as the mythbackend status webpage. + MythTV is smart enough to determine which directories are on shared + filesystems so it should not count free or used space multiple times + if you have more than one directory on the same filesystem. + + + [1m9.1.6.3. Migrating to Storage Groups.[0m + + Migrating to Storage groups is very simple: if you have existing + recordings in a storage directory, then the system will automatically + add that directory to the Default Storage Group. If you then add + additional directories to a storage group, the system is flexible + enough to check [4mall[24m Storage Groups for a file before deciding that it + can't be found, which means that you can use the [1mmv [22mcommand from the + Unix command line to arrange files however you'd like. + + + + [1m9.1.6.4. Advanced: Algorithm used by the Storage Group[0m + + This section details the logic of the Storage Group allocation engine. + + The current load-balancing preferences (in order) are: + + +o Local filesystems over remote + + +o Less-busy (less weight) over more-busy (more weight) + + +o More Free Space over Less Free Space + + The 'business' of a filesystem is determined by weights. The following + weights are added to a filesystem if it is in use for the following + things: + + +o recording = +10 + + +o playback = +5 (mythfrontend) + + +o comm flagging = +5 (mythcommflag) + + +o transcoding = +5 (mythtranscode) + + If a recording is due to end within 3 minutes, it is not counted + against the weight of a filesystem. This is done to account for the + pre/post-roll and start-early/end-late settings. + + + [1m9.2. Post-configuration[0m + + Run the mythfilldatabase program as directed. The master backend will + obtain guide data for all the video sources you defined during setup. + + [1mNOTE[22m: If you are using Schedules Direct and watching the output + messages on the console or the log file it is normal to see a "401 + Unauthorized" error followed by a "200 OK" when the connection to + Schedules Direct is being established. + + + From : Sun Jun 13 05:00:00 2004 To : Mon Jun 14 05:00:00 2004 (UTC) + --02:58:01-- + http://datadirect.webservices.zap2it.com/tvlistings/xtvdService + => -' + Resolving datadirect.webservices.zap2it.com... 206.18.98.160 + Connecting to datadirect.webservices.zap2it.com[206.18.98.160]:80... + connected. + HTTP request sent, awaiting response... 401 Unauthorized + Connecting to datadirect.webservices.zap2it.com[206.18.98.160]:80... + connected. + HTTP request sent, awaiting response... 200 OK + Length: unspecified [text/xml] + + [ <=> ] 114,125 63.57K/s + + 02:58:03 (63.53 KB/s) - -' saved [114125] + + Your subscription expires on 08/20/2004 12:00:00 AM + Grab complete. Actual data from Sun Jun 13 05:00:00 2004 to Mon Jun 14 + 00:00:00 2004 (UTC) + + + + Once mythfilldatabase has finished, start the master server before + continuing. + $ mythbackend + + + + mythbackend will print information about connections and what it's + doing to the console. If you'd like to see the options that are + available for mythbackend, type mythbackend -h for help. + + As of MythTV v0.21, the available options are: + + + $ mythbackend --help + Valid options are: + -h or --help List valid command line parameters + -l or --logfile filename Writes STDERR and STDOUT messages to filename + -p or --pidfile filename Write PID of mythbackend to filename + -d or --daemon Runs mythbackend as a daemon + -v or --verbose debug-level Use '-v help' for level info + --printexpire List of auto-expire programs + --printsched Upcoming scheduled programs + --testsched Test run scheduler (ignore existing schedule) + --resched Force the scheduler to update + --nosched Do not perform any scheduling + --nojobqueue Do not start the JobQueue + --noautoexpire Do not start the AutoExpire thread + --version Version information + + + + Running mythbackend as a daemon and using the logfile option will + allow you to have mythbackend automatically start up during boot. You + can follow the steps outlined in the section called ``Automatically + starting mythbackend at system boot time'' for configuration steps. + + If you enable the -l parameter, you will want to keep your logfiles + rotated (so that they don't fill up a partition). See the section + called ``Automatically rotating logs'' for more information. + + + [1m9.3. Configuring a non-master backend[0m + + Ensure that you've granted access to the master MySQL database for + remote backends as discussed in the section titled ``Modifying access + to the MySQL database for multiple systems'' and that you have the + correct IP address for the database server in the "Database + Configuration" screen of the mythtv-setup application on this slave + backend. + + + + [1mNOTE[22m: Slave backends [1mmust not [22mrun a local MySQL + daemon. By default, they will connect to their local daemon rather + than the central database, causing unexpected behavior such as empty + "Watch Recordings" lists and a failure to locate the Video Sources + defined on the master backend. Modify the + /usr/local/share/mythtv/mysql.txt file on all slave backends to ensure + that the DBHostName has the address of the MySQL server. Caveat: You + may make a slave backend the primary MySQL server, or run a non-MythTV + database on a slave backend as long as you have edited the mysql.txt + file on [1mall [22msystems and made it consistent. There can be only one + authoritative MySQL database in a MythTV system - errors such as the + one above ensue if backends and frontends have differing ideas of + which MySQL database they should talk to. + + Make sure that the IP addresses on the General setup screen are + accurate. If the slave backend can't communicate with the master + backend due to IP address misconfiguration then MythTV will not + function properly. + + Configuration of a non-master backend follows the same general + procedure as that of the master backend, with the exception that you + skip over the "Video Sources" step. All possible video sources need + to be defined on the master backend system; only the master backend + will query a listings provider to obtain guide data for all the non- + master backends. + + + + [1mNOTE[22m: Do not run mythfilldatabase on a non-master backend. + + [1m9.4. Configuring and running mythfilldatabase[0m + + + + [1mNOTE[22m: [1mmythfilldatabase [22mmight take a while to complete, + depending on any number of factors, most of which you can't control. + It's best to just let the program run to completion. [1mmythfilldatabase[0m + [1m--help [22mwill give a full listing of the options available. + + [1mmythfilldatabase --manual [22mis another option; the manual option will + allow you to fine tune channel frequencies and specify which channels + will be added to the database. + + [1mmythfilldatabase --file [22mis an option if there isn't an XMLTV grabber + for your country, but you [1mdo [22mhave an XML formatted listings file + created by some other program. + + [1mmythfilldatabase --xawchannels [22mis an option if you have used [1mxawtv [22mto + fine-tune your channels and would like to import the fine tuning + offsets into MythTV. + + [1mmythfilldatabase --refresh-today [22mwill only pull guide data for today + (in case of late-breaking changes to the schedule). + + + + [1m9.4.1. Periodically running mythfilldatabase[0m + + In order to keep your database filled, [1mmythfilldatabase [22mshould be run + once a day. + + To use MythTV's built-in capability, you'll need to run the + [1mmythfrontend [22mSetup option. From the mythfrontend, enter the + Setup>General screen and advance to "Mythfilldatabase", the fourth + screen. Select the checkbox, then complete the options as you see + fit. The [1mmythbackend [22mprogram will now run [1mmythfilldatabase [22mfor you. + + + + [1m9.5. Grabbing channel icons for Schedules Direct users[0m + + While the Schedules Direct TV listings service has several advantages, + it does not support grabbing logo icons for the stations you receive. + However, there are utilities provided with MythTV which you may use to + grab your initial set of icons and to keep them updated if your + lineups change. + + First, you need to generate or obtain an XML file with the information + for your stations. + + If you have XMLTV software installed, there is a perl script in + MythTV's contrib/ directory which will generate this file for you. Run + the command: + + + $ perl mkiconmap.pl + + + + You will be asked for your zip code and the service that you use. If + there are no errors, the iconmap.xml file that you need for the next + step will be created. + + If you do not have XMLTV software installed and do not want to install + it for the sake of this minor task, there is a generic + contrib/master_iconmap.xml which you can copy and use but this may not + be as complete as using the specific information for your service. + + Once you have an iconmap.xml file, add the icon information to your + database and grab any new icons with the command: + + + $ mythfilldatabase --import-icon-map iconmap.xml --update-icon-map + + + + [1m10. Configuring mythfrontend.[0m + + Once you have completed configuration of your backend systems, the + next step is to configure the frontend client. + + When you start mythfrontend for the first time, it will attempt to + connect to a configuration database on the local machine. If there is + none, a "Database Configuration" screen will appear, and you will need + to fill in some details. The "Host name" field needs the backend or + database server's IP address or DNS name, and the User or password + fields may need to be set to match your database user accounts. After + editing those fields, press Enter twice to write these configurations + on your local machine, and attempt to connect to the database. If you + make any mistakes, the screens will pop up again. + + Now that mythfrontend has started up, you should have a number of + buttons/choices. Before doing anything, go to TV, then to Setup and + configure the frontend client. + + + + [1mNOTE[22m: You should go through the various setup screens in + mythfrontend before using any other modules to ensure that the the + database is correctly initialized. + [1m10.1. General[0m + + The General screen has configuration items that don't really fit + anywhere else. The first few configuration items ask you to indicate + the number of seconds to record before or after a program, which is + useful if the broadcast network or your system clock are out of sync + and will help prevent you missing the beginning or end of a program. + + To change the value, use the left and right arrow keys to increment + and decrement the number of seconds. When you're satisfied with the + result, use the down arrow to put the input focus on the Next button + or press RETURN to continue to the next page. + + The next page has a number of options to do with how channels are + displayed on your system. The help text will give you more + information. Move the focus to Next and press the space bar to + continue. + + The last General page sets up some final configuration items. See the + help text for more information. + + + [1m10.2. Appearance[0m + + This set of screens is mostly concerned with how MythTV will look on + your system. From here, you can choose different themes and set the + resolution of your system. + + + [1m10.3. Program Guide[0m + + Fairly self explanatory. Note that the alternate program guide does + not use the same font settings as defined in Appearance, so if the EPG + is unreadable this is where you make the adjustments to fonts, number + of elements displayed, etc. + + + [1m10.4. Playback[0m + + The one configuration item which may cause problems on your system is + the "Deinterlace playback" setting. MythTV uses a linear blend + algorithm for deinterlacing, which will improve how the image looks on + your screen. Deinterlacing requires that your processor support SSE. + (Streaming SIMD Extensions, aka "MMX2"). Early Intel Celeron (those + that don't use the Coppermine 0.18um core and are usually <600MHz), + Pentium Pro and Pentium II CPUs do not have SSE, so make sure you + haven't enabled deinterlacing if your processor doesn't support it. If + you enable it, and your processor doesn't support SSE, you will get + "Illegal Instruction" errors. + + To determine if you've got SSE on an Intel processor, you can: + + + $ cat /proc/cpuinfo + [snip] + flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca + cmov pat pse36 mmx fxsr sse + + + + Notice the [1msse [22mat the end of the line - this tells you that this + processor will be able to deinterlace correctly. + + On an AMD processor, look for "3dnow" in the cpuinfo line; "3dnow" is + AMD's implementation of SSE instructions, so if your processor has + 3dnow you shouldn't have any issues with deinterlacing. + + [1m10.4.1. Video Filters[0m + + MythTV provides a means of employing video filters while recording and + during playback. These filters can be used to improve or modify the + video image, including hiding the effects of an interlaced image or + reducing the impact of noise in a poor video signal. The following is + a brief introduction to introduce you to the filters that are + available in MythTV version 0.20 and higher. + + [1m10.4.2. Applying filters[0m + + One or more filters can be included in a "filter chain". The filters + to be used are identified in a "filter string". A filter string is a + group of filter names and parameters separated by commas. To include + parameters, the filter name is followed by "=" and the parameter + information. There should be no spaces in the filter string. Here is + an example filter string: + + With parameters: kerneldeint=10:1,denoise3d=12 + + Without: kerneldeint,denoise3d + + Recording filters are set for each individual channel. These may be + used when encoding in software (MPEG-4, RTjpeg) but do not apply when + using a capture card with hardware encoding such as those supported by + the ivtv driver, DVB, HDTV or MJPEG cards. You can run MythTV's + "setup" program and select the "Channel Editor". On the first page for + each channel, you can enter a filter string in the box titled "Video + filters". If you are running "mythweb" on your web server, you can + click on "Settings" then "Channels" and enter filter strings in the + "videofilters" column. + + Playback filters are per-host and apply to any recording you watch + from the frontend where filters have been applied. Playback filtering + can only work with software decoding so the viaslice, xvmc, and ivtv + outputs ignore filters entirely. From "mythfrontend" go to Setup->TV + Settings->Playback. Enter your filter string in the box titled + "Custom Filters". + + + [1m10.4.3. Currently Available Filters[0m + + "Deinterlace Playback" checkbox. + + This implements special behavior needed for the "bobdeint" filter but + can also be used to choose any of the deinterlace filters. If you + prefer, you may leave this unchecked and include any of the + deinterlace filters, other than "bobdeint", in your custom filter + chain. + + o The "invert" filter + + Invert ignores any parameters and inverts the pixel values of the + video frames. In other words, a negative image. This would rarely be + useful but may be a good example to verify that your filter strings + take effect. + + o The "linearblend" filter + + It is a simple deinterlacing filter that ignores parameters and works + by blending adjacent lines. It replaces combing in interlaced video + with a less distracting "ghost" image. + + + o The "bobdeint" filter + + This filter splits the interlaced image into two separate fields that + can be line doubled then displayed at twice the frame rate. If the + display is at the same refresh rate as the recording (59.92Hz NTSC or + 50Hz PAL) this will cause each refresh to show objects in motion in a + new position with no jagged edges. However, if the display is not + synchronous, it will cause flickering or the appearance of the picture + moving up and down by one line. + + + + [1mNOTE[22m: This filter requires the frame rate to be doubled + and therefore can only be used with the "Deinterlace Playback" + checkbox. Do not include this in your filter chain. + + o The "kerneldeint" filter + + Kerneldeint is a more complex deinterlacing filter which applies a + filter kernel using input from several lines. It generally removes + combing without a "ghost" image, sometimes leaving a faint outline of + the image from the other field. It is considered to be less + distracting to watch than linearblend or no filter at all. It accepts + one or two integer parameters separated by a colon. + + The first parameter is the filter threshold and defaults to 12. + Adjacent lines differing by more than the threshold value are + filtered. The second option defaults to 0. If set to a non-zero + value, it will cause the filter to skip chroma, and filter only the + luminance. It may be useful on some capture cards which do not + capture the chroma fields of interlaced video correctly. + + o The "onefield" filter + + This is a simple one-field deinterlacing filter that uses only one + field of the interlaced video. By default it keeps the top field, + though passing the parameter "bottom" will cause it to keep the bottom + field instead. + + This filter is primarily useful for those who display 1080i HDTV + signals with a video mode that has 540 pixels vertically. The + advantage over other deinterlacing filters is that scenes with motion + never show combing or ghosting. + + o The "adjust" filter + + This filter adjusts the digital values for luma and chroma to ensure + that they will fall within the ranges specified in the ITU-R601 + standard. By default, this corrects a known problem for the luma range + used by bt8x8 chips which causes video to look washed out. If + parameters are passed, there need to be exactly six. However, passing + a single parameter of "-1" will disable the filter. + + 1: luma minimum input value (int) 2: luma maximum input value (int) 3: + luma gamma correction (float) 4: chroma minimum input value (int) 5: + chroma maximum input value (int) 6: chroma gamma correction (float) + + The default bt8x8 correction values are equivalent to + "16:253:1.0:2:253:1.0". Output ranges are fixed at ITU-R601 values + (16-235 luma, 16-240 chroma). + + [1mNOTE[22m: If it is not already specified in the filter chain, this filter + will be automatically applied when recording with the "bttv" driver. + o The "quickdnr" filter + + A fast temporal denoiser. This can take 1, 2 or 4 parameters, each + being a value from "0" for the least filtering to "255" for the + greatest filtering. With one parameter, the filter will compute the + values it should use for all of its variables. Two parameters will set + the filter strength for luma and chroma independently. If you are + interested in how the algorithm works, you may examine the source code + to see how four parameter are used. + + o The "denoise3d" filter + + A slower denoiser that applies a spatial and temporal low-pass filter. + The spatial filter can remove some noise that quickdnr can't, but a + more powerful CPU is needed. This filter accepts 3 float parameters: + + + +o luma spatial filter strength + + +o chroma spatial filter strength + + +o luma temporal filter strength + + Reasonable defaults will be selected for omitted parameters. The + chroma temporal filter strength is calculated from the other filter + strengths. + + o The "crop" filter + + Covers edges of video with black bars. This helps improve video + quality when the edges of the frame are distorted. By default, this + removes 16 pixels from each edge. This can optionally take four + parameters representing top:left:bottom:right. The number times 16 is + the number of pixels to remove so, for example, the default is + "=1:1:1:1". + + o The "forceyv12" and "forceyuv422p" filters + + These force the filter manager to use the given format. You can use + one of these at the head of a filter chain to change the capture + format. The most likely use would be forceyuv422p to use YUV422P + capture on cards with known chroma interlacing problems with YV12. + + There are some filters included in the MythTV source code that should + not be used: + + o The "forcergb24" and "forceargb32" filters + + The two RGB formats should not be used because there is no conversion + filter for them yet. + + o The "convert" filter + + It exists but don't use it. The filter manager uses this filter + automatically when it is unable to match the input/output formats of + two adjacent filters. + + o The "postprocess" filter + + While this exists in MythTV source code, it is currently not + recommended for use. + + + + [1m10.4.4. Usage Considerations[0m + + There are trade-offs to consider when deciding if it would be wise to + use a filter. Any processing will modify the original image so you + should assess if the filter has made a noticeable improvement to the + picture in order to justify the impact of the processing. Adding any + filter will inherently increase CPU usage. The impact can vary + dramatically depending on your CPU type and speed, the resolution of + the recording, which filters you are using and other factors. You can + only determine what is right for you through experimentation. However, + as a starting point, here are some filter strings that you may find + useful: + + For typical broadcast stations: "kerneldeint,quickdnr" + + For stations with poor signal quality: "linearblend,denoise3d=12" + + For synchronous TV-out: check Deinterlace with "Bob (2x framerate)" + + + [1m10.5. Recording[0m + + Depending on your capture card, MythTV offers different video + encoders. The following types of hardware encoding cards are + supported: + + +o MJPEG - Zoran-based cards; see http://mjpeg.sourceforge.net + <http://mjpeg.sourceforge.net> + + +o MPEG-2 - iTVC15/16 based cards (Hauppauge PVR-250/PVR-350); see + http://ivtvdriver.org <http://ivtvdriver.org> + + +o HDTV - pcHDTV cards; see http://pchdtv.com <http://pchdtv.com> and + the Air2PC-ATSC-PCI see + http://www.cyberestore.com/product_info.php?cPath=28&products_id=103 + <http://www.cyberestore.com/product_info.php?cPath=28&products_id=103> + + +o DVB - cards supporting DVB; see http://linuxtv.org + <http://linuxtv.org> + + For cards without hardware encoding capabilities (all cards + supported by V4L not listed above), Myth includes two methods for + software encoding: RTjpeg and MPEG-4. RTjpeg has significantly + fewer CPU demands than MPEG-4, but it generates larger files than + MPEG-4 for a given recording. + + For DVB and HDTV cards, no further configuration is required after + setting up the card using the 'mythtv-setup' program. For all other + cards, configuration is done through MythFrontend. Selecting + 'Recording Profiles' from the 'TV Settings' screen will list the + profiles currently available for the cards in your system. Depending + on what types of cards you have installed you may see: + + + (Create new profile group) + Software Encoders + Hardware MPEG Encoders + Hardware MJPEG Encoders + Transcoders + + + + The '(Create new profile group)' option will allow you to create cus- + tom profiles in case you have multiple backends. Note that custom + profiles are per backend and card type. If you have 2 MPEG-2 encoders + in a given backend system, creating a custom profile will affect both + of them. This option should not be needed otherwise. + + The 'Transcoders' group is a little different from the others. + Selecting this group will result in a menu with the following options: + 'RTjpeg/MPEG-4' and 'MPEG-2'. These types indicate what transcoder + options will be used for a given input type (i.e. the 'MPEG-2' + settings would be used to transcode MPEG-2 files into MPEG-4. The + source of the MPEG-2 stream (DVB, HDTV, or PVR-x50) does not matter. + Configuration of the options is the same as below (although any + resolution settings will be ignored). + + Selecting any of the other options will show a new screen with a list + of four profiles: + + +o Default + + +o Live TV + + +o Low Quality + + +o High Quality + + The Default profile will be used for any recording which does not + otherwise have a specific profile assigned. The 'Live TV' profile will + be used when watching TV. The remaining two profiles are available + for customizing to allow for more precise control over what quality is + used for a given program. + + Selecting a profile will allow you to adjust the relevant options for + that card. The most significant setting is the recording resolution, + but you can also choose encoding format, audio format, and tweak other + encoder specific properties. + + + + [1mNOTE[22m: although the width and height can be changed to almost + anything, if you start MythTV and don't see video or you get + "segmentation fault" errors, it is likely that the video4linux (v4l) + subsystem did not like the height and width parameters specified. + It's best to leave the default as-is until you're sure that MythTV is + operational. + + See the ``What capture resolution should I use? How does video work?'' + section for more information. + + + [1m10.6. Xbox Frontends[0m + + MythTV is able to control the LED on the Xbox to indicate backend + recording status. + + To control the LED, you will need the [1mblink [22mprogram from the xbox- + linux project, which is installed as /bin/led on GentooX. On Xebian + (the new Ed's Debian) you must install it yourself. On other + distributions it may or may not be installed as a program called [1mblink[0m + and should be located in your path. (Type which blink to see if the + program is available.) If you do not have [1mblink[22m, you may obtain it + from the Xbox-Linux project site at http://xbox-linux.sf.net/ + <http://xbox-linux.sf.net/>. The program you need is part of the + eds_i2c_staff module in CVS. Note the spelling. + + + Once you have installed [1mblink [22myou will need to set permissions. [1mblink[0m + needs write permission to the i2c device to function properly. There + are three methods to accomplish this. First, you could run + mythfrontend as root, which is the simplest method, but could + potentially be a security risk. Next, you may make the [1mblink [22mbinary + setuid root, which allows non-privileged users to run a program with + root capability. This is done by typing the command: + + + $ su + # chmod u+s /path/to/blink + + + + The final technique would be to set the /dev/i2c/0 device read/write + for all users, but this is the least preferred method. + + Now it's time to setup MythTV for Xbox hardware. Enter Setup -> + General. On the second page check the 'Enable Xbox Hardware' option. + Upon reentering the settings, you should have a new option named + 'Xbox'. Within this option you may select the distribution, LED + colors for recording and the update interval. If you select GentooX + as the distribution [1mled [22mwill be used as the [1mblink [22mbinary name, + otherwise, [1mblink [22mis used. Colors should be self explanatory. The + update interval determines how often the frontend should poll the + backend to determine if the status has changed. + + + [1m11. Using MythTV.[0m + + + + [1mNOTE to Red Hat/Fedora 4 users[22m: Red Hat Linux and Fedora Core ship + with Gnome as the default desktop environment. However, Gnome seems + to have issues with window focus and window switching which sometimes + cause mythfrontend to obscure the video. KDE does not seem to have any + such issues. Therefore you will need to switch to KDE by selecting + RedHatMenu>Extras>System Settings>Desktop Switching Tool and choose + "KDE". [1mNOTE to Fedora Core 5 and 6 users[22m: Fedora 5 and 6 no longer + have this tool in the Menu. Use "switchdesk KDE" from a command line. + Read "man switchdesk" for further information about changing to other + desktop environments. + + [1m11.1. Keyboard commands[0m + + The keys.txt file describes what the various keyboard commands are. + If you have loaded mythweb, you may change the default keys to your + liking. + + [1m11.1.1. mythfrontend[0m + + + Arrow keys used to move the highlight point around + ALT-F4 exit out of the application + Space/Enter take action on the item under the highlight point + P play in both "Watch a Recording" and "Delete a Recording" + D delete in both "Watch a Recording" and "Delete a Recording" + U to view details for the currently selected show on the Watch or Delete screens, EPG, "Program Finder", "Fix Scheduling Conflicts" and search results screens + O to list the upcoming episodes for the currently selected show on the EPG, "Program Finder", "Program Recording Priorities", "Fix Scheduling Conflicts" or search results screens + I edit recording options from the EPG, "Program Finder", "Program Recording Priorities", or "Fix Scheduling Conflicts" screens. From the Playback and Delete screens, 'I' presents options for recorded shows such as Auto Expire or Stop Recording. Pressing 'I' while on the Recording Options screen will take you to the Advanced Recording Options screen. + + + [1m11.1.2. Watching TV or a recording[0m + + + Up or down keys change the channel + num pad Type a number to enter a channel number or jump amount (HHMM format) + P pause / play. You may also add an explicit keybinding for 'Play' through MythWeb, returning you to normal speed if you are in slow motion, rewind fast forward or pause mode. + C change inputs on TV Tuner card + ESC quits + I puts the On-screen Display up again. During playback, 'I' toggles between position and show description info. If a jump amount is entered, jump to that position. + M brings up the electronic program guide (Grid) -- see the EPG section + Page Up jump back the configured number of minutes (default is 10) + Page Down jump ahead the configured number of minutes (default is 10) + End or Z skip to next commercial break marker + Home or Q skip back to previous commercial break marker + T toggle close caption support Pressing 0-9 (preferably 3 times) + T changes teletext page and turns on teletext. + F rotate between the various Picture Adjustments (Colour, Hue, etc.) While Picture Adjustment is on-screen, use Left and Right arrows to adjust. These settings adjust the look of the video playback, and are independent of the G-key settings used at record-time. + [ or F10 decrease volume + ] or F11 increase volume + or F9 toggle mute + / jump to the next "favorite" channel + ? mark/unmark the current channel as a "favorite" + U increase the play speed + J decrease the play speed + A Adjust time stretch (speed up or slow down normal play of audio and video + W cycle through zoom and fill modes: 4:3 aspect ratio, 16:9, 4:3 Zoom (like Pan and Scan), 16:9 Zoom, and 16:9 Stretch (eliminates black sidebars in TV signal) + F8 toggle the sleep timer 30m->1hr->1hr30m->2hr->Off + CTRL-B Jump to the beginning of the recording / ringbuffer + + Switch between audio streams + Left (if a jump amount is entered) to jump back that amount + Right (if a jump amount is entered) to jump ahead that amount + + + [1mWithout the stickykeys option selected[0m + Left rewind the configured number of seconds (default is 5) + Right fast forward the configured number of seconds (default is 30) + < starts rewind mode as if stickykeys are selected + > starts fast forward mode as if stickykeys are selected + + + [1mWith Stickykeys option selected[0m + Right starts fast forward mode + Left starts rewind mode + + + [1mIn fast forward or rewind mode:[0m + Left/Right increases the ff/rew speed + 0 plays at normal speed, but leaves the time indicator on screen + 1 or 2 plays back more slowly than normal ff/rew speed (1 is slowest) + 3 plays back at normal ff/rew speed + 4-9 plays back faster than normal ff/rew speed (9 is fastest) + Space exits fast forward or rewind mode + + + [1mWhile video is paused:[0m + Left rewind 1 frame + < rewind 1 second + Right advance 1 frame + > advance 1 second + + + [1m11.1.3. Watching TV only[0m + + + + G rotate between the various Picture Adjustments (Colour, Hue, etc.) for recording. These values affect the look of the resulting .nuv file, and are independent of the playback picture settings. While Picture Adjustment is on-screen, use Left and Right arrows to adjust. + H Channel history. Each repeat steps back through the previous channels. + O Turns on 'Browse' mode, allowing user to browse channels and program info while watching current show FullScreen. + Y switch between multiple capture cards. [1mNOTE[22m: you will lose your LiveTV buffer on your current card. Useful for different-sourced cards (such as Dish Network on one, HDTV over-the-air on another card.) + + [1m11.1.4. LiveTV Browse Mode[0m + + + Left browse program prior to current listed program + Right browse program following current listed program + Up browse program on channel above current listed channel/program + Down browse program on channel below current listed channel/program + / browse program on next favorite channel + 0-9 enter a channel number to browse + Space/Enter change channel to channel of current listed program + R/r Toggle recording of current program (cycles through types) + ESC/O Exit Browse mode + + + [1m11.1.5. Playback Recording Zoom Mode[0m + + + Left Move video to Left + Right Move video to Right + Up Move video Up + Down Move video Down + PageUp Zoom In + PageDown Zoom Out + Space/Enter Exit Zoom mode leaving picture at current size and position + ESC Exit Zoom mode and return to original size + + + [1m11.1.6. If you have two or more tuner cards[0m + + + V toggle Picture-in-picture on or off + B toggles the window focus (lets you change channels on the PiP window) + N swaps the two channels by changing channels on both cards + + + [1m11.1.7. Watching a recording only[0m + + + Space/Enter set a bookmark at that point. Next time you start the recording, you will automatically jump forward to this point and clear the bookmark. + X queues the current recording for transcoding + O brings up menu to allow toggling settings such as Commercial Auto-Skip, Auto-Expire, etc. + D exits the current recording and displays the Delete menu + E or M enters/exits edit mode. + + + [1mIn edit mode[0m + Left/Right move forward and backward + Up/Down alter the amount of time you jump forward and backward. Increments are: nearest cutpoint, nearest video keyframe, 1 frame, 0.5 seconds, 1 second, 20 seconds, 1 minute, 5 minutes, and 10 minutes. + PageUp/PageDown move forward and backward to the nearest cut point + < or > move forward or backward by 10 times the normal jump amount + Space/Enter allows you to set or delete a cut point + Z loads the commercial skip list (if one exists) into the cutlist + C or Q clear all cut points in the cutlist + I Inverts the cutlist + + + [1m11.1.8. EPG[0m + + + + Arrows are used to move the highlighted program point around + A, D, S, W perform the same as left, right, down and up + PageUp/PageDown move the channel list up or down a page + Home/End move the highlight left or right by one day + Ctrl+Left or < move the highlight left by one page + Ctrl+Right or > move the highlight right by one page + 9, 3, 7, 1 (like a numeric keypad) perform the same as PageUp, PageDown, Home and End + I bring up more information about a show, and allow you to schedule a recording. If you select "Record this showing" while watching Live TV you can "Instant Record" a program. + Space/Enter allow you resolve conflicts or change overrides. If the program is not already scheduled to record, it will instead act like pressing 'I'. + M when on a channel will change to that channel + ESC or C exits without changing the channel + R change the current item from Recording/Not-Recording. Successive keypresses cycle through the scheduled recording type list. + X change the channel to the currently selected channel without leaving the EPG (Most useful in the alternate EPG) + ? mark/unmark the current channel as a "favorite" + / or 4 toggle the guide listing between all channels and filtered "favorites" + + [1m11.1.9. Setting Program or Channel Recording Priorities[0m + + + Right increases priority value + Left decreases priority value + 1 sorts by title + 2 sorts by priority + Home/End toggle sort priority + I edit recording options + ESC commits changes and exits + + + [1m11.1.10. Viewing Scheduled Recordings/Resolving Conflicts[0m + + + 1 show all recordings + 2 show only important recordings + Home/End toggle show showing all/important + I edit recording options + Space/Enter resolve conflict or override + + + [1m11.1.11. Viewing Search Listings[0m + + + Home change to the previous view if applicable + End change to the next view if applicable + M select another view if applicable. In the title and description search popup, press M again to edit or delete the selected view. + + + [1m11.1.12. Recording Profiles Setup Screen[0m + + + D on a custom profile group displays a popup to delete the group + + + [1m11.1.13. Recording Groups[0m + + In the Watch Recordings screen, Recording Groups allow you to separate + programs into user-defined categories, such as "Kids", "Alice", "Bob", + etc. This can be used to reduce clutter, or to segregate content if + you use the PIN function. + + M change the view or to set a group password + I move a program from one Recording Group to another + + + + [1m11.1.14. Watch Recordings Screen[0m + + + 1 or F1 Meaning of the icons + / Tags a recording. Tagged recordings can be played either in order or shuffled and deleted as a group. You can also change the recording group for several recordings at once by tagging them and using the Menu (m) button, selecting "Playlist options", then "Change Recording Group". + ? Clear the tagged list. + + + [1m11.1.15. Remote Controls[0m + + If you are using MythTV with just a remote control then it is + suggested that you map the remote control keys as described below. + Your remote control may not have the same set of keys as those named + below, the names are only a suggestion that roughly correspond to the + function. + + If you are adding new key bindings to the program then consideration + of this suggested list will help users with remote controls. + + This list assumes a minimal remote control that only has 20 keys, + nearly all features can be used with this configuration. If you have + more keys then you can access all of the features. With only 16 keys + most features are usable. + + REMOTE CONTROL LIRC KEYSTROKE FUNCTION + 0 - 9 0 - 9 channel selection, EPG navigation, ff/rew speed setting (with stickykeys) + Left Arrow Left scroll left, rewind + Right Arrow Right scroll right, fast forward + Up Arrow Up scroll up, channel change up + Down Arrow Down scroll down, channel change down + Select / OK / Play Space Select item, play (with stickykeys) set bookmark + Cancel Escape Cancel, quit playback + Menu m EPG (from watching TV) edit (from playback). + Pause p Pause + Other key 1 i Information + Other key 2 c Change tuner card input + + + + [1m11.2. Using themes with MythTV[0m + + MythTV is "themeable", meaning that the visual appearance of the + program can be modified by the user without re-compiling or altering + the program functionality. Download the MythThemes tarball from the + website and untar it: + + + + $ tar -xjf myththemes-0.21.tar.bz2 + $ cd ~/myththemes-0.21 + $ qmake myththemes.pro + $ su - + # make install + # exit + $ + + + + The theme will now be available in the mythfrontend Appearance + section. + + + + [1m11.3. Adding DishTV information to the database[0m + + A script for adding Pay Per View information into the MythTV database + for DishTV subscribers is available at http://www.mythppv.com/ + <http://www.mythppv.com/>. + + + [1m11.4. Adding support for an external tuner[0m + + MythTV supports changing the channel on an external tuner. If you + have an external tuner, such as a DirecTV or digital cable set top + box, you should add /usr/local/bin/changechannel to your Input + Connections in the mythbackend configuration GUI. + + However, there is not [1mchangechannel [22mprogram per-se, because this is + going to be dependent on what sort of external tuner you have. Look + in the contrib/channel_changers directory for a number of programs and + scripts which may be used to change channels. Once you find one which + works, copy it to /usr/local/bin/changechannel. + + Feel free to browse some of what sort of hardware is available at + http://store.snapstream.com/accessories.html + <http://store.snapstream.com/accessories.html>, or if you wish to + assemble your own, rather than purchase, the following may be helpful: + http://www.dtvcontrol.com/ <http://www.dtvcontrol.com/> for cable + pinouts. + + + [1m11.5. Using Shutdown/Wakeup[0m + + What does the MythTV Shutdown/Wakeup function do? The scheduler on the + Master backend (MBE) keeps track of the idle status of the entire + MythTV system, including the Slave backends (SBE). If it considers the + system to be idle, and thus ready to shutdown, it sets the wakeuptime + to the time of the next recording and then proceeds to shut down all + Slave backends and then itself. Once it is time to begin recording, + the Master backend and the Slave Backends are automatically woken up. + This system allows MythTV to record like a normal VCR, thereby + conserving power when not in active use. + + In order to use the Shutdown/Wakeup function there must be some method + of waking up the Master backend. There are any number of solutions, + but we will discuss in detail two possibilities: + + + +o Use another server that runs 24/7 and have it send a WakeOnLAN + (WOL) packet to wake the Master backend. This assumes that you + have the WOL tools installed, and that your Master backend + motherboard supports WOL. + + +o Use your motherboard's BIOS wakeup capability. You'll need a + motherboard that supports BIOS wakeup, and some tools. Two that + work are: http://sourceforge.net/projects/nvram-wakeup + <http://sourceforge.net/projects/nvram-wakeup> and + http://www.malloc.de/tools/wakeup_clock.html + <http://www.malloc.de/tools/wakeup_clock.html> + + + [1m11.5.1. A deeper look into the operation[0m + + The scheduler keeps track of the idle status of the MythTV system. To + determine whether or not the MythTV system is idle, the following + conditions must be met for a period of time defined in the "Idle + timeout (secs)" parameter. + + + +o no client is connected to the server + + +o no recording (neither LiveTV nor a regular recording) is currently + taking place + + +o no recording starts within a definable amount of time ("Max. wait + for recording (min)") + + +o the "pre Shutdown check-command" returns 0 + + If we get to this idle state the Master backend will set the + wakeuptime using the "Set wakeuptime command", which is the same for + WOL and BIOS wakeup. The Master backend will then shut down the Slave + backends and itself using the "Server halt command". + + One caveat is that the scheduler tries to guess if the Master backend + was started by a wakeup call or by the user. If it thinks it was woken + up by a user, it blocks shutdown until a client connects to the Master + backend, after which it will behave as described above. To disable + this feature, unset "Block shutdown before client connected" in the + mythfrontend Setup->Setup->General screen. + + Once it is time to startup the system, the Master backend is woken up + first and will wakeup the Slave backends using the "Wake command for + slaves". At this time, there is no support for starting only the + required Slave backend, so all Slave backends will startup. + + + [1m11.5.2. Setting up the MythTV side of this extension.[0m + + There are a number of options that are used to control the Shutdown / + Wakeup feature. + + Shutdown/Wakeup Options: + + +o "Idle timeout (secs)" is the time the server waits while idle until + a shutdown occurs. + + +o "Max. wait for recording (min)" is the time the Master backend + waits for a recording without shutting down. For example, this + would be used to prevent a 10 minute system shutdown if a recording + is set to start 15 minutes from now. + + +o "Startup before rec. (secs)" Sets how long before a programmed + recording the MythTV system will be woken up. This should be + roughly be the time your systems need to bootup, and if you have + Slave backends, you'll need to ensure this value is long enough for + all your machines to perform their bootup cycle. + + +o "Wakeup time format" is the format of the wakeup time that is given + in the "Set wakeuptime command" as a parameter "$time". You need to + set this according to your wakeup mechanism. If you need seconds + since the epoch (1970-01-01) set the "Wakeup time format" to + "time_t". + + +o "Set wakeuptime command" is the command executed to set the new + wakeuptime. + + +o "Server Halt Command" is the command executed to shutdown the + Master backend and the Slave backends. + + +o "pre Shutdown check-command" is used to give a "Go/NO-GO" decision + from a non-MythTV source. This command is executed immediately + before the shutdown would occur. The return value is use to make + the following choices: + + +o If it returns a "0" the shutdown will occur as scheduled. + + +o If it returns a "1" the "idle timeout" will be reset and the + system waits again for the timeout. + + +o If it returns a "2" the entire shutdown sequence is reset. This + means that a new client connect is needed before a shutdown + occurs, unless you have the "Wait for client connect" setting + disabled, in which case this is the same as returning "1". An + example of a use for this return value is to prevent the + shutdown if a user is currently logged in, or if a specific + program (i.e. transcode, automatic updates, etc.) is currently + running. If you don't need it, leave the field blank. + + The "WakeOnLan settings": These settings have nothing to do with using + BIOS or WOL wakeup, they are the same for both. + + +o "Master backend" This setting defines timings for the frontends to + wakeup the Master backend using WOL. Useful if your frontend can + emit a WOL packet so you don't need to physically go to the Master + backend if you're trying to watch TV. + + +o "Reconnect wait time (secs)" is the time the frontend waits after + executing the "Wake command" before attempting to retry the + connection. This should be roughly the amount of time your Master + backend needs for bootup. Set to "0" to disable. The frontends + will retry to connect for "Count of reconnect tries" times before + giving up. + + +o "Wake command for slaves" is the [4mone[24m command executed to wake your + Slave backends. This should be a script that contains the calls to + wakeup all Slave backend systems. + + + [1m11.5.2.1. Using WOL to wake your Master backend.[0m + + To use WOL to wake your Master backend you will need a WOL capable + Master backend, a machine that runs 24/7 which can execute an at-job + and nc (netcat) on the Master backend. I use some little bash scripts + to make my DSL router wakeup my mythbox if required. + + Replace $SERVER and $PORT with your own settings! On my Master + backend I have a script that gets called as 'setwakeuptime command' + which looks like the following: + + + #! /bin/sh + echo $@ | nc $SERVER $PORT + + + + This simply cats the parameters (that is $time) to my 24/7 server. On + my $SERVER I have (x)inetd listening on $PORT starting a little script + which cares about setting the at-job. The following additions are nec- + essary on the $SERVER: + + If you use [1minetd[22m: + + In /etc/inetd.conf add: + + + mythwake stream tcp nowait mythtv /usr/sbin/tcpd /usr/local/bin/mythwake + + + + If you use [1mxinetd[22m, save the following as [1mmythwake [22min your + /etc/xinet.d/ directory: + + + service mythwake + { + socket_type = stream + wait = no + user = mythtv + protocol = tcp + id = mythwake + server = /usr/local/bin/mythwake + } + + + + and add the following to /etc/services: + + + mythwake $PORT/tcp + + + + Finally, /usr/local/bin/mythwake looks like: + + + #! /bin/bash + #this should be a command to wake your server + WAKECMD="#!/bin/sh\n /usr/local/bin/wakeMBE" + #first we need to delete all wake jobs in queue + for JOB in atq | cut -f 1 ; do + atrm $JOB; + done + #now we read the date from 'nc' + read date; + #now set the atjob + echo -e "$WAKECMD" | at $date ; + + + + [1mSECURITY WARNING[22m: Be sure to secure $SERVER:$PORT from untrusted net- + works, because this allows 3rd parties to run arbitrary code on your + server! + + + [1m11.5.2.2. Using BIOS wakeup to wake your Master backend.[0m + + Since I don't use this, I cannot say much about this. If your + motherboard supports any wakeup tool you have to call that tool as + "Set wakeuptime command" with the "Wakeup time format" suitable for + that tool. + + [1m11.5.3. Wakeup the MySQL server using WOL[0m + + If your MySQL server and your Master backend are not on the same + machine, you can have the Master backend wake your MySQL server using + WOL. You will find the settings for this in the second page of the + mythtv-setup program, or at the end of mysql.txt. The meanings are + the same as discussed in "The WakeOnLan settings" above. + + + + [1m11.5.4. Tips/Tricks:[0m + + If, for example, one of the Slave backends is also your desktop + computer, you could simply use a little script as 'server halt + command' which first calls /sbin/shutdown -t TIMEOUT where TIMEOUT is + a value sufficient for you to react. You could then popup a window + using *dialog, asking for permission to shutdown. If you cancel the + shutdown, simply call /sbin/shutdown -c. + + If you get "nvram-wakeup: /dev/rtc: Device or resource busy" your set- + wakeuptime-script should stop the program that uses /dev/rtc before + setting the wakeuptime. + + [1m11.6. Controlling the mythfrontend via telnet[0m + + To use this feature you must first enable it in + Settings>General>General + + The network control listens on port 6546, as demonstrated below: + + + + $ telnet basement 6546 + Connected to basement. + Escape character is '^]'. + MythFrontend Network Control + Type 'help' for usage information + --------------------------------- + # help + Valid Commands: + --------------- + jump - Jump to a specified location in Myth + key - Send a keypress to the program + play - Playback related commands + query - Queries + exit - Exit Network Control + + Type 'help COMMANDNAME' for help on any specific command. + + # help jump + Usage: jump JUMPPOINT + + Where JUMPPOINT is one of the following: + channelpriorities - Channel Recording Priorities + channelrecpriority - Channel Recording Priorities + deletebox - TV Recording Deletion + deleterecordings - TV Recording Deletion + guidegrid - Program Guide + livetv - Live TV + livetvinguide - Live TV In Guide + mainmenu - Main Menu + ...snip... + # exit + $ + + + + Please note that this feature only allows one connection at a time, so + any new connections will automatically terminate prior ones. + + + [1m12. Scheduling Recordings.[0m + + The MythTV master backend is responsible for managing the schedule for + all TV tuner cards on the master and any slave. Its job is to search + the TV listing for the shows you have requested and assign recordings + to the TV tuner cards. If none of the shows that you've chosen + overlap, it simply records all of them. However, if there are shows + where the beginning and end times overlap, the scheduler follows rules + that you've specified or makes logical decisions about what would be + best if you haven't expressed your preference. Further, the "Upcoming + Recordings" page allows you make specific decisions about what you + really do and don't want to record. + + + [1m12.1. Record Types[0m + + When you choose a show that you would like to record from the Options + Page, there are eight different types of rules to help the scheduler + find which showings you would like to record. + + + +o Single Record -- record only this title at this specific time and + this station. This is the best way to be sure that a certain + showing will be recorded. However, if the TV listings change and + the show is not broadcast at that time, the show will not be + recorded but will be marked as Not Listed to let you know that you + should investigate. + + +o Find One -- this will record a title once from any of the times + that appear in the TV listings. This is useful for recording a + movie or special that has multiple showings because it allows the + scheduler to choose one that doesn't conflict. It is not a good + choice for recording a single episode of a series because it + records the first available showing of the title without regard to + the episode information. + + +o Record Weekly -- this records a show whenever the title is listed + on the same channel, weekday and time. Note that if the TV station + changes the schedule for a special episode, it would not be + recorded. However, you can add a Single record for the special + episode. If there are no matching showings in the TV listings, a + Not Listed item will be added to your schedule for the next time + slot to let you know that you should investigate. + + +o Find Weekly -- this will record a title once per week from any of + the times that appear in the TV listings beginning from the time of + the showing that was selected when the rule was set. This is useful + for news, current events or other programs where the same episode + is shown several times each week but the listings may not include + descriptive information. This may not be a good choice if there are + different episodes shown during the week. + + +o Record Daily -- this records a show whenever the title is listed + for the time and station on any day of the week. Here again, a show + will not be recorded if the time was altered by the station. If + there are no matching showings in the TV listings, a Not Listed + item will be added to your schedule for the next time slot to let + you know that you should investigate. + + +o Find Daily -- this will record a title once per day from any of the + times that appear in the TV listings beginning from the time of the + showing that was selected when the rule was set. This is useful for + news, current events or other programs where the same episode is + shown several times each day but the listings may not include + descriptive information. This may not be a good choice if there are + different episodes shown during the day. + + +o Channel Record -- records one showing of each unique episode from + any of the times the title is listed on this station. This is + perhaps the most common rule to use for most shows. + +o Record All -- records one showing of each unique episode from any + of the times this title is listed on any channel. This can be + useful if a station has sister stations where shows are rebroadcast + allowing the scheduler to record rebroadcasts on the other station + when the original airing cannot be recorded. + + + [1m12.2. Scheduling Options[0m + + [1m12.2.1. Priority[0m + + By default, all shows you select have equal value to the scheduler. + There are a set of rules to make good choices when two or more shows + are in conflict. However, priority values let the scheduler know what + you prefer so that it can set the schedule based on your preferences. + + Initially, recording rule priority values are set to zero. You may + choose to leave everything at "0" and let the scheduler follow rules + to guess what you might prefer when there are conflicts. However, if + you have one or two favorite shows, you may want to increase the + priority value so the scheduler will know that you would prefer + recording these over other shows. You might use certain values to rate + shows so that all favorites are 2. good shows are 1 and extra 'filler' + shows are all -1 for example. You could sort each title on the "Set + Priorities" page to have a unique value so the scheduler can know + which show you'd prefer versus any other show. The choice and style + are entirely up to you. However, the more information you give to the + scheduler, the more likely it will make the choices you would prefer + in the first place. + + The scheduler choices are based on the total priority for a showing by + adding up all priority factors that match the showing. By default, + most of these factors are "0" but you may use any combination to + express your likes and needs. + + + +o Per record rule -- this is the "priority" selection in the + "Scheduling Options" section of the options page and this value is + included for any showings that match the recording rule. You may + choose to only use these values and not use the other factors for + the sake of simplicity and clarity. + + +o Per record type -- Setup->TV Settings->Recording + Priorities->General allows you to add to the priority based on the + type. It may make sense to increase the value for "Single" so that + by default they have an extra advantage over other shows. The + default is +1. You may want to decrease the value for Find rules so + that they will be less likely to interfere with regularly scheduled + shows and will be more likely to record in a non-conflicting time + instead. The default is -1. + + +o Per channel -- Setup->TV Settings->Recording Priorities->Channel + Priorities can be useful if you believe that you prefer any of the + shows on certain channels. This would give all shows on a channel + an advantage by default. + + +o Input priority -- in the "mythtv-setup" program, the "Input + Connections" section allows you to add additional priority in the + "Input priority". This is simply another priority factor but has + an interesting effect. If a card input has a higher value than the + other cards, the scheduler will see that you would rather record + showings of episodes on this input rather than a showing on other + inputs. If you have multiple cards of different quality, you may + want to set input priority to encourage the scheduler to record + shows on your best card(s) whenever possible. This can also be + useful if you have multiple video sources which include the same + stations. For example, with digital and analog cable you could + increase the digital cable input preference by 1 to tell the + scheduler that you want to record from the digital channel whenever + possible but the channel on the analog input could still be used + when the digital input is busy. + + +o Custom Priority -- this allows you to add any specialized factors + you would like in order to influence scheduling decisions. See the + ``Custom Priority'' section below. + + For any single showing of any show you've chosen to record, these + factors are added together to find the "total priority". This is + the priority that the scheduler uses to decide which showings are + given the first choice when filling in the schedule. + + The scheduling priority of a show may also be used to determine auto- + expiration of recordings when disk space gets full (see ``Auto- + Expire'', below). + + + [1m12.2.2. Duplicates[0m + + Singles will record without regard to duplicate matching. + + + The standard recurring methods of All, Channel, Weekly and Daily use + the descriptive information in the TV listings to try to record only + one showing of each unique episode. However, This goal is sometimes + complicated by the fact that the stations may not include a + description for a specific episode but use a generic description for + the series instead. When there is a generic description, the default + behavior is to assume that it may be an episode that you have not seen + and to record it for you. One of the duplicate matching options is + "Record new episodes only". If this is selected, listing that have an + original air date of more than 14 days earlier are considered repeats + and are not eligible to record. Generally, generic episodes will be + marked as repeats also. + + + Because of generic episodes and other situations, MythTV offers an + alternative approach where shows may be recorded by choosing from + multiple showings even when the descriptive information is not + reliable. All of the "Find" record types look for matching titles in + the listings. If there is a showing with specific episode information + and that episode has recorded before, that showing is marked as + previously or currently recorded. The scheduler will then choose to + record the earliest non-conflicting showing from any of other + remaining showings regardless of the descriptive information. + Generally, Find One is most useful for movies or specials and the Find + Daily and Find Weekly rules are best for news or current events shows + that are repeated. However, these may be useful in other situations + where the standard recording rules may not work correctly. + + + [1m12.2.3. Conflicts[0m + + As you add more shows that you would like to record, the scheduler + will eventually encounter conflicts. If there are two shows at the + same time and you have two or more TV tuner cards, both shows will + record. However, if there are more shows than cards, the scheduler + will have to decide what it thinks it should not record based on the + information you have given. If you see an unexpected situation you are + not "stuck" with the scheduler's choice. You can still tell the + scheduler exactly which shows you do want to record and/or don't want + to record in any situation. + + [1m12.2.4. Scheduling decisions[0m + + Here are the actual decisions made by the scheduler as it fills in the + schedule. + + + +o Currently recording beats not currently recording -- A recording in + progress can not be moved to another input or time so it "wins" its + current timeslot. + + +o Single, Daily, or Weekly rules with no match are marked Not Listed + -- If these or Overrides do not match the current listings because + the listings have changed, they are added to the schedule and + marked to indicate that they will not record. + + +o Rules that could record beat rules that can not record a showing -- + If two rules match the same showing of a program, a rule marked as + inactive or a showing marked as a repeat, for example, yield to the + other rule. + + +o More specific record type is used in place of less specific -- If + two rules match the same showing of a program, preference is given + to Don't Record then Override, Single, Find One, Record Weekly, + Find Weekly, Record Daily, Find Daily, Channel and finally All. + + +o Higher total priority beats lower total priority -- This is the + core of the scheduling process. Episodes of the highest priority + show are placed on the first available input followed by the next + highest priority show and so on. + + +o Future start time beats past start time -- If there is an episode + in progress and also a later showing of the same episode, it is + better to record the complete episode. If there isn't another + showing, it will start recording immediately to record the + remaining portion. This should only happen if you add a new rule + while the show is in progress or if the master backend is started + after the start time of a scheduled show. + + +o More specific record type beats less specific record type -- If two + shows are on at the same time and have the same total priority but + different types they will be sorted by Single then Find One, Record + Weekly, Find Weekly, Record Daily, Find Daily, Channel and finally + All. This only applies if the priorities are the same. + + +o If both start times have passed, later start time beats earlier + start time -- This attempts to miss the least amount of time. + + +o If neither start time has passed, earlier start time beats later + start time -- This helps assure that the earliest showing of an + episode has the advantage. + + +o Lower input id beats higher input id -- The scheduler fills in open + time slots on the first available input for the video source. The + next input is used when there is another show already placed for + the card of the first input. + + +o Older record rule beats newer record rule -- If two shows are still + equal after all of these other checks, the show whose record rule + was added first is preferred over a more recent addition. + + +o Postpone showings to resolve conflicts -- If Reschedule Higher + Priorities is set or if a conflict has the same priority as a show + that was scheduled at the same time, the scheduler will check to + see if a scheduled show can be moved to another input or later + matching showing without creating a new conflict so that the + conflicting show can be scheduled to record. + [1m12.2.5. Reschedule Higher Priorities[0m + + Setup->TV Settings->Recording Priorities->General has a checkbox for + "Reschedule Higher Priorities" which tells the scheduler to try to be + a little smarter in certain situations. If this is checked, the + scheduler will look for situations where a show cannot record because + all inputs for the channel are used for higher priority shows. It will + check to see if any of the other shows could be recorded at another + time so that the conflicting show can be recorded in its place. + + Generally, this is a good strategy but there are tradeoffs. If a + higher priority show is postponed, you will not get to watch it until + it is recorded in the later timeslot. There is also a risk that the TV + listings may change and the later showing may go away. In this rare + case the higher priority show may never record. On the other hand, if + you do not use this option you will miss recording some lower priority + shows unnecessarily unless you manually make similar changes. + + By using Reschedule Higher Priorities, the scheduler will do a better + job of recording as many of your shows as possible when left + unattended. It will also be easy to see that shows have been marked to + record at a later time. You can then decide for yourself when you + would prefer to record the first showing by clicking "Record anyway". + + + [1m12.2.6. Controlling Your Schedule[0m + + The Manage Recordings->Upcoming Recordings page is your control center + for the MythTV scheduler. Unlike other DVR systems, this one page + gives you all of the information and tools you need to see all of your + alternatives and make whatever adjustments you desire. + + The upper half of the screen has a scrollable box listing items that + match your record rules sorted by time. The lower half shows the + details for the highlighted item. There are two 'views' available. + Press "1" to include all of the items that match record rules even if + they do not need to be recorded. Press "2" to focus on just the things + that will record and items that may need your attention. The message + in the upper right-hand corner will remind you when there are + conflicts that would prevent one or more shows from being recorded. + + The items in the list are colored in the record color for things that + will record, white for things that may need attention, gray for those + that do not need to record and yellow when there is a time conflict. + Items at the top of the list may also be highlighted indicating that + the recording is in progress. + + Along with the channels, start times and titles, the right-hand column + has a status code. Numbers indicate which card number has been + assigned to record the show. Letters are used to indicate the reason + that something will not be recorded. Just below the box is a short + status message for the highlighted item that indicates the type of + record rule that was matched, the "total priority" for this showing + and a one or two word explanation of the status code. If you press + SELECT, you will see more information about the status. + + There are a few status codes that may require your attention. "C" + indicates that there are more overlapping shows to record than there + are TV tuners to record them. "L" indicates that the scheduler found + that it may be better to record a later showing of this episode. These + states happen as a result of your choices and should normally reflect + your preferences. However, you may notice situations where you would + like to modify the scheduler's initial choices. + + The first thing you can do is to highlight an item and press INFO to + see the recording options page. From this page you can change the + record rule type, the duplicate matching rules, or raise or lower the + priority to resolve whatever problem you noticed. + + Additionally, you can treat any individual showing as an exception + that you do want to record or don't want to record. To use these + "override" features, highlight the item and press SELECT. You will see + a message explaining the current status and at least an "OK" button to + exit without making changes. + + For items scheduled to record, there will be a button for "Don't + record" which will prevent recording this showing but will still allow + the same episode to record in the future. If there is episode + description information, you may also see a button for "Never record". + This prevents recording this showing and tells MythTV to remember that + this is an episode that you've seen or don't need to see if it is ever + in the TV listings again. + + For items that are not scheduled to record, the message will describe + the reason and in the case of "C" or "L" it will include a list of the + shows that are scheduled to record instead. For any item that could + potentially be recorded there will be buttons for "Edit Options" and + "Add Override". "Edit Options" will allow you to change the options + for the existing record rule such as raising the priority so that the + show will record. These changes would apply to this and all future + showings that match this record rule. "Add Override" will allow you + to set options that apply to the specific showing without affecting + the recurring record rule. + + If you return to an override page after an override has already been + set, you will also see a "Clear Override" to undo your changes. This + option makes it very easy to try out some "what if" attempts when + deciding on your best strategy in a difficult situation. + + For a recording in progress, there will be a "Change Ending Time" + button. This will take you to the options page for a Single or + Override or create an Override if it is a recurring rule. Here you can + go to the Recording Options section to change the program end time + offset. If you extend the end time so that it overlaps upcoming + recordings, the schedule will change to accommodate the new end time. + This may cause a conflict or later showing even for a show with higher + priority. Therefore, it is a good idea to check your schedule after + changing the end time of a recording in progress. + + + [1m12.3. Storage Options[0m + + [1m12.3.1. Recording Profile[0m + + Each recording rule can be configured with a different recording + profile. For example, colorful cinematography can be configured with + a "High Quality" profile, while 'talking heads' interviews shows can + be configured with a "Low Quality" profile. These recording profiles + need to be configured before using them (see ``Recording'', above). + + + [1m12.3.2. Recording Group[0m + + For organization of the "Watch Recordings" screen and the MythWeb + interface, recordings can be assigned into "recording groups". + + + [1m12.3.3. ``Storage Groups''[0m + + This allows you to select any special "Storage Groups" you may have + created to determine where recordings from this rule should be stored + on your disks. The "Default" storage group is always available. + [1m12.3.4. Playback Group[0m + + This selects a set of pre-configured playback parameters which can be + created and edited in Setup->TV Settings->Playback Groups. When the + recording is played, the values from this playback group will be used. + This allows you to choose a default time stretch value, skip and jump + amounts appropriate for this type of television program. + + + [1m12.3.5. Auto-Expire[0m + + MythTV will "autoexpire" old recordings to make room for new + recordings when disk space gets filled up. This option can be set to + "Don't allow auto expire" to prevent these recordings from being + automatically deleted when disk space fills up. + + + The default setting is for all scheduled recordings to be eligible for + auto-expiration; this can be changed in the Settings->TV + Settings->General page by manipulating the "Auto Expire Default" + checkbox. + + + The default auto-expire policy is "Oldest Show First"; the oldest + recordings are deleted first. The "Lowest Priority First" method + chooses to expire the lowest-priority recordings first. + + + [1m12.3.6. Episode Limit[0m + + An episode limit can also be configured to limit the maximum number of + episodes recorded of a single series, to restrict that series' disk + usage. If this is set, you can further decide what to do when this + limit is reached; either stop recording that series, or to delete the + oldest episodes in favor of the new ones. + + + [1m12.4. Post Recording Processing[0m + + [1m12.4.1. Commercial Flagging[0m + + Select whether or not to automatically flag commercials for these + recordings. Commercial Flagging parameters can be set in Setup->TV + Settings->General. + + + [1m12.4.2. Transcoding[0m + + Select whether or not to automatically transcode recordings to save + disk space. Before using this, you must first enable auto-transcode in + the recording profile and configure the transcoding parameters; see + ``Recording'', above. + + + [1m12.4.3. User Jobs[0m + + User Jobs allow you to configure up to 4 custom commands to run on + recordings. They can be configured in mythtv-setup. The following + tokens have special meaning when used in the User Job commands: + + + +o %DIR% - the directory component of the recording's filename + + +o %FILE% - the filename component of the recording's filename + + + +o %TITLE% - the title of the recording (e.g., name of the series) + + +o %SUBTITLE% - the subtitle of the recording (e.g., name of the + episode) + + +o %DESCRIPTION% - description text for the recording (from guide + data) + + +o %HOSTNAME% - the backend making the recording + + +o %CATEGORY% - the category of the recording (from guide data) + + +o %RECGROUP% - the ``recording group'' + + +o %CHANID% - the MythTV channel ID making the recording + + +o %STARTTIME% - the recording start time (YYYYMMDDhhmmss) + + +o %ENDTIME% - the recording end time (YYYYMMDDhhmmss) + + +o %STARTTIMEISO% - the recording start time in ISO 8601 format (YYYY- + MM-DDTHH:MM:SS) + + +o %ENDTIMEISO% - the recording end time in ISO 8601 format + + +o %PROGSTART% - the recording's start time (from guide data; + YYYYMMDDhhmmss) + + +o %PROGEND% - the recording's end time (from guide data) + + +o %PROGSTARTISO%, %PROGENDISO% - the recording's start and end time + in ISO 8601 format. + + + [1m12.5. Advanced Recording Options[0m + + [1m12.5.1. Creating Power Search rules with Custom Record[0m + + MythTV's "Custom Record" feature gives you unlimited control for + creating specialized search recording rules to meet your needs. It + allows you to choose your criteria to search for matching shows based + on any of the information in the program listings, channel + information, time functions and more. This goes beyond the + capabilities of any other DVR system and it is unlikely that this + level of scheduling customization will ever be available in any + commercial DVR system. + + + [1m12.5.2. Getting Started[0m + + Go to Schedule Recordings->Custom Record. This page, helps you build a + database search one clause at a time. Each added clause further limits + which showings will be matched in the TV listings. You can test the + search at any time and when you are done, you can save your search as + a recording rule. + + To familiarize yourself with how you can create custom rules, create a + simple rule to record "Nova" only in primetime. + + The first item at the top of the page allows you to edit an existing + rule or create a new rule. Leave it on "<New rule>". Arrow down to the + third item which says "Match an exact title". Right and left arrows + would allow you to select any of several prefabricated pieces or full + examples but leave it on the default for now. Arrow down to "Add this + example clause" and press SELECT (Enter or Space on a keyboard). The + large text box should now show: + program.title = 'Nova' + + + + As you have probably guessed, this says that we want to search for all + programs with the title "Nova" regardless of the time, day, channel, + etc. + + If you do not receive a PBS station that carries "Nova" or would like + to use another title, edit the title by pressing the down arrow to + highlight the text box and right arrow over the the word "Nova". If + you are using a keyboard you can simply delete the four letters and + type a different title between the quotes. With a remote control, you + can do 'cell phone' style text entry with the number pad. The delete + key is the "X" in the grouping for "1", zero is grouped with "9" and + "0" acts as the "Caps Lock" key. You can press ENTER in the text box + to popup a virtual keyboard. + + Note: the text box honors many familiar Emacs control keys. It is also + possible to cut and paste text into the text box so you can edit with + a favorite editor or insert a rule sent in email or from other + sources. + + In any case, choose a title that is shown both in primetime and late + night or daytime. Next, click the "Test" button. You should see a list + of the upcoming episodes for "Nova" just as if you had clicked the + Upcoming button for "Nova" elsewhere in MythTV. + + Press ESC to go back to the Custom Record page. Move to the example + selector then press the right or left arrows until you find "Only in + primetime". Click "Add this example clause". You should now see: + + + program.title = 'Nova' + AND HOUR(program.starttime) >= 19 + AND HOUR(program.starttime) < 23 + + + + Click "Test". You should now see a shorter list with only the showings + that begin between 7PM and 11PM. To create a rule for this, press ESC + to go back to the custom page and move to "Rule Name:" then type + "Nova" or anything else you would like. This is only a label and will + not affect the search results. Once a name has been entered, the + "Record" button will light up. Click this to enter the recording + options page. If you named it "Nova" the title will say "Nova (Power + Search)". Set whatever options you would like then click "Save these + settings". You now have a special rule to record "Nova" but only when + it is shown in primetime. + + You can make further modifications to this rule by returning to the + Custom Record page then press the right or left arrow keys on "Edit + Rule:" until you find "Nova". You can experiment and test but the + saved rule will not be updated until you click "Record" then "Save + these settings". + + To remove this, or any other rule, you can go to the "Recording + Priorities" page, arrow down to the title, press Enter and change the + the recording type to "Do not record this program" then "Save these + settings". + + + + [1m12.5.3. How it Works[0m + + MythTV stores TV program information in a database and uses the + Structured Query Language (SQL) to access the data. Information about + each TV program is stored in the 'program' table and information about + each TV station you receive is stored in 'channel'. These two tables + are used in the scheduler queries and their columns are available to + be used in your rules. The rules you create are stored in 'record'. + + Normal rules in MythTV simply match the title in the rule with the + titles in the 'program' table. MythTV also has search rules for + "Titles", "Keywords" and "People". These store the key phrase in the + description column of the rule and includes them in specialized SQL + replacements for the normal title check. There is also a type called + "Power Search" which takes the raw SQL in the description as the + replacement for title matching. + + Custom Record is a tool to help you build valid SQL for Power Search + rules. You do not need to be a SQL expert to use Custom Record + because the examples are known to work correctly and are usually self- + explanatory so you can choose the pieces you need then modify them. + Many powerful solutions to unique problems are possible by combining + the examples. With some creativity and some knowledge of SQL, the + possibilities are limitless. + + + [1m12.5.4. Common Tricks and Tips[0m + + The example clauses marked "complete example" are actual rules that + have been used to address specific problems. You may find that some of + these are useful for you as-is or with slight modifications. These + show off how powerful custom rules can be but there are also several + simple idioms that you may find useful for many of the shows you would + like to record. + + Wait for a known title -- If there is a movie that you anticipate will + be televised in the coming months but is not yet in the listings, you + can select "Match an exact title", edit the movie title, click + "Record" then choose "Record one showing of this title". The rule will + wait weeks, months or years until this title shows up in your listings + then it will record one showing. These rules have no impact on the + scheduler throughout the day and only take a tiny fraction of a second + when the master backend starts or when the listings are updated. + + Silence series out of season -- "Celebrity Poker Showdown", for + example, will have new episodes for a while then long periods where + reruns are shown dozens of times per week. By checking the previously + shown flag you can create a rule that will only match new episodes. + Therefore, your schedule won't be polluted with dozens of entries + marked as "Repeat" or "Previously Recorded". + + + program.title = "Celebrity Poker Showdown" + AND program.previouslyshown = 0 + + + + This allows you to keep rules for your favorite shows that are dormant + while out of season but will spring back to life when new episodes + appear. + + Choose showings on certain days -- Several cable stations will show + their highest rated shows a dozen on more times per week. However, the + scheduler only needs two or three choices to do a good job of making a + flexible choice. + program.title LIKE "Celebrity Fit Club%" + AND DAYNAME(program.starttime) = "Sunday" + + + + This says to choose any showing of an episode that hasn't been + recorded when it appears on Sunday. This prevents all the other show- + ings during the week from being listed in the schedule. + + Notice the word "LIKE" and the "%" at the end. This does wildcard + matching so that this would match even if the title ended with "2". + "III" or ":Revenge of the Snapple Lady". This can be useful where the + title may change from one season to the next like "Survivor: %", "Big + Brother%" or "The Amazing Race%". + + + [1m12.5.5. Working with SQL[0m + + As you experiment, it is possible that you may misplace a quote or + mistype a word. If there is a mistake when you press "Test" or + "Record" you will see an error message returned from the database. + This will usually give you a good idea about what needs to be fixed. + However, for more subtle MySQL syntax errors, you can find more + information in the documentation at http://dev.mysql.com/doc/mysql/en/ + <http://dev.mysql.com/doc/mysql/en/>. This contains a lot of + information that can be useful for Power Search rules such as the + "Date and Time Functions". There are many other good resources for SQL + on the Web. + + While the example clauses demonstrate how to use many of the data + columns, you can get a more complete list of all the columns that are + available by using a MySQL client program: + + + $ mysql -u mythtv -pmythtv mythconverg + mysql> describe program; + mysql> describe channel; + + + + This will show the names of all of the columns along with their type + and default value. Most are easy to understand but a few need some + explanation in order to use them effectively with Power Search. + + +o "program.category_type" holds one of these exact four strings: + "movie", "series", "sports" or "tvshow". + + +o "program.airdate" is a string representing the year of release for + movies and may have no meaning for other types of shows. + + +o "program.stars" is a floating point number from 0.0 to 1.0. On a + four star scale, 1.0 would be four stars, 0.75 would be three stars + and so on. + + +o "program.originalairdate" if provided is the date when a show was, + or will be, first televised. This may be useful for finding + episodes before or after a certain date such as finding just the + original series of "Battlestar Galactica". + + +o "program.previouslyshown" is a column created by MythTV to try to + determine if a showing is more than 14 days after its original air + date or if the show was marked as a repeat and did not have a date + for the first airing. If this is "0" it usually means that this is + a brand new show or a rebroadcast within the first two weeks. + +o "program.generic" is a column created by MythTV to try mark + showings for a series where the specific episode information is not + included. When these generic showings appear, it is impossible for + the system to determine if they are repeats of the same episode(s) + or if they are all different episodes. + + +o "program.first" is a column created by MythTV to mark the first + showing in the current listings for each episode, movie or special. + Choosing to match only the "first" showing can be useful for sports + that are brodcast live then repeated. + + +o "program.last" is a column created by MythTV to mark the last + showing in the current listings for each episode, movie or special. + If a showing is marked both "first" and "last" then it is the only + showing of that program in the current TV listings. + + +o "program.programid" is the Tribune Media Service database record + identifier for each program description. In general, these start + with a two letter prefix, MV, EP, SP or SH that correspond to the + "program.category_type". For most, the last four digits are "0000" + except EP where the last four digits are the episode number in the + series. Note that these are generated by TMS and not the show's + producers but they are usually in the same order as the original + air dates for the episodes. + + +o "program.videoprop" also "audioprop" and "subtitletypes". These + columns contain bit flags for a variety of attributes that may be + associated with a program. These are filled with information + offered by the TV listings provider. However, your listings source + will not have information for all of the available flags. + Therefore, some of these may not be useful for your search rules. + This information is organized in "sets" and the MySQL function + FIND_IN_SET() can be used to test for any of these flags. For + example: + + + FIND_IN_SET('SURROUND', program.audioprop) > 0 + + + + would be true for the programs where the surround sound bit is + present. To see all of the available attribute names: + + + $ mysql -u mythtv -pmythtv mythconverg + mysql> SHOW COLUMNS FROM program LIKE '%prop'\G + mysql> SHOW COLUMNS FROM program LIKE 'subtitletypes'\G + + + + Finally, if you are doing something very experimental and a column is + not giving you the results you had anticipated, you can always check + the MythTV source code to see exactly how a column is used. The open + source for MythTV is available from http://www.mythtv.org/ + <http://www.mythtv.org/> . + + + [1m12.6. Scheduling with more than one Input[0m + + + MythTV is designed to allow recording television programs from one or + more service providers, or video source, on one or more video input + from each provider. Some inputs may not be allowed to record at the + same time as each other while others may record simultaneously. + A television station may be broadcast on more than one channel from + one provider or may be available on channels from two or more + providers. If a TV station is available from more than one source, the + video quality or type of broadcast may differ. Therefore, MythTV + allows you to control how you would like the scheduler to select the + best channel and input for a show which is available on more than one + input or more than one channel. + + + [1m12.6.1. Mutually Exclusive Inputs[0m + + A single TV capture card may have video connections to more than one + of its inputs and each input may be from a different service. The + card may only be allowed to record from one of these inputs at one + time because there is only one encoder on the card that actually + captures the content. + + + + These are mutually exclusive meaning that only one input or the other + may record at a given time but not both. + + Usually, inputs on different cards can record at the same time but two + or more inputs on the same card cannot. However, there are cases where + inputs on different cards should not be allowed to record at the same + time, for example, a firewire card and s-video analog card connected + to the same set top cable box. + + + + | + | coax +--------------+ firewire ------------------+ + | .-=|Cable Provider|=------------=| Card 1 input 1 | HDTV + | | |HD/Cable STB |=--. +-----|||||||||||| + | | +--------------+ | s-video ------------------+ + | | `---------=| input 2 | Digital + |wall | coax | Card 2 | + |=---=^=------------------------------=| input 3 | Cable + | +-----|||||||||||| + + + + Input 1 and input 2 receive content from the same set top box and the + channels can not be tuned independently. Therefore only one of these + two inputs should be used at any given time. The solution is to create + an "Input Group" with [1mmythtv-setup [22min "Input connections". Including + these two inputs in the same Input Group will tell the scheduler that + these are mutually exclusive and may not record at the same time. + Inputs 2 and 3 are automatically mutually exclusive because they are + on the same card so there is no need to create an Input Group for + these inputs. + + Cards such as the Hauppauge PVR-500 are able to record as two cards + simultaneously because it has two MPEG-2 encoders and each encoder + appears as a separate device. DVB cards may be allowed to capture + content from more than one channel at a time if the channels are in + the same MUX. + + + + [1m12.6.2. Stations, Channels and Video Sources[0m + + Although we may be accustomed to thinking of a broadcast station and + its channel number as being synonymous, stations and channels are very + different things. A "station" is in a building with wires and + employees. A "channel" is a carrier frequency or digital ID that + carries a broadcast stream. The same TV station may be broadcast over + different frequencies in different cities or by different providers in + the same city. The same frequency will carry different stations in + different cities. In the digital realm of DVB and ATSC (HDTV), it is + even possible for a single frequency to carry multiple program streams + but each of these streams of content are actually different channels + that the receiving devices can 'tune' to independently. + + + +o Station: building + + +o Channel: frequency + + In MythTV, a "video source" is a set of channels from a provider, or + over the air, that can be received by an input. The set defines the + channels and the broadcasters primarily associated with each of those + channels. If you have more than one device or cable from the same + provider connected to more than one card and input, you only need to + create one video source in mythtv-setup then associate that one source + with each of these connected inputs. This will let your MythTV system + know that the same channels and their TV listings are available to be + recorded from any of these inputs. + + For example. A MythTV system may have two capture cards. Both have a + cable connected to the coaxial connectors. These cables carry the + local cable TV service. In mythtv-setup, the user should create one + "Video source" called "Cable", for example. Under "Input connections", + "Cable" should be associated with each of the two tuner inputs. The + scheduler will then know that any program on one of the channels from + the "Cable" source could be recorded by either card from the card's + tuner input. + + You need to create a different video source for each provider or + service that has a different set of channels. Each input with a + connection to that service should be associated with the video source + for that service so the system will know which set of channels are + available for each of your active inputs. + + Let's say that this user also has one digital cable set top box. The + digital cable service carries channels that are not available over + basic cable. The user would create another source called "Digital". + This set top box is connected to the second card by S-Video so under + "Input connections", "Digital" is associated with the S-Video input of + card 2. The system would then know that programs on channels from the + Digital source can only be recorded from this input. Further, the + scheduler understands that it can only record one show at a time from + card 2 so it can assign Cable or Digital shows to the card but not + both at the same time. + + Some TV stations may be broadcast over a channel from the Cable source + and also broadcast over a channel from the Digital source. Note that + two channels carrying the same primary station may not have the same + TV listings due to carrying the primary station part time, including + local programming exclusive to one of the channels, the channels may + be in different timezones, etc. Listings information must be + associated with each channel even if two or more channels report that + they carry the same station. + + + + [1m12.6.3. Order of Inputs[0m + + By default the scheduler chooses the first (lowest numbered) input + which has a showing of the scheduled program as it fills the schedule. + If a lower priority show is on at the same time as a higher priority + show that has been assigned to input 1, then input 2 will be used next + and so on. Therefore, configure your best card and input first and + next best card and input second. There may be differences in the type + or brand of capture card, signal quality from the cable, system + resources such as disk space, CPU, etc. By configuring your best input + first, more recordings, and your highest priority recordings, will use + that input. + + A common situation is that a newer and better card is added last. For + example, you may initially setup your system with two analog cable + cards and then add a HDTV card. If NBC is on a cable channel and "The + Apprentice" is shown in HDTV on an NBC HD channel, the scheduler would + still prefer analog inputs 1 and 2 over the new HD input 3. + + So, if you'd like the scheduler to prefer a new source, the simplest + thing is to run [1mmythtv-setup [22mand "Delete all capture cards" then enter + your cards and inputs in your preferred order. This will not remove + your sources and channels - you want to keep those and only renumber + your cards and inputs. In this example, once the changes have been + made and the Master Backend is restarted, the scheduler would then + choose "The Apprentice" in HD on the new input 1 and only use the + analog inputs (now numbered 2 and 3) when the HDTV input was occupied + with another show. + + + [1m12.6.4. Matching Callsigns[0m + + If a recording rule is a type that can record from any channel, "The + Apprentice" would match for any channel that shows episodes which may + include CNBC or BRAVO. However, for Single, Timeslot, Weekslot or + Channel rules, "The Apprentice" would only match showings on the + selected station as identified by the "callsign". For example, KVBC is + an NBC affiliate on channel 3. Channel 733 is KVBCDT which is HDTV + over cable from the same station. If a Single record rule was set for + "The Apprentice" on KVBC channel 3, it could not record this showing + from KVBCDT on 733. If 733 was chosen when the rule was saved, channel + 3 could not be used to record. + + However, the "Channel Editor" in mythtv-setup can be used to change + the Callsign for channel 733 to "KVBC". MythTV would then understand + that both of these channels are from the same broadcast station. + Assuming the HDTV input was input number "1", "The Apprentice" would + record on 733. If, however, this HDTV input already had a higher + priority show assigned to it in that time slot, "The Apprentice" would + be assigned to KVBC channel 3 on input 2. + + Having two channels with the same callsign may affect how program + information is shown in mythfrontend. If two sources have the same + callsign and channel number, the program guide and program lists will + only show one instance of the channel number and callsign. If the same + callsign is on two different channel numbers, both will be shown and + if two sources have different callsigns with the same channel number, + both of those will be shown. + + Continuing with the example above, the Electronic Program Guide would + include rows for both "3 KVBC" and "733 KVBC". If channel 3 KVBC was + also included in the Digital cable source, the EPG would still include + just one line for "3 KVBC" even though there are two different + channels, Cable and Digital, with this identification. Regardless of + how these are displayed and which "KVBC" channel you select to add a + rule to record "The Apprentice", the scheduler will pick the best + channel, source and input to record "The Apprentice" on "KVBC". + + + [1m12.6.5. Using Priorities to Prefer an Input[0m + + The fundamental concept to keep in mind is that the MythTV scheduler + will choose the lowest numbered input available when showings have the + same priority. If there are factors that cause two showings of the + same show to have different priorities then the higher priority + showing will be considered before the showings with lower priority. + + + [1m12.6.6. Input Priority[0m + + "Input Connections" in mythtv-setup includes a box to set "Input + priority" which defaults to "0". If a value is set, that amount will + be added to the "total priority" for showings on that input. This can + be used to influence using favored cards or not using less favored + cards unless necessary. + + Let's say the "The Apprentice" is on at 8:00pm with a priority of 3. + "Who Cares" is -2 and an episode is shown at 8:00pm then repeated at + 11:00pm. The scheduler would assign "The Apprentice" to card 1 and + "Who Cares" to card 2 at 8:00pm. If the input priority for the input + on card 2 was changed to -1, "Who Cares" would have a total priority + of -2 for showings on card 1 and -3 for showings on card 2. The + scheduler would assign "The Apprentice" to card 1 at 8:00pm and "Who + Cares" to card 1 at 11:00pm when the better card is available. If + there was another higher priority show at 11pm, the next best choice + for "Who Cares" would be card 2 at 8pm with the priority -3. + + Card 1 and 2 have input priority "0": + + + + Time Title Priority Card Status + 8:00 The Apprentice +3 1 Will Record + 8:00 Who Cares -2 2 Will Record + 11:00 Who Cares -2 1 Earlier Showing + + + + Card 2 with input priority "-1": + + + + Time Title Priority Card Status + 8:00 The Apprentice +3 1 Will Record + 8:00 Who Cares -3 2 Later Showing + 11:00 Who Cares -2 1 Will Record + + + + Card 2 at "-1" but higher priority shows at both 8 P.M. and 11 P.M.: + + + + Time Title Priority Card Status + 8:00 The Apprentice +3 1 Will Record + 8:00 Who Cares -3 2 Will Record + 11:00 The Daily Show +1 1 Will Record + 11:00 Who Cares -3 2 Earlier Showing + + + + Note the two different effects, each of which may be what you desire + depending on circumstance. If input priorities are equal, shows will + record at the earliest time if any input is available. If input + priorities differ, shows may be postponed to a later time in order to + record on the best input. + + + [1m12.6.7. Channel Priority[0m + + Priority can be added for individual channels (remember, frequencies + from a video source, not stations). This can be used to tell the + system that you generally prefer the content of the station on a + channel over the formats of other stations. You may want to raise the + priority for ESPN, SciFi, Comedy Central or lower the priority for + CSPAN, CourtTV, etc. If the same station is on two different channels, + you can use channel priority to have the same effect for these + channels as input priority would have for whole inputs. + + For example, say CNN is on analog channel 20 and there is an HD CNN on + 750. You may not want to tie up the HD input for news originating in + standard definition. Under TV Settings->Recording Priorities->Channel + Priorities you could set channel 750 to -1. The scheduler would then + prefer to record CNN shows on any analog channel 20 before considering + using 750 only when there are no analog inputs available. + + + [1m12.6.8. Preferred Input[0m + + For an even finer grain of control, there is a per rule option to + specify which input should be preferred for showings that match the + rule. By default, this adds +2 to the priority for showings on the + specified input. + + For illustration, let's say there will be a Space Shuttle launch on + CNN that will be broadcast in high definition. Adding a rule to record + the launch with priority "0" should default to channel 20 on input 2. + Channel 750 would have this at -1 due to the channel priority set in + the previous example. If on the recording options page for this rule, + the "Scheduling Options" had the input set to prefer the HD input on + card 1, then the showing on channel 750 for this input would be + increased in value by +2 for a total of +1 and would be the best + choice for this launch coverage. While this one rule would prefer the + HD input with channel 750, all other rules that match shows on CNN + would still prefer channel 20. + + Note that this will not work properly if the preferred input priority + does not out weigh differences in input and channel priorities. The + value of the priority boost when this option is chosen defaults to +2 + but can be modified in TV Settings->Recording Priorities->Set + Recording Priorities. + + + [1m12.6.9. HDTV Priority[0m + + In the preceeding fictious example, the Space Shuttle launch is + broadcast in high definition and a preferred input is selected to give + preference to the HD input. However, TV listings from zap2it.com + through the DataDirect service may allow this to work without having + to use this per rule option. + + In Settings->Recording Priorities->Set Recording Priorities there is + an option for "HDTV Recording Priority". This value will be added + automatically if the listings for the show have the "hdtv" flag set. + DataDirect will set this flag for shows known to be broadcast in HDTV + on HD channels. However, the flag is not set for standard definition + channels. This is another example of the listings being different for + the same station on a different channel. If the HDTV priority is set + to "+2", the shuttle launch would automatically have a total priority + of +1 so that channel 750 would be preferred over channel 20 for this + HDTV broadcast. + + Channel "750 CNN" at priority "-1" and HDTV broadcast priority at + "+2": + + + + [1m12.6.10. Custom Priority[0m + + + + New for MythTV 0.21 + + While Input, Channel, and HDTV Priority can be used for indicating a + preference for certain programs and inputs, there may be circumstances + that cannot be resolved easily with these standard features. MythTV + version 0.21 includes a feature for "power priority". The Custom + Priority editor in mythfrontend's "TV Settings" screen is similar to + Custom Record, however, Custom Priority allows you to create + specialized power priority factors to influence scheduling decisions. + + For example, the 'program.closecaptioned' flag can be used in a + similar way as the 'program.hdtv' flag. + + + + Priority Rule Name: Closed Captioned priority + Priority Value: 2 + program.closecaptioned > 0 + + + + This will raise the priority of shows marked with "CC" over those that + are not by applying the "Priority Value" whenever the SQL fragment + evaluates to true. If the expression evaluates to false for a showing, + the "Priority Value" is not applied. + + + + Priority Rule Name: Priority when shown once + Priority Value: 1 + program.first > 0 AND program.last > 0 + + + + The "first" and "last" flags for an episode will only be set for the + same showing when there is only one showing of that episode in the + current TV listings. This rule would raise the priority in these cases + so that these shows would have an advantage to record in their only + available time slot. + + + + Priority Rule Name: Input 1 signal quality + Priority Value: -1 + cardinput.cardinputid = 1 AND + channel.channum IN (3, 5, 39, 66) + + + + A common issue with two or more analog capture cards is that one of + the cards may have more interference on some channels than the same + channels on other cards. This example gives a disadvantage to the + channels in this list but only for the first input. Therefore, a show + on channel 39 would choose input 2 or 3 if possible but for channels + not in this list, input 1 is still the first choice. + + The Custom Priority editor includes many example fragments and + complete examples that can be used or you can create your own to suit + your needs. + + + [1m13. MythPlugins.[0m + + MythTV has a rich set of plugins available. Once you have downloaded + the tarball, untar it and run the [1mconfigure [22mscript: + + + + $ tar -xjf mythplugins-0.21.tar.bz2 + $ cd mythplugins-0.21 + $ ./configure --help + + Usage: configure [options] + Options: [defaults in brackets after descriptions] + NB: all --enable-* options can be reversed with --disable-* + + Generic options: + --help print this message + --enable-all Enable all options + --enable-opengl enable OpenGL (Music and Gallery) [default=no] + + MythBrowser related options: + --enable-mythbrowser build the mythbrowser plugin [default=yes] + + MythDVD related options: + --enable-mythdvd build the mythdvd plugin [default=yes] + --enable-transcode enable DVD ripping and transcoding [default=no] + --enable-vcd enable VCD playing [default=no] + + MythGallery related options: + --enable-mythgallery build the mythgallery plugin [default=yes] + --enable-exif enable reading of EXIF headers [default=no] + + MythGame related options: + --enable-mythgame build the mythgame plugin [default=yes] + + MythMusic related options: + --enable-mythmusic build the mythmusic plugin [default=yes] + --enable-fftw enable fftw visualizers [default=no] + --enable-sdl use SDL for the synaesthesia output [default=no] + --enable-aac enable AAC/MP4 audio file decompression [default=no] + + MythNews related options: + --enable-mythnews build the mythnews plugin [default=yes] + + MythPhone related options: + --enable-mythphone build the mythphone plugin [default=yes] + --enable-festival enable festival TTS Engine [default=no] + + MythVideo related options: + --enable-mythvideo build the mythvideo plugin [default=yes] + + MythWeather related options: + --enable-mythweather build the mythweather plugin [default=yes] + + + + The sections detailing configuration of the plugins assume that you + are already in the ~/mythplugins-0.21/ directory. + + Note that a single [1mconfigure [22mscript now does configuration for all + modules. By default, it will compile all modules. If you do not wish + to compile a module, either because it is of no use to you, or you do + not have the prerequisites, the simplest course of action is to go + through the various sections below, satisfying the prerequisites, and + then compile all modules at once. + + For example, you would only like to compile and install MythGallery + and MythMusic. For MythGallery, you would like to use the EXIF data + in the .JPG file to present additional information onscreen. For + MythMusic, you would like to enable support for the opengl and FFT + visualizations. The command line would look like: + + $ cd ~/mythplugins-0.21 + $ ./configure --disable-all --enable-opengl --enable-mythgallery --enable-exif --enable-mythmusic --enable-fft + $ qmake mythplugins.pro + $ make + $ su - + # make install + # exit + $ + + + + For simplicity, the examples below will disable compilation of all + other modules other than the one being discussed. + + + [1m14. MythWeb.[0m + + MythWeb allows you to use a web page to control various aspects of + your MythTV system. MythWeb is a separate application, but it's + dependent on MythTV being installed and operational. + + + [1m14.1. Installation and prerequisites[0m + + Mythweb is a part of the [1mmythplugins [22mpackage. See ``MythPlugins'' for + instructions on downloading the tarball. The next step depends on + whether your distribution has a web server and if you have PHP + support. + + + [1m14.1.1. Mandriva[0m + + Mandriva has [1mapache [22mand [1mPHP [22mpre-packaged, so installation is quite + simple. + + + + [1mNOTE[22m: Mandriva 9.1 users, perform the following: + + + # urpmi apache2 apache2-mod_php php-mysql + # chkconfig --level 345 httpd on + # /etc/rc.d/init.d/httpd restart + + + + [1m14.2. Completing the installation[0m + + + + $ cd ~/mythplugins-0.21/mythweb + $ su + # mkdir /var/www/html/mythweb + # cp -r . /var/www/html/mythweb + # exit + $ + + + + By default, MythWeb uses an Apache .htaccess file to restrict access + to the website and to configure some variables. + + To create the password file for Apache (if your system doesn't already + have one), you could do something like this: + + + # cd /var/www + # htpasswd -c htpasswd mythtv + New password: + Re-type new password: + Adding password for user mythtv + + + + See the man page for [1mhtpasswd [22mfor more examples. + + To access the web page, open a web browser and use [1mhttp://[name or ip[0m + [1maddress]/mythweb/[0m + + + + [1mNOTE[22m: Make sure that you have a trailing slash on the URL, + otherwise you will get a 404 Page not Found error. + + [1m14.3. Resetting the key binding table[0m + + MythWeb allows you to configure which keys are bound to which actions + within MythTV. If you'd like to reset this back to the default, + execute the following command: + + + $ echo "delete from keybindings ;" | mysql -u mythtv -pmythtv mythconverg + + + + [1m14.4. Resetting the theme.[0m + + If you find yourself wedged into a theme that isn't working, open your + web browser and go to site: + http://mythweb_name_or_ip_address/mythweb/settings.php?RESET_THEME=yes + + [1m15. MythGallery.[0m + + MythGallery is a photo and slideshow application. MythGallery is a + separate application, but it's dependent on MythTV being installed and + operational. + + [1m15.1. Installation and prerequisites[0m + + MythGallery is a part of the [1mmythplugins [22mpackage. See ``MythPlugins'' + for instructions on downloading the tarball. + + There are a number of transitions available, some requiring OpenGL + support. You will also need to install a TIFF library. Under + Mandriva, you would perform the following command: + + + # urpmi libtiff3-devel + + + Once you have satisfied the prerequisites for your distribution, + install the application: + + + $ cd ~/mythplugins-0.21 + $ ./configure --disable-all --enable-opengl --enable-mythgallery + $ qmake mythplugins.pro + $ make + # su + # make install + # exit + $ + + + + The configuration for MythGallery is accessed through the main Setup + option in mythfrontend. Make sure you set your pictures directory to + wherever you're storing your photos. + + The controls for MythGallery can be found in the README that comes + with the application. + + [1m15.2. Using MythGallery[0m + + When you first start MythGallery, you will see a thumbnail view of any + folders and pictures in the Gallery Directory you specified in setup. + If this is the first time you have accessed this directory, the + thumbnails will be generated on the fly. If the Gallery Dir is + writable, these thumbnails will be cached thus speeding up future + access. On the left is a greyed-out menu of options. + + Use the arrow keys to select a folder or picture to open/view with the + Select key, or use the Menu key to toggle access the menu on the left. + The menu options are as follows: + + +o Slideshow - Will cycle through all the pictures in the current + folder. The currently selected item must be a picture (not a + folder) for this to work. It does not currently traverse + subfolders. + + +o Rotate CW - Rotate the current image 90 degrees in the clockwise + direction. This change persists if the current directory is + writable. + + +o Rotate CCW - As above except the direction of rotation is + counter(anti) clockwise. + + +o Import - Import pictures into your Gallery Dir. This option is + described in the next section. + + +o Settings - Access the MythGallery settings screen. + + [1m15.3. Importing Pictures[0m + + The import path in the setup dialog is a colon separated list of + directories and/or executable files. When the import key is pressed, + a new directory (the destination directory) under the current + directory will be created and the import path will be searched. If + the item in the import path is a directory (the source directory), the + contents of that directory will be copied to the destination + directory. If you would like the source directory to be that of a + removable device, it might be a good idea to use autofs. See the + automount howto at www.linuxdoc.org <www.linuxdoc.org> for info on how + to get it working. + + If the item in the import path is an executable file, MythGallery will + attempt to execute it with the destination directory as its sole + argument. Be careful when using executable scripts that the script + runs unattended (doesn't need user intervention) and returns properly, + otherwise it could create the appearance of MythGallery hanging (e.g. + running [1msmbclient [22mand prompting for password). Also be sure that + scripts have executable permissions set. + + Here is an example script that a user may want to run on import: + + + #!/bin/csh + + if ($#argv == 0) then + echo "Usage: $0 dest_dir" + exit + endif + + cd $argv[1] + + # get stuff over the network + wget http://www.somesite.dom/dir/file1.jpg + wget http://www.somesite.dom/dir/file2.jpg + wget http://www.somesite.dom/dir/file3.jpg + + # stuff that requires manual module loading and/or fs mounting + modprobe camera_module + mount /dev/camera /mnt/camera + cp /mnt/camera/* $argv[1] + umount /mnt/camera + rmmod camera_module + + # perform some processing + foreach pname (`ls *.jpg`) + jpegtran -flip vertical $pname > $pname.new + mv $pname.new $pname + end + + + + [1m16. MythGame.[0m + + MythGame can used as a frontend to start any emulator that your host + OS runs. This is an example of how to set up xmame on Linux. + http://www.mameworld.net/ <http://www.mameworld.net/> is an excellent + resource for all things mame. + + Installation overview: + + 1. Setup directory structure + + 2. Download and install xmame + + 3. Download and place extra files (artwork/catver.ini/etc..) + + 4. Download and install MythGame plugin + + 5. Setup xmame in MythGame + + 6. Hints + + + + [1m16.1. Setup Directory Structure[0m + + To keep things organized, create the following directories for [1mxmame[0m + to use in /usr/local/share/xmame: hiscore, roms, and snaps. + + + + $ mkdir -p /usr/local/share/xmame/{highscore,roms,snaps} + + + + [1m16.2. Download and Install xmame[0m + + [1mNOTE[22m: There may be pre-packaged versions of [1mxmame [22mavailable for your + distribution. Check http://x.mame.net/download.html + <http://x.mame.net/download.html> for the latest version. + + Download the source to [1mxmame [22mfrom + http://x.mame.net/download/xmame-0.103.tar.bz2 + <http://x.mame.net/download/xmame-0.103.tar.bz2> + + + + $ wget http://x.mame.net/download/xmame-0.103.tar.bz2 + $ tar -xjf xmame-0.103.tar.bz2 + $ cd xmame-0.103 + + + + Edit the Makefile with your favorite editor. Adjust the options as + required for your system. + + + $ joe Makefile + + + + Then make and install xmame + + + $ make + $ su + (enter password) + # make install + # exit + + + + After [1mmame [22mhas been installed, we need to create some defaults. + + + $ mkdir ~/.xmame + $ cp docs/xmamerc.dist ~/.xmame/xmamerc + + + + Because some ROMS work better with different display toolkits, or + possibly even older versions of xmame, it's convenient to keep all of + your [1mxmame [22mbinaries and to rename them to include the version number. + MythGame allows you to match individual roms to preferred binaries. + $ su + (enter password) + # mv /usr/local/bin/xmame.x11 /usr/local/bin/xmame-0.103.x11 + # exit + + + + [1mNOTE[22m: Depending on how you compiled [1mxmame[22m, you may have [1mxmame.X11[22m, + [1mxmame.SDL [22mor [1mxmame.xgl [22mbased on what display toolkit you used. Also, + you may need to remove and recreate xmamerc after upgrading since some + of the default options may have changed. + + Edit ~/.xmame/xmamerc to include your paths. + + + ### Fileio Related ### + rompath /usr/local/share/xmame/roms + snapshot_directory /usr/local/share/xmame/snaps + cheat_file /usr/local/share/xmame/cheat.dat + hiscore_file /usr/local/share/xmame/hiscore.dat + hiscore_directory /usr/local/share/xmame/hiscore + history_file /usr/local/share/xmame/history.dat + mameinfo_file /usr/local/share/xmame/mameinfo.dat + + + + Confirm that [1mxmame [22mworks before running it inside MythTV. Place your + ROM in the /usr/local/share/xmame/roms directory you created earlier. + + [1mNOTE[22m: There are three public domain ROM sets available at + http://www.mame.net/downmisc.html <http://www.mame.net/downmisc.html> + + Launch [1mxmame [22mwith your game of choice. In this example, we are using + Gauntlet. + + + $ xmame gauntlet + + + + Some basic [1mmame [22mkeyboard commands: + + + 5 = Insert coin + 1 = Player 1 start + arrow keys = movement + left control = button 1 + left alt = button 2 + SPACE = button 3 + ESC = exit + TAB - menu + ~ to adjust Volume + < and > + + + + [1m16.3. Download extra files[0m + + The following files allow you to add extra functionality. Place them + into /usr/local/share/xmame + + - catver.ini is a catalog of categories and versions of popular mame + ROMs. + + Useful for keeping large libraries of ROMs organized. + + It may be downloaded from http://www.catver.com + <http://www.catver.com> or http://www.mameworld.net/catlist + <http://www.mameworld.net/catlist> + + - Screenshots aka "snaps" + + These may be downloaded from http://www.classicgaming.com/mame32qa/ + <http://www.classicgaming.com/mame32qa/> + + Screenshots are displayed when you are browsing your ROMS in [1mmythgame[22m. + Unzip and place them in /usr/local/share/xmame/snaps + + - history.dat + + Download from http://www.arcade-history.com/ <http://www.arcade- + history.com/> This file fills in a bit of background about each ROM. + + - hiscore.dat + + Download from http://www.mameworld.net/highscore/ + <http://www.mameworld.net/highscore/> + + - Cheats + + Download from http://cheat.retrogames.com/ + <http://cheat.retrogames.com/> + + + [1m16.4. Download and Install MythGame.[0m + + [1mMythGame [22mis part of the mythplugins package. See the instructions in + the ``Downloading and Compiling'' section to obtain mythplugins. + + Switch to the mythplugins directory: + + + $ cd ~/mythplugins-0.21 + + + + Compile and install mythgame: + + + $ ./configure --disable-all --enable-mythgame + $ qmake mythplugins.pro + $ make + $ su + (enter password) + # make install + # exit + + + + [1m16.5. Setup xmame in MythGame[0m + + Start [1mmythfrontend [22mand navigate to Utilities/Setup > Setup > Media + Settings > Game Settings > Game Players. Select (New Game Player). + + To set up a new player for xmame enter the following: + + + + Player Name: xmame-0.103.x11 (Name by which you want your emulator or game called) + Type: xmame (This is used for display purposes only and does not affect the function of your system) + Command: xmame-0.103.x11 -vidmod 1 -fullscreen (Path and name of binary + any optional parameters) + Rom Path: /usr/local/share/xmame/roms (This tells MythGame what directories to scan for roms to be used with this emulator) + ScreenShots: /usr/local/share/xmame/snaps (This tells MythGame what directories to scan for snapshots to be used with these roms) + Working Directory: (Directory to change to before launching game or emulator. Blank in our case ignores this setting) + File Extensions: (List of all file extension to be used for this emulator. Blank menas any file under the Rom Path) + [] Allow games to span multiple roms/disks (will treat game.1.rom game.2.rom game.3.rom as one game) + + + + [1m16.6. Hints:[0m + + + +o Rom name before options: %s can be used as a standin for rom names + on the command line. + + +o Multiple disk/rom games: %d1 %d2 etc can be used as standins for + multiple disc games on the command line. + + +o Associating a rom with an emulator: Browse to the desired rom and + press 'M' to enter the settings page for that rom. + + +o Assign a Game Favorite Status: Browse to the desired game and press + "/". + + + [1m17. MythMusic.[0m + + MythMusic has a number of prerequisites that must be satisfied before + it is operational. Depending on your distribution, some of these + prerequisites can be satisfied through the various package managers. + If your distribution doesn't offer pre-compiled versions of the + software below, then follow the generic instructions for manually + compiling and installing the software. + + The prerequisites for MythMusic are: + + +o MAD + + +o taglib + + +o libogg and libvorbis + + +o FLAC + + +o libcdaudio + + +o CDParanoia + + + [1m17.1. Manual installation of prerequisites[0m + + These instructions are for distributions which don't have pre-compiled + versions of the software necessary to run MythTV. + + Download MAD from http://www.underbit.com/products/mad + <http://www.underbit.com/products/mad> and install: + + + $ tar -xzf mad-0.15.1b.tar.gz + $ cd mad-0.15.1b + $ ./configure + $ make + $ su + # make install + # exit + + + + Download TagLib from http://developer.kde.org/~wheeler/taglib.html + <http://developer.kde.org/~wheeler/taglib.html> and install: + + + + $ tar -xzf taglib-1.4.tar.gz + $ cd taglib-1.4 + $ ./configure + $ make + $ su + # make install + # exit + + + + Download libogg and libvorbis from http://www.xiph.org/downloads + <http://www.xiph.org/downloads> and install in a similar manner to the + above packages. + + Download FLAC from http://flac.sourceforge.net + <http://flac.sourceforge.net> and install: + + + $ tar -xzf flac-1.1.2.tar.gz + $ cd flac-1.1.2 + $ ./configure + $ make + $ su + # make install + # exit + $ + + + + Download libcdaudio from http://libcdaudio.sourceforge.net + <http://sourceforge.net/project/showfiles.php?group_id=27134> and + install: + + + $ tar -xzf libcdaudio-0.99.12p2.tar.gz + $ cd libcdaudio-0.99.12p2 + $ ./configure + $ make + $ su + # make install + # exit + $ + + + + Download cdparanoia from http://www.xiph.org/paranoia/down.html + <http://www.xiph.org/paranoia/download/cdparanoia-III- + alpha9.8.src.tgz>. + + + $ tar -xzf cdparanoia-III-alpha9.8.src.tgz + $ cd cdparanoia-III-alpha9.8 + $ ./configure + $ make + $ su + # make install + # cd /usr/lib + # ln -sf libcdda_interface.so.0.9.8 libcdda_interface.so + # ln -sf libcdda_paranoia.so.0.9.8 libcdda_paranoia.so + # exit + $ + + + + [1m17.2. Mandriva[0m + + Mandriva has a number of the prerequisites available on the + installation CD. Some of the software you're going to need will have + to be obtained from the "contrib" or "cooker" development + repositories. Applications downloaded from "cooker" come from the + development branch, so there may be issues with some software. It + isn't recommended that you mix cooker and release-level software. + + + [1murpmi [22mis the simplest tool for installation of packages from the + command line. The difficult part is the configuration, but this has + been made easier at the following website: + http://addmedia.linuxfornewbies.org/ + <http://addmedia.linuxfornewbies.org/> The website will allow you to + choose a mirror site and then present the command-line configuration + text for that mirror. You will most likely need to add a "Contrib" + mirror to your setup. Once you have done that, you can proceed. If + [1murpmi [22mprompts you about other modules that need to be installed to + satisfy dependencies, say "Yes". + + + + # urpmi libmad0 libmad0-devel libflac4 libflac4-devel libcdaudio1 cdparanoia + # urpmi libcdda0 libcdda0-devel libvorbis0 libvorbis0-devel + # urpmi libcdaudio1-devel libid3tag0 libid3tag0-devel + + + + [1m17.2.1. Additional options with MythMusic[0m + + Additional visualizations have been added to MythMusic. If you wish + to use these, there are some prerequisites you must install prior to + compiling. + + + +o fftw + + +o OpenGL + + +o SDL + + fftw may be obtained from http://www.fftw.org/ <http://www.fftw.org/>. + In Mandriva it may be installed by typing: + + # urpmi libfftw2 libfftw2-devel + + + + OpenGL should be installed on practically all distributions. However, + you will need the devel module. In Mandriva it may be installed by + typing: + + + # urpmi libMesaGLU1-devel + + + + SDL may be obtained from http://www.libsdl.org + <http://www.libsdl.org>. In Mandriva it may be installed by typing: + + + # urpmi libSDL1.2 libSDL1.2-devel + + + + [1m17.3. Red Hat Linux 9[0m + + Red Hat provides packages for several of the prerequisites, making + installation very simple. Of the prerequisites, Red Hat provides + packages for Vorbis, cdparanoia, SDL, and OpenGL (which you probably + already have installed). To install these all at once, simply type + (all on the same line): + + + $ up2date --solvedeps libvorbis libvorbis-devel vorbis-tools cdparanoia-devel cdparanoia-libs cdparanoia SDL-devel SDL + + + + If you get the following message: "None of the packages you requested + were found, or they are already updated" it probably means you already + have all of those packages installed. + + You must install the remaining packages, (MAD, FLAC, libcdaudio and + optionally fftw) manually following the installation directions above. + When installing fftw do not use the rpm package offered on the website + because it will cause an error, so use the source package instead. + + + + [1mNOTE[22m: you can use the instructions given at the ``automated + installation section'' to install all of MythMusic in one + step. + + [1m17.4. Compiling MythMusic[0m + + Once all the prerequisites have been installed, you can proceed with + compiling MythMusic. + + + + $ cd ~/mythplugins-0.21 + $ ./configure --disable-all --enable-mythmusic --enable-fftw --enable-sdl --enable-aac + $ qmake mythplugins.pro + $ make + $ su + # make install + # exit + + + + [1m17.5. Configuring MythMusic[0m + + Configuration of MythMusic occurs in two places. The main + mythfrontend Setup is for global MythMusic configuration. Go to the + Setup/MythMusic/General Setup screen and adjust it for your particular + configuration. + + The second configuration screen is within the MythMusic program and + will allow you rescan your music library, etc. + + Here's some explanation about the Ignore_ID3 and The + NonID3FileNameFormat: + + If Ignore_ID3 is set to TRUE, MythMusic will try to determine the + Genre, Artist, Album, Track Number, and Title from the filename of the + mp3 file. The NonID3FileNameFormat variable should be set to the + directory/file format where the mp3 files are stored. For instance, I + store mine in the above shown Genre/Artist/Album/Track format. + MythMusic will then use this information to fill in the proper fields + when it populates the musicmetadata table rather than searching for an + ID3 tag in the mp3 file. + + The files can be laid out in any format, such as: + + Genre/Artist/Album/Title Artist/Genre/Album/Title Artist/Album/Title + (with Genre left as Unknown) + + The track number is optional but can be specified with the title by + using the TRACK_TITLE keyword instead of TITLE. If TRACK_TITLE is + used, then the filename can have a space, hyphen, or underscore + separating the track number from the track title. Keywords are case + insensitive, so if you specify GENRE it's the same as Genre in the + format field. + + The Ignore_ID3 option does not disable the code that determines the + track length, just the portion that tries to read ID3 info. + + + [1m17.6. Using MythMusic[0m + + MythMusic is fairly simple to use. It is recommended that you insert + the CD before selecting "Import CD". You should also ensure that your + system doesn't try to automount the CD and begin playing it + automatically. + + Here's some information on playlist management: + + Q: How do I create a new playlist? A: Using the MythMusic "Select + Music" menu option, setup the playlist as you normally would by adding + songs or other playlists as needed. When you are ready to save the + new playlist, highlight "Active Play Queue" at the bottom of the + selection tree and hit the "i" key. This will pop up a menu allowing + you to name and save the new playlist. You can also hit Enter to + bring up the popup on the Active Play Queue. This does not work on the + playlists above, as Enter is obviously bound to checking/unchecking + the boxes. Any number (i.e. keypad on remote) will also bring up the + menu in both cases. + + Q: How do I enter the playlist name in the text field without a + keyboard? A: Use the keypad number keys (bound to your remote) to + select letters quasi-cell phone style. Keys 2-9 work pretty much like + any cell phone text entry. 1 cycles through a few special characters, + delete, and space. 0 is like a CAPS LOCK. Hard to describe, fairly + easy to use. You will soon be able to specify the cycle timing in a + Setup screen. You can type fairly quickly through a combination of + jumping around the number keys AND hitting a non-number key (right + arrow is particularly good for this) to force the current character. + + Q: How do I edit a playlist? A: Highlight the playlist in the + selection tree and hit the "i" key then select "Move to Active Play + Queue" in the popup. You can now modify the "Active Play Queue" like + normal, adding songs and playlists by selecting them from the song + tree. When you are done, highlight the "Active Play Queue" in the + selection tree and hit the "i" key then select "Save Back to Playlist + Tree". And whatever you were editing as your Active Queue before you + moved an existing playlist "on top" of Active reappears. Think of + Active has having a push on, pop off capability, but with a depth of + only 1. + + Q: How do I delete an item from a playlist? A: Highlight the item in + the selection tree and hit the "d" key. + + Q: How do I rearrange the songs in my playlist? A: Highlight a song + and hit the "space" bar, the song will now have pair of red arrows in + front of it. Use the up and down arrow keys to move it around in the + playlist. When you have it where you want it, hit the "space" bar + again. + + Q: How do I delete a playlist? A: Highlight the playlist in the + selection tree and hit the "i" key then select "Delete this Playlist" + from the popup. + + + [1m17.7. Troubleshooting MythMusic[0m + + You may run into errors when running MythMusic. + + [1m17.7.1. When I run MythMusic and try and look up a CD, I get an error[0m + [1mmessage[0m + + The full text of the message will say: + + databasebox.o: Couldn't find your CD. It may not be in the freedb + database. More likely, however, is that you need to delete /.cddb + and /.cdserverrc and restart mythmusic. Have a nice day. + + If you get this message, you should go to the home directory of + whatever user MythMusic is running as and type: + + + rm .cdserverrc + rm -rf .cddb/ + + + + These files aren't automatically deleted because of a conscious design + decision by the author that programs that automatically delete things + are bad. + + The files are used to locally cache CD lookups. If you are re- + inserting CDs, your machine will not actually have to go out to the + Internet to determine what is on them. However, the URL used to + access the freedb database has recently changed, so the stale + information in the files from previous runs of MythMusic would cause + the error above. Once the files have been deleted the stale + information will be gone and your local database will be rebuilt as + you use CDs. + + + [1m18. MythWeather.[0m + + MythWeather is a part of the [1mmythplugins [22mpackage. See ``MythPlugins'' + for instructions on downloading the tarball. + + + + $ cd ~/mythplugins-0.21 + $ ./configure --disable-all --enable-mythweather + $ qmake mythplugins.pro + $ make + $ su + # make install + # exit + + + + MythWeather uses MSNBC.com as its source for weather data and + weather.com for its radar image. + + These are the keyboard commands for MythWeather: + + + Left Key Goes back one page, and extends the time spent + on the page you are on. + Right Key Goes forward one page, see above. + Space Pause, wait on the current page until space is hit + again. + Numeric Keys You can check other weather by keying in other ZIP codes. + Enter Key Switch between Celsius and Fahrenheit. Can also + be used a way to force a data update. + "m" Key Resets the location to the database default, then updates the data. + "i" Enter / Save settings + ESC Exit the settings screen without saving / Exit the program + + + + MythWeather also has an "Aggressiveness" setting. This affects how + long MythWeather waits for data from the msnbc.com website before + timing out. If you are on a slow connection, or have a slow DNS, or + MythWeather just doesn't seem to be working and you've already tried + everything else, then try increasing the aggressiveness level + parameter. This parameter is inverse; a higher number actually means + that MythWeather will be less aggressive, and will therefore wait + longer before timing out. + + MythWeather will print debugging information on the terminal. If you + wish to see additional debugging information while MythWeather is + running, run mythweather from the command line with as mythweather + --debug + + You may also force mythweather to re-run the configuration by starting + it on the command line as mythweather --configure. These two options + are mutually exclusive. + [1m19. MythVideo.[0m + + MythVideo is a part of the [1mmythplugins [22mpackage. See ``MythPlugins'' + for instructions on downloading the tarball. + + MythVideo will allow you to use an external program to watch media + files that are not directly supported by MythTV. + + + + $ cd ~/mythplugins-0.21 + $ ./configure --disable-all --enable-mythvideo + $ qmake mythplugins.pro + $ make + $ su + # make install + # exit + + + + See MythVideo's README file for additional information. + + + [1m20. MythDVD.[0m + + MythDVD is a part of the [1mmythplugins [22mpackage. See ``MythPlugins'' for + instructions on downloading the tarball. MythDVD is an application + which rips DVDs and makes them available for use with MythVideo. You + may also transcode the DVD content from MPEG-2 to other formats which + should greatly reduce the amount of space the DVD material takes up on + your hard drive. + + MythDVD has a number of prerequisites to enable transcoding + functionality. If you only wish to play DVDs rather than convert them + to something like MPEG-4 or xvid you may skip the prerequisite + installation step. + + + [1m20.1. Manual Compilation of Prerequisites[0m + + + [1m20.2. Pre-compiled binaries[0m + + Mandriva users may install the prerequisites this way: + + + # urpmi libdvdread3 libdvdread3-devel a52dec liba52dec-devel + # urpmi mplayer ogle xine + + + + Assuming that you've added a PLF mirror, you may also load the rest of + the prerequisites using the following command: + + + # urpmi xvid xvid-devel fame libfame0.9-devel transcode libdvdcss + + + + In the example below, we have enabled support for transcoding and for + VCD playing. You may remove these options if you don't need them. + + + $ cd ~/mythplugins-0.20 + $ ./configure --disable-all --enable-mythdvd --enable-transcode --enable-vcd + $ qmake mythplugins.pro + $ make + $ su + # make install + + + + [1m20.3. Running the Myth Transcoding Daemon[0m + + Transcoding ("ripping") a DVD requires you to run the Myth Transcoding + Daemon (mtd). To ensure that mtd is configured correctly, you should + first test it at the command line. + + + $ mtd -n + + + + The last line of text should show something like: + + + mtd is listening on port 2342 + + + + This indicates that mtd is ready for use. Once you've successfully + tested mtd in the foreground, type [1mCTRL-C [22mto stop mtd. You may then + start it as a background (daemon) process. + + + $ mtd -d + + + + Running mtd as a daemon will allow you to automatically start it + during the boot process. For example, you may add mtd -d to your + rc.local file, or you can adjust the script/steps outlined in the + section called ``Automatically starting mythbackend at system boot + time'' to start mtd instead of mythbackend. + + + [1m21. MythNews.[0m + + MythNews is a part of the [1mmythplugins [22mpackage. See ``MythPlugins'' + for instructions on downloading the tarball. MythNews is a RSS + reader. + + + $ cd ~/mythplugins-0.21 + $ ./configure --disable-all --enable-mythnews + $ qmake mythplugins.pro + $ make + $ su + # make install + + + + [1m22. Troubleshooting.[0m + + [1m22.1. Compiling[0m + + [1m22.1.1. Compile errors[0m + + Some compile errors are worse than others. If you get an error that + doesn't abort the compilation, and says something like: + + + cc1plus: warning: changing search order for system directory + "/usr/local/include" + cc1plus: warning: as it has already been specified as a non-system + directory + + + + then it shouldn't be a problem. + + If you get an error like /usr/bin/ld: cannot find -lXext, the compiler + is telling you that you don't have XFree86-devel installed, or that + your distribution hasn't set it up correctly. This needs to be fixed + before MythTV will compile. + + + [1m22.1.2. make: *** No rule to make target[0m + [1m/usr/lib/qt3/mkspecs/default/qmake.conf', needed by Makefile'. Stop.[0m + + This error happens when there's a missing link in the + /usr/lib/qt3/mkspecs directory. There are two ways to fix this error: + + 1. Create the link manually: + + + $ su + # cd /usr/lib/qt3/mkspecs + # ln -sf linux-g++ default + + + + and then restart the compile, + + or + + 2. Run [1mqmake mythtv.pro [22min the mythtv directory. Rerunning [1mqmake[0m + will create a new Makefile for you, however this still doesn't fix the + root cause of the issue, which is that your distribution didn't create + the symlink for you when the qt3 package was installed. The first + choice is the better solution. + + + [1m22.1.3. make: *** No rule to make target[0m + [1m/mkspecs/default/qmake.conf', needed by Makefile'. Stop.[0m + + You didn't set your QTDIR. Re-read the section on ``Setting up + paths''. + + + [1m22.1.4. Internal Segmentation Fault.[0m + + This is most likely to be caused by an overheating processor rather + than an actual programming fault within gcc. + + + [1m22.2. Debugging[0m + + [1m22.2.1. MythTV segfaults[0m + + [1m22.2.2. MythTV isn't doing anything[0m + + [1m22.2.3. Debugging with GDB[0m + + Without details, the developers will not be able to determine if you + have discovered a genuine code-bug, or if the problem is with your + system. In order to determine what's going on, you must recompile + MythTV with debugging support and run MythTV within [1mgdb[22m, the GNU + debugger. Note that, on OS X, some data is provided without going + through these steps. See + /Library/Logs/CrashReporter/MythFrontend.crash.log + + Re-run the [1mconfigure [22mscript and add --compile-type=debug to any + previous configuration options you may have used. Check the + config.log file if you have forgotten. + + Now, you need to clear out the old versions of the software to ensure + that you're running with the debugging code, then compile and install. + + + $ make distclean + $ ./configure --compile-type=debug + $ make + $ su + # make install + # exit + + + + At this point, you now have debug-enabled software ready. To make + sure that you don't forget to type a command required for debugging, + it's best to setup a gdbcommands file. This will be read by [1mgdb [22mwhen + it's started. Put the following into gdbcommands in your home + directory: + + + + handle SIGPIPE nostop noprint + handle SIG33 nostop noprint + set logging on + set pagination off + set args -l myth.log -v record,channel,siparser + run + thread apply all bt full + set logging off + + + + Let's assume that the problem you're having is in [1mmythbackend[22m. + + + + $ gdb mythbackend -x gdbcommands + GNU gdb 6.3-debian + Copyright 2004 Free Software Foundation, Inc. + GDB is free software, covered by the GNU General Public License, and you are + welcome to change it and/or distribute copies of it under certain conditions. + Type "show copying" to see the conditions. + There is absolutely no warranty for GDB. Type "show warranty" for details. + This GDB was configured as "i386-linux".Using host libthread_db library "/lib/tls/libthread_db.so.1". + [Thread debugging using libthread_db enabled] + + + + [1mgdb [22mwill automatically read the commands that you've placed in the + gdbcommands file and begin running the program you specified on the + command line. + + If the program appears to be locked up, press CTRL-C to create the + backtrace file. + + All of the output from gdb.txt should be posted to the mythtv-dev + mailing list, along with the steps you followed to get the program to + crash. + + [1mNOTE[22m: If you're trimming the gdb.txt file to remove extraneous + information from the beginning of the file, make sure you include at + least 10 lines [4mprior[24m to the point where the backtrace actually begins. + This ensures that there is some context to the backtrace, and so that + it's possible to see what exactly caused the segfault. + + [1mgdb [22mhas a number of options, read the man page for more information. + + Using the gdbcommands file in conjunction with a [1mwhile [22mloop will + ensure that [1mgdb [22mcreates a trace file and then restarts: + + + + $ while true; do date >> gdb.txt; gdb mythbackend -x gdbcommands; done; + + + + [1mNOTE[22m: To exit this loop you will need to kill the while loop. + + If you're trying to troubleshoot and you can't get back to the [1mgdb[0m + window for some reason, it may be easier to use two systems or to + start mythfrontend from the text console. + + If you're going to troubleshoot from a remote system, connect to the + machine that you're going to test using [1mssh [22mor [1mtelnet[22m. Next, type $ + export DISPLAY=localhost:0.0. This will allow the graphics to be + displayed on the X console (usually ALT-F6 or ALT-F7) and still give + you output and control of [1mmythfrontend[22m, either from the [1mssh [22msession, + or by switching back to the text console by pressing CTRL-ALT-F1. You + can now continue troubleshooting using [1mgdb [22mas detailed in the + instructions. + + + [1m22.2.4. MythTV is crashing your system[0m + + When run as a non-privileged user, MythTV [4mcan[24m [4mnot[24m crash your system. + If your system is crashing when you run MythTV, then you have some + issue with the drivers for your capture card or other hardware, or the + CPU fan has fallen off/broken and your system is overheating when + asked to perform a CPU intensive task like encoding video. + + If you are running as root, which is [1mstrongly discouraged[22m, it is + possible that your system may crash due to the real-time thread using + all available CPU. You will not be able to interrupt the process, so + for all intents and purposes your computer will have crashed. + + + [1m22.3. Installing[0m + + [1m22.3.1. When trying to run mythtv-setup, you get an error like this:[0m + [1m"mythtv-setup: error while loading shared libraries:"[0m + + You didn't add /usr/local/lib to /etc/ld.so.conf. See the section on + modifying ``/etc/ld.so.conf''. + + + [1m22.4. Using[0m + + [1m22.4.1. No programs are displayed in "Watch Recordings"[0m + + This situation occurs most often with a system that acts as a frontend + and a slave backend. MythTV supports system-global and user-specific + configuration files, with user-configuration files taking precedence. + 99% of the configuration for MythTV is in the MySQL database, but + MythTV still needs to know where the MySQL server is running. This + information is in the mysql.txt file. By default, it will be + installed to /usr/local/share/mythtv, but a copy placed into ~/.mythtv + will over-ride the global configuration. + + You must ensure that there aren't multiple, conflicting versions of + this file on your system! + + + $ locate mysql.txt + /usr/local/share/mythtv/mysql.txt + /home/mythtv/.mythtv/mysql.txt + $ + + + + As you can see, in this example there are two mysql.txt files. If + they are not identical, then there may be unintended consequences. + + You may also see this error if you completely fill the /var partition. + The most likely [4mmythtv-related[24m reason for this is an overly large + mythbackend or mythfrontend log file in /var/log. If you have logging + enabled for the backend, and myth runs for weeks at a time, this may + creep up and surprise you. Note that many system processes also write + to /var and the system may not boot if it is unable to write to /var + due to a full partition. + + + [1m22.4.2. MySQL not connecting correctly[0m + + Your [1mMySQL [22minstallation may have networking turned off. Check that + /etc/mysql/my.cnf [4mdoes[24m [4mnot[24m contain skip-networking. If it does, + remove it. Also verify that bind-address is set to your IP address + instead of 127.0.0.1. If you change either of these items, restart + [1mMySQL[22m. + + + [1m22.4.3. MySQL database is corrupt[0m + + If you have reason to believe that your MySQL database is corrupt, + execute the following commands to attempt to repair it. + + [1mNOTE[22m: Ensure that there are no programs accessing the database while + you attempt to repair it. Make sure that all backend and frontend + programs have exited. + + mysqlcheck -r -umythtv -p<password> mythconverg + + + [1m22.4.4. Using a MPEG-2 encoder card and the video appears "jittery"[0m + + [1m22.4.5. Using a MPEG-2 encoder card and the video is jumping up and[0m + [1mdown[0m + + This is a different problem than the one discussed in the previous + section. Currently, the ivtv driver or firmware appear to have some + issues if the vertical capture resolution is not the full screen + height. If you are having a jitter problem then ensure that you are + capturing either 480 lines (for NTSC) or 576 lines (for PAL). The + default capture profiles may need to be edited for your setup. Go to + Settings->TV Settings->Recording Profiles and adjust the [1mDefault [22mand + [1mLive TV [22moptions to 480 or 576 from their defaults. + + + [1m22.4.6. Screen goes blank but returns when mouse is moved or keyboard[0m + [1mis used[0m + + This is due to DPMS, the Display Power Management System, which is + used to save power by turning off your monitor when the system decides + that it's not being used or due to a screensaver that has defaulted to + a blank screen. MythTV now has DPMS support built-in, and should + intelligently handle the screen. Continue reading if you wish to + override DPMS and force it off. + + Since it's likely that watching TV will not generate keyboard or mouse + events for a time, you need to turn off DPMS and the screensaver. + There are a few ways to do this. You may also need to check your BIOS + for power saving modes and disable screen blanking there as well. + + Edit your /etc/X11/XF86Config-4 or /etc/X11/xorg.conf file, and look + for: + + + Section "ServerFlags" + #DontZap # disable <Ctrl><Alt><BS> (server abort) + #DontZoom # disable <Ctrl><Alt><KP_+>/<KP_-> (resolution switching) + AllowMouseOpenFail # allows the server to start up even if the mouse doesn't work + + Option "blank time" "0" + Option "standby time" "0" + Option "suspend time" "0" + Option "off time" "0" + Option "NoPM" "1" + EndSection + + + + Also, look for: + + + + Section "Device" + Identifier "device1" + VendorName "nVidia Corporation" + BoardName "NVIDIA GeForce 256 (generic)" + Driver "nv" + Option "DPMS" + EndSection + + + + In this case, you would need to either delete the Option "DPMS" line, + or change it to # Option "DPMS" to comment it out. The next time you + start XFree this change will take effect. + + Finally, check: + + + Section "Monitor" + Identifier "monitor1" + VendorName "Plug'n Play" + HorizSync 30-85 + VertRefresh 50-160 + + # Sony Vaio C1(X,XS,VE,VN)? + # 1024x480 @ 85.6 Hz, 48 kHz hsync + ModeLine "1024x480" 65.00 1024 1032 1176 1344 480 488 494 563 -hsync -vsync + + # TV fullscreen mode or DVD fullscreen output. + # 768x576 @ 79 Hz, 50 kHz hsync + ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630 + + # 768x576 @ 100 Hz, 61.6 kHz hsync + ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616 + EndSection + + + + Ensure that there isn't an Option "DPMS" in the Monitor configuration. + + You can also turn off DPMS from the Command Line, but this will not + survive a reboot. + + + $ xset -dpms + + + + Using xset +dpms will turn it back on. + + Another technique to try, which will turn off the screensaver: + + + $ xset s off + + + + You may also combine the command to turn off DPMS and the screensaver: + + + $ xset -dpms s off + + + Finally, depending on your distribution, you may be able to turn it + off from within the control panel. + + [1m22.5. Miscellaneous[0m + + [1m22.5.1. mythfilldatabase failing[0m + + If mythfilldatabase suddenly appears to be failing, there are at least + two things to check. + + First, if you are in North America, ensure that your DataDirect + subscription is still valid, otherwise, check to see what version of + XMLTV you're running and that it's the latest version. + + + + [1mNOTE[22m: It is highly recommended that you run the latest + version of XMLTV available. Your listings provider may have made + changes which negatively impact XMLTV. + + + [1m22.5.2. Fast CPU, choppy or jittery video[0m + + First, you should check that your kernel has been enabled for DMA: + + + [mythtv@pvr mythtv]$ dmesg |grep DMA + ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA + ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio + hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63, UDMA(33) + hdb: 80043264 sectors (40982 MB) w/2048KiB Cache, CHS=4982/255/63, UDMA(33) + + + + From the listing above, you can see that hda, hdb and hdc are set for + DMA, and hdd is set for pio. If your kernel is not reporting DMA + being enabled, you may need to recompile your kernel. Check your + motherboard's chipset (look in the "ATA/IDE/MFM/RLL support" section + in "make menuconfig") for more information. + + Next, check that the hard drive has DMA enabled. Use the [1mhdparm[0m + program to check and enable DMA. + + + # hdparm -d /dev/hd? + + + + will tell you the DMA status for your hard drives. If you run [1mhdparm[0m + with the -d1 parameter, it will turn DMA on. + + + You may also setup your PC to do this at boot time, either by adding + the command to your /etc/rc.local file, or by adding files to + /etc/sysconfig. + + On Mandriva and other distributions, if you install [1mhdparm [22mfrom an RPM + you will most likely get a /etc/sysconfig/harddisks file installed. + This file will be parsed by the /etc/rc.sysinit script. If you use + the default harddisks file, your changes will affect all IDE devices + (including CD ROMs). If you wish to use different parameters for + various devices, rename and/or copy the file to harddiskhda, + harddiskhdb, etc. Edit the file to your liking and on the next reboot + your setting will be preserved. + + + [1m22.5.3. Frontend appears to be slow at jumping / seeking.[0m + + [1m22.5.4. On-screen Display shows incorrect program length.[0m + + This may occur when MythTV doesn't have an accurate seek table. Run + [1mmythcommflag --rebuild[0m + + + [1m22.5.5. Troubleshooting audio[0m + + + + [1mNOTE[22m: the following instructions do not apply to PVR-250/350 + encoders; the MPEG-2 file will have the audio embedded in the stream + so it is not accessible using /dev/dsp. + + Audio appears to be one of the bigger issues that users run into on + the mailing list. If the audio isn't configured correctly, then + MythTV will often appear to hang, when in fact it is trying to + manipulate the audio subsystem and failing. You may or may not + receive error messages indicating that the source of the error is the + audio subsystem. + + You can not use [1mxawtv [22mto determine if your audio is working correctly, + since [1mxawtv [22mis simply using the analog sound patched through line-in + to line-out. It doesn't need to digitize the sound unless you are + using the recording function. + + A better test to verify that sound will work for MythTV (and recording + with [1mxawtv [22mfor that matter) is to startup [1mxawtv[22m, mute the line-in then + run aplay /dev/dsp. You should hear the recorded audio slightly + delayed behind the real-time video. You should see messages about + "underrun". These can be ignored but they do confirm that the driver + is loaded and there is an active device. Once this test succeeds, + MythTV should work correctly because it writes to and read from + /dev/dsp in the same way that [1maplay [22mdoes. + + To record audio along with video the audio signal must be digitized by + a DSP so that the audio data can be stored in a file. On playback, the + audio data is written to /dev/dsp and converted back to an analog + signal. This analog signal should then be sent to your speakers. Here + is what is needed in [1malsamixer[22m. If you are using an ALSA version after + 1.0.6, use [1malsamixer -V all[22m: + + CAPTUR source - the analog source to be sent to the DSP. This should + be set to the input source from the tuner card to the sound card. In + most cases this is Line but this could also be Aux, CD, Mic, etc., + depending on how you connect the input cable. This source should be + muted to prevent patching through the analog sound. The volume of this + source will not affect the record level. + + Capture mixer - this sets the level for the analog to digital + recording. While a volume of 100% is recommended for testing, + distortion may occur. Lowering this level to 75% to 85% may result in + better audio quality. "Capture" should be marked as the CAPTUR + destination. + + PCM mixer - this sets the level for the digital to analog playback. + While a volume of 100% is recommended for testing, distortion may + occur. Lowering this level to 75% to 85% may result in better audio + quality. + + Master mixer - sets the level for the analog signal sent to line-out + or the speakers. + + You may also want to ensure that /dev/dsp , or whatever device file is + being used, hasn't already been grabbed by another process, like [1mesd[0m + or [1martsd[22m. If the device file isn't available, then MythTV won't work. + You may wish to run [1mconfigure [22mand enable support for these. + + If you wish to see what application is grabbing a resource, you can + use the fuser command: + + + # fuser -v /dev/dsp + + + + To disable aRts in KDE, go to KDE->Control Center->Sound->Sound System + and uncheck the "Start aRts soundserver on KDE startup" box. Run # + killall artsd from the command line to stop the artsd program. + + If you're using multiple sound cards and multiple tuners, use + alsamixer -c 1 to work with the second sound card. The first card is + #0, the second card is #1, etc. + + + [1m22.5.6. Mythbackend reports that your card is not reporting full[0m + [1mduplex capabilities[0m + + [1m22.5.7. The mythbackend program told me to look at this section[0m + + mythbackend does a check to see if your sound device is capable of + full duplex operation. If it's not, it's most likely that you're + going to run into issues when you try to record and play sound at the + same time. If your backend is a separate machine than your frontend, + then there's no problem, since you're only going to be doing one thing + at a time with the card. Likewise, if you're running the frontend and + backend on the same machine, but you're using btaudio or a hardware + encoder card such as the Hauppauge PVR-250, DVB cards or HDTV capture + cards as your recording source and you're only using the playback + function of your sound card, then you also shouldn't have an issue, + since the sound card isn't being asked to perform two functions at + once. + + If you can't get your sound card to go full-duplex and need it to, + then check your distribution for updated sound drivers. If your sound + card is not capable of full-duplex operation, either because the + drivers don't support it, or it has been designed that way, then + you're pretty much out of luck and will either need to purchase a new + sound card, or will need to get btaudio ``operational''. + + + [1m22.5.8. My remote doesn't work / works sometimes and not others /[0m + [1m"ghost" keypresses[0m + + This can be due to a number of factors. The simplest case is the + "ghost" keypresses. For me, it was due to compact fluorescent lights + in the same room as the IR receiver, which the receiver was picking up + as keypresses. Once the lights were switched to incandescent bulbs, + the ghost went away. + + You may have an issue with [1mlirc [22mmisinterpreting IR commands from a + different remote. I also have an issue where the TiVo "Peanut" remote + will eventually cause [1mlircd [22mto stop responding; even though [1mlircd [22mis + configured for the Pinnacle Systems remote, the TiVo remote IR + patterns are being seen by the IR receiver. + + If your remote has been properly configured, and [1mirw [22mand [1mirxevent [22mare + working correctly, then it's highly likely that your window manager is + not giving focus correctly to the various Myth programs as they run. + The following window managers are known to work correctly: + + + +o fvwm + + +o blackbox (using "Sloppy Focus" and "Focus New Windows") + + [1mNOTE[22m: You do not need to use [1mirxevent [22mif you are using MythTV's + native LIRC support, so the window manager focus issue does not apply + in that case. + + + [1m22.5.9. Where's "canada-cable"?[0m + + [1m22.5.10. Channels are off by one[0m + + There is no such thing as "Canada Cable"; Canada uses the same + frequencies as the United States. "Canada Cable" was a hack that some + people used when they would discover that their channels were off-by- + one, i.e. when tuning to channel 42, they might get channel 41 or 43. + This is actually due to the tuner on the video capture device being + mis-detected. You must manually specify the tuner type in your + /etc/modules.conf. See the video4linux mailing list + (https://listman.redhat.com/mailman/listinfo/video4linux-list + <https://listman.redhat.com/mailman/listinfo/video4linux-list>) for + more information. + + + [1m22.5.11. Mythweb is showing a db_open error when I connect to it[0m + + Find your php.ini file. Make sure you've got a line in it like this: + + extension=mysql.so + + Restart [1mapache [22mfor it to take effect. + + + [1m22.5.12. Mouse pointer disappears when placed over the MythTV windows[0m + + This is the intended behavior. The MythTV interface is meant for use + with a remote control or a keyboard. + + + [1m22.5.13. What does "strange error flushing buffer" mean on the con-[0m + [1msole?[0m + + Nothing, really. It's just lame (the mp3 encoder) complaining for + some obscure reason. This seems to be fixed in more recent versions + of the libmp3lame library. + + + [1m22.5.14. Can't change the channel when watching Live TV.[0m + + Something's wrong with your program database. Did mythfilldatabase + run with no major errors? Or, MythTV may not have permissions to the + appropriate video4linux devices. See the section titled ``Device + Permissions'' for an example. + + + [1m22.5.15. Screen goes black when you try to play something[0m + + MythTV prints error and status messages to the shell that was used to + start the application. If nothing seems to be happening when you try + to view a program, try switching back to the shell and look for error + messages there, or, if you're running from a startup script, check the + log file. + + + [1m22.5.16. Poor performance with NVidia cards and XvMC[0m + + XvMC is a NVidia driver feature which is supposed to help with + decoding video. Users have reported that rather than speeding up + their video it appears to be doing the opposite. You may want to + check that your color depth is set for 24bpp. + + + [1m22.5.17. Computer is loading a media player application when you[0m + [1minsert a CD or DVD[0m + + You need to disable any sort of auto-running media player in your + environment, otherwise MythDVD or MythMusic will not be able to work + properly. + + In KDE, you may want to perform the following: + + + $ rm ~/.kde/Autostart/Autorun.desktop + + + + [1m23. Miscellaneous.[0m + + [1m23.1. I'd like to watch the files without using MythTV / I'd like to[0m + [1mconvert the files to some other format[0m + + First, check if the [1mmytharchive [22mplugin does what you want. If not, + then read on: + + MythTV comes with a utility called [1mmythtranscode [22mwhich can decode nuv + files into raw format for use with other applications. This command- + line utility was not designed to be used by the end-user, but instead + to be called by other applications or scripts. Programs like + [1mnuvexport [22m(http://forevermore.net/myth/ + <http://forevermore.net/myth/>) are better suited for the end user. + However, since [1mmythtranscode [22mcan be a useful tool, directions on using + it follow. + + [1mmythtranscode [22mcreates raw streams, which means that they do not + contain any container information such as resolution, frame-rate, or + audio sampling rate. In order to process the output, you must supply + this information to the processing utility. [1mmythtranscode [22mprovides + the relevant information on STDOUT. + + There are two modes in which [1mmythtranscode [22mcan create raw streams. + The first has no synchronization and assumes that the processing + utility will read audio and video at a constant rate. This method is + useful when a single application will be processing the raw output, + such as [1mmencoder [22mor [1mffmpeg[22m. The second method assumes that two + separate applications will be processing the audio and video streams + independently, and there is no rate control between them which means + that the two programs don't coordinate their efforts to maintain + synchronization. + + + [1m23.1.1. mythtranscode example[0m + + First, start [1mmythtranscode[22m. You will need to determine the channel + and the start time manually. + + + $ mythtranscode --chanid 1036 --starttime 2003-10-20T15:30:00 --profile \ + autodetect --fifodir . & + + + + When [1mmythtranscode [22mbegins executing, it will create two FIFOs + ("audout" and "vidout") in the directory specified (in this case ".", + meaning the current directory) and will print out information about + the video stream. + + The next step is to start the processing application. The following + assumes that the stream is NTSC 640x480 with 32Kbps audio. + + To use [1mmencoder [22myou would enter a command like: + + + mencoder -audiofile audout -audio-demuxer 20 -rawaudio rate=32000 \ + -rawvideo on:w=640:h=480:fps=29.97 -ovc lavc -oac mp3lame -o out.avi \ + vidout + + + + [1mNOTE[22m: You must use mencoder 1.0PRE1 or later. [1mmencoder[0m + version 0.9x [4mWILL[24m [4mNOT[24m [4mWORK![24m Using ffmepg: + + + ffmpeg -f u16le -ar 32000 -ac 2 -i audout -f rawvideo -s 640x480 -r 29.97 \ + -i vidout -vcodec mpeg4 -b 2000 -acodec mp3 -ab 128 out.avi + + + + Or to play directly using mplayer (again 1.0PRE1 or later is needed): + + + mplayer -audiofile audout -audio-demuxer 20 -rawaudio rate=32000 \ + -rawvideo on:w=640:h=480:fps=29.97 vidout + + + + If you wanted to write the raw data to separate audio and video files + for later processing, the following would work (note the use of + --fifosync for rate-control): + + + $ mythtranscode --chanid 1036 --starttime 2003-10-20T15:30:00 \ + --profile autodetect --fifodir . --fifosync & + $ cat audout > audio.raw & + $ cat vidout > video.yuv + + + + [1m23.2. Using a different window manager[0m + + MythTV is not dependent on any particular window manager. If you wish + to run a lightweight window manager, the contrib/configfiles/ + directory has an example of a .twmrc and .fvwmrc file you may use. + + + [1m23.3. What capture resolution should I use? How does video work?[0m + + While MythTV allows you to set various GUI and capture resolutions, + not all combinations make sense. + + First, analog video signals have a defined vertical resolution. In + NTSC, the video standard specifies that there are 525 vertical scan + lines. Once the "extra" lines are removed (they're used to + synchronize the video signal, and encode closed captioning data), you + have 480 horizontal lines stacked vertically. + + In PAL, there are 625 "raw" lines of resolution, with a net of 576 + horizontal lines stacked vertically. + + Horizontally, the maximum value allowed for a Bt8X8 chip is 720. + However, due to limitations in the chip and other limitations of + broadcast television, there may not be a noticeable improvement in + image quality beyond 400 or 500 pixels. + + With this in mind, there are certain commonly accepted values for + resolution. While other values may be accepted for the vertical + resolution, they will cause scan lines to be repeated or dropped. + + From "best" to "worst", in NTSC: + + +o 720x480 "DVD" resolution. ReplayTV High and medium resolution + + +o 704x480 DVD standalone recorder standard resolution + + +o 640x480 4:3 + + +o 544x480 TiVo Best resolution + + +o 480x480 SuperVCD (SVCD) Video CD resolution, TiVo High resolution + + +o 352x480 ReplayTV "Standard" quality, TiVo Basic and Medium + resolution, DVD "LP" resolution + + +o 320x480 + + +o 544x240 + + +o 480x240 + + +o 352x240 Video CD (VCD) resolution + + +o 320x240 + + As you can see, the lower quality values are half of the better ones. + 720x240 is possible, but isn't a good tradeoff relative to the number + of vertical lines lost. In a PAL country, the you would use values + like 720x576 or x288. + + The higher resolutions will be more CPU intensive if you're using + software encoding (PVR-250/350 will have minimal host CPU impact even + if you're using 720x480). If the CPU is overtaxed, frames will be + dropped causing uneven motion. You will likely see the best results at + resolutions which average at least 10% CPU idle time. You can use + system tools such as top or sar to check the CPU % idle while + recording. If the CPU average usage is consistently exceeding 90%, + frames will need to be dropped during peak times when more than 100% + of the available CPU would be needed to process all of the frames. + + If you'd like to read more on this, go to the vcdhelp website at + http://www.vcdhelp.com/forum/userguides/94382.php + <http://www.vcdhelp.com/forum/userguides/94382.php>. + + + [1m23.4. MythTV GUI and X Display Sizes[0m + + MythTV is designed to be run as dedicated full screen TV application + but can also be run as a desktop application on a computer monitor. + Here are a few consideration for configuring sizes to best suit you + needs. + + + [1m23.4.1. X Dimensions[0m + + For output to a Television, common resolutions are 640x480, 800x600, + and some rare devices support 1024x768. Generally, higher resolutions + are better. However, you may find that you prefer the picture quality + at one of the lower resolutions. Everything in MythTV is scalable and + should 'fit' regardless of the resolution you choose. + + Edit your X configuration file, usually /etc/X11/XF86Config-4 for + XFree, or /etc/X11/xorg.conf for Xorg, so that the resolution you want + to use is listed first in the lists under "Screen". If this resolution + is higher than the resolutions supported by your output device, you + will see a 'panning' effect where moving the mouse to the edge will + scroll around a desktop area which is larger than the display size. If + this happens, edit your X configuration file to match the display size + then restart X. + + + [1m23.4.2. MythTV Dimensions[0m + + From "mythfrontend" go to Setup->Appearance. The default for the + height and width is "0" - this will cause MythTV to automatically size + itself to full screen. + + If the MythTV GUI width and height are not 0, mythfrontend uses these + GUI dimensions and is anchored to the upper left corner of the X + Desktop. If the GUI X and/or Y are not 0, the upper left corner is + positioned at the specified coordinates. If the "Run the frontend in a + window" box is checked, the window will have a frame and can then be + dragged to any position on the desktop. + + + + [1mNOTE[22m: When the GUI is full screen, you may see windows rapidly + flipping on top of each other. If this happens you will need to set + your window manager to 'Click to Focus' for windows to stack properly. + The fonts for the GUI and OSD will scale to whatever sizes you use. + Most font sizes can be changed in setup selections or in the .xml + files under /usr/local/share/mythtv/ . Make sure to use fonts large + enough to be read on a TV screen from a distance. + + The full screen TV size is based on the X display size. For Xinerama, + you can specify a screen in Setup->General. The TV picture will be + stretched to fit the entire GUI area regardless of the ``capture + resolutions'' used. However, during playback, the "W" key can to used + to correct differences between 16:9 and 4:3. + [1m23.4.3. Overscan Dimensions[0m + + Because picture edges can be ragged and screen edges aren't straight, + Television is designed to project an image larger than the physical + screen. This is called "overscan". Underscan is fitting the entire + image inside the screen. Underscan is useful for computer monitors so + that toolbars and scrollbars at the edges can be seen. + + For best results, match the X display area as close as possible to the + edges of the physical screen. This can only be adjusted by your tv-out + device or by the settings for the television set. Many sets have these + adjustments in a 'service mode'. If you cannot make these adjustments, + there will be black borders around the edges of the X desktop, MythTV + GUI and TV playback. + + MythTV has settings for "Overscan" in Setup->Playback. These can not, + and do not, cause the image to display beyond the edge of the X + display area. The purpose of these settings are to cut off rough edges + and to expand the image so that objects will appear to be the same + size as a normal overscanned TV picture. + + + [1m23.5. Saving or restoring the database[0m + + See the [1mmysqldump [22mmanpage for more information. + + + $ mysqldump -u mythtv -pmythtv mythconverg -c > mythtv_backup.sql + + + + To restore: (assuming that you've dropped the database) + + + $ mysql -u root + mysql>create database mythconverg; + mysql>exit + $ mysql -u mythtv -pmythtv mythconverg < mythtv_backup.sql + + + + You may need to alter the MySQL permissions if this database is being + shared with multiple systems. See the ``Modifying access to the MySQL + database for multiple systems'' section for more information. + + + [1m23.6. Deleting the MySQL database[0m + + + + [1mNOTE[22m: Performing this step will remove the entire database. You will + lose all of your settings and will need to re-run the mc.sql script + to setup the database structure before running the mythtv-setup + program. + + + $ mysql -u root + mysql> drop database mythconverg; + mysql> quit + + + [1m23.7. Moving your data to new hardware[0m + + This assumes that you will be moving your data to newer / bigger + hardware and don't want to lose your programs. + + The first step is to create a database backup as demonstrated in an + earlier section. + + Next, you will extract only the data that is relevant to the programs: + + + $ grep "INSERT INTO record " mythtv_backup.sql > restore.sql + $ grep "INSERT INTO recorded " mythtv_backup.sql >> restore.sql + $ grep "INSERT INTO oldrecorded " mythtv_backup.sql >> restore.sql + $ grep "INSERT INTO recordedprogram " mythtv_backup.sql >> restore.sql + $ grep "INSERT INTO recordedrating " mythtv_backup.sql >> restore.sql + $ grep "INSERT INTO recordedmarkup " mythtv_backup.sql >> restore.sql + $ grep "INSERT INTO recordedseek " mythtv_backup.sql >> restore.sql + + + + [1mNOTE[22m: Newer versions of [1mmysqldump [22mplace backticks around the table + names. Backticks are not the same as apostrophes! On a typical North + American keyboard, backticks are located to the left of the "1" key, + on the same key as the tilde. Also, because the [1mbash [22mshell may try to + interpret the backticks, make sure you use a \ before each one. + + If your restore.sql file is empty, you'll need to re-run the commands + like this: + + + $ grep "INSERT INTO \`record\` " mythtv_backup.sql > restore.sql + $ grep "INSERT INTO \`recorded\` " mythtv_backup.sql >> restore.sql + $ grep "INSERT INTO \`oldrecorded\` " mythtv_backup.sql >> restore.sql + $ grep "INSERT INTO \`recordedprogram\` " mythtv_backup.sql >> restore.sql + $ grep "INSERT INTO \`recordedrating\` " mythtv_backup.sql >> restore.sql + $ grep "INSERT INTO \`recordedmarkup\` " mythtv_backup.sql >> restore.sql + $ grep "INSERT INTO \`recordedseek\` " mythtv_backup.sql >> restore.sql + + + + Note the space after the table name and the ">>" to append to the file + for all but the first [1mgrep[22m. "recordedmarkup" and "recordedseek" are + huge and there may be hundreds of thousands of lines if you had lots + of hours of recordings. + + After you have moved the data files to the new hardware, configure + MythTV using the [1mmythtv-setup [22mprogram as you normally would with a + standard MythTV installation. + + At this point we will restore the information about your programs back + into the database: + + + $ mysql -u mythtv -pmythtv mythconverg < restore.sql + + + + After successful insertion of the data you may delete the restore.sql + file. + + + + [1m23.8. btaudio[0m + + btaudio allows you to obtain the audio data from your tuner card + directly over the PCI bus without using a sound card. This is useful + if you would like to use multiple tuner cards in a system without + adding a sound card for each one, or if your existing sound card is + not capable of full-duplex operation. + + In order to use btaudio, your tuner card will need certain hardware + installed on it, and that hardware must be wired correctly. The chip + that will allow you to use the btaudio module is the MSP34xx. + However, having a MSP34xx is no guarantee that you will be able to use + the btaudio module. + + As of 2003-03-31, this is the current list of cards and their status: + Works with btaudio: + + + +o Hauppauge WinTV-radio with dbx-TV stereo, model 401 + + +o Hauppauge WinTV-Theater, model 495, 498 (Europe) + + +o ATI TV Wonder + + The following cards do not work: + + +o Pinnacle Studio PCTV Pro - note: this has a MSP34xx, but it's not + wired correctly to the BT878 chip. + + +o ATI TV Wonder VE + + +o Leadtek Winfast 2000 XP (PAL, UK and NTSC) + + +o I/O Magic PC-PVR. No MSP34xx chip. + + The following cards have been reported to work, but have issues: + + +o Avermedia AVerTV Studio (no digital DSP output, "whiney noise" on + analog) + + Once btaudio loads, it should register additional /dev/dsp and + /dev/mixer devices. Typing $ dmesg will let you know what's going on. + + + [1m23.9. Removing unwanted channels[0m + + If [1mmythfilldatabase [22mgrabbed a channel which you do not want to include + in your TV listings, you can remove the entries from the grabber + configuration and the MySQL database. This often happens with premium + channels; for example, HBO or Showtime may be available on your cable + TV system, but is scrambled because you're not a subscriber to that + channel. Since you can never watch it, you want to get rid of it. + + If you are using the DataDirect service, login to your account at + http://labs.zap2it.com/ <http://labs.zap2it.com/> to modify your + lineup. Uncheck the boxes for any unwanted channels, and they will no + longer be included in your download. + + If you are using a grabber from XMLTV, comment out the channel from + the ~/.mythtv/<sourcename>.xmltv file by inserting the word "not " + (including the space) in front of the unwanted entry. This will + prevent [1mxmltv [22mfrom grabbing future listings. + + Next, delete the unwanted item from the channel table so that it will + not appear in the EPG or when changing channels. To delete the data + from the database we need to perform some steps. First, assuming that + HBO is channel 15, we need to find out the internal chanid used by + MySQL: + + + $ mysql -u root mythconverg + mysql> select chanid from channel where channum=15; + +--------+ + | chanid | + +--------+ + | 1015 | + +--------+ + 1 row in set (0.00 sec) + mysql> delete from channel where chanid = 1015; + + + + Old program data will be removed over the course of a week. However, + you may want to immediately delete any current program listings for + the channel that has been removed: + + + $ mysql -u root mythconverg + mysql> delete from program where chanid = 1015; + + + + [1m23.10. NFS[0m + + You may want to use a central server to store your files. + + On the host machine, (in this case, the hostname is "masterbackend") + you'll want to edit your /etc/exports file and use something like: + + + /var/video (rw) + + + + To export the /var/video directory with read / write privileges. + + On the "slave" machine, you'll want to edit the /etc/fstab file and + add something like: + + + masterbackend:/var/video /var/video nfs rsize=8192,wsize=8192,hard,intr,nfsvers=3,actimeo=0 + + + + Then run # mount -a to re-read the file to mount the file system. + + In this case, the source is a machine called "masterbackend" which is + exporting the directory "/var/video", which we're mounting locally at + "/var/video". The rsize and wsize options are used to increase the + performance of NFS; "hard,intr" is there because that's the + recommendation of the NFS-HOWTO, the nfsvers is required for filesizes + over 2GB and actimeo is used to turn off file attribute caching. + Attribute caching for a shared media point causes problems; you always + want to see the latest state of the directory and files. See + http://www.mythtv.org/wiki/index.php/Optimizing_Performance + <http://www.mythtv.org/wiki/index.php/Optimizing_Performance> for + additional information regarding performance optimization. + [1m23.11. Automatically starting mythfrontend at system boot time[0m + + Here's an example submitted to the mythtv-dev list by Pat Pflaum + mailto:pat@netburp.com <mailto:pat@netburp.com> using fvwm: + + + $ cat > .xinitrc + fvwm & + mythfrontend + ^D + $ cat > .fvwmrc + Style myth* NoTitle, NoHandles, Sticky, WindowListSkip, SloppyFocus, GrabFocus, BorderWidth 0 + ^D + $ + + + + The following also works with blackbox: + + + $ cat > .xinitrc + xset -dpms s off & + irxevent & + mythfrontend & + blackbox + + + + Make sure that your .blackboxrc file has: + + + session.screen0.focusNewWindows: True + session.screen0.focusModel: SloppyFocus + + + + in it. + + + [1m23.12. Automatically starting mythbackend at system boot time[0m + + [1m23.12.1. Red Hat And Mandriva[0m + + Here's a method for automatically starting mythbackend submitted by + Mike Thomson (mailto:linux@m-thomson.net <mailto:linux@m-thomson.net>) + and Stu Tomlinson (mailto:stu@nosnilmot.com + <mailto:stu@nosnilmot.com>). + + Copy the files from the MythTV contrib directory or from Mike's web + site (http://m-thomson.net/mythtv/ <http://m-thomson.net/mythtv/>) as + follows: + + etc.rc.d.init.mythbackend should be made executable and copied to + /etc/rc.d/init.d/: + + + $ cd contrib + $ su + # chmod a+x etc.rc.d.init.d.mythbackend + # cp etc.rc.d.init.d.mythbackend /etc/rc.d/init.d/mythbackend + + + + etc.sysconfig.mythbackend should be copied to /etc/sysconfig/: + + + $ cd contrib + $ su + # cp etc.sysconfig.mythbackend /etc/sysconfig/mythbackend + + + + Edit /etc/sysconfig/mythbackend if you want to change the defaults + (the userid that should start mythbackend, location of the logfile and + (if required) the name and location of the mythbackend binary). + + Use [1mchkconfig [22mto make sure the script is called when entering + runlevels 3, 4 or 5: + + + $ su + # chkconfig --level 345 mythbackend on + # exit + $ + + + + [1m23.12.1.1. Log files[0m + + By default, the log file for mythbackend will be written to + /var/tmp/mythbackend.log. This has been tested and is known to work on + Mandriva and Red Hat, but many people prefer to place logs under + /var/log/. + + To do this, create a group called mythtv (or anything you prefer) and + add your usual MythTV users to that group. If you changed the user + that starts mythbackend from the default of root you [4mmust[24m perform this + step. + + Create the directory /var/log/mythtv and set its permissions as + follows: + + + $ su + # mkdir /var/log/mythtv + # chown root:mythtv /var/log/mythtv + # chmod 0775 /var/log/mythtv + # exit + $ ls -ld /var/log/mythtv + drwxrwxr-x 2 root mythtv 4096 Apr 28 21:58 /var/log/mythtv/ + $ + + + + Create a mythtv file in /etc/logrotate.d: + + + + $ su + # cat > /etc/logrotate.d/mythtv + # Set default values for all log files first... + + # Rotate the logs once a week, or more frequently if they + # exceed 10Mb in size (size is checked daily). + weekly + size 10M + + # 'copytruncate' is used for logs generated by + # currently-running programs that should not be restarted + # (and can't be signalled to start a new log) after the + # rotation. It duplicates the existing log file and then + # sets the length of the existing file to 0. The only time + # this would break would be if the program writing the log + # was using lseek. + copytruncate + + # After rotating the files, leave the most recent rotated + # copy alone but gzip everything else to save space. + compress + delaycompress + + # If a log isn't present then don't worry about it. + missingok + + # Don't rotate an empty file. + notifempty + + # end of the global options + + /var/log/mythtv/mythbackend.log /var/log/mythtv/mythfrontend.log { + # Keep logs until they are 2 months old or the number of + # logs reaches 12. If the log files stay small, the age will + # kick in first and you'll only have 8 log files. If they + # get larger than 10Mb then you won't keep all 60 days. + rotate 12 + maxage 60 + } + + # Different options for mythfilldatabase: + /var/log/mythtv/mythfilldatabase.log { + rotate 2 + } + ^D + # + + + + [1m23.12.1.2. Mandriva[0m + + Mandriva adds one more twist in the form of the msec utility, which + runs regularly and (at the default or any higher security level) sets + permissions on many files, including those under /var/log. + + To tell msec about the MythTV log files and their directory, you need + to edit the /etc/security/msec/perm.local file to include the + following: + + + + # /etc/security/msec/perm.local + # Local overrides to the msec program + # + # Full file path user.group permissions + /var/log/mythtv/ root.mythtv 775 + /var/log/mythtv/* root.mythtv 664 + + + + A copy of the above has been included in the contrib/ directory. You + may add it by typing: + + + $ cd contrib + $ su + # cat etc.security.msec.perm.local >> /etc/security/msec/perm.local + # exit + + + + Finally run the msec tool to check and implement your changes. + + + $ su + # msec + # exit + $ + + + + [1mNOTE[22m: msec can only [4mreduce[24m the permissions of files, so if + you don't get the results you expect, check that you're not asking + msec to add missing permissions to the files or directories you + created. + + [1m23.12.2. Gentoo[0m + + The portage file for MythTV has scripts that will allow you to run + mythbackend at startup. + + To run mythbackend as a daemon which starts at boot time: + + + # rc-update add mythbackend default + + + + To stop mythbackend as a daemon: + + + # /etc/init.d/mythbackend stop + + + + To obtain a list of options: + + # /etc/init.d/mythbackend + + + + [1m23.13. Advanced Backend Configurations[0m + + MythTV is flexible in the way that you define multiple backend tuner + configurations. The only hard-and-fast rule is that the Master + backend [4mmust[24m have a capture device defined, but shouldn't imply that + the capture device in the Master backend must be the first capture + card defined in the database. + + One example of an advanced configuration is the round-robin scheme. + Rather than defining all of the cards on the master, you could first + go into mythtv-setup on the master to define globals such as the + general configuration and the channel lineup but not the host-specific + configuration item like the capture card. In this example, we will + use a 4 tuner configuration, where two slaves have one card each and + the master has two. + + 1. Add the first capture card on one of the slaves. Complete the + configuration, connecting the input source to the card. This will + get cardid #1 in the database. Exit mythtv-setup. + + 2. Configure the first capture card on the master backend. This will + get cardid #2 in the database. Exit mythtv-setup. + + 3. Configure the first capture card on the second slave. This will be + cardid #3 in the database. Exit mythtv-setup. + + 4. Configure the second capture card on the master backend. This will + get cardid #4 in the database. Exit mythtv-setup. + + Using this scheme, the master backend will not use both capture cards + until one of the following happens: + + +o There are four recordings scheduled for the same time + + +o Both slaves are unavailable + + The scheduler in MythTV checks whether an encoder is available; if a + slave backend isn't running, its encoder isn't available, so the + scheduler will look for the next available encoder. This makes MythTV + very flexible; slave tuners can come and go, and as long as there are + enough tuners for what you'd like to record it doesn't matter which + tuner in particular is going to be used. + + Using this round-robin scheme along with a shared storage directory + like NFS and enabling the Master Backend Override setting will allow + you to view content even if the slave backend that recorded a program + is not available. + + + [1m23.14. Using the transcoder[0m + + MythTV's built-in transcoder re-encodes recordings from one codec to + another. The transcoder has three primary uses; it can transcode + MPEG-2 files captured using a hardware encoder (PVR cards, DVB cards, + ATSC HD, etc.) to MPEG-4, it can be used to transcode RTjpeg files + (usually only used on systems that can not real-time encode to MPEG-4 + using a framegrabber) to MPEG-4, and finally it can be used to remove + commercials from a MPEG-2 file while leaving the file in MPEG-2 + format. + + When MythTV transcodes a file to MPEG-4 or RTjpeg the resulting file + format is NuppelVideo (nuv). NuppelVideo is a container which + provides a method of keeping the audio and video in sync throughout + the recording, which is why it is used instead of the .avi format. + You may have difficulty playing .nuv files in non-MythTV systems. + + + The original file is removed when the transcoding process is complete. + Unless you're sure that you will be satisfied with the result you may + want to enable the [1mmythtv-setup [22moption which causes [1mmythbackend [22mto + keep the original file after transcoding. This option is on the + second page of the General section in mythtv-setup. Enabling this + allows you to compare the two files and restore the original if you + like. Outside of the initial setup phase it usually isn't necessary + to leave this option enabled. A recording can be transcoded in two + ways: + + + +o Automatically transcode the file once it has completed recording. + + +o Manually choosing to transcode a recording, usually after importing + a cutlist or manually marking commercials to be removed. + + The second method can be used on files that have already been + transcoded (or files which were are already in the desired format), so + only the frames immediately following a cut section will be re- + encoded, resulting in a minimal loss of quality when removing + commercials with the added benefit of being extremely quick. + + The current transcoding system has a lot flexibility, but there are a + number of steps involved in setting it up. In order to automatically + transcode a given recording you must do the following: + + 1. Configure recording profile for your capture source and enable + transcoding on one or more profiles. + + 2. Configure one or more transcoding profiles. + + 3. Create or alter existing scheduled recordings to enable transcoding + for that recording. + + + [1m23.14.1. Configuring Recording Profiles to Allow Transcoding[0m + + Enter the Utilities/Setup > Setup > TV Settings > Recording Profiles + section in [1mmythfrontend[22m. Choose the option that corresponds to your + capture source (ignore the Transcoders for now.) Choose the quality + profile you are interested in using for transcoding. Ensure that + "Enable auto-transcode after recording" is checked. + + + [1m23.14.2. Configure Transcoding Profiles[0m + + Enter the Recording Profiles > Transcoders menu. There are three + quality settings to choose from and a two special Autodetect settings. + Later, when scheduling recordings you'll have to choose one of + Autodetect, High, Medium, and Low Quality transcode settings in + addition to the recording profile we set up above. If you choose the + Autodetect transcoding profile for a recording, MythTV will use the + "Autodetect from RTjpeg/MPEG-4" profile for recordings which are + RTjpeg/MPEG-4 files. Otherwise, it will use the "Autodetect from + MPEG-2" profile provided it's an MPEG-2 recording. If you choose one + of the others (High, Medium, Low) it will use the settings in that + profile regardless of the codec of the original recording. + + + There are a number of options for transcoding but the simplest is to + enable lossless transcoding (the first option) which subsequently + removes all other options. Enabling lossless encoding simply removes + commercials (if you've marked them) and attempts to clean up MPEG-2 + streams. Note that with this option MythTV will not apply any sort of + filters and will only attempt to normalize the stream into something + cleaner and less likely to have trouble with other less forgiving + MPEG-2 hardware/software (including players, video editors, etc.) + + If you enable resizing of the recording the next page has the settings + for choosing the final resolution. MythTV will scale the video as + appropriate, not crop it to this resolution. + + The final two pages allow configuration of the video and audio codecs. + Although RTjpeg is an option for video codec there is no reason to + transcode [4mto[24m this format because it will produce larger files than + MPEG-4 and the recording will take [4mmore[24m CPU power to play back. The + MPEG-4 settings are described in the documentation for the [1mffmpeg[0m + project at http://ffmpeg.sourceforge.net/ffmpeg-doc.html + <http://ffmpeg.sourceforge.net/ffmpeg-doc.html>. It's a matter of + trial and error to discover which settings achieve a good compromise + between size and quality. + + If you wish to return to the default settings, they are Bitrate: + 2200-2500, MaxQ: 2, MinQ: 15, MaxQDiff: 3, and "Scale bitrate for + frame size" is enabled. The other options are unchecked. + + + [1m23.14.3. Create/Alter Scheduled Recordings to Enable Transcoding[0m + + Transcoding is actually enabled on a per-recording basis. Two things + must be true before any given recording will be auto-transcoded, + however. The first is that the recording must have been made with a + recording profile that has auto-transcode enabled. Under "Storage + Options" for the recording you must set the "Record using the "X" + profile" to the profile you configured in the first step. In + addition, under the "Post Recording Options" section of the recording + you must also set "Transcode new recordings." This is also where you + specify the Transcoding profile to use (Auto, High, Medium, Low.) + + It may not be obvious from above but the flexibility of this system is + primarily to make it possible to auto-transcode a show recorded via + one source (ie: pcHDTV 3000), and not transcode that same show if it's + recorded on another kind of card (ie: PVR-250.) There are other uses + however. You could have a PVR-250 and a V4L card. You may want to + transcode the MPEG-2 from the PVR-250 but there is no need to + transcode the recordings made with the V4L card, as it's already + likely to be MPEG-4. + + As an example, you could configure the Default profile for "Hardware + DVB Encoders" (the profile group used for DVB cards, including ATSC + cards like the pcHDTV 3000) to "Enable auto-transcoding". In the + Default profile for MPEG-2 Encoders (PVR cards) you'd leave "Enable + auto-transcoding" unchecked. For programs that are available on both + kinds of cards you'd set the recording profile to Default and enable + auto-transcoding in the record settings. Then you pick your + transcoding profile. The result is that when a program is recorded on + your DVB card, it will get transcoded. When it plays on a channel + available via your PVR card, it won't be. + + + [1m23.14.4. Manual Transcoding[0m + + Manually transcoding is activated while watching a show by hitting + 'x', from the OSD menu by choosing the Transcode option, or by + choosing Job Options/Transcode from the info menu from the Watch or + Delete Recordings screens. + + The transcoding profile used for manual transcoding is whatever was + set when the recording was originally configured, even if you didn't + enable auto-transcoding. The only way to change what transcoding + profile will be used is to alter the transcoder column in the recorded + table in the database. The transcoder column contains a number which + corresponds with the id column in the recordingprofiles table. You + can find out the id number for each profile in the transcoder group + with an SQL command like: + + + + mysql> select r.* from recordingprofiles r,profilegroups p where p.name='Transcoders' and p.id=r.profilegroup; + +----+----------------+------------+------------+--------------+ + | id | name | videocodec | audiocodec | profilegroup | + +----+----------------+------------+------------+--------------+ + | 21 | RTjpeg/MPEG4 | MPEG-4 | MP3 | 6 | + | 22 | MPEG2 | MPEG-4 | MP3 | 6 | + | 27 | High Quality | MPEG-4 | MP3 | 6 | + | 28 | Medium Quality | MPEG-4 | MP3 | 6 | + | 29 | Low Quality | MPEG-4 | MP3 | 6 | + +----+----------------+------------+------------+--------------+ + 5 rows in set (0.01 sec) + + mysql> + + + + Armed with the knowledge of what the profile ID's are you can also + choose to run mythtranscode from the command line and explicitly + specify the transcoder profile. Run mythtranscode --help for usage + information. + + + [1m23.15. Changing your hostname[0m + + If you need to change the name of the computers used with MythTV + you'll need to perform a sequence of steps. There are a number of + pieces of information that MythTV keeps track of which are tied to the + hostname of the box, so changing the hostname involves altering the + name in the operating system and in the MySQL database. In the + examples below, the old name of the system was "frontend1" and we're + going to change it to "kidsroom". + + + + [1mNOTE[22m: Changing the hostname using direct SQL update commands will + break things. You [4mMUST[24m use this indirect method. + + 1. Stop all backends. If you run [1mmythbackend [22mfrom a terminal + session, press control-c. If your backends are started with an init + script, you would do something like the following: + + + $ su + # /etc/init.d/mythbackend stop + + + + 2. Change the hostname. + + For Red Hat and derived distributions, edit the /etc/sysconfig/network + file. Look for HOSTNAME=frontend1 and change this to + HOSTNAME=kidsroom or whatever you'll be using. For other + distributions, refer to the documentation, such as the + + hostname(1) + + + + To alter the hostname in the current session, run: + + + # hostname kidsroom + + + + 3. Dump the database. + + + $ mysqldump -u mythtv -pmythtv mythconverg -c > mythtv_backup.sql + + + + 4. Rename the host in the database. First, ensure that the new + hostname you'll be using isn't already in the database. + + + $ grep kidsroom mythtv_backup.sql + + + + Now we're actually going to change the name. The following should all + be typed on the same line: + + + $ cat mythtv_backup.sql | sed s/\'frontend1\'/\'kidsroom\'/g >> mythtv_restore.sql + + + + If you don't feel comfortable using [1msed[22m, you can open the + mythtv_backup.sql file in a text editor and perform a global search + and replace. When saving the file, make sure you use the new name, + mythtv_restore.sql or the rest of the steps below will fail. + + 5. Drop and recreate the database. + + + $ mysql -u root + mysql>drop database mythconverg; + mysql>create database mythconverg; + mysql>exit + + + + 6. Restore the database using your edited version. + + + + $ mysql -u mythtv -pmythtv mythconverg < mythtv_restore.sql + + + + If you are running slave backends or frontends, don't forget to re- + enable access as detailed in ``Modifying access to the MySQL database + for multiple systems''. + + 7. Start the backends. If you use init scripts, do the following, + otherwise start them from terminal consoles. + + + # /etc/init.d/mythbackend start + + + + 8. Quit and restart all frontends. Delete the mythtv_backup.sql and + mythtv_restore.sql files. + + + [1m23.16. Can I run MythTV on my TiVo?[0m + + [1m23.17. Can I run MythTV on my ReplayTV?[0m + + No. + + While it is true that the TiVo runs the Linux kernel, and TiVo has + released their changes to the kernel under the GPL, the TiVo is [4mnot[24m a + general-purpose computer, and there is no programming information + available for the custom hardware contained within a TiVo. TiVo is + under no obligation to release the source code to their [4mapplication[24m. + + The ReplayTV runs VxWorks, a Real Time Operating System from Wind + River Systems. + + [1m23.18. Can a wireless connection be used between the frontend and the[0m + [1mbackend?[0m + + Yes, assuming that your wireless connection has sufficient bandwidth + to maintain the datarate between the frontend and the backend. + 802.11b should be sufficient if the encoded bitrate of the content is + less than the datarate of your wireless connection, which in the case + of 802.11b would be approximately 4 Mbps. (The advertised rate of + 11Mbps gives an actual throughput of 4 Mbps.) 802.11a and 802.11g, if + operating in their high-speed modes, or proprietary 802.11b "Turbo" + schemes should be adequate. Multiple wireless frontends, poor signal + strength or other factors can severely impact the viewing experience + on the frontend. + + + [1m23.19. How can I burn shows that I have recorded to a DVD?[0m + + Use the mytharchive plugin. + + + [1m23.20. Using the DBoxII within MythTV[0m + + The configuration of the DBoxII for use within MythTV is tricky (as of + May 16 2005), that's why it's covered here. Your DBoxII has to be + running linux and the Neutrino GUI instead of the stock BetaNova + firmware. For further information, please refer to + http://www.tuxbox.org <http://www.tuxbox.org>. Additionally, you need + to enable the SPTS mode in Neutrino. + + +o Add a new "Capture Card" in the setup. The "Card type" is "DBOX2 + Input", the other values have to be adjusted according to your + setup. The default values, except for the "DBOX2 host ip", should + work fine. + + +o Define a new video source. It doesn't need to be configured, you + just need to define it. MythTV grabs the EPG from the DBoxII. + + +o Connect the DBoxII to the newly defined input source in "input + connections". + + +o Since channel scanning is not implemented yet, you need to define + channels in the "Channel Editor". Make sure that you use the same + value for "Channel Name" as on the DBoxII. You can get a list of + available channels from the web interface of Neutrino at http://ip- + of-your-box:80/. Associate the channel with your new video source + and repeat when needed. + + You may leave the Setup now and proceed as usual. + + + [1m23.21. What do the icons on the Watch Recordings screen mean?[0m + + Press "1" or F1 to get a popup. + + [1m23.22. What do the letters mean when I change channels?[0m + + These letters let you know what's going on with the backend as it + tries to tune to a channel. + + Lower case = seen + + Upper Case = seen & good + + +o l/L = Lock : This could be seen by PVR-250/BTTV users + + +o a/A = PAT : Any recording transmitted in MPEG + + +o m/M = PMT : Any recording transmitted in MPEG + + +o g/G = MGT : ATSC only + + +o v/V = VCT : ATSC only + + +o n/N = NIT : DVB only + + +o s/S = SDT : DVB only + + [1m23.23. What is the difference between the various Hauppauge PVR mod-[0m + [1mels?[0m + + This is covered in the hardware section, and extensively covered on + the Hauppauge website. + (http://www.hauppauge.com/pages/compare_pvr.html + <http://www.hauppauge.com/pages/compare_pvr.html>) Please check the + Hauppauge website for the most accurate information. + + A PVR-150 comes in a number of versions: + + +o The PVR-150 (Model 1045) is the retail kit. It comes with a remote + control and an IR Blaster. It does not have a radio tuner. + + +o The PVR-150 MCE (Model 1042) will usually come in a plain white box + and is sold as an OEM device. It does not come with a remote + control, since it's usually used as the second, third, etc capture + device. + +o The PVR-150 MCE Kit (Model 1062) does not have a radio tuner and + comes with a Microsoft Media Center remote control instead of + Hauppauge's. + + +o The PVR-150 low profile (Model 1086) is a low-profile card. It has + a radio tuner and is approximately half the height of a standard + card. However, it comes with a low-profile PCI bracket, so it is + not suitable for use in a standard PCI slot without removing the + bracket, which may not be worth the trouble. + + A PVR-250 (Model 980) is a retail kit which comes with an IR receiver + and a remote control. + + The PVR-250 MCE (Model 975) contains a FM radio tuner. The PVR-250 + MCE does not contain a IR receiver or a remote. + + The PVR-250 Rev 1 contained an MPEG-2 decoder. However, this function + was not connected to any output jacks, and there doesn't appear to be + any way to pull decoded video from the card, so it's a fairly useless + feature. + + The PVR-350 (model 990) has the features of the PVR-250 as well as + being able to decode MPEG-2. The encode and decode functions may be + used simultaneously. The MPEG-2 decoder function gives superior video + quality compared to what you'll find on a standard video card. + However, the decoder function is only available once Linux has + started, so you will not see any boot-time messages. Also, the card + is not capable of resolutions higher than 720x480, so it cannot be + used with HDTV. Make a conscious decision (and ask for advice on the + mailing list) that you want to tradeoff potential HDTV use in the + future compared to video quality. + + The X-driver for the PVR-350 support playback using Xv efficiently but + does not support any other 2D or 3D acceleration. For some application + this may place a large load on the host CPU, some will run without any + problem and others (mplayer, xine, xmame etc.) should be configured to + utilize the Xv interface. + + Note that for the PVR-350 there are some ``considerations'' regarding + the way audio is handled. + + The PVR-500 is a dual-encoder version of the PVR-150 card, so you can + simultaneously record two different programs at the same time, because + there are two encoder chips on the PCI card. Hauppuage has also + installed an onboard splitter, so you can use one COAX to feed both + tuners. Current versions of the PVR-500 should come with an adapter + to allow you to connect a second S-Video or composite input, but this + will take up a second PCI slot. Early adopters may need to purchase + this item separately. + + + [1m23.24. Changing channels on an external Set Top Box[0m + + If you need to use an external Set Top Box (STB), such as for + satellite TV or for digital cable you will need some way for MythTV to + tell the STB to switch to a new channel. There are several methods: + + 1. Use an IR blaster. An IR blaster is an infrared transmitter + connected to your computer. When MythTV needs to change channels + it will send IR pulses, thereby emulating a remote control. + + 2. Use a direct serial connection. Some STB's have a serial port on + the back, although it may not look like a serial port. It may look + like a phone jack, or a strange VGA connector. It may be labeled + "Low Speed Data". A direct serial connection is more reliable than + an IR blaster. Not all STB's that have a Low Speed Data port have + it enabled; you may need to convince your service provider to turn + it on. Stating that you have a Tivo may help; the Tivo has a + direct-connect capability. + + 3. Use a firewire connection. There is a 6200ch.c in the MythTV + contrib directory which may work for you. + + [1m23.25. Configuring one machine to flag all commercials[0m + + Commercial flagging can be CPU intensive. By default, the backend + that created a recording is the one which will flag commercials. You + may wish to use a different machine to run commercial flagging. + + On the slower machine: + + Start the mythtv-setup program. Advance through the pages until you + get to the Job Queue page. Turn off the setting that says "Allow + Commercial Detection jobs", thereby preventing any commercial flagging + jobs from running on this machine. + + Next, make sure that "Run Jobs only on original recording host" is + turned OFF so that new jobs are allowed to run anywhere. + + Restart [1mmythbackend [22msince it only reads this setting when it starts + up. + + On the faster machine: + + Start the [1mmythtv-setup [22mprogram. Advance through the pages until you + get to the Job Queue page. Ensure that "Allow Commercial Detection + jobs" is turned ON for this machine. + + Run [1mmythjobqueue[22m. [1mmythjobqueue [22mwill examine the JobQueue and run any + jobs it finds. [1mmythjobqueue [22mshould be left running so that it will + pick up any new commercial flagging jobs that are added to the queue, + otherwise new jobs will be added to the queue and your programs won't + be flagged until you run manually run [1mmythjobqueue[22m. + + Using this technique it's possible to add commercial flagging machines + as needed, even on systems that aren't running a backend. It's also + possible to run the commercial flagger in a virtual machine + environment such as VMWare. + + + [1m24. Example Configurations.[0m + + [1m24.1. Logical Volume Manager (LVM)[0m + + LVM greatly increases the flexibility you have in managing your + storage than traditional physical partitions. This section will + provide some brief notes on how to use LVM to create storage space for + your video files and how to add additional disk space in the future. + There's lots more that can be done with LVM, so check the LVM HOWTO + http://tldp.org/HOWTO/LVM-HOWTO/ <http://tldp.org/HOWTO/LVM-HOWTO/> + document for details. + + + + [1mNOTE[22m: If you are running MythTV 0.21 and you are using LVM to + create one large filesystem to store your recordings, it's no longer + recommended that you go the LVM route. The preferred solution is to + use ``Storage Groups''. They're more flexible and less likely to lose + all of your recordings if you have a drive failure. + + If you don't understand how to partition a drive, or how to change the + partition type you should stop and look at documentation on how to + perform these steps. + + + + [1mBIG FAT WARNING[22m: Using an incorrect parameter can make your files + inaccessible, prevent your computer from booting, etc. Be careful! + + Make sure your kernel configuration includes LVM support or that it's + available as a module. Today, most vendors include this by default. + You'll also want to ensure that you have a copy of the LVM utilities; + check your distribution, or get the latest versions from + http://www.sistina.com/products_lvm.htm + <http://www.sistina.com/products_lvm.htm> and build them manually. + + Check that the [1mvgscan [22mprogram is being run at some point during your + boot sequence - most distributions do this by default. Look for a + message during boot up that looks like this: vgscan -- reading all + physical volumes (this may take a while...) If you don't see any + messages during boot, you may need to install a LVM init script or + confirm that you have all of the LVM packages installed from your + distribution. + + LVM uses a few concepts you should be familiar with before starting. + + +o PV (Physical Volume). The actual partition on the hard drive. + + +o VG (Volume Group). The aggregation of all the PVs make a VG. + + +o LV (Logical Volume). Subdivision of the pool of space available in + the VG into individual chunks, like /usr, /var/video, etc. + + The following example assumes that you want to create a LVM partition + from a chunk of space in /dev/hda5, using a reiserfs filesystem and + mounted on /var/video. You later decide to extend this filesystem by + adding a new disk: /dev/hdb. + + You need to create at least one LVM partition for a physical volume. + Use [1mfdisk [22mor your favorite partition editor to set the type to LVM + (0x8e). If you're using an entire disk, create one big partition + rather than using the device itself. e.g. use /dev/hdb1 not /dev/hdb. + + In the following example, you have a 15GB disk. The first 6GB are set + as your boot partition. /dev/hda2 was added as an extended partition, + and within that partition you created the /dev/hda5 linux (ext2) + partition. + + + + # fdisk /dev/hda + + The number of cylinders for this disk is set to 1823. + There is nothing wrong with that, but this is larger than 1024, + and could in certain setups cause problems with: + 1) software that runs at boot time (e.g., old versions of LILO) + 2) booting and partitioning software from other OSs + (e.g., DOS FDISK, OS/2 FDISK) + + Command (m for help): p + + Disk /dev/hda: 15.0 GB, 15000330240 bytes + 255 heads, 63 sectors/track, 1823 cylinders + Units = cylinders of 16065 * 512 = 8225280 bytes + + Device Boot Start End Blocks Id System + /dev/hda1 * 1 764 6136798+ 83 Linux + /dev/hda2 765 1823 8506417+ 5 Extended + /dev/hda5 765 1823 8506417 83 Linux + + Command (m for help): t + Partition number (1-6): 5 + Hex code (type L to list codes): 8e + + Command (m for help): p + + Disk /dev/hda: 15.0 GB, 15000330240 bytes + 255 heads, 63 sectors/track, 1823 cylinders + Units = cylinders of 16065 * 512 = 8225280 bytes + + Device Boot Start End Blocks Id System + /dev/hda1 * 1 764 6136798+ 83 Linux + /dev/hda2 765 1823 8506417+ 5 Extended + /dev/hda5 765 1823 8506417 8e Linux LVM + + Command (m for help): w + + # + + + + Create the LVM physical volume from the partitions (repeat if you have + multiple partitions to use): + + + # pvcreate /dev/hda5 + + + + Create a LVM volume group out of this physical volume called + "VGforMyth" that is allocated in chunks that are a multiple of 64MB + + + # vgcreate VGforMyth -s 64m /dev/hda5 + + + + Create a logical volume of 5GB called "video" and then create the + reiserfs filesystem and mount it: + + + + # lvcreate --name video --size 5G VGforMyth + # mkreiserfs /dev/VGforMyth/video + # mount /dev/VGforMyth/video /var/video + + + + Now create a 3GB volume for mythmusic files if you like: + + + # lvcreate --name music --size 3G VGforMyth + # mkreiserfs /dev/VGforMyth/music + # mount /dev/VGforMyth/music /var/music + + + + Display the volume group status: # vgdisplay -v + + Now, lets suppose you want to add a 60GB hard disk to the system as + hdb and allocate 50GB of it to video storage. + + First, create a single partition /dev/hdb1 covering the whole disk and + make it type 0x8e using your partition editor. + + # fdisk /dev/hdb .... create partition, set type, save and reboot if + it says you have to + + Create the new LVM physical volume: + + # pvcreate /dev/hdb1 + + Add the new physical volume to the volume group: + + # vgextend VGforMyth /dev/hdb1 + + + + [1mNOTE[22m: You may get errors at this point stating that there are no + physical volumes available for adding to the LV, even though you know + for a fact that there are. You may need to specify the physical + volume in the /dev/ide/host/bus/target/lun/etc format. Once you've + completed one of the following two procedures, use [1mdf [22mto check that + you've got more space. + + Make the logical volume used for video bigger: + + # lvextend --size +50G /dev/VGforMyth/video + + [1m24.1.1. ReiserFS[0m + + Unmount, resize and remount the filesystem. Technically, you don't + need to unmount and remount the ReiserFS. + + + # umount /var/video + # resize_reiserfs /dev/VGforMyth/video + # mount /dev/VGforMyth/video /var/video + + + + [1m24.1.2. ext2 or ext3[0m + + LVM comes with a program called [1mresize2fs[22m. + + Unmount, resize and remount the filesystem. The filesystem [4mmust[24m be + unmounted during this procedure. + + + # umount /var/video + # resize2fs --size +50G /dev/VGforMyth/video + # mount /dev/VGforMyth/video /var/video + + + + [1m24.1.3. xfs[0m + + XFS does not need to be unmounted to extend the size: + + + # xfs_growfs /var/video + + + + [1m24.2. Advanced Partition Formatting[0m + + The partitions that your distribution sets up for you may not be + optimized for large files. Using LVM in conjunction with the following + techniques can be quite useful. + + Unlike a typical filesystem, a MythTV video partition is usually a + very large filesystem filled with a fairly small number of large + files. Filesystem I/O is usually not an issue, even in multi-tuner + and/or multi-frontend setups. + + There is however, one aspect of filesystem performance that can have a + bearing on the performance of MythTV. In Linux, deleting a file will + utilize I/O bandwidth until the deletion has been completed. If + deleting the file takes long enough, the video capture buffer may + overrun, thereby resulting in dropped frames. Some filesystems are + faster at deleting files than others and, for multi-gigabyte MythTV + video files, these differences can be significant. + + Fortunately, there are published tests + (http://aurora.zemris.fer.hr/filesystems/big.html + <http://aurora.zemris.fer.hr/filesystems/big.html>) that provide + insight into filesystem performance under conditions relevant to + MythTV usage. In addition, some limited testing (archived at + http://www.gossamer-threads.com/lists/mythtv/users/52672 + <http://www.gossamer-threads.com/lists/mythtv/users/52672>) with very + large files (10 gigabytes) was reported in the MythTV Users mailing + list. + + + [1m24.2.1. Ext2[0m + + Ext2 was the defacto standard Linux filesystem for many years. It is + stable, provides good I/O performance and can quickly delete large + files. The primary disadvantage of Ext2 is that it is not a + journaling filesystem, so a file system consistency check (fsck, which + is normally only performed after a system crash) can take many hours + on a filesystem the size of a typical MythTV partition. + + + + [1m24.2.2. Ext3[0m + + Ext3 is Ext2 with a journal, so your biggest gain is that in case of a + crash and reboot you won't have to wait very long for your partition + to be remounted. + + There are options available when formatting an Ext3 partition, as in: + + + # mkfs.ext3 -T largefile4 /dev/hdb1 + + + + This example assumes that /dev/hdb1 has already been created using + [1mfdisk[22m. If you're using LVM, /dev/hdb1 may be something like + /dev/VGforMyth/video. + + The "-T largefile4" option creates one inode per 4 megabytes, which + can provide a few percent more storage space. However, tests indicate + that using the "-T largefile4" option can drastically increase the + amount of time required to delete a large file and thus it should only + be used with encoder settings that produce small video files (YMMV). + + You can check on your filesystem using the [1mdumpe2fs [22mprogram. See the + man page for details. + + [1m24.2.3. ReiserFS[0m + + The Reiser filesystem is another journaling filesystem commonly + distributed with Linux. It is known to be an extremely efficient + filesystem and it especially excels at managing partitions containing + a large number of small files. However, tests indicate it is not the + fastest at deleting very large files. For that reason, it may not be + the best choice when using encoder bitrates that produce very large + files. + + + [1m24.2.4. JFS[0m + + JFS (Journaling File System) is a journaling filesystem originally + developed by IBM for AIX which was later released as open source. + While not as common as Ext3 or ReiserFS, it is distributed with RedHat + 9 (RH9), Fedora Core and Mandriva as well as other distros. According + to tests, JFS is the file deletion speed king, deleting virtually any + file in under one second, even files as large as 10 gigabytes. + + + [1m24.2.5. XFS[0m + + XFS is a journaling file system originally developed by SGI for Irix, + and later released as open source. While not a part of the default + RedHat Linux 9 or Fedora Core installation (although it is a part of + Mandriva and Fedora Core 2+), it can be easily installed via ATrpms. + XFS provides deletion speeds for large files only slightly slower than + JFS. According to the test results shown at + (http://aurora.zemris.fer.hr/filesystems/big.html + <http://aurora.zemris.fer.hr/filesystems/big.html>), XFS provide + higher I/O rates than JFS, albeit at a higher CPU loading. This may + cause issues if you do not have the spare CPU capacity to handle XFS, + potentially leading to dropped frames. + + + + [1m24.3. Migrating from DataDirect Labs to Schedules Direct[0m + + MythTV v0.20.2 or later is required to natively support Schedules + Direct. Code has been included to make the transition as simple as + possible. + + [1mYou do not need to delete your existing video sources or add new ones![0m + + The following steps should work for most users: + + +o Create a Schedules Direct account and use the same information as + your existing lineups at Zap2It Labs. Do not add or delete + channels at this time. + + +o Shut down any running [1mmythfrontend [22mand [1mmythbackend [22mprograms. + + +o Perform a backup of your existing database. See ``Saving or + restoring the database'' for instructions. + + +o Run [1mmythtv-setup [22m-> Video Sources. Change the grabber to Schedules + Direct, update the username and password fields with the account + information you created at Schedules Direct and select "Retrieve + Lineups". Click Finish. + + +o Exit [1mmythtv-setup [22mand run [1mmythfilldatabase[22m. Check if there were + any errors. + + +o Restart your [1mmythbackend [22mand [1mmythfrontend [22mprograms. + + + [1m24.4. Caching support for Schedules Direct[0m + + MythTV 0.20.2 or later supports caching of downloaded information from + Schedules Direct, so devices that share a common source do not require + multiple downloads. + + Before beginning, perform a backup of your existing database. See + ``Saving or restoring the database'' for instructions. + + In the following scenario, assume that you have the following: + + 1. A PVR-150 MPEG-2 encoder card connected directly to a CATV source. + + 2. A PVR-250 MPEG-2 encoder card connected via S-Video to a CATV Set + Top Box. + + What we are going to do is to create a single lineup at Schedules + Direct and then create two Video Sources which use the same login + information but have different channels associated with them. + + On your Schedules Direct account, create a lineup that has all of the + channels that you can receive. Because we have a Set Top Box (STB), + choose a Digital lineup. Yes, this means that you may have 900 + channels in this lineup, but that's OK. + + Use the Schedules Direct channel editor and unselect any channels that + you can't tune without the STB. This will usually be channels higher + than 125, but check your CATV provider lineup if you're not sure. + Once you've deselected them (using a click on the first channel you + can't receive and then a shift-click on the last channel you can't + receive will deselect all the channels in between those two.) click + the Save Changes button at the bottom of the screen. + + In [1mmythtv-setup[22m, create a Video Source with an appropriate name. "SD- + Analog Only" will be used in this example. Click "Retrieve Lineups" + and select the digital lineup you just created at Schedules Direct. + Click "Finish" to return to the Video sources selector and then press + the ESC key to go back to the main screen. + + Now choose Input Connections. Select the PVR-150 which is connected + directly to the CATV. Set the Video Source to "SD-Analog Only" and + click "Fetch channels from listings source". + + Set the start channel to an appropriate value. + + [1mNOTE[22m: There is a bug where the "Fetch" command may not work; you can + tell that the Fetch did not retrieve any channels in one of two ways: + in the text-mode console, you will see a connection to Schedules + Direct, but it doesn't appear to retrieve any channel information: + + + 2007-08-25 15:03:05.526 New DB DataDirect connection + 2007-08-25 15:03:05.526 Connected to database 'mythconverg' at host: localhost + 2007-08-25 15:03:05.536 DataDirect: Your subscription expires on 11/23/2007 01:12:10 PM + 2007-08-25 15:03:05.707 New DB connection, total: 3 + 2007-08-25 15:03:05.707 Connected to database 'mythconverg' at host: localhost + 2007-08-25 15:03:05.708 sourceid 2 has lineup type: CableDigital + 2007-08-25 15:03:06.623 Data fetching complete. + 2007-08-25 15:03:06.624 DataDirect: Deleting temporary files + + + + or, the "Please add channels to this source" message in the "Starting + channel" field stays on the screen. + + If either of these happens, save the information on this screen by + clicking the "Finish" button. Exit back to the Input connections + screen by pressing ESC, then select this Input Connection again. This + time the Fetch will work and the "Please add channels to this source" + message will disappear. + + If you look at the text-mode console, you'll see this if the channel + retrieval is working: + + + 2007-08-25 15:04:32.437 New DB DataDirect connection + 2007-08-25 15:04:32.437 Connected to database 'mythconverg' at host: localhost + 2007-08-25 15:04:32.447 DataDirect: Your subscription expires on 11/23/2007 01:12:10 PM + 2007-08-25 15:04:32.622 New DB connection, total: 3 + 2007-08-25 15:04:32.622 Connected to database 'mythconverg' at host: localhost + 2007-08-25 15:04:32.623 sourceid 2 has lineup type: CableDigital + 2007-08-25 15:04:33.418 DataDirect: Adding channel 41 'AMC' (AMC). + 2007-08-25 15:04:33.422 DataDirect: Adding channel 32 'A & E Network' (AETV). + 2007-08-25 15:04:33.425 DataDirect: Adding channel 66 'Black Entertainment Television' (BET). + 2007-08-25 15:04:33.427 DataDirect: Adding channel 180 'Bravo' (BRAVO). + 2007-08-25 15:04:33.430 DataDirect: Adding channel 51 'ABC Family' (FAM). + 2007-08-25 15:04:33.432 DataDirect: Adding channel 146 'Country Music Television' (CMTV). + 2007-08-25 15:04:33.435 DataDirect: Adding channel 39 'CNBC' (CNBC). + 2007-08-25 15:04:33.437 DataDirect: Adding channel 36 'Cable News Network' (CNN). + 2007-08-25 15:04:33.440 DataDirect: Adding channel 35 'CNN Headline News' (CNNH). + + + + Repeat the Input Connection configuration for any other capture + devices that are connected directly to the CATV system. You do not + need to click Fetch once you've done one successful download of the + channel information - the Starting channel should be automatically + populated. + + + Go back to Schedules Direct and re-enable the channels that you had + previously deselected, then click Save Changes. + + Create a new Video Source, here called "SD-All Digital Channels". + Perform the same "Retrieve Listings" you did before. + + Go back to the Input Connections screen, select the PVR-250 which is + connected to the STB, assign the "SD-All Digital Channels" video + source and perform a retrieve channels. This will pull down the + complete channel listing, but only for [4mthis[24m device. + + When [1mmythfilldatabase [22mruns, it will cache the "big" download which is + appropriate for the STB, and then copy the information to the channels + that can only be accessed without the STB. But by default + [1mmythfilldatabase [22mis going to notice that the "Analog only" video + source is missing the channels that are in the Digital lineup you + created at Schedules Direct, so we need to override the addition of + new channels. + + When you run [1mmythfilldatabase [22mto populate your database, you'll need + to run it like this: + + + + $ mythfilldatabase --remove-new-channels + + + + You will also need to modify how the [1mmythbackend [22mcalls + [1mmythfilldatabase [22mwhen it performs its automatic listings update. + + In [1mmythfrontend[22m, select "Setup" -> "General". + + Continue press ENTER until you reach the Mythfilldatabase + configuration screen. In the "mythfilldatabase Arguments" field, type + --remove-new-channels + + then press the TAB key until you reach Finish, then press ENTER to + save. You can then press ESC until you return to the main screen. + + + diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/stop.eps b/abs/core-testing/local-website/htdocs/mythtv-doc/stop.eps new file mode 100644 index 0000000..534208a --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/stop.eps @@ -0,0 +1,103 @@ +%!PS-Adobe-3.0 EPSF-3.0 +%%Creator: tiff2ps +%%Title: stop.tif +%%CreationDate: Tue Feb 24 10:42:00 2004 +%%DocumentData: Clean7Bit +%%Origin: 0 0 +%%BoundingBox: 0 0 19 19 +%%LanguageLevel: 1 +%%Pages: (atend) +%%EndComments +%%BeginSetup +%%EndSetup +%%Page: 1 1 +gsave +100 dict begin +18.750000 18.750000 scale +/bwproc { + rgbproc + dup length 3 idiv string 0 3 0 + 5 -1 roll { + add 2 1 roll 1 sub dup 0 eq { + pop 3 idiv + 3 -1 roll + dup 4 -1 roll + dup 3 1 roll + 5 -1 roll put + 1 add 3 0 + } { 2 1 roll } ifelse + } forall + pop pop pop +} def +/colorimage where {pop} { + /colorimage {pop pop /rgbproc exch def {bwproc} image} bind def +} ifelse +%ImageData: 25 25 8 3 0 1 2 "false 3 colorimage" +/line 75 string def +25 25 8 +[25 0 0 -25 0 25] +{currentfile line readhexstring pop} bind +false 3 colorimage +ffffffffffffffffffffffffffffffffffffffffffffc3c3ff9f9fff9f9fff9f9f +ff9f9fff9f9fff9f9fff9f9fff9f9fff9f9fffb7b7ffffffffffffffffffffffff +ffffffffffffffffffffffffffffffffffffffffffffffffffffffffbcbcffc1c1 +ffbfbfffbfbfffbfbfffbfbfffbfbfffbfbfffbfbfffbfbfffbfbfffc7c7ffabab +ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff +ffbcbcffc1c1ff3030ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000 +ff0000ff2020ffbfbfffababffffffffffffffffffffffffffffffffffffffffff +ffffffffffffffbcbcffc1c1ff3030ff0000ff0000ff0000ff0000ff0000ff0000 +ff0000ff0000ff0000ff0000ff0000ff2020ffbfbfffababffffffffffffffffff +ffffffffffffffffffffffffffbcbcffc1c1ff3030ff0000ff0000ff0000ff0000 +ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff2020ffbfbf +ffababffffffffffffffffffffffffffffffffbcbcffc1c1ff3030ff0000ff0000 +ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000 +ff0000ff0000ff2020ffbfbfffababffffffffffffffffffffbcbcffc1c1ff3030 +ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000 +ff0000ff0000ff0000ff0000ff0000ff0000ff2020ffbfbfffababffffffffc3c3 +ffc1c1ff3030ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000 +ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff2020 +ffbfbfffb9b9ffafafff9f9fff0000ff3030ff4040ff4040ff3030ff2020ff4040 +ff4040ff4040ff4040ff0808ff0000ff3030ff4040ff1818ff0000ff0000ff1818 +ff4040ff3838ff0000ff8080ffbfbfffafafff9f9fff9797ffffffffffffffffff +ffbfbfff8080ffffffffffffffffffffffffff2020ffa7a7ffffffffffffffffff +ff4848ff3838ffffffffffffffffffffc7c7ff8080ffbfbfffafafff9f9ffff7f7 +ffe7e7ff5050ff4040ff3030ff2020ff4040ffffffffb7b7ff4040ff0808fff7f7 +ffd7d7ff7070ffffffff9f9fff9797ffffffff8787ffc7c7ffffffff8c8cffbfbf +ffafafff9f9fffffffffcfcfff4040ff0808ff0000ff0000ff0000ffffffff9f9f +ff0000ff0000ffffffff8080ff0000ffdfdfff9f9fff9f9fffffffff4040ffb7b7 +ffffffff9090ffbfbfffafafff9f9fffafaffffffffffffffff7f7ff5050ff0000 +ff0000ffffffff9f9fff0000ff0000ffffffff8080ff0000ffdfdfff9f9fff9f9f +ffffffffffffffffffffdfdfff8080ffbfbfffafafff9f9fff0808ff6060ff8f8f +ffffffffb7b7ff0000ff0000ffffffff9f9fff0000ff0000ffffffff8080ff0000 +ffdfdfff9f9fff9f9fffffffff8080ff7070ff1818ff8080ffbfbfffafafff9f9f +ff0000ff0000ff1818ffefefffbfbfff0000ff0000ffffffff9f9fff0000ff0000 +ffffffffb7b7ff2020fff7f7ff9f9fff9f9fffffffff0000ff0000ff0000ff8080 +ffbfbfffafafff9f9fffffffffffffffffffffffffff8f8fff0000ff0000ffffff +ff9f9fff0000ff0000ffcfcfffffffffffffffffffff7070ff9f9fffffffff0000 +ff0000ff0000ff8080ffbfbfffafafff9f9fff8080ff8080ff8080ff6868ff1010 +ff0000ff0000ff8080ff5050ff0000ff0000ff2828ff7878ff8080ff6868ff0808 +ff5050ff8080ff0000ff0000ff0000ff8080ffbfbfffaeaeffbfbfff0808ff0000 +ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000 +ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ffafafffb2b2ffffff +ffa3a3ffafafff0808ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000 +ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff9f9f +ff9c9cffffffffffffffffffffa3a3ffafafff0808ff0000ff0000ff0000ff0000 +ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000 +ff0000ff9f9fff9c9cffffffffffffffffffffffffffffffffa3a3ffafafff0808 +ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff0000 +ff0000ff0000ff0000ff9f9fff9c9cffffffffffffffffffffffffffffffffffff +ffffffffa3a3ffafafff0808ff0000ff0000ff0000ff0000ff0000ff0000ff0000 +ff0000ff0000ff0000ff0000ff0000ff9f9fff9c9cffffffffffffffffffffffff +ffffffffffffffffffffffffffffffffa3a3ffafafff0808ff0000ff0000ff0000 +ff0000ff0000ff0000ff0000ff0000ff0000ff0000ff9f9fff9c9cffffffffffff +ffffffffffffffffffffffffffffffffffffffffffffffffffffffffa3a3ffb7b7 +ff8080ff8080ff8080ff8080ff8080ff8080ff8080ff8080ff8080ffafafff9c9c +ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff +ffffffffffffffb7b7ffbfbfffbfbfffbfbfffbfbfffbfbfffbfbfffbfbfffbfbf +ffbfbfffb2b2ffffffffffffffffffffffffffffffffffffffffff +end +grestore +showpage +%%Trailer +%%Pages: 1 +%%EOF diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/stop.png b/abs/core-testing/local-website/htdocs/mythtv-doc/stop.png Binary files differnew file mode 100644 index 0000000..bf24d76 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/stop.png diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/warning.eps b/abs/core-testing/local-website/htdocs/mythtv-doc/warning.eps new file mode 100644 index 0000000..e9bf928 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/warning.eps @@ -0,0 +1,134 @@ +%!PS-Adobe-3.0 EPSF-3.0 +%%Creator: tiff2ps +%%Title: warning.tif +%%CreationDate: Tue Feb 24 11:06:30 2004 +%%DocumentData: Clean7Bit +%%Origin: 0 0 +%%BoundingBox: 0 0 24 24 +%%LanguageLevel: 1 +%%Pages: (atend) +%%EndComments +%%BeginSetup +%%EndSetup +%%Page: 1 1 +gsave +100 dict begin +23.250000 23.250000 scale +/bwproc { + rgbproc + dup length 3 idiv string 0 3 0 + 5 -1 roll { + add 2 1 roll 1 sub dup 0 eq { + pop 3 idiv + 3 -1 roll + dup 4 -1 roll + dup 3 1 roll + 5 -1 roll put + 1 add 3 0 + } { 2 1 roll } ifelse + } forall + pop pop pop +} def +/colorimage where {pop} { + /colorimage {pop pop /rgbproc exch def {bwproc} image} bind def +} ifelse +%ImageData: 31 31 8 3 0 1 2 "false 3 colorimage" +/line 93 string def +31 31 8 +[31 0 0 -31 0 31] +{currentfile line readhexstring pop} bind +false 3 colorimage +ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff +fffffffffffffffff8ffffdcffffbaffffffffffffffffffffffffffffffffffff +ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff +fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff4 +ffff7affff10ffff27fcfcc1f7f7f9fdfdffffffffffffffffffffffffffffffff +ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff +fffffffffffffffffffffffffffffffffffffffffffffff9feff92fcfe03ffff00 +ffff03f1f116b4b48dcbcbefffffffffffffffffffffffffffffffffffffffffff +ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff +ffffffffffffffffffffffffffffffffffcffcf739e4dd01ffff28ffff21fefe00 +b3b315757595cecef6ffffffffffffffffffffffffffffffffffffffffffffffff +ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff +fffffffffffffffff9ffffa3f9e601ffe40dffff4cffff3bffff04f5f51146464a +7e7ed4fefef8ffffffffffffffffffffffffffffffffffffffffffffffffffffff +ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff +fafacff9fa38e6e400ffff07ffff1affff34ffff19ffff0096962b5f5f8ecfcfe9 +ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff +fffffffffffffffffffffffffffffffffffffffffffffffffffff7efee94ece800 +f5ff00ffff12ffff14ffff1bffff1cffff00f7f7004343538282eafcfcf9ffffff +ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff +fffffffffffffffffffffffffffffffffffffffed5fffa38e2de00e7f606ffff0a +fffd00fffc16ffff1dffff07ffff008d8d2b61618ad5d5defffffcffffffffffff +ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff +fffffffffffffffffffffff7ffffa9e6dc00e5f208fde21fd1d1199f8a009e8700 +d7d71effff1affff00dbdd004b4a559a9ddcfaf9f6ffffffffffffffffffffffff +ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff +fffffffff8d2fcf82ed7e200fffa0ec9cc182c2c000000060000104b4d23e8eb27 +fff706fffc008b8e325e4e9dd5ddf4ffffffffffffffffffffffffffffffffffff +fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffdfdf4a7 +eedc00e8e609fff40e9396000000080b0023080046231742c1b82afff01afff608 +dde3114a2d479dabe9f8fdfeffffffffffffffffffffffffffffffffffffffffff +fffffffffffffffffffffffffffffffffffffffffffffae1fff951d5ca00ffe90d +ffff169494000000181200340b004522114ec2af0fffff1efff019ffff008b9134 +5a5a96e5d2f2ffffffffffffffffffffffffffffffffffffffffffffffffffffff +fffffffffffffffffffffffffffffdfcf7a7e9d400e9ef00ffff06ffff0fa9ab00 +0c111405004312003c3d3324cbcf0cffff22ffe816ffe300dfde10474a49bda3ea +fbf9feffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff +fffffffffffffffae3fff84ce8d200ffef0affff21ffff17e4d6004a3b120a0551 +2e1365706020e7eb00ffff13ffff1cffec0affff008c8f36404391dedef3ffffff +fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffc +fbf9a8eecb00ffd000ffeb09fff615ffed00fff200695a1112055b342a738c9624 +fcf300fff400ffff27fff017ffe300e3e10f2f304cb0b0e7fbfbfeffffffffffff +fffffffffffffffffffffffffffffffffffffffffffffffffff9e4fff747d3c700 +ffdb0bfff915ffe000ffee00fdfe0084750a362a84563389a89c0cfff900ffde00 +fff411ffee1dffc80afffd008f97365755a3e8e7fbffffffffffffffffffffffff +fffffffffffffffffffffffffffffffffffdf9f8a7e7ca00edd200fff107ffed15 +ffda00fff800fff000a79a0d1822724e4064cbbc05fff400ffe300ffe200fff625 +ffef16ffe600e4c80c2e4365aeb9f0fcf9ffffffffffffffffffffffffffffffff +fffffffffffffffffffffae7fff240d4ca00ffdc0afff818ffe500ffe800ffe000 +fff800c7bd14190655464e30eef800ffe200ffeb00ffe100ffe727ffff13ffd800 +ffe9007870364b4a86e8e8f1ffffffffffffffffffffffffffffffffffffffffff +fffffcf7f9a4e1cc00f0c800ffdb05fff213ffcb00ffe900ffe500fff000f4da07 +4c294763593dfee700ffe900ffe700ffcd00ffee0fffff1fffd708ffdc00ebd30d +4d4753a2a4d1fafafdfffffffffffffffffffffffffffffffffffffffaf0ffec56 +efcd00ffd40affe81bffe600ffe100ffcb00ffea00ffe900f9db006060247d602a +ffea00ffe900ffea00ffd400ffd300fff528fff22dffcf08ffff0072773a5655ae +ececfbfffffffffffffffffffffffffffffffffffcf9faaae7cc0affc800ffdb03 +fff611ffc900ffea00ffe100ffcc00ffe900fce600bd981cc5ad1efff400ffcf00 +ffd200ffee00ffd400ffed0cffff33ffd80fffd700d9d70b424566a2a2d6fbfafe +fffffffffffffffffffffffffffaeaffe730d4ce00ffd309ffeb1dffe400ffe500 +ffcc00ffea00ffde00ffdf00ffff00fff507ffed08ffee00ffd800ffdd00ffe900 +ffd000ffd300fff50bfff321ffd00affe000918e38595ba8eaeafbffffffffffff +fffffffffffcf9f3a3e1ad01f3c900ffdb03fff80effce00ffd900ffc700ffcd00 +ffea12ffe7179e85114a4e12504b0fc3a412fff800ffea00ffcd00ffc800ffc700 +fff100ffff2affd710ffc700edc40a4a4468a0a1d4fafafefffffffffffffffcf1 +fcdb4ad8c402ffca09ffce1fffd700ffc800ffd80effe71effd700fff707b1a509 +131606000006000017403c32d3bc10ffd500ffe500ffdd00ffc800ffd400fff729 +fff50effd400ffce006e88355761adedebfbfffffffffffff9fbc6e0d00ff6cd00 +ffd603ffec0cffc800ffcb00ffd105ffd60bffce00fff70091930000000c12153c +250e56301e64bcbb2affe600ffd300ffd200ffcb00ffc900ffd209fff923dfda0b +f9cc00dfc1072b296bbebfd4fffffffffdf7fdd172f4b005dfca00ffd000ffd500 +ffd800ffed00ffc700ffda00ffe800ffdb00ac9414040a180c052e5d40bba184b7 +e4d524ffec00ffc300ffe800ffdd00ffc900ffc800fff409f4da04fdcc00ffcd00 +6a615b5052a2f0f0fafffbf0facb39e1c603f4cb00ffcc00f4c900e0cf00f3d600 +e0cb00ffd100eed500e2c900f2dd06b3a4135f46478c776eecb937fed205ffd100 +e3cb00edd400ffd100e0cb00f2cc00ffd300e0cf00f7cd00ffce009c73341c1772 +bfc2d0fffbf4f9cb5cd7ab06d5aa00d4c500dfa100efaf00e0bf00efb000d2be00 +e4b000edbb00d4ba00edd700f0bf0df2c606ebb300d4bb00d3b300edbd00e5b100 +d2be00efb200e1c100d3ac00f1c200e3b000f4c4005b6e4d2d34709997c3fffffe +fef3dcf3c834d1c40bc09500c49b01cab501c59601ca9301c19701c69301c99601 +c19101c79a00d19e00cf9a00c7af00c1ac01c19101c99601c69401c19401cab401 +c5a501c18f01cc9701e9b6018778282a145e1d3977b79ac8fffffffffffffffce9 +bbbbac534b6c4d49654c4f664f47664c49664f47664d49664e47664e4b664e4766 +4c47664d46664e4d664e4c664f48664d47664e49664e47664e4f664d4966504966 +4d4865544f671d1d8f342d766c709defeaf3fffffffffffffffffff1f3ffc0b6ee +b4a0cd9db2cab1a1caa0b2caafa2caa2b0caada2caa4c6caaba9caa7a8caa8aaca +a9aacaa6a7caacaecaa3a5caadafcaa1a3cab0b0ca9fa0cab2b4ca9d9fcab1b3cb +9c9dd1bbbcc9f3f2f3ffffff +end +grestore +showpage +%%Trailer +%%Pages: 1 +%%EOF diff --git a/abs/core-testing/local-website/htdocs/mythtv-doc/warning.png b/abs/core-testing/local-website/htdocs/mythtv-doc/warning.png Binary files differnew file mode 100644 index 0000000..b0c668b --- /dev/null +++ b/abs/core-testing/local-website/htdocs/mythtv-doc/warning.png diff --git a/abs/core-testing/local-website/htdocs/remote/COPYING b/abs/core-testing/local-website/htdocs/remote/COPYING new file mode 100644 index 0000000..caa0a06 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/COPYING @@ -0,0 +1,341 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Library General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + <one line to give the program's name and a brief idea of what it does.> + Copyright (C) 19yy <name of author> + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) 19yy name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + <signature of Ty Coon>, 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Library General +Public License instead of this License. diff --git a/abs/core-testing/local-website/htdocs/remote/CREDITS b/abs/core-testing/local-website/htdocs/remote/CREDITS new file mode 100644 index 0000000..7d959f8 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/CREDITS @@ -0,0 +1,11 @@ +Credits +------- + +Original concept - Steven Ellis <support@openmedia.co.nz> + +Initial base php code - Mike Poublon <poublon@geeksoft.dyndns.org> + +Original remote layout, core design and coding - Steven Ellis <support@openmedia.co.nz> + +CSS based layouts and IE support - Michael Lynch <lynchmv@gmail.com> +Additional PDA Layout - Michael Lynch <lynchmv@gmail.com> diff --git a/abs/core-testing/local-website/htdocs/remote/Changelog b/abs/core-testing/local-website/htdocs/remote/Changelog new file mode 100644 index 0000000..71172d9 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/Changelog @@ -0,0 +1,131 @@ +mythtv-web-remote (0.0.17) unstable; urgency=low + + * Remove old ie_hover.htc code as we no longer need it + * Tidy up style sheet + * Add stylesheet support for additional active buttons + * Rebuild all png files to optimise for size + * Generate new active png files for remaining buttons + * Redo index.html to point at new code + * Correct selected png files in gimp due to IE transparency issues + + -- OpenMedia Support <support@openmedia.co.nz> Sun, 17 Dec 2006 16:05:46 +1300 + +mythtv-web-remote (0.0.16) unstable; urgency=low + + * Merge of IE Fixes and new layout code so that we have IE roll over buttons + * For the moment we are still using a table based layout + + -- OpenMedia Support <support@openmedia.co.nz> Sun, 17 Dec 2006 14:04:37 +1300 + +mythtv-web-remote (0.0.15) unstable; urgency=low + + * Add apache configuration file remote.conf + * Fix IE roll over support on apache - AddType text/x-component .htc + + -- OpenMedia Support <support@openmedia.co.nz> Sun, 17 Dec 2006 13:41:28 +1300 + +mythtv-web-remote (0.0.14) unstable; urgency=low + + * Change host to work for myPVR + * Fix missing support for Record button + * Create a remote-wide.html based on remote.html and layout-wide.html + + -- OpenMedia Support <support@openmedia.co.nz> Sat, 16 Dec 2006 18:59:06 +1300 + +mythtv-web-remote (0.0.13) unstable; urgency=low + + * Extra work from Mike Poublon <poublon@geeksoft.dyndns.org> + * Support image based submit buttons under IE + * Seperate GUI and PHP code + + -- OpenMedia Support <support@openmedia.co.nz> Sat, 16 Dec 2006 18:46:10 +1300 + +mythtv-web-remote (0.0.12) unstable; urgency=low + + * Makefile needs to install csshover.htc + + -- OpenMedia Support <support@openmedia.co.nz> Sat, 16 Dec 2006 18:28:18 +1300 + +mythtv-web-remote (0.0.11) unstable; urgency=low + + * Update wide layout to use new buttons + * Wide layout is still table based at this stage + * Correct some of the submit buttons on the normal layour as they were + passing the wrong value + + -- OpenMedia Support <support@openmedia.co.nz> Sat, 16 Dec 2006 18:24:54 +1300 + +mythtv-web-remote (0.0.10) unstable; urgency=low + + * Merge changes from Michael Lynch <lynchmv@gmail.com> + * Better IE support in layout.html + * Additional layout for his PDA + * Some php rework + * Add CREDITS file to track changes + + -- OpenMedia Support <support@openmedia.co.nz> Sat, 16 Dec 2006 18:04:51 +1300 + +mythtv-web-remote (0.0.9) unstable; urgency=low + + * Add in README, COPYING, Issues and Changelog files + * First release to MythTV team + + -- OpenMedia Support <support@openmedia.co.nz> Tue, 12 Dec 2006 09:19:13 +1300 + +mythtv-web-remote (0.0.8) unstable; urgency=low + + * Make sure we enable the Network Control port when installing on myPVR + + -- OpenMedia Support <support@openmedia.co.nz> Mon, 4 Dec 2006 15:23:26 +1300 + +mythtv-web-remote (0.0.7) unstable; urgency=low + + * Add wide layout + + -- OpenMedia Support <support@openmedia.co.nz> Sun, 3 Dec 2006 11:43:47 +1300 + +mythtv-web-remote (0.0.6) unstable; urgency=low + + * Load new layout into remote.php + * Issues with IE because of use if submit images + + -- OpenMedia Support <support@openmedia.co.nz> Sun, 3 Dec 2006 11:28:47 +1300 + +mythtv-web-remote (0.0.5) unstable; urgency=low + + * Add wide layout + * Try and make layouts HTML standards compliant + * Can't make CSS standards compliant due to IE hacks + * Correct permissions on installed files + + -- OpenMedia Support <support@openmedia.co.nz> Sun, 3 Dec 2006 09:56:22 +1300 + +mythtv-web-remote (0.0.4) unstable; urgency=low + + * Limited button roll over support for IE + + -- OpenMedia Support <support@openmedia.co.nz> Sun, 3 Dec 2006 09:18:51 +1300 + +mythtv-web-remote (0.0.3) unstable; urgency=low + + * Setup index.html holder + * Rename php remote file + * More tidy ups of layout file + * Add remote.css to install + + -- OpenMedia Support <support@openmedia.co.nz> Mon, 27 Nov 2006 23:05:58 +1300 + +mythtv-web-remote (0.0.2) unstable; urgency=low + + * Update layout + * Add stylesheet remote.css + * Additional images for roll over graphics + + -- OpenMedia Support <support@openmedia.co.nz> Mon, 27 Nov 2006 22:40:33 +1300 + +mythtv-web-remote (0.0.1) unstable; urgency=low + + * Initial version of the mythtv-web-remote + * This is a web based virtual remote control for MythTV + + -- OpenMedia Support <support@openmedia.co.nz> Sun, 26 Nov 2006 11:57:33 +1300 diff --git a/abs/core-testing/local-website/htdocs/remote/Issues b/abs/core-testing/local-website/htdocs/remote/Issues new file mode 100644 index 0000000..95f808f --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/Issues @@ -0,0 +1,18 @@ +MythTV Web Remote ISSUES +------------------------ + +Limited IE Support +------------------ +At present the roll overs don't work very well in IE. Also the way the icons +are mapped as submit buttons needs modification as in IE it submits the image +co-ordinates rather than the value + +Rapid Clicking can cause mythfrontend to freeze +----------------------------------------------- +Possible an issue with the telnet control interface. If a user clicks too +rapidly it can cause the front end to lock up, requiring a restart of the GUI. + +Roll Over images required for remaining buttons +----------------------------------------------- +At present only the number and text buttons have rollover and click alternate +images diff --git a/abs/core-testing/local-website/htdocs/remote/README b/abs/core-testing/local-website/htdocs/remote/README new file mode 100644 index 0000000..ecc4797 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/README @@ -0,0 +1,43 @@ +MythWeb Remote - Version 0.0.9 +-------------- + +This has been designed to improve MythTV access for people with certain forms +of disability. It has two web based interfaces that are based on the Hauppauge +MCE Remote control with its additional fast access hotkeys. + +For more details on how the hotkeys are mapped see + http://openmedia.co.nz/openmedia/content/view/27/58/ + +All html/php/css code is released under GPL V2, and all images under +Creative Commons (http://web.resource.org/cc/PublicDomain) as they are based on +the Etiquette Icons by Andy Fitzsimon, see - + http://openclipart.org/clipart/computer/buttons/b_down.txt + + +Installing +---------- +In order to use this install as a directory called "remote" under your web +document root. You should then be able to access it as + http://mythtv/remote +You will also need to enable the Network Control port for the MythTV frontend +for the controls to work. + + +See COPYING for details on the GPL V2 license. + +See ISSUES for outstanding problems + +See Changelog for recent changes + +GPL 2.0 Components +------------------ +Original php code (c) 2006 Mike Poublon <poublon@geeksoft.dyndns.org> +Enhancements (c) 2006 Steven Ellis <support@openmedia.co.nz> +CSS (c) 2006 Steven Ellis <support@openmedia.co.nz> +Remote Layouts (c) 2006 Steven Ellis <support@openmedia.co.nz> + +Creative Commons +---------------- +Original image design (c) Andy Fitzsimon +Final buttom images (c) 2006 Steven Ellis <support@openmedia.co.nz> + diff --git a/abs/core-testing/local-website/htdocs/remote/backend.php b/abs/core-testing/local-website/htdocs/remote/backend.php new file mode 100644 index 0000000..530d220 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/backend.php @@ -0,0 +1,168 @@ +<? +# +# Original code (c) 2006 Mike Poublon <poublon@geeksoft.dyndns.org> +# +# Enhancements (c) 2006 Steven Ellis <support@openmedia.co.nz> and +# (c) 2006 Mike Poublon <poublon@geeksoft.dyndns.org> +# + +#change the line below that has localhost pointing to the address of your frontend. +$HOSTNAME = "localhost"; + +$submit = $_POST['submit']; + +#workaround for IE's image button wierdness +if ( $submit == "" ) +{ + $submit = $_POST['buttonvalue']; +} + +#if we aren't being posted to, then don't do anything useful +if ( $submit == "" ) +{ + echo "Sorry, this file is meant to be called by one of the frontend "; + echo "pages, please try using one of them instead."; + exit(); +} + +# We set jump when we want to perform more complex commands +$jump=""; + +if ($submit == "Power"){ + #Power - not really used yet + $key = ""; +} else if ($submit == "TV"){ + $jump = "livetv"; +} else if ($submit == "Music"){ + $jump = "playmusic"; +} else if ($submit == "Video"){ + $jump = "mythvideo"; +} else if ($submit == "Recordings"){ + $jump = "playbackrecordings"; +} else if ($submit == "Guide"){ + $jump = "programguide"; +} else if ($submit == "Pictures"){ + $jump = "mythgallery"; +} else if ($submit == "Back") { + $key = "escape"; +} else if ($submit == "Info") { + $key = "i"; +} else if ($submit == "Menu") { + #Menu + $key = "m"; +} else if ($submit == "U") { + $key = "up"; +} else if ($submit == "L") { + $key = "left"; +} else if ($submit == "D") { + $key = "down"; +} else if ($submit == "R") { + $key = "right"; +} else if ($submit == "OK") { + $key = "enter"; +} else if ($submit == "Page Up") { + $key = "pageup"; +} else if ($submit == "Page Dn") { + $key = "pagedown"; +} else if ($submit == "Vol Up") { + $key = "bracketright"; +} else if ($submit == "Vol Dn") { + $key = "bracketleft"; +} else if ($submit == "Mute") { + $key = "f9"; +} else if ($submit == "Pause") { + $key = "p"; +} else if ($submit == "Stop") { + $key = "s"; +} else if ($submit == "Play") { + $key = "p"; +} else if ($submit == "Rec") { + $key = "r"; +} else if ($submit == "<<") { + $key = "left"; +} else if ($submit == ">>") { + $key = "right"; +} else if ($submit == "|<") { + #skip commercial back + $key = "q"; +} else if ($submit == ">|") { + #skip commercial + $key = "z"; +# Special keys used by myPVR +} else if ($submit == "#") { + # Change tuner + $key = "y"; +} else if ($submit == "*") { + #skip commercial + $key = "z"; +} else if ($submit == "0" || + $submit == "1" || + $submit == "2" || + $submit == "3" || + $submit == "4" || + $submit == "5" || + $submit == "6" || + $submit == "7" || + $submit == "8" || + $submit == "9" ) { + $key = $submit; +} + +#set the maximum time to execute the page +set_time_limit (5); + +#open the socket to the frontend +$fp = fsockopen($HOSTNAME, 6546, $errno, $errstr, 30); + +if (!$fp) { + #couldn't connect, print the error + echo "ERROR: $errstr ($errno)<br />\n"; + exit(); +} else { + #set up a place for the banner to get read into + $banner = ""; + + #read through the banner, one char at a time and append + #to the banner string until we see a '#' + $c = fgetc($fp); + while ($c !== false && $c != "#") + { + $banner .= $c; + $c = fgetc($fp); + } + if ($c !== false) + { + #if the connection is still valid then read + #in the extra space after the # + $c = fgetc($fp); + } + + #create the command to issue to the frontend based + #on what the user clicked on + if ($jump != "") { + $cmd = "jump $jump\x0d\x0a"; + $jump=""; + } else { + $cmd = "key $key\x0d\x0a"; + } + + #write the command to the socket + fwrite($fp,$cmd); + + #close the socket + fclose($fp); + + #get the specified page to redirect to + $redirectpage = $_POST['redirectpage']; + if ( $redirectpage == "" ) + { + #use the refering page if all else fails + $redirectpage = getenv('HTTP_REFERER'); + } + + #redirect to the desired location + header( "Location: $redirectpage" ); +} + +?> + diff --git a/abs/core-testing/local-website/htdocs/remote/csshover.htc b/abs/core-testing/local-website/htdocs/remote/csshover.htc new file mode 100644 index 0000000..f6e8f3c --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/csshover.htc @@ -0,0 +1,120 @@ +<attach event="ondocumentready" handler="parseStylesheets" /> +<script> +/** + * Whatever:hover - V1.42.060206 - hover & active + * ------------------------------------------------------------ + * (c) 2005 - Peter Nederlof + * Peterned - http://www.xs4all.nl/~peterned/ + * License - http://creativecommons.org/licenses/LGPL/2.1/ + * + * Whatever:hover is free software; you can redistribute it and/or + * modify it under the terms of the GNU Lesser General Public + * License as published by the Free Software Foundation; either + * version 2.1 of the License, or (at your option) any later version. + * + * Whatever:hover is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + * Lesser General Public License for more details. + * + * Credits and thanks to: + * Arnoud Berendsen, Martin Reurings, Robert Hanson + * + * howto: body { behavior:url("csshover.htc"); } + * ------------------------------------------------------------ + */ + +var csshoverReg = /(^|\s)(([^a]([^ ]+)?)|(a([^#.][^ ]+)+)):(hover|active)/i, +currentSheet, doc = window.document, hoverEvents = [], activators = { + onhover:{on:'onmouseover', off:'onmouseout'}, + onactive:{on:'onmousedown', off:'onmouseup'} +} + +function parseStylesheets() { + if(!/MSIE (5|6)/.test(navigator.userAgent)) return; + window.attachEvent('onunload', unhookHoverEvents); + var sheets = doc.styleSheets, l = sheets.length; + for(var i=0; i<l; i++) + parseStylesheet(sheets[i]); +} + function parseStylesheet(sheet) { + if(sheet.imports) { + try { + var imports = sheet.imports, l = imports.length; + for(var i=0; i<l; i++) parseStylesheet(sheet.imports[i]); + } catch(securityException){} + } + + try { + var rules = (currentSheet = sheet).rules, l = rules.length; + for(var j=0; j<l; j++) parseCSSRule(rules[j]); + } catch(securityException){} + } + + function parseCSSRule(rule) { + var select = rule.selectorText, style = rule.style.cssText; + if(!csshoverReg.test(select) || !style) return; + + var pseudo = select.replace(/[^:]+:([a-z-]+).*/i, 'on$1'); + var newSelect = select.replace(/(\.([a-z0-9_-]+):[a-z]+)|(:[a-z]+)/gi, '.$2' + pseudo); + var className = (/\.([a-z0-9_-]*on(hover|active))/i).exec(newSelect)[1]; + var affected = select.replace(/:(hover|active).*$/, ''); + var elements = getElementsBySelect(affected); + if(elements.length == 0) return; + + currentSheet.addRule(newSelect, style); + for(var i=0; i<elements.length; i++) + new HoverElement(elements[i], className, activators[pseudo]); + } + +function HoverElement(node, className, events) { + if(!node.hovers) node.hovers = {}; + if(node.hovers[className]) return; + node.hovers[className] = true; + hookHoverEvent(node, events.on, function() { node.className += ' ' + className; }); + hookHoverEvent(node, events.off, function() { node.className = node.className.replace(new RegExp('\\s+'+className, 'g'),''); }); +} + function hookHoverEvent(node, type, handler) { + node.attachEvent(type, handler); + hoverEvents[hoverEvents.length] = { + node:node, type:type, handler:handler + }; + } + + function unhookHoverEvents() { + for(var e,i=0; i<hoverEvents.length; i++) { + e = hoverEvents[i]; + e.node.detachEvent(e.type, e.handler); + } + } + +function getElementsBySelect(rule) { + var parts, nodes = [doc]; + parts = rule.split(' '); + for(var i=0; i<parts.length; i++) { + nodes = getSelectedNodes(parts[i], nodes); + } return nodes; +} + function getSelectedNodes(select, elements) { + var result, node, nodes = []; + var identify = (/\#([a-z0-9_-]+)/i).exec(select); + if(identify) { + var element = doc.getElementById(identify[1]); + return element? [element]:nodes; + } + + var classname = (/\.([a-z0-9_-]+)/i).exec(select); + var tagName = select.replace(/(\.|\#|\:)[a-z0-9_-]+/i, ''); + var classReg = classname? new RegExp('\\b' + classname[1] + '\\b'):false; + for(var i=0; i<elements.length; i++) { + result = tagName? elements[i].all.tags(tagName):elements[i].all; + for(var j=0; j<result.length; j++) { + node = result[j]; + if(classReg && !classReg.test(node.className)) continue; + nodes[nodes.length] = node; + } + } + + return nodes; + } +</script> diff --git a/abs/core-testing/local-website/htdocs/remote/images/blank.gif b/abs/core-testing/local-website/htdocs/remote/images/blank.gif Binary files differnew file mode 100644 index 0000000..35d42e8 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/blank.gif diff --git a/abs/core-testing/local-website/htdocs/remote/images/button_30.png b/abs/core-testing/local-website/htdocs/remote/images/button_30.png Binary files differnew file mode 100644 index 0000000..198b062 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/button_30.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/button_30g.png b/abs/core-testing/local-website/htdocs/remote/images/button_30g.png Binary files differnew file mode 100644 index 0000000..19166b2 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/button_30g.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/button_30r.png b/abs/core-testing/local-website/htdocs/remote/images/button_30r.png Binary files differnew file mode 100644 index 0000000..3411381 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/button_30r.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/button_text.png b/abs/core-testing/local-website/htdocs/remote/images/button_text.png Binary files differnew file mode 100644 index 0000000..2976a2d --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/button_text.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/button_textg.png b/abs/core-testing/local-website/htdocs/remote/images/button_textg.png Binary files differnew file mode 100644 index 0000000..6f2146c --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/button_textg.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/button_textr.png b/abs/core-testing/local-website/htdocs/remote/images/button_textr.png Binary files differnew file mode 100644 index 0000000..02b5738 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/button_textr.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/down.png b/abs/core-testing/local-website/htdocs/remote/images/down.png Binary files differnew file mode 100644 index 0000000..335f28c --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/down.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/down_g.png b/abs/core-testing/local-website/htdocs/remote/images/down_g.png Binary files differnew file mode 100644 index 0000000..5d31913 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/down_g.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/down_r.png b/abs/core-testing/local-website/htdocs/remote/images/down_r.png Binary files differnew file mode 100644 index 0000000..00cde0b --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/down_r.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/fast_forward.png b/abs/core-testing/local-website/htdocs/remote/images/fast_forward.png Binary files differnew file mode 100644 index 0000000..6563f92 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/fast_forward.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/fast_forward_g.png b/abs/core-testing/local-website/htdocs/remote/images/fast_forward_g.png Binary files differnew file mode 100644 index 0000000..f608095 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/fast_forward_g.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/fast_forward_r.png b/abs/core-testing/local-website/htdocs/remote/images/fast_forward_r.png Binary files differnew file mode 100644 index 0000000..9c71739 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/fast_forward_r.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/fast_rewind.png b/abs/core-testing/local-website/htdocs/remote/images/fast_rewind.png Binary files differnew file mode 100644 index 0000000..6daf86c --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/fast_rewind.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/fast_rewind_g.png b/abs/core-testing/local-website/htdocs/remote/images/fast_rewind_g.png Binary files differnew file mode 100644 index 0000000..a7ba769 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/fast_rewind_g.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/fast_rewind_r.png b/abs/core-testing/local-website/htdocs/remote/images/fast_rewind_r.png Binary files differnew file mode 100644 index 0000000..f8c1151 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/fast_rewind_r.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/left.png b/abs/core-testing/local-website/htdocs/remote/images/left.png Binary files differnew file mode 100644 index 0000000..c9c4b72 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/left.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/left_g.png b/abs/core-testing/local-website/htdocs/remote/images/left_g.png Binary files differnew file mode 100644 index 0000000..5e93269 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/left_g.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/left_r.png b/abs/core-testing/local-website/htdocs/remote/images/left_r.png Binary files differnew file mode 100644 index 0000000..960ed9e --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/left_r.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/ok.png b/abs/core-testing/local-website/htdocs/remote/images/ok.png Binary files differnew file mode 100644 index 0000000..269099c --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/ok.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/ok_g.png b/abs/core-testing/local-website/htdocs/remote/images/ok_g.png Binary files differnew file mode 100644 index 0000000..73a0931 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/ok_g.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/ok_r.png b/abs/core-testing/local-website/htdocs/remote/images/ok_r.png Binary files differnew file mode 100644 index 0000000..8b5473f --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/ok_r.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/pause.png b/abs/core-testing/local-website/htdocs/remote/images/pause.png Binary files differnew file mode 100644 index 0000000..12a1e0e --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/pause.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/pause_g.png b/abs/core-testing/local-website/htdocs/remote/images/pause_g.png Binary files differnew file mode 100644 index 0000000..720798c --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/pause_g.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/pause_r.png b/abs/core-testing/local-website/htdocs/remote/images/pause_r.png Binary files differnew file mode 100644 index 0000000..df9d032 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/pause_r.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/rec.png b/abs/core-testing/local-website/htdocs/remote/images/rec.png Binary files differnew file mode 100644 index 0000000..8dddf07 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/rec.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/rec_g.png b/abs/core-testing/local-website/htdocs/remote/images/rec_g.png Binary files differnew file mode 100644 index 0000000..1f29994 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/rec_g.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/rec_r.png b/abs/core-testing/local-website/htdocs/remote/images/rec_r.png Binary files differnew file mode 100644 index 0000000..8263119 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/rec_r.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/right.png b/abs/core-testing/local-website/htdocs/remote/images/right.png Binary files differnew file mode 100644 index 0000000..3c94d77 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/right.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/right_g.png b/abs/core-testing/local-website/htdocs/remote/images/right_g.png Binary files differnew file mode 100644 index 0000000..3b48fd0 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/right_g.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/right_r.png b/abs/core-testing/local-website/htdocs/remote/images/right_r.png Binary files differnew file mode 100644 index 0000000..707bccb --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/right_r.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/skip_back.png b/abs/core-testing/local-website/htdocs/remote/images/skip_back.png Binary files differnew file mode 100644 index 0000000..4708f76 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/skip_back.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/skip_back_g.png b/abs/core-testing/local-website/htdocs/remote/images/skip_back_g.png Binary files differnew file mode 100644 index 0000000..d5654e7 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/skip_back_g.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/skip_back_r.png b/abs/core-testing/local-website/htdocs/remote/images/skip_back_r.png Binary files differnew file mode 100644 index 0000000..52554b3 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/skip_back_r.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/skip_forward.png b/abs/core-testing/local-website/htdocs/remote/images/skip_forward.png Binary files differnew file mode 100644 index 0000000..4103f16 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/skip_forward.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/skip_forward_g.png b/abs/core-testing/local-website/htdocs/remote/images/skip_forward_g.png Binary files differnew file mode 100644 index 0000000..af37f40 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/skip_forward_g.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/skip_forward_r.png b/abs/core-testing/local-website/htdocs/remote/images/skip_forward_r.png Binary files differnew file mode 100644 index 0000000..bd464ac --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/skip_forward_r.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/stop.png b/abs/core-testing/local-website/htdocs/remote/images/stop.png Binary files differnew file mode 100644 index 0000000..0b10429 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/stop.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/stop_g.png b/abs/core-testing/local-website/htdocs/remote/images/stop_g.png Binary files differnew file mode 100644 index 0000000..9f317f7 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/stop_g.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/stop_r.png b/abs/core-testing/local-website/htdocs/remote/images/stop_r.png Binary files differnew file mode 100644 index 0000000..e53f0f4 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/stop_r.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/up.png b/abs/core-testing/local-website/htdocs/remote/images/up.png Binary files differnew file mode 100644 index 0000000..42f5d67 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/up.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/up_g.png b/abs/core-testing/local-website/htdocs/remote/images/up_g.png Binary files differnew file mode 100644 index 0000000..d944b71 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/up_g.png diff --git a/abs/core-testing/local-website/htdocs/remote/images/up_r.png b/abs/core-testing/local-website/htdocs/remote/images/up_r.png Binary files differnew file mode 100644 index 0000000..f8a7d16 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/images/up_r.png diff --git a/abs/core-testing/local-website/htdocs/remote/inc/process.php b/abs/core-testing/local-website/htdocs/remote/inc/process.php new file mode 100644 index 0000000..b71719b --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/inc/process.php @@ -0,0 +1,131 @@ +<?php +# +# Original code (c) 2006 Mike Poublon <poublon@geeksoft.dyndns.org> +# +# Enhancements (c) 2006 Steven Ellis <support@openmedia.co.nz> +# +#change the line below that has tv.local to the address of your frontend. + +#echo time() . "<br>"; +if(isset($_POST['submit'])){ + $submit = $_POST['submit']; + #echo "form submitted = $submit<br>"; + + # We set jump when we want to perform more complex commands + $jump=""; + + if ($submit == "Power"){ + #Power - not really used yet + $key = ""; + } else if ($submit == "TV"){ + $jump = "livetv"; + } else if ($submit == "Music"){ + $jump = "playmusic"; + } else if ($submit == "Video" || $submit == "Videos"){ + $jump = "mythvideo"; + } else if ($submit == "Recordings" || $submit == "Recorded"){ + $jump = "playbackrecordings"; + } else if ($submit == "Guide"){ + $jump = "programguide"; + } else if ($submit == "Pictures"){ + $jump = "mythgallery"; + } else if ($submit == "Back" || $submit == "Clear") { + $key = "escape"; + } else if ($submit == "Info") { + $key = "i"; + } else if ($submit == "Menu") { + #Menu + $key = "m"; + } else if ($submit == "U" || $submit == "^") { + $key = "up"; + } else if ($submit == "L" || $submit == "<") { + $key = "left"; + } else if ($submit == "D" || $submit == "v") { + $key = "down"; + } else if ($submit == "R" || $submit == ">") { + $key = "right"; + } else if ($submit == "OK" || $submit == "Enter") { + $key = "enter"; + } else if ($submit == "Page Up" || $submit == "Chan Up") { + $key = "pageup"; + } else if ($submit == "Page Dn" || $submit == "Chan Dn") { + $key = "pagedown"; + } else if ($submit == "Vol Up") { + $key = "bracketright"; + } else if ($submit == "Vol Dn") { + $key = "bracketleft"; + } else if ($submit == "Mute") { + $key = "f9"; + } else if ($submit == "Pause") { + $key = "p"; + } else if ($submit == "Stop") { + $key = "s"; + } else if ($submit == "Rec") { + $key = "r"; + } else if ($submit == "Play") { + $key = "p"; + } else if ($submit == "<<") { + $key = "left"; + } else if ($submit == ">>") { + $key = "right"; + } else if ($submit == "|<") { + #skip commercial back + $key = "q"; + } else if ($submit == ">|") { + #skip commercial + $key = "z"; + # Special keys used by myPVR + } else if ($submit == "#") { + # Change tuner + $key = "y"; + } else if ($submit == "*") { + #skip commercial + $key = "z"; + } else if ($submit == "0" || + $submit == "1" || + $submit == "2" || + $submit == "3" || + $submit == "4" || + $submit == "5" || + $submit == "6" || + $submit == "7" || + $submit == "8" || + $submit == "9" ) { + $key = $submit; + } + + set_time_limit (5); + # change tv.local to the hostname/address of your frontend + $fp = fsockopen("localhost", 6546, $errno, $errstr, 30); + if (!$fp) { + $error = "ERROR: $errstr ($errno)"; + } else { + #stream_set_timeout ( $fp, 0, 100000); + #$banner = stream_get_contents($fp); + + $banner = ""; + + $c = fgetc($fp); + while ($c !== false && $c != "#") { + #echo "c = $c<br>\n"; + $banner .= $c; + $c = fgetc($fp); + } + if ($c !== false) { + $c = fgetc($fp); #Read in the extra space after the # + } + + if ($jump != "") { + $cmd = "jump $jump\x0d\x0a"; + $jump=""; + } else { + $cmd = "key $key\x0d\x0a"; + } + fwrite($fp,$cmd); + $res = fgets($fp); + #echo "result = $res<br>\n"; + + fclose($fp); + } +} +?> diff --git a/abs/core-testing/local-website/htdocs/remote/index.html b/abs/core-testing/local-website/htdocs/remote/index.html new file mode 100644 index 0000000..35ff9e7 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/index.html @@ -0,0 +1,19 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + +<head> + <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type" /> + + + <title>MythWeb Remote</title> + +</head> + +<body> +Please click through for the <a href="remote.html">vertical remote control</a>.<br /><br /> +Or click through for the <a href="remote-wide.html">horizontal remote control</a>.<br /> +<br /> +There is now an initial <a href="pda.php">PDA</a> version of the layout<br /> +</body> + +</html> diff --git a/abs/core-testing/local-website/htdocs/remote/layout-wide.html b/abs/core-testing/local-website/htdocs/remote/layout-wide.html new file mode 100644 index 0000000..d534199 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/layout-wide.html @@ -0,0 +1,250 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + + <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" /> + <title>Wide Remote Control</title> + + + <link href="remote.css" media="screen" type="text/css" rel="stylesheet" /> + +</head> + + +<body> + +<table style="" align="left" border="0" cellspacing="0" width="300"> + + <tbody> + + <tr> + + <td valign="top"> + <table border="0" cellspacing="0"> + + <tbody> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + + </tr> + + <tr align="center"> + + <td><input name="submit" class="txt" value="TV" type="submit" /></td> + + <td><input name="submit" class="txt" value="Music" type="submit" /></td> + + <td><input name="submit" class="txt" value="Video" type="submit" /></td> + + <td><input name="submit" class="txt" value="Recordings" type="submit" /></td> + + <td><input name="submit" class="txt" value="Guide" type="submit" /></td> + + <td><input name="submit" class="txt" value="Pictures" type="submit" /></td> + + </tr> + + <tr style="height: 8px;" align="center"> + + <td> + </td> + </tr> + + <tr> + + <td colspan="3" align="center"> + <table style="width: 70%;" border="0" cellspacing="0"> + + <tbody> + + <tr align="center"> + + <td> </td> + + <td><input type="image" name="submit" class="record" alt="Record" value="Rec" src="images/blank.gif" /> </td> + <td><input type="image" name="submit" class="stop" alt="Stop" value="Stop" src="images/blank.gif" /> </td> + <td><input type="image" name="submit" class="pause" alt="Pause" value="Pause" src="images/blank.gif" /> </td> + + <td> </td> + + </tr> + + <tr> + + <td><input type="image" name="submit" class="rewind" alt="Rewind" value="<<" src="images/blank.gif" /> </td> + + <td> </td> + + <td><input type="image" name="submit" class="play" alt="Play" value="Play" src="images/blank.gif" /> </td> + + <td> </td> + + <td><input type="image" name="submit" class="ffwd" alt="Fast Forward" value=">>" src="images/blank.gif" /> </td> + + </tr> + + <tr> + + <td> </td> + + <td><input type="image" name="submit" class="sback" alt="Skip Back" value="|<" src="images/blank.gif" /> </td> + + <td> </td> + + <td><input type="image" name="submit" class="sfwd" alt="Skip Forward" value="|>" src="images/blank.gif" /> </td> + + <td> </td> + + </tr> + + </tbody> + </table> + + </td> + + <td colspan="3" align="center"> + <table border="0" cellspacing="0" width="60%"> + + <tbody> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="1" type="submit" /></td> + + <td><input name="submit" class="number" value="2" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="3" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="4" type="submit" /></td> + + <td><input name="submit" class="number" value="5" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="6" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="7" type="submit" /></td> + + <td><input name="submit" class="number" value="8" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="9" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="*" type="submit" /></td> + + <td><input name="submit" class="number" value="0" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="#" type="submit" /></td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + + </tr> + + <tr align="center"> + + <td><input name="submit" class="txt" value="Back" type="submit" /></td> + + <td><input name="submit" class="txt" value="Info" type="submit" /></td> + + <td><input name="submit" class="txt" value="Menu" type="submit" /></td> + + <td><input name="submit" class="txt" value="Mute" type="submit" /></td> + + <td><input name="submit" class="txt" value="Clear" type="submit" /></td> + + <td><input name="submit" class="txt" value="Enter" type="submit" /></td> + + </tr> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + </tr> + + <tr> + + <td colspan="6" align="center"> + <table border="0" cellspacing="0" width="50%"> + + <tbody> + + <tr> + + <td><input name="submit" class="txt" value="Vol Up" type="submit" /></td> + + <td> </td> + + <td><input type="image" name="submit" class="navup" alt="Up" value="U" src="images/blank.gif" /> </td> + + <td> </td> + + <td><input name="submit" class="txt" value="Page Up" type="submit" /></td> + + </tr> + + <tr> + + <td> </td> + + <td><input type="image" name="submit" class="navleft" alt="Left" value="L" src="images/blank.gif" /> </td> + + <td><input type="image" name="submit" class="navok" alt="Ok" value="Ok" src="images/blank.gif" /> </td> + + <td><input type="image" name="submit" class="navright" alt="Right" value="R" src="images/blank.gif" /> </td> + + <td> </td> + + </tr> + + <tr> + + <td><input name="submit" class="txt" value="Vol Dn" type="submit" /></td> + + <td> </td> + + <td <input type="image" name="submit" class="navdown" alt="Down" value="D" src="images/blank.gif" /> </td> + + <td> </td> + + <td><input name="submit" class="txt" value="Page Dn" type="submit" /></td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + </tbody> +</table> + +</body> +</html> diff --git a/abs/core-testing/local-website/htdocs/remote/layout.html b/abs/core-testing/local-website/htdocs/remote/layout.html new file mode 100644 index 0000000..7e44ade --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/layout.html @@ -0,0 +1,269 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> + + <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type" /> + <title>Remote Control</title> + + + <link rel="stylesheet" type="text/css" media="screen" href="remote.css" /> + +</head> + + +<body> + +<div id="narrow"> + + <!-- BEGIN ERROR CHECK --> + <?php + if(isset($error)){ + ?> + <div id="subwide"> + <?php echo $error; unset($error); ?> + </div> + <?php + } + ?> + <!-- END ERROR CHECK --> + + <!-- BEGIN TOP ROW --> + <div id="subwide"> + <div id="thirds"> + <input type="submit" class="txt" name="submit" value="TV" /> + </div> + <div id="thirds"> + <input type="submit" class="txt" name="submit" value="Music" /> + </div> + <div id="thirds"> + <input type="submit" class="txt" name="submit" value="Videos" /> + </div> + </div> + <!-- END TOP ROW --> + + <!-- BEGIN 2ND ROW --> + <div id="subwide"> + <div id="thirds"> + <input type="submit" class="txt" name="submit" value="Recordings" /> + </div> + <div id="thirds"> + <input type="submit" class="txt" name="submit" value="Guide" /> + </div> + <div id="thirds"> + <input type="submit" class="txt" name="submit" value="Pictures" /> + </div> + </div> + <!-- END 2ND ROW --> + + <!-- BEGIN PLAY CONTROLS --> + <div id="subround"> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="record" alt="Record" value="Rec" src="images/blank.gif" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="stop" alt="Stop" value="Stop" src="images/blank.gif" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="pause" alt="Pause" value="Pause" src="images/blank.gif" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + </div> + <div id="subround"> + <div id="fifths"> + <input type="image" name="submit" class="rewind" alt="Rewind" value="<<" src="images/blank.gif" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="play" alt="Play" value="Play" src="images/blank.gif" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="ffwd" alt="Fast Forward" value=">>" src="images/blank.gif" /> + </div> + </div> + <div id="subround"> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="sback" alt="Skip Back" value="|<" src="images/blank.gif" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="sfwd" alt="Skip Forward" value="|>" src="images/blank.gif" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + </div> + <!-- END PLAY CONTROLS --> + + <!-- BEGIN MUTE ROW --> + <div id="subwide"> + <div id="thirds"> + <input type="submit" class="notxt" name="submit" value="RESERVED" /> + </div> + <div id="thirds"> + <input type="submit" class="txt" name="submit" value="Mute" /> + </div> + <div id="thirds"> + <input type="submit" class="notxt" name="submit" value="RESERVED" /> + </div> + </div> + <!-- END MUTE ROW --> + + <!-- BEGIN GENERAL ROW --> + <div id="subwide"> + <div id="thirds"> + <input type="submit" class="txt" name="submit" value="Back" /> + </div> + <div id="thirds"> + <input type="submit" class="txt" name="submit" value="Info" /> + </div> + <div id="thirds"> + <input type="submit" class="txt" name="submit" value="Menu" /> + </div> + </div> + <!-- END GENERAL ROW --> + + <!-- BEGIN NAV SECTION --> + <div id="subround"> + <div id="thirds"> + <input type="submit" class="txt" name="submit" value="Vol Up" /> + </div> + <div id="thirds"> + <input type="image" name="submit" class="navup" alt="Up" value="Up" src="images/blank.gif" /> + </div> + <div id="thirds"> + <input type="submit" class="txt" name="submit" value="Page Up" /> + </div> + </div> + <div id="subround"> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="navleft" alt="Left" value="L" src="images/blank.gif" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="navok" alt="Ok" value="Ok" src="images/blank.gif" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="navright" alt="Right" value="R" src="images/blank.gif" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + </div> + <div id="subround"> + <div id="thirds"> + <input type="submit" class="txt" name="submit" value="Vol Dn" /> + </div> + <div id="thirds"> + <input type="image" name="submit" class="navdown" alt="Down" value="D" src="images/blank.gif" /> + </div> + <div id="thirds"> + <input type="submit" class="txt" name="submit" value="Page Dn" /> + </div> + </div> + <!-- END NAV SECTION --> + + <!-- BEGIN NUMBERS --> + <div id="subround"> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + <div id="fifths"> + <input name="submit" class="number" value="1" type="submit" /> + </div> + <div id="fifths"> + <input name="submit" class="number" value="2" type="submit" /> + </div> + <div id="fifths"> + <input name="submit" class="number" value="3" type="submit" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + </div> + <div id="subround"> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + <div id="fifths"> + <input name="submit" class="number" value="4" type="submit" /> + </div> + <div id="fifths"> + <input name="submit" class="number" value="5" type="submit" /> + </div> + <div id="fifths"> + <input name="submit" class="number" value="6" type="submit" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + </div> + <div id="subround"> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + <div id="fifths"> + <input name="submit" class="number" value="7" type="submit" /> + </div> + <div id="fifths"> + <input name="submit" class="number" value="8" type="submit" /> + </div> + <div id="fifths"> + <input name="submit" class="number" value="9" type="submit" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + </div> + <div id="subround"> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + <div id="fifths"> + <input name="submit" class="number" value="*" type="submit" /> + </div> + <div id="fifths"> + <input name="submit" class="number" value="0" type="submit" /> + </div> + <div id="fifths"> + <input name="submit" class="number" value="#" type="submit" /> + </div> + <div id="fifths"> + <input type="image" name="submit" class="noimage" /> + </div> + </div> + <!-- END NUMBERS --> + + <!-- BEGIN LAST ROW --> + <div id="subwide"> + <div id="thirds"> + <input name="submit" class="halfleft" value="Clear" type="submit" /> + </div> + <div id="thirds"> + <input type="image" name="submit" class="noimage" /> + </div> + <div id="thirds"> + <input name="submit" class="halfright" value="Enter" type="submit" /> + </div> + </div> + <!-- END LAST ROW --> +</div> + +</body> +</html> diff --git a/abs/core-testing/local-website/htdocs/remote/nav.php b/abs/core-testing/local-website/htdocs/remote/nav.php new file mode 100644 index 0000000..916bfa2 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/nav.php @@ -0,0 +1,57 @@ +<?php +include "inc/process.php"; +?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> +<title>MythTV Web Remote</title> +<link rel="stylesheet" type="text/css" media="screen" href="remote.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> +</head> + +<body class="mypda"> +<form method="post"> + +<div> + <div class="tabArea"> + <a class="tab" href="pda.php">Main</a> + <a class="tab activeTab" href="nav.php">Nav</a> + <a class="tab" href="num.php">Digits</a> + </div> + <div class="tabMain"> + <div id="subpda"> + <input type="submit" class="tiny" name="submit" value="Vol Up" /> + <input type="submit" class="tiny" name="submit" value="^" /> + <input type="submit" class="tiny" name="submit" value="Chan Up" /> + </div> + + <div id="subpda"> + <input type="submit" class="tiny" name="submit" value="<" /> + <input type="submit" class="tiny" name="submit" value="OK" /> + <input type="submit" class="tiny" name="submit" value=">" /> + </div> + + <div id="subpda"> + <input type="submit" class="tiny" name="submit" value="Vol Dn" /> + <input type="submit" class="tiny" name="submit" value="v" /> + <input type="submit" class="tiny" name="submit" value="Chan DN" /> + </div> + + <div id="subpda"> + <input type="submit" class="tiny" name="submit" value="Rec" /> + <input type="submit" class="tiny" name="submit" value="Stop" /> + <input type="submit" class="tiny" name="submit" value="Pause" /> + </div> + + <div id="subpda"> + <input type="submit" class="tiny" name="submit" value="<<" /> + <input type="submit" class="tiny" name="submit" value="Play" /> + <input type="submit" class="tiny" name="submit" value=">>" /> + </div> + + </div> +</div> + +</form> +</body> +</html> diff --git a/abs/core-testing/local-website/htdocs/remote/num.php b/abs/core-testing/local-website/htdocs/remote/num.php new file mode 100644 index 0000000..1665947 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/num.php @@ -0,0 +1,57 @@ +<?php +include "inc/process.php"; +?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> +<title>MythTV Web Remote</title> +<link rel="stylesheet" type="text/css" media="screen" href="remote.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> +</head> + +<body class="mypda"> +<form method="post"> + +<div> + <div class="tabArea"> + <a class="tab" href="pda.php">Main</a> + <a class="tab" href="nav.php">Nav</a> + <a class="tab activeTab" href="num.php">Digits</a> + </div> + <div class="tabMain"> + <div id="subpda"> + <input type="submit" class="tiny" name="submit" value="1" /> + <input type="submit" class="tiny" name="submit" value="2" /> + <input type="submit" class="tiny" name="submit" value="3" /> + </div> + + <div id="subpda"> + <input type="submit" class="tiny" name="submit" value="4" /> + <input type="submit" class="tiny" name="submit" value="5" /> + <input type="submit" class="tiny" name="submit" value="6" /> + </div> + + <div id="subpda"> + <input type="submit" class="tiny" name="submit" value="7" /> + <input type="submit" class="tiny" name="submit" value="8" /> + <input type="submit" class="tiny" name="submit" value="9" /> + </div> + + <div id="subpda"> + <input type="submit" class="tiny" name="submit" value="*" /> + <input type="submit" class="tiny" name="submit" value="0" /> + <input type="submit" class="tiny" name="submit" value="#" /> + </div> + + <div id="subpda"> + <input type="submit" class="tiny" name="submit" value="Clear" /> + <input type="submit" class="tiny" name="submit" value="Mute" /> + <input type="submit" class="tiny" name="submit" value="Enter" /> + </div> + + </div> +</div> + +</form> +</body> +</html> diff --git a/abs/core-testing/local-website/htdocs/remote/pda.php b/abs/core-testing/local-website/htdocs/remote/pda.php new file mode 100644 index 0000000..888c966 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/pda.php @@ -0,0 +1,39 @@ +<?php +include "inc/process.php"; +?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> +<title>MythTV Web Remote</title> +<link rel="stylesheet" type="text/css" media="screen" href="remote.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> +</head> + +<body class="mypda"> +<form method="post"> + +<div> + <div class="tabArea"> + <a class="tab activeTab" href="pda.php">Main</a> + <a class="tab" href="nav.php">Nav</a> + <a class="tab" href="num.php">Digits</a> + </div> + <div class="tabMain"> + <div id="subpda"> + <input type="submit" class="tiny" name="submit" value="TV" /> + <input type="submit" class="tiny" name="submit" value="Videos" /> + <input type="submit" class="tiny" name="submit" value="Music" /> + </div> + + <div id="subpda"> + <input type="submit" class="tiny" name="submit" value="Recorded" /> + <input type="submit" class="tiny" name="submit" value="Guide" /> + <input type="submit" class="tiny" name="submit" value="Pictures" /> + </div> + + </div> +</div> + +</form> +</body> +</html> diff --git a/abs/core-testing/local-website/htdocs/remote/remote-wide.html b/abs/core-testing/local-website/htdocs/remote/remote-wide.html new file mode 100644 index 0000000..2806007 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/remote-wide.html @@ -0,0 +1,275 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> +<title>MythTV Web Wide Remote</title> +<link rel="stylesheet" type="text/css" media="screen" href="remote.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + +<script language="javascript"> + function setredirect(where,value) + { + //set the redirect location + document.getElementById('redirectpage').value=where; + //set the clicked on value + document.getElementById('buttonvalue').value=value; + return true; + } +</script> + +</head> + + +<body> +<form method="post" action="backend.php"> +<!--- +Set this hidden field to the default page that you want all redirections to go to. +When left unset, the default behavior is to redirect back to the original page that +sent the request to the backend.php script. +---> +<input type="hidden" name="redirectpage" id="redirectpage" value=""> + +<!--- +This hidden field is set via javascript to get around IE's problem with posting +an imagebutton value +---> +<input type="hidden" name="buttonvalue" id="buttonvalue" value=""> + + +<table style="" align="left" border="0" cellspacing="0" width="300"> + + <tbody> + + <tr> + + <td valign="top"> + <table border="0" cellspacing="0"> + + <tbody> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + + </tr> + + <tr align="center"> + + <td><input name="submit" class="txt" value="TV" type="submit" /></td> + + <td><input name="submit" class="txt" value="Music" type="submit" /></td> + + <td><input name="submit" class="txt" value="Video" type="submit" /></td> + + <td><input name="submit" class="txt" value="Recordings" type="submit" /></td> + + <td><input name="submit" class="txt" value="Guide" type="submit" /></td> + + <td><input name="submit" class="txt" value="Pictures" type="submit" /></td> + + </tr> + + <tr style="height: 8px;" align="center"> + + <td> + </td> + </tr> + + <tr> + + <td colspan="3" align="center"> + <table style="width: 70%;" border="0" cellspacing="0"> + + <tbody> + + <tr align="center"> + + <td> </td> + + + <td><input alt="Record" name="submit" class="record" value="Rec" src="images/blank.gif" type="image" onclick="setredirect('','Rec')" /> </td> + + <td><input alt="Stop" name="submit" class="stop" value="Stop" src="images/blank.gif" type="image" onclick="setredirect('','Stop')" /> </td> + + <td><input alt="Pause" name="submit" class="pause" value="Pause" src="images/blank.gif" type="image" onclick="setredirect('','Pause')" /> </td> + + <td> </td> + + </tr> + + <tr> + + <td><input alt="Rewind" name="submit" class="rewind" value="<<" src="images/blank.gif" type="image" onclick="setredirect('','<<')" /> </td> + + <td> </td> + + <td><input alt="Play" name="submit" class="play" value="Play" src="images/blank.gif" type="image" onclick="setredirect('','Play')" /> </td> + + <td> </td> + + <td><input alt="Fast Forward" name="submit" class="ffwd" value=">>" src="images/blank.gif" type="image" onclick="setredirect('','>>')" /> </td> + + </tr> + + <tr> + + <td> </td> + + <td><input alt="Skip Back" name="submit" class="sback" value="|<" src="images/blank.gif" type="image" onclick="setredirect('','|<')" /> </td> + + <td> </td> + + <td><input alt="Skip Forward" name="submit" class="sfwd" value=">|" src="images/blank.gif" type="image" onclick="setredirect('','>|')" /> </td> + + <td> </td> + + </tr> + + </tbody> + </table> + + </td> + + <td colspan="3" align="center"> + <table border="0" cellspacing="0" width="60%"> + + <tbody> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="1" type="submit" /></td> + + <td><input name="submit" class="number" value="2" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="3" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="4" type="submit" /></td> + + <td><input name="submit" class="number" value="5" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="6" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="7" type="submit" /></td> + + <td><input name="submit" class="number" value="8" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="9" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="*" type="submit" /></td> + + <td><input name="submit" class="number" value="0" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="#" type="submit" /></td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + + </tr> + + <tr align="center"> + + <td><input name="submit" class="txt" value="Back" type="submit" /></td> + + <td><input name="submit" class="txt" value="Info" type="submit" /></td> + + <td><input name="submit" class="txt" value="Menu" type="submit" /></td> + + <td><input name="submit" class="txt" value="Mute" type="submit" /></td> + + <td><input name="submit" class="txt" value="Clear" type="submit" /></td> + + <td><input name="submit" class="txt" value="Enter" type="submit" /></td> + + </tr> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + </tr> + + <tr> + + <td colspan="6" align="center"> + <table border="0" cellspacing="0" width="50%"> + + <tbody> + + <tr> + + <td><input name="submit" class="txt" value="Vol Up" type="submit" /></td> + + <td> </td> + + <td><input alt="Up" name="submit" class="navup" value="U" src="images/blank.gif" type="image" onclick="setredirect('','U')" /> </td> + + <td> </td> + + <td><input name="submit" class="txt" value="Page Up" type="submit" /></td> + + </tr> + + <tr> + + <td> </td> + + <td><input alt="Left" name="submit" class="navleft" value="L" src="images/blank.gif" type="image" onclick="setredirect('','L')" /> </td> + + <td><input alt="OK" name="submit" class="navok" value="OK" src="images/blank.gif" type="image" onclick="setredirect('','OK')" /> </td> + + <td><input alt="Right" name="submit" class="navright" value="R" src="images/blank.gif" type="image" onclick="setredirect('','R')" /> </td> + + <td> </td> + + </tr> + + <tr> + + <td><input name="submit" class="txt" value="Vol Dn" type="submit" /></td> + + <td> </td> + + <td><input alt="Down" name="submit" class="navdown" value="D" src="images/blank.gif" type="image" onclick="setredirect('','D')" /> </td> + + <td> </td> + + <td><input name="submit" class="txt" value="Page Dn" type="submit" /></td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + </tbody> +</table> +<form> +</body> +</html> diff --git a/abs/core-testing/local-website/htdocs/remote/remote-wide.php b/abs/core-testing/local-website/htdocs/remote/remote-wide.php new file mode 100644 index 0000000..a9035df --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/remote-wide.php @@ -0,0 +1,380 @@ +<? +# +# Original code (c) 2006 Mike Poublon <poublon@geeksoft.dyndns.org> +# +# Enhancements (c) 2006 Steven Ellis <support@openmedia.co.nz> +# +#change the line below that has tv.local to the address of your frontend. + +#echo time() . "<br>"; +$submit = $_POST['submit']; +#echo "form submitted = $submit<br>"; + +# We set jump when we want to perform more complex commands +$jump=""; + +if ($submit == "Power"){ + #Power - not really used yet + $key = ""; +} else if ($submit == "TV"){ + $jump = "livetv"; +} else if ($submit == "Music"){ + $jump = "playmusic"; +} else if ($submit == "Video"){ + $jump = "mythvideo"; +} else if ($submit == "Recordings"){ + $jump = "playbackrecordings"; +} else if ($submit == "Guide"){ + $jump = "programguide"; +} else if ($submit == "Pictures"){ + $jump = "mythgallery"; +} else if ($submit == "Back") { + $key = "escape"; +} else if ($submit == "Info") { + $key = "i"; +} else if ($submit == "Menu") { + #Menu + $key = "m"; +} else if ($submit == "U") { + $key = "up"; +} else if ($submit == "L") { + $key = "left"; +} else if ($submit == "D") { + $key = "down"; +} else if ($submit == "R") { + $key = "right"; +} else if ($submit == "OK") { + $key = "enter"; +} else if ($submit == "Page Up") { + $key = "pageup"; +} else if ($submit == "Page Dn") { + $key = "pagedown"; +} else if ($submit == "Vol Up") { + $key = "bracketright"; +} else if ($submit == "Vol Dn") { + $key = "bracketleft"; +} else if ($submit == "Mute") { + $key = "f9"; +} else if ($submit == "Pause") { + $key = "p"; +} else if ($submit == "Stop") { + $key = "s"; +} else if ($submit == "Play") { + $key = "p"; +} else if ($submit == "<<") { + $key = "left"; +} else if ($submit == ">>") { + $key = "right"; +} else if ($submit == "|<") { + #skip commercial back + $key = "q"; +} else if ($submit == ">|") { + #skip commercial + $key = "z"; +# Special keys used by myPVR +} else if ($submit == "#") { + # Change tuner + $key = "y"; +} else if ($submit == "*") { + #skip commercial + $key = "z"; +} else if ($submit == "0" || + $submit == "1" || + $submit == "2" || + $submit == "3" || + $submit == "4" || + $submit == "5" || + $submit == "6" || + $submit == "7" || + $submit == "8" || + $submit == "9" ) { + $key = $submit; +} + +set_time_limit (5); +# change tv.local to the hostname/address of your frontend +$fp = fsockopen("localhost", 6546, $errno, $errstr, 30); +if (!$fp) { + echo "ERROR: $errstr ($errno)<br />\n"; +} else { + #stream_set_timeout ( $fp, 0, 100000); + #$banner = stream_get_contents($fp); + + $banner = ""; + + $c = fgetc($fp); + while ($c !== false && $c != "#") + { + #echo "c = $c<br>\n"; + $banner .= $c; + $c = fgetc($fp); + } + if ($c !== false) + { + $c = fgetc($fp); #Read in the extra space after the # + } + + if ($jump != "") { + $cmd = "jump $jump\x0d\x0a"; + $jump=""; + } else { + $cmd = "key $key\x0d\x0a"; + } + fwrite($fp,$cmd); + $res = fgets($fp); + #echo "result = $res<br>\n"; + + fclose($fp); +} + + +?> + +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> +<title>MythTV Web Remote</title> +<link rel="stylesheet" type="text/css" media="screen" href="remote.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> +</head> + +<body> +<form method="post"> +<table style="" align="left" border="0" cellspacing="0" width="300"> + + <tbody> + + <tr> + + <td valign="top"> + <table border="0" cellspacing="0"> + + <tbody> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + + </tr> + + <tr align="center"> + + <td><input name="submit" class="txt" value="TV" type="submit" /></td> + + <td><input name="submit" class="txt" value="Music" type="submit" /></td> + + <td><input name="submit" class="txt" value="Video" type="submit" /></td> + + <td><input name="submit" class="txt" value="Recordings" type="submit" /></td> + + <td><input name="submit" class="txt" value="Guide" type="submit" /></td> + + <td><input name="submit" class="txt" value="Pictures" type="submit" /></td> + + </tr> + + <tr style="height: 8px;" align="center"> + + <td> + </td> + </tr> + + <tr> + + <td colspan="3" align="center"> + <table style="width: 70%;" border="0" cellspacing="0"> + + <tbody> + + <tr align="center"> + + <td> </td> + + <td><input alt="Record" name="submit" class="image" value="Rec" src="images/rec.png" type="image" /> </td> + + <td><input alt="Stop" name="submit" class="image" value="Stop" src="images/stop.png" type="image" /> </td> + + <td><input alt="Pause" name="submit" class="image" value="Pause" src="images/pause.png" type="image" /> </td> + + <td> </td> + + </tr> + + <tr> + + <td><input alt="Rewind" name="submit" class="image" value="<<" src="images/fast_rewind.png" type="image" /> </td> + + <td> </td> + + <td><input alt="Play" name="submit" class="image" value="Play" src="images/right.png" type="image" /> </td> + + <td> </td> + + <td><input alt="Fast Forward" name="submit" class="image" value=">>" src="images/fast_forward.png" type="image" /> </td> + + </tr> + + <tr> + + <td> </td> + + <td><input alt="Skip Back" name="submit" class="image" value="|<" src="images/skip_back.png" type="image" /> </td> + + <td> </td> + + <td><input alt="Skip Forward" name="submit" class="image" value=">|" src="images/skip_forward.png" type="image" /> </td> + + <td> </td> + + </tr> + + </tbody> + </table> + + </td> + + <td colspan="3" align="center"> + <table border="0" cellspacing="0" width="60%"> + + <tbody> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="1" type="submit" /></td> + + <td><input name="submit" class="number" value="2" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="3" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="4" type="submit" /></td> + + <td><input name="submit" class="number" value="5" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="6" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="7" type="submit" /></td> + + <td><input name="submit" class="number" value="8" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="9" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="*" type="submit" /></td> + + <td><input name="submit" class="number" value="0" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="#" type="submit" /></td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + + </tr> + + <tr align="center"> + + <td><input name="submit" class="txt" value="Back" type="submit" /></td> + + <td><input name="submit" class="txt" value="Info" type="submit" /></td> + + <td><input name="submit" class="txt" value="Menu" type="submit" /></td> + + <td><input name="submit" class="txt" value="Mute" type="submit" /></td> + + <td><input name="submit" class="txt" value="Clear" type="submit" /></td> + + <td><input name="submit" class="txt" value="Enter" type="submit" /></td> + + </tr> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + </tr> + + <tr> + + <td colspan="6" align="center"> + <table border="0" cellspacing="0" width="50%"> + + <tbody> + + <tr> + + <td><input name="submit" class="txt" value="Vol Up" type="submit" /></td> + + <td> </td> + + <td><input alt="Up" name="submit" class="image" value="U" src="images/up.png" type="image" /> </td> + + <td> </td> + + <td><input name="submit" class="txt" value="Page Up" type="submit" /></td> + + </tr> + + <tr> + + <td> </td> + + <td><input alt="Left" name="submit" class="image" value="L" src="images/left.png" type="image" /> </td> + + <td><input alt="OK" name="submit" class="image" value="OK" src="images/ok.png" type="image" /> </td> + + <td><input alt="Right" name="submit" class="image" value="R" src="images/right.png" type="image" /> </td> + + <td> </td> + + </tr> + + <tr> + + <td><input name="submit" class="txt" value="Vol Dn" type="submit" /></td> + + <td> </td> + + <td><input alt="Down" name="submit" class="image" value="D" src="images/down.png" type="image" /> </td> + + <td> </td> + + <td><input name="submit" class="txt" value="Page Dn" type="submit" /></td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + </tbody> +</table> + +<form> +</body> +</html> diff --git a/abs/core-testing/local-website/htdocs/remote/remote.css b/abs/core-testing/local-website/htdocs/remote/remote.css new file mode 100644 index 0000000..0678a65 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/remote.css @@ -0,0 +1,436 @@ +/* + * Style sheet (c) 2006 Steven Ellis <support@openmedia.co.nz> + * + * Enhancements by Michael Lynch <lynchmv@gmail.com> + * + * Published under http://creativecommons.org/licenses/by/2.5/ + */ + +body { + width:300px; + margin:10px 0 0 10px; + padding 3px; + behavior:url('csshover.htc'); +} + +#narrow { + width:300px; +} + +.mypda { + width:285; + background-color:#fff; + color:#000; +} + +#subround { + width:100%; + min-height:40px; + height:40px; + padding-top:1%; + padding-right:1%; + padding-bottom:1%; + padding-left:1%; +} + +#subwide { + width:100%; + min-height:25px; + height:25px; + padding-top:1%; + padding-right:1%; + padding-bottom:1%; + padding-left:1%; +} + +#subpda { + width:100%; + height:auto; + padding:3px 2px 3px 2px; +} + +#halves { + float:left; + width:49%; +} + +#thirds { + float:left; + width:32.5%; +} + +#fourths { + float:left; + width:24%; +} + +#fifths { + float:left; + width:19%; +} + +#sixths { + float:left; + width:15%; + border:1px solid black; +} + +input.txt { + background:none; + border-style:none; + width:80px; + height:24px; + text-align:center; + font-size:8pt; + font-weight:normal; + background:url(images/button_text.png) no-repeat; +} + +input.txt:hover { + background:url(images/button_textg.png) no-repeat; +} +input.txt:active { + background:url(images/button_textr.png) no-repeat; +} +input.tiny { + border:1px solid #f6f6f6; + background-color:#2991c7; + width:86px; + color:#fff; + text-align:center; + font-size:8pt; + font-weight:normal; +} + +input.tiny:hover { +} + +input.halfleft { + background:none; + border-style:none; + width:80px; + height:24px; + text-align:center; + font-size:8pt; + font-weight:normal; + background:url(images/button_text.png) no-repeat; + float:right; +} + +input.halfleft:hover { + background:url(images/button_textg.png) no-repeat; +} +input.halfleft:active { + background:url(images/button_textr.png) no-repeat; +} + +input.halfright { + background:none; + border-style:none; + width:80px; + height:24px; + text-align:center; + font-size:8pt; + font-weight:normal; + background:url(images/button_text.png) no-repeat; + float:left; +} + +input.halfright:hover { + background:url(images/button_textg.png) no-repeat; +} +input.halfright:active { + background:url(images/button_textr.png) no-repeat; +} + +input.notxt { + visibility:hidden; + background:none; + border-style:none; + width:80px; + height:24px; + text-align:center; + font-size:8pt; + font-weight:normal; + background:url(images/button_text.png) no-repeat; +} + +input.image { + background:#fff; + width:40px; + height:40px; + padding:2px; +} + +input.record { + background:url(images/rec.png) no-repeat; + width:40px; + height:40px; + padding:2px; +} + +input.record:hover { + background:url(images/rec_g.png) no-repeat; +} + +input.record:active { + background:url(images/rec_r.png) no-repeat; +} + +input.stop { + background:url(images/stop.png) no-repeat; + width:40px; + height:40px; + padding:2px; +} + +input.stop:hover { + background:url(images/stop_g.png) no-repeat; +} + +input.stop:active { + background:url(images/stop_r.png) no-repeat; +} + +input.pause { + background:url(images/pause.png) no-repeat; + width:40px; + height:40px; + padding:2px; +} + +input.pause:hover { + background:url(images/pause_g.png) no-repeat; +} + +input.pause:active { + background:url(images/pause_r.png) no-repeat; +} + +input.rewind { + background:url(images/fast_rewind.png) no-repeat; + width:40px; + height:40px; + padding:2px; +} + +input.rewind:hover { + background:url(images/fast_rewind_g.png) no-repeat; +} + +input.rewind:active { + background:url(images/fast_rewind_r.png) no-repeat; +} + +input.play { + background:url(images/right.png) no-repeat; + width:40px; + height:40px; + padding:2px; +} + +input.play:hover { + background:url(images/right_g.png) no-repeat; +} + +input.play:active { + background:url(images/right_r.png) no-repeat; +} + +input.ffwd { + background:url(images/fast_forward.png) no-repeat; + width:40px; + height:40px; + padding:2px; +} + +input.ffwd:hover { + background:url(images/fast_forward_g.png) no-repeat; +} + +input.ffwd:active { + background:url(images/fast_forward_r.png) no-repeat; +} + +input.sback { + background:url(images/skip_back.png) no-repeat; + width:40px; + height:40px; + padding:2px; +} + +input.sback:hover { + background:url(images/skip_back_g.png) no-repeat; +} + +input.sback:active { + background:url(images/skip_back_r.png) no-repeat; +} + +input.sfwd { + background:url(images/skip_forward.png) no-repeat; + width:40px; + height:40px; + padding:2px; +} + +input.sfwd:hover { + background:url(images/skip_forward_g.png) no-repeat; +} + +input.sfwd:active { + background:url(images/skip_forward_r.png) no-repeat; +} + +input.navup { + background:url(images/up.png) no-repeat; + width:40px; + height:40px; + padding:2px; + display:block; + margin-left:auto; + margin-right:auto; +} + +input.navup:hover { + background:url(images/up_g.png) no-repeat; +} +input.navup:active { + background:url(images/up_r.png) no-repeat; +} + + +input.navleft { + background:url(images/left.png) no-repeat; + width:40px; + height:40px; + padding:2px; + float:right; +} + +input.navleft:hover { + background:url(images/left_g.png) no-repeat; +} + +input.navleft:active { + background:url(images/left_r.png) no-repeat; +} + +input.navok { + background:url(images/ok.png) no-repeat; + width:40px; + height:40px; + padding:2px; + display:block; + margin-left:auto; + margin-right:auto; +} + +input.navok:hover { + background:url(images/ok_g.png) no-repeat; +} + +input.navok:active { + background:url(images/ok_r.png) no-repeat; +} + +input.navright { + background:url(images/right.png) no-repeat; + width:40px; + height:40px; + padding:2px; + float:left; +} + +input.navright:hover { + background:url(images/right_g.png) no-repeat; +} + +input.navright:active { + background:url(images/right_r.png) no-repeat; +} + +input.navdown { + background:url(images/down.png) no-repeat; + width:40px; + height:40px; + padding:2px; + display:block; + margin-left:auto; + margin-right:auto; +} + +input.navdown:hover { + background:url(images/down_g.png) no-repeat; +} +input.navdown:active { + background:url(images/down_r.png) no-repeat; +} + +input.noimage { + visibility:hidden; + border-radius:21px; + background: #fff; + width:40px; + height:40px; + padding:2px; +} + +input.number { + border: none; + width: 30px; + height: 30px; + background: url(./images/button_30.png) no-repeat; + font-size: 12pt; + font-weight: bold; + padding: 0px; + display:block; + margin-left:auto; + margin-right:auto; +} + +input.number:hover { + background: url(./images/button_30g.png) no-repeat; +} + +input.number:active { + background: url(./images/button_30r.png) no-repeat; +} + +div.tabArea { + font-size: 80%; + font-weight: bold; +} + +a.tab { + background-color: #f0f0f0; + border: 1px solid #000000; + border-bottom-width: 0px; + padding: 2px .3em 2px .3em; + position:relative; + text-decoration: none; + top:-1px; + z-index:100; +} + +a.tab, a.tab:visited { + color: #808080; +} + +a.tab:hover { + background-color: #d0d0d0; + color: #606060; +} + +a.tab.activeTab, a.tab.activeTab:hover, a.tab.activeTab:visited { + background-color: #c0c0c0; + color: #000000; + z-index:102; +} + +div.tabMain { + background-color: #c0c0c0; + border: 1px solid #000000; + position:relative; + z-index:101; +} diff --git a/abs/core-testing/local-website/htdocs/remote/remote.html b/abs/core-testing/local-website/htdocs/remote/remote.html new file mode 100644 index 0000000..71ec374 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/remote.html @@ -0,0 +1,307 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> +<title>MythTV Web Remote</title> +<link rel="stylesheet" type="text/css" media="screen" href="remote.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + +<script language="javascript"> + function setredirect(where,value) + { + //set the redirect location + document.getElementById('redirectpage').value=where; + //set the clicked on value + document.getElementById('buttonvalue').value=value; + return true; + } +</script> + +</head> + +<body> +<form method="post" action="backend.php"> +<!--- +Set this hidden field to the default page that you want all redirections to go to. +When left unset, the default behavior is to redirect back to the original page that +sent the request to the backend.php script. +---> +<input type="hidden" name="redirectpage" id="redirectpage" value=""> + +<!--- +This hidden field is set via javascript to get around IE's problem with posting +an imagebutton value +---> +<input type="hidden" name="buttonvalue" id="buttonvalue" value=""> + + +<table style="" align="left" border="0" cellspacing="0" width="300"> + + <tbody> + + <tr> + + <td valign="top"> + <table border="0" cellspacing="0"> + + <tbody> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + + </tr> + + <tr align="center"> + + <td><input name="submit" class="txt" value="TV" type="submit" /></td> + + <td><input name="submit" class="txt" value="Music" type="submit" /></td> + + <td><input name="submit" class="txt" value="Video" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td><input name="submit" class="txt" value="Recordings" type="submit" /></td> + + <td><input name="submit" class="txt" value="Guide" type="submit" /></td> + + <td><input name="submit" class="txt" value="Pictures" type="submit" /></td> + + </tr> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + + </tr> + + <tr> + + <td colspan="3" align="center"> + <table style="width: 70%;" border="0" cellspacing="0"> + + <tbody> + + <tr align="center"> + + <td> </td> + + <td><input alt="Record" name="submit" class="record" value="Rec" src="images/blank.gif" type="image" onclick="setredirect('','Rec')" /> </td> + + <td><input alt="Stop" name="submit" class="stop" value="Stop" src="images/blank.gif" type="image" onclick="setredirect('','Stop')" /> </td> + + <td><input alt="Pause" name="submit" class="pause" value="Pause" src="images/blank.gif" type="image" onclick="setredirect('','Pause')" /> </td> + + <td> </td> + + </tr> + + <tr> + + <td><input alt="Rewind" name="submit" class="rewind" value="<<" src="images/blank.gif" type="image" onclick="setredirect('','<<')" /> </td> + + <td> </td> + + <td><input alt="Play" name="submit" class="play" value="Play" src="images/blank.gif" type="image" onclick="setredirect('','Play')" /> </td> + + <td> </td> + + <td><input alt="Fast Forward" name="submit" class="ffwd" value=">>" src="images/blank.gif" type="image" onclick="setredirect('','>>')" /> </td> + + </tr> + + <tr> + + <td> </td> + + <td><input alt="Skip Back" name="submit" class="sback" value="|<" src="images/blank.gif" type="image" onclick="setredirect('','|<')" /> </td> + + <td> </td> + + <td><input alt="Skip Forward" name="submit" class="sfwd" value=">|" src="images/blank.gif" type="image" onclick="setredirect('','>|')" /> </td> + + <td> </td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + <tr align="center"> + + <td> </td> + + <td><input name="submit" class="txt" value="Mute" type="submit" /></td> + + <td> </td> + + </tr> + + <tr align="center"> + + <td><input name="submit" class="txt" value="Back" type="submit" /></td> + + <td><input name="submit" class="txt" value="Info" type="submit" /></td> + + <td><input name="submit" class="txt" value="Menu" type="submit" /></td> + + </tr> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + + </tr> + + <tr> + + <td colspan="3" align="center"> + <table border="0" cellspacing="0" width="50%"> + + <tbody> + + <tr> + + <td><input name="submit" class="txt" value="Vol Up" type="submit" /></td> + + <td> </td> + + <td><input alt="Up" name="submit" class="navup" value="U" src="images/blank.gif" type="image" onclick="setredirect('','U')" /> </td> + + <td> </td> + + <td><input name="submit" class="txt" value="Page Up" type="submit" /></td> + + </tr> + + <tr> + + <td> </td> + + <td><input alt="Left" name="submit" class="navleft" value="L" src="images/blank.gif" type="image" onclick="setredirect('','L')" /> </td> + + <td><input alt="OK" name="submit" class="navok" value="OK" src="images/blank.gif" type="image" onclick="setredirect('','OK')" /> </td> + + <td><input alt="Right" name="submit" class="navright" value="R" src="images/blank.gif" type="image" onclick="setredirect('','R')" /> </td> + + <td> </td> + + </tr> + + <tr> + + <td><input name="submit" class="txt" value="Vol Dn" type="submit" /></td> + + <td> </td> + + <td><input alt="Down" name="submit" class="navdown" value="D" src="images/blank.gif" type="image" onclick="setredirect('','D')" /> </td> + + <td> </td> + + <td><input name="submit" class="txt" value="Page Dn" type="submit" /></td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + + </tr> + + <tr> + + <td colspan="3" align="center"> + <table border="0" cellspacing="0" width="60%"> + + <tbody> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="1" type="submit" /></td> + + <td><input name="submit" class="number" value="2" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="3" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="4" type="submit" /></td> + + <td><input name="submit" class="number" value="5" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="6" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="7" type="submit" /></td> + + <td><input name="submit" class="number" value="8" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="9" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="*" type="submit" /></td> + + <td><input name="submit" class="number" value="0" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="#" type="submit" /></td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + <tr> + + <td colspan="3" align="center"> + <table border="0" cellspacing="0" width="80%"> + + <tbody> + + <tr align="center"> + + <td><input name="submit" class="txt" value="Clear" type="submit" /></td> + + <td><input name="submit" class="txt" value="Enter" type="submit" /></td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + </tbody> +</table> +<form> +</body> +</html> diff --git a/abs/core-testing/local-website/htdocs/remote/remote.php b/abs/core-testing/local-website/htdocs/remote/remote.php new file mode 100644 index 0000000..bacf6a3 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/remote.php @@ -0,0 +1,413 @@ +<? +# +# Original code (c) 2006 Mike Poublon <poublon@geeksoft.dyndns.org> +# +# Enhancements (c) 2006 Steven Ellis <support@openmedia.co.nz> +# +#change the line below that has tv.local to the address of your frontend. + +#echo time() . "<br>"; +$submit = $_POST['submit']; +#echo "form submitted = $submit<br>"; + +# We set jump when we want to perform more complex commands +$jump=""; + +if ($submit == "Power"){ + #Power - not really used yet + $key = ""; +} else if ($submit == "TV"){ + $jump = "livetv"; +} else if ($submit == "Music"){ + $jump = "playmusic"; +} else if ($submit == "Video"){ + $jump = "mythvideo"; +} else if ($submit == "Recordings"){ + $jump = "playbackrecordings"; +} else if ($submit == "Guide"){ + $jump = "programguide"; +} else if ($submit == "Pictures"){ + $jump = "mythgallery"; +} else if ($submit == "Back") { + $key = "escape"; +} else if ($submit == "Info") { + $key = "i"; +} else if ($submit == "Menu") { + #Menu + $key = "m"; +} else if ($submit == "U") { + $key = "up"; +} else if ($submit == "L") { + $key = "left"; +} else if ($submit == "D") { + $key = "down"; +} else if ($submit == "R") { + $key = "right"; +} else if ($submit == "OK") { + $key = "enter"; +} else if ($submit == "Page Up") { + $key = "pageup"; +} else if ($submit == "Page Dn") { + $key = "pagedown"; +} else if ($submit == "Vol Up") { + $key = "bracketright"; +} else if ($submit == "Vol Dn") { + $key = "bracketleft"; +} else if ($submit == "Mute") { + $key = "f9"; +} else if ($submit == "Pause") { + $key = "p"; +} else if ($submit == "Stop") { + $key = "s"; +} else if ($submit == "Play") { + $key = "p"; +} else if ($submit == "<<") { + $key = "left"; +} else if ($submit == ">>") { + $key = "right"; +} else if ($submit == "|<") { + #skip commercial back + $key = "q"; +} else if ($submit == ">|") { + #skip commercial + $key = "z"; +# Special keys used by myPVR +} else if ($submit == "#") { + # Change tuner + $key = "y"; +} else if ($submit == "*") { + #skip commercial + $key = "z"; +} else if ($submit == "0" || + $submit == "1" || + $submit == "2" || + $submit == "3" || + $submit == "4" || + $submit == "5" || + $submit == "6" || + $submit == "7" || + $submit == "8" || + $submit == "9" ) { + $key = $submit; +} + +set_time_limit (5); +# change tv.local to the hostname/address of your frontend +$fp = fsockopen("localhost", 6546, $errno, $errstr, 30); +if (!$fp) { + echo "ERROR: $errstr ($errno)<br />\n"; +} else { + #stream_set_timeout ( $fp, 0, 100000); + #$banner = stream_get_contents($fp); + + $banner = ""; + + $c = fgetc($fp); + while ($c !== false && $c != "#") + { + #echo "c = $c<br>\n"; + $banner .= $c; + $c = fgetc($fp); + } + if ($c !== false) + { + $c = fgetc($fp); #Read in the extra space after the # + } + + if ($jump != "") { + $cmd = "jump $jump\x0d\x0a"; + $jump=""; + } else { + $cmd = "key $key\x0d\x0a"; + } + fwrite($fp,$cmd); + $res = fgets($fp); + #echo "result = $res<br>\n"; + + fclose($fp); +} + + +?> + +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> +<title>MythTV Web Remote</title> +<link rel="stylesheet" type="text/css" media="screen" href="remote.css" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> +</head> + +<body> +<form method="post"> +<table style="" align="left" border="0" cellspacing="0" width="300"> + + <tbody> + + <tr> + + <td valign="top"> + <table border="0" cellspacing="0"> + + <tbody> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + + </tr> + + <tr align="center"> + + <td><input name="submit" class="txt" value="TV" type="submit" /></td> + + <td><input name="submit" class="txt" value="Music" type="submit" /></td> + + <td><input name="submit" class="txt" value="Video" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td><input name="submit" class="txt" value="Recordings" type="submit" /></td> + + <td><input name="submit" class="txt" value="Guide" type="submit" /></td> + + <td><input name="submit" class="txt" value="Pictures" type="submit" /></td> + + </tr> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + + </tr> + + <tr> + + <td colspan="3" align="center"> + <table style="width: 70%;" border="0" cellspacing="0"> + + <tbody> + + <tr align="center"> + + <td> </td> + + <td><input alt="Record" name="submit" class="image" value="Rec" src="images/rec.png" type="image" /> </td> + + <td><input alt="Stop" name="submit" class="image" value="Stop" src="images/stop.png" type="image" /> </td> + + <td><input alt="Pause" name="submit" class="image" value="Pause" src="images/pause.png" type="image" /> </td> + + <td> </td> + + </tr> + + <tr> + + <td><input alt="Rewind" name="submit" class="image" value="<<" src="images/fast_rewind.png" type="image" /> </td> + + <td> </td> + + <td><input alt="Play" name="submit" class="image" value="Play" src="images/right.png" type="image" /> </td> + + <td> </td> + + <td><input alt="Fast Forward" name="submit" class="image" value=">>" src="images/fast_forward.png" type="image" /> </td> + + </tr> + + <tr> + + <td> </td> + + <td><input alt="Skip Back" name="submit" class="image" value="|<" src="images/skip_back.png" type="image" /> </td> + + <td> </td> + + <td><input alt="Skip Forward" name="submit" class="image" value=">|" src="images/skip_forward.png" type="image" /> </td> + + <td> </td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + <tr align="center"> + + <td> </td> + + <td><input name="submit" class="txt" value="Mute" type="submit" /></td> + + <td> </td> + + </tr> + + <tr align="center"> + + <td><input name="submit" class="txt" value="Back" type="submit" /></td> + + <td><input name="submit" class="txt" value="Info" type="submit" /></td> + + <td><input name="submit" class="txt" value="Menu" type="submit" /></td> + + </tr> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + + </tr> + + <tr> + + <td colspan="3" align="center"> + <table border="0" cellspacing="0" width="50%"> + + <tbody> + + <tr> + + <td><input name="submit" class="txt" value="Vol Up" type="submit" /></td> + + <td> </td> + + <td><input alt="Up" name="submit" class="image" value="U" src="images/up.png" type="image" /> </td> + + <td> </td> + + <td><input name="submit" class="txt" value="Page Up" type="submit" /></td> + + </tr> + + <tr> + + <td> </td> + + <td><input alt="Left" name="submit" class="image" value="L" src="images/left.png" type="image" /> </td> + + <td><input alt="OK" name="submit" class="image" value="OK" src="images/ok.png" type="image" /> </td> + + <td><input alt="Right" name="submit" class="image" value="R" src="images/right.png" type="image" /> </td> + + <td> </td> + + </tr> + + <tr> + + <td><input name="submit" class="txt" value="Vol Dn" type="submit" /></td> + + <td> </td> + + <td><input alt="Down" name="submit" class="image" value="D" src="images/down.png" type="image" /> </td> + + <td> </td> + + <td><input name="submit" class="txt" value="Page Dn" type="submit" /></td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + <tr style="height: 8px;" align="center"> + <td colspan="6"></td> + + </tr> + + <tr> + + <td colspan="3" align="center"> + <table border="0" cellspacing="0" width="60%"> + + <tbody> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="1" type="submit" /></td> + + <td><input name="submit" class="number" value="2" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="3" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="4" type="submit" /></td> + + <td><input name="submit" class="number" value="5" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="6" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="7" type="submit" /></td> + + <td><input name="submit" class="number" value="8" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="9" type="submit" /></td> + + </tr> + + <tr align="center"> + + <td align="right"><input name="submit" class="number" value="*" type="submit" /></td> + + <td><input name="submit" class="number" value="0" type="submit" /></td> + + <td align="left"><input name="submit" class="number" value="#" type="submit" /></td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + <tr> + + <td colspan="3" align="center"> + <table border="0" cellspacing="0" width="80%"> + + <tbody> + + <tr align="center"> + + <td><input name="submit" class="txt" value="Clear" type="submit" /></td> + + <td><input name="submit" class="txt" value="Enter" type="submit" /></td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + </tbody> + </table> + + </td> + + </tr> + + </tbody> +</table> +<form> +</body> +</html> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/button.svg b/abs/core-testing/local-website/htdocs/remote/svg/button.svg new file mode 100644 index 0000000..6f34399 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/button.svg @@ -0,0 +1,353 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + height="128.00000pt" + id="svg1" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Development/mypvr-web-remote/remote/svg" + sodipodi:docname="button.svg" + sodipodi:version="0.32" + width="128.00000pt"> + <metadata + id="metadata1663"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:title>Etiquette Icons</dc:title> + <dc:description /> + <dc:subject> + <rdf:Bag> + <rdf:li>hash</rdf:li> + <rdf:li /> + <rdf:li>action</rdf:li> + <rdf:li>computer</rdf:li> + <rdf:li>icons</rdf:li> + <rdf:li>buttons</rdf:li> + </rdf:Bag> + </dc:subject> + <dc:publisher> + <cc:Agent + rdf:about="http://www.openclipart.org"> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:publisher> + <dc:creator> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:creator> + <dc:rights> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:rights> + <dc:date /> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <cc:license + rdf:resource="http://web.resource.org/cc/PublicDomain" /> + <dc:language>en</dc:language> + </cc:Work> + <cc:License + rdf:about="http://web.resource.org/cc/PublicDomain"> + <cc:permits + rdf:resource="http://web.resource.org/cc/Reproduction" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/Distribution" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> + </cc:License> + </rdf:RDF> + </metadata> + <defs + id="defs3"> + <linearGradient + id="linearGradient1416"> + <stop + id="stop1417" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1419" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1418" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient1397"> + <stop + id="stop1398" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.53725493;" /> + <stop + id="stop1400" + offset="0.50000000" + style="stop-color:#ffffff;stop-opacity:0.26666668;" /> + <stop + id="stop1401" + offset="0.75000000" + style="stop-color:#000000;stop-opacity:0.13333334;" /> + <stop + id="stop1399" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient896"> + <stop + id="stop897" + offset="0.00000000" + style="stop-color:#e2d9a9;stop-opacity:1.0000000;" /> + <stop + id="stop898" + offset="1.0000000" + style="stop-color:#857c4d;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient893"> + <stop + id="stop894" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.27083334;" /> + <stop + id="stop895" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient841"> + <stop + id="stop842" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + <stop + id="stop844" + offset="0.50379843" + style="stop-color:#dadada;stop-opacity:1.0000000;" /> + <stop + id="stop845" + offset="0.51379842" + style="stop-color:#bdbdbd;stop-opacity:1.0000000;" /> + <stop + id="stop846" + offset="0.64667326" + style="stop-color:#dedede;stop-opacity:1.0000000;" /> + <stop + id="stop843" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient836"> + <stop + id="stop837" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:0.00000000;" /> + <stop + id="stop838" + offset="1" + style="stop-color:#fff;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="0.19090909" + x2="1.1454545" + xlink:href="#linearGradient832" + y1="0.68421054" + y2="-0.17105263" /> + <linearGradient + id="linearGradient839" + x1="0.47235259" + x2="0.47235259" + xlink:href="#linearGradient836" + y1="0.39059740" + y2="0.013744113" /> + <radialGradient + cx="0.50000000" + cy="0.50000000" + fx="0.51298690" + fy="0.092105433" + id="radialGradient840" + r="0.50000000" + xlink:href="#linearGradient1397" /> + <linearGradient + id="linearGradient860" + x1="0.21710530" + x2="0.89436638" + xlink:href="#linearGradient832" + y1="0.74342090" + y2="-0.33333325" /> + <linearGradient + id="linearGradient863" + x1="0.52739727" + x2="0.65068495" + xlink:href="#linearGradient836" + y1="0.48611110" + y2="-0.041666668" /> + <linearGradient + id="linearGradient891" + x1="0.12500000" + x2="0.82894737" + xlink:href="#linearGradient836" + y1="1.0986842" + y2="0.13815789" /> + <linearGradient + id="linearGradient892" + x1="-0.11404288" + x2="-0.061766334" + xlink:href="#linearGradient896" + y1="0.24721514" + y2="2.5462053" /> + <linearGradient + id="linearGradient900" + x1="0.37142858" + x2="0.11428571" + xlink:href="#linearGradient836" + y1="0.63888890" + y2="1.0416666" /> + <linearGradient + id="linearGradient905" + x1="1.3074018" + x2="1.3074018" + xlink:href="#linearGradient893" + y1="1.7768639" + y2="0.11690380" /> + <linearGradient + id="linearGradient906" + x1="-0.42276084" + x2="-0.42276084" + xlink:href="#linearGradient893" + y1="1.8603847" + y2="0.20042460" /> + <linearGradient + id="linearGradient908" + x1="0.50352114" + x2="0.21478873" + xlink:href="#linearGradient832" + y1="0.44615385" + y2="1.1615385" /> + <linearGradient + id="linearGradient910" + x1="0.45422536" + x2="0.69594592" + xlink:href="#linearGradient836" + y1="0.50000000" + y2="-0.078947365" /> + <linearGradient + id="linearGradient911" + x1="1.1710526" + x2="-2.2763157" + xlink:href="#linearGradient896" + y1="0.16447368" + y2="1.5986842" /> + <linearGradient + id="linearGradient912" + x1="0.67222220" + x2="0.25000000" + xlink:href="#linearGradient832" + y1="0.30167598" + y2="0.44692737" /> + <radialGradient + cx="0.48684204" + cy="0.44078955" + fx="0.53289479" + fy="0.013157940" + id="radialGradient1402" + r="0.76976496" + xlink:href="#linearGradient841" /> + <radialGradient + cx="0.48684210" + cy="0.46052632" + fx="0.52631575" + fy="0.71710521" + id="radialGradient1415" + r="0.76976496" + xlink:href="#linearGradient1416" /> + </defs> + <sodipodi:namedview + bordercolor="#666666" + borderopacity="1.0" + id="base" + inkscape:cx="56.622445" + inkscape:cy="59.112624" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:window-height="803" + inkscape:window-width="952" + inkscape:window-x="77" + inkscape:window-y="143" + inkscape:zoom="2.4559706" + pagecolor="#ffffff" + inkscape:current-layer="svg1" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path855" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1402);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-92.18625,-774.3955)" + inkscape:export-filename="/home/steve/Documents/remote/images/down.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path1414" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1415);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-91.90522,-774.4678)" + inkscape:export-filename="/home/steve/Documents/remote/images/down.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 184.98434 527.64008 A 29.511122 29.511122 0 1 0 125.96210,527.64008 A 29.511122 29.511122 0 1 0 184.98434 527.64008 z" + id="path856" + sodipodi:cx="155.47322" + sodipodi:cy="527.64008" + sodipodi:rx="29.511122" + sodipodi:ry="29.511122" + sodipodi:type="arc" + style="fill:url(#linearGradient839);fill-opacity:1;fill-rule:evenodd;stroke-width:1.0000000pt;stroke-opacity:0.37190083;" + transform="matrix(1.291670,0.000000,0.000000,1.524596,-118.6605,-740.1552)" + inkscape:export-filename="/home/steve/Documents/remote/images/down.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 361.33127,396.63946 C 361.33127,460.21074 309.73720,511.80481 246.16592,511.80481 C 182.59465,511.80481 131.00057,460.21074 131.00057,396.63946 C 131.00057,333.06819 182.59465,281.47411 246.16592,281.47411 C 309.73720,281.47411 361.33127,333.06819 361.33127,396.63946 z " + id="path862" + sodipodi:insensitive="true" + style="fill:url(#linearGradient863);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:1.0000000pt;" /> +</svg> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/button_30.xcf b/abs/core-testing/local-website/htdocs/remote/svg/button_30.xcf Binary files differnew file mode 100644 index 0000000..baa07b4 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/button_30.xcf diff --git a/abs/core-testing/local-website/htdocs/remote/svg/button_g.svg b/abs/core-testing/local-website/htdocs/remote/svg/button_g.svg new file mode 100644 index 0000000..f219560 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/button_g.svg @@ -0,0 +1,373 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + height="128.00000pt" + id="svg1" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Development/mypvr-web-remote/remote/svg" + sodipodi:docname="button_g.svg" + sodipodi:version="0.32" + width="128.00000pt"> + <metadata + id="metadata1663"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:title>Etiquette Icons</dc:title> + <dc:description /> + <dc:subject> + <rdf:Bag> + <rdf:li>hash</rdf:li> + <rdf:li /> + <rdf:li>action</rdf:li> + <rdf:li>computer</rdf:li> + <rdf:li>icons</rdf:li> + <rdf:li>buttons</rdf:li> + </rdf:Bag> + </dc:subject> + <dc:publisher> + <cc:Agent + rdf:about="http://www.openclipart.org"> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:publisher> + <dc:creator> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:creator> + <dc:rights> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:rights> + <dc:date /> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <cc:license + rdf:resource="http://web.resource.org/cc/PublicDomain" /> + <dc:language>en</dc:language> + </cc:Work> + <cc:License + rdf:about="http://web.resource.org/cc/PublicDomain"> + <cc:permits + rdf:resource="http://web.resource.org/cc/Reproduction" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/Distribution" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> + </cc:License> + </rdf:RDF> + </metadata> + <defs + id="defs3"> + <linearGradient + id="linearGradient1416"> + <stop + id="stop1417" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1419" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1418" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient1397"> + <stop + id="stop1398" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.53725493;" /> + <stop + id="stop1400" + offset="0.50000000" + style="stop-color:#ffffff;stop-opacity:0.26666668;" /> + <stop + id="stop1401" + offset="0.75000000" + style="stop-color:#000000;stop-opacity:0.13333334;" /> + <stop + id="stop1399" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient896"> + <stop + id="stop897" + offset="0.00000000" + style="stop-color:#e2d9a9;stop-opacity:1.0000000;" /> + <stop + id="stop898" + offset="1.0000000" + style="stop-color:#857c4d;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient893"> + <stop + id="stop894" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.27083334;" /> + <stop + id="stop895" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient841"> + <stop + id="stop842" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + <stop + id="stop844" + offset="0.50379843" + style="stop-color:#dadada;stop-opacity:1.0000000;" /> + <stop + id="stop845" + offset="0.51379842" + style="stop-color:#bdbdbd;stop-opacity:1.0000000;" /> + <stop + id="stop846" + offset="0.64667326" + style="stop-color:#dedede;stop-opacity:1.0000000;" /> + <stop + id="stop843" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient836"> + <stop + id="stop837" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:0.00000000;" /> + <stop + id="stop838" + offset="1" + style="stop-color:#fff;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="0.19090909" + x2="1.1454545" + xlink:href="#linearGradient832" + y1="0.68421054" + y2="-0.17105263" /> + <linearGradient + id="linearGradient839" + x1="0.47235259" + x2="0.47235259" + xlink:href="#linearGradient836" + y1="0.39059740" + y2="0.013744113" /> + <radialGradient + cx="0.50000000" + cy="0.50000000" + fx="0.51298690" + fy="0.092105433" + id="radialGradient840" + r="0.50000000" + xlink:href="#linearGradient1397" /> + <linearGradient + id="linearGradient860" + x1="0.21710530" + x2="0.89436638" + xlink:href="#linearGradient832" + y1="0.74342090" + y2="-0.33333325" /> + <linearGradient + id="linearGradient863" + x1="0.52739727" + x2="0.65068495" + xlink:href="#linearGradient836" + y1="0.48611110" + y2="-0.041666668" /> + <linearGradient + id="linearGradient891" + x1="0.12500000" + x2="0.82894737" + xlink:href="#linearGradient836" + y1="1.0986842" + y2="0.13815789" /> + <linearGradient + id="linearGradient892" + x1="-0.11404288" + x2="-0.061766334" + xlink:href="#linearGradient896" + y1="0.24721514" + y2="2.5462053" /> + <linearGradient + id="linearGradient900" + x1="0.37142858" + x2="0.11428571" + xlink:href="#linearGradient836" + y1="0.63888890" + y2="1.0416666" /> + <linearGradient + id="linearGradient905" + x1="1.3074018" + x2="1.3074018" + xlink:href="#linearGradient893" + y1="1.7768639" + y2="0.11690380" /> + <linearGradient + id="linearGradient906" + x1="-0.42276084" + x2="-0.42276084" + xlink:href="#linearGradient893" + y1="1.8603847" + y2="0.20042460" /> + <linearGradient + id="linearGradient908" + x1="0.50352114" + x2="0.21478873" + xlink:href="#linearGradient832" + y1="0.44615385" + y2="1.1615385" /> + <linearGradient + id="linearGradient910" + x1="0.45422536" + x2="0.69594592" + xlink:href="#linearGradient836" + y1="0.50000000" + y2="-0.078947365" /> + <linearGradient + id="linearGradient911" + x1="1.1710526" + x2="-2.2763157" + xlink:href="#linearGradient896" + y1="0.16447368" + y2="1.5986842" /> + <linearGradient + id="linearGradient912" + x1="0.67222220" + x2="0.25000000" + xlink:href="#linearGradient832" + y1="0.30167598" + y2="0.44692737" /> + <radialGradient + cx="0.48684204" + cy="0.44078955" + fx="0.53289479" + fy="0.013157940" + id="radialGradient1402" + r="0.76976496" + xlink:href="#linearGradient841" /> + <radialGradient + cx="0.48684210" + cy="0.46052632" + fx="0.52631575" + fy="0.71710521" + id="radialGradient1415" + r="0.76976496" + xlink:href="#linearGradient1416" /> + </defs> + <sodipodi:namedview + bordercolor="#666666" + borderopacity="1.0" + id="base" + inkscape:cx="66.407707" + inkscape:cy="87.742158" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:window-height="834" + inkscape:window-width="1586" + inkscape:window-x="38" + inkscape:window-y="78" + inkscape:zoom="7.3998677" + pagecolor="#ffffff" + inkscape:current-layer="layer1" + showguides="false" + showgrid="true" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path855" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1402);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-92.18625,-774.3955)" + inkscape:export-filename="/home/steve/Documents/remote/images/down.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path1414" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1415);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-91.90522,-774.4678)" + inkscape:export-filename="/home/steve/Documents/remote/images/down.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 184.98434 527.64008 A 29.511122 29.511122 0 1 0 125.96210,527.64008 A 29.511122 29.511122 0 1 0 184.98434 527.64008 z" + id="path856" + sodipodi:cx="155.47322" + sodipodi:cy="527.64008" + sodipodi:rx="29.511122" + sodipodi:ry="29.511122" + sodipodi:type="arc" + style="fill:url(#linearGradient839);fill-opacity:1;fill-rule:evenodd;stroke-width:1.0000000pt;stroke-opacity:0.37190083;" + transform="matrix(1.291670,0.000000,0.000000,1.524596,-118.6605,-740.1552)" + inkscape:export-filename="/home/steve/Documents/remote/images/down.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 361.33127,396.63946 C 361.33127,460.21074 309.73720,511.80481 246.16592,511.80481 C 182.59465,511.80481 131.00057,460.21074 131.00057,396.63946 C 131.00057,333.06819 182.59465,281.47411 246.16592,281.47411 C 309.73720,281.47411 361.33127,333.06819 361.33127,396.63946 z " + id="path862" + sodipodi:insensitive="true" + style="fill:url(#linearGradient863);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:1.0000000pt;" /> + <g + inkscape:groupmode="layer" + id="layer1" + inkscape:label="Green"> + <path + sodipodi:type="arc" + style="opacity:0.54945056;fill:#7caa92;fill-opacity:1" + id="path4624" + sodipodi:cx="93.836662" + sodipodi:cy="78.585709" + sodipodi:rx="45.676094" + sodipodi:ry="47.013885" + d="M 139.51276 78.585709 A 45.676094 47.013885 0 1 1 48.160568,78.585709 A 45.676094 47.013885 0 1 1 139.51276 78.585709 z" + transform="matrix(1.039931,0,0,1.01034,-16.08364,-13.89829)" + inkscape:export-filename="/home/steve/Development/mypvr-web-remote/remote/images/button_30g.png" + inkscape:export-xdpi="28.42" + inkscape:export-ydpi="28.42" /> + </g> +</svg> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/button_r.svg b/abs/core-testing/local-website/htdocs/remote/svg/button_r.svg new file mode 100644 index 0000000..d2cb508 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/button_r.svg @@ -0,0 +1,371 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + height="128.00000pt" + id="svg1" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Development/mypvr-web-remote/remote/svg" + sodipodi:docname="button_r.svg" + sodipodi:version="0.32" + width="128.00000pt"> + <metadata + id="metadata1663"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:title>Etiquette Icons</dc:title> + <dc:description /> + <dc:subject> + <rdf:Bag> + <rdf:li>hash</rdf:li> + <rdf:li /> + <rdf:li>action</rdf:li> + <rdf:li>computer</rdf:li> + <rdf:li>icons</rdf:li> + <rdf:li>buttons</rdf:li> + </rdf:Bag> + </dc:subject> + <dc:publisher> + <cc:Agent + rdf:about="http://www.openclipart.org"> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:publisher> + <dc:creator> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:creator> + <dc:rights> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:rights> + <dc:date /> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <cc:license + rdf:resource="http://web.resource.org/cc/PublicDomain" /> + <dc:language>en</dc:language> + </cc:Work> + <cc:License + rdf:about="http://web.resource.org/cc/PublicDomain"> + <cc:permits + rdf:resource="http://web.resource.org/cc/Reproduction" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/Distribution" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> + </cc:License> + </rdf:RDF> + </metadata> + <defs + id="defs3"> + <linearGradient + id="linearGradient1416"> + <stop + id="stop1417" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1419" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1418" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient1397"> + <stop + id="stop1398" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.53725493;" /> + <stop + id="stop1400" + offset="0.50000000" + style="stop-color:#ffffff;stop-opacity:0.26666668;" /> + <stop + id="stop1401" + offset="0.75000000" + style="stop-color:#000000;stop-opacity:0.13333334;" /> + <stop + id="stop1399" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient896"> + <stop + id="stop897" + offset="0.00000000" + style="stop-color:#e2d9a9;stop-opacity:1.0000000;" /> + <stop + id="stop898" + offset="1.0000000" + style="stop-color:#857c4d;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient893"> + <stop + id="stop894" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.27083334;" /> + <stop + id="stop895" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient841"> + <stop + id="stop842" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + <stop + id="stop844" + offset="0.50379843" + style="stop-color:#dadada;stop-opacity:1.0000000;" /> + <stop + id="stop845" + offset="0.51379842" + style="stop-color:#bdbdbd;stop-opacity:1.0000000;" /> + <stop + id="stop846" + offset="0.64667326" + style="stop-color:#dedede;stop-opacity:1.0000000;" /> + <stop + id="stop843" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient836"> + <stop + id="stop837" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:0.00000000;" /> + <stop + id="stop838" + offset="1" + style="stop-color:#fff;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="0.19090909" + x2="1.1454545" + xlink:href="#linearGradient832" + y1="0.68421054" + y2="-0.17105263" /> + <linearGradient + id="linearGradient839" + x1="0.47235259" + x2="0.47235259" + xlink:href="#linearGradient836" + y1="0.39059740" + y2="0.013744113" /> + <radialGradient + cx="0.50000000" + cy="0.50000000" + fx="0.51298690" + fy="0.092105433" + id="radialGradient840" + r="0.50000000" + xlink:href="#linearGradient1397" /> + <linearGradient + id="linearGradient860" + x1="0.21710530" + x2="0.89436638" + xlink:href="#linearGradient832" + y1="0.74342090" + y2="-0.33333325" /> + <linearGradient + id="linearGradient863" + x1="0.52739727" + x2="0.65068495" + xlink:href="#linearGradient836" + y1="0.48611110" + y2="-0.041666668" /> + <linearGradient + id="linearGradient891" + x1="0.12500000" + x2="0.82894737" + xlink:href="#linearGradient836" + y1="1.0986842" + y2="0.13815789" /> + <linearGradient + id="linearGradient892" + x1="-0.11404288" + x2="-0.061766334" + xlink:href="#linearGradient896" + y1="0.24721514" + y2="2.5462053" /> + <linearGradient + id="linearGradient900" + x1="0.37142858" + x2="0.11428571" + xlink:href="#linearGradient836" + y1="0.63888890" + y2="1.0416666" /> + <linearGradient + id="linearGradient905" + x1="1.3074018" + x2="1.3074018" + xlink:href="#linearGradient893" + y1="1.7768639" + y2="0.11690380" /> + <linearGradient + id="linearGradient906" + x1="-0.42276084" + x2="-0.42276084" + xlink:href="#linearGradient893" + y1="1.8603847" + y2="0.20042460" /> + <linearGradient + id="linearGradient908" + x1="0.50352114" + x2="0.21478873" + xlink:href="#linearGradient832" + y1="0.44615385" + y2="1.1615385" /> + <linearGradient + id="linearGradient910" + x1="0.45422536" + x2="0.69594592" + xlink:href="#linearGradient836" + y1="0.50000000" + y2="-0.078947365" /> + <linearGradient + id="linearGradient911" + x1="1.1710526" + x2="-2.2763157" + xlink:href="#linearGradient896" + y1="0.16447368" + y2="1.5986842" /> + <linearGradient + id="linearGradient912" + x1="0.67222220" + x2="0.25000000" + xlink:href="#linearGradient832" + y1="0.30167598" + y2="0.44692737" /> + <radialGradient + cx="0.48684204" + cy="0.44078955" + fx="0.53289479" + fy="0.013157940" + id="radialGradient1402" + r="0.76976496" + xlink:href="#linearGradient841" /> + <radialGradient + cx="0.48684210" + cy="0.46052632" + fx="0.52631575" + fy="0.71710521" + id="radialGradient1415" + r="0.76976496" + xlink:href="#linearGradient1416" /> + </defs> + <sodipodi:namedview + bordercolor="#666666" + borderopacity="1.0" + id="base" + inkscape:cx="60.540922" + inkscape:cy="93.850029" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:window-height="917" + inkscape:window-width="1125" + inkscape:window-x="77" + inkscape:window-y="56" + inkscape:zoom="6.9465339" + pagecolor="#ffffff" + inkscape:current-layer="layer2" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path855" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1402);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-92.18625,-774.3955)" + inkscape:export-filename="/home/steve/Documents/remote/images/down.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path1414" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1415);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-91.90522,-774.4678)" + inkscape:export-filename="/home/steve/Documents/remote/images/down.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 184.98434 527.64008 A 29.511122 29.511122 0 1 0 125.96210,527.64008 A 29.511122 29.511122 0 1 0 184.98434 527.64008 z" + id="path856" + sodipodi:cx="155.47322" + sodipodi:cy="527.64008" + sodipodi:rx="29.511122" + sodipodi:ry="29.511122" + sodipodi:type="arc" + style="fill:url(#linearGradient839);fill-opacity:1;fill-rule:evenodd;stroke-width:1.0000000pt;stroke-opacity:0.37190083;" + transform="matrix(1.291670,0.000000,0.000000,1.524596,-118.6605,-740.1552)" + inkscape:export-filename="/home/steve/Documents/remote/images/down.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 361.33127,396.63946 C 361.33127,460.21074 309.73720,511.80481 246.16592,511.80481 C 182.59465,511.80481 131.00057,460.21074 131.00057,396.63946 C 131.00057,333.06819 182.59465,281.47411 246.16592,281.47411 C 309.73720,281.47411 361.33127,333.06819 361.33127,396.63946 z " + id="path862" + sodipodi:insensitive="true" + style="fill:url(#linearGradient863);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:1.0000000pt;" /> + <g + inkscape:groupmode="layer" + id="layer2" + inkscape:label="Red"> + <path + sodipodi:type="arc" + style="opacity:0.56043956;fill:#a9896a;fill-opacity:1" + id="path5769" + sodipodi:cx="86.517967" + sodipodi:cy="88.453529" + sodipodi:rx="48.513405" + sodipodi:ry="33.541908" + d="M 135.03137 88.453529 A 48.513405 33.541908 0 1 1 38.004562,88.453529 A 48.513405 33.541908 0 1 1 135.03137 88.453529 z" + transform="matrix(0.979229,0,0,1.414164,-2.953461,-59.73923)" + inkscape:export-xdpi="28.42" + inkscape:export-ydpi="28.42" + inkscape:export-filename="/home/steve/Development/mypvr-web-remote/remote/images/button_30r.png" /> + </g> +</svg> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/down.svg b/abs/core-testing/local-website/htdocs/remote/svg/down.svg new file mode 100644 index 0000000..a321bc6 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/down.svg @@ -0,0 +1,361 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + height="128.00000pt" + id="svg1" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Documents/remote" + sodipodi:docname="down.svg" + sodipodi:version="0.32" + width="128.00000pt"> + <metadata + id="metadata1663"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:title>Etiquette Icons</dc:title> + <dc:description /> + <dc:subject> + <rdf:Bag> + <rdf:li>hash</rdf:li> + <rdf:li /> + <rdf:li>action</rdf:li> + <rdf:li>computer</rdf:li> + <rdf:li>icons</rdf:li> + <rdf:li>buttons</rdf:li> + </rdf:Bag> + </dc:subject> + <dc:publisher> + <cc:Agent + rdf:about="http://www.openclipart.org"> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:publisher> + <dc:creator> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:creator> + <dc:rights> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:rights> + <dc:date /> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <cc:license + rdf:resource="http://web.resource.org/cc/PublicDomain" /> + <dc:language>en</dc:language> + </cc:Work> + <cc:License + rdf:about="http://web.resource.org/cc/PublicDomain"> + <cc:permits + rdf:resource="http://web.resource.org/cc/Reproduction" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/Distribution" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> + </cc:License> + </rdf:RDF> + </metadata> + <defs + id="defs3"> + <linearGradient + id="linearGradient1416"> + <stop + id="stop1417" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1419" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1418" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient1397"> + <stop + id="stop1398" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.53725493;" /> + <stop + id="stop1400" + offset="0.50000000" + style="stop-color:#ffffff;stop-opacity:0.26666668;" /> + <stop + id="stop1401" + offset="0.75000000" + style="stop-color:#000000;stop-opacity:0.13333334;" /> + <stop + id="stop1399" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient896"> + <stop + id="stop897" + offset="0.00000000" + style="stop-color:#e2d9a9;stop-opacity:1.0000000;" /> + <stop + id="stop898" + offset="1.0000000" + style="stop-color:#857c4d;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient893"> + <stop + id="stop894" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.27083334;" /> + <stop + id="stop895" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient841"> + <stop + id="stop842" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + <stop + id="stop844" + offset="0.50379843" + style="stop-color:#dadada;stop-opacity:1.0000000;" /> + <stop + id="stop845" + offset="0.51379842" + style="stop-color:#bdbdbd;stop-opacity:1.0000000;" /> + <stop + id="stop846" + offset="0.64667326" + style="stop-color:#dedede;stop-opacity:1.0000000;" /> + <stop + id="stop843" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient836"> + <stop + id="stop837" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:0.00000000;" /> + <stop + id="stop838" + offset="1" + style="stop-color:#fff;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="0.19090909" + x2="1.1454545" + xlink:href="#linearGradient832" + y1="0.68421054" + y2="-0.17105263" /> + <linearGradient + id="linearGradient839" + x1="0.47235259" + x2="0.47235259" + xlink:href="#linearGradient836" + y1="0.39059740" + y2="0.013744113" /> + <radialGradient + cx="0.50000000" + cy="0.50000000" + fx="0.51298690" + fy="0.092105433" + id="radialGradient840" + r="0.50000000" + xlink:href="#linearGradient1397" /> + <linearGradient + id="linearGradient860" + x1="0.21710530" + x2="0.89436638" + xlink:href="#linearGradient832" + y1="0.74342090" + y2="-0.33333325" /> + <linearGradient + id="linearGradient863" + x1="0.52739727" + x2="0.65068495" + xlink:href="#linearGradient836" + y1="0.48611110" + y2="-0.041666668" /> + <linearGradient + id="linearGradient891" + x1="0.12500000" + x2="0.82894737" + xlink:href="#linearGradient836" + y1="1.0986842" + y2="0.13815789" /> + <linearGradient + id="linearGradient892" + x1="-0.11404288" + x2="-0.061766334" + xlink:href="#linearGradient896" + y1="0.24721514" + y2="2.5462053" /> + <linearGradient + id="linearGradient900" + x1="0.37142858" + x2="0.11428571" + xlink:href="#linearGradient836" + y1="0.63888890" + y2="1.0416666" /> + <linearGradient + id="linearGradient905" + x1="1.3074018" + x2="1.3074018" + xlink:href="#linearGradient893" + y1="1.7768639" + y2="0.11690380" /> + <linearGradient + id="linearGradient906" + x1="-0.42276084" + x2="-0.42276084" + xlink:href="#linearGradient893" + y1="1.8603847" + y2="0.20042460" /> + <linearGradient + id="linearGradient908" + x1="0.50352114" + x2="0.21478873" + xlink:href="#linearGradient832" + y1="0.44615385" + y2="1.1615385" /> + <linearGradient + id="linearGradient910" + x1="0.45422536" + x2="0.69594592" + xlink:href="#linearGradient836" + y1="0.50000000" + y2="-0.078947365" /> + <linearGradient + id="linearGradient911" + x1="1.1710526" + x2="-2.2763157" + xlink:href="#linearGradient896" + y1="0.16447368" + y2="1.5986842" /> + <linearGradient + id="linearGradient912" + x1="0.67222220" + x2="0.25000000" + xlink:href="#linearGradient832" + y1="0.30167598" + y2="0.44692737" /> + <radialGradient + cx="0.48684204" + cy="0.44078955" + fx="0.53289479" + fy="0.013157940" + id="radialGradient1402" + r="0.76976496" + xlink:href="#linearGradient841" /> + <radialGradient + cx="0.48684210" + cy="0.46052632" + fx="0.52631575" + fy="0.71710521" + id="radialGradient1415" + r="0.76976496" + xlink:href="#linearGradient1416" /> + </defs> + <sodipodi:namedview + bordercolor="#666666" + borderopacity="1.0" + id="base" + inkscape:cx="72.909285" + inkscape:cy="75.399464" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:window-height="575" + inkscape:window-width="797" + inkscape:window-x="76" + inkscape:window-y="454" + inkscape:zoom="2.4559706" + pagecolor="#ffffff" + inkscape:current-layer="svg1" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path855" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1402);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-92.18625,-774.3955)" + inkscape:export-filename="/home/steve/Documents/remote/images/down.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path1414" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1415);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-91.90522,-774.4678)" + inkscape:export-filename="/home/steve/Documents/remote/images/down.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 184.98434 527.64008 A 29.511122 29.511122 0 1 0 125.96210,527.64008 A 29.511122 29.511122 0 1 0 184.98434 527.64008 z" + id="path856" + sodipodi:cx="155.47322" + sodipodi:cy="527.64008" + sodipodi:rx="29.511122" + sodipodi:ry="29.511122" + sodipodi:type="arc" + style="fill:url(#linearGradient839);fill-opacity:1;fill-rule:evenodd;stroke-width:1.0000000pt;stroke-opacity:0.37190083;" + transform="matrix(1.291670,0.000000,0.000000,1.524596,-118.6605,-740.1552)" + inkscape:export-filename="/home/steve/Documents/remote/images/down.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 361.33127,396.63946 C 361.33127,460.21074 309.73720,511.80481 246.16592,511.80481 C 182.59465,511.80481 131.00057,460.21074 131.00057,396.63946 C 131.00057,333.06819 182.59465,281.47411 246.16592,281.47411 C 309.73720,281.47411 361.33127,333.06819 361.33127,396.63946 z " + id="path862" + sodipodi:insensitive="true" + style="fill:url(#linearGradient863);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:1.0000000pt;" /> + <path + d="M 55.941329,56.455672 L 107.14521,56.021852 L 82.637595,91.240215 L 55.941329,56.455672 z " + id="path1440" + sodipodi:nodetypes="cccc" + style="fill:url(#linearGradient835);fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:5.1250000;stroke-linecap:round;stroke-linejoin:round;stroke-opacity:0.27272728;" + inkscape:export-filename="/home/steve/Documents/remote/images/down.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> +</svg> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/fast_forward.svg b/abs/core-testing/local-website/htdocs/remote/svg/fast_forward.svg new file mode 100644 index 0000000..a19f70a --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/fast_forward.svg @@ -0,0 +1,406 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + height="128.00000pt" + id="svg1" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Documents/remote/svg" + sodipodi:docname="fast_forward.svg" + sodipodi:version="0.32" + width="128.00000pt" + inkscape:export-filename="/home/steve/Documents/remote/images/skip_forward.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90"> + <metadata + id="metadata1718"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:title>Etiquette Icons</dc:title> + <dc:description /> + <dc:subject> + <rdf:Bag> + <rdf:li>hash</rdf:li> + <rdf:li /> + <rdf:li>action</rdf:li> + <rdf:li>computer</rdf:li> + <rdf:li>icons</rdf:li> + <rdf:li>buttons</rdf:li> + </rdf:Bag> + </dc:subject> + <dc:publisher> + <cc:Agent + rdf:about="http://www.openclipart.org"> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:publisher> + <dc:creator> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:creator> + <dc:rights> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:rights> + <dc:date /> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <cc:license + rdf:resource="http://web.resource.org/cc/PublicDomain" /> + <dc:language>en</dc:language> + </cc:Work> + <cc:License + rdf:about="http://web.resource.org/cc/PublicDomain"> + <cc:permits + rdf:resource="http://web.resource.org/cc/Reproduction" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/Distribution" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> + </cc:License> + </rdf:RDF> + </metadata> + <defs + id="defs3"> + <linearGradient + id="linearGradient1416"> + <stop + id="stop1417" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1419" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1418" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient1397"> + <stop + id="stop1398" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.53725493;" /> + <stop + id="stop1400" + offset="0.50000000" + style="stop-color:#ffffff;stop-opacity:0.26666668;" /> + <stop + id="stop1401" + offset="0.75000000" + style="stop-color:#000000;stop-opacity:0.13333334;" /> + <stop + id="stop1399" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient896"> + <stop + id="stop897" + offset="0.00000000" + style="stop-color:#e2d9a9;stop-opacity:1.0000000;" /> + <stop + id="stop898" + offset="1.0000000" + style="stop-color:#857c4d;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient893"> + <stop + id="stop894" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.27083334;" /> + <stop + id="stop895" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient841"> + <stop + id="stop842" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + <stop + id="stop844" + offset="0.50379843" + style="stop-color:#dadada;stop-opacity:1.0000000;" /> + <stop + id="stop845" + offset="0.51379842" + style="stop-color:#bdbdbd;stop-opacity:1.0000000;" /> + <stop + id="stop846" + offset="0.64667326" + style="stop-color:#dedede;stop-opacity:1.0000000;" /> + <stop + id="stop843" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient836"> + <stop + id="stop837" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:0.00000000;" /> + <stop + id="stop838" + offset="1" + style="stop-color:#fff;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="54.705607" + x2="100.20946" + xlink:href="#linearGradient832" + y1="80.75058" + y2="39.97958" + gradientTransform="matrix(0,1.181625,-0.846293,0,137.4075,-15.14529)" + gradientUnits="userSpaceOnUse" /> + <linearGradient + id="linearGradient839" + x1="153.84141" + x2="153.84141" + xlink:href="#linearGradient836" + y1="521.18289" + y2="498.94016" + gradientUnits="userSpaceOnUse" /> + <radialGradient + cx="0.50000000" + cy="0.50000000" + fx="0.51298690" + fy="0.092105433" + id="radialGradient840" + r="0.50000000" + xlink:href="#linearGradient1397" /> + <linearGradient + id="linearGradient860" + x1="0.21710530" + x2="0.89436638" + xlink:href="#linearGradient832" + y1="0.74342090" + y2="-0.33333325" /> + <linearGradient + id="linearGradient863" + x1="0.52739727" + x2="0.65068495" + xlink:href="#linearGradient836" + y1="0.48611110" + y2="-0.041666668" /> + <linearGradient + id="linearGradient891" + x1="0.12500000" + x2="0.82894737" + xlink:href="#linearGradient836" + y1="1.0986842" + y2="0.13815789" /> + <linearGradient + id="linearGradient892" + x1="-0.11404288" + x2="-0.061766334" + xlink:href="#linearGradient896" + y1="0.24721514" + y2="2.5462053" /> + <linearGradient + id="linearGradient900" + x1="0.37142858" + x2="0.11428571" + xlink:href="#linearGradient836" + y1="0.63888890" + y2="1.0416666" /> + <linearGradient + id="linearGradient905" + x1="1.3074018" + x2="1.3074018" + xlink:href="#linearGradient893" + y1="1.7768639" + y2="0.11690380" /> + <linearGradient + id="linearGradient906" + x1="-0.42276084" + x2="-0.42276084" + xlink:href="#linearGradient893" + y1="1.8603847" + y2="0.20042460" /> + <linearGradient + id="linearGradient908" + x1="0.50352114" + x2="0.21478873" + xlink:href="#linearGradient832" + y1="0.44615385" + y2="1.1615385" /> + <linearGradient + id="linearGradient910" + x1="0.45422536" + x2="0.69594592" + xlink:href="#linearGradient836" + y1="0.50000000" + y2="-0.078947365" /> + <linearGradient + id="linearGradient911" + x1="1.1710526" + x2="-2.2763157" + xlink:href="#linearGradient896" + y1="0.16447368" + y2="1.5986842" /> + <linearGradient + id="linearGradient912" + x1="0.67222220" + x2="0.25000000" + xlink:href="#linearGradient832" + y1="0.30167598" + y2="0.44692737" /> + <radialGradient + cx="99.330109" + cy="480.49422" + fx="101.84936" + fy="457.10126" + id="radialGradient1402" + r="42.108869" + xlink:href="#linearGradient841" + gradientUnits="userSpaceOnUse" /> + <radialGradient + cx="99.330112" + cy="481.5739" + fx="101.48946" + fy="495.60967" + id="radialGradient1415" + r="42.108869" + xlink:href="#linearGradient1416" + gradientUnits="userSpaceOnUse" /> + <linearGradient + inkscape:collect="always" + xlink:href="#linearGradient832" + id="linearGradient2532" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0,1.181625,-0.846293,0,161.6985,-15.09932)" + x1="54.705607" + y1="80.75058" + x2="100.20946" + y2="39.97958" /> + </defs> + <sodipodi:namedview + bordercolor="#666666" + borderopacity="1.0" + id="base" + inkscape:cx="94.389377" + inkscape:cy="96.874111" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:window-height="923" + inkscape:window-width="968" + inkscape:window-x="349" + inkscape:window-y="76" + inkscape:zoom="6.9465339" + pagecolor="#ffffff" + inkscape:current-layer="svg1" + showguides="true" + inkscape:guide-bbox="true"> + <sodipodi:guide + orientation="vertical" + position="80.619858" + id="guide1772" /> + <sodipodi:guide + orientation="horizontal" + position="91.988323" + id="guide2428" /> + <sodipodi:guide + orientation="horizontal" + position="121.21153" + id="guide2430" /> + <sodipodi:guide + orientation="horizontal" + position="64.780509" + id="guide2432" /> + </sodipodi:namedview> + <path + d="M 127.40167 483.73325 A 27.35177 27.35177 0 1 1 72.698126,483.73325 A 27.35177 27.35177 0 1 1 127.40167 483.73325 z" + id="path855" + sodipodi:cx="100.0499" + sodipodi:cy="483.73325" + sodipodi:rx="27.35177" + sodipodi:ry="27.35177" + sodipodi:type="arc" + style="fill:url(#radialGradient1402);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:3.08127832;stroke-dasharray:none;stroke-opacity:0.37190085" + transform="matrix(1.736345,0,0,1.736345,-92.18625,-774.3955)" + inkscape:export-filename="/home/steve/Documents/remote/images/skip_forward.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 127.40167 483.73325 A 27.35177 27.35177 0 1 1 72.698126,483.73325 A 27.35177 27.35177 0 1 1 127.40167 483.73325 z" + id="path1414" + sodipodi:cx="100.0499" + sodipodi:cy="483.73325" + sodipodi:rx="27.35177" + sodipodi:ry="27.35177" + sodipodi:type="arc" + style="fill:url(#radialGradient1415);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:3.08127832;stroke-dasharray:none;stroke-opacity:0.37190085" + transform="matrix(1.736345,0,0,1.736345,-91.90522,-774.4678)" + inkscape:export-filename="/home/steve/Documents/remote/images/skip_forward.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 184.98434 527.64008 A 29.511122 29.511122 0 1 1 125.9621,527.64008 A 29.511122 29.511122 0 1 1 184.98434 527.64008 z" + id="path856" + sodipodi:cx="155.47322" + sodipodi:cy="527.64008" + sodipodi:rx="29.511122" + sodipodi:ry="29.511122" + sodipodi:type="arc" + style="fill:url(#linearGradient839);fill-opacity:1;fill-rule:evenodd;stroke-width:1pt;stroke-opacity:0.37190085" + transform="matrix(1.29167,0,0,1.524596,-118.6605,-740.1552)" + inkscape:export-filename="/home/steve/Documents/remote/images/skip_forward.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 361.33127,396.63946 C 361.33127,460.21074 309.73720,511.80481 246.16592,511.80481 C 182.59465,511.80481 131.00057,460.21074 131.00057,396.63946 C 131.00057,333.06819 182.59465,281.47411 246.16592,281.47411 C 309.73720,281.47411 361.33127,333.06819 361.33127,396.63946 z " + id="path862" + sodipodi:insensitive="true" + style="fill:url(#linearGradient863);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:1.0000000pt;" /> + <path + d="M 59.325123,41.305001 L 58.891303,92.508878 L 94.109663,68.001267 L 59.325123,41.305001 z " + id="path1440" + sodipodi:nodetypes="cccc" + style="fill:url(#linearGradient835);fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:5.125;stroke-linecap:round;stroke-linejoin:round;stroke-opacity:0.27272728" + inkscape:export-filename="/home/steve/Documents/remote/images/skip_forward.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 83.616178,41.35097 L 83.182358,92.554847 L 118.40072,68.047236 L 83.616178,41.35097 z " + id="path2530" + sodipodi:nodetypes="cccc" + style="fill:url(#linearGradient2532);fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:5.125;stroke-linecap:round;stroke-linejoin:round;stroke-opacity:0.27272728" + inkscape:export-filename="/home/steve/Documents/remote/images/skip_forward.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> +</svg> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/fast_rewind.svg b/abs/core-testing/local-website/htdocs/remote/svg/fast_rewind.svg new file mode 100644 index 0000000..fe872e4 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/fast_rewind.svg @@ -0,0 +1,406 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + height="128.00000pt" + id="svg1" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Documents/remote/svg" + sodipodi:docname="fast_rewind.svg" + sodipodi:version="0.32" + width="128.00000pt" + inkscape:export-filename="/home/steve/Documents/remote/images/skip_forward.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90"> + <metadata + id="metadata1718"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:title>Etiquette Icons</dc:title> + <dc:description /> + <dc:subject> + <rdf:Bag> + <rdf:li>hash</rdf:li> + <rdf:li /> + <rdf:li>action</rdf:li> + <rdf:li>computer</rdf:li> + <rdf:li>icons</rdf:li> + <rdf:li>buttons</rdf:li> + </rdf:Bag> + </dc:subject> + <dc:publisher> + <cc:Agent + rdf:about="http://www.openclipart.org"> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:publisher> + <dc:creator> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:creator> + <dc:rights> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:rights> + <dc:date /> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <cc:license + rdf:resource="http://web.resource.org/cc/PublicDomain" /> + <dc:language>en</dc:language> + </cc:Work> + <cc:License + rdf:about="http://web.resource.org/cc/PublicDomain"> + <cc:permits + rdf:resource="http://web.resource.org/cc/Reproduction" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/Distribution" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> + </cc:License> + </rdf:RDF> + </metadata> + <defs + id="defs3"> + <linearGradient + id="linearGradient1416"> + <stop + id="stop1417" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1419" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1418" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient1397"> + <stop + id="stop1398" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.53725493;" /> + <stop + id="stop1400" + offset="0.50000000" + style="stop-color:#ffffff;stop-opacity:0.26666668;" /> + <stop + id="stop1401" + offset="0.75000000" + style="stop-color:#000000;stop-opacity:0.13333334;" /> + <stop + id="stop1399" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient896"> + <stop + id="stop897" + offset="0.00000000" + style="stop-color:#e2d9a9;stop-opacity:1.0000000;" /> + <stop + id="stop898" + offset="1.0000000" + style="stop-color:#857c4d;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient893"> + <stop + id="stop894" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.27083334;" /> + <stop + id="stop895" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient841"> + <stop + id="stop842" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + <stop + id="stop844" + offset="0.50379843" + style="stop-color:#dadada;stop-opacity:1.0000000;" /> + <stop + id="stop845" + offset="0.51379842" + style="stop-color:#bdbdbd;stop-opacity:1.0000000;" /> + <stop + id="stop846" + offset="0.64667326" + style="stop-color:#dedede;stop-opacity:1.0000000;" /> + <stop + id="stop843" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient836"> + <stop + id="stop837" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:0.00000000;" /> + <stop + id="stop838" + offset="1" + style="stop-color:#fff;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="54.705607" + x2="100.20946" + xlink:href="#linearGradient832" + y1="80.75058" + y2="39.97958" + gradientTransform="matrix(0,1.181625,0.846293,0,27.88452,-15.14529)" + gradientUnits="userSpaceOnUse" /> + <linearGradient + id="linearGradient839" + x1="153.84141" + x2="153.84141" + xlink:href="#linearGradient836" + y1="521.18289" + y2="498.94016" + gradientUnits="userSpaceOnUse" /> + <radialGradient + cx="0.50000000" + cy="0.50000000" + fx="0.51298690" + fy="0.092105433" + id="radialGradient840" + r="0.50000000" + xlink:href="#linearGradient1397" /> + <linearGradient + id="linearGradient860" + x1="0.21710530" + x2="0.89436638" + xlink:href="#linearGradient832" + y1="0.74342090" + y2="-0.33333325" /> + <linearGradient + id="linearGradient863" + x1="0.52739727" + x2="0.65068495" + xlink:href="#linearGradient836" + y1="0.48611110" + y2="-0.041666668" /> + <linearGradient + id="linearGradient891" + x1="0.12500000" + x2="0.82894737" + xlink:href="#linearGradient836" + y1="1.0986842" + y2="0.13815789" /> + <linearGradient + id="linearGradient892" + x1="-0.11404288" + x2="-0.061766334" + xlink:href="#linearGradient896" + y1="0.24721514" + y2="2.5462053" /> + <linearGradient + id="linearGradient900" + x1="0.37142858" + x2="0.11428571" + xlink:href="#linearGradient836" + y1="0.63888890" + y2="1.0416666" /> + <linearGradient + id="linearGradient905" + x1="1.3074018" + x2="1.3074018" + xlink:href="#linearGradient893" + y1="1.7768639" + y2="0.11690380" /> + <linearGradient + id="linearGradient906" + x1="-0.42276084" + x2="-0.42276084" + xlink:href="#linearGradient893" + y1="1.8603847" + y2="0.20042460" /> + <linearGradient + id="linearGradient908" + x1="0.50352114" + x2="0.21478873" + xlink:href="#linearGradient832" + y1="0.44615385" + y2="1.1615385" /> + <linearGradient + id="linearGradient910" + x1="0.45422536" + x2="0.69594592" + xlink:href="#linearGradient836" + y1="0.50000000" + y2="-0.078947365" /> + <linearGradient + id="linearGradient911" + x1="1.1710526" + x2="-2.2763157" + xlink:href="#linearGradient896" + y1="0.16447368" + y2="1.5986842" /> + <linearGradient + id="linearGradient912" + x1="0.67222220" + x2="0.25000000" + xlink:href="#linearGradient832" + y1="0.30167598" + y2="0.44692737" /> + <radialGradient + cx="99.330109" + cy="480.49422" + fx="101.84936" + fy="457.10126" + id="radialGradient1402" + r="42.108869" + xlink:href="#linearGradient841" + gradientUnits="userSpaceOnUse" /> + <radialGradient + cx="99.330112" + cy="481.5739" + fx="101.48946" + fy="495.60967" + id="radialGradient1415" + r="42.108869" + xlink:href="#linearGradient1416" + gradientUnits="userSpaceOnUse" /> + <linearGradient + inkscape:collect="always" + xlink:href="#linearGradient832" + id="linearGradient2532" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0,1.181625,0.846293,0,3.59352,-15.09932)" + x1="54.705607" + y1="80.75058" + x2="100.20946" + y2="39.97958" /> + </defs> + <sodipodi:namedview + bordercolor="#666666" + borderopacity="1.0" + id="base" + inkscape:cx="94.389377" + inkscape:cy="96.874111" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:window-height="923" + inkscape:window-width="968" + inkscape:window-x="349" + inkscape:window-y="76" + inkscape:zoom="6.9465339" + pagecolor="#ffffff" + inkscape:current-layer="svg1" + showguides="true" + inkscape:guide-bbox="true"> + <sodipodi:guide + orientation="vertical" + position="80.619858" + id="guide1772" /> + <sodipodi:guide + orientation="horizontal" + position="91.988323" + id="guide2428" /> + <sodipodi:guide + orientation="horizontal" + position="121.21153" + id="guide2430" /> + <sodipodi:guide + orientation="horizontal" + position="64.780509" + id="guide2432" /> + </sodipodi:namedview> + <path + d="M 127.40167 483.73325 A 27.35177 27.35177 0 1 1 72.698126,483.73325 A 27.35177 27.35177 0 1 1 127.40167 483.73325 z" + id="path855" + sodipodi:cx="100.0499" + sodipodi:cy="483.73325" + sodipodi:rx="27.35177" + sodipodi:ry="27.35177" + sodipodi:type="arc" + style="fill:url(#radialGradient1402);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:3.08127832;stroke-dasharray:none;stroke-opacity:0.37190085" + transform="matrix(1.736345,0,0,1.736345,-92.18625,-774.3955)" + inkscape:export-filename="/home/steve/Documents/remote/images/fast_rewind.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 127.40167 483.73325 A 27.35177 27.35177 0 1 1 72.698126,483.73325 A 27.35177 27.35177 0 1 1 127.40167 483.73325 z" + id="path1414" + sodipodi:cx="100.0499" + sodipodi:cy="483.73325" + sodipodi:rx="27.35177" + sodipodi:ry="27.35177" + sodipodi:type="arc" + style="fill:url(#radialGradient1415);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:3.08127832;stroke-dasharray:none;stroke-opacity:0.37190085" + transform="matrix(1.736345,0,0,1.736345,-91.90522,-774.4678)" + inkscape:export-filename="/home/steve/Documents/remote/images/fast_rewind.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 184.98434 527.64008 A 29.511122 29.511122 0 1 1 125.9621,527.64008 A 29.511122 29.511122 0 1 1 184.98434 527.64008 z" + id="path856" + sodipodi:cx="155.47322" + sodipodi:cy="527.64008" + sodipodi:rx="29.511122" + sodipodi:ry="29.511122" + sodipodi:type="arc" + style="fill:url(#linearGradient839);fill-opacity:1;fill-rule:evenodd;stroke-width:1pt;stroke-opacity:0.37190085" + transform="matrix(1.29167,0,0,1.524596,-118.6605,-740.1552)" + inkscape:export-filename="/home/steve/Documents/remote/images/fast_rewind.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 361.33127,396.63946 C 361.33127,460.21074 309.73720,511.80481 246.16592,511.80481 C 182.59465,511.80481 131.00057,460.21074 131.00057,396.63946 C 131.00057,333.06819 182.59465,281.47411 246.16592,281.47411 C 309.73720,281.47411 361.33127,333.06819 361.33127,396.63946 z " + id="path862" + sodipodi:insensitive="true" + style="fill:url(#linearGradient863);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:1.0000000pt;" /> + <path + d="M 105.9669,41.305001 L 106.40072,92.508878 L 71.18236,68.001267 L 105.9669,41.305001 z " + id="path1440" + sodipodi:nodetypes="cccc" + style="fill:url(#linearGradient835);fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:5.125;stroke-linecap:round;stroke-linejoin:round;stroke-opacity:0.27272728" + inkscape:export-filename="/home/steve/Documents/remote/images/fast_rewind.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 81.675845,41.35097 L 82.109665,92.554847 L 46.891303,68.047236 L 81.675845,41.35097 z " + id="path2530" + sodipodi:nodetypes="cccc" + style="fill:url(#linearGradient2532);fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:5.125;stroke-linecap:round;stroke-linejoin:round;stroke-opacity:0.27272728" + inkscape:export-filename="/home/steve/Documents/remote/images/fast_rewind.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> +</svg> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/left.svg b/abs/core-testing/local-website/htdocs/remote/svg/left.svg new file mode 100644 index 0000000..fdaec7e --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/left.svg @@ -0,0 +1,358 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + height="128.00000pt" + id="svg1" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Downloads/buttons" + sodipodi:docname="left.svg" + sodipodi:version="0.32" + width="128.00000pt"> + <metadata + id="metadata1718"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:title>Etiquette Icons</dc:title> + <dc:description /> + <dc:subject> + <rdf:Bag> + <rdf:li>hash</rdf:li> + <rdf:li /> + <rdf:li>action</rdf:li> + <rdf:li>computer</rdf:li> + <rdf:li>icons</rdf:li> + <rdf:li>buttons</rdf:li> + </rdf:Bag> + </dc:subject> + <dc:publisher> + <cc:Agent + rdf:about="http://www.openclipart.org"> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:publisher> + <dc:creator> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:creator> + <dc:rights> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:rights> + <dc:date /> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <cc:license + rdf:resource="http://web.resource.org/cc/PublicDomain" /> + <dc:language>en</dc:language> + </cc:Work> + <cc:License + rdf:about="http://web.resource.org/cc/PublicDomain"> + <cc:permits + rdf:resource="http://web.resource.org/cc/Reproduction" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/Distribution" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> + </cc:License> + </rdf:RDF> + </metadata> + <defs + id="defs3"> + <linearGradient + id="linearGradient1416"> + <stop + id="stop1417" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1419" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1418" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient1397"> + <stop + id="stop1398" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.53725493;" /> + <stop + id="stop1400" + offset="0.50000000" + style="stop-color:#ffffff;stop-opacity:0.26666668;" /> + <stop + id="stop1401" + offset="0.75000000" + style="stop-color:#000000;stop-opacity:0.13333334;" /> + <stop + id="stop1399" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient896"> + <stop + id="stop897" + offset="0.00000000" + style="stop-color:#e2d9a9;stop-opacity:1.0000000;" /> + <stop + id="stop898" + offset="1.0000000" + style="stop-color:#857c4d;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient893"> + <stop + id="stop894" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.27083334;" /> + <stop + id="stop895" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient841"> + <stop + id="stop842" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + <stop + id="stop844" + offset="0.50379843" + style="stop-color:#dadada;stop-opacity:1.0000000;" /> + <stop + id="stop845" + offset="0.51379842" + style="stop-color:#bdbdbd;stop-opacity:1.0000000;" /> + <stop + id="stop846" + offset="0.64667326" + style="stop-color:#dedede;stop-opacity:1.0000000;" /> + <stop + id="stop843" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient836"> + <stop + id="stop837" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:0.00000000;" /> + <stop + id="stop838" + offset="1" + style="stop-color:#fff;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="54.705607" + x2="100.20946" + xlink:href="#linearGradient832" + y1="80.75058" + y2="39.97958" + gradientTransform="matrix(0,1.181625,0.846293,0,15.14526,-15.14529)" + gradientUnits="userSpaceOnUse" /> + <linearGradient + id="linearGradient839" + x1="0.47235259" + x2="0.47235259" + xlink:href="#linearGradient836" + y1="0.39059740" + y2="0.013744113" /> + <radialGradient + cx="0.50000000" + cy="0.50000000" + fx="0.51298690" + fy="0.092105433" + id="radialGradient840" + r="0.50000000" + xlink:href="#linearGradient1397" /> + <linearGradient + id="linearGradient860" + x1="0.21710530" + x2="0.89436638" + xlink:href="#linearGradient832" + y1="0.74342090" + y2="-0.33333325" /> + <linearGradient + id="linearGradient863" + x1="0.52739727" + x2="0.65068495" + xlink:href="#linearGradient836" + y1="0.48611110" + y2="-0.041666668" /> + <linearGradient + id="linearGradient891" + x1="0.12500000" + x2="0.82894737" + xlink:href="#linearGradient836" + y1="1.0986842" + y2="0.13815789" /> + <linearGradient + id="linearGradient892" + x1="-0.11404288" + x2="-0.061766334" + xlink:href="#linearGradient896" + y1="0.24721514" + y2="2.5462053" /> + <linearGradient + id="linearGradient900" + x1="0.37142858" + x2="0.11428571" + xlink:href="#linearGradient836" + y1="0.63888890" + y2="1.0416666" /> + <linearGradient + id="linearGradient905" + x1="1.3074018" + x2="1.3074018" + xlink:href="#linearGradient893" + y1="1.7768639" + y2="0.11690380" /> + <linearGradient + id="linearGradient906" + x1="-0.42276084" + x2="-0.42276084" + xlink:href="#linearGradient893" + y1="1.8603847" + y2="0.20042460" /> + <linearGradient + id="linearGradient908" + x1="0.50352114" + x2="0.21478873" + xlink:href="#linearGradient832" + y1="0.44615385" + y2="1.1615385" /> + <linearGradient + id="linearGradient910" + x1="0.45422536" + x2="0.69594592" + xlink:href="#linearGradient836" + y1="0.50000000" + y2="-0.078947365" /> + <linearGradient + id="linearGradient911" + x1="1.1710526" + x2="-2.2763157" + xlink:href="#linearGradient896" + y1="0.16447368" + y2="1.5986842" /> + <linearGradient + id="linearGradient912" + x1="0.67222220" + x2="0.25000000" + xlink:href="#linearGradient832" + y1="0.30167598" + y2="0.44692737" /> + <radialGradient + cx="0.48684204" + cy="0.44078955" + fx="0.53289479" + fy="0.013157940" + id="radialGradient1402" + r="0.76976496" + xlink:href="#linearGradient841" /> + <radialGradient + cx="0.48684210" + cy="0.46052632" + fx="0.52631575" + fy="0.71710521" + id="radialGradient1415" + r="0.76976496" + xlink:href="#linearGradient1416" /> + </defs> + <sodipodi:namedview + bordercolor="#666666" + borderopacity="1.0" + id="base" + inkscape:cx="72.909285" + inkscape:cy="75.399464" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:window-height="575" + inkscape:window-width="797" + inkscape:window-x="447" + inkscape:window-y="416" + inkscape:zoom="2.4559706" + pagecolor="#ffffff" + inkscape:current-layer="svg1" + showguides="true" + inkscape:guide-bbox="true"> + <sodipodi:guide + orientation="vertical" + position="80.619858" + id="guide1772" /> + </sodipodi:namedview> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path855" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1402);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-92.18625,-774.3955)" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path1414" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1415);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-91.90522,-774.4678)" /> + <path + d="M 184.98434 527.64008 A 29.511122 29.511122 0 1 0 125.96210,527.64008 A 29.511122 29.511122 0 1 0 184.98434 527.64008 z" + id="path856" + sodipodi:cx="155.47322" + sodipodi:cy="527.64008" + sodipodi:rx="29.511122" + sodipodi:ry="29.511122" + sodipodi:type="arc" + style="fill:url(#linearGradient839);fill-opacity:1;fill-rule:evenodd;stroke-width:1.0000000pt;stroke-opacity:0.37190083;" + transform="matrix(1.291670,0.000000,0.000000,1.524596,-118.6605,-740.1552)" /> + <path + d="M 361.33127,396.63946 C 361.33127,460.21074 309.73720,511.80481 246.16592,511.80481 C 182.59465,511.80481 131.00057,460.21074 131.00057,396.63946 C 131.00057,333.06819 182.59465,281.47411 246.16592,281.47411 C 309.73720,281.47411 361.33127,333.06819 361.33127,396.63946 z " + id="path862" + sodipodi:insensitive="true" + style="fill:url(#linearGradient863);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:1.0000000pt;" /> + <path + d="M 93.22759,41.305001 L 93.66141,92.508878 L 58.44305,68.001267 L 93.22759,41.305001 z " + id="path1440" + sodipodi:nodetypes="cccc" + style="fill:url(#linearGradient835);fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:5.125;stroke-linecap:round;stroke-linejoin:round;stroke-opacity:0.27272728" /> +</svg> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/ok.svg b/abs/core-testing/local-website/htdocs/remote/svg/ok.svg new file mode 100644 index 0000000..22975ff --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/ok.svg @@ -0,0 +1,378 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + height="128.00000pt" + id="svg1" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Documents/remote/images" + sodipodi:docname="ok.svg" + sodipodi:version="0.32" + width="128.00000pt"> + <metadata + id="metadata1718"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:title>Etiquette Icons</dc:title> + <dc:description /> + <dc:subject> + <rdf:Bag> + <rdf:li>hash</rdf:li> + <rdf:li /> + <rdf:li>action</rdf:li> + <rdf:li>computer</rdf:li> + <rdf:li>icons</rdf:li> + <rdf:li>buttons</rdf:li> + </rdf:Bag> + </dc:subject> + <dc:publisher> + <cc:Agent + rdf:about="http://www.openclipart.org"> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:publisher> + <dc:creator> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:creator> + <dc:rights> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:rights> + <dc:date /> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <cc:license + rdf:resource="http://web.resource.org/cc/PublicDomain" /> + <dc:language>en</dc:language> + </cc:Work> + <cc:License + rdf:about="http://web.resource.org/cc/PublicDomain"> + <cc:permits + rdf:resource="http://web.resource.org/cc/Reproduction" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/Distribution" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> + </cc:License> + </rdf:RDF> + </metadata> + <defs + id="defs3"> + <linearGradient + id="linearGradient1416"> + <stop + id="stop1417" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1419" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1418" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient1397"> + <stop + id="stop1398" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.53725493;" /> + <stop + id="stop1400" + offset="0.50000000" + style="stop-color:#ffffff;stop-opacity:0.26666668;" /> + <stop + id="stop1401" + offset="0.75000000" + style="stop-color:#000000;stop-opacity:0.13333334;" /> + <stop + id="stop1399" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient896"> + <stop + id="stop897" + offset="0.00000000" + style="stop-color:#e2d9a9;stop-opacity:1.0000000;" /> + <stop + id="stop898" + offset="1.0000000" + style="stop-color:#857c4d;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient893"> + <stop + id="stop894" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.27083334;" /> + <stop + id="stop895" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient841"> + <stop + id="stop842" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + <stop + id="stop844" + offset="0.50379843" + style="stop-color:#dadada;stop-opacity:1.0000000;" /> + <stop + id="stop845" + offset="0.51379842" + style="stop-color:#bdbdbd;stop-opacity:1.0000000;" /> + <stop + id="stop846" + offset="0.64667326" + style="stop-color:#dedede;stop-opacity:1.0000000;" /> + <stop + id="stop843" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient836"> + <stop + id="stop837" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:0.00000000;" /> + <stop + id="stop838" + offset="1" + style="stop-color:#fff;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="0.19090909" + x2="1.1454545" + xlink:href="#linearGradient832" + y1="0.68421054" + y2="-0.17105263" /> + <linearGradient + id="linearGradient839" + x1="0.47235259" + x2="0.47235259" + xlink:href="#linearGradient836" + y1="0.39059740" + y2="0.013744113" /> + <radialGradient + cx="0.50000000" + cy="0.50000000" + fx="0.51298690" + fy="0.092105433" + id="radialGradient840" + r="0.50000000" + xlink:href="#linearGradient1397" /> + <linearGradient + id="linearGradient860" + x1="0.21710530" + x2="0.89436638" + xlink:href="#linearGradient832" + y1="0.74342090" + y2="-0.33333325" /> + <linearGradient + id="linearGradient863" + x1="0.52739727" + x2="0.65068495" + xlink:href="#linearGradient836" + y1="0.48611110" + y2="-0.041666668" /> + <linearGradient + id="linearGradient891" + x1="0.12500000" + x2="0.82894737" + xlink:href="#linearGradient836" + y1="1.0986842" + y2="0.13815789" /> + <linearGradient + id="linearGradient892" + x1="-0.11404288" + x2="-0.061766334" + xlink:href="#linearGradient896" + y1="0.24721514" + y2="2.5462053" /> + <linearGradient + id="linearGradient900" + x1="0.37142858" + x2="0.11428571" + xlink:href="#linearGradient836" + y1="0.63888890" + y2="1.0416666" /> + <linearGradient + id="linearGradient905" + x1="1.3074018" + x2="1.3074018" + xlink:href="#linearGradient893" + y1="1.7768639" + y2="0.11690380" /> + <linearGradient + id="linearGradient906" + x1="-0.42276084" + x2="-0.42276084" + xlink:href="#linearGradient893" + y1="1.8603847" + y2="0.20042460" /> + <linearGradient + id="linearGradient908" + x1="0.50352114" + x2="0.21478873" + xlink:href="#linearGradient832" + y1="0.44615385" + y2="1.1615385" /> + <linearGradient + id="linearGradient910" + x1="0.45422536" + x2="0.69594592" + xlink:href="#linearGradient836" + y1="0.50000000" + y2="-0.078947365" /> + <linearGradient + id="linearGradient911" + x1="1.1710526" + x2="-2.2763157" + xlink:href="#linearGradient896" + y1="0.16447368" + y2="1.5986842" /> + <linearGradient + id="linearGradient912" + x1="0.67222220" + x2="0.25000000" + xlink:href="#linearGradient832" + y1="0.30167598" + y2="0.44692737" /> + <radialGradient + cx="0.48684204" + cy="0.44078955" + fx="0.53289479" + fy="0.013157940" + id="radialGradient1402" + r="0.76976496" + xlink:href="#linearGradient841" /> + <radialGradient + cx="0.48684210" + cy="0.46052632" + fx="0.52631575" + fy="0.71710521" + id="radialGradient1415" + r="0.76976496" + xlink:href="#linearGradient1416" /> + </defs> + <sodipodi:namedview + bordercolor="#666666" + borderopacity="1.0" + id="base" + inkscape:cx="73.286607" + inkscape:cy="76.149307" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:window-height="575" + inkscape:window-width="797" + inkscape:window-x="396" + inkscape:window-y="218" + inkscape:zoom="2.4559706" + pagecolor="#ffffff" + inkscape:current-layer="svg1" + showguides="true" + inkscape:guide-bbox="true"> + <sodipodi:guide + orientation="vertical" + position="81.027029" + id="guide2290" /> + <sodipodi:guide + orientation="horizontal" + position="94.463672" + id="guide2292" /> + </sodipodi:namedview> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path855" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1402);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-92.18625,-774.3955)" + inkscape:export-filename="/home/steve/Documents/remote/images/ok.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path1414" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1415);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-91.90522,-774.4678)" + inkscape:export-filename="/home/steve/Documents/remote/images/ok.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 184.98434 527.64008 A 29.511122 29.511122 0 1 0 125.96210,527.64008 A 29.511122 29.511122 0 1 0 184.98434 527.64008 z" + id="path856" + sodipodi:cx="155.47322" + sodipodi:cy="527.64008" + sodipodi:rx="29.511122" + sodipodi:ry="29.511122" + sodipodi:type="arc" + style="fill:url(#linearGradient839);fill-opacity:1;fill-rule:evenodd;stroke-width:1.0000000pt;stroke-opacity:0.37190083;" + transform="matrix(1.291670,0.000000,0.000000,1.524596,-118.6605,-740.1552)" + inkscape:export-filename="/home/steve/Documents/remote/images/ok.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 361.33127,396.63946 C 361.33127,460.21074 309.73720,511.80481 246.16592,511.80481 C 182.59465,511.80481 131.00057,460.21074 131.00057,396.63946 C 131.00057,333.06819 182.59465,281.47411 246.16592,281.47411 C 309.73720,281.47411 361.33127,333.06819 361.33127,396.63946 z " + id="path862" + sodipodi:insensitive="true" + style="fill:url(#linearGradient863);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:1.0000000pt;" /> + <text + xml:space="preserve" + style="font-size:40px;font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;text-align:center;line-height:110.00000238%;writing-mode:lr-tb;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Vera Sans" + x="79.470055" + y="80.67337" + id="text2286" + sodipodi:linespacing="110%" + inkscape:export-filename="/home/steve/Documents/remote/images/ok.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90"><tspan + sodipodi:role="line" + id="tspan2288" + x="79.470055" + y="80.67337">OK</tspan></text> +</svg> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/pause.svg b/abs/core-testing/local-website/htdocs/remote/svg/pause.svg new file mode 100644 index 0000000..26fcc74 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/pause.svg @@ -0,0 +1,410 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + height="128.00000pt" + id="svg1" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Documents/remote/svg" + sodipodi:docname="pause.svg" + sodipodi:version="0.32" + width="128.00000pt"> + <metadata + id="metadata1718"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:title>Etiquette Icons</dc:title> + <dc:description /> + <dc:subject> + <rdf:Bag> + <rdf:li>hash</rdf:li> + <rdf:li /> + <rdf:li>action</rdf:li> + <rdf:li>computer</rdf:li> + <rdf:li>icons</rdf:li> + <rdf:li>buttons</rdf:li> + </rdf:Bag> + </dc:subject> + <dc:publisher> + <cc:Agent + rdf:about="http://www.openclipart.org"> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:publisher> + <dc:creator> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:creator> + <dc:rights> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:rights> + <dc:date /> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <cc:license + rdf:resource="http://web.resource.org/cc/PublicDomain" /> + <dc:language>en</dc:language> + </cc:Work> + <cc:License + rdf:about="http://web.resource.org/cc/PublicDomain"> + <cc:permits + rdf:resource="http://web.resource.org/cc/Reproduction" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/Distribution" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> + </cc:License> + </rdf:RDF> + </metadata> + <defs + id="defs3"> + <linearGradient + id="linearGradient1416"> + <stop + id="stop1417" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1419" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1418" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient1397"> + <stop + id="stop1398" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.53725493;" /> + <stop + id="stop1400" + offset="0.50000000" + style="stop-color:#ffffff;stop-opacity:0.26666668;" /> + <stop + id="stop1401" + offset="0.75000000" + style="stop-color:#000000;stop-opacity:0.13333334;" /> + <stop + id="stop1399" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient896"> + <stop + id="stop897" + offset="0.00000000" + style="stop-color:#e2d9a9;stop-opacity:1.0000000;" /> + <stop + id="stop898" + offset="1.0000000" + style="stop-color:#857c4d;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient893"> + <stop + id="stop894" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.27083334;" /> + <stop + id="stop895" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient841"> + <stop + id="stop842" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + <stop + id="stop844" + offset="0.50379843" + style="stop-color:#dadada;stop-opacity:1.0000000;" /> + <stop + id="stop845" + offset="0.51379842" + style="stop-color:#bdbdbd;stop-opacity:1.0000000;" /> + <stop + id="stop846" + offset="0.64667326" + style="stop-color:#dedede;stop-opacity:1.0000000;" /> + <stop + id="stop843" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient836"> + <stop + id="stop837" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:0.00000000;" /> + <stop + id="stop838" + offset="1" + style="stop-color:#fff;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="54.705607" + x2="100.20946" + xlink:href="#linearGradient832" + y1="80.75058" + y2="39.97958" + gradientTransform="matrix(0,1.181625,-0.846293,0,146.9592,-15.14529)" + gradientUnits="userSpaceOnUse" /> + <linearGradient + id="linearGradient839" + x1="0.47235259" + x2="0.47235259" + xlink:href="#linearGradient836" + y1="0.39059740" + y2="0.013744113" /> + <radialGradient + cx="0.50000000" + cy="0.50000000" + fx="0.51298690" + fy="0.092105433" + id="radialGradient840" + r="0.50000000" + xlink:href="#linearGradient1397" /> + <linearGradient + id="linearGradient860" + x1="0.21710530" + x2="0.89436638" + xlink:href="#linearGradient832" + y1="0.74342090" + y2="-0.33333325" /> + <linearGradient + id="linearGradient863" + x1="0.52739727" + x2="0.65068495" + xlink:href="#linearGradient836" + y1="0.48611110" + y2="-0.041666668" /> + <linearGradient + id="linearGradient891" + x1="0.12500000" + x2="0.82894737" + xlink:href="#linearGradient836" + y1="1.0986842" + y2="0.13815789" /> + <linearGradient + id="linearGradient892" + x1="-0.11404288" + x2="-0.061766334" + xlink:href="#linearGradient896" + y1="0.24721514" + y2="2.5462053" /> + <linearGradient + id="linearGradient900" + x1="0.37142858" + x2="0.11428571" + xlink:href="#linearGradient836" + y1="0.63888890" + y2="1.0416666" /> + <linearGradient + id="linearGradient905" + x1="1.3074018" + x2="1.3074018" + xlink:href="#linearGradient893" + y1="1.7768639" + y2="0.11690380" /> + <linearGradient + id="linearGradient906" + x1="-0.42276084" + x2="-0.42276084" + xlink:href="#linearGradient893" + y1="1.8603847" + y2="0.20042460" /> + <linearGradient + id="linearGradient908" + x1="0.50352114" + x2="0.21478873" + xlink:href="#linearGradient832" + y1="0.44615385" + y2="1.1615385" /> + <linearGradient + id="linearGradient910" + x1="0.45422536" + x2="0.69594592" + xlink:href="#linearGradient836" + y1="0.50000000" + y2="-0.078947365" /> + <linearGradient + id="linearGradient911" + x1="1.1710526" + x2="-2.2763157" + xlink:href="#linearGradient896" + y1="0.16447368" + y2="1.5986842" /> + <linearGradient + id="linearGradient912" + x1="0.67222220" + x2="0.25000000" + xlink:href="#linearGradient832" + y1="0.30167598" + y2="0.44692737" /> + <radialGradient + cx="0.48684204" + cy="0.44078955" + fx="0.53289479" + fy="0.013157940" + id="radialGradient1402" + r="0.76976496" + xlink:href="#linearGradient841" /> + <radialGradient + cx="0.48684210" + cy="0.46052632" + fx="0.52631575" + fy="0.71710521" + id="radialGradient1415" + r="0.76976496" + xlink:href="#linearGradient1416" /> + </defs> + <sodipodi:namedview + bordercolor="#666666" + borderopacity="1.0" + id="base" + inkscape:cx="20.644188" + inkscape:cy="81.910525" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:window-height="820" + inkscape:window-width="1110" + inkscape:window-x="215" + inkscape:window-y="166" + inkscape:zoom="3.4732669" + pagecolor="#ffffff" + inkscape:current-layer="svg1" + showguides="true" + inkscape:guide-bbox="true"> + <sodipodi:guide + orientation="vertical" + position="80.619858" + id="guide1772" /> + <sodipodi:guide + orientation="horizontal" + position="121.13337" + id="guide2608" /> + </sodipodi:namedview> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path855" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1402);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-92.18625,-774.3955)" + inkscape:export-filename="/home/steve/Documents/remote/images/right.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path1414" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1415);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-91.90522,-774.4678)" + inkscape:export-filename="/home/steve/Documents/remote/images/right.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 184.98434 527.64008 A 29.511122 29.511122 0 1 0 125.96210,527.64008 A 29.511122 29.511122 0 1 0 184.98434 527.64008 z" + id="path856" + sodipodi:cx="155.47322" + sodipodi:cy="527.64008" + sodipodi:rx="29.511122" + sodipodi:ry="29.511122" + sodipodi:type="arc" + style="fill:url(#linearGradient839);fill-opacity:1;fill-rule:evenodd;stroke-width:1.0000000pt;stroke-opacity:0.37190083;" + transform="matrix(1.291670,0.000000,0.000000,1.524596,-118.6605,-740.1552)" + inkscape:export-filename="/home/steve/Documents/remote/images/right.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 361.33127,396.63946 C 361.33127,460.21074 309.73720,511.80481 246.16592,511.80481 C 182.59465,511.80481 131.00057,460.21074 131.00057,396.63946 C 131.00057,333.06819 182.59465,281.47411 246.16592,281.47411 C 309.73720,281.47411 361.33127,333.06819 361.33127,396.63946 z " + id="path862" + sodipodi:insensitive="true" + style="fill:url(#linearGradient863);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:1.0000000pt;" /> + <g + id="g2421" + transform="matrix(1.604618,0,0,1,-475.3725,-472.9867)"> + <rect + rx="1.6131665" + ry="4.8613596" + y="511.93057" + x="335.1181" + height="56.442268" + width="8.0812206" + id="rect2386" + style="fill:#bababa;fill-opacity:1" /> + <rect + ry="4.8613596" + rx="1.6131665" + y="513.82458" + x="337.01215" + height="52.906738" + width="4.2931485" + id="rect2398" + style="fill:#323232;fill-opacity:1" /> + </g> + <g + id="g2596" + transform="matrix(1.705388,0,0,1,-484.7837,-472.9867)"> + <rect + rx="1.517846" + ry="4.8613596" + y="511.93057" + x="335.1181" + height="56.442268" + width="8.0812206" + id="rect2598" + style="fill:#bababa;fill-opacity:1" /> + <rect + ry="4.8613596" + rx="1.517846" + y="513.82458" + x="337.01215" + height="52.906738" + width="4.2931485" + id="rect2600" + style="fill:#323232;fill-opacity:1" /> + </g> +</svg> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/rec.svg b/abs/core-testing/local-website/htdocs/remote/svg/rec.svg new file mode 100644 index 0000000..bc3cd54 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/rec.svg @@ -0,0 +1,395 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + height="128.00000pt" + id="svg1" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Documents/remote/svg" + sodipodi:docname="rec.svg" + sodipodi:version="0.32" + width="128.00000pt" + inkscape:export-filename="/home/steve/Documents/remote/images/pause.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90"> + <metadata + id="metadata1718"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:title>Etiquette Icons</dc:title> + <dc:description /> + <dc:subject> + <rdf:Bag> + <rdf:li>hash</rdf:li> + <rdf:li /> + <rdf:li>action</rdf:li> + <rdf:li>computer</rdf:li> + <rdf:li>icons</rdf:li> + <rdf:li>buttons</rdf:li> + </rdf:Bag> + </dc:subject> + <dc:publisher> + <cc:Agent + rdf:about="http://www.openclipart.org"> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:publisher> + <dc:creator> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:creator> + <dc:rights> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:rights> + <dc:date /> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <cc:license + rdf:resource="http://web.resource.org/cc/PublicDomain" /> + <dc:language>en</dc:language> + </cc:Work> + <cc:License + rdf:about="http://web.resource.org/cc/PublicDomain"> + <cc:permits + rdf:resource="http://web.resource.org/cc/Reproduction" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/Distribution" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> + </cc:License> + </rdf:RDF> + </metadata> + <defs + id="defs3"> + <linearGradient + id="linearGradient1416"> + <stop + id="stop1417" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1419" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1418" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient1397"> + <stop + id="stop1398" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.53725493;" /> + <stop + id="stop1400" + offset="0.50000000" + style="stop-color:#ffffff;stop-opacity:0.26666668;" /> + <stop + id="stop1401" + offset="0.75000000" + style="stop-color:#000000;stop-opacity:0.13333334;" /> + <stop + id="stop1399" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient896"> + <stop + id="stop897" + offset="0.00000000" + style="stop-color:#e2d9a9;stop-opacity:1.0000000;" /> + <stop + id="stop898" + offset="1.0000000" + style="stop-color:#857c4d;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient893"> + <stop + id="stop894" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.27083334;" /> + <stop + id="stop895" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient841"> + <stop + id="stop842" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + <stop + id="stop844" + offset="0.50379843" + style="stop-color:#dadada;stop-opacity:1.0000000;" /> + <stop + id="stop845" + offset="0.51379842" + style="stop-color:#bdbdbd;stop-opacity:1.0000000;" /> + <stop + id="stop846" + offset="0.64667326" + style="stop-color:#dedede;stop-opacity:1.0000000;" /> + <stop + id="stop843" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient836"> + <stop + id="stop837" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:0.00000000;" /> + <stop + id="stop838" + offset="1" + style="stop-color:#fff;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="54.705607" + x2="100.20946" + xlink:href="#linearGradient832" + y1="80.75058" + y2="39.97958" + gradientTransform="matrix(0,1.181625,-0.846293,0,146.9592,-15.14529)" + gradientUnits="userSpaceOnUse" /> + <linearGradient + id="linearGradient839" + x1="0.47235259" + x2="0.47235259" + xlink:href="#linearGradient836" + y1="0.39059740" + y2="0.013744113" /> + <radialGradient + cx="0.50000000" + cy="0.50000000" + fx="0.51298690" + fy="0.092105433" + id="radialGradient840" + r="0.50000000" + xlink:href="#linearGradient1397" /> + <linearGradient + id="linearGradient860" + x1="0.21710530" + x2="0.89436638" + xlink:href="#linearGradient832" + y1="0.74342090" + y2="-0.33333325" /> + <linearGradient + id="linearGradient863" + x1="0.52739727" + x2="0.65068495" + xlink:href="#linearGradient836" + y1="0.48611110" + y2="-0.041666668" /> + <linearGradient + id="linearGradient891" + x1="0.12500000" + x2="0.82894737" + xlink:href="#linearGradient836" + y1="1.0986842" + y2="0.13815789" /> + <linearGradient + id="linearGradient892" + x1="-0.11404288" + x2="-0.061766334" + xlink:href="#linearGradient896" + y1="0.24721514" + y2="2.5462053" /> + <linearGradient + id="linearGradient900" + x1="0.37142858" + x2="0.11428571" + xlink:href="#linearGradient836" + y1="0.63888890" + y2="1.0416666" /> + <linearGradient + id="linearGradient905" + x1="1.3074018" + x2="1.3074018" + xlink:href="#linearGradient893" + y1="1.7768639" + y2="0.11690380" /> + <linearGradient + id="linearGradient906" + x1="-0.42276084" + x2="-0.42276084" + xlink:href="#linearGradient893" + y1="1.8603847" + y2="0.20042460" /> + <linearGradient + id="linearGradient908" + x1="0.50352114" + x2="0.21478873" + xlink:href="#linearGradient832" + y1="0.44615385" + y2="1.1615385" /> + <linearGradient + id="linearGradient910" + x1="0.45422536" + x2="0.69594592" + xlink:href="#linearGradient836" + y1="0.50000000" + y2="-0.078947365" /> + <linearGradient + id="linearGradient911" + x1="1.1710526" + x2="-2.2763157" + xlink:href="#linearGradient896" + y1="0.16447368" + y2="1.5986842" /> + <linearGradient + id="linearGradient912" + x1="0.67222220" + x2="0.25000000" + xlink:href="#linearGradient832" + y1="0.30167598" + y2="0.44692737" /> + <radialGradient + cx="0.48684204" + cy="0.44078955" + fx="0.53289479" + fy="0.013157940" + id="radialGradient1402" + r="0.76976496" + xlink:href="#linearGradient841" /> + <radialGradient + cx="0.48684210" + cy="0.46052632" + fx="0.52631575" + fy="0.71710521" + id="radialGradient1415" + r="0.76976496" + xlink:href="#linearGradient1416" /> + </defs> + <sodipodi:namedview + bordercolor="#666666" + borderopacity="1.0" + id="base" + inkscape:cx="55.960102" + inkscape:cy="90.990883" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:window-height="820" + inkscape:window-width="1110" + inkscape:window-x="177" + inkscape:window-y="162" + inkscape:zoom="6.9465339" + pagecolor="#ffffff" + inkscape:current-layer="svg1" + showguides="true" + inkscape:guide-bbox="true"> + <sodipodi:guide + orientation="vertical" + position="80.619858" + id="guide1772" /> + <sodipodi:guide + orientation="horizontal" + position="93.283933" + id="guide2608" /> + </sodipodi:namedview> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path855" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1402);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-92.18625,-774.3955)" + inkscape:export-filename="/home/steve/Documents/remote/images/rec.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path1414" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1415);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-91.90522,-774.4678)" + inkscape:export-filename="/home/steve/Documents/remote/images/rec.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 184.98434 527.64008 A 29.511122 29.511122 0 1 0 125.96210,527.64008 A 29.511122 29.511122 0 1 0 184.98434 527.64008 z" + id="path856" + sodipodi:cx="155.47322" + sodipodi:cy="527.64008" + sodipodi:rx="29.511122" + sodipodi:ry="29.511122" + sodipodi:type="arc" + style="fill:url(#linearGradient839);fill-opacity:1;fill-rule:evenodd;stroke-width:1.0000000pt;stroke-opacity:0.37190083;" + transform="matrix(1.291670,0.000000,0.000000,1.524596,-118.6605,-740.1552)" + inkscape:export-filename="/home/steve/Documents/remote/images/rec.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 361.33127,396.63946 C 361.33127,460.21074 309.73720,511.80481 246.16592,511.80481 C 182.59465,511.80481 131.00057,460.21074 131.00057,396.63946 C 131.00057,333.06819 182.59465,281.47411 246.16592,281.47411 C 309.73720,281.47411 361.33127,333.06819 361.33127,396.63946 z " + id="path862" + sodipodi:insensitive="true" + style="fill:url(#linearGradient863);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:1.0000000pt;" /> + <path + sodipodi:type="arc" + style="fill:#bababa;fill-opacity:1" + id="path2618" + sodipodi:cx="566.25366" + sodipodi:cy="540.15173" + sodipodi:rx="28.221136" + sodipodi:ry="28.221136" + d="M 594.4748 540.15173 A 28.221136 28.221136 0 1 1 538.03253,540.15173 A 28.221136 28.221136 0 1 1 594.4748 540.15173 z" + transform="translate(-485.7818,-473.5794)" + inkscape:export-filename="/home/steve/Documents/remote/images/rec.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + sodipodi:type="arc" + style="fill:#ce401a;fill-opacity:1" + id="path2626" + sodipodi:cx="526.28949" + sodipodi:cy="539.96228" + sodipodi:rx="24.36993" + sodipodi:ry="24.36993" + d="M 550.65942 539.96228 A 24.36993 24.36993 0 1 1 501.91956,539.96228 A 24.36993 24.36993 0 1 1 550.65942 539.96228 z" + transform="matrix(1,0,0,1.010363,-445.7545,-479.0485)" + inkscape:export-filename="/home/steve/Documents/remote/images/rec.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> +</svg> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/right.svg b/abs/core-testing/local-website/htdocs/remote/svg/right.svg new file mode 100644 index 0000000..5873a44 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/right.svg @@ -0,0 +1,370 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + height="128.00000pt" + id="svg1" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Documents/remote" + sodipodi:docname="right.svg" + sodipodi:version="0.32" + width="128.00000pt"> + <metadata + id="metadata1718"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:title>Etiquette Icons</dc:title> + <dc:description /> + <dc:subject> + <rdf:Bag> + <rdf:li>hash</rdf:li> + <rdf:li /> + <rdf:li>action</rdf:li> + <rdf:li>computer</rdf:li> + <rdf:li>icons</rdf:li> + <rdf:li>buttons</rdf:li> + </rdf:Bag> + </dc:subject> + <dc:publisher> + <cc:Agent + rdf:about="http://www.openclipart.org"> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:publisher> + <dc:creator> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:creator> + <dc:rights> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:rights> + <dc:date /> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <cc:license + rdf:resource="http://web.resource.org/cc/PublicDomain" /> + <dc:language>en</dc:language> + </cc:Work> + <cc:License + rdf:about="http://web.resource.org/cc/PublicDomain"> + <cc:permits + rdf:resource="http://web.resource.org/cc/Reproduction" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/Distribution" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> + </cc:License> + </rdf:RDF> + </metadata> + <defs + id="defs3"> + <linearGradient + id="linearGradient1416"> + <stop + id="stop1417" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1419" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1418" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient1397"> + <stop + id="stop1398" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.53725493;" /> + <stop + id="stop1400" + offset="0.50000000" + style="stop-color:#ffffff;stop-opacity:0.26666668;" /> + <stop + id="stop1401" + offset="0.75000000" + style="stop-color:#000000;stop-opacity:0.13333334;" /> + <stop + id="stop1399" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient896"> + <stop + id="stop897" + offset="0.00000000" + style="stop-color:#e2d9a9;stop-opacity:1.0000000;" /> + <stop + id="stop898" + offset="1.0000000" + style="stop-color:#857c4d;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient893"> + <stop + id="stop894" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.27083334;" /> + <stop + id="stop895" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient841"> + <stop + id="stop842" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + <stop + id="stop844" + offset="0.50379843" + style="stop-color:#dadada;stop-opacity:1.0000000;" /> + <stop + id="stop845" + offset="0.51379842" + style="stop-color:#bdbdbd;stop-opacity:1.0000000;" /> + <stop + id="stop846" + offset="0.64667326" + style="stop-color:#dedede;stop-opacity:1.0000000;" /> + <stop + id="stop843" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient836"> + <stop + id="stop837" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:0.00000000;" /> + <stop + id="stop838" + offset="1" + style="stop-color:#fff;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="54.705607" + x2="100.20946" + xlink:href="#linearGradient832" + y1="80.75058" + y2="39.97958" + gradientTransform="matrix(0,1.181625,-0.846293,0,146.9592,-15.14529)" + gradientUnits="userSpaceOnUse" /> + <linearGradient + id="linearGradient839" + x1="0.47235259" + x2="0.47235259" + xlink:href="#linearGradient836" + y1="0.39059740" + y2="0.013744113" /> + <radialGradient + cx="0.50000000" + cy="0.50000000" + fx="0.51298690" + fy="0.092105433" + id="radialGradient840" + r="0.50000000" + xlink:href="#linearGradient1397" /> + <linearGradient + id="linearGradient860" + x1="0.21710530" + x2="0.89436638" + xlink:href="#linearGradient832" + y1="0.74342090" + y2="-0.33333325" /> + <linearGradient + id="linearGradient863" + x1="0.52739727" + x2="0.65068495" + xlink:href="#linearGradient836" + y1="0.48611110" + y2="-0.041666668" /> + <linearGradient + id="linearGradient891" + x1="0.12500000" + x2="0.82894737" + xlink:href="#linearGradient836" + y1="1.0986842" + y2="0.13815789" /> + <linearGradient + id="linearGradient892" + x1="-0.11404288" + x2="-0.061766334" + xlink:href="#linearGradient896" + y1="0.24721514" + y2="2.5462053" /> + <linearGradient + id="linearGradient900" + x1="0.37142858" + x2="0.11428571" + xlink:href="#linearGradient836" + y1="0.63888890" + y2="1.0416666" /> + <linearGradient + id="linearGradient905" + x1="1.3074018" + x2="1.3074018" + xlink:href="#linearGradient893" + y1="1.7768639" + y2="0.11690380" /> + <linearGradient + id="linearGradient906" + x1="-0.42276084" + x2="-0.42276084" + xlink:href="#linearGradient893" + y1="1.8603847" + y2="0.20042460" /> + <linearGradient + id="linearGradient908" + x1="0.50352114" + x2="0.21478873" + xlink:href="#linearGradient832" + y1="0.44615385" + y2="1.1615385" /> + <linearGradient + id="linearGradient910" + x1="0.45422536" + x2="0.69594592" + xlink:href="#linearGradient836" + y1="0.50000000" + y2="-0.078947365" /> + <linearGradient + id="linearGradient911" + x1="1.1710526" + x2="-2.2763157" + xlink:href="#linearGradient896" + y1="0.16447368" + y2="1.5986842" /> + <linearGradient + id="linearGradient912" + x1="0.67222220" + x2="0.25000000" + xlink:href="#linearGradient832" + y1="0.30167598" + y2="0.44692737" /> + <radialGradient + cx="0.48684204" + cy="0.44078955" + fx="0.53289479" + fy="0.013157940" + id="radialGradient1402" + r="0.76976496" + xlink:href="#linearGradient841" /> + <radialGradient + cx="0.48684210" + cy="0.46052632" + fx="0.52631575" + fy="0.71710521" + id="radialGradient1415" + r="0.76976496" + xlink:href="#linearGradient1416" /> + </defs> + <sodipodi:namedview + bordercolor="#666666" + borderopacity="1.0" + id="base" + inkscape:cx="72.909285" + inkscape:cy="75.399464" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:window-height="575" + inkscape:window-width="797" + inkscape:window-x="447" + inkscape:window-y="416" + inkscape:zoom="2.4559706" + pagecolor="#ffffff" + inkscape:current-layer="svg1" + showguides="true" + inkscape:guide-bbox="true"> + <sodipodi:guide + orientation="vertical" + position="80.619858" + id="guide1772" /> + </sodipodi:namedview> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path855" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1402);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-92.18625,-774.3955)" + inkscape:export-filename="/home/steve/Documents/remote/images/right.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path1414" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1415);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-91.90522,-774.4678)" + inkscape:export-filename="/home/steve/Documents/remote/images/right.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 184.98434 527.64008 A 29.511122 29.511122 0 1 0 125.96210,527.64008 A 29.511122 29.511122 0 1 0 184.98434 527.64008 z" + id="path856" + sodipodi:cx="155.47322" + sodipodi:cy="527.64008" + sodipodi:rx="29.511122" + sodipodi:ry="29.511122" + sodipodi:type="arc" + style="fill:url(#linearGradient839);fill-opacity:1;fill-rule:evenodd;stroke-width:1.0000000pt;stroke-opacity:0.37190083;" + transform="matrix(1.291670,0.000000,0.000000,1.524596,-118.6605,-740.1552)" + inkscape:export-filename="/home/steve/Documents/remote/images/right.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 361.33127,396.63946 C 361.33127,460.21074 309.73720,511.80481 246.16592,511.80481 C 182.59465,511.80481 131.00057,460.21074 131.00057,396.63946 C 131.00057,333.06819 182.59465,281.47411 246.16592,281.47411 C 309.73720,281.47411 361.33127,333.06819 361.33127,396.63946 z " + id="path862" + sodipodi:insensitive="true" + style="fill:url(#linearGradient863);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:1.0000000pt;" /> + <path + d="M 68.87687,41.305001 L 68.44305,92.508878 L 103.66141,68.001267 L 68.87687,41.305001 z " + id="path1440" + sodipodi:nodetypes="cccc" + style="fill:url(#linearGradient835);fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:5.125;stroke-linecap:round;stroke-linejoin:round;stroke-opacity:0.27272728" + inkscape:export-filename="/home/steve/Documents/remote/images/right.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> +</svg> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/scratch.svg b/abs/core-testing/local-website/htdocs/remote/svg/scratch.svg new file mode 100644 index 0000000..9da222b --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/scratch.svg @@ -0,0 +1,243 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + width="744.09448819" + height="1052.3622047" + id="svg2348" + sodipodi:version="0.32" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Documents/remote/svg" + sodipodi:docname="scratch.svg"> + <defs + id="defs2350"> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="54.705607" + x2="100.20946" + xlink:href="#linearGradient832" + y1="80.75058" + y2="39.97958" + gradientTransform="matrix(0,1.181625,0.846293,0,323.6894,451.8252)" + gradientUnits="userSpaceOnUse" /> + <linearGradient + inkscape:collect="always" + xlink:href="#linearGradient832" + id="linearGradient2363" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0,1.181625,0.846293,0,707.8879,925.0133)" + x1="54.705607" + y1="80.75058" + x2="100.20946" + y2="39.97958" /> + </defs> + <sodipodi:namedview + id="base" + pagecolor="#ffffff" + bordercolor="#666666" + borderopacity="1.0" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:zoom="7.9195959" + inkscape:cx="531.08711" + inkscape:cy="511.28536" + inkscape:document-units="px" + inkscape:current-layer="layer2" + showguides="true" + inkscape:guide-bbox="true" + inkscape:window-width="1312" + inkscape:window-height="918" + inkscape:window-x="5" + inkscape:window-y="51"> + <sodipodi:guide + orientation="horizontal" + position="540.43161" + id="guide2367" /> + <sodipodi:guide + orientation="horizontal" + position="483.98934" + id="guide2371" /> + <sodipodi:guide + orientation="horizontal" + position="536.89608" + id="guide2622" /> + <sodipodi:guide + orientation="vertical" + position="566.31677" + id="guide2624" /> + <sodipodi:guide + orientation="horizontal" + position="512.14734" + id="guide3501" /> + </sodipodi:namedview> + <metadata + id="metadata2353"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + </cc:Work> + </rdf:RDF> + </metadata> + <g + inkscape:label="Layer 1" + inkscape:groupmode="layer" + id="layer1"> + <path + d="M 477.42612,514.49307 L 477.85994,565.69695 L 442.64158,541.18933 L 477.42612,514.49307 z " + id="path1440" + sodipodi:nodetypes="cccc" + style="fill:url(#linearGradient2363);fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:5.125;stroke-linecap:round;stroke-linejoin:round;stroke-opacity:0.27272728" + inkscape:export-filename="/home/steve/Documents/remote/images/left.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <rect + style="fill:#cacaca;fill-opacity:1" + id="rect2369" + width="9.5964489" + height="6.8185296" + x="385.12067" + y="435.41153" /> + <rect + style="fill:#bababa;fill-opacity:1" + id="rect2381" + width="48.594997" + height="56.449001" + x="366.18121" + y="515.08051" + transform="matrix(0.999968,-8.050361e-3,-7.165447e-3,0.999974,0,0)" /> + <rect + style="fill:#bababa;fill-opacity:1" + id="rect2383" + width="5.177032" + height="56.442268" + x="354.43729" + y="511.93057" /> + <rect + style="fill:#ffffff;fill-opacity:1" + id="rect2610" + width="0.37880722" + height="7.5761414" + x="464.41763" + y="511.93057" /> + </g> + <g + inkscape:groupmode="layer" + id="layer2" + inkscape:label="me"> + <path + sodipodi:type="arc" + style="fill:#bababa;fill-opacity:1" + id="path2392" + sodipodi:cx="345.78784" + sodipodi:cy="515.21356" + sodipodi:rx="2.841054" + sodipodi:ry="0" + d="M 348.6289 515.21356 A 2.841054 0 0 1 1 342.94679,515.21356 A 2.841054 0 0 1 1 348.6289 515.21356 z" /> + <path + sodipodi:type="arc" + style="fill:#bababa;fill-opacity:1" + id="path2396" + sodipodi:cx="326.97375" + sodipodi:cy="513.88776" + sodipodi:rx="1.8309015" + sodipodi:ry="1.9571706" + d="M 328.80466,513.88776 A 1.8309015,1.9571706 0 1 1 328.38153,512.6364 L 326.97375,513.88776 z" + sodipodi:start="0" + sodipodi:end="5.5895056" /> + <g + id="g2421"> + <rect + rx="2.588516" + ry="4.8613596" + y="511.93057" + x="335.1181" + height="56.442268" + width="8.0812206" + id="rect2386" + style="fill:#bababa;fill-opacity:1" /> + <rect + ry="4.8613596" + rx="2.588516" + y="513.82458" + x="337.01215" + height="52.906738" + width="4.2931485" + id="rect2398" + style="fill:#323232;fill-opacity:1" /> + </g> + <g + id="g2602" + transform="matrix(1.328125,0,0,1,4.186576,1.73584e-6)"> + <rect + rx="1.9490002" + ry="4.8613596" + y="511.93057" + x="335.1181" + height="56.442268" + width="8.0812206" + id="rect2604" + style="fill:#bababa;fill-opacity:1" /> + <rect + ry="4.8613596" + rx="1.9490002" + y="513.82458" + x="337.01215" + height="52.906738" + width="4.2931485" + id="rect2606" + style="fill:#323232;fill-opacity:1" /> + </g> + <rect + style="fill:#323232;fill-opacity:1" + id="rect2612" + width="41.163712" + height="49.623737" + x="365.52863" + y="515.08734" /> + <path + sodipodi:type="arc" + style="fill:#bababa;fill-opacity:1" + id="path2618" + sodipodi:cx="566.25366" + sodipodi:cy="540.15173" + sodipodi:rx="28.221136" + sodipodi:ry="28.221136" + d="M 594.4748 540.15173 A 28.221136 28.221136 0 1 1 538.03253,540.15173 A 28.221136 28.221136 0 1 1 594.4748 540.15173 z" + transform="translate(-0.126269,-2.468811e-5)" /> + <path + sodipodi:type="arc" + style="fill:#ce401a;fill-opacity:1" + id="path2626" + sodipodi:cx="526.28949" + sodipodi:cy="539.96228" + sodipodi:rx="24.36993" + sodipodi:ry="24.36993" + d="M 550.65942 539.96228 A 24.36993 24.36993 0 1 1 501.91956,539.96228 A 24.36993 24.36993 0 1 1 550.65942 539.96228 z" + transform="matrix(1,0,0,1.010363,39.90103,-5.469173)" /> + </g> +</svg> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/skip_back.svg b/abs/core-testing/local-website/htdocs/remote/svg/skip_back.svg new file mode 100644 index 0000000..de35870 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/skip_back.svg @@ -0,0 +1,407 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + height="128.00000pt" + id="svg1" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Documents/remote/svg" + sodipodi:docname="skip_back.svg" + sodipodi:version="0.32" + width="128.00000pt"> + <metadata + id="metadata1718"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:title>Etiquette Icons</dc:title> + <dc:description /> + <dc:subject> + <rdf:Bag> + <rdf:li>hash</rdf:li> + <rdf:li /> + <rdf:li>action</rdf:li> + <rdf:li>computer</rdf:li> + <rdf:li>icons</rdf:li> + <rdf:li>buttons</rdf:li> + </rdf:Bag> + </dc:subject> + <dc:publisher> + <cc:Agent + rdf:about="http://www.openclipart.org"> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:publisher> + <dc:creator> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:creator> + <dc:rights> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:rights> + <dc:date /> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <cc:license + rdf:resource="http://web.resource.org/cc/PublicDomain" /> + <dc:language>en</dc:language> + </cc:Work> + <cc:License + rdf:about="http://web.resource.org/cc/PublicDomain"> + <cc:permits + rdf:resource="http://web.resource.org/cc/Reproduction" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/Distribution" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> + </cc:License> + </rdf:RDF> + </metadata> + <defs + id="defs3"> + <linearGradient + id="linearGradient1416"> + <stop + id="stop1417" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1419" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1418" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient1397"> + <stop + id="stop1398" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.53725493;" /> + <stop + id="stop1400" + offset="0.50000000" + style="stop-color:#ffffff;stop-opacity:0.26666668;" /> + <stop + id="stop1401" + offset="0.75000000" + style="stop-color:#000000;stop-opacity:0.13333334;" /> + <stop + id="stop1399" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient896"> + <stop + id="stop897" + offset="0.00000000" + style="stop-color:#e2d9a9;stop-opacity:1.0000000;" /> + <stop + id="stop898" + offset="1.0000000" + style="stop-color:#857c4d;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient893"> + <stop + id="stop894" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.27083334;" /> + <stop + id="stop895" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient841"> + <stop + id="stop842" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + <stop + id="stop844" + offset="0.50379843" + style="stop-color:#dadada;stop-opacity:1.0000000;" /> + <stop + id="stop845" + offset="0.51379842" + style="stop-color:#bdbdbd;stop-opacity:1.0000000;" /> + <stop + id="stop846" + offset="0.64667326" + style="stop-color:#dedede;stop-opacity:1.0000000;" /> + <stop + id="stop843" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient836"> + <stop + id="stop837" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:0.00000000;" /> + <stop + id="stop838" + offset="1" + style="stop-color:#fff;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="54.705607" + x2="100.20946" + xlink:href="#linearGradient832" + y1="80.75058" + y2="39.97958" + gradientTransform="matrix(0,1.181625,0.846293,0,21.14526,-15.14529)" + gradientUnits="userSpaceOnUse" /> + <linearGradient + id="linearGradient839" + x1="153.84141" + x2="153.84141" + xlink:href="#linearGradient836" + y1="521.18289" + y2="498.94016" + gradientUnits="userSpaceOnUse" /> + <radialGradient + cx="0.50000000" + cy="0.50000000" + fx="0.51298690" + fy="0.092105433" + id="radialGradient840" + r="0.50000000" + xlink:href="#linearGradient1397" /> + <linearGradient + id="linearGradient860" + x1="0.21710530" + x2="0.89436638" + xlink:href="#linearGradient832" + y1="0.74342090" + y2="-0.33333325" /> + <linearGradient + id="linearGradient863" + x1="0.52739727" + x2="0.65068495" + xlink:href="#linearGradient836" + y1="0.48611110" + y2="-0.041666668" /> + <linearGradient + id="linearGradient891" + x1="0.12500000" + x2="0.82894737" + xlink:href="#linearGradient836" + y1="1.0986842" + y2="0.13815789" /> + <linearGradient + id="linearGradient892" + x1="-0.11404288" + x2="-0.061766334" + xlink:href="#linearGradient896" + y1="0.24721514" + y2="2.5462053" /> + <linearGradient + id="linearGradient900" + x1="0.37142858" + x2="0.11428571" + xlink:href="#linearGradient836" + y1="0.63888890" + y2="1.0416666" /> + <linearGradient + id="linearGradient905" + x1="1.3074018" + x2="1.3074018" + xlink:href="#linearGradient893" + y1="1.7768639" + y2="0.11690380" /> + <linearGradient + id="linearGradient906" + x1="-0.42276084" + x2="-0.42276084" + xlink:href="#linearGradient893" + y1="1.8603847" + y2="0.20042460" /> + <linearGradient + id="linearGradient908" + x1="0.50352114" + x2="0.21478873" + xlink:href="#linearGradient832" + y1="0.44615385" + y2="1.1615385" /> + <linearGradient + id="linearGradient910" + x1="0.45422536" + x2="0.69594592" + xlink:href="#linearGradient836" + y1="0.50000000" + y2="-0.078947365" /> + <linearGradient + id="linearGradient911" + x1="1.1710526" + x2="-2.2763157" + xlink:href="#linearGradient896" + y1="0.16447368" + y2="1.5986842" /> + <linearGradient + id="linearGradient912" + x1="0.67222220" + x2="0.25000000" + xlink:href="#linearGradient832" + y1="0.30167598" + y2="0.44692737" /> + <radialGradient + cx="99.330109" + cy="480.49422" + fx="101.84936" + fy="457.10126" + id="radialGradient1402" + r="42.108869" + xlink:href="#linearGradient841" + gradientUnits="userSpaceOnUse" /> + <radialGradient + cx="99.330112" + cy="481.5739" + fx="101.48946" + fy="495.60967" + id="radialGradient1415" + r="42.108869" + xlink:href="#linearGradient1416" + gradientUnits="userSpaceOnUse" /> + </defs> + <sodipodi:namedview + bordercolor="#666666" + borderopacity="1.0" + id="base" + inkscape:cx="94.389377" + inkscape:cy="96.874111" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:window-height="923" + inkscape:window-width="968" + inkscape:window-x="349" + inkscape:window-y="76" + inkscape:zoom="6.9465339" + pagecolor="#ffffff" + inkscape:current-layer="svg1" + showguides="true" + inkscape:guide-bbox="true"> + <sodipodi:guide + orientation="vertical" + position="80.619858" + id="guide1772" /> + <sodipodi:guide + orientation="horizontal" + position="91.988323" + id="guide2428" /> + <sodipodi:guide + orientation="horizontal" + position="121.21153" + id="guide2430" /> + <sodipodi:guide + orientation="horizontal" + position="64.780509" + id="guide2432" /> + </sodipodi:namedview> + <path + d="M 127.40167 483.73325 A 27.35177 27.35177 0 1 1 72.698126,483.73325 A 27.35177 27.35177 0 1 1 127.40167 483.73325 z" + id="path855" + sodipodi:cx="100.0499" + sodipodi:cy="483.73325" + sodipodi:rx="27.35177" + sodipodi:ry="27.35177" + sodipodi:type="arc" + style="fill:url(#radialGradient1402);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:3.08127832;stroke-dasharray:none;stroke-opacity:0.37190085" + transform="matrix(1.736345,0,0,1.736345,-92.18625,-774.3955)" + inkscape:export-filename="/home/steve/Documents/remote/images/left.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 127.40167 483.73325 A 27.35177 27.35177 0 1 1 72.698126,483.73325 A 27.35177 27.35177 0 1 1 127.40167 483.73325 z" + id="path1414" + sodipodi:cx="100.0499" + sodipodi:cy="483.73325" + sodipodi:rx="27.35177" + sodipodi:ry="27.35177" + sodipodi:type="arc" + style="fill:url(#radialGradient1415);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:3.08127832;stroke-dasharray:none;stroke-opacity:0.37190085" + transform="matrix(1.736345,0,0,1.736345,-91.90522,-774.4678)" + inkscape:export-filename="/home/steve/Documents/remote/images/left.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 184.98434 527.64008 A 29.511122 29.511122 0 1 1 125.9621,527.64008 A 29.511122 29.511122 0 1 1 184.98434 527.64008 z" + id="path856" + sodipodi:cx="155.47322" + sodipodi:cy="527.64008" + sodipodi:rx="29.511122" + sodipodi:ry="29.511122" + sodipodi:type="arc" + style="fill:url(#linearGradient839);fill-opacity:1;fill-rule:evenodd;stroke-width:1pt;stroke-opacity:0.37190085" + transform="matrix(1.29167,0,0,1.524596,-118.6605,-740.1552)" + inkscape:export-filename="/home/steve/Documents/remote/images/left.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 361.33127,396.63946 C 361.33127,460.21074 309.73720,511.80481 246.16592,511.80481 C 182.59465,511.80481 131.00057,460.21074 131.00057,396.63946 C 131.00057,333.06819 182.59465,281.47411 246.16592,281.47411 C 309.73720,281.47411 361.33127,333.06819 361.33127,396.63946 z " + id="path862" + sodipodi:insensitive="true" + style="fill:url(#linearGradient863);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:1.0000000pt;" /> + <path + d="M 99.22759,41.305001 L 99.66141,92.508878 L 64.44305,68.001267 L 99.22759,41.305001 z " + id="path1440" + sodipodi:nodetypes="cccc" + style="fill:url(#linearGradient835);fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:5.125;stroke-linecap:round;stroke-linejoin:round;stroke-opacity:0.27272728" + inkscape:export-filename="/home/steve/Documents/remote/images/left.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <g + id="g2421" + transform="translate(-278.7893,-473.1082)"> + <rect + rx="2.588516" + ry="4.8613596" + y="511.93057" + x="335.1181" + height="56.442268" + width="8.0812206" + id="rect2386" + style="fill:#bababa;fill-opacity:1" /> + <rect + ry="4.8613596" + rx="2.588516" + y="513.82458" + x="337.01215" + height="52.906738" + width="4.2931485" + id="rect2398" + style="fill:#323232;fill-opacity:1" /> + </g> +</svg> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/skip_forward.svg b/abs/core-testing/local-website/htdocs/remote/svg/skip_forward.svg new file mode 100644 index 0000000..38bdc9c --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/skip_forward.svg @@ -0,0 +1,413 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + height="128.00000pt" + id="svg1" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Documents/remote/svg" + sodipodi:docname="skip_forward.svg" + sodipodi:version="0.32" + width="128.00000pt" + inkscape:export-filename="/home/steve/Documents/remote/images/skip_forward.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90"> + <metadata + id="metadata1718"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:title>Etiquette Icons</dc:title> + <dc:description /> + <dc:subject> + <rdf:Bag> + <rdf:li>hash</rdf:li> + <rdf:li /> + <rdf:li>action</rdf:li> + <rdf:li>computer</rdf:li> + <rdf:li>icons</rdf:li> + <rdf:li>buttons</rdf:li> + </rdf:Bag> + </dc:subject> + <dc:publisher> + <cc:Agent + rdf:about="http://www.openclipart.org"> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:publisher> + <dc:creator> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:creator> + <dc:rights> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:rights> + <dc:date /> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <cc:license + rdf:resource="http://web.resource.org/cc/PublicDomain" /> + <dc:language>en</dc:language> + </cc:Work> + <cc:License + rdf:about="http://web.resource.org/cc/PublicDomain"> + <cc:permits + rdf:resource="http://web.resource.org/cc/Reproduction" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/Distribution" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> + </cc:License> + </rdf:RDF> + </metadata> + <defs + id="defs3"> + <linearGradient + id="linearGradient1416"> + <stop + id="stop1417" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1419" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1418" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient1397"> + <stop + id="stop1398" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.53725493;" /> + <stop + id="stop1400" + offset="0.50000000" + style="stop-color:#ffffff;stop-opacity:0.26666668;" /> + <stop + id="stop1401" + offset="0.75000000" + style="stop-color:#000000;stop-opacity:0.13333334;" /> + <stop + id="stop1399" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient896"> + <stop + id="stop897" + offset="0.00000000" + style="stop-color:#e2d9a9;stop-opacity:1.0000000;" /> + <stop + id="stop898" + offset="1.0000000" + style="stop-color:#857c4d;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient893"> + <stop + id="stop894" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.27083334;" /> + <stop + id="stop895" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient841"> + <stop + id="stop842" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + <stop + id="stop844" + offset="0.50379843" + style="stop-color:#dadada;stop-opacity:1.0000000;" /> + <stop + id="stop845" + offset="0.51379842" + style="stop-color:#bdbdbd;stop-opacity:1.0000000;" /> + <stop + id="stop846" + offset="0.64667326" + style="stop-color:#dedede;stop-opacity:1.0000000;" /> + <stop + id="stop843" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient836"> + <stop + id="stop837" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:0.00000000;" /> + <stop + id="stop838" + offset="1" + style="stop-color:#fff;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="54.705607" + x2="100.20946" + xlink:href="#linearGradient832" + y1="80.75058" + y2="39.97958" + gradientTransform="matrix(0,1.181625,-0.846293,0,137.4075,-15.14529)" + gradientUnits="userSpaceOnUse" /> + <linearGradient + id="linearGradient839" + x1="153.84141" + x2="153.84141" + xlink:href="#linearGradient836" + y1="521.18289" + y2="498.94016" + gradientUnits="userSpaceOnUse" /> + <radialGradient + cx="0.50000000" + cy="0.50000000" + fx="0.51298690" + fy="0.092105433" + id="radialGradient840" + r="0.50000000" + xlink:href="#linearGradient1397" /> + <linearGradient + id="linearGradient860" + x1="0.21710530" + x2="0.89436638" + xlink:href="#linearGradient832" + y1="0.74342090" + y2="-0.33333325" /> + <linearGradient + id="linearGradient863" + x1="0.52739727" + x2="0.65068495" + xlink:href="#linearGradient836" + y1="0.48611110" + y2="-0.041666668" /> + <linearGradient + id="linearGradient891" + x1="0.12500000" + x2="0.82894737" + xlink:href="#linearGradient836" + y1="1.0986842" + y2="0.13815789" /> + <linearGradient + id="linearGradient892" + x1="-0.11404288" + x2="-0.061766334" + xlink:href="#linearGradient896" + y1="0.24721514" + y2="2.5462053" /> + <linearGradient + id="linearGradient900" + x1="0.37142858" + x2="0.11428571" + xlink:href="#linearGradient836" + y1="0.63888890" + y2="1.0416666" /> + <linearGradient + id="linearGradient905" + x1="1.3074018" + x2="1.3074018" + xlink:href="#linearGradient893" + y1="1.7768639" + y2="0.11690380" /> + <linearGradient + id="linearGradient906" + x1="-0.42276084" + x2="-0.42276084" + xlink:href="#linearGradient893" + y1="1.8603847" + y2="0.20042460" /> + <linearGradient + id="linearGradient908" + x1="0.50352114" + x2="0.21478873" + xlink:href="#linearGradient832" + y1="0.44615385" + y2="1.1615385" /> + <linearGradient + id="linearGradient910" + x1="0.45422536" + x2="0.69594592" + xlink:href="#linearGradient836" + y1="0.50000000" + y2="-0.078947365" /> + <linearGradient + id="linearGradient911" + x1="1.1710526" + x2="-2.2763157" + xlink:href="#linearGradient896" + y1="0.16447368" + y2="1.5986842" /> + <linearGradient + id="linearGradient912" + x1="0.67222220" + x2="0.25000000" + xlink:href="#linearGradient832" + y1="0.30167598" + y2="0.44692737" /> + <radialGradient + cx="99.330109" + cy="480.49422" + fx="101.84936" + fy="457.10126" + id="radialGradient1402" + r="42.108869" + xlink:href="#linearGradient841" + gradientUnits="userSpaceOnUse" /> + <radialGradient + cx="99.330112" + cy="481.5739" + fx="101.48946" + fy="495.60967" + id="radialGradient1415" + r="42.108869" + xlink:href="#linearGradient1416" + gradientUnits="userSpaceOnUse" /> + </defs> + <sodipodi:namedview + bordercolor="#666666" + borderopacity="1.0" + id="base" + inkscape:cx="94.389377" + inkscape:cy="96.874111" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:window-height="923" + inkscape:window-width="968" + inkscape:window-x="349" + inkscape:window-y="76" + inkscape:zoom="6.9465339" + pagecolor="#ffffff" + inkscape:current-layer="svg1" + showguides="true" + inkscape:guide-bbox="true"> + <sodipodi:guide + orientation="vertical" + position="80.619858" + id="guide1772" /> + <sodipodi:guide + orientation="horizontal" + position="91.988323" + id="guide2428" /> + <sodipodi:guide + orientation="horizontal" + position="121.21153" + id="guide2430" /> + <sodipodi:guide + orientation="horizontal" + position="64.780509" + id="guide2432" /> + </sodipodi:namedview> + <path + d="M 127.40167 483.73325 A 27.35177 27.35177 0 1 1 72.698126,483.73325 A 27.35177 27.35177 0 1 1 127.40167 483.73325 z" + id="path855" + sodipodi:cx="100.0499" + sodipodi:cy="483.73325" + sodipodi:rx="27.35177" + sodipodi:ry="27.35177" + sodipodi:type="arc" + style="fill:url(#radialGradient1402);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:3.08127832;stroke-dasharray:none;stroke-opacity:0.37190085" + transform="matrix(1.736345,0,0,1.736345,-92.18625,-774.3955)" + inkscape:export-filename="/home/steve/Documents/remote/images/skip_back.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 127.40167 483.73325 A 27.35177 27.35177 0 1 1 72.698126,483.73325 A 27.35177 27.35177 0 1 1 127.40167 483.73325 z" + id="path1414" + sodipodi:cx="100.0499" + sodipodi:cy="483.73325" + sodipodi:rx="27.35177" + sodipodi:ry="27.35177" + sodipodi:type="arc" + style="fill:url(#radialGradient1415);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:3.08127832;stroke-dasharray:none;stroke-opacity:0.37190085" + transform="matrix(1.736345,0,0,1.736345,-91.90522,-774.4678)" + inkscape:export-filename="/home/steve/Documents/remote/images/skip_back.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 184.98434 527.64008 A 29.511122 29.511122 0 1 1 125.9621,527.64008 A 29.511122 29.511122 0 1 1 184.98434 527.64008 z" + id="path856" + sodipodi:cx="155.47322" + sodipodi:cy="527.64008" + sodipodi:rx="29.511122" + sodipodi:ry="29.511122" + sodipodi:type="arc" + style="fill:url(#linearGradient839);fill-opacity:1;fill-rule:evenodd;stroke-width:1pt;stroke-opacity:0.37190085" + transform="matrix(1.29167,0,0,1.524596,-118.6605,-740.1552)" + inkscape:export-filename="/home/steve/Documents/remote/images/skip_back.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 361.33127,396.63946 C 361.33127,460.21074 309.73720,511.80481 246.16592,511.80481 C 182.59465,511.80481 131.00057,460.21074 131.00057,396.63946 C 131.00057,333.06819 182.59465,281.47411 246.16592,281.47411 C 309.73720,281.47411 361.33127,333.06819 361.33127,396.63946 z " + id="path862" + sodipodi:insensitive="true" + style="fill:url(#linearGradient863);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:1.0000000pt;" /> + <path + d="M 59.325123,41.305001 L 58.891303,92.508878 L 94.109663,68.001267 L 59.325123,41.305001 z " + id="path1440" + sodipodi:nodetypes="cccc" + style="fill:url(#linearGradient835);fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:5.125;stroke-linecap:round;stroke-linejoin:round;stroke-opacity:0.27272728" + inkscape:export-filename="/home/steve/Documents/remote/images/skip_back.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <g + id="g2421" + transform="matrix(-1,0,0,1,437.342,-473.1082)" + inkscape:export-filename="/home/steve/Documents/remote/images/skip_back.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90"> + <rect + rx="2.588516" + ry="4.8613596" + y="511.93057" + x="335.1181" + height="56.442268" + width="8.0812206" + id="rect2386" + style="fill:#bababa;fill-opacity:1" /> + <rect + ry="4.8613596" + rx="2.588516" + y="513.82458" + x="337.01215" + height="52.906738" + width="4.2931485" + id="rect2398" + style="fill:#323232;fill-opacity:1" /> + </g> +</svg> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/stop.svg b/abs/core-testing/local-website/htdocs/remote/svg/stop.svg new file mode 100644 index 0000000..f3d082d --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/stop.svg @@ -0,0 +1,384 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + height="128.00000pt" + id="svg1" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Documents/remote/svg" + sodipodi:docname="stop.svg" + sodipodi:version="0.32" + width="128.00000pt" + inkscape:export-filename="/home/steve/Documents/remote/images/pause.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90"> + <metadata + id="metadata1718"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:title>Etiquette Icons</dc:title> + <dc:description /> + <dc:subject> + <rdf:Bag> + <rdf:li>hash</rdf:li> + <rdf:li /> + <rdf:li>action</rdf:li> + <rdf:li>computer</rdf:li> + <rdf:li>icons</rdf:li> + <rdf:li>buttons</rdf:li> + </rdf:Bag> + </dc:subject> + <dc:publisher> + <cc:Agent + rdf:about="http://www.openclipart.org"> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:publisher> + <dc:creator> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:creator> + <dc:rights> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:rights> + <dc:date /> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <cc:license + rdf:resource="http://web.resource.org/cc/PublicDomain" /> + <dc:language>en</dc:language> + </cc:Work> + <cc:License + rdf:about="http://web.resource.org/cc/PublicDomain"> + <cc:permits + rdf:resource="http://web.resource.org/cc/Reproduction" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/Distribution" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> + </cc:License> + </rdf:RDF> + </metadata> + <defs + id="defs3"> + <linearGradient + id="linearGradient1416"> + <stop + id="stop1417" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1419" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1418" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient1397"> + <stop + id="stop1398" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.53725493;" /> + <stop + id="stop1400" + offset="0.50000000" + style="stop-color:#ffffff;stop-opacity:0.26666668;" /> + <stop + id="stop1401" + offset="0.75000000" + style="stop-color:#000000;stop-opacity:0.13333334;" /> + <stop + id="stop1399" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient896"> + <stop + id="stop897" + offset="0.00000000" + style="stop-color:#e2d9a9;stop-opacity:1.0000000;" /> + <stop + id="stop898" + offset="1.0000000" + style="stop-color:#857c4d;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient893"> + <stop + id="stop894" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.27083334;" /> + <stop + id="stop895" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient841"> + <stop + id="stop842" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + <stop + id="stop844" + offset="0.50379843" + style="stop-color:#dadada;stop-opacity:1.0000000;" /> + <stop + id="stop845" + offset="0.51379842" + style="stop-color:#bdbdbd;stop-opacity:1.0000000;" /> + <stop + id="stop846" + offset="0.64667326" + style="stop-color:#dedede;stop-opacity:1.0000000;" /> + <stop + id="stop843" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient836"> + <stop + id="stop837" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:0.00000000;" /> + <stop + id="stop838" + offset="1" + style="stop-color:#fff;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="54.705607" + x2="100.20946" + xlink:href="#linearGradient832" + y1="80.75058" + y2="39.97958" + gradientTransform="matrix(0,1.181625,-0.846293,0,146.9592,-15.14529)" + gradientUnits="userSpaceOnUse" /> + <linearGradient + id="linearGradient839" + x1="0.47235259" + x2="0.47235259" + xlink:href="#linearGradient836" + y1="0.39059740" + y2="0.013744113" /> + <radialGradient + cx="0.50000000" + cy="0.50000000" + fx="0.51298690" + fy="0.092105433" + id="radialGradient840" + r="0.50000000" + xlink:href="#linearGradient1397" /> + <linearGradient + id="linearGradient860" + x1="0.21710530" + x2="0.89436638" + xlink:href="#linearGradient832" + y1="0.74342090" + y2="-0.33333325" /> + <linearGradient + id="linearGradient863" + x1="0.52739727" + x2="0.65068495" + xlink:href="#linearGradient836" + y1="0.48611110" + y2="-0.041666668" /> + <linearGradient + id="linearGradient891" + x1="0.12500000" + x2="0.82894737" + xlink:href="#linearGradient836" + y1="1.0986842" + y2="0.13815789" /> + <linearGradient + id="linearGradient892" + x1="-0.11404288" + x2="-0.061766334" + xlink:href="#linearGradient896" + y1="0.24721514" + y2="2.5462053" /> + <linearGradient + id="linearGradient900" + x1="0.37142858" + x2="0.11428571" + xlink:href="#linearGradient836" + y1="0.63888890" + y2="1.0416666" /> + <linearGradient + id="linearGradient905" + x1="1.3074018" + x2="1.3074018" + xlink:href="#linearGradient893" + y1="1.7768639" + y2="0.11690380" /> + <linearGradient + id="linearGradient906" + x1="-0.42276084" + x2="-0.42276084" + xlink:href="#linearGradient893" + y1="1.8603847" + y2="0.20042460" /> + <linearGradient + id="linearGradient908" + x1="0.50352114" + x2="0.21478873" + xlink:href="#linearGradient832" + y1="0.44615385" + y2="1.1615385" /> + <linearGradient + id="linearGradient910" + x1="0.45422536" + x2="0.69594592" + xlink:href="#linearGradient836" + y1="0.50000000" + y2="-0.078947365" /> + <linearGradient + id="linearGradient911" + x1="1.1710526" + x2="-2.2763157" + xlink:href="#linearGradient896" + y1="0.16447368" + y2="1.5986842" /> + <linearGradient + id="linearGradient912" + x1="0.67222220" + x2="0.25000000" + xlink:href="#linearGradient832" + y1="0.30167598" + y2="0.44692737" /> + <radialGradient + cx="0.48684204" + cy="0.44078955" + fx="0.53289479" + fy="0.013157940" + id="radialGradient1402" + r="0.76976496" + xlink:href="#linearGradient841" /> + <radialGradient + cx="0.48684210" + cy="0.46052632" + fx="0.52631575" + fy="0.71710521" + id="radialGradient1415" + r="0.76976496" + xlink:href="#linearGradient1416" /> + </defs> + <sodipodi:namedview + bordercolor="#666666" + borderopacity="1.0" + id="base" + inkscape:cx="54.232622" + inkscape:cy="92.070558" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:window-height="820" + inkscape:window-width="1110" + inkscape:window-x="177" + inkscape:window-y="162" + inkscape:zoom="6.9465339" + pagecolor="#ffffff" + inkscape:current-layer="svg1" + showguides="true" + inkscape:guide-bbox="true"> + <sodipodi:guide + orientation="vertical" + position="80.619858" + id="guide1772" /> + <sodipodi:guide + orientation="horizontal" + position="93.283933" + id="guide2608" /> + </sodipodi:namedview> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path855" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1402);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-92.18625,-774.3955)" + inkscape:export-filename="/home/steve/Documents/remote/images/pause.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path1414" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1415);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-91.90522,-774.4678)" + inkscape:export-filename="/home/steve/Documents/remote/images/pause.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 184.98434 527.64008 A 29.511122 29.511122 0 1 0 125.96210,527.64008 A 29.511122 29.511122 0 1 0 184.98434 527.64008 z" + id="path856" + sodipodi:cx="155.47322" + sodipodi:cy="527.64008" + sodipodi:rx="29.511122" + sodipodi:ry="29.511122" + sodipodi:type="arc" + style="fill:url(#linearGradient839);fill-opacity:1;fill-rule:evenodd;stroke-width:1.0000000pt;stroke-opacity:0.37190083;" + transform="matrix(1.291670,0.000000,0.000000,1.524596,-118.6605,-740.1552)" + inkscape:export-filename="/home/steve/Documents/remote/images/pause.png" + inkscape:export-xdpi="90" + inkscape:export-ydpi="90" /> + <path + d="M 361.33127,396.63946 C 361.33127,460.21074 309.73720,511.80481 246.16592,511.80481 C 182.59465,511.80481 131.00057,460.21074 131.00057,396.63946 C 131.00057,333.06819 182.59465,281.47411 246.16592,281.47411 C 309.73720,281.47411 361.33127,333.06819 361.33127,396.63946 z " + id="path862" + sodipodi:insensitive="true" + style="fill:url(#linearGradient863);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:1.0000000pt;" /> + <rect + style="fill:#bababa;fill-opacity:1" + id="rect2381" + width="48.595245" + height="56.448753" + x="56.803886" + y="39.146034" + transform="matrix(0.999968,-8.050322e-3,-7.165473e-3,0.999974,0,0)" /> + <rect + style="fill:#323232;fill-opacity:1" + id="rect2612" + width="41.163712" + height="49.623737" + x="59.571178" + y="41.656029" /> +</svg> diff --git a/abs/core-testing/local-website/htdocs/remote/svg/up.svg b/abs/core-testing/local-website/htdocs/remote/svg/up.svg new file mode 100644 index 0000000..d980f23 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/remote/svg/up.svg @@ -0,0 +1,349 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://inkscape.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + height="128.00000pt" + id="svg1" + inkscape:version="0.43" + sodipodi:docbase="/home/steve/Downloads/buttons" + sodipodi:docname="up.svg" + sodipodi:version="0.32" + width="128.00000pt"> + <metadata + id="metadata1718"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:title>Etiquette Icons</dc:title> + <dc:description /> + <dc:subject> + <rdf:Bag> + <rdf:li>hash</rdf:li> + <rdf:li /> + <rdf:li>action</rdf:li> + <rdf:li>computer</rdf:li> + <rdf:li>icons</rdf:li> + <rdf:li>buttons</rdf:li> + </rdf:Bag> + </dc:subject> + <dc:publisher> + <cc:Agent + rdf:about="http://www.openclipart.org"> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:publisher> + <dc:creator> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:creator> + <dc:rights> + <cc:Agent> + <dc:title>Andy Fitzsimon</dc:title> + </cc:Agent> + </dc:rights> + <dc:date /> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <cc:license + rdf:resource="http://web.resource.org/cc/PublicDomain" /> + <dc:language>en</dc:language> + </cc:Work> + <cc:License + rdf:about="http://web.resource.org/cc/PublicDomain"> + <cc:permits + rdf:resource="http://web.resource.org/cc/Reproduction" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/Distribution" /> + <cc:permits + rdf:resource="http://web.resource.org/cc/DerivativeWorks" /> + </cc:License> + </rdf:RDF> + </metadata> + <defs + id="defs3"> + <linearGradient + id="linearGradient1416"> + <stop + id="stop1417" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1419" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + <stop + id="stop1418" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient1397"> + <stop + id="stop1398" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.53725493;" /> + <stop + id="stop1400" + offset="0.50000000" + style="stop-color:#ffffff;stop-opacity:0.26666668;" /> + <stop + id="stop1401" + offset="0.75000000" + style="stop-color:#000000;stop-opacity:0.13333334;" /> + <stop + id="stop1399" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient896"> + <stop + id="stop897" + offset="0.00000000" + style="stop-color:#e2d9a9;stop-opacity:1.0000000;" /> + <stop + id="stop898" + offset="1.0000000" + style="stop-color:#857c4d;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient893"> + <stop + id="stop894" + offset="0.00000000" + style="stop-color:#000000;stop-opacity:0.27083334;" /> + <stop + id="stop895" + offset="1.0000000" + style="stop-color:#000000;stop-opacity:0.00000000;" /> + </linearGradient> + <linearGradient + id="linearGradient841"> + <stop + id="stop842" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + <stop + id="stop844" + offset="0.50379843" + style="stop-color:#dadada;stop-opacity:1.0000000;" /> + <stop + id="stop845" + offset="0.51379842" + style="stop-color:#bdbdbd;stop-opacity:1.0000000;" /> + <stop + id="stop846" + offset="0.64667326" + style="stop-color:#dedede;stop-opacity:1.0000000;" /> + <stop + id="stop843" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient836"> + <stop + id="stop837" + offset="0.00000000" + style="stop-color:#ffffff;stop-opacity:0.00000000;" /> + <stop + id="stop838" + offset="1" + style="stop-color:#fff;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient832"> + <stop + id="stop833" + offset="0.00000000" + style="stop-color:#323232;stop-opacity:1.0000000;" /> + <stop + id="stop1430" + offset="0.50000000" + style="stop-color:#000000;stop-opacity:1.0000000;" /> + <stop + id="stop834" + offset="1.0000000" + style="stop-color:#ffffff;stop-opacity:1.0000000;" /> + </linearGradient> + <linearGradient + id="linearGradient835" + x1="0.19090909" + x2="1.1454545" + xlink:href="#linearGradient832" + y1="0.68421054" + y2="-0.17105263" /> + <linearGradient + id="linearGradient839" + x1="0.47235259" + x2="0.47235259" + xlink:href="#linearGradient836" + y1="0.39059740" + y2="0.013744113" /> + <radialGradient + cx="0.50000000" + cy="0.50000000" + fx="0.51298690" + fy="0.092105433" + id="radialGradient840" + r="0.50000000" + xlink:href="#linearGradient1397" /> + <linearGradient + id="linearGradient860" + x1="0.21710530" + x2="0.89436638" + xlink:href="#linearGradient832" + y1="0.74342090" + y2="-0.33333325" /> + <linearGradient + id="linearGradient863" + x1="0.52739727" + x2="0.65068495" + xlink:href="#linearGradient836" + y1="0.48611110" + y2="-0.041666668" /> + <linearGradient + id="linearGradient891" + x1="0.12500000" + x2="0.82894737" + xlink:href="#linearGradient836" + y1="1.0986842" + y2="0.13815789" /> + <linearGradient + id="linearGradient892" + x1="-0.11404288" + x2="-0.061766334" + xlink:href="#linearGradient896" + y1="0.24721514" + y2="2.5462053" /> + <linearGradient + id="linearGradient900" + x1="0.37142858" + x2="0.11428571" + xlink:href="#linearGradient836" + y1="0.63888890" + y2="1.0416666" /> + <linearGradient + id="linearGradient905" + x1="1.3074018" + x2="1.3074018" + xlink:href="#linearGradient893" + y1="1.7768639" + y2="0.11690380" /> + <linearGradient + id="linearGradient906" + x1="-0.42276084" + x2="-0.42276084" + xlink:href="#linearGradient893" + y1="1.8603847" + y2="0.20042460" /> + <linearGradient + id="linearGradient908" + x1="0.50352114" + x2="0.21478873" + xlink:href="#linearGradient832" + y1="0.44615385" + y2="1.1615385" /> + <linearGradient + id="linearGradient910" + x1="0.45422536" + x2="0.69594592" + xlink:href="#linearGradient836" + y1="0.50000000" + y2="-0.078947365" /> + <linearGradient + id="linearGradient911" + x1="1.1710526" + x2="-2.2763157" + xlink:href="#linearGradient896" + y1="0.16447368" + y2="1.5986842" /> + <linearGradient + id="linearGradient912" + x1="0.67222220" + x2="0.25000000" + xlink:href="#linearGradient832" + y1="0.30167598" + y2="0.44692737" /> + <radialGradient + cx="0.48684204" + cy="0.44078955" + fx="0.53289479" + fy="0.013157940" + id="radialGradient1402" + r="0.76976496" + xlink:href="#linearGradient841" /> + <radialGradient + cx="0.48684210" + cy="0.46052632" + fx="0.52631575" + fy="0.71710521" + id="radialGradient1415" + r="0.76976496" + xlink:href="#linearGradient1416" /> + </defs> + <sodipodi:namedview + bordercolor="#666666" + borderopacity="1.0" + id="base" + inkscape:cx="72.909285" + inkscape:cy="75.399464" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:window-height="575" + inkscape:window-width="797" + inkscape:window-x="447" + inkscape:window-y="416" + inkscape:zoom="2.4559706" + pagecolor="#ffffff" + inkscape:current-layer="svg1" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path855" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1402);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-92.18625,-774.3955)" /> + <path + d="M 127.40167 483.73325 A 27.351770 27.351770 0 1 0 72.698126,483.73325 A 27.351770 27.351770 0 1 0 127.40167 483.73325 z" + id="path1414" + sodipodi:cx="100.04990" + sodipodi:cy="483.73325" + sodipodi:rx="27.351770" + sodipodi:ry="27.351770" + sodipodi:type="arc" + style="fill:url(#radialGradient1415);fill-opacity:1;fill-rule:evenodd;stroke-width:3.0812783;stroke-opacity:0.37190083;stroke:none;stroke-dasharray:none;" + transform="matrix(1.736345,0.000000,0.000000,1.736345,-91.90522,-774.4678)" /> + <path + d="M 184.98434 527.64008 A 29.511122 29.511122 0 1 0 125.96210,527.64008 A 29.511122 29.511122 0 1 0 184.98434 527.64008 z" + id="path856" + sodipodi:cx="155.47322" + sodipodi:cy="527.64008" + sodipodi:rx="29.511122" + sodipodi:ry="29.511122" + sodipodi:type="arc" + style="fill:url(#linearGradient839);fill-opacity:1;fill-rule:evenodd;stroke-width:1.0000000pt;stroke-opacity:0.37190083;" + transform="matrix(1.291670,0.000000,0.000000,1.524596,-118.6605,-740.1552)" /> + <path + d="M 361.33127,396.63946 C 361.33127,460.21074 309.73720,511.80481 246.16592,511.80481 C 182.59465,511.80481 131.00057,460.21074 131.00057,396.63946 C 131.00057,333.06819 182.59465,281.47411 246.16592,281.47411 C 309.73720,281.47411 361.33127,333.06819 361.33127,396.63946 z " + id="path862" + sodipodi:insensitive="true" + style="fill:url(#linearGradient863);fill-opacity:1;fill-rule:evenodd;stroke:none;stroke-width:1.0000000pt;" /> + <path + d="M 56.450293,78.082301 L 107.65417,78.516121 L 83.146559,43.297758 L 56.450293,78.082301 z " + id="path1440" + sodipodi:nodetypes="cccc" + style="fill:url(#linearGradient835);fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:5.1250000;stroke-linecap:round;stroke-linejoin:round;stroke-opacity:0.27272728;" /> +</svg> diff --git a/abs/core-testing/local-website/htdocs/rrd/Disabled b/abs/core-testing/local-website/htdocs/rrd/Disabled new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/rrd/Disabled diff --git a/abs/core-testing/local-website/htdocs/rrd/index.html b/abs/core-testing/local-website/htdocs/rrd/index.html new file mode 100644 index 0000000..5f595b2 --- /dev/null +++ b/abs/core-testing/local-website/htdocs/rrd/index.html @@ -0,0 +1,29 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> +<head> + <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"> + <meta content="Cecil Watson" name="author"> + <title>KnoppMyth R5.5</title> + <!-- Generated by: /usr/local/bin/rrd_Configure.sh --> + <link href="/KnoppMyth.css" rel="stylesheet" type="text/css" /> + <p align="center"><a href="http://www.mysettopbox.tv"> + <img src="/header.png" alt="Tux with a Remote" align="middle" border="0"></a> + </p> + <table align="center" border="0" cellpadding="5"> + <tbody> + <tr> + <td style="vertical-align: top;"> + <p class="headerimage" align="center"><b>KnoppMyth R5.5</b></p> + <p align=center> +<font size="+2">RRD Tool</font><br> +<font size="+1">Is <font color="#CC0000">disabled</font> +by rrd_Configure.sh and may be re-enabled by running as root:<br> +<b>rrd_Configure.sh</b></font> + </p> + <p> </p> + </td> + </tr> + </tbody> + </table> +</body> +</html> diff --git a/abs/core-testing/local-website/htdocs/style.css b/abs/core-testing/local-website/htdocs/style.css new file mode 100644 index 0000000..535ffec --- /dev/null +++ b/abs/core-testing/local-website/htdocs/style.css @@ -0,0 +1,227 @@ +/* + * Global page handlers. +/*/ + + html,body { + border: 0; + margin: 0; + padding: 0; + font-size: 9pt; + font-family: Arial, Helvetica, sans-serif; + background-color: #191c26; + color: #dedede; + } + + /* For some reason, settings for the main body element doesn't always work for + * text inside of tables + /*/ + .body { + font-size: 12px; + font-family: Arial, Helvetica, sans-serif; + } + +/* + * We should try to keep links and labels looking consistent across the app. +/*/ + + a, a:link { color: #E0E0FF; text-decoration: none; } + a:active { color: #990033; text-decoration: none; } + a:visited { color: #E0E0FF; text-decoration: none; } + a:hover { color: #F0F000; text-decoration: underline; } + + label { color: #E0E0FF; text-decoration: none; } + label:hover { color: #F0F000; text-decoration: underline; } + +/* a class for the menu across the top of the page as well as menu headers throughout the page */ + .menu { background-color: #265990 } + .menu_border_t { border-top: 2px solid #9090B0 } + .menu_border_b { border-bottom: 2px solid #9090B0 } + .menu_border_l { border-left: 2px solid #9090B0 } + .menu_border_r { border-right: 2px solid #9090B0 } + +/* a class for commands and other user input boxes */ + +/* @deprecated old classes */ +.command { background-color: #1040A0 } +.command_border_t { border-top: 2px solid #9090B0 } +.command_border_b { border-bottom: 2px solid #9090B0 } +.command_border_l { border-left: 2px solid #9090B0 } +.command_border_r { border-right: 2px solid #9090B0 } +.activecommand { background-color: #108040 } + +/* New command classes */ + + /* Box to hold commands */ + .commandbox { + background-color: #102923; + color: #E0E0FF; + border: 1px solid #9090B0; + } + + /* Commands themselves */ + + .commands { /* Placeholder for handling sub-elements */ } + + .commands input.x-submit { + border: 2px outset #7b8; + padding: 0 .5em; + height: 2em; + background-color: #263; + color: #E0E0FF; + } + .commands input.x-submit:hover { + border: 1px outset #9da; + background-color: #485; + color: #F0F000; + text-decoration: underline; + } + + .commands a { + font-weight: bold; + border: 1px solid #7b8; + padding: .15em .5em; + background-color: #263; + } + .commands a:hover { + border: 1px solid #9da; + background-color: #485; + } + +/* + * The following styles refer to forms and form elements throughout MythWeb +/*/ + + /* Avoid those nasty extra linefeeds in IE </form> tags */ + form { display: inline; } + + /* A special class for submit buttons */ + .submit { + border: 2px outset #7b8; + padding: 0 .5em; + background-color: #263; + color: #E0E0FF; + font-weight: bold; + height: 2em; + } + .submit:hover { + border: 2px outset #9da; + background-color: #485; + color: #F0F000; + text-decoration: underline; + } + + /* A special class for radio buttons and check boxes because some browsers render them weirdly */ + .radio { + height: 14px !important; + width: 14px !important; + color: #002000; + background-color: #C0D0C0; + } + + /* Default styles for form fields */ + select { + font-family: Arial, Helvetica, sans-serif; + color: #002000; + background-color: #C0D0C0; + font-size: 9pt; + } + + input { + padding-left: .25em; + font-family: Arial, Helvetica, sans-serif; + color: #002000; + background-color: #C0D0C0; + font-size: 9pt; + } + + textarea { + font-family: terminal, courier, courier-new; + color: #002000; + background-color: #C0D0C0; + font-size: 9pt; + } + + /* Quantity-sized elements look better with the text centered */ + input.quantity { + width: 2em !important; + text-align: center; + } + +/* + * A special class for error stuff, so all page errors look the same. +/*/ + + #error, .error { + color: #F03030; + background-color: #360000; + border-color: #F03030; + border: thin groove #F03030; + padding: 8px; + } + +/* + * The following represent some global classes to accommodate minor but + * oft-used manipulations like font sizes.0 +/*/ + + /* font size classes */ + .tiny { font-size: 9px; } + .small { font-size: 9pt; } + .normal { font-size: 10pt; } + .large { font-size: 12pt; } + .huge { font-size: 24px; } + + /* fony style classes */ + .bold, .bold a, .bold a:link, .bold a:visited, .bold a:active, .bold a:hover { + font-weight: bold !important; + } + .italic, .italic a, .italic a:link, .italic a:visited, .italic a:active, .italic a:hover { + font-style: italic !important; + } + + /* Handy for, well, hiding things.. Also for mouseover popup menus */ + .hidden { + visibility: hidden; + display: none; + } + +/* + * clearfix -- see http://positioniseverything.net/easyclearing.html for details on how/why this works +/*/ + + .clearfix:after { + content: "."; + display: block; + height: 0; + clear: both; + visibility: hidden; + } + .clearfix {display: inline-block;} + /* Hides from IE-mac \*/ + * html .clearfix {height: 1%;} + .clearfix {display: block;} + /* End hide from IE-mac */ + + /* Ajax little popup request thing style */ + #ajax_working { + position: fixed; + background-color: green; + bottom: 0px; + left: 1em; + padding: 1em; + width: 10em; + text-align: center; + } + + .link { + cursor: pointer; + } + +/* I don't think we have a single image with a border in the default template, so disable it */ + a img { + border: 0px; + } + + .nowrap { + white-space: nowrap; + } |
