[mythtv] [PATCH] to mythtv-HOWTO.txt: try to explain channel setup/programm data import

[Stefan Frank]

Hi Robert / everyone else,

here's a draft trying to better explain how to setup channels and programm
data import. Feel free to ignore it or reword it as you see fit.

As i'm not 100% sure about it's correctness, everyone is welcome to send
corrections, improvements.

Robert, should you decide to include it, better check the spelling. ;)

Bye, Stefan

-- 
   That's the difference between me and the rest of the world! Happiness isn't
good enough for me! I demand euphoria!	-- Calvin
-------------- next part --------------
--- mythtv-HOWTO-orig.txt	2003-09-20 13:17:41.000000000 +0200
+++ mythtv-HOWTO.txt	2003-10-08 00:43:14.000000000 +0200
@@ -110,8 +110,10 @@
         9.1.4 Input Connections
      9.2 Post-configuration.
      9.3 Configuring a non-master backend.
-     9.4 Configuring and running mythfilldatabase.
-        9.4.1 Setting mythfilldatabase to run from cron
+     9.4 Setting up channels and importing programm data using mythfilldatabase
+        9.4.1 Configuring TV channels
+        9.4.2 Importing programm data into the database
+        9.4.3 Setting mythfilldatabase to run from cron
 
   10. Configuring mythfrontend.
      10.1 General
@@ -373,7 +375,7 @@
      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
+  hardware-based video encoder, such as a Matrox Marvel G200/G400 or a Hauppauge
   WinTV-PVR-250/350.  In this mode, because the video encoding is being
   done externally, the CPU requirements are quite low.  See the ``Video
   Capture Device'' section for details.
@@ -2879,16 +2881,18 @@
   doing to the console.  If you'd like to see the options that are
   available for mythbackend, type mythbackend -h for help.
 
-  As of 2003-03-27, the available options are:
+  As of 2003-10-07, the available options are:
 
 
        $ mythbackend -h
-       Invalid argument: -h
-       Valid options are:
+       Valid options are: 
        -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                Prints more information
+       -v or --verbose debug-level    Prints more information
+                                      Accepts any combination (separated by comma)
+                                      of all,none,quiet,record,playback,
+                                      channel,osd,file,schedule,network
        --printexpire                  List of auto-expire programs
        --printsched                   Upcoming scheduled programs
 
@@ -2900,6 +2904,7 @@
   can follow the steps outlined in the section called ``I'd like to
   automatically start mythbackend at system boot time''.
 
+
   9.3.  Configuring a non-master backend.
 
   Configuration of a non-master backend follows the same general
@@ -2923,28 +2928,61 @@
   NOTE: Do not run mythfilldatabase on a non-master backend.
 
 
-  9.4.  Configuring and running mythfilldatabase.
+  9.4.  Setting up channels and importing programm data using mythfilldatabase.
+
+  mythfilldatabase is used to configure your channels and to import programm
+  data into the database.
 
   NOTE:  mythfilldatabase 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.
 
-  mythfilldatabase --manual is another option; the manual option will
-  allow you to fine tune channel frequencies and specify which channels
-  will be added to the database.  If you are not using the tv_grab_na
-  grabber, you must use the --manual option.
+  See mythfilldatabase -h  for an explanation of the various
+  options to mythfilldatabase.
+
+  9.4.1.  Configuring TV channels
+  
+  If your XMLTV grabber scripts output contains channel information
+  (i.e. tv_grab_na for US users) consider yourself lucky and skip
+  to section 9.4.3.
+
+  As of 2003/10/07 mythtv doesn't have an option (yet) to automatically
+  determine all available channels in your area. If you are using xawtv you
+  can import the channel setup from your .xawtv file. This is the preferred
+  method as it also assures you of having a properly configured tv tuner card.
+
+  With the above assumptions you now should run mythfilldatabase to configure
+  your channels:
+
+  mythfilldatabase --manual --preset --xawchannels <sourceid> <xawtvrcfile> 
+
+      where sourceid = 1 (in a typical single tuner setup),
+      and xawtvrcfile = path/filename of your xawtv configuration file.
+
+  NOTE: the xmltvid for each channel mmust match the
+  corresponding channel id in your xmltv data file.
+
+  If you encounter any problems at this point you might want to search the
+  mythtv-users mailing list archive for possible solutions.
+
+  
+  9.4.2.  Importing programm data into the database
 
-  mythfilldatabase --file is an option if there isn't an XMLTV grabber
-  for your country, but you do have an XML formatted listings file
-  created by some other program.
+  If you are using a XMLTV grabber script supported by mythtv you can skip
+  to section 9.4.3. If not then you have to look for an alternative source
+  by yourself. And yes, they exist (for german speaking countries at least).
 
-  mythfilldatabase --xawchannels is an option if you have used xawtv to
-  fine-tune your channels and would like to import the fine tuning
-  offsets into MythTV.
+  So, with a xmltv file 'data.xml' containing the program data, run
+  
+  mythfilldatabase --update --file <sourceid> <offset> data.xml 
 
+      where sourceid = 1 (in a typical single tuner setup),
+      and offset = days from today that data.xml defines
 
+  You may add --no-delete to the above command if you want to keep
+  up to seven days of old programm data.
 
-  9.4.1.  Setting mythfilldatabase  to run from cron
+  9.4.3.  Setting mythfilldatabase to run from cron
 
   In order to keep your database filled, mythfilldatabase should be run
   once a day.