Difference between revisions of "User Manual:Setting up DVB-C (cable)"

From MythTV Official Wiki
Jump to: navigation, search
m
(flesh out DVB-C setup some more after yet another succesful installation via IRC this way...)
 
Line 2: Line 2:
 
{{User Manual TOC}}
 
{{User Manual TOC}}
  
This page is up-to-date to MythTV version 0.1
+
This page is up-to-date to MythTV version 0.24
  
=Setting up DVB-C (cable)=
+
= Setting up DVB-C (cable) =
  
 
In this chapter you'll find information about how to setup up MythTV as a cable (DVB-C) receiver. For general information about DVB and DVB-C you should read the chapter called [[User Manual:DVB | About DVB]].
 
In this chapter you'll find information about how to setup up MythTV as a cable (DVB-C) receiver. For general information about DVB and DVB-C you should read the chapter called [[User Manual:DVB | About DVB]].
  
  
==Scanning for channels==
+
== Common Steps 1-3 ==
  
In order to scan DVB-C with MythTV, you need to give it an initial transponder. The data you need to enter is: frequency, polarity, symbol rate and modulation. It can be obtained from your channels.conf file.
+
TODO insert common part of adding the capture device, creating a video source and connecting both here
  
Also, DO NOT import a channels.conf into mythTV any more (as of .21).  It does NOT provide all the information necessary to properly tune DVB and will lead to myriad problems.
+
== Step 4: The Scan for Channels ==
  
Someone really ought to flesh out this page.
+
In order to scan DVB-C with MythTV, you need to give it an initial transponder in a tuned scan. The data you need to enter is: frequency, polarity, symbol rate and modulation. The information can be obtained from your operator. (Should it not be easily available it can also be obtained from an [http://linuxtv.org/hg/dvb-apps/file/default/util/scan/dvb-c initial tuning file] or a channels.conf for your location.)
  
 +
{{Warning box|Do not import a channels.conf into MythTV any more. It does not provide all the information necessary to properly tune DVB and will lead to myriad problems.}}
  
==Scripts ==
 
  
'''[[Channel_tuning_broken_with_DVB-C#modified_mythic.pl_solution | Channel_tuning_broken_with_DVB-C]]'''
+
== Known Issues ==
: With some cable providers scanning for channels gives trouble (not possible to tune the channels found by MythTV). This script fixes the channels found by the scanner. It does not find missing channels for you, for this you need a different script.
+
There is only one simple solution for these problems: '''Talk to your cable provider they need to fix it!'''
 +
 
 +
* {{Ticket|7486}}, Some cable operators don't mark the correct tuning tables in their networks active. The ticket has a patch that allows selecting the correct tables.
 +
 
 +
* [[Channel tuning broken with DVB-C]], Some cable operators just deliver the tuning tables straight from a satelite feed and are unwilling to fix the problem.

Latest revision as of 16:53, 7 September 2011

This page is up-to-date to MythTV version 0.24

Setting up DVB-C (cable)

In this chapter you'll find information about how to setup up MythTV as a cable (DVB-C) receiver. For general information about DVB and DVB-C you should read the chapter called About DVB.


Common Steps 1-3

TODO insert common part of adding the capture device, creating a video source and connecting both here

Step 4: The Scan for Channels

In order to scan DVB-C with MythTV, you need to give it an initial transponder in a tuned scan. The data you need to enter is: frequency, polarity, symbol rate and modulation. The information can be obtained from your operator. (Should it not be easily available it can also be obtained from an initial tuning file or a channels.conf for your location.)

Warning.png Warning: Do not import a channels.conf into MythTV any more. It does not provide all the information necessary to properly tune DVB and will lead to myriad problems.


Known Issues

There is only one simple solution for these problems: Talk to your cable provider they need to fix it!

  • #7486, Some cable operators don't mark the correct tuning tables in their networks active. The ticket has a patch that allows selecting the correct tables.