''dvbscan'' is one of the two command line [[Frequency scan|frequency scanning]] utilities contained in the [[LinuxTV dvb-apps]] (The other one is [[Scan|scan]]. There are also two utilities, not included in [[LinuxTV dvb-apps]], called [[W_scan|w_scan]] and [[Scan-s2|scan-s2]]; See the [[Frequency_scan#Comparison_of_DVB_frequency_scanning_commandline_utilities|Comparison of the scanning utilities]] for more information).

+

:{{Note|Depending on where/how you got the dvb-apps package, the program may instead be called scandvb (as some distro package managers have rebranded it as such). In the following examples, we'll use the correct name, ''dvbscan''.}}

−

''scan'' is one of the command line utilities contained in the [[LinuxTV dvb-apps]]. It scans specific frequencies for programs that can be received and generates a channel list.

+

When using ''dvbscan'', one indirectly instructs it to search for programs streams that can be received from specified frequencies and generates a resultant channel list.

−

+

−

:{{Note|Depending on where/how you got the dvb-apps package, the program may be called either ''scan'', ''scandvb'' or ''dvbscan''. In the following examples, we'll use the name ''dvbscan''.}}

+

==Documentation==

==Documentation==

Line 12:

Line 12:

-h help

-h help

-adapter <id> adapter to use (default 0)

-adapter <id> adapter to use (default 0)

−

-frontend <id> frontend to use (default 0)

+

-frontend <id> frontend to use (default 0)

-demux <id> demux to use (default 0)

-demux <id> demux to use (default 0)

-secfile <filename> Optional sec.conf file.

-secfile <filename> Optional sec.conf file.

Line 41:

Line 41:

<initial scan file>

<initial scan file>

−

Most experts or experienced users will likely find that this information conveys sufficient details in so far as how to manipulate a specific DVB hardware device with dvbscan. 'New users', however, are probably left scratching their heads by some of the options listed in the output -- but fear not!

+

Most experts or experienced users will likely find that this information conveys sufficient details in so far as how to manipulate a specific DVB hardware device with ''dvbscan''. 'New users', however, are probably left scratching their heads by some of the options listed in the output -- but fear not!

−

One thing that is noteworthy from the output above is that dvbscan does not take file system device names; instead, it cobbles them together from the adaptor, frontend and demux numbers. If you only have one tuner, you don't need to worry about this detail.

+

One thing that is noteworthy from the output above is that ''dvbscan'' does not take file system device names; instead, it cobbles them together from the adaptor, frontend and demux numbers. If you only have one tuner, you don't need to worry about this detail.

−

==The initial scan file==

+

==Scanning for channels you can receive==

−

In order for dvbscan to search for channels that you can receive, you must provide the name of an initial scan frequency file in the dvbscan command line. The initial scan frequency file provides a frequency that dvbscan uses as a starting point from which to proceed with its scan. These initial scan frequency files are specific to your geographic location. Initial scan information files for many localities are supplied with the [[LinuxTV dvb-apps]] package. The exact location where these files are installed may vary. In the following examples, the directory is ''/usr/share/doc/dvb-utils/examples/scan/dvb-t/''; other installations may use ''/usr/share/doc/dvb-apps'', ''/usr/local/share/dvb/scan/dvb-t/'', ''/usr/share/dvb/dvb-t/au-Adelaide'' ....

+

:{{Note|If you get an error 'Unable to query frontend status', try using 'scan' instead.}}

−

In each case, the file you're looking for is contained in the folder for the type of DVB device your using. DVB-T users, for example, should find a initial scan file from /usr/share/doc/dvb-utils/examples/scan/dvb-t/ ... or, depending on the installation of the package, in /usr/share/doc/dvb-apps or /usr/local/share/dvb/scan/dvb-t/ ....

+

===Running ''dvbscan'' with an initial scan file===

−

Second, the name of the file you're looking for is of the form cc-Ttttt, where cc is a two-letter country abbreviation, and Ttttt is the name of the location of the transmitter. So in Adelaide, Australia, you'd look for a file called au-Adelaide (''/usr/local/share/dvb/zap/dvb-t/au-Adelaide''); in Oxford, UK you would use uk-Oxford (usr/share/dvb/dvb-t/uk-Oxford).

+

One of the ways that ''dvbscan'' can be used to search for channels that you can receive is by instructing it to use an initial scan file. An initial scan file provides a list of frequencies, and some other specific data that ''dvbscan'' should use, to proceed with a scan.

−

==Scanning for channels you can receive==

+

The [[LinuxTV dvb-apps]] package supplies a large number of user submitted initial scan files for many different localities. The exact directory location where these files are installed may vary depending upon the installation of the package (for an explanation of this incongruity, see [[LinuxTV_dvb-apps#Obtaining the dvb-apps_package|here]]). Nonetheless, the file you're looking for is:

+

* First, contained within the folder for the type of DVB device you're using. For example, DVB-T users should find an initial scan file from ''/usr/share/dvb/dvb-t/'' ... other installations may use:

+

** ''/usr/share/doc/dvb-utils/examples/scan/dvb-t/'' or

+

** ''/usr/share/doc/dvb-apps/dvb-t'' or

+

** ''/usr/local/share/dvb/scan/dvb-t/'' or ...

+

** ''/usr/share/dvb/dvb-t/'' or ...

+

* Second, the name of the file you're looking for is of the form ''cc-Ttttt'', where ''cc'' is a two-letter country abbreviation, and ''Ttttt'' is the name of the location of the transmitter. So, if you're in:

** Oxford, UK you would use uk-Oxford (eg. ''/usr/share/dvb/dvb-t/uk-Oxford'').

−

'''1. Run ''dvbscan'' with a initial scan file, relevant to your locality, specified in the command''' <BR>

+

If you're using a packaged dvb-apps (or dvb-utils), you can also [http://linuxtv.org/hg/dvb-apps/file/tip/util/scan/ check the dvb-apps repository directly].

−

Some examples:

+

−

For DVB-T

+

Some usage examples:

−

$ dvbscan /usr/local/share/dvb/scan/dvb-t/au-Adelaide

+

$ dvbscan /usr/local/share/dvb/scan/dvb-t/au-Adelaide

−

scan /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-Oxford

+

$ dvbscan /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-Oxford

+

Obviously, you will have to adapt this command for your own situation/locality. In any regard, ''dvbscan'' will try to find programs on frequencies it takes from the initial scan file (e.g. au-Adelaide or uk-Oxford, or where ever ...).

+

+

===If you can't find a suitable initial scan file to use with ''dvbscan'' and:===

+

+

====If you're an North American user:====

+

Just use the initial scan file entitled "''us-ATSC-center-frequencies-8VSB''" (for Over-the-Air) or "''us-Cable-Standard-center-frequencies-QAM256''" (for digital cable), as these will lead ''dvbscan'' to proceed to do a full search of the channel frequency spectrum.

Obviously, you will have to adopt this command for your own situation/locality. In any regard, dvbscan will try to find programs on frequencies it takes from the initial scan file (e.g. uk-Oxford etc or whatever your place is).

+

=====Generate initial-tuning data for ATSC QAM (digital cable)=====

+

You can also try to use w_scan to generate initial tuning data (needs w_scan >= 20080815):

+

$ w_scan -fa -A2 -x > ~/dvbscan.txt

+

or search directly using w_scan:

+

$ w_scan -fa -A2 -X

+

NOTE: w_scan >= 20090504 needs additionally option -c <COUNTRY>

−

'''2. During the scan'''<BR>

+

====If you're a DVB-T or DVB-C user:====

−

After initiating the ''dvbscan'' command, a lot of output data will be produced in the shell. The first thing that dvbscan does is parse the information form the initial scan file and reports with what hardware device that this information is going to be utilized. For example:

+

You can use the [http://wirbel.htpc-forum.de/w_scan/index2.html w_scan] app instead (in German; [http://64.233.179.104/translate_c?hl=en&langpair=de%7Cen&u=http://wirbel.htpc-forum.de/w_scan/index2.html English translation via Google]). w_scan doesn't need an initial scan file; instead, it scans all frequencies. Run it with:

−

$ dvbscan /usr/local/share/dvb/scan/dvb-t/au-Adelaide

+

−

scanning /usr/local/share/dvb/scan/dvb-t/au-Adelaide

+

−

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'

+

−

initial transponder 226500000 1 3 9 3 1 1 0

+

−

Next ''dvbscan'' commences a search through all the frequencies listed in an initial scan file. This process can take some time to complete.

+

$ w_scan -X

−

During this phase, the utility will output its progress in the shell.

+

w_scan can also be used to create an initial scan file via the command

+

w_scan -x >''cc-Ttttt''

+

If you choose to create an initial scan file (and you know the name of your local transmitter or cable provider), you can send the resulting file to the [http://linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb dvb mailing list] after checking that it hasn't already been posted or added to the [http://linuxtv.org/hg/dvb-apps/file/tip/util/scan/ scan directory in the dvb-apps repository].

+

NOTE: w_scan >= 20090504 needs additionally option -c <COUNTRY>

+

In addition, w_scan can also generate a [[#Creating a channels.conf file|channels.conf]] file.

−

------

+

===Create your own initial scan file===

−

The information presented will provides details on the channels being detected during the scan. Often many lines of transponder information are reported. Here are some examples:

+

This is useful for when testing specific frequencies. Also see [[Scan#An_alternative_method_of_using_dvbscan_to_check_a_specific_frequency|here]].

+

==During the scan==

+

After initiating the ''dvbscan'' command, a lot of output data will be produced in the shell. The first thing that ''dvbscan'' does is to report which file it is parsing information from and with what hardware device that this information is going to be utilized.

+

For example:

+

$ dvbscan /usr/local/share/dvb/scan/dvb-t/au-Adelaide

+

scanning /usr/local/share/dvb/scan/dvb-t/au-Adelaide

+

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'

+

+

Next ''dvbscan'' commences a search through all the frequencies listed in an initial scan file. During this phase, the utility will update the progress of the scan within its output. Do note that this process can take some time to complete, particularly if the initial scan file contains a long list of frequencies to test. The information presented provides details on the channels being detected during the scan. Often many lines of transponder information are reported. Here are some examples:

This is the tuning information for the first transponder. Each transponder can transmit multiple programs. The last one is a radio program, which you can see from the output later on.

+

This is the tuning information for the first transponder. Each transponder can transmit multiple programs and further discussion about their contents is provided later below. Note that the information presented doesn't really say if you can actually make use of the streams that are detected. This is particularly true in the case of cable systems, which tend to encrypt most channels. So while ''dvbscan'' is perfectly capable of detecting such channels, you may very well be out of luck on the viewing end.

−

+

−

Note that information presented doesn't really say if you can receive something.

+

−

+

−

+

−

On the other hand, if a signal was not found on a particular frequency, you will notice that the output produces "WARNING: >>> tuning failed!!!". Do not be alarmed by such tuning failed messages.

Do not be alarmed by such "tuning failed" messages, as this is not fatal. It simply means that no signal was found on that particular frequency -- it's possible that the initial scan files contain information about stations that are not yet, or no longer, in service, or it may imply that you presently lack a strong enough signal for reception to occur.

−

This is not fatal. It's possible that the scan files contain information about stations that are not yet, or no longer, in service. Or it may mean that you don't have strong enough signal.

+

==After the scan completes==

+

Eventually, upon completion of its search, ''dvbscan'' outputs a list of services that it found.

−

-------

+

:{{Note|The actual number of available services it finds will, of course, depend upon several factors (the number of services available in your area and those related to signal strength). Check ''dvbscan's'' output with a list of known services available for your area. If you are missing some services, then try to troubleshoot your antenna and/or cable configuration. Hopefully you will be able to improve the environment for signal reception. If you are unable to obtain a particular service, then you may just be out of range or subject to inhospitable environmental conditions that your hardware just cannot overcome to achieve reception. If zero services where found, perhaps check your antenna and/or cable lead ... maybe it's simply a case that its not plugged in at all ;-) }}

+

Each line in the output consists of a number of fields delimited by colons. The exact number of fields will depend upon the type of scan you where performing, as will be exemplified below. In any regard, these lines of output are szap/tzap/czap/azap compatible and, as such, can be copied and pasted into a simple text editor to create a "colon-separated" channels.conf file. Alternatively, one can automate the creation of a channels.conf file as described later below.

+

'''Here is a sample list for the output of a DVB-T scan:'''<br>

−

'''3. After the scan completes'''<BR>

−

Eventually, upon completion of its search, ''dvbscan'' outputs a list of services that it found.

−

−

:{{Note|The actual number of available services it finds will, of course, depend upon several factors (the number of services available in your area and those related to signal strength). Check ''dvbscan's'' output with a list of known services available for your area. If you are missing some services, then try to troubleshoot your antenna and/or cable configuration. Hopefully you will be able to improve the environment for signal reception. If you are unable to obtain a particular service, then you may just be out of range or subject to inhospitable environmental conditions that your hardware just cannot overcome to achieve reception. If zero services where found, perhaps check your antenna and/or cable lead ... maybe it's simply a case that its not plugged in at all ;-) }}

These fields vary depending on the type of modulation; the ones shown are for QFDM (and, paradoxically, not for QAM). For other forms of modulation, the meanings of the fields differ. See the source code (and document it, please!) at ''util/scan/dump-zap.c''.

+

The frequencies shown here in Hz correspond to 226.5 MHz for ABC and 219.5 MHz for TEN. Note that the first two channels are the same frequency, which means that they're both present in the same MPEG transport stream, but are distinguished by their respective [[PID]]s. Looking at the values, it's clear that ABC DiG Jazz is a radio station, since it doesn't have a video PID. Less clear is why the ABC HDTV stream (a known TV channel) does not have an audio PID. This is a real issue: this means that when tuning to that stream, no audio is output. We'll look at how to solve this problem later below.

−

Looking at the values, it's clear that ABC DiG Jazz is a radio programme, since it doesn't have a video pid. Less clear is why ABC HDTV does not have an audio pid. This is a real issue: this means that when tuning to these streams, no audio is output. We'll look at how to solve this problem below.

+

Notes:

+

* These fields will vary depending on the type of modulation; the ones shown are for QFDM (and, paradoxically, not for QAM). For other forms of modulation, the meanings of the fields differ. See the source code (and document it, please!) at ''util/scan/dump-zap.c''.

+

* If a channel has a video [[PID]] of 0 and the audio PID is not 0, then it's probably a radio channel.

+

* if dvbscan detected a channel but the signal was too weak for reliable reception, the video and audio [[PID|PIDs]] (third- and second-last numbers in the output line) will likely be shown as 0.

−

The frequencies shown here are in Hz. They correspond to 226.5 MHz for ABC and 219.5 MHz for TEN. Note that the first two programmes are the same frequency, so they come in the same MPEG stream. They're distinguished by the pids.

+

So, after reviewing the above information, you should now be able to determine the pertainent information from the output of any scan. As a further example,

conveys that the channel BBC ONE is found on frequency 578000000 Hz, and has the two PIDs 600 and 601 for the video and audio stream.

−

Notes:

+

'''Sample output from an ATSC scan:'''<br>

−

* If a channel has a video [[PID]] of 0 and and audio PID is not 0, then it's probably a radio channel.

+

There aren't as many colon delimited fields in the output as there would be as in the case of a scan of DVB-{C,T,S} system counterparts, but the substance of the output is largely the same, as can be seen in the following sample list:

−

* if dvbscan detected a channel but the signal was too weak for reliable reception, the video and audio [[PID|PIDs]] (third and second last number in the output line) will likely be shown as 0

* the dvb-apps package contains a number of files that are essentially channels.conf files for given localities. These will probably be installed on you system. For example, ''/usr/local/share/dvb/zap/dvb-t/au-Adelaide'' is a canned version of the ''output'' of ''dvbscan''. It may be out of date, so it's better to generate it from ''dvbscan'', but if you can't get ''dvbscan'' to work, you might get further by using this file.

* the dvb-apps package contains a number of files that are essentially channels.conf files for given localities. These will probably be installed on you system. For example, ''/usr/local/share/dvb/zap/dvb-t/au-Adelaide'' is a canned version of the ''output'' of ''dvbscan''. It may be out of date, so it's better to generate it from ''dvbscan'', but if you can't get ''dvbscan'' to work, you might get further by using this file.

+

==An alternative method of using ''dvbscan'' to check a specific frequency==

+

Tune to that specific frequency (e.g. using szap/tzap/czap/azap) and then use

Note: Depending on where/how you got the dvb-apps package, the program may instead be called scandvb (as some distro package managers have rebranded it as such). In the following examples, we'll use the correct name, dvbscan.

When using dvbscan, one indirectly instructs it to search for programs streams that can be received from specified frequencies and generates a resultant channel list.

Most experts or experienced users will likely find that this information conveys sufficient details in so far as how to manipulate a specific DVB hardware device with dvbscan. 'New users', however, are probably left scratching their heads by some of the options listed in the output -- but fear not!

One thing that is noteworthy from the output above is that dvbscan does not take file system device names; instead, it cobbles them together from the adaptor, frontend and demux numbers. If you only have one tuner, you don't need to worry about this detail.

Scanning for channels you can receive

Note: If you get an error 'Unable to query frontend status', try using 'scan' instead.

Running dvbscan with an initial scan file

One of the ways that dvbscan can be used to search for channels that you can receive is by instructing it to use an initial scan file. An initial scan file provides a list of frequencies, and some other specific data that dvbscan should use, to proceed with a scan.

The LinuxTV dvb-apps package supplies a large number of user submitted initial scan files for many different localities. The exact directory location where these files are installed may vary depending upon the installation of the package (for an explanation of this incongruity, see here). Nonetheless, the file you're looking for is:

First, contained within the folder for the type of DVB device you're using. For example, DVB-T users should find an initial scan file from /usr/share/dvb/dvb-t/ ... other installations may use:

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

/usr/share/doc/dvb-apps/dvb-t or

/usr/local/share/dvb/scan/dvb-t/ or ...

/usr/share/dvb/dvb-t/ or ...

Second, the name of the file you're looking for is of the form cc-Ttttt, where cc is a two-letter country abbreviation, and Ttttt is the name of the location of the transmitter. So, if you're in:

Adelaide, Australia, you'd want to look for a file called au-Adelaide (eg. /usr/share/dvb/dvb-t/au-Adelaide)

Oxford, UK you would use uk-Oxford (eg. /usr/share/dvb/dvb-t/uk-Oxford).

Obviously, you will have to adapt this command for your own situation/locality. In any regard, dvbscan will try to find programs on frequencies it takes from the initial scan file (e.g. au-Adelaide or uk-Oxford, or where ever ...).

If you can't find a suitable initial scan file to use with dvbscan and:

If you're an North American user:

Just use the initial scan file entitled "us-ATSC-center-frequencies-8VSB" (for Over-the-Air) or "us-Cable-Standard-center-frequencies-QAM256" (for digital cable), as these will lead dvbscan to proceed to do a full search of the channel frequency spectrum.

If you're a DVB-T or DVB-C user:

w_scan can also be used to create an initial scan file via the command

w_scan -x >cc-Ttttt

If you choose to create an initial scan file (and you know the name of your local transmitter or cable provider), you can send the resulting file to the dvb mailing list after checking that it hasn't already been posted or added to the scan directory in the dvb-apps repository.
NOTE: w_scan >= 20090504 needs additionally option -c <COUNTRY>

Create your own initial scan file

During the scan

After initiating the dvbscan command, a lot of output data will be produced in the shell. The first thing that dvbscan does is to report which file it is parsing information from and with what hardware device that this information is going to be utilized.
For example:

Next dvbscan commences a search through all the frequencies listed in an initial scan file. During this phase, the utility will update the progress of the scan within its output. Do note that this process can take some time to complete, particularly if the initial scan file contains a long list of frequencies to test. The information presented provides details on the channels being detected during the scan. Often many lines of transponder information are reported. Here are some examples:

This is the tuning information for the first transponder. Each transponder can transmit multiple programs and further discussion about their contents is provided later below. Note that the information presented doesn't really say if you can actually make use of the streams that are detected. This is particularly true in the case of cable systems, which tend to encrypt most channels. So while dvbscan is perfectly capable of detecting such channels, you may very well be out of luck on the viewing end.

Do not be alarmed by such "tuning failed" messages, as this is not fatal. It simply means that no signal was found on that particular frequency -- it's possible that the initial scan files contain information about stations that are not yet, or no longer, in service, or it may imply that you presently lack a strong enough signal for reception to occur.

After the scan completes

Eventually, upon completion of its search, dvbscan outputs a list of services that it found.

Note: The actual number of available services it finds will, of course, depend upon several factors (the number of services available in your area and those related to signal strength). Check dvbscan's output with a list of known services available for your area. If you are missing some services, then try to troubleshoot your antenna and/or cable configuration. Hopefully you will be able to improve the environment for signal reception. If you are unable to obtain a particular service, then you may just be out of range or subject to inhospitable environmental conditions that your hardware just cannot overcome to achieve reception. If zero services where found, perhaps check your antenna and/or cable lead ... maybe it's simply a case that its not plugged in at all ;-)

Each line in the output consists of a number of fields delimited by colons. The exact number of fields will depend upon the type of scan you where performing, as will be exemplified below. In any regard, these lines of output are szap/tzap/czap/azap compatible and, as such, can be copied and pasted into a simple text editor to create a "colon-separated" channels.conf file. Alternatively, one can automate the creation of a channels.conf file as described later below.

The frequencies shown here in Hz correspond to 226.5 MHz for ABC and 219.5 MHz for TEN. Note that the first two channels are the same frequency, which means that they're both present in the same MPEG transport stream, but are distinguished by their respective PIDs. Looking at the values, it's clear that ABC DiG Jazz is a radio station, since it doesn't have a video PID. Less clear is why the ABC HDTV stream (a known TV channel) does not have an audio PID. This is a real issue: this means that when tuning to that stream, no audio is output. We'll look at how to solve this problem later below.

Notes:

These fields will vary depending on the type of modulation; the ones shown are for QFDM (and, paradoxically, not for QAM). For other forms of modulation, the meanings of the fields differ. See the source code (and document it, please!) at util/scan/dump-zap.c.

If a channel has a video PID of 0 and the audio PID is not 0, then it's probably a radio channel.

if dvbscan detected a channel but the signal was too weak for reliable reception, the video and audio PIDs (third- and second-last numbers in the output line) will likely be shown as 0.

So, after reviewing the above information, you should now be able to determine the pertainent information from the output of any scan. As a further example,

conveys that the channel BBC ONE is found on frequency 578000000 Hz, and has the two PIDs 600 and 601 for the video and audio stream.

Sample output from an ATSC scan:
There aren't as many colon delimited fields in the output as there would be as in the case of a scan of DVB-{C,T,S} system counterparts, but the substance of the output is largely the same, as can be seen in the following sample list:

Creating a channels.conf file

Next create a "channels.conf" file. This file takes the data for your available TV-channels, as shown above, and stores it for tuning use by simple "zapper" programs, such as tzap, or for higher level applications like MPlayer or Xine.

Each of the "zapper" utilities will, by default, expect to find the channels.conf file in the specific hidden (dotted) directory off your "home" directory. For example, for DVB-C tuning with czap, you would set up a ~/.czap directory. Likewise, for use with szap, you would make a ~/.szap directory, and so forth. Here are some examples of how to automagically create the channels.conf file by directing the stdout from the dvbscan command to be placed in a file in a given directory:

one step scan and channels.conf creation (i.e if you were paying attention, don't need to run dvbscan twice as was like performed above)

~/.{a,c,s,t}zap directories for the channels.conf is just the default location. Each of the zapper utilities can use any other location for channels.conf provided you specify its location ... (i.e. ~/. is really just a ease of use) ... see the zap articles for more usage detail

the dvb-apps package contains a number of files that are essentially channels.conf files for given localities. These will probably be installed on you system. For example, /usr/local/share/dvb/zap/dvb-t/au-Adelaide is a canned version of the output of dvbscan. It may be out of date, so it's better to generate it from dvbscan, but if you can't get dvbscan to work, you might get further by using this file.

An alternative method of using dvbscan to check a specific frequency

Tune to that specific frequency (e.g. using szap/tzap/czap/azap) and then use

dvbscan -c

A word about dvbscan and audio streams

scan does not always seem to correctly recognize audio streams for a television channel.

Example, in Australia, most channels broadcast HDTV with AC3 audio, which scan does not recognize when invoked as above. The result is the output shown above for ABC HDTV: no audio.

This is almost certainly a bug in scan. Until it is fixed, you can proceed in the following way:

This output was limited to the interesting information. The last two lines show the output for ABC HDTV and ABC TV Adelaide. ABC TV Adelaide has a video pid 0x200, an audio pid 0x28a, and an AC3 pid 0x294. The meanings of the other values still need to be documented.

By contrast, ABC HDTV has a video pid 0x90a, and AC3 pid 0x90b--and no audio pid. This is the problem. In the output from scan based on the transmitter data, the corresponding values are (leaving out the middle of the lines, which aren't of interest here):

ABC HDTV: ... :2314:0:592
ABC TV Adelaide: ... :512:650:593

As described above, the third-last value is the video pid, and the second-last value is the audio pid. In this output they're in decimal, while in the output of dvbscan -c they're in hexadecimal; but they correspond.

To work around the lack of audio pid in ABC HDTV, convert the value of the AC3 pid (0x90b) to decimal (2315) and edit the channels.conf file: