LinuxTVWiki - User contributions [en]

Dvb constellation

2013-05-12T22:08:03Z

CityK: add some links

Patches for Linux kernel (v4l code) and for v4l-utils should be applied to obtain I&Q constellation described in this article.

Patch for Linux kernel:
http://stand.netup.tv/downloads/iq_constellation.patch

Patch for v4l-utils:
http://stand.netup.tv/downloads/iq_constellation_v4l-utils.patch

== Receiving I&Q data from DVB demodulator ==

<pre>
dvb_const -f /dev/dvb/adapter0/frontend1 -o iq_dvbc_qam256.txt -p 100000
</pre>

received data (100000 points) will be saved into iq_dvbc_qam256.txt file. File format is simple text csv. Example of received data:

<pre>
-175,-45
-46,110
-241,-178
176,11
-50,173
16,44
</pre>

Values are signed. First I part, second Q part.

== Visualization of received data ==

'''dvb_const_plot''' utility build PNG image with constellation:

<pre>
dvb_const_plot -i iq_dvbc_qam256.txt -o iq_dvbc_qam256.png -c "SNR=38dB QAM256"
</pre>

resulting image will be saved into iq_dvbc_qam256.png. Here is example of images received with [[NetUP_Dual_DVB_T_C_CI_RF|NetUP Dual DVB-T/C-CI RF]] and [[NetUP_Dual_DVB_S2_CI|NetUP Dual DVB S2 CI]] cards.

<gallery>
File:Iq_dvbc_qam16_38db.png|QAM16 constellation (DVB-C)
File:Iq_dvbc_qam64_38db.png|QAM64 constellation (DVB-C)
File:Iq_dvbc_qam128_38db.png|QAM128 constellation (DVB-C)
File:Iq_dvbc_qam256_36db.png|QAM256 constellation (DVB-C)
</gallery>

<gallery>
File:iq_dvbs2_32apsk.png|32APSK constellation (DVB-S2)
File:iq_dvbs2_16apsk.png|16APSK constellation (DVB-S2)
File:iq_dvbs2_8psk.png|8PSK constellation (DVB-S2)
File:iq_dvbs2_qpsk.png|QPSK constellation (DVB-S2)
</gallery>

== Also See ==
* [[Quadrature Amplitude Modulation]]
* [[Quadrature Phase Shift Keying]]

== External links ==

[http://en.wikipedia.org/wiki/Constellation_diagram] Constellation diagram

[http://www.cisco.com/en/US/prod/collateral/video/ps8806/ps5684/ps2209/prod_white_paper0900aecd805738f5.html] Digital Transmission: Carrier-to-Noise, Signal-to-Noise & Modulation Error Ratio

Hardware Device Information

2013-03-02T19:14:22Z

CityK: Changed the message after pondering a post I had read elsewhere -- the onus is on USERS to keep the info current; there is/are no particular person(s) committed to such task

__NOTOC__
__NOEDITSECTION__
<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;">
{| style="background-color:#F7F9FB;" cellspacing=0 cellpadding=5 border=0
| valign=top | [[Image:Hardware_icon.png|50px]]
|
=='''Hardware Device Information:'''==
* [[List of Device Vendors|Sortable List of Device Vendors]]
|}

{{Note|The information contained within the respective sections is compiled by user submissions. Hence, it is far from exhaustive and, secondly, may contain errors,
despite the good intentions and best efforts to do otherwise. Please contribute and help to keep these lists up-to-date and factual, so that they are useful for everyone!}}

{|valign=top cellpadding=0 cellspacing=0 width=100%

|valign=top bgcolor=#F7F9FB width=32%|
[[Image:V4l_label.png|50px]] '''Analog Devices:''' 

* [[Graphics cards with TV Tuner and/or Capture facilities]]
* [[Video via PCI]]
* [[Video via PCI Express (PCIe)]]
* [[Video via USB]]
* ''Other analogue devices:''
** [[V4L IEEE1394 devices|IEEE1394 devices]] (aka FireWire or i.LINK)
** [[Loopback]]
** [[Radio devices|Radio]]
** [[Scanners]]
** [[Webcam Devices|Webcams]]

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=32%|
[[Image:DVB_label.png|50px]] '''Digital Devices:''' 

* [[ATSC Devices]]
* [[DMB-T/H Devices]]
* [[DVB-C Devices]]
* [[DVB-S Devices]]
* [[DVB-S2 Devices]]
* [[8-PSK Turbo Coded Devices]]
* [[DVB-T Devices]]
* [[DVB-T2 Devices]]
* [[ISDB-T Devices]]
* [[Pre-configured DVB Systems and Set Top Hardware]]''

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=32%|
[[Image:Peripheral_component_icon.png|50px]] '''Peripheral Components:''' 

* [[Antenna]]s (Rooftop, Indoor, Satellite Dishes)
* [[DD receiver|Dolby Digital receiver]]
* [[DiSEqC related hardware]]
** Switches, attenuators, and amplifiers
* [[DVB Conditional Access Modules]]
** [[Conditional Access Module Usage Examples]] (sorted by country)
* [[Remote Controllers]]
** [[Remote controllers-V4L|Remote controllers (V4L article)]]

'''Miscellaneous:'''
* [[User Modifications to Supported Devices]]
|}
</div>

How to Obtain, Build and Install V4L-DVB Device Drivers

2013-03-02T18:54:20Z

CityK: /* Retrieving and Building/Compiling the Latest V4L-DVB Source Code */ minor descriptional edits and corrections

The LinuxTV project hosts the latest set of Linux kernel driver modules for [[What is V4L or DVB?|V4L-DVB devices]]. This page contains information to help an "end user" install these device drivers in a GNU/Linux system.

{{Note|This article assumes that:
* your device is actually supported by the drivers -- Just because your board happens to have a chip on it that corresponds to some existing driver does NOT mean your product is supported. The driver has to be aware that it's related to some hardware (typically through the [[Supported_Hardware#Determining_the_Device's_Identity|subsystem ID from the USB ID or PCI ID]]). If the driver doesn't recognize/bind to your particular hardware, then the module will probably load but then proceed to not do anything. In other words, support for your device would have to be added to the driver.
* you have already physically installed the hardware device into, or connected it to, your system. (Refer to the manufacturer's instructions for such details)}}.

== Software Requirements ==
===Kernel Support===
The LinuxTV V4L-DVB drivers will work only in conjunction with relatively modern 2.6 kernels; specifically 2.6.31 and up.

===Additional Software Requrirements===
In order to be able to build the V4L-DVB kernel driver modules, you will need:
* kernel-source or kernel-headers
* (OpenSuSE and fedora only) kernel-devel
* (Debian) libdigest-sha1-perl
* make
* gcc
* git
* patch
* patchutils
* libproc-processtable-perl ("perl-Proc-ProcessTable")
If these packages are not currently installed on your system, you should do so now.

==Retrieving and Building/Compiling the Latest V4L-DVB Source Code==
There are a couple of different methods by which you can obtain and build the latest source code. Regardless of which route you take, all are performed from the command line (either within a console or terminal emulator). The "basic" method is likely appropriate for most end users, though, in particular cases, some users will have to use the slightly more "manually intensive" approach (which is effectively, for all intents and purposes, really just the same as the "basic" method, but performs the steps in a piecemeal fashion which affords you the opportunity to tailor the source code, or the "make"/build process, as might be required in your particular situation). Again, before proceeding with any of the approaches, make sure you have installed all the prerequisite software listed above.

{{Note|If you are using Ubuntu, you were previously very likely to run into a fatal compilation error within the v4l-dvb build process when it reaches the firedtv module. The reason for this is because Ubuntu had a bug in their packaging of the kernel headers. This seems to be fixed on a fully updated systtem (5 July 2011) This was a long standing issue, and one of the most frequently reported on the mailing list. 
If you still have the problem, you should be able to correct this compilation problem by following the more manual procedure listed below. In particular, before proceeding to build the modules, you will have to edit the file ''v4l/.config'' and change the line for the firedtv driver from <nowiki>"firedtv=m" to "firedtv=n"</nowiki>.}}

{{Note|If you are having build failures like "implicit declaration of function 'mfd_get_data'" try editing v4l/Makefile.media, and just comment out anything related to CONFIG_*_TIMBERALE. [[http://sourceforge.net/mailarchive/message.php?msg_id=27353778 Source]] }}

{| class="wikitable"
|+'''Retrieving the Source Code & Building/Compiling the Modules'''
|-
! "Basic" Approach !! Developer's Approach !! More "Manually Intensive" Approach

|-
| valign=top |
git clone git://linuxtv.org/media_build.git
''(alternately to get only the latest revision without history)
git clone --depth=1 git://linuxtv.org/media_build.git''
cd media_build
./build

These commands will download the newest tarball of the source code from linuxtv.org, apply the backport patches to it and then build/compile the source via the included script build.sh.

NB: to add a patch copy the .patch file to the backports directory, and add the patch file as a line to the {kernel-version}_series file in the packports dir.
| valign=top |
~ $ git clone git://linuxtv.org/media_build.git
''(or ~ $ git clone --depth=1 git://linuxtv.org/media_build.git)''
~ $ cd media_build
~/media_build $./build --main-git
{{Note|'''The build script will clone the entire media-tree.git, which will take some time'''}}

In order to modify a driver foo.c:

~/media_build $ cd media
~/media $ gedit drivers/media/video/foo.c
~/media $ make -C ../v4l
~/media $ make -C ../ install
~/media $ make -C .. rmmod
~/media $ modprobe foo

(some procedure to test the "foo" driver)

To generate a patch, use:

~/media $ git commit -as

Then submit the patch upstream. If your sendmail is properly configured, you can easily send the patch upstream with:

~/media $ git send-email HEAD^1

or, to send a patch series:

~/media $ git send-email ''initial_branch''

Where ''initial_branch'' is the name of a branch of a changeset number for the last patch before your changes.

|
git clone git://linuxtv.org/media_build.git
cd media_build/linux
make tar DIR=<some dir with media -git tree>
make untar
cd ..

If you need to make any sort of change or modification to the source code, now is the time.

<div style="border: solid 1px; border-color: blue; margin: 1em; padding: 1em; background-color: Lavender;">
'''Optional Pre-Compilation Steps''' 
These optional command steps are applicable only in certain situations approaching a new build of the driver set, or for experienced users wishing to streamline the build process to consist of only those components they want to install.
* <code>make rminstall</code> ... you would use this to remove the currently installed driver set (located within the relevant ''/lib/modules/["kernel version"]/kernel/drivers/media'' directory to which they were installed)
* <code>make distclean</code> ... cleans up the build configuration environment ... noteworthy is that it will set things up such that a following "make" build process will be against "''/usr/src/[uname -r]''” kernel source
* <code>make menuconfig</code> ... this will open up the ncurses based menu that allows you to select only those components you wish to build and install

The building system offers some other make targets that may be useful for advanced users or developers. For listing the supported targets, please use <code>make help</code>.</div>

Next, build/compile the modules from the source code with the command:
make
{{Note|For multi-core processor systems, the ''make'' command has available options that can be beneficial in terms of the reducing the amount of time required for the process' completion. Specifically, you can run "''make -jN''" (where "''N''" <nowiki>=</nowiki> 1 + the number of cores your cpu has ... i.e. if you have a dual core cpu use: ''make -j3'' )}}

|}
===Information Regarding the Build Process===
Generally, this step will tend to take a while to complete; being dependent upon both the number of modules being built and your system's processing power.

You can monitor the build progress via the console output. You will notice that a ''/v4l'' directory will have been created and within which the completed *.ko module files are written. Some drivers included within the snapshot may have their own requirements in regards to the kernel that you must be running in order for the module to be built; such cases can be found listed at the beginning of the build process' console output.

The entire build process should complete without error. If any errors are encountered, the compilation will be halted and, at this point, you should not attempt to proceed any further (unless you really, really enjoy experiencing the outcome of a preordained failure). Errors that prevent building a particular V4L-DVB snapshot do indeed surface from time to time, but these are usually corrected quickly upon notification from an end user submitted [[Bug Report|bug report]], or upon detection from the daily automated build tests (see note below). If you have run into a build error via the "basic" approach outlined above, you may wish to see if you can remedy the error and attempt a module build via the more "manually intensive" approach also outlined above.

{{Note|'''The Daily Automated Build Tests''' 
Hans Verkuil has set up an automated daily build of the V4L-DVB source code upon all supported kernels, as well as testing that very same upon several CPU architectures. A brief synopsis of the results from those tests is published each day on the Linux-Media Mailing List (LMML) under a message subject heading prefix of "''[cron job] v4l-dvb daily build ...''". A link to more detailed results of these tests is also provided within that message or can be found directly from [http://www.xs4all.nl/~hverkuil/logs/ here].}}

If you do run into any problems during the build step, you should:
* first, see whether the issue is already known or not -- consult the results of the daily automated build tests (see note above)
* if it appears that this is a new issue, please [[Bug Report|inform the developers of the bug via the LMML]] (preferred) or thorough one of the irc.freenode.net irc channels (#v4l or #linuxtv or #dvb).
* you may also wish to consult any errata that might be found on this article's talk page

In general, if the source builds correctly, it is likely that the drivers will work, though this is not a guarantee.

== Installing the Compiled Driver Modules ==
The next step is to install the kernel driver modules by executing:
sudo make install
The command above will prompt you for your root password, and will then copy the *.ko module files you built in the above step into the ''/lib/modules/[kernel version]/kernel/drivers/media'' directories.

{{Note|If your distribution doesn't support the sudo command (i.e the command line returns ''"bash: sudo: command not found"''), use the "su" command instead. "su" will prompt you for the root password, and after which entering, you can then proceed with the command. Ex.:
su
make install
}}
 
{{Note|In the case where you have more then one kernel installed but have used the pre-compilation option of "make distclean", the new modules will be installed only into the ''/lib/modules/[uname -r]/kernel/drivers/media'' directory}} 

== First Use: Out with the Old, In with the New==
{|
| valign=top |
Before trying to use the device with your newly installed driver set, you should remove from system memory any older versions of related modules that may have been loaded by the running kernel; otherwise, you will likely run into various fatal mismatch errors -- typified by an "unknown symbol" or "unknown parameter" -- as a result of your system trying to work from a mixture of old and new modules.

To achieve a [[Wikipedia:Tabula rasa |clean slate]] state, you could either: 

'''1. Reboot:''' Perhaps the most straightforward thing to do at this point, particularly for Linux newbies, is to just restart your system; the reboot will, obviously, clear out the old modules loaded into memory and, as an added bonus, create a fresh running environment under which the new modules should have been automagically loaded into system memory.

Or, on the other hand,

'''2. Take care of business yourself:''' More experienced users might prefer to use more eloquent approaches. For example, using
sudo make unload
will essentially (and similar as to manually using "rmmod" commands) remove all older modules for the device that might be currently loaded in memory by the running kernel. After which, one can then load, from the newly installed device driver set, the appropriate modules for the device using relevant
modprobe ''driver_name''
commands.

| valign=top halign=right width=30% |
<div style="border: solid 1px; border-color: blue; margin: 1em; padding: 1em; background-color: Lavender;">
'''For Advanced Users''' 
The following information is likely useful only for developers. After building the modules as per usual ("make"), and without needing to install them, you can:
* remove all older modules from memory at once using "make unload" and
* then insert all the newly built modules into memory for the running kernel with "make load"
Alternatively, to perform the previous two commands ("make unload" and "make load") in a single step, you can use "make reload"

Note, however, that it is highly recommended that you avoid using either the make load or make reload options, as they will end up inserting all V4L-DVB device drivers into memory, and that may introduce instability, or complicate testing.
</div>
|}
Regardless of which approach you take to remove the old modules and to insert the new ones, the end result should be the same. In addition, upon future starts of your system, your device should "automagically" be detected and will have the appropriate driver modules loaded into memory.

===If the Modules load correctly:===
Provided that the modules were loaded correctly into system memory:

'''1. They should be listed in ''/proc/modules''''': you can use either <code>cat /proc/modules</code> or, even better, <code>lsmod</code> to see this content.

Which modules should you be looking for? Well, the answer to that question depends entirely upon the chipsets used by your device -- see the relevant wiki article for your device for a listing of such components and required drivers (or search the web if such information does not exist. '''Note''': Please add any information missing from the wiki!)

'''2. They should provide some indication within your system log''': you can consult the output from the "<code>dmesg</code>" command or directly review your system log file (typically housed within the ''/var/log'' directory) for indication that they have been successfully loaded and that the device is now correctly configured for operation. Examples of successful module loads are provided by users under the "Sample kernel output" section in many device articles witin the wiki.

'''3. The device manager [[Wikipedia:udev|udev]] will "automagically" create appropriate [[Device nodes and character devices|device nodes]] on ''/dev''''': 
'''(a) For a DVB device''', you should now have a non-empty ''/dev/dvb'' directory. You can check on whether this is true for you with the following command:
: <code>ls -l /dev/dvb/</code>
(alternatively, you can browse your directory structure with the graphical file manager of your choice). If you have a single DVB device installed in your system, then the output of the above command should reveal that /dev/dvb/ is populated by adapter0. Digging further,
: <code>ls -l /dev/dvb/adapter0 </code>
reveals the [[Device_nodes_and_character_devices#DVB_character_devices|character devices]] associated with adapter0 for which the drivers have control. If you have more then one DVB device, you can see the same for all with
: <code>ls -l /dev/dvb/adapter* </code>

'''(b) For a V4L device''', you should now have a non-empty ''/dev/v4l'' directory. You can check on whether this is true for you with the following command:
: <code>ls -l /dev/v4l</code>
Digging further,
: <code>ls -l /dev/v4l/by-path </code>
reveals the symbolic links to the [[Device_nodes_and_character_devices#V4L_character_devices|character devices]] associated with your V4L adapter for which the drivers have control. The most typical of which is ''/dev/video0''. If you have more then one V4L device, you can see the same for all with
: <code>ls -l /dev/video* </code>

===If the Modules did not load correctly or the device is still not configured correctly for use:===
There could be several reasons why you may have encountered a module loading error or, absent such an error, why the device is still not configured correctly for use, even after having correctly followed the steps from the above procedure. If either of these cases applies, the very first thing you should do is [[Supported Hardware|check whether your device is actually supported]] by the driver (see the very first note at the top of this page). Next, provided your device is supposed to be supported, check within your system log/dmesg for any messages that may give indication as to the problem. The following points address a few common trouble spots:

'''Module Load Order Can Matter'''
* in cases where loading more then one module is necessary, the order in which you load the modules can matter!

'''Sometimes Automagic just isn't Automagic'''
* If a module was, for whatever reason, not loaded, you can try manually loading it with the appropriate ''modprobe'' command.

'''Unresolved Symbols'''
* if you tried the second method ("make unload" followed by an appropriate modprobe command) but encountered errors in relation to unresolved symbols, e.g. using the saa7134 module as an example:
sudo modprobe saa7134
FATAL: Error inserting saa7134 (/lib/modules/''[your kernel version]''/kernel/drivers/media/video/saa7134/saa7134.ko):\
Unknown symbol in module, or unknown parameter (see dmesg)
please try a system reboot before filing an [[Bug Report|error report]]. Irregardless of what caused the unresolved symbols errors, usually, after performing the reboot, you will find that the install was actually successful and the drivers will work as intended.

* Special case: If your system uses compressed kernel modules, after running the "make install" command of the V4L-DVB installation process, you could end up with a mixture of new modules (*.ko) and their older compressed version (*.ko.gz) installed. If the system attempts to concurrently load both sets into memory, you are bound to run into modprobe insertion errors (eg. unknown symbol or unknown parameter). All conflicting *.ko.gz files must be removed. The following command line can help you locate these conflicting files in all your installed kernels:
for file in `find /lib/modules -name "*.ko"`; do if <nowiki>[[</nowiki> -e $file.gz <nowiki>]]</nowiki>; then echo "$file.gz should be removed"; fi; done
Usually all conflicting module files resulting of v4l-dvb installation will be located in:
/lib/modules/''[your kernel version]''/kernel/drivers/media
Once the conflicting *.ko.gz have been moved elsewhere or renamed (to *.ko.gz.disabled for example), use the v4l-dvb reload command and, to be safe, also add a "depmod" step in order to rebuild modules dependencies):
make reload
depmod -a
Your new modules should now be loaded correctly.

'''A Note on Firmware'''
* You have all the modules active (listed in lsmod) but device nodes are nowhere to be found: The problem may be as simple as the [[Firmware|firmware]] for the device not being loaded; some devices also require a [[Firmware|firmware]], which is uploaded from the host PC to the device, in order to operate.

In some cases, when the device is correctly recognized, the associated drivers provide information as to which firmware file is required -- look in the system log output. For example, for many [[TechnoTrend]] & [[Hauppauge]] (and other similar "premium" cards), if the dvb-ttpci firmware is not available you will observe an error such as:
<pre> dvb-ttpci: could not load firmware, file not found: dvb-ttpci-01.fw
dvb-ttpci: usually this should be in /usr/lib/hotplug/firmware or /lib/firmware
dvb-ttpci: and can be downloaded from http://www.linuxtv.org/download/dvb/firmware/</pre>
Resolving that missing firmware issue should then result in proper detection and configuration of your device.
In other cases, obtaining the correct firmware is not so straightforward a task. The very first thing you need to know is what device you're using; see "[[Supported_Hardware#Determining_the_Device's_Identity|Determining the Device's Identity]]". Once you have established which particular device you are in possession of, you can then move on to [[Firmware#Acquiring the Firmware|obtaining the correct firmware]]. In addition, information in wiki articles (eg. such as [[DVB-T USB Devices]]) will cite the appropriate firmware required. If you're still at a loss, a Google search may shed light on what file you need. Note, however, that not all supported devices have easily available firmware (eg. Hauppauge HVR 1100 & 1300). Firmware for such cards could be loaded via temporary installation in a Mirosoft Windows System with the manufacturer-supplied drivers.

In any regard, once you find and obtain the necessary firmware for your device, copy it into the appropriate directory; the directory location depends upon that used by your distro, but typically it is:
*/lib/firmware
Consult resources for your distro if its preferred location is somewhere otherwise.

==Some Further Documentation==
* See [[Testing your DVB device]] for instructions on testing your newly installed DVB device

[[Category:Software]]
[[Category:Drivers]]

Saa7134-alsa

2013-01-04T01:38:47Z

CityK: /* Record with mencoder */ punctuation

Also see the [[Saa7134-alsa redundant]] article; whose info (if it is not redundant) should/will be merged (preferably by its authour so that proper user attribution is maintained for information additions) into this original existing article.

=== How to use alsa or oss with saa7134 ===

Starting with kernel 2.6.15, the module saa7134-alsa lets you use ALSA to get sound directly from your capture card. From 2.6.16 you can use this module with more than one capture card.

In kernel 2.6.16, the saa7134-oss module is also separated out, and the two modules are treated in much the same way; you can build both and switch between them, though both cannot be loaded at once.

=== Insmod parameters ===

Now that both alsa and oss DMA sound have been separated out as distinct modules, it is no longer necessary (though it is not forbidden) to include the insmod parameter "alsa=1" or "oss=1".

On the other hand, on the 2.6.16 kernel, it's not safe to use the parameter "disable_ir=1" to turn off the infrared system for the remote -- that caused an oops. This is fixed in 2.6.17.

In the case of more than one card, you can use something like this:

saa7134 card=2,2,2,2 tuner=43,43,43,43 video_nr=1,2,3,4 vbi_nr=1,2,3,4 radio_nr=1,2,3,4

In dmesg, you should see this type of content murmuring:

<pre>
input: saa7134 IR (LifeView FlyVIDEO30 as /class/input/input5
tuner 5-0061: chip found @ 0xc2 (saa7133[3])
tuner 5-0061: type set to 43 (Philips NTSC MK3 (FM1236MK3 or FM1236/F))
tuner 5-0063: chip found @ 0xc6 (saa7133[3])
saa7133[3]: i2c eeprom 00: 69 51 38 01 10 28 ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: registered device video4 [v4l2]
saa7133[3]: registered device vbi4
saa7133[3]: registered device radio4
</pre>

To then load the new driver that lets you get sound off the PCI bus via ALSA or OSS, you would normally just issue "sudo modprobe saa7134-alsa" or "sudo modprobe saa7134-oss". You can also deliberately assign the enumeration; for instance, for four cards, do this for alsa:

sudo modprobe saa7134-alsa index=1,2,3,4

Again, dmesg approves:

<pre>
saa7134 ALSA driver for DMA sound loaded
saa7133[0]/alsa: saa7133[0] at 0xf5006000 irq 19 registered as card 1
saa7133[1]/alsa: saa7133[1] at 0xf5007000 irq 20 registered as card 2
saa7133[2]/alsa: saa7133[2] at 0xf5004000 irq 21 registered as card 3
saa7133[3]/alsa: saa7133[3] at 0xf5005000 irq 22 registered as card 4
</pre>

If instead you use OSS, issue this to determine enumeration:

sudo modprobe saa7134-oss dsp_nr=1,2,3,4 mixer_nr=1,2,3,4

You should see this in dmesg:

<pre>
saa7134 OSS driver for DMA sound loaded
saa7133[0]: registered device dsp1
saa7133[0]: registered device mixer1
saa7133[1]: registered device dsp2
saa7133[1]: registered device mixer2
saa7133[2]: registered device dsp3
saa7133[2]: registered device mixer3
saa7133[3]: registered device dsp4
saa7133[3]: registered device mixer4
</pre>

Note that if you use saa7134-oss in Debian, and build your kernel with ALSA as modules, you may need to add saa7134 to the OSS-module-list to keep your OSS emulation under ALSA (cf. [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=359851 #359851]):

echo saa7134 >> /usr/share/linux-sound-base/OSS-module-list

If OSS emulation is not working, some applications (such as VLC) that expect ALSA sound devices won't be able to find the legacy OSS devices created by saa7134-oss.

If your ALSA is built into the kernel rather than as modules, you won't need to worry about this.

===Insert modules on boot===

To insert the modules with these parameters on boot, you can create a file called /etc/modprobe.d/saa7134 with the following lines (adjust card and tuner numbers as required):

options saa7134 card=2,2,2,2 tuner=43,43,43,43 video_nr=1,2,3,4 vbi_nr=1,2,3,4 radio_nr=1,2,3,4
install saa7134 /sbin/modprobe --ignore-install saa7134; /sbin/modprobe saa7134-alsa
options saa7134-alsa index=1,2,3,4

Your distribution may require you to put these lines into /etc/modprobe.conf; this is not a good idea in Debian, since the files in /etc/modprobe.d will then be ignored.

If instead you use OSS, these lines will load the modules for four cards:

options saa7134 card=2,2,2,2 tuner=43,43,43,43 video_nr=1,2,3,4 vbi_nr=1,2,3,4 radio_nr=1,2,3,4
install saa7134 /sbin/modprobe --ignore-install saa7134; /sbin/modprobe saa7134-oss
options saa7134-oss dsp_nr=1,2,3,4 mixer_nr=1,2,3,4

Note that once you've entered this information inside /etc/modprobe.d, your subsequent manual insertions will also make use of this information. Scripts, for instance, need not repeat it.

These instructions are of course specific to kernels 2.6.16 and later, as earlier kernels do not have separate DMA modules.

For kernels before 2.6.16, DMA sound via OSS is activated simply by the insmod parameter "oss=1".

=== Set permissions ===

Make sure your users are added to the group "audio" to get access to them -- in Debian, if your user name is "tv", you would use

adduser tv audio

=== List your capture devices ===

To get a list of your alsa capture devices, issue

arecord -l

You should see your regular sound card and the capture card(s):

<pre>
**** List of CAPTURE Hardware Devices ****
card 0: CK8S [NVidia CK8S], device 0: Intel ICH [NVidia CK8S]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CK8S [NVidia CK8S], device 1: Intel ICH - MIC ADC [NVidia CK8S - MIC ADC]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: SAA7134 [SAA7134], device 0: SAA7134 PCM [SAA7134 PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: SAA7134_1 [SAA7134], device 0: SAA7134 PCM [SAA7134 PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: SAA7134_2 [SAA7134], device 0: SAA7134 PCM [SAA7134 PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 4: SAA7134_3 [SAA7134], device 0: SAA7134 PCM [SAA7134 PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
</pre>

=== Configure the cards to record ===

Set the cards to record on channel 1 and max volume, using for instance

alsamixergui -c 1

for each of the cards.

=== Watch with mplayer ===

You should now be ready to watch live tv with mplayer, using something like this:

These are for rf connections:

US broadcast or satellite:
mplayer tv://$channel -tv driver=v4l2:device=/dev/video0:chanlist=us-bcast:alsa:\
adevice=hw.1,0:amode=1:audiorate=32000:forceaudio:volume=100:immediatemode=0:norm=NTSC

If you're using a satellite box, $channel should probably be set to 3 or 4. If that doesn't work, try the US cable TV setup below.
If you're getting your broadcast off the air, you can run the scantv utility to detect stations and set $channel to the local channel for your area.

US cable:
mplayer tv://"insert channel" -tv driver=v4l2:device=/dev/video0:chanlist=us-cable:alsa:\
adevice=hw.1,0:amode=1:audiorate=32000:forceaudio:volume=100:immediatemode=0:norm=NTSC

Here again you can run the scantv utility to detect the channels available from your provider, or you can use your provider's channel table.

Europe cable:
mplayer tv://"insert channel" -tv driver=v4l2:device=/dev/video0:chanlist=europe-west:alsa:\
adevice=hw.1,0:amode=1:audiorate=32000:forceaudio:volume=100:immediatemode=0:norm=PAL

Note the ''norm='' and ''chanlist='' parameters. Adjust as required for your location.

If "adevice=hw.1,0" doesn't work, try simply "adevice=hw.1". Some tuners require "adevice=hw.2" -- for instance, on a board with nforce 3 250/gb chipsets. If others experiance this with other boards, please update.

=== Record with mencoder ===

It may be simpler to get sound during recording than during playback. The example given below, in which "$DEV" is the number of the device node, is known to produce good sound:

mencoder -tv driver=v4l2:device=/dev/video$DEV:fps=30000/1001:chanlist=us-bcast:\
audiorate=32000:alsa:adevice=hw.$DEV:input=0:amode=1:normid=4:width=576:height=432 \
-ovc x264 -x264encopts threads=2:bitrate=500:bframes=2:subq=1:me=1:frameref=4:8x8dct \
-oac mp3lame -lameopts cbr:br=64 -endpos $TIM -o $DIR/$FIL.avi tv:// > /dev/null

So the alsa device is simply called hw.1 -- not hw.1,0. The line is taken from the [[V4L channel script]]. You may find you need to use hw.2 instead, depending on the audio hardware on your system.

Neither ffmpeg nor transcode as yet have ALSA support.

Because so many applications still appear to have difficulties accessing ALSA's odd device enumeration, the OSS module for DMA sound continues to be useful. You can also use ALSA's OSS emulation with saa7134-alsa to get /dev/dspX devices for OSS-aware applications.

=== Using with Mplayer, Mencoder with Gentoo default Pulseaudio and Alsa config ===

If you are using default SAA7134 Pulseaudio settings (Analog Stero Input with the video channel being captured), then you can try command line for composite signal capture:
mplayer -tv driver=v4l2:device=/dev/video1:audiorate=32000:alsa:adevice=hw.1:immediatemode=0:input=1:amode=1:normid=7:width=720:height=576 -ao alsa -aspect 16:9 tv://
Note: the line above may work in place of trying with arecord and aplay, as per the example below (arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | aplay -), which may not work as well as expected.

For Mencoder, the following command line can be used:
mencoder -tv driver=v4l2:device=/dev/video1:audiorate=32000:alsa:adevice=hw.1:input=1:amode=1:normid=7:width=720:height=576 -o filename.mpg -ovc lavc -oac copy -lavcopts vcodec=mpeg2video:vbitrate=1000:\
keyint=5:aspect=16/9 -vf harddup -endpos 00:00:00 tv://
This line has been successfully tested, recording a good few gigabytes, from a Virginmedia V+HD box.

These lines were created with the help of this very page and the Mplayer/Mencoder manual.

=== ALSA audio with other applications ===

To hear the audio through ALSA using tvtime (or other programs that don't support it directly), run the following command after starting tvtime:

arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | aplay -

It basically records at 32kHz Stereo from the SAA7134 ALSA source (hw:1,0 or change accordingly), and plays it through your default ALSA output. Look at the options from aplay to change your output.

There might be a delay between the video and the audio. To avoid it, specify a device for aplay (not the 'default' device):

arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | aplay -D surround41

In order to get full surround sound from the stereo TV audio output, edit your /etc/asound.conf or ~/.asoundrc file as described in ALSA FAQ028 (http://alsa.opensrc.org/FAQ028) and use this device:

arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | aplay -D ch51dup

I don't know how to use ALSA directly with xawtv, motv, kdtv, tvtime, or zapping; if you do, please add it in here!

If using arecord still causes a delay between the video and the audio, try using sox:

sox -r 32000 -w -t alsa hw:1,0 -t alsa hw:0,0

Recent versions of sox no longer accept "-w" option, so just omit it. You can also use "--buffer" option to improve A/V synchronization, as the default 8KB buffer causes audio to lag significantly. On my system 2KB buffer is optimal:

sox --buffer 2048 -r 32000 -t alsa hw:1,0 -t alsa hw:0,0

Sox might get you mono sound, while all the alsa solutions cause delays. A combination has been known to work:

arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | sox -q -c 2 -r 32000 -w -t wav - -t alsa hw:0,0

If sox doesn't have alsa support, you can try this instead:

arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | play -q -c 2 -r 32000 -w -t wav -

Alternatively you can use alsa's oss-emulation with sox, which seems to result in way better latency then all the above:

sox -q -c 2 -s -w -r 32000 -t ossdsp /dev/dsp1 -t ossdsp -w -r 32000 /dev/dsp

=== Howto use Saa7134-alsa with Pulseaudio based-system ===

==== Redirect the sound with pulseaudio loopback module ====
* If your Saa713x device is properly configured and still can get no sound with TVTime, you may to redirect the input source from your TV card to the output of your sound card. You must load the [http://pulseaudio.org/wiki/Modules#module-loopback loopback module] with the command:
$ pactl load-module module-loopback
It will redirect the default input to the default output. The default input may not be the right one, you can change it in the 'Recording' tab with 'All Streams' displayed with Pulseaudio Volume Control (pavucontrol)
[[File:Pavucontrol.png|thumb|400px|center|alt=Example of loopback module selection in Pulseaudio Volume Control|Example of loopback module selection in Pulseaudio Volume Control]]

* The sound should now works. To automate the process, we will edit /etc/pulse/default.pa

First we need to now what is the TV card source name in pulseaudio. You can know the PCI address of your card with
$ lspci | grep SAA
It will output something like that :
04:08.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1)
'''04:08.0''' is the ''address'' of your card.

* Then, the following command
$ LANG=C pactl list | grep -A2 'Source #' | grep 'Name: ' | cut -d" " -f 2
will list all source detected by Pulseaudio.

For example, on my computer:
alsa_input.pci-0000_04_08.0.analog-stereo
alsa_output.pci-0000_00_10.1.analog-stereo.monitor
alsa_input.pci-0000_00_10.1.analog-stereo

The source name to use is '''the one with the right PCI address'''. Here the third one: alsa_input.pci-0000_'''04_08.0'''.analog-stereo

* Edit the file /etc/pulse/default.pa with your favorite text editor:
# gedit /etc/pulse/default.pa
Add the following line at the end of the file (replacing source with the one you found):
load-module module-loopback source=alsa_input.pci-0000_04_08.0.analog-stereo

* Restart Pulseaudio
$ pulseaudio -k

=== Sound distorted and high-pitched ===

* On some card, the sound is distorted, high-pitched as if it is accelerated. Some program will output buffer underrun in the terminal. Fixed for newer kernel: http://git.alsa-project.org/?p=alsa-kernel.git;a=commit;h=7b54360293c9d72b54e462d146c9376287d2f71b
* To correct this problem we need to change the autodetected sampling rate of the TV card from to 32000Hz.
* First we search for the current card parameters. Type :
$ pactl list | grep device_id
It will output sound card argument detected by udev :
Argument: device_id="2" name="pci-0000_'''04_08.0'''" card_name="alsa_card.pci-0000_04_08.0" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1"
Argument: device_id="0" name="pci-0000_00_10.1" card_name="alsa_card.pci-0000_00_10.1" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1"

As previously explained we will need arguments from the card with the right PCI address (here, the first line).

* Edit the file /etc/pulse/default.pa with your favorite text editor:
# gedit /etc/pulse/default.pa

* Before the line
### Automatically load driver modules depending on the hardware available
add the following
load-module module-alsa-card rate=32000 format=s16le $argument
where $argument is the line previously found without the last argument card_properties="module-udev-detect.discovered=1"

For example,
load-module module-alsa-card rate=32000 format=s16le device_id="2" name="pci-0000_04_08.0" card_name="alsa_card.pci-0000_04_08.0" tsched=yes ignore_dB=no

* Restart Pulseaudio
$ pulseaudio -k
[[Category:Drivers]]
[[Category:Software]]

Saa7134-alsa

2013-01-04T01:35:24Z

CityK: /* Using with Mplayer, Mencoder with Gentoo default Pulseaudio and Alsa config */ Remove first person

Also see the [[Saa7134-alsa redundant]] article; whose info (if it is not redundant) should/will be merged (preferably by its authour so that proper user attribution is maintained for information additions) into this original existing article.

=== How to use alsa or oss with saa7134 ===

Starting with kernel 2.6.15, the module saa7134-alsa lets you use ALSA to get sound directly from your capture card. From 2.6.16 you can use this module with more than one capture card.

In kernel 2.6.16, the saa7134-oss module is also separated out, and the two modules are treated in much the same way; you can build both and switch between them, though both cannot be loaded at once.

=== Insmod parameters ===

Now that both alsa and oss DMA sound have been separated out as distinct modules, it is no longer necessary (though it is not forbidden) to include the insmod parameter "alsa=1" or "oss=1".

On the other hand, on the 2.6.16 kernel, it's not safe to use the parameter "disable_ir=1" to turn off the infrared system for the remote -- that caused an oops. This is fixed in 2.6.17.

In the case of more than one card, you can use something like this:

saa7134 card=2,2,2,2 tuner=43,43,43,43 video_nr=1,2,3,4 vbi_nr=1,2,3,4 radio_nr=1,2,3,4

In dmesg, you should see this type of content murmuring:

<pre>
input: saa7134 IR (LifeView FlyVIDEO30 as /class/input/input5
tuner 5-0061: chip found @ 0xc2 (saa7133[3])
tuner 5-0061: type set to 43 (Philips NTSC MK3 (FM1236MK3 or FM1236/F))
tuner 5-0063: chip found @ 0xc6 (saa7133[3])
saa7133[3]: i2c eeprom 00: 69 51 38 01 10 28 ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: registered device video4 [v4l2]
saa7133[3]: registered device vbi4
saa7133[3]: registered device radio4
</pre>

To then load the new driver that lets you get sound off the PCI bus via ALSA or OSS, you would normally just issue "sudo modprobe saa7134-alsa" or "sudo modprobe saa7134-oss". You can also deliberately assign the enumeration; for instance, for four cards, do this for alsa:

sudo modprobe saa7134-alsa index=1,2,3,4

Again, dmesg approves:

<pre>
saa7134 ALSA driver for DMA sound loaded
saa7133[0]/alsa: saa7133[0] at 0xf5006000 irq 19 registered as card 1
saa7133[1]/alsa: saa7133[1] at 0xf5007000 irq 20 registered as card 2
saa7133[2]/alsa: saa7133[2] at 0xf5004000 irq 21 registered as card 3
saa7133[3]/alsa: saa7133[3] at 0xf5005000 irq 22 registered as card 4
</pre>

If instead you use OSS, issue this to determine enumeration:

sudo modprobe saa7134-oss dsp_nr=1,2,3,4 mixer_nr=1,2,3,4

You should see this in dmesg:

<pre>
saa7134 OSS driver for DMA sound loaded
saa7133[0]: registered device dsp1
saa7133[0]: registered device mixer1
saa7133[1]: registered device dsp2
saa7133[1]: registered device mixer2
saa7133[2]: registered device dsp3
saa7133[2]: registered device mixer3
saa7133[3]: registered device dsp4
saa7133[3]: registered device mixer4
</pre>

Note that if you use saa7134-oss in Debian, and build your kernel with ALSA as modules, you may need to add saa7134 to the OSS-module-list to keep your OSS emulation under ALSA (cf. [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=359851 #359851]):

echo saa7134 >> /usr/share/linux-sound-base/OSS-module-list

If OSS emulation is not working, some applications (such as VLC) that expect ALSA sound devices won't be able to find the legacy OSS devices created by saa7134-oss.

If your ALSA is built into the kernel rather than as modules, you won't need to worry about this.

===Insert modules on boot===

To insert the modules with these parameters on boot, you can create a file called /etc/modprobe.d/saa7134 with the following lines (adjust card and tuner numbers as required):

options saa7134 card=2,2,2,2 tuner=43,43,43,43 video_nr=1,2,3,4 vbi_nr=1,2,3,4 radio_nr=1,2,3,4
install saa7134 /sbin/modprobe --ignore-install saa7134; /sbin/modprobe saa7134-alsa
options saa7134-alsa index=1,2,3,4

Your distribution may require you to put these lines into /etc/modprobe.conf; this is not a good idea in Debian, since the files in /etc/modprobe.d will then be ignored.

If instead you use OSS, these lines will load the modules for four cards:

options saa7134 card=2,2,2,2 tuner=43,43,43,43 video_nr=1,2,3,4 vbi_nr=1,2,3,4 radio_nr=1,2,3,4
install saa7134 /sbin/modprobe --ignore-install saa7134; /sbin/modprobe saa7134-oss
options saa7134-oss dsp_nr=1,2,3,4 mixer_nr=1,2,3,4

Note that once you've entered this information inside /etc/modprobe.d, your subsequent manual insertions will also make use of this information. Scripts, for instance, need not repeat it.

These instructions are of course specific to kernels 2.6.16 and later, as earlier kernels do not have separate DMA modules.

For kernels before 2.6.16, DMA sound via OSS is activated simply by the insmod parameter "oss=1".

=== Set permissions ===

Make sure your users are added to the group "audio" to get access to them -- in Debian, if your user name is "tv", you would use

adduser tv audio

=== List your capture devices ===

To get a list of your alsa capture devices, issue

arecord -l

You should see your regular sound card and the capture card(s):

<pre>
**** List of CAPTURE Hardware Devices ****
card 0: CK8S [NVidia CK8S], device 0: Intel ICH [NVidia CK8S]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CK8S [NVidia CK8S], device 1: Intel ICH - MIC ADC [NVidia CK8S - MIC ADC]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: SAA7134 [SAA7134], device 0: SAA7134 PCM [SAA7134 PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: SAA7134_1 [SAA7134], device 0: SAA7134 PCM [SAA7134 PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: SAA7134_2 [SAA7134], device 0: SAA7134 PCM [SAA7134 PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 4: SAA7134_3 [SAA7134], device 0: SAA7134 PCM [SAA7134 PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
</pre>

=== Configure the cards to record ===

Set the cards to record on channel 1 and max volume, using for instance

alsamixergui -c 1

for each of the cards.

=== Watch with mplayer ===

You should now be ready to watch live tv with mplayer, using something like this:

These are for rf connections:

US broadcast or satellite:
mplayer tv://$channel -tv driver=v4l2:device=/dev/video0:chanlist=us-bcast:alsa:\
adevice=hw.1,0:amode=1:audiorate=32000:forceaudio:volume=100:immediatemode=0:norm=NTSC

If you're using a satellite box, $channel should probably be set to 3 or 4. If that doesn't work, try the US cable TV setup below.
If you're getting your broadcast off the air, you can run the scantv utility to detect stations and set $channel to the local channel for your area.

US cable:
mplayer tv://"insert channel" -tv driver=v4l2:device=/dev/video0:chanlist=us-cable:alsa:\
adevice=hw.1,0:amode=1:audiorate=32000:forceaudio:volume=100:immediatemode=0:norm=NTSC

Here again you can run the scantv utility to detect the channels available from your provider, or you can use your provider's channel table.

Europe cable:
mplayer tv://"insert channel" -tv driver=v4l2:device=/dev/video0:chanlist=europe-west:alsa:\
adevice=hw.1,0:amode=1:audiorate=32000:forceaudio:volume=100:immediatemode=0:norm=PAL

Note the ''norm='' and ''chanlist='' parameters. Adjust as required for your location.

If "adevice=hw.1,0" doesn't work, try simply "adevice=hw.1". Some tuners require "adevice=hw.2" -- for instance, on a board with nforce 3 250/gb chipsets. If others experiance this with other boards, please update.

=== Record with mencoder ===

It may be simpler to get sound during recording than during playback. The example given below, in which "$DEV" is the number of the device node is known to produce good sound:

mencoder -tv driver=v4l2:device=/dev/video$DEV:fps=30000/1001:chanlist=us-bcast:\
audiorate=32000:alsa:adevice=hw.$DEV:input=0:amode=1:normid=4:width=576:height=432 \
-ovc x264 -x264encopts threads=2:bitrate=500:bframes=2:subq=1:me=1:frameref=4:8x8dct \
-oac mp3lame -lameopts cbr:br=64 -endpos $TIM -o $DIR/$FIL.avi tv:// > /dev/null

So the alsa device is simply called hw.1 -- not hw.1,0. The line is taken from the [[V4L channel script]]. You may find you need to use hw.2 instead, depending on the audio hardware on your system.

Neither ffmpeg nor transcode as yet have ALSA support.

Because so many applications still appear to have difficulties accessing ALSA's odd device enumeration, the OSS module for DMA sound continues to be useful. You can also use ALSA's OSS emulation with saa7134-alsa to get /dev/dspX devices for OSS-aware applications.

=== Using with Mplayer, Mencoder with Gentoo default Pulseaudio and Alsa config ===

If you are using default SAA7134 Pulseaudio settings (Analog Stero Input with the video channel being captured), then you can try command line for composite signal capture:
mplayer -tv driver=v4l2:device=/dev/video1:audiorate=32000:alsa:adevice=hw.1:immediatemode=0:input=1:amode=1:normid=7:width=720:height=576 -ao alsa -aspect 16:9 tv://
Note: the line above may work in place of trying with arecord and aplay, as per the example below (arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | aplay -), which may not work as well as expected.

For Mencoder, the following command line can be used:
mencoder -tv driver=v4l2:device=/dev/video1:audiorate=32000:alsa:adevice=hw.1:input=1:amode=1:normid=7:width=720:height=576 -o filename.mpg -ovc lavc -oac copy -lavcopts vcodec=mpeg2video:vbitrate=1000:\
keyint=5:aspect=16/9 -vf harddup -endpos 00:00:00 tv://
This line has been successfully tested, recording a good few gigabytes, from a Virginmedia V+HD box.

These lines were created with the help of this very page and the Mplayer/Mencoder manual.

=== ALSA audio with other applications ===

To hear the audio through ALSA using tvtime (or other programs that don't support it directly), run the following command after starting tvtime:

arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | aplay -

It basically records at 32kHz Stereo from the SAA7134 ALSA source (hw:1,0 or change accordingly), and plays it through your default ALSA output. Look at the options from aplay to change your output.

There might be a delay between the video and the audio. To avoid it, specify a device for aplay (not the 'default' device):

arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | aplay -D surround41

In order to get full surround sound from the stereo TV audio output, edit your /etc/asound.conf or ~/.asoundrc file as described in ALSA FAQ028 (http://alsa.opensrc.org/FAQ028) and use this device:

arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | aplay -D ch51dup

I don't know how to use ALSA directly with xawtv, motv, kdtv, tvtime, or zapping; if you do, please add it in here!

If using arecord still causes a delay between the video and the audio, try using sox:

sox -r 32000 -w -t alsa hw:1,0 -t alsa hw:0,0

Recent versions of sox no longer accept "-w" option, so just omit it. You can also use "--buffer" option to improve A/V synchronization, as the default 8KB buffer causes audio to lag significantly. On my system 2KB buffer is optimal:

sox --buffer 2048 -r 32000 -t alsa hw:1,0 -t alsa hw:0,0

Sox might get you mono sound, while all the alsa solutions cause delays. A combination has been known to work:

arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | sox -q -c 2 -r 32000 -w -t wav - -t alsa hw:0,0

If sox doesn't have alsa support, you can try this instead:

arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | play -q -c 2 -r 32000 -w -t wav -

Alternatively you can use alsa's oss-emulation with sox, which seems to result in way better latency then all the above:

sox -q -c 2 -s -w -r 32000 -t ossdsp /dev/dsp1 -t ossdsp -w -r 32000 /dev/dsp

=== Howto use Saa7134-alsa with Pulseaudio based-system ===

==== Redirect the sound with pulseaudio loopback module ====
* If your Saa713x device is properly configured and still can get no sound with TVTime, you may to redirect the input source from your TV card to the output of your sound card. You must load the [http://pulseaudio.org/wiki/Modules#module-loopback loopback module] with the command:
$ pactl load-module module-loopback
It will redirect the default input to the default output. The default input may not be the right one, you can change it in the 'Recording' tab with 'All Streams' displayed with Pulseaudio Volume Control (pavucontrol)
[[File:Pavucontrol.png|thumb|400px|center|alt=Example of loopback module selection in Pulseaudio Volume Control|Example of loopback module selection in Pulseaudio Volume Control]]

* The sound should now works. To automate the process, we will edit /etc/pulse/default.pa

First we need to now what is the TV card source name in pulseaudio. You can know the PCI address of your card with
$ lspci | grep SAA
It will output something like that :
04:08.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1)
'''04:08.0''' is the ''address'' of your card.

* Then, the following command
$ LANG=C pactl list | grep -A2 'Source #' | grep 'Name: ' | cut -d" " -f 2
will list all source detected by Pulseaudio.

For example, on my computer:
alsa_input.pci-0000_04_08.0.analog-stereo
alsa_output.pci-0000_00_10.1.analog-stereo.monitor
alsa_input.pci-0000_00_10.1.analog-stereo

The source name to use is '''the one with the right PCI address'''. Here the third one: alsa_input.pci-0000_'''04_08.0'''.analog-stereo

* Edit the file /etc/pulse/default.pa with your favorite text editor:
# gedit /etc/pulse/default.pa
Add the following line at the end of the file (replacing source with the one you found):
load-module module-loopback source=alsa_input.pci-0000_04_08.0.analog-stereo

* Restart Pulseaudio
$ pulseaudio -k

=== Sound distorted and high-pitched ===

* On some card, the sound is distorted, high-pitched as if it is accelerated. Some program will output buffer underrun in the terminal. Fixed for newer kernel: http://git.alsa-project.org/?p=alsa-kernel.git;a=commit;h=7b54360293c9d72b54e462d146c9376287d2f71b
* To correct this problem we need to change the autodetected sampling rate of the TV card from to 32000Hz.
* First we search for the current card parameters. Type :
$ pactl list | grep device_id
It will output sound card argument detected by udev :
Argument: device_id="2" name="pci-0000_'''04_08.0'''" card_name="alsa_card.pci-0000_04_08.0" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1"
Argument: device_id="0" name="pci-0000_00_10.1" card_name="alsa_card.pci-0000_00_10.1" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1"

As previously explained we will need arguments from the card with the right PCI address (here, the first line).

* Edit the file /etc/pulse/default.pa with your favorite text editor:
# gedit /etc/pulse/default.pa

* Before the line
### Automatically load driver modules depending on the hardware available
add the following
load-module module-alsa-card rate=32000 format=s16le $argument
where $argument is the line previously found without the last argument card_properties="module-udev-detect.discovered=1"

For example,
load-module module-alsa-card rate=32000 format=s16le device_id="2" name="pci-0000_04_08.0" card_name="alsa_card.pci-0000_04_08.0" tsched=yes ignore_dB=no

* Restart Pulseaudio
$ pulseaudio -k
[[Category:Drivers]]
[[Category:Software]]

Saa7134-alsa

2013-01-04T01:28:42Z

CityK: /* Record with mencoder */ remove first persno

Also see the [[Saa7134-alsa redundant]] article; whose info (if it is not redundant) should/will be merged (preferably by its authour so that proper user attribution is maintained for information additions) into this original existing article.

=== How to use alsa or oss with saa7134 ===

Starting with kernel 2.6.15, the module saa7134-alsa lets you use ALSA to get sound directly from your capture card. From 2.6.16 you can use this module with more than one capture card.

In kernel 2.6.16, the saa7134-oss module is also separated out, and the two modules are treated in much the same way; you can build both and switch between them, though both cannot be loaded at once.

=== Insmod parameters ===

Now that both alsa and oss DMA sound have been separated out as distinct modules, it is no longer necessary (though it is not forbidden) to include the insmod parameter "alsa=1" or "oss=1".

On the other hand, on the 2.6.16 kernel, it's not safe to use the parameter "disable_ir=1" to turn off the infrared system for the remote -- that caused an oops. This is fixed in 2.6.17.

In the case of more than one card, you can use something like this:

saa7134 card=2,2,2,2 tuner=43,43,43,43 video_nr=1,2,3,4 vbi_nr=1,2,3,4 radio_nr=1,2,3,4

In dmesg, you should see this type of content murmuring:

<pre>
input: saa7134 IR (LifeView FlyVIDEO30 as /class/input/input5
tuner 5-0061: chip found @ 0xc2 (saa7133[3])
tuner 5-0061: type set to 43 (Philips NTSC MK3 (FM1236MK3 or FM1236/F))
tuner 5-0063: chip found @ 0xc6 (saa7133[3])
saa7133[3]: i2c eeprom 00: 69 51 38 01 10 28 ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7133[3]: registered device video4 [v4l2]
saa7133[3]: registered device vbi4
saa7133[3]: registered device radio4
</pre>

To then load the new driver that lets you get sound off the PCI bus via ALSA or OSS, you would normally just issue "sudo modprobe saa7134-alsa" or "sudo modprobe saa7134-oss". You can also deliberately assign the enumeration; for instance, for four cards, do this for alsa:

sudo modprobe saa7134-alsa index=1,2,3,4

Again, dmesg approves:

<pre>
saa7134 ALSA driver for DMA sound loaded
saa7133[0]/alsa: saa7133[0] at 0xf5006000 irq 19 registered as card 1
saa7133[1]/alsa: saa7133[1] at 0xf5007000 irq 20 registered as card 2
saa7133[2]/alsa: saa7133[2] at 0xf5004000 irq 21 registered as card 3
saa7133[3]/alsa: saa7133[3] at 0xf5005000 irq 22 registered as card 4
</pre>

If instead you use OSS, issue this to determine enumeration:

sudo modprobe saa7134-oss dsp_nr=1,2,3,4 mixer_nr=1,2,3,4

You should see this in dmesg:

<pre>
saa7134 OSS driver for DMA sound loaded
saa7133[0]: registered device dsp1
saa7133[0]: registered device mixer1
saa7133[1]: registered device dsp2
saa7133[1]: registered device mixer2
saa7133[2]: registered device dsp3
saa7133[2]: registered device mixer3
saa7133[3]: registered device dsp4
saa7133[3]: registered device mixer4
</pre>

Note that if you use saa7134-oss in Debian, and build your kernel with ALSA as modules, you may need to add saa7134 to the OSS-module-list to keep your OSS emulation under ALSA (cf. [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=359851 #359851]):

echo saa7134 >> /usr/share/linux-sound-base/OSS-module-list

If OSS emulation is not working, some applications (such as VLC) that expect ALSA sound devices won't be able to find the legacy OSS devices created by saa7134-oss.

If your ALSA is built into the kernel rather than as modules, you won't need to worry about this.

===Insert modules on boot===

To insert the modules with these parameters on boot, you can create a file called /etc/modprobe.d/saa7134 with the following lines (adjust card and tuner numbers as required):

options saa7134 card=2,2,2,2 tuner=43,43,43,43 video_nr=1,2,3,4 vbi_nr=1,2,3,4 radio_nr=1,2,3,4
install saa7134 /sbin/modprobe --ignore-install saa7134; /sbin/modprobe saa7134-alsa
options saa7134-alsa index=1,2,3,4

Your distribution may require you to put these lines into /etc/modprobe.conf; this is not a good idea in Debian, since the files in /etc/modprobe.d will then be ignored.

If instead you use OSS, these lines will load the modules for four cards:

options saa7134 card=2,2,2,2 tuner=43,43,43,43 video_nr=1,2,3,4 vbi_nr=1,2,3,4 radio_nr=1,2,3,4
install saa7134 /sbin/modprobe --ignore-install saa7134; /sbin/modprobe saa7134-oss
options saa7134-oss dsp_nr=1,2,3,4 mixer_nr=1,2,3,4

Note that once you've entered this information inside /etc/modprobe.d, your subsequent manual insertions will also make use of this information. Scripts, for instance, need not repeat it.

These instructions are of course specific to kernels 2.6.16 and later, as earlier kernels do not have separate DMA modules.

For kernels before 2.6.16, DMA sound via OSS is activated simply by the insmod parameter "oss=1".

=== Set permissions ===

Make sure your users are added to the group "audio" to get access to them -- in Debian, if your user name is "tv", you would use

adduser tv audio

=== List your capture devices ===

To get a list of your alsa capture devices, issue

arecord -l

You should see your regular sound card and the capture card(s):

<pre>
**** List of CAPTURE Hardware Devices ****
card 0: CK8S [NVidia CK8S], device 0: Intel ICH [NVidia CK8S]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CK8S [NVidia CK8S], device 1: Intel ICH - MIC ADC [NVidia CK8S - MIC ADC]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: SAA7134 [SAA7134], device 0: SAA7134 PCM [SAA7134 PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: SAA7134_1 [SAA7134], device 0: SAA7134 PCM [SAA7134 PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 3: SAA7134_2 [SAA7134], device 0: SAA7134 PCM [SAA7134 PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 4: SAA7134_3 [SAA7134], device 0: SAA7134 PCM [SAA7134 PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0
</pre>

=== Configure the cards to record ===

Set the cards to record on channel 1 and max volume, using for instance

alsamixergui -c 1

for each of the cards.

=== Watch with mplayer ===

You should now be ready to watch live tv with mplayer, using something like this:

These are for rf connections:

US broadcast or satellite:
mplayer tv://$channel -tv driver=v4l2:device=/dev/video0:chanlist=us-bcast:alsa:\
adevice=hw.1,0:amode=1:audiorate=32000:forceaudio:volume=100:immediatemode=0:norm=NTSC

If you're using a satellite box, $channel should probably be set to 3 or 4. If that doesn't work, try the US cable TV setup below.
If you're getting your broadcast off the air, you can run the scantv utility to detect stations and set $channel to the local channel for your area.

US cable:
mplayer tv://"insert channel" -tv driver=v4l2:device=/dev/video0:chanlist=us-cable:alsa:\
adevice=hw.1,0:amode=1:audiorate=32000:forceaudio:volume=100:immediatemode=0:norm=NTSC

Here again you can run the scantv utility to detect the channels available from your provider, or you can use your provider's channel table.

Europe cable:
mplayer tv://"insert channel" -tv driver=v4l2:device=/dev/video0:chanlist=europe-west:alsa:\
adevice=hw.1,0:amode=1:audiorate=32000:forceaudio:volume=100:immediatemode=0:norm=PAL

Note the ''norm='' and ''chanlist='' parameters. Adjust as required for your location.

If "adevice=hw.1,0" doesn't work, try simply "adevice=hw.1". Some tuners require "adevice=hw.2" -- for instance, on a board with nforce 3 250/gb chipsets. If others experiance this with other boards, please update.

=== Record with mencoder ===

It may be simpler to get sound during recording than during playback. The example given below, in which "$DEV" is the number of the device node is known to produce good sound:

mencoder -tv driver=v4l2:device=/dev/video$DEV:fps=30000/1001:chanlist=us-bcast:\
audiorate=32000:alsa:adevice=hw.$DEV:input=0:amode=1:normid=4:width=576:height=432 \
-ovc x264 -x264encopts threads=2:bitrate=500:bframes=2:subq=1:me=1:frameref=4:8x8dct \
-oac mp3lame -lameopts cbr:br=64 -endpos $TIM -o $DIR/$FIL.avi tv:// > /dev/null

So the alsa device is simply called hw.1 -- not hw.1,0. The line is taken from the [[V4L channel script]]. You may find you need to use hw.2 instead, depending on the audio hardware on your system.

Neither ffmpeg nor transcode as yet have ALSA support.

Because so many applications still appear to have difficulties accessing ALSA's odd device enumeration, the OSS module for DMA sound continues to be useful. You can also use ALSA's OSS emulation with saa7134-alsa to get /dev/dspX devices for OSS-aware applications.

=== Using with Mplayer, Mencoder with Gentoo default Pulseaudio and Alsa config ===

If you are using default SAA7134 Pulseaudio settings (Analog Stero Input with the video channel being captured) as I do, this is my line (Note, these lines are for composite capture) :
mplayer -tv driver=v4l2:device=/dev/video1:audiorate=32000:alsa:adevice=hw.1:immediatemode=0:input=1:amode=1:normid=7:width=720:height=576 -ao alsa -aspect 16:9 tv://
Note, Before figuring out this line above, I had previously tried arecord and aplay as per the example below (arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | aplay -) and that didn't work as well as I had expected.

For Mencoder I use this line:
mencoder -tv driver=v4l2:device=/dev/video1:audiorate=32000:alsa:adevice=hw.1:input=1:amode=1:normid=7:width=720:height=576 -o filename.mpg -ovc lavc -oac copy -lavcopts vcodec=mpeg2video:vbitrate=1000:\
keyint=5:aspect=16/9 -vf harddup -endpos 00:00:00 tv://
I have recorded a good few gigabytes with this line from my Virginmedia V+HD box

These lines were created with the help of this very page and the Mplayer/Mencoder manual.

=== ALSA audio with other applications ===

To hear the audio through ALSA using tvtime (or other programs that don't support it directly), run the following command after starting tvtime:

arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | aplay -

It basically records at 32kHz Stereo from the SAA7134 ALSA source (hw:1,0 or change accordingly), and plays it through your default ALSA output. Look at the options from aplay to change your output.

There might be a delay between the video and the audio. To avoid it, specify a device for aplay (not the 'default' device):

arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | aplay -D surround41

In order to get full surround sound from the stereo TV audio output, edit your /etc/asound.conf or ~/.asoundrc file as described in ALSA FAQ028 (http://alsa.opensrc.org/FAQ028) and use this device:

arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | aplay -D ch51dup

I don't know how to use ALSA directly with xawtv, motv, kdtv, tvtime, or zapping; if you do, please add it in here!

If using arecord still causes a delay between the video and the audio, try using sox:

sox -r 32000 -w -t alsa hw:1,0 -t alsa hw:0,0

Recent versions of sox no longer accept "-w" option, so just omit it. You can also use "--buffer" option to improve A/V synchronization, as the default 8KB buffer causes audio to lag significantly. On my system 2KB buffer is optimal:

sox --buffer 2048 -r 32000 -t alsa hw:1,0 -t alsa hw:0,0

Sox might get you mono sound, while all the alsa solutions cause delays. A combination has been known to work:

arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | sox -q -c 2 -r 32000 -w -t wav - -t alsa hw:0,0

If sox doesn't have alsa support, you can try this instead:

arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | play -q -c 2 -r 32000 -w -t wav -

Alternatively you can use alsa's oss-emulation with sox, which seems to result in way better latency then all the above:

sox -q -c 2 -s -w -r 32000 -t ossdsp /dev/dsp1 -t ossdsp -w -r 32000 /dev/dsp

=== Howto use Saa7134-alsa with Pulseaudio based-system ===

==== Redirect the sound with pulseaudio loopback module ====
* If your Saa713x device is properly configured and still can get no sound with TVTime, you may to redirect the input source from your TV card to the output of your sound card. You must load the [http://pulseaudio.org/wiki/Modules#module-loopback loopback module] with the command:
$ pactl load-module module-loopback
It will redirect the default input to the default output. The default input may not be the right one, you can change it in the 'Recording' tab with 'All Streams' displayed with Pulseaudio Volume Control (pavucontrol)
[[File:Pavucontrol.png|thumb|400px|center|alt=Example of loopback module selection in Pulseaudio Volume Control|Example of loopback module selection in Pulseaudio Volume Control]]

* The sound should now works. To automate the process, we will edit /etc/pulse/default.pa

First we need to now what is the TV card source name in pulseaudio. You can know the PCI address of your card with
$ lspci | grep SAA
It will output something like that :
04:08.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1)
'''04:08.0''' is the ''address'' of your card.

* Then, the following command
$ LANG=C pactl list | grep -A2 'Source #' | grep 'Name: ' | cut -d" " -f 2
will list all source detected by Pulseaudio.

For example, on my computer:
alsa_input.pci-0000_04_08.0.analog-stereo
alsa_output.pci-0000_00_10.1.analog-stereo.monitor
alsa_input.pci-0000_00_10.1.analog-stereo

The source name to use is '''the one with the right PCI address'''. Here the third one: alsa_input.pci-0000_'''04_08.0'''.analog-stereo

* Edit the file /etc/pulse/default.pa with your favorite text editor:
# gedit /etc/pulse/default.pa
Add the following line at the end of the file (replacing source with the one you found):
load-module module-loopback source=alsa_input.pci-0000_04_08.0.analog-stereo

* Restart Pulseaudio
$ pulseaudio -k

=== Sound distorted and high-pitched ===

* On some card, the sound is distorted, high-pitched as if it is accelerated. Some program will output buffer underrun in the terminal. Fixed for newer kernel: http://git.alsa-project.org/?p=alsa-kernel.git;a=commit;h=7b54360293c9d72b54e462d146c9376287d2f71b
* To correct this problem we need to change the autodetected sampling rate of the TV card from to 32000Hz.
* First we search for the current card parameters. Type :
$ pactl list | grep device_id
It will output sound card argument detected by udev :
Argument: device_id="2" name="pci-0000_'''04_08.0'''" card_name="alsa_card.pci-0000_04_08.0" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1"
Argument: device_id="0" name="pci-0000_00_10.1" card_name="alsa_card.pci-0000_00_10.1" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1"

As previously explained we will need arguments from the card with the right PCI address (here, the first line).

* Edit the file /etc/pulse/default.pa with your favorite text editor:
# gedit /etc/pulse/default.pa

* Before the line
### Automatically load driver modules depending on the hardware available
add the following
load-module module-alsa-card rate=32000 format=s16le $argument
where $argument is the line previously found without the last argument card_properties="module-udev-detect.discovered=1"

For example,
load-module module-alsa-card rate=32000 format=s16le device_id="2" name="pci-0000_04_08.0" card_name="alsa_card.pci-0000_04_08.0" tsched=yes ignore_dB=no

* Restart Pulseaudio
$ pulseaudio -k
[[Category:Drivers]]
[[Category:Software]]

MSI TV@nywhere E-Duo

2013-01-04T01:18:44Z

CityK: moved TV@nywhere E-Duo to MSI TV@nywhere E-Duo: name

[[Image:msi_tvanywhere_e_duo.jpg|250px|thumb|right|MSI TV@nywhere E-Duo Card]]
A dual tuner [[DVB-T]] [[DVB-T PCIe Cards|PCIe card]] from [[MSI]].
It is currently not supported under Linux.

==Overview/Features==

* Dual tuner DVB-T
* PCI-E 1x interface

==Components Used==
* [[NXP SAA716x|NXP SAA7160ET]] [[PCIe interface chipsets|PCIe interface chipset]]
* 2x [[NXP TDA10048|NXP TDA10048HN]] DVB-T demodulators
* 2x [[NXP/Philips TDA182xx|NXP TDA18211HDC1]] silicon tuner ICs

==External links==
* [http://global.msi.eu/index.php?func=proddesc&maincat_no=132&prod_no=1432# MSI TV@nywhere E-DUO product page]
* [https://picasaweb.google.com/lh/photo/_NqoKWlTKBe54Lj1O72Z2pxPPKVTixhzqWw3fwrCO3U?feat=directlink MSI TV@nywhere E-DUO tuner chip under shield]

Saa7162 devices

2013-01-04T01:18:03Z

CityK: /* Examples of saa7160 Based Cards */ added link

Saa7162 devices are collectively those PCIe devices that are based upon either a [[NXP SAA716x|SAA7160, SAA7161 or SAA7162]] chip, and which will be supported under Linux by the [[NXP SAA716x#Driver Development|SAA716x kernel driver module]].

==Supported Cards==
There are currently no supported cards. (Check here for current status of [[NXP SAA716x#Driver Development|driver development]]).

==Examples of saa7160 Based Cards==
===AVerMedia AVerTV Speedy Hybrid PCI-E===
* [[AVerMedia AVerTV Speedy Hybrid PCI-E]] Its a combo card Analog + DVB-T
===Kworld pe355-2T PCI-E Dual DVB-T TV Card Pro===
* [[Kworld pe355-2T PCI-E Dual DVB-T TV Card Pro]] is a dual DVB-T card.

* [[MSI]] [[MSI TV@nywhere E-Duo|TV@nywhere E-Duo]]

==Examples of saa7162 Based Cards==

===Blackgold TV BGT3540===

A "6 in 1" PCI express card, dual digital satellite, dual digital terrestrial, dual analogue terrestrial. Dual F connectors for two DVB-S sources, one Belling-Lee connector for terrestrial.

[[Image:BGT3540.png|Blackgold BGT3540]]

See [http://shop.blackgold.tv/epages/BT3159.sf/en_GB/?ObjectPath=/Shops/BT3159/Products/BGT3540 product page] and [http://shop.blackgold.tv/pages.php?pageid=15 specifications].

===DNTV PCI Express cards===

* [[DNTV Live! Dual Hybrid PCI Express]] (a rebadge of the FlyTV Express X1 MST-T2A2EX, see below)
* [[DNTV Live! QuattroS PCI Express]]

See [http://marc.info/?l=linux-video&m=115718592220235&w=2 v4l discussion].

===KWorld PCI Express Hybrid===

An early example of a card that uses the saa7162 decoder chip is this hybrid card, which also supports Intel's serial digital video out (SDVO):

[[Image:KWorld-PCIe.png|KWorld PCI Express Hybrid]]

See [http://www.kworldcomputer.com/product/pci-e/002/PCI_E_Hybird.htm product page].

(Someone needs to tell them it's hybrid, not hybird!)

===LifeView Express cards===

* [[LifeView FlyTV Express X1]]

===Philips PCV290===

Dual DVB-T and Dual DVB-S
[http://www.nxp.com/applications/pc_pda/pc_tv/pcv290/index.html Reference Design]

Uses 2xTDA8263 DVB-S Tuner, 1 x TDA10093 Dual Channel DVB-S channel decoder, 2xTDA8275A DVB-T Tuner, 2xTDA10046A DVB-T channel decoder, 1xSAA7162E TV video/audio decoder/PCI express interface)

===Pinnacle PCTV Dual Hybrid Pro===
Tuner cards from Pinnacle with PCI Express x1. [http://support.packardbell.com/de/item/index.php?i=tv013a&ppn=PB34313803 PackardBell] have some windows drivers for them.

''Pinnacle PCTV Dual Analog + DVB-T + DVB-S'', [[Pinnacle_PCTV_7010iX]]: Two FM, DVB-T, analog TV, and two DVB-S recievers. Chips used: Philips SAA7162, Philips TDA8275A, Zarlink ZL10313 (for DVB-S).

''Pinnacle PCTV Dual Hybrid Pro PCI-e'', [[Pinnacle_PCTV_3010iX]]: Low profile card, Two FM, DVB-T, analog TV recievers. Chips used: Philips SAA7162, Philips TDA8275A.

[[Image:Pinnacles-1sm.jpg|Photos of new PCI Express Pinnacle cards]]

===ViXS Diamond Reference Design===
In August 2005, ViXS Systems announced the Diamond PCI Express TV tuner reference design. The design provides for analog and hybrid (analog/digital) video processing, combining ViXS' XCode II-L Dual MPEG Encoder with Philips' SAA7162 Dual Video Decoder and Philips' TV tuner ([http://www.vixs.com/sub_sections/news_events/press/press_ViXS_Philips.html press release]).

==Examples of saa7160e Based Cards==

===Creatix CTX975===

PCIe DVB-T receiver in a 34 mm Express Card design.

See [http://www.creatix.de/produkte/multimedia/ctx975.htm product page] and [http://www.creatix.de/produkte/multimedia/datenblatt/CTX975%20V1%20NewCard.pdf specifications].
[[Category:Drivers]]
[[Category:Hardware]]

DVB-T PCIe Cards

2013-01-04T01:16:48Z

CityK: fixed link

On this page you will find information regarding [[DVB-T]] [[PCIe]] and [[PCIe Mini Card]] devices.

{{non-exhaustive list}}
 
__TOC__
 
== DVB-T PCIe Cards ==

=== Supported DVB-T PCIe Cards: ===

* [[Hauppauge]] [[Hauppauge WinTV-HVR-1200|WinTV-HVR-1200]] [[#fn_1|1]]
* [[Hauppauge]] [[Hauppauge WinTV-HVR-1700|WinTV-HVR-1700]] [[#fn_1|1,]] [[#fn_2|2]]
* [[TerraTec]] [[TerraTec Cinergy 2400i DVB-T|Cinergy 2400i DVB-T]]: Works with a patch for the [[NGene_devices|NGene]]-driver.
* [[Hauppauge]] [[Hauppauge_WinTV-HVR-2200|WinTV-HVR-2200]] [[#fn_1|1]] Needs binary blob firmware and drivers from linuxtv.org git tree (not in mainline kernel yet)
* [[TerraTec]] [[TerraTec Cinergy T PCIe dual|Cinergy T PCIe dual]]
<cite id="fn_1">[[#fn_1_back|Note 1:]] </cite> Support is currently limited to digital TV mode only. Analog support (both analog TV & A/V input) will be added to the CX23885/7 driver soon; which will enable preview analog video support. 
<cite id="fn_2">[[#fn_2_back|Note 2:]] </cite>Hauppauge's analog mpeg encoder support is also contingent upon further development of the driver for the CX23417 encoder.

==== Experimental Support: ====
* [[DViCO]] [[DViCO FusionHDTV DVB-T Dual Express|FusionHDTV DVB-T Dual Express]]
* [[Leadtek]] [[Leadtek WinFast PxDVR3200 H|WinFast PxDVR3200 H]]

* [[NetUP Dual DVB T C CI RF|NetUP_Dual_DVB_T_C_CI_RF]]
* [[Digital Devices DuoFlex C&T]]

=== Unsupported DVB-T PCIe Cards: ===
{{help to support}}

* [[Compro Technology|Compro]] [[Compro VideoMate E650|VideoMate E650]]
* [[Compro Technology|Compro]] [[Compro VideoMate E700|VideoMate E700]]
* [[Compro Technology|Compro]] [[Compro VideoMate E800|VideoMate E800]]
* [[Compro Technology|Compro]] [[Compro VideoMate E900/E850F|Videomate E900/E850F]]
* [[DViCO]] [[DViCO FusionHDTV DVB-T Dual Express|FusionHDTV DVB-T Dual Express]]
* [[DViCO]] [[DViCO FusionHDTV DVB-T Dual Express2|FusionHDTV DVB-T Dual Express2]]
* [[KWorld]] KWorld PlusTV Dual Hybrid PCIExpress (VS-DVBT PE310RF)
* [[Kworld pe355-2T PCI-E Dual DVB-T TV Card Pro]]
* [[Pinnacle]] [[Pinnacle PCTV Dual Hybrid Pro PCI Express (3010i)|PCTV Dual Hybrid Pro PCI Express (3010i)]]
* [[Pinnacle]] [[Pinnacle PCTV 7010iX|PCTV 7010iX]]
* [[Blackgold]] [[Blackgold BGT3540|BGT3540]]
* [[X3M Digital]] [[X3M Digital HPCe2100|HPCe2100]]
* [[MSI]] [[MSI TV@nywhere E-Duo|TV@nywhere E-Duo]]

== DVB-T PCIe Mini Cards ==

=== Supported DVB-T PCIe Mini Cards ===
* [[LifeView]] LR534 ... information is currently contained [http://www.linuxtv.org/v4lwiki/index.php/LifeView/TVWalkerTwin#LifeView_LR534_mini-PCIe_card here] (link will be changing soon)
* [http://www.pro-nets.com/eng/product.php?mode=show&cid=109&pid=143 PRO-NETS DM100A]: works using the driver for the [[Afatech_AF9015]] chip from http://linuxtv.org
* [[Sundtek]] MediaTV Pro (MiniPCIe), AnalogTV, FM Radio, DVB-T, DVB-C Hybrid MiniPCIe device. Supported by the manufacturer.

=== Unsupported DVB-T PCIe Mini Cards: ===
{{help to support}}

* LifeView LR535
* Lite-On TVT-1060
* [[AVerMedia A373 MiniCard Dual DVB-T]]

[[Category:PCIe| ]]
[[Category:DVB-T| ]]
[[Category:DVB-T PCIe Cards| ]]

Saa713x devices

2013-01-04T01:06:40Z

CityK: Reverted edits by DLX (talk) to last revision by Wirbel

saa713x devices are collectively those PCI cards that are based upon one of the [[Philips SAA7134|SAA713x]] chips, and which are supported under Linux by the saa7134 and associated kernel driver modules.

==saa7134 and associated kernel driver modules==
TV cards based on the saa713x chips are well supported by the saa7134 driver. The picture quality is typically high, and the sound can be taken directly from the TV card or through a patch cable to your sound card. On the [[text_capture | text capture]] front, both teletext and NTSC closed captioning are supported.

===Sound support===
Support for DMA sound, or sound taken directly off the PCI bus, has improved in the 2.6.16 kernel, thanks to the work of Ricardo Cerqueira and others. There are now two separate drivers for DMA sound, saa7134-alsa and saa7134-oss. In order to enable these in the kernel, you must first have selected support for ALSA and/or OSS under Sound. If you build both DMA devices as modules, you can use both alternately, though they cannot both be loaded at the same time.

While the saa7134-oss is listed as deprecated, there are still programs that have difficulties using ALSA's device enumeration, and the oss module remains useful.

These modules do not require parameters during insertion. For details and sound problems see [[saa7134-alsa]].

==Supported saa713x devices==
An up-to-date list of saa713x devices supported by V4L-DVB drivers is found in the [http://linuxtv.org/hg/v4l-dvb/file/tip/linux/Documentation/video4linux/CARDLIST.saa7134 CARDLIST.saa7134] file in the master development repository.

Devices supported by the kernel running on your system are listed in your local <code><path_to_your_kernel_sources>/Documentation/video4linux/CARDLIST.saa7134</code>. If you don't find your device listed here, but support for it is cited in the up-to-date sources (see above), then you will need to either upgrade to a more recent kernel that has already absorbed support for the device or, more simply, just get the latest V4L-DVB drivers. You can install the V4L-DVB modules on top of your existing kernel (see: [[How to Obtain, Build and Install V4L-DVB Device Drivers|detailed instructions]]), however, note that support for some devices may also require use of a newer kernel.

===Getting an unlisted card to work===
If your card is not listed, see the "[[Development: How to add support for a device|How to add support for a device]]" article.
----
this part needs to be edited:
* ask for assistance on the [https://listman.redhat.com/mailman/listinfo/video4linux-list v4l mailing list]
* [http://marc.theaimsgroup.com/?l=linux-video searchable archives].
* It may be a clone of a listed card ... card= entries may work for several similar cards.
* Full card names can be cross-referenced from drivers/media/video/saa7134/saa7134-cards.c.

Before buying a new TV card, it's always worth checking its support status on V4L documentation. However, be advised that, since some producers label with the same product name boards that, inside, are actually different, there is always some risk of buying an un- (or non-completely) supported card even if it appears to be. Spending some more time searching newsgroups and mailing lists for complaints is recommended.

Make sure you post the findings of your investigations here and on the video4linux mailing list (video4linux-list@redhat.com) so that saa7134-cards.c can be updated with a new card= entry for your card.

==Installation notes==
See [[Saa713x devices: Generic SAA7134 Card Installation]] for how to properly setup your saa7134-based tv tuner card or use the installation instructions for your specific card:

=== [[ASUS]] ===
* [[ASUS P7131 Dual]]
* [[ASUS My Cinema-P7131 Hybrid|ASUS P7131 Hybrid]]
* [[ASUS TV-FM 7133]]
* [[ASUS TV-FM 7135]]
* [[ASUSTeK P7131 Dual]]
* [[ASUS Digimatrix TV]]
* [[Asus Europa2 OEM]]
* [[ASUS P7131 4871]]
* [[ASUSTeK P7131 Analog]]
* [[Asus Tiger 3in1]]
* [[Asus Tiger Rev:1.00]]

=== [[AVerMedia]] ===
As described in [[AVerMedia AVerTV_305/307_Linux_user_guide|AVerTV 305/307 Linux user guide (Russian language)]], the following cards are supported:
* AVerTV 305
* AVerTV Studio 305
* AVerTV 307
* AVerTV Studio 307
In addition, the following cards are known to work:
* [[AVerMedia Cardbus E500]]
* [[AVerMedia Cardbus Plus E501R |AVerMedia Cardbus Plus E501R (russian)]]
* [[AverMedia M156 / Medion 2819]]
* [[AVerMedia DVD EZMaker]]
* [[AVerMedia AVerTV GO 007]]
* [[AVerMedia AVerTV GO 007 FM]]
* [[AVerMedia AVerTVHD MCE A180]]
* [[AVerMedia AVerTV Hybrid+FM Cardbus (E506R)]]
* [[AVerMedia AVerTV Hybrid+FM PCI (A16D)]]
* [[AverMedia M103 (Hybrid) Mini PCI]]
*[[AverMedia M156]]
*[[AVerMedia DVD EZMaker]]
*[[AVerMedia AVerTVHD MCE A180]]
*[[AVerMedia A169 B]]
*[[AVerMedia A169 B1]]
*[[AVerMedia TV Hybrid A16A]]
*[[Avermedia AVerTV Studio 507]]
*[[Avermedia M102]]
*[[Avermedia Super 007]]
*[[Avermedia M115]]
*[[Avermedia DVB-S Pro A700]]
*[[Avermedia DVB-S Hybrid+FM A700]]
*[[AVerMedia MiniPCI DVB-T Hybrid M103]]
*[[Avermedia PCI pure analog (M135A)]]
*[[Avermedia AVerTV GO 007 FM Plus]]
*[[Avermedia AVerTV Studio 507UA]]

=== Bona ===
The brand is also refered to as Mentor. [http://www.bona.com.tw:8080/ Bona Website]
* [[Bona TV-PCI]]

=== Canopus ===
* [[Canopus KTVX-CB (aka ITACHU) CardBus|KTVX-CB (aka ITACHU) CardBus]]

=== Compro ===
* [[Compro Videomate T750]]
* [[Compro VideoMate T300]]
* [[Compro VideoMate DVB-T220]]
* [[Compro VideoMate T200a]]
* [[Compro VideoMate T200]]
* [[Compro VideoMate TV Gold-Plus]]
* [[Compro VideoMate TV PVR/FM]]
* [[Compro VideoMate TV Gold-Plus PAL]]
* [[Compro VideoMate S350]]
* [[Compro VideoMate TV Gold+II]]
* [[Compro VideoMate Vista M1F]]

=== Encore ===
* [[Encore USA ELNTV-FM]]
* [[Encore ENLTV]]
* [[Encore ENLTV-FM v5.3]]

=== Hercules ===
* [[Hercules Smart TV 3]]

=== KNC One (KNC1) ===
* [[KNC One TV-Station DVR]]
* [[KNC One TV-Station RDS]] / Typhoon TV Tuner RDS

=== KWorld ===
* [[KWorld ATSC 110|ATSC-110]]
* [[KWorld Studio TV Terminator|Studio TV Terminator]] (a.k.a. Global TV Terminator)
* [[KWorld NB-TV 100 CardBus|NB-TV 100 CardBus]]
* [[KWorld DVB-T 220|DVB-T 220]]
* [[Kworld/KuroutoShikou SAA7130-TVPCI]]
* [[Kworld/Tevion V-Stream Xpert TV PVR7134]]
* [[Kworld Xpert TV PVR7134]]
* [[KWorld DVB-T 210]]
* [[Kworld Plus TV Analog Lite PCI]]
* [[Kworld PCI Analog TV Card Lite]]

=== LifeView ===
* [[LifeView FlyVideo2000|FlyVideo2000]]
* [[LifeView FlyVideo3000FM NTSC|FlyVideo3000FM and FlyVideo3000]]
* [[LifeView FlyVideo3000 PAL-N|FlyVideo3000 PAL-N]]
* [[LifeView FlyDVB-T Hybrid|FlyDVB-T Hybrid]]
* [[LifeView FlyDVB-T Hybrid CardBus|FlyDVB-T Hybrid CardBus]]
* [[LifeView FlyDVB-T Duo CardBus|FlyDVB-T Duo CardBus]]
* [[LifeView FlyTV Platinum|FlyTV Platinum]]

=== MSI ===
* [[MSI TV@nywhere A/D NB|TV@nywhere A/D NB]]
* [[MSI TV@nywhere Duo]]
* [[MSI TV@Anywhere plus]]
* [[MSI TV@nywhere A/D v1.1]]

=== Mercury ===

* [[Mercury TV Tuner card PAL/Mecury EzView tuner card (Philips chipset)]]
* [[Mercury TV PAL]]

=== Pearl ===

* [[Auvisio TV Tuner & Video Capture Card]]

=== Pinnacle ===
* [[Pinnacle PCTV 40i]]
* [[Pinnacle PCTV 50i]]
* [[Pinnacle PCTV 110i]]
* [[Pinnacle PCTV 300i]]
* [[Pinnacle PCTV (310i)]]
* [[Pinnacle PCTV Stereo]]
* [[Pinnacle PCTV Stereo XE]]

=== Sabrent ===
* [[Sabrent SBT-TVFM]]
* [[Sabrent TV-PCIRC]]
* [[Sabrent PCMCIA TV-PCB05]]

=== TerraTec ===
* [[Terratec Cinergy 200 TV]]
* [[TerraTec Cinergy 250 PCI|Cinergy 250 PCI]]
* [[TerraTec Cinergy 400|Cinergy 400]]
* [[TerraTec Cinergy 400TV mobile|Cinergy 400TV mobile]]
* [[TerraTec Cinergy 600|Cinergy 600]]
* [[TerraTec Cinergy HT PCI|Cinergy HT PCI]]
* [[Terratec Cinergy HT PCMCIA]]
* [[TerraTec Cinergy HT Express]]

=== Tevion ===
* [[Tevion MD 9717]]
* [[Tevion DVBT-220RF]]
* [[Tevion V-Stream Xpert TV PVR7134]]

=== Vivanco ===
* [[Vivanco Cardbus DVB-T]]

=== Other ===
* [[Smartv_card |SmartTV Card]]
* [http://techcomindia.com/itemdetail.asp?Cat=&CatID=&prodid=501&ProdName=SSD%2DTV%2D670 TECH-COM, Card Model: SSD-TV-670 ]
* [[Zolid Hybrid TV Tuner|Zolid Hybrid TV Tuner]]

==External Links==
* [http://en.gentoo-wiki.com/wiki/Saa7134 Gentoo Wiki's saa7134 article]
[[Category:Hardware]]

Development: How to add support for a device

2012-10-08T17:56:00Z

CityK: /* Determining the Device's Identity */ update bttv-gallery section

This article is meant to serve as an introduction to the task of developing driver support for a device.

==Getting Started==
The very first thing you should do is find out how your device identifies itself:

'''For PCI/PCIe devices''' - use the command:
:<code>$ /sbin/lspci -vnn</code>

'''For USB based devices''' - use the command:
:<code>$ /sbin/lsusb -v</code>

The output generated from the above should provide you with the identify of the main bridge chip as well as the important piece of information known as the device's subsystem ID.

Next, you should try to identify the other component ICs/chips that your device uses. In regards to TV tuner devices, often the tuner chip and demodulator(s) are hidden within a metallic box connected directly to the antenna input. In such cases, this tuner module will usually have an identifying model name/type printed upon it's face, though it is also just as common for this to be obscured underneath a sticker that the device manufacturer has laid over top. With care, you can usually peel back the manufacturer's device sticker to discover the tuner module's own part identifier label or stamp.

Note: You can find a lot of useful device related information:
* here in the wiki
* in the [[Development:_How_to_add_support_for_a_device#bttv-gallery|bttv-gallery]]
* and by having a look at MS-Windows drivers (in particular, the .inf files), as they often contain a lot of particulars about a device's hardware components

== Case 1: Development steps for when your device uses components for which drivers already exist==
Extending support for your device under such circumstances can range from being a trivial matter to one which requires some patience and discovery through the process of trial & error.

First off, [[How to Obtain, Build and Install V4L-DVB Device Drivers|download the latest V4L-DVB source code from Git]] and search for a device that is similar to your own - something like your device may already be supported but with another name. In such a case, you can copy a similar entry and fill in the values for the new device. For example:
* for a bttv chip you add to bttv-cards.c and bttv.h,
* for cx88 chip - cx88-cards.c and cx88.h,
* for saa713x chip saa7134-cards.c and saa7134.h
... and so forth.

==== For TV tuner devices: Finding the correct tuner ====
In more than 90% of all cases something like.. first test one to your norm specific type with older Philips API, then test LG API and if there are still missing channels in UHF test MK3 API types will succeed. To find the exact takeover and radio config might be further steps, but most likely this can be/is covered by one of the existing types already.

At least it will usually take only three tuners to reach this point and if you find all three API types don't work, then ...

To check for the tda9887 on MK3 and mt32xx types can be done at once or as a next step. Since also the Philips silicon tuners should be well detected now, we can identify such like the yet unsupported Xceive types quite well. They seem to fail safely upon the initialization sequence with tuner=54 if I got Carsten right. So the really difficult/new ones should show up quickly enough and we can try to prepare a list of typical addresses for new devices like channel decoders, second eeproms, most likely hidden analog demodulators and such.

That the multi and hybrid types can have other issues too, like antenna input/filter/demodulator RF-amplifier switching and the like is above simple analog tuner programming and not yet fully investigated for all new types, but it seems there is some very good progress too.

The takeover suggestions in most datasheets on switch between VHF and UHF aren't related closely to technical specifications and precise measurements. They simply take it from _known_ channels currently in use and select those which are closest from both sides! Most obvious for NTSC-M tuners. If one is missing in the gap, to go right into the middle seems to be still reasonable for me as a next step in such cases, but to finally make the decision on what is empirically reported to work best is legal in lack of further documentation.

==== Guessing the .gpio values and masks for input ====
For some guidance on programming for these aspects, see:
* the programming section of the [[GPIO pins]] article and
* the [[Remote controllers-V4L|Remote controllers]] article. Note: before writing the patch please double-check that there are no such keys in V4L-DVB source code already.

==== Test your code====
If the device works - that's cool! Congratulations! You are now ready to [[Development: How to submit patches|send a patch to the mailing list]].

==Case 2: Development steps for when your device uses components for which drivers do not currently exist==

Unfortunately, development of a new chipset driver is generally not an easy task. For starters, you're going to have to be capable and/or ambitious enough to produce the code or, at the very least, inspire an existing developer to do such (and there is by no means any guarantee that anyone will be interested...even if you cry and beg and/or throw bags of money). Either way, you should first search and/or inquire on the mailing list as to whether or not someone is already undertaking such development.

If you're going to work on a driver for a chip you should try to find documentation for it online. In the end, you may require getting information directly from the manufacturer (in the case where no information can be found in the "wild" or those where publicly available information is incomplete or lacking).

* For general references on how to develop a Linux kernel driver module, take a look at the [http://jungla.dit.upm.es/%7Ejmseyas/linux/kernel/hackers-docs.html Index of Documentation for People Interested in Writing and/or Understanding the Linux Kernel].

* USB based devices; Also see:
** [[Development: How to develop drivers for USB based devices|How to develop drivers for USB based devices]]
** [[Development: Reverse Engineering USB Webcams|Reverse Engineering USB Webcams]]

==== A Word on Non-Disclosure Agreements ====
Companies frequently allow developers to see detailed chip specifications or even Linux source code under a Non-disclosure agreement (NDA).

A NDA isn't necessarily a barrier to writing a GPL'd driver; it just depends on what it says. While there are some movements at the Open Source community for open datasheets, unfortunately several vendors still prefer to keep the Intelectual Property (IP) of their documents protected, under the terms of an NDA.

If you are required to sign an NDA, read it carefully. If the NDA merely stops you from disclosing the specifications, you should be fine. This does not prevent you from writing and distributing a driver under a free software license. Also note that, in some cases, signing a NDA may even go so far as restricting you from even mentioning to others that you've signed a NDA -- in other words, you can't talk about or even mention the development of the new driver until the terms of the NDA lift. Also make sure to check that you're allowed to be the copyright holder of your driver. If not, they might redistribute your code under another license, and thus close the code. It is wise to ask to a lawyer to analyze the NDA clauses or to use [[http://www.linuxfoundation.org/en/NDA_program Linux Foundation NDA program]] to be sure if the terms you're signing will allow you to release an open source code.

Chip and board manufacturers have an incentive to be helpful to free software developers, as the drivers will help move their product. And as long as the NDA gives you the necessary freedom to publish your code, the information supplied can be extremely helpful in writing the driver.

====After you've finished the driver(s) for the previously unsupported components====
Its time to return to the steps outlined in "Case 1", where you link together the necessary pieces in the drivers that will bring about support for your device (i.e. adding all the glue code).

== Don't forget to send info to the Wiki !==
* upload non-proprietary picture(s) of the device (i.e. those that you took, and not ones taken from the vendor's website without express permission to do so!) Note: Please use a descriptive filename, as opposed to "image1.jpg" or the generic/cryptic filename that your digital camera gave to it when it was created.
* create a device article outlining what type of device it is, features, support information (drivers, firmware, remote), identification, kernel output messages etc., etc., (see the [[Wiki - New Device Copy & Paste Template|New Device Copy & Paste Template]] as a guide for an article's format).

===bttv-gallery ===
{{Note|in the early stages of V4L history, well before a wiki was even dreamt of, the bttv-gallery was initiated by Gunther Mayer, a leading tuner/hardware developer with the project. The bttv-gallery essentially served as the official hardware resource centre for V4L, whereby it documented a great deal of the insights (such as tuner components, GPIO settings, EEPROM detection etc., etc.,) that were conveyed on the mailing list, as well as from user submissions, and also provided a visual library of the devices. Over time, a great many analogue and DVB devices were documented. Even after the site feel into a state of stasis, it remained an excellent reference source that was easily searchable for many hard to find facts/items, as well as for purposes of device identification. Unfortunately, it appears that the bttv-gallery webpage no longer exits, though access to its resources can be made through the last available snapshot on the wayback machine: http://wayback.archive.org/web/*/http://www.bttv-gallery.de}}

[[Category:Development]]

Supported Hardware

2012-10-08T17:40:06Z

CityK: /* Determining the Device's Identity */ update bttv-gallery remark

This page is intended to help the "end user" determine whether or not the V4L-DVB device they own, or one that they are considering acquiring, is supported under Linux.
{{Note|Just because your device happens to have a chip on it that corresponds to some existing driver does NOT mean your product is supported. The driver has to be aware that it's related to some hardware (typically through the [[Supported_Hardware#Determining_the_Device's_Identity|subsystem ID from the USB ID or PCI ID]]). If the driver doesn't recognize/bind to your particular hardware, then the module will probably load but then proceed to not do anything. In other words, support for your device would have to be added to the driver.}}

== Determining the Device's Identity==
Normally the device name and model are written somewhere on either the device itself, its box/packaging or, at the very least, listed in its manual. That may seem obvious enough, but a surprising number of devices are available with no, or next to little in the way of, model identification. Ordinarily, that would make for a rather problematic exercise of trying to find support information, however, there are a couple of steps you can do to help give you a starting point for your search (and these steps are just as relevant in the case where you know the device's identity, and you know that it is unsupported, but are seeking to see if it is possible to add support for it):

'''A. With the device NOT installed within or attached to the system:''' 
Take note of any visual clues that will help identify the device. For PCI/PCIe based devices, see if there are any written text/numerical markings printed directly on the board or on IC components. With USB based devices, as they tend to be completely encased, it is difficult, if not impossible, to make any visual identifications of components used in the device's design without resorting to physically prying it open. The degree of difficulty of undertaking such a task can vary greatly, but in most cases the user can, with patience and care, find a way to non-destructively disassemble the device. (Nonetheless, anyone attempting such a venture should be prepared to fully accept the consequences of their own actions in the event of an unsuccessful attempt). If you are not willing to do so, proceed to step "B".

Also note that, for older devices, the former bttv-gallery was a good resource for helping to identify a device; see [[Development:_How_to_add_support_for_a_device#bttv-gallery|here for more details]].

'''B. With the device installed within or attached to the system:''' 
For PCI/PCIe based devices, the output of the following command may be able to aide you in making a determination
:<code>$ /sbin/lspci -vnn</code>
In the output from those commands, look for lines with "Multimedia video controller", "Multimedia controller", "Multimedia adapters" or something similar. The item of particular interest is the '''Subsystem ID''' for that entry.

Similarily, for USB devices, look at the output generated from the command
:<code>$ /sbin/lsusb -v</code>

'''Note:''' Subsystem ID's are usually unique, but in some cases they are not. Meaning that sometimes two different devices have, unfortunately, been given the same ID. This in turn makes obtaining as many as possible identifiable aspects about a device (such as described in point "A" above) an important factor in making a precise device identification.

== Support Information Resources==
Armed with the information you obtained above (such as model name, subsystem ID, etc) try searching:

===The V4L-DVB Wiki===
A good first step is to check whether the device is listed as supported within the appropriate section of the wiki (see the "[[Hardware Device Information]]" section, as also linked to from the Main Pag,e for a starting point for your search. Though, it might be a good idea to also search this wiki using the device's name or the manufacturer name). If the device is not cited anywhere as being supported, then there is a good chance that it will not work under Linux. However, as the information in the wiki is not always current, and far from exhaustive, there are also other sources from which you can check.

{{Note|'''Please be nice to the community and add your insights about your device to the appropriate area in this wiki if there currently is none !!! '''}}

===The V4L-DVB source code===
Navigate through the Linux media driver files (e.g. on your system try /usr/src/linux/drivers/media/, or check the corresponding directories on the git or hg repos you are interested in) and search for the relevant "xxxx-cards.c" file, as it will list devices supported by the "xxxx" driver. Example, within the file [http://git.linuxtv.org/media_tree.git/blob/HEAD:/drivers/media/video/saa7134/saa7134-cards.c saa7134-cards.c] is a listing of all the saa713x media controller IC based devices supported by the saa7134 driver. Similarly for exm28xx-cards.c, cx88-cards.c, etc. etc. ...

===The Mailing Lists===
You should also consider consulting the mailing list archives to see if there is any mention of the device.
* The [mailto:majordomo@vger.kernel.org?body=subscribe%20linux-media Linux-Media Mailing List]. [http://vger.kernel.org/vger-lists.html#linux-media Subscription to the mailing list] is recommended, though it is not required.

Older mailing list archives: Make sure you check both the V4L and DVB mailing lists, as topical misplacement/mis-posting often occurs (as many users are unaware of the distinction between the two different, but in many ways intertwined, subsystems).
* MARC provides a comprehensive [http://marc.info/?l=linux-video searchable V4L archive] ... the actual m/l is archived [https://www.redhat.com/mailman/private/video4linux-list/ here] but requires authentication to access, nor is it as easily searched through
* MARC also provides a [http://marc.info/?l=linux-dvb&r=1&w=2 searchable DVB archive], but its records are not comprehensive (and, as well as, contain a large gap). Therefore, for inquiries relevant to older equipment you will have to sift through either the [http://www.linuxtv.org/pipermail/linux-dvb/ new DVB mailing list] (which began Feb 2005) or use the likes of either a [http://www.google.ca/search?hs=NtR&hl=en&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=site%3Alinuxtv.org&btnG=Search&meta= google site search] or [http://www.spinics.net/lists/linux-dvb/ spinics] to find even older (as well as present) DVB m/l postings...some further resources are also [http://www.linuxtv.org/lists.php mentioned here].

If that search step also proves unsuccessful, then you may wish to consider directly inquiring about the device's status on the relevant mailing list (but please search the archives first!) or #irc channel. Send the information obtained from steps "A" and "B" to the mailing list, along with other important information (such as what type of device it is, a link to a product page if you can find one etc etc). '''''But please first do a search through the archives* to make sure that this hasn't been submitted previously''''' --- a simple way to check if this has been the case is to search the archives for your device's subsystem ID (as determined in step "B"). 

===Elsewhere on the Internet ===
It is worth mentioning that there may be support for your device under Linux offered outside of that provided by LinuxTV, so a google search, using the appropriate combinations of terms, is also recommended. In addition, there are likely a number of websites (outside of the V4L-DVB wiki) that track hardware support -- For example, you can take a look at http://hardware4linux.info/type/87/ to see the note for the different devices.
[[Category:Hardware]]

Development: How to add support for a device

2012-10-08T17:29:38Z

CityK: /* Case 1: Development steps for when your device uses components for which drivers already exist */ remove reference to Hg, provide link to d/l instructions

This article is meant to serve as an introduction to the task of developing driver support for a device.

==Getting Started==
The very first thing you should do is find out how your device identifies itself:

'''For PCI/PCIe devices''' - use the command:
:<code>$ /sbin/lspci -vnn</code>

'''For USB based devices''' - use the command:
:<code>$ /sbin/lsusb -v</code>

The output generated from the above should provide you with the identify of the main bridge chip as well as the important piece of information known as the device's subsystem ID.

Next, you should try to identify the other component ICs/chips that your device uses. In regards to TV tuner devices, often the tuner chip and demodulator(s) are hidden within a metallic box connected directly to the antenna input. In such cases, this tuner module will usually have an identifying model name/type printed upon it's face, though it is also just as common for this to be obscured underneath a sticker that the device manufacturer has laid over top. With care, you can usually peel back the manufacturer's device sticker to discover the tuner module's own part identifier label or stamp.

Note: You can find a lot of useful device related information:
* here in the wiki
* in the [[Development:_How_to_add_support_for_a_device#bttv-gallery|bttv-gallery]]
* and by having a look at MS-Windows drivers (in particular, the .inf files), as they often contain a lot of particulars about a device's hardware components

== Case 1: Development steps for when your device uses components for which drivers already exist==
Extending support for your device under such circumstances can range from being a trivial matter to one which requires some patience and discovery through the process of trial & error.

First off, [[How to Obtain, Build and Install V4L-DVB Device Drivers|download the latest V4L-DVB source code from Git]] and search for a device that is similar to your own - something like your device may already be supported but with another name. In such a case, you can copy a similar entry and fill in the values for the new device. For example:
* for a bttv chip you add to bttv-cards.c and bttv.h,
* for cx88 chip - cx88-cards.c and cx88.h,
* for saa713x chip saa7134-cards.c and saa7134.h
... and so forth.

==== For TV tuner devices: Finding the correct tuner ====
In more than 90% of all cases something like.. first test one to your norm specific type with older Philips API, then test LG API and if there are still missing channels in UHF test MK3 API types will succeed. To find the exact takeover and radio config might be further steps, but most likely this can be/is covered by one of the existing types already.

At least it will usually take only three tuners to reach this point and if you find all three API types don't work, then ...

To check for the tda9887 on MK3 and mt32xx types can be done at once or as a next step. Since also the Philips silicon tuners should be well detected now, we can identify such like the yet unsupported Xceive types quite well. They seem to fail safely upon the initialization sequence with tuner=54 if I got Carsten right. So the really difficult/new ones should show up quickly enough and we can try to prepare a list of typical addresses for new devices like channel decoders, second eeproms, most likely hidden analog demodulators and such.

That the multi and hybrid types can have other issues too, like antenna input/filter/demodulator RF-amplifier switching and the like is above simple analog tuner programming and not yet fully investigated for all new types, but it seems there is some very good progress too.

The takeover suggestions in most datasheets on switch between VHF and UHF aren't related closely to technical specifications and precise measurements. They simply take it from _known_ channels currently in use and select those which are closest from both sides! Most obvious for NTSC-M tuners. If one is missing in the gap, to go right into the middle seems to be still reasonable for me as a next step in such cases, but to finally make the decision on what is empirically reported to work best is legal in lack of further documentation.

==== Guessing the .gpio values and masks for input ====
For some guidance on programming for these aspects, see:
* the programming section of the [[GPIO pins]] article and
* the [[Remote controllers-V4L|Remote controllers]] article. Note: before writing the patch please double-check that there are no such keys in V4L-DVB source code already.

==== Test your code====
If the device works - that's cool! Congratulations! You are now ready to [[Development: How to submit patches|send a patch to the mailing list]].

==Case 2: Development steps for when your device uses components for which drivers do not currently exist==

Unfortunately, development of a new chipset driver is generally not an easy task. For starters, you're going to have to be capable and/or ambitious enough to produce the code or, at the very least, inspire an existing developer to do such (and there is by no means any guarantee that anyone will be interested...even if you cry and beg and/or throw bags of money). Either way, you should first search and/or inquire on the mailing list as to whether or not someone is already undertaking such development.

If you're going to work on a driver for a chip you should try to find documentation for it online. In the end, you may require getting information directly from the manufacturer (in the case where no information can be found in the "wild" or those where publicly available information is incomplete or lacking).

* For general references on how to develop a Linux kernel driver module, take a look at the [http://jungla.dit.upm.es/%7Ejmseyas/linux/kernel/hackers-docs.html Index of Documentation for People Interested in Writing and/or Understanding the Linux Kernel].

* USB based devices; Also see:
** [[Development: How to develop drivers for USB based devices|How to develop drivers for USB based devices]]
** [[Development: Reverse Engineering USB Webcams|Reverse Engineering USB Webcams]]

==== A Word on Non-Disclosure Agreements ====
Companies frequently allow developers to see detailed chip specifications or even Linux source code under a Non-disclosure agreement (NDA).

A NDA isn't necessarily a barrier to writing a GPL'd driver; it just depends on what it says. While there are some movements at the Open Source community for open datasheets, unfortunately several vendors still prefer to keep the Intelectual Property (IP) of their documents protected, under the terms of an NDA.

If you are required to sign an NDA, read it carefully. If the NDA merely stops you from disclosing the specifications, you should be fine. This does not prevent you from writing and distributing a driver under a free software license. Also note that, in some cases, signing a NDA may even go so far as restricting you from even mentioning to others that you've signed a NDA -- in other words, you can't talk about or even mention the development of the new driver until the terms of the NDA lift. Also make sure to check that you're allowed to be the copyright holder of your driver. If not, they might redistribute your code under another license, and thus close the code. It is wise to ask to a lawyer to analyze the NDA clauses or to use [[http://www.linuxfoundation.org/en/NDA_program Linux Foundation NDA program]] to be sure if the terms you're signing will allow you to release an open source code.

Chip and board manufacturers have an incentive to be helpful to free software developers, as the drivers will help move their product. And as long as the NDA gives you the necessary freedom to publish your code, the information supplied can be extremely helpful in writing the driver.

====After you've finished the driver(s) for the previously unsupported components====
Its time to return to the steps outlined in "Case 1", where you link together the necessary pieces in the drivers that will bring about support for your device (i.e. adding all the glue code).

== Don't forget to send info to the Wiki !==
* upload non-proprietary picture(s) of the device (i.e. those that you took, and not ones taken from the vendor's website without express permission to do so!) Note: Please use a descriptive filename, as opposed to "image1.jpg" or the generic/cryptic filename that your digital camera gave to it when it was created.
* create a device article outlining what type of device it is, features, support information (drivers, firmware, remote), identification, kernel output messages etc., etc., (see the [[Wiki - New Device Copy & Paste Template|New Device Copy & Paste Template]] as a guide for an article's format).

===bttv-gallery ===
In addition, if your device is not included in the [http://bttv-gallery.de bttv-gallery.de], you may wish to consider sending the following info to Gunther Mayer <gunther.mayer () gmx ! net>.

{{Note|in the early stages of V4L history, well before a wiki was even dreamt of, the bttv-gallery was initiated by Gunther Mayer, a leading tuner/hardware developer with the project. The bttv-gallery essentially served as the official hardware resource centre for V4L, whereby it documented a great deal of the insights (such as tuner components, GPIO settings, EEPROM detection etc., etc.,) that were conveyed on the mailing list, and also provided a visual library of the devices. Though it seems, unfortunately, that the bttv-gallery has fallen into stasis, it still remains an excellent reference source that is easily searchable for many hard to find facts/items as well as for purposes of device identification.}}

Your contribution will help to improve open source support!
Because there are many cards and variations by different
vendors, the developers need _your_ help to get it all supported.

1st priority:
* picture of the card, the card backside (high resolution pics if feasible)
* lspci -vnn

further information:
# picture of remote control (if applicable) and of original package
# list of chips
# list of input connectors
# printings on PCB, printings on stickers on the card
# lspci -v and lspci -vn
# "dmesg" when loading the modules
# if feasible "eeprom" output (from bttv tools)
# if feasible "*.INF" files from the Windows Driver CD
# exact tuner type (possibly this is hidden under the vendor sticker)
# exact model name and model number from package
# in which country do you live/ in which country this card was bought
# which application(s) did you use to test your setup ?
# If some parts of your card seem to work, describe exactly what you did and what you see/hear now.

Even parts of this info will be very helpful!

[[Category:Development]]

TV Related Software

2012-10-07T01:17:04Z

CityK: minor edit and additon to zapping list

__NOEDITSECTION__
<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;">
{| style="background-color:#F7F9FB;" cellspacing=0 cellpadding=5 border=0
| valign=top | [[Image:Software_viewing_apps_icon.png|50px]]
|
= '''TV Related Software:'''=
|}
Here, we aim to provide useful information about software applications that are directly related to or which are generally useful in some respect to the reception and manipulation of TV signals on Linux based computer systems.

In order to be most useful for the reader, this page is divided into two sections:
* A categorical overview of software
* An alphabetical listing of software

{{Note|''If you're new to this aspect of computing, rather than trying single programs one after another, you might be more interested in how to quickly get a fully working system as described in the "[[Example setups]]" page. Or perhaps instead you may simply want to perform some quick tests on your system, such as like those outlined in the "[[Testing your DVB device]]" article.''}} 

__TOC__
=A Categorical Overview=
==Utility Suites and Standalone Tools==
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|

===Analogue Utility Suites or Standalone Tools===
* [[dov4l2]] [http://www.vanheusden.com/dov4l2/]
* [[v4l2-utils]]
* [[v4l2ucp]]
* [[V4L Test Suite]]
* [[xawtv]]

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|

===DVB Utility Suites and Standalone Tools===

* [[LinuxTV dvb-apps]]
* [[DVB tools]]
* [[DVBv5 Tools]]
* [[dvbsak]]
* [[ZapDvb]]
* [[dvbd]]
* [[JustDvb-It]]
|}

==Tools for performing frequency scans==
* [[Frequency scan|Frequency Scanning]]
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue Tools for performing frequency scans===
* [[scantv]] (part of the [[Xawtv#Associated_Utilities|xawtv package]])
|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===DVB Tools for performing frequency scans===
... also see [[Testing your DVB device]] (PCI, USB, ...) ... scan & zap stuff
* [[scan]]
* [[dvbscan|dvbscan/scandvb/atscscan]]
* [[w_scan]]
* [[scan-s2]]
* [[scte65scan]] [http://www.mythtv.org/wiki/Scte65scan] [http://forums.sagetv.com/forums/showthread.php?t=45474] [http://scte65scan.sourceforge.net/]
* [[dvbv5-scan]]
|}

==Tools for tuning==
* [[Tuning]]
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue Tools for tuning===
|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===DVB Tools for tuning===
... also see [[Testing your DVB device]] (PCI, USB, ...) ... scan & zap stuff
* [[zap|{a,s,c,t}zap]]
* [[dvbsnoop]]
* [[dvbtune]]
* [[dvbv5-zap]]
* [[szap-s2]]
* [[ZapDvb]]
|}

==Tools for signal strength==
* [[Testing reception quality]]
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue Tools for signal strength===
|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===DVB Tools for signal strength===
* [[femon]]
* [[dvb-fe-tool]]
|}

==Standalone Software to Watch & Record TV==
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|

===Standalone Software to Watch Analogue TV===
* [[fftv]] [http://fftv.sourceforge.net/] -- tv/radio viewer/recorder -- [http://sourceforge.net/project/showfiles.php?group_id=71197 sourcecode]
* [[Gnometv]] [http://gnometv.sourceforge.net/]
* [[Gv4l]] [http://gv4l.sourceforge.net/]
* [[kdetv]] (also formerly known as [[QtVision]], the rewrite of the former [[KWinTV]])
* [[ktv]] [http://jerous.thimhallan.org/static//ktv/]
* [[LinTV]]
* [[MPlayer]]
** [[SMPlayer]] [http://smplayer.sourceforge.net/]
* [[tvtime]] [http://tvtime.sourceforge.net/]
* [[TV-Viewer]] (for Hardware MPEG2 Encoder cards)
* [[VLC media player]]
* [[xawtv]]
** [[MoTV]]
* [[XdTV]]
* [[Xine]]
* [[Zapping]] [http://zapping.sourceforge.net/Zapping/index.html] - a TV viewer for the Gnome desktop.
... also see [[V4L TV Viewing]]

===Analogue Capturing / Frame Grabbing Utilities===
* [[V4L capturing]] ... also see [[Transcode]]

* [[DVR]] [http://www.pierrox.net/dvr/]
* [[Grabby]] [http://www.vanheusden.com/grabby/]
* [[Streamer]]
* VideoDog [http://linux.softpedia.com/get/Multimedia/Video/VideoDog-9261.shtml] [http://linux.die.net/man/1/videodog]
* [[WebVCR+]] [http://webvcrplus.sourceforge.net/index.html]

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|

===Standalone Software to Watch Digital TV ===
* [[Antenna DTV]]
* [[gdvb]]
* [[gnutv]]
* [[Kaffeine]]
** [[KaxTV]]
* [[Klear]]
* [[Me TV]]
* [[MPlayer]]
** [[SMPlayer]] [http://smplayer.sourceforge.net/]
* [[VLC media player]]
* [[xawtv]] ... (only version 4 for DVB)
* [[XdTV]]
* [[Xine]]
** [[gxine]]

===DVB Tools for unattended/headless recording===
* [[dvbsched]] (in [[dvbd]])
* [[dvbrecord]] (in [[dvbsak]])
* [[atscap]]
* [[DvbCronRecordingPlugin]] for Trac

''Misc ''Tutorials, Howtos, Usage Info & Guides:''
* Howto record [[multiple programs]] at once
|}

==Media Player Software==
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Media Center Software===
In addition to offline playback of captured & downloaded media material, many will feature live TV viewing and capturing facilities
* [[Elisa]] [http://elisa.fluendo.com/]
* [[Entertainer Project]] [http://www.entertainer-project.com/features.php]
* [[Freevo]]
* [[GeeXboX]]
* [[Home Theater System]]
** showtime (OpenGL-based media player)
** tvheadend (TV streaming server)
* [[LinuxMCE]] [http://www.linuxmce.com/] Linux media center - A forked project from [[pluto]]
* [[Morphine.TV]] [http://wiki.morphine.tv/tiki-custom_home.php]
* [[My Media System]] [http://mymediasystem.org/]
* [[MythTV]]
* [[Mini DVB Linux]] ??
* [[oxine]] [http://oxine.sourceforge.net/]
* [[pluto]]
* [[Rage]] [http://www.rasterman.com/index.php?page=News (see the Monday, 27 March 2006 entry)]
* [[SageTV]] [http://sagetv.com/linuxOEMedition.html]
* [[VDR]] - VDR is one of the most popular TV applications. It features watching TV, recording storage on disk, EPG, Dolby Digital, playback, multi language and much more. VDR, although originally written for FF cards, works also with budget cards, if one installs the [[VDR Software Decoder Plugin]].
* XBMC [http://xbmc.org/]
* [[Yahdr]] 
...
|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===Media Center Distributions===
Complete operating systems tailored for easy installation of everything required to have a media centre.
* [[iMedia MythTV Linux]] [http://www.mini-box.com/iMediaMythTV]
* Knoppmyth
* [[LinVDR]] [http://www.linvdr.org/projects/linvdr/index.en.php] -- this was a Linux distro based around VDR. Now ancient history
* [[MiniMyth]] [http://linpvr.org/minimyth/]
* Mythbuntu
* MythDora
...

===Standalone Media Players===
i.e. for offline playback of captured materials
* [[Kaffeine]]
* [[Wikipedia:KMPlayer|KMPlayer]]
* [[MPlayer]]
** [[SMPlayer]] [http://smplayer.sourceforge.net/]
* [[Totem]]
* [[VLC media player]]
* [[Xine]]
...

|}

==Network and Streaming Tools==
* [[Streaming]]
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue TV Streaming Utilities===
* [[Streaming-V4L]]
* [[GStreamer]]

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===Network Tools for DVB Streams===
* [[dvbshout]]
* [[dvbsnoop]]
* [[dvbstream]]
* [[DVBStreamer]]
* [[dvbyell]]
* [[getstream]]
* [[Me TV]]
* [[mumudvb]]
* [[Home Theater System|TVheadend]]

===Streaming Software for Digital TV===
* [[dvbice]]
* [[VLC media player]]
|}

==Tools to Show Videotext/Teletext/Interactive Content/Closed Captioning==
* [[Text capture]]
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue TV Tools to Show Videotext/Teletext/Interactive Content/Closed Captioning===
* [[AleVT]]
* [[mtt]] (part of the [[Xawtv#Associated_Utilities|xawtv package]] ... both v3 and v4)

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===DVB Tools to Show Videotext/Teletext/Interactive Content/Closed Captioning===
* [[AleVT]] - v1.7.0 or a patched v1.6.2
* [[mtt]] - (part of the [[Xawtv#Associated_Utilities_2|xawtv package]]... v4 only )
* [[RedButton MHEG Engine]]
|}

==Electronic Program Guide / EIT tools==
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue TV Program Guide Tools===
|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
=== DVB Program Guide Tools===
* atsc_epg - included within the [[LinuxTV dvb-apps]]
* [[tv_grab_dvb]]
* [[dvbsnoop]]
* [[DVBStreamer]]
* LoadEPG [http://lukkinosat.altervista.org/]
* MediaHighWay EPG, mhwepg [http://jrepetto.free.fr/] [http://www.linuxtv.org/vdrwiki/index.php/Mhwepg]
* tv_grab_dvb_plus ( was tvgrabeit ) [http://sourceforge.net/projects/tvgrabeit/]
* [[XMLTV]]
|}

==Tools for Editing Captured TV content==
* [[Avidemux2]]
* [[dvbcut]]
* [[ProjectX]]
* [[MEncoder]]
''Misc ''Tutorials, Howtos, Usage Info & Guides:''
* [[Post-processing]] of recorded material
....

'''Examples of User TV Device Hardware and Software Configurations:'''
* [[Example setups]]

</div>

= An Alphabetical Listing =

{| class="wikitable sortable"
|+'''A Overview of Software Applications which are useful in regards to TV on a Linux based Computer System'''
|-
! Software Application !! Supports Analogue !! Supports DVB !! Recording Capabilities !! Offline Playback !! Editing Capabilities !! Channel storage !! Language !! class="unsortable"| Comments
|-
| [[AleVT]] || y || y || || || || || || Program to use Teletext/Videotext on analog and digital TV
|-
| [[Antenna DTV]] || n || y || y || n || n || t channels.conf format || Python || Watch, record and monitor signal level of digital TV
|-
| [[dvbd]] || || y || || || || || C++ || Traditional UNIX daemon for DVB
|-
| [[dvbice]] || n || y || y || || || || C || Recompress and stream audio and video to Icecast/HTTP in Theora/Vorbis
|-
| [[dvbsak]] || n || y || || || || || ||
|-
| [[dvbshout]] || n || y || || || || || || Stream radio to Icecast/multicast
|-
| [[dvbsnoop]] || n || y || || || || || C ||
|-
| [[dvbstream]] || n || y || y || n || n || || || a streaming utilitity. Part of the [[DVB tools]] project
|-
| [[DVBStreamer]] || n || y || || || || sqlite, XMLTV format || C || PSI/SI tracking and correctly streams all PIDs including PCR
|-
| [[dvbyell]] || n || y || n || n || n || || || A DVB streaming service.
|-
| [[gdvb]] || || || || || || || ||
|-
| [[GeeXboX]] || || || || || || || ||
|-
| [[getstream]] || n || y || || || || || ||
|-
| [[GStreamer]] || n || y || || || || || ||
|-
| [[Gv4l]] || || || || || || || || A GUI frontend for [[Transcode]]'s V4L functions
|-
| [[Kaffeine]] || n || y || y || y || n || own text format || C++ || Desktop TV Solution
|-
| [[KaxTV]] || || || || || || || || obsoleted
|-
| [[Klear]] || || y || || || || || ||
|-
| [[LinuxTV dvb-apps]] || n || y || y || ? || ? || {a,c,t,s} channels.conf formats|| C || contains dvbscan, {a,c,t,s}zap ...
|-
| [[MEncoder]] || y || y || y || n || y || || C || encoding suite of tools
|-
| [[Me TV]] || n || y || y || n || n || SQLite || C++ || GNOME based DVB TV viewer
|-
| [[Mini DVB Linux]] || || y || || || || || || Distribution with live-CD
|-
| [[MPlayer]] || y || y || y || y || n || channels.conf || C || multi-functional media player
|-
| [[mumudvb]] || n || y || n || n || n || || || Stream multiples channels in multicast (each channel in different group)
|-
| [[MythTV]] || y || y || y || y || y || mysql || C++ || Media Center
|-
| [[pluto]] || || || || || || || ||
|-
| [[ProjectX]] || || || || || || || ||
|-
| [[RedButton MHEG Engine]] || || || || || || || || [[MHEG-5]] engine
|-
| [[scan-s2]] || n || y || n || n || n || || C || frequency scanning utility which supports DVB APIv5 (for DVB-S2)
|-
| [[Home Theater System | showtime]] || || || || || || || C || OpenGL-based media player
|-
| [[szap-s2]] || || y || y || || || || C || tuning utility which supports DVB APIv5 (for DVB-S2)
|-
| [[tv_grab_dvb]] || || y || || || || [[XMLTV]] format || C || dumps DVB [[EPG]] info in [[XMLTV]] format
|-
| [[Home Theater System | HTS Tvheadend]] || y || y || y || y || y || [[XMLTV]] format || C || TV streaming server
|-
| [[VDR]] || y * || y || y || y || y || VDR format channels.conf || C++ || analogue with plugins only DVB APIv5 since 1.7.2
|-
| [[VLC media player]] || || || || || || || ||
|-
| [[w_scan]] || n || y || n || n || n || VDR channels.conf kaffeine zap/xine tuning data for scan|| C || ATSC/DVB-C/S/S2/T frequency scanner
|-
| [[xawtv]] || y || y * || y || y || n || || || * only v4 supports DVB
|-
| [[XdTV]] || y || y || y || || || || || TV viewing app. Development stopped
|-
| [[xine]] || || y || y || y || || || || multi-functional media player
|-
| [[ZapDvb]] || || || || || || || ||

|}

[[Category:Software]]

DVBv5 Tools

2012-10-07T01:12:59Z

CityK: minor edits; add note about older dvb tools; category

DVBv5 Tools (not to be confused with the similarly named, but much older, [[DVB tools]] project) is a small set of command line utilities that was developed to be compliant with the newer features provided by [[Development:_Linux_Media_Infrastructure_API|version 5 of the DVB API]].[http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/43100] The tools should also be backward compatible with the older v3 DVB API.

This DVB tool suite (confusingly enough!) resides in the [http://git.linuxtv.org/v4l-utils.git v4l-utils git repository]. Its components include:
* [[dvbv5-scan]] for frequency scanning
* [[dvbv5-zap]] for channel tuning
* [[dvb-fe-tool]] for testing a DVB device's frontend
* and [[dvb-format-convert]] for initial scan file format conversion

[[Category:Software]][[Category:Apps & Utilities]]

TV Related Software

2012-10-07T01:08:50Z

CityK: a few additions to the lists

__NOEDITSECTION__
<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;">
{| style="background-color:#F7F9FB;" cellspacing=0 cellpadding=5 border=0
| valign=top | [[Image:Software_viewing_apps_icon.png|50px]]
|
= '''TV Related Software:'''=
|}
Here, we aim to provide useful information about software applications that are directly related to or which are generally useful in some respect to the reception and manipulation of TV signals on Linux based computer systems.

In order to be most useful for the reader, this page is divided into two sections:
* A categorical overview of software
* An alphabetical listing of software

{{Note|''If you're new to this aspect of computing, rather than trying single programs one after another, you might be more interested in how to quickly get a fully working system as described in the "[[Example setups]]" page. Or perhaps instead you may simply want to perform some quick tests on your system, such as like those outlined in the "[[Testing your DVB device]]" article.''}} 

__TOC__
=A Categorical Overview=
==Utility Suites and Standalone Tools==
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|

===Analogue Utility Suites or Standalone Tools===
* [[dov4l2]] [http://www.vanheusden.com/dov4l2/]
* [[v4l2-utils]]
* [[v4l2ucp]]
* [[V4L Test Suite]]
* [[xawtv]]

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|

===DVB Utility Suites and Standalone Tools===

* [[LinuxTV dvb-apps]]
* [[DVB tools]]
* [[DVBv5 Tools]]
* [[dvbsak]]
* [[ZapDvb]]
* [[dvbd]]
* [[JustDvb-It]]
|}

==Tools for performing frequency scans==
* [[Frequency scan|Frequency Scanning]]
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue Tools for performing frequency scans===
* [[scantv]] (part of the [[Xawtv#Associated_Utilities|xawtv package]])
|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===DVB Tools for performing frequency scans===
... also see [[Testing your DVB device]] (PCI, USB, ...) ... scan & zap stuff
* [[scan]]
* [[dvbscan|dvbscan/scandvb/atscscan]]
* [[w_scan]]
* [[scan-s2]]
* [[scte65scan]] [http://www.mythtv.org/wiki/Scte65scan] [http://forums.sagetv.com/forums/showthread.php?t=45474] [http://scte65scan.sourceforge.net/]
* [[dvbv5-scan]]
|}

==Tools for tuning==
* [[Tuning]]
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue Tools for tuning===
|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===DVB Tools for tuning===
... also see [[Testing your DVB device]] (PCI, USB, ...) ... scan & zap stuff
* [[zap|{a,s,c,t}zap]]
* [[dvbsnoop]]
* [[dvbtune]]
* [[szap-s2]]
* [[dvbv5-zap]]
|}

==Tools for signal strength==
* [[Testing reception quality]]
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue Tools for signal strength===
|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===DVB Tools for signal strength===
* [[femon]]
* [[dvb-fe-tool]]
|}

==Standalone Software to Watch & Record TV==
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|

===Standalone Software to Watch Analogue TV===
* [[fftv]] [http://fftv.sourceforge.net/] -- tv/radio viewer/recorder -- [http://sourceforge.net/project/showfiles.php?group_id=71197 sourcecode]
* [[Gnometv]] [http://gnometv.sourceforge.net/]
* [[Gv4l]] [http://gv4l.sourceforge.net/]
* [[kdetv]] (also formerly known as [[QtVision]], the rewrite of the former [[KWinTV]])
* [[ktv]] [http://jerous.thimhallan.org/static//ktv/]
* [[LinTV]]
* [[MPlayer]]
** [[SMPlayer]] [http://smplayer.sourceforge.net/]
* [[tvtime]] [http://tvtime.sourceforge.net/]
* [[TV-Viewer]] (for Hardware MPEG2 Encoder cards)
* [[VLC media player]]
* [[xawtv]]
** [[MoTV]]
* [[XdTV]]
* [[Xine]]
* [[Zapping]] [http://zapping.sourceforge.net/Zapping/index.html] - a TV viewer for the Gnome desktop.
... also see [[V4L TV Viewing]]

===Analogue Capturing / Frame Grabbing Utilities===
* [[V4L capturing]] ... also see [[Transcode]]

* [[DVR]] [http://www.pierrox.net/dvr/]
* [[Grabby]] [http://www.vanheusden.com/grabby/]
* [[Streamer]]
* VideoDog [http://linux.softpedia.com/get/Multimedia/Video/VideoDog-9261.shtml] [http://linux.die.net/man/1/videodog]
* [[WebVCR+]] [http://webvcrplus.sourceforge.net/index.html]

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|

===Standalone Software to Watch Digital TV ===
* [[Antenna DTV]]
* [[gdvb]]
* [[gnutv]]
* [[Kaffeine]]
** [[KaxTV]]
* [[Klear]]
* [[Me TV]]
* [[MPlayer]]
** [[SMPlayer]] [http://smplayer.sourceforge.net/]
* [[VLC media player]]
* [[xawtv]] ... (only version 4 for DVB)
* [[XdTV]]
* [[Xine]]
** [[gxine]]

===DVB Tools for unattended/headless recording===
* [[dvbsched]] (in [[dvbd]])
* [[dvbrecord]] (in [[dvbsak]])
* [[atscap]]
* [[DvbCronRecordingPlugin]] for Trac

''Misc ''Tutorials, Howtos, Usage Info & Guides:''
* Howto record [[multiple programs]] at once
|}

==Media Player Software==
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Media Center Software===
In addition to offline playback of captured & downloaded media material, many will feature live TV viewing and capturing facilities
* [[Elisa]] [http://elisa.fluendo.com/]
* [[Entertainer Project]] [http://www.entertainer-project.com/features.php]
* [[Freevo]]
* [[GeeXboX]]
* [[Home Theater System]]
** showtime (OpenGL-based media player)
** tvheadend (TV streaming server)
* [[LinuxMCE]] [http://www.linuxmce.com/] Linux media center - A forked project from [[pluto]]
* [[Morphine.TV]] [http://wiki.morphine.tv/tiki-custom_home.php]
* [[My Media System]] [http://mymediasystem.org/]
* [[MythTV]]
* [[Mini DVB Linux]] ??
* [[oxine]] [http://oxine.sourceforge.net/]
* [[pluto]]
* [[Rage]] [http://www.rasterman.com/index.php?page=News (see the Monday, 27 March 2006 entry)]
* [[SageTV]] [http://sagetv.com/linuxOEMedition.html]
* [[VDR]] - VDR is one of the most popular TV applications. It features watching TV, recording storage on disk, EPG, Dolby Digital, playback, multi language and much more. VDR, although originally written for FF cards, works also with budget cards, if one installs the [[VDR Software Decoder Plugin]].
* XBMC [http://xbmc.org/]
* [[Yahdr]] 
...
|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===Media Center Distributions===
Complete operating systems tailored for easy installation of everything required to have a media centre.
* [[iMedia MythTV Linux]] [http://www.mini-box.com/iMediaMythTV]
* Knoppmyth
* [[LinVDR]] [http://www.linvdr.org/projects/linvdr/index.en.php] -- this was a Linux distro based around VDR. Now ancient history
* [[MiniMyth]] [http://linpvr.org/minimyth/]
* Mythbuntu
* MythDora
...

===Standalone Media Players===
i.e. for offline playback of captured materials
* [[Kaffeine]]
* [[Wikipedia:KMPlayer|KMPlayer]]
* [[MPlayer]]
** [[SMPlayer]] [http://smplayer.sourceforge.net/]
* [[Totem]]
* [[VLC media player]]
* [[Xine]]
...

|}

==Network and Streaming Tools==
* [[Streaming]]
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue TV Streaming Utilities===
* [[Streaming-V4L]]
* [[GStreamer]]

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===Network Tools for DVB Streams===
* [[dvbshout]]
* [[dvbsnoop]]
* [[dvbstream]]
* [[DVBStreamer]]
* [[dvbyell]]
* [[getstream]]
* [[Me TV]]
* [[mumudvb]]
* [[Home Theater System|TVheadend]]

===Streaming Software for Digital TV===
* [[dvbice]]
* [[VLC media player]]
|}

==Tools to Show Videotext/Teletext/Interactive Content/Closed Captioning==
* [[Text capture]]
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue TV Tools to Show Videotext/Teletext/Interactive Content/Closed Captioning===
* [[AleVT]]
* [[mtt]] (part of the [[Xawtv#Associated_Utilities|xawtv package]] ... both v3 and v4)

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===DVB Tools to Show Videotext/Teletext/Interactive Content/Closed Captioning===
* [[AleVT]] - v1.7.0 or a patched v1.6.2
* [[mtt]] - (part of the [[Xawtv#Associated_Utilities_2|xawtv package]]... v4 only )
* [[RedButton MHEG Engine]]
|}

==Electronic Program Guide / EIT tools==
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue TV Program Guide Tools===
|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
=== DVB Program Guide Tools===
* atsc_epg - included within the [[LinuxTV dvb-apps]]
* [[tv_grab_dvb]]
* [[dvbsnoop]]
* [[DVBStreamer]]
* LoadEPG [http://lukkinosat.altervista.org/]
* MediaHighWay EPG, mhwepg [http://jrepetto.free.fr/] [http://www.linuxtv.org/vdrwiki/index.php/Mhwepg]
* tv_grab_dvb_plus ( was tvgrabeit ) [http://sourceforge.net/projects/tvgrabeit/]
* [[XMLTV]]
|}

==Tools for Editing Captured TV content==
* [[Avidemux2]]
* [[dvbcut]]
* [[ProjectX]]
* [[MEncoder]]
''Misc ''Tutorials, Howtos, Usage Info & Guides:''
* [[Post-processing]] of recorded material
....

'''Examples of User TV Device Hardware and Software Configurations:'''
* [[Example setups]]

</div>

= An Alphabetical Listing =

{| class="wikitable sortable"
|+'''A Overview of Software Applications which are useful in regards to TV on a Linux based Computer System'''
|-
! Software Application !! Supports Analogue !! Supports DVB !! Recording Capabilities !! Offline Playback !! Editing Capabilities !! Channel storage !! Language !! class="unsortable"| Comments
|-
| [[AleVT]] || y || y || || || || || || Program to use Teletext/Videotext on analog and digital TV
|-
| [[Antenna DTV]] || n || y || y || n || n || t channels.conf format || Python || Watch, record and monitor signal level of digital TV
|-
| [[dvbd]] || || y || || || || || C++ || Traditional UNIX daemon for DVB
|-
| [[dvbice]] || n || y || y || || || || C || Recompress and stream audio and video to Icecast/HTTP in Theora/Vorbis
|-
| [[dvbsak]] || n || y || || || || || ||
|-
| [[dvbshout]] || n || y || || || || || || Stream radio to Icecast/multicast
|-
| [[dvbsnoop]] || n || y || || || || || C ||
|-
| [[dvbstream]] || n || y || y || n || n || || || a streaming utilitity. Part of the [[DVB tools]] project
|-
| [[DVBStreamer]] || n || y || || || || sqlite, XMLTV format || C || PSI/SI tracking and correctly streams all PIDs including PCR
|-
| [[dvbyell]] || n || y || n || n || n || || || A DVB streaming service.
|-
| [[gdvb]] || || || || || || || ||
|-
| [[GeeXboX]] || || || || || || || ||
|-
| [[getstream]] || n || y || || || || || ||
|-
| [[GStreamer]] || n || y || || || || || ||
|-
| [[Gv4l]] || || || || || || || || A GUI frontend for [[Transcode]]'s V4L functions
|-
| [[Kaffeine]] || n || y || y || y || n || own text format || C++ || Desktop TV Solution
|-
| [[KaxTV]] || || || || || || || || obsoleted
|-
| [[Klear]] || || y || || || || || ||
|-
| [[LinuxTV dvb-apps]] || n || y || y || ? || ? || {a,c,t,s} channels.conf formats|| C || contains dvbscan, {a,c,t,s}zap ...
|-
| [[MEncoder]] || y || y || y || n || y || || C || encoding suite of tools
|-
| [[Me TV]] || n || y || y || n || n || SQLite || C++ || GNOME based DVB TV viewer
|-
| [[Mini DVB Linux]] || || y || || || || || || Distribution with live-CD
|-
| [[MPlayer]] || y || y || y || y || n || channels.conf || C || multi-functional media player
|-
| [[mumudvb]] || n || y || n || n || n || || || Stream multiples channels in multicast (each channel in different group)
|-
| [[MythTV]] || y || y || y || y || y || mysql || C++ || Media Center
|-
| [[pluto]] || || || || || || || ||
|-
| [[ProjectX]] || || || || || || || ||
|-
| [[RedButton MHEG Engine]] || || || || || || || || [[MHEG-5]] engine
|-
| [[scan-s2]] || n || y || n || n || n || || C || frequency scanning utility which supports DVB APIv5 (for DVB-S2)
|-
| [[Home Theater System | showtime]] || || || || || || || C || OpenGL-based media player
|-
| [[szap-s2]] || || y || y || || || || C || tuning utility which supports DVB APIv5 (for DVB-S2)
|-
| [[tv_grab_dvb]] || || y || || || || [[XMLTV]] format || C || dumps DVB [[EPG]] info in [[XMLTV]] format
|-
| [[Home Theater System | HTS Tvheadend]] || y || y || y || y || y || [[XMLTV]] format || C || TV streaming server
|-
| [[VDR]] || y * || y || y || y || y || VDR format channels.conf || C++ || analogue with plugins only DVB APIv5 since 1.7.2
|-
| [[VLC media player]] || || || || || || || ||
|-
| [[w_scan]] || n || y || n || n || n || VDR channels.conf kaffeine zap/xine tuning data for scan|| C || ATSC/DVB-C/S/S2/T frequency scanner
|-
| [[xawtv]] || y || y * || y || y || n || || || * only v4 supports DVB
|-
| [[XdTV]] || y || y || y || || || || || TV viewing app. Development stopped
|-
| [[xine]] || || y || y || y || || || || multi-functional media player
|-
| [[ZapDvb]] || || || || || || || ||

|}

[[Category:Software]]

DVB tools

2012-10-07T00:59:43Z

CityK: minor edits; add note about dvbv5 tools and improve dvbdate citation description

The '''DVB tools''' project (not associated with LinuxTV, nor to be confused with the [[DVBv5 Tools]] or [[LinuxTV dvb-apps|dvb-apps]][[#fn_1|1]] packages) includes the following apps:
* [[dvbstream]] - a popular tool that can be used to save a DVB program stream to disk or distribute it over a network using the rtp protocol
* [[dvbtune]] - a simple tune utility list szap/tzap/czap
* [[dvbaudio]] - a tool for DVB audio recordings and
* [[dvbtextsubs]] - a package for generating DVD subtitles from a DVB broadcast
* [[dvbdate]][[#fn_1|1]]
....and others

<cite id="fn_1">[[#fn_1_back|Note 1:]] </cite>Though the [[dvbdate]] utility that is found in both the DVB tools and dvb-apps packages is the same! ... ''perhaps different versions/releases of the app?''

==External Links==
* [http://sourceforge.net/projects/dvbtools DVB tools Sourceforge project page]

[[Category:Software]]

Dvbv5-scan

2012-09-13T21:29:20Z

CityK: "yet known" or "currently unknown", but not "yet unknown" ... there are knowns and unknowns ... and if you're Rumsfeld, there are also unknown unkowns

{{lowercase|dvbv5-scan}}

dvbv5-scan is a command line [[Frequency scan|frequency scanning]] tool for [[Digital Video Broadcasting|digital TV services]] that is compliant with [[Development:_Linux_Media_Infrastructure_API|version 5 of the DVB API]], and backward compatable with the older v3 DVB API. It was developed as part of [[DVBv5 Tools]] suite, which (confusingly enough!) resides in the [http://git.linuxtv.org/v4l-utils.git v4l-utils git repositiory] [http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/43100].

dvbv5-scan uses a new channel/service file format, which is yet known to other applications.

Other dvb tools from this packet are dvbv5-zap, dvb-fe-tool and dvb-format-convert.

== Parameters ==
<pre>
Usage: dvbv5-scan [OPTION...] <initial file>
scan DVB services using the channel file

-a, --adapter=adapter# use given adapter (default 0)
-d, --demux=demux# use given demux (default 0)
-f, --frontend=frontend# use given frontend (default 0)
-F, --file-freqs-only don't use the other frequencies discovered during
scan
-G, --get_frontend use data from get_frontend on the output file
-I, --input-format=format Input format: CHANNEL, DVBV5 (default: DVBV5)
-l, --lnbf=LNBf_type type of LNBf to use. 'help' lists the available
ones
-N, --nit use data from NIT table on the output file
-o, --output=file output filename (default: dvb_channel.conf)
-O, --output-format=format Output format: CHANNEL, ZAP, DVBV5 (default:
DVBV5)
-p, --parse-other-nit Parse the other NIT/SDT tables
-S, --sat_number=satellite_number
satellite number. If not specified, disable DISEqC

-T, --timeout-multiply=factor Multiply scan timeouts by this factor
-U, --freq_bpf=frequency SCR/Unicable band-pass filter frequency to use, in
kHz
-v, --verbose be (very) verbose
-W, --wait=time adds aditional wait time for DISEqC command
completion

Mandatory or optional arguments to long options are also mandatory or optional
for any corresponding short options.

Report bugs to Mauro Carvalho Chehab <mchehab@redhat.com>.
</pre>

== Examples ==

example channel list:
<pre>
[CHANNEL]
DELIVERY_SYSTEM = DVBC/ANNEX_A
FREQUENCY = 113000000
SYMBOL_RATE = 6900000
INNER_FEC = NONE
MODULATION = QAM/64
INVERSION = AUTO

[CHANNEL]
DELIVERY_SYSTEM = DVBC/ANNEX_A
FREQUENCY = 121000000
SYMBOL_RATE = 6900000
INNER_FEC = NONE
MODULATION = QAM/64
INVERSION = AUTO

[CHANNEL]
DELIVERY_SYSTEM = DVBC/ANNEX_A
FREQUENCY = 130000000
SYMBOL_RATE = 6900000
INNER_FEC = NONE
MODULATION = QAM/256
INVERSION = AUTO

[CHANNEL]
DELIVERY_SYSTEM = DVBC/ANNEX_A
FREQUENCY = 330000000
SYMBOL_RATE = 6900000
INNER_FEC = NONE
MODULATION = QAM/256
INVERSION = AUTO

[CHANNEL]
DELIVERY_SYSTEM = DVBC/ANNEX_A
FREQUENCY = 338000000
SYMBOL_RATE = 6900000
INNER_FEC = NONE
MODULATION = QAM/256
INVERSION = AUTO

[CHANNEL]
DELIVERY_SYSTEM = DVBC/ANNEX_A
FREQUENCY = 346000000
SYMBOL_RATE = 6900000
INNER_FEC = NONE
MODULATION = QAM/256
INVERSION = AUTO
</pre>

example service list:
<pre>
[Das Erste]
SERVICE_ID = 28106
VIDEO_PID = 101
AUDIO_PID = 102 103 106
PID_0b = 2171
PID_06 = 105 104 84
PID_05 = 2070
FREQUENCY = 113000000
MODULATION = QAM/64
INVERSION = OFF
SYMBOL_RATE = 6900000
INNER_FEC = NONE
DELIVERY_SYSTEM = DVBC/ANNEX_A

[Bayerisches FS Süd]
SERVICE_ID = 28107
VIDEO_PID = 201
AUDIO_PID = 202 203 206
PID_0b = 2171
PID_06 = 204
PID_05 = 2178
FREQUENCY = 113000000
MODULATION = QAM/64
INVERSION = OFF
SYMBOL_RATE = 6900000
INNER_FEC = NONE
DELIVERY_SYSTEM = DVBC/ANNEX_A

[hr-fernsehen]
SERVICE_ID = 28108
VIDEO_PID = 301
AUDIO_PID = 302 303
PID_0b = 2171
PID_06 = 304
PID_05 = 2270
FREQUENCY = 113000000
MODULATION = QAM/64
INVERSION = OFF
SYMBOL_RATE = 6900000
INNER_FEC = NONE
DELIVERY_SYSTEM = DVBC/ANNEX_A

[Bayerisches FS Nord]
SERVICE_ID = 28110
VIDEO_PID = 201
AUDIO_PID = 202 203 206
PID_0b = 2171
PID_06 = 204
PID_05 = 2178
FREQUENCY = 113000000
MODULATION = QAM/64
INVERSION = OFF
SYMBOL_RATE = 6900000
INNER_FEC = NONE
DELIVERY_SYSTEM = DVBC/ANNEX_A

[WDR Köln]
SERVICE_ID = 28111
VIDEO_PID = 601
AUDIO_PID = 602 603
PID_0b = 2171
PID_06 = 604
PID_05 = 2370
FREQUENCY = 113000000
MODULATION = QAM/64
INVERSION = OFF
SYMBOL_RATE = 6900000
INNER_FEC = NONE
DELIVERY_SYSTEM = DVBC/ANNEX_A

[Planet HD]
SERVICE_ID = 50003
VIDEO_PID = 6821
AUDIO_PID = 6822
FREQUENCY = 130000000
MODULATION = QAM/256
INVERSION = OFF
SYMBOL_RATE = 6900000
INNER_FEC = NONE
DELIVERY_SYSTEM = DVBC/ANNEX_A

[13th Street HD]
SERVICE_ID = 50004
VIDEO_PID = 6831
AUDIO_PID = 6832 6833
FREQUENCY = 130000000
MODULATION = QAM/256
INVERSION = OFF
SYMBOL_RATE = 6900000
INNER_FEC = NONE
DELIVERY_SYSTEM = DVBC/ANNEX_A

[ProSieben HD]
SERVICE_ID = 50015
VIDEO_PID = 6841
AUDIO_PID = 6842
PID_06 = 6844
FREQUENCY = 130000000
MODULATION = QAM/256
INVERSION = OFF
SYMBOL_RATE = 6900000
INNER_FEC = NONE
DELIVERY_SYSTEM = DVBC/ANNEX_A
</pre>

==Also See==
* [[Frequency_scan#Comparison_of_DVB_frequency_scanning_commandline_utilities|Comparison of the scanning utilities]]

[[Category:Apps & Utilities]]

Testing your DVB device

2012-09-09T20:05:10Z

CityK: /* Using dvb-apps */ minor edits

This page provides a few suggestions on how to test that a properly installed DVB device '''1''' is functioning correctly. The command line steps described are also indispensable for quick setup and no frills viewing with DVB hardware under Linux.

{{Note|'''1''' In other words, this article assumes that you have already both:
:* physically installed the device into, or attached it to, your system (refer to the manufacturer's instructions for such details) and
:* installed the drivers for your hardware and have the proper modules loaded (see "[[How to Obtain, Build and Install V4L-DVB Device Drivers]]" for such details) 
:Having completed such tasks, you should at least now have a ''/dev/dvb/adapter0/'' directory. (If you have additional DVB devices installed in your system, they will be assigned an increased ''adapter'' number accordingly).}} 

== Comparison of DTV testing applications ==

The following table lists the main features of the different command line DTV testing utilities. For specific information on usage, have a look at its specific wiki article.
 

{| border=1 cellpadding=10 cellspacing=0 valign="top"
|- bgcolor=#efefef valign="top"
|'''feature \ utility'''
|'''dvb-apps [[zap]]'''
|'''[[Szap-s2]]'''
|'''[[dvbtune]]''' and '''[[dvbstream]]''' from dvbtools
|'''[[dvbsnoop]]'''
|-
|'''download'''
|[http://linuxtv.org/hg/dvb-apps linuxtv.org/hg/dvb-apps]
|[http://mercurial.intuxication.org/hg/szap-s2 http://mercurial.intuxication.org/hg/szap-s2]
|[http://sourceforge.net/projects/dvbtools http://sourceforge.net/projects/dvbtools]
|[http://dvbsnoop.sourceforge.net http://dvbsnoop.sourceforge.net]
|-
|'''supported delivery systems'''
|DVB-S, DVB-C, DVB-T, ATSC
|DVB-S, DVB-S2
|DVB-S, DVB-C, DVB-T
|DVB-S, DVB-C, DVB-T
|-
|'''comments'''
|useful for debugging, but inappropriate for newer delivery systems.
|satellite only.
|outdated.
|outdated, but still the most powerful tool for reading and parsing DVB tables. Hint: use another tool to tune and dvbsnoop in parallel to read data. Unfortunally, dvbsnoop misses support for newer descriptors.
|-
|'''supported features'''
|
* channel scan for legacy systems
* tuning
* streaming
* show signal strength/lock
|
* tuning
|
* tuning (dvbtune)
* streaming (dvbstream)
|
* analyse DVB tables and MPEG streams
* show signal strength/lock
|}

== Using dvb-apps ==

'''1. Obtain the dvb-apps package''' 
See the [[LinuxTV dvb-apps]] article for details on how to obtain the package. The dvb-apps package contains several useful tools.

'''2. Scan for the channels you can receive''' 
Refer to the [[Scan|(dvb)scan]] article for details of how to perform this step. Once familiar with the content of that article, you will recognize that this step can be summarized (in general form) by:
mkdir ~/.''{a,c,s,t}''zap
(dvb)scan /''path_to_the_initial_scan_file'' > ~/.''{a,c,s,t}''zap/channels.conf

Note that you may have both a program <code>scan</code> and <code>dvbscan</code> installed on your system, and only one of them may work.

'''3. Tune a frequency and program''' 
Refer to the [[Zap|zap]] article for details of how to perform this step. Once familiar with the content of that article, you will recognize that this step can be summarized (in general form) by:
$ /usr/bin/''{a,c,s,t}''zap -r -c ~/.''{a,c,s,t}''zap/channels.conf "''channel name''"
where, respective to the type of transmission, [[azap]] is used for [[ATSC]], [[czap]] for [[DVB-C]], [[szap]] for [[DVB-S]] and [[tzap]] for [[DVB-T]].
Make sure you do not overlook the -r option for setting up the /dev/dvb/adapterX/dvr0 interface. Otherwise, you cannot record data from dvr0.

{{Note|If (dvb)scan was unable to correctly resolve the audio or video [[PID]] values for a channel in the previous step, a manual adjustment to the channels.conf file will be necessary to correct any inaccurately written PID(s) information. Such occurrences tend to be rare, but nonetheless, they do happen -- often, one only becomes aware of a problem with the PID values after unsuccessful attempts to tune a particular channel. The correct values may be determined using using [[dvbtraffic]] (see step '''4.c)''' below). Another method for finding correct PID values for a channel is also outlined in the section entitled "[[Scan#A_word_about_dvbscan_and_audio_streams|A word about dvbscan and audio streams]]".}}

'''4. After you've tuned a frequency and program''' 

'''a)''' You could now start up your simple TV watching application and decode the stream you have tuned.

For example, while keeping ''{a,c,s,t}''zap running in the first console shell, open up another console and run
mplayer /dev/dvb/adapter0/dvr0 <options>
If you have more than one dvb device installed in your system, then you will have to pass the correct ''adaptor'' number. See the [[MPlayer#Usage_with_more_complex_DVB_device_configurations|MPlayer article]] for some further information, as well as the MPlayer man page (i.e. in a console run "man mplayer") for a lengthy list of options.

'''b)''' Or, you could now start up a datastreamer

'''c)''' Or, alternatively, you may want to see some statistics of what's coming in for each channel and PID.
Example:
$ /usr/bin/dvbtraffic

dvbtraffic which will access the [[Device nodes and character devices#DVB character devices|/dev/dvb/adapter0/dvr0 logical device]].
An example of output from dvbtraffic is:

0000 24 p/s 4 kb/s 37 kbit
0010 20 p/s 3 kb/s 31 kbit
0011 20 p/s 3 kb/s 31 kbit
0012 70 p/s 12 kb/s 106 kbit
0015 1 p/s 0 kb/s 2 kbit
0080 26 p/s 4 kb/s 40 kbit
0082 26 p/s 4 kb/s 40 kbit
0087 25 p/s 4 kb/s 38 kbit
0100 25 p/s 4 kb/s 38 kbit
0101 25 p/s 4 kb/s 38 kbit
0102 24 p/s 4 kb/s 37 kbit
0200 8567 p/s 1572 kb/s 12885 kbit <--- 
0201 4708 p/s 864 kb/s 7081 kbit
0205 926 p/s 170 kb/s 1392 kbit
0240 49 p/s 8 kb/s 75 kbit
0241 49 p/s 8 kb/s 75 kbit
028b 261 p/s 47 kb/s 393 kbit <--- 
0294 174 p/s 31 kb/s 262 kbit
0295 130 p/s 23 kb/s 196 kbit
02bc 75 p/s 13 kb/s 113 kbit
1fff 87 p/s 15 kb/s 131 kbit
2000 15329 p/s 2814 kb/s 23055 kbit
-PID--FREQ-----BANDWIDTH-BANDWIDTH-

In this case, for the frequency that has been tuned, PID 0x0200 is for the video stream of an HDTV channel and PID 0x028b is for the associated audio stream (both of these have been highlighted in red in the above output for easier visual identification). These PID values presented by dvbtraffuc are in hexadecimal form and need to be converted to their decimal representation (respectively, 512 and 651) for use in a channel.conf file. 

This is the line you would create in the file "channel.conf" given the PID values from the dvbtraffic output shown above:

Nine High Def Gold Coast:746625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:512:651:1138

And finally
dvbdate

== Using dvbsnoop ==
If the testing steps in the dvb-apps section above work fine, you can jump over this section here. On the other hand, [[dvbsnoop]] is a small, down-to-earth utility that is very handy for debugging and also seeing what is occuring with a dvb device (i.e. tuning works? data coming in? signal strong enough?).

'''1. Obtain the dvbsnoop package''' 
See the [[dvbsnoop]] article for details on how to obtain the package.

'''2. Testing with dvbsnoop''' 
Try things like
dvbsnoop -help
dvbsnoop -s pidscan
This will give out a lot of numbers, but if you understand the system of [[DVB]] you should see if they make sense. Go for one of the PIDs (choose a right one which is a bit difficult as you don't know what they stand for unless you used the scan line above) and try:
dvbsnoop -s bandwidth <PID>
dvbsnoop <PID>
The latter will spit out a lot of hexdumps - at least you receive '''something''' ;-)

== Save a TV program to your hard drive ==
The handy thing about digital TV is, it comes in as a digital stream that you can save right away to your harddisk without any changes necessary to it. Therefore, hardly any CPU resources are needed -- just a lot of HD space (few GB per hour as the stream is MPEG-2 which is not as compressed as, for example, DivX/MPEG-4; it's even more as mostly one [[transport stream]] contains multiple [[PID]]s). There are several ways to do this. For example:

'''a) Using the combination of {a,c,s,t}zap and cat'ing the logical dvr device to save a program stream to disk''' 
If you have a channel tuned with {a,c,s,t}zap (and note that you MUST also be using the -r parameter to set up the logical dvr device in order for the following to work; see [[Zap]] for detail), open up another shell console and run (as root user):
cat /dev/dvb/adapter0/dvr0 > <filename>
The result is that particular program stream will be written to disk, and you should be able to play it back at any later time with your favourite media player.

'''b) Using the combination of {a,c,s,t}zap and test_dvr to save an entire transport stream to disk'''

'''c) Saving to disk with dvbstream''' 
[[dvbstream]] is a useful program that, amongst other things, can save a DVB stream to disk.
'''Method 1''': First tune into a channel, as described above in the zapping step, and then next have dvbstream save a particular stream to file. For example:
tzap 'BBC ONE'
dvbstream 600 601 -o > bbc1.mpeg
The values "600 and 601" are, respectively, the video and audio [[PID]]s for the channel BBC ONE, as derived from the channels.conf file. So this is why it's important that you have your personal channels.conf file with all the PIDs so you can look them up.

'''Method 2''': Alternatively, instead of using a combination of *zap and dvbstream, you can use dvbstream alone provided you pass which frequency to tune and list the correct PIDs. For example:
dvbstream -f 578000 600 601 -o >bbc1.mpeg

Wait a few seconds and then press Ctrl+C to stop. You should then be able to open/playback the recorded file with any of your favourite media players (like Mplayer, (g)xine, noatune, etc. etc ) provided you have the correct decoders installed on your system (which, in general regards to DVB transmissions, are usually going to be MPEG-2, but can now also be MPEG-4).

If the file is rather small, e.g. smaller than 1 MB after a minute of recording, then you can't receive this TV channel - maybe the reception is bad (too weak antenna signal) - or maybe your card's frequency is not tuned for the right sender? Watch out, some PIDs come up a few times (but for different frequencies).

This might not be what you wanna do every day (unless you only watch BBC1 or you can easily memorise all your channels with their two PIDs) - but it's very fast and easy to do these steps for testing purposes.

==Next steps - More feature rich viewing software ==
It is not the intention of this page to provide a detailed description of the use of DVB hardware with more complex Linux viewing software applications. Suffice it to say that you will have some choice. For example:
* for light TV watching with a DVB device under Linux, [[MPlayer]], [[Xine]], [[Kaffeine]], [[Klear]] and a few others are often selected.
* alternatively, for "Media Center" type applications, the usual first suspects are [[Freevo]], [[MythTV]], and [[VDR]], but there are others as well
* you could use the streaming facilities of [[dvbstream]] and then watch the MPEG-2 stream (even possible on a different computer) with programs like Xine, MPlayer etc.

For some further inspiration on what's possible with more advanced software usage see:
* the [[TV Related Software]] page, a commented software list, and
* [[Example setups]]

---------

(note: you'll need to install the [[VDR Software Decoder Plugin]] if you want to use VDR for watching with a software decoding card).

* Digital Video Broadcasting – A practical guide by Hugo Mills [http://www.carfax.org.uk/docs/DVB/]
[[Category:Drivers]]
[[Category:Software]]

MPlayer

2012-09-09T19:58:27Z

CityK: /* Watching DVB Streams */ minor edits

The Linux video "Swiss Army knife", which plays almost every movie format imaginable [http://www.mplayerhq.hu/design7/info.html].

:''The player is rock solid playing damaged MPEG files (useful for some VCDs), and it plays bad AVI files which are unplayable with the famous windows media player. Even AVI files without index chunk are playable, and you can temporarily rebuild their indexes with the -idx option, or permanently with MEncoder, thus enabling seeking! As you see, stability and quality are the most important things, but the speed is also amazing. There is also a powerful filter system for video and audio manipulation.'' [http://www.mplayerhq.hu/DOCS/HTML/en/intro.html]

In addition, MPlayer can also serve as:
* a TV viewer application for both analogue TV or DVB.
* a Radio listening application
* a [[Webcam]] viewing application

==Using MPlayer to Watch TV==

=== Useful MPlayer Global Keyboard Hotkeys When Watching TV===
These are global settings applicable for either analogue or DVB.

You can change the channel and control the volume with those keys:
{| border="1" cellpadding="2"
!width="100"|Keys
!width="200"|Meaning
|-
| / and * || Decrease/increase volume
|-
| 9 and 0 || Decrease/increase volume
|-
| m || Mute sound
|-
| h and k || Select previous/next channel
|}

For more info about MPlayer command line parameters and other control keys, please read the [http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html MPlayer man page]

=== Watching Analogue TV===
A sample MPlayer command line that will play TV for Europe, channel E2, for devices that use analog audio wired from the TV card audio output into the aux or cd audio input on the motherboard or on the audio card:

mplayer tv:// -tv driver=v4l2:norm=PAL:input=0:amode=1:width=384:height=288:outfmt=yv12:device=/dev/video0:chanlist=europe-west:channel=E2

If your board provides a digital audio input, don't forget to load the alsa module for it. In this case, you'll need to teach mplayer to read the audio stream as well. This is an example of using mplayer for viewing TV on a NTSC video stream, reading also the audio stream:

mplayer -tv driver=v4l2:device=/dev/video0:norm=NTSC:chanlist=us-bcast:channel=10:alsa=1:adevice=hw.1:audiorate=48000:immediatemode=0:amode=1 tv://

In this case, it is assumed that the -alsa module created as the second audio adapter (hw:1), and supports an audio rate of 48 kHz. There are more useful information about audio setups with alsa modules on [[Saa7134-alsa]].

To avoid having to specify all the above parameters, it is recommended to write them to the ~/.mplayer/config:
zoom = yes
vo = x11
tv = "driver=v4l2:device=/dev/video0:norm=NTSC:chanlist=us-bcast:channel=10:alsa=1:adevice=hw.1:audiorate=48000:immediatemode=0:amode=1"
monitoraspect = "16:9"

=== Watching DVB Streams ===
One method of using MPlayer to watch DVB streams is outlined in the [[Testing your DVB device]] article. However, it is a convoluted solution, and is much more suited for testing purposes rather then daily use. A much simpler and convenient method is outlined below.

{{Note|The following methods require that you configure a ''channels.conf'' file and store it in ''~/.mplayer'' (instructions on how to do this are detailed in the [[Testing your DVB device]] article) before you can actually use MPlayer to view or record DVB streams.}}

If you have a single DVB device, which itself has a single [[Frontend|frontend]](a usage case which will be true for most persons; See the section below for MPlayer [[MPlayer#Usage with more complex DVB device configurations|usage with more complex DVB device configurations]]), you can start watching DVB streams with MPlayer simply by typing:

$ mplayer dvb://

That command will result in your DVB device receiving the first channel listed in your channels.conf and displaying that stream's contents in MPlayer. You can then move forward through your channel list by pressing h (next) on your keyboard. Conversely, pressing k (previous) on your keyboard will move backwards through your channel list.

If you wish to open a specific DVB stream (as listed in the ''channels.conf'' file), type:

$ mplayer dvb://"STREAM NAME"

"STREAM NAME" is, of course, a generic descriptor and you will have to substitute the correct name accordingly (e.g. BBC, CBS, CBC, ....)
{{Note|Around the stream name you can use double parenthesis, single parenthesis, or none at all}}

Of course, for even better results, you may wish to run MPlayer with some options (<code>mplayer dvb:// <options></code>). For example, to utilise linear blend deinterlacing for display/playback, run:

$ mplayer dvb:// -vf pp=lb

You may have to force demuxer type for better results. For example, for a DVB-T device (all DVB devices?):

$ mplayer dvb:// -demuxer mpegts

See the MPlayer man page (i.e. in a console run "man mplayer") for a lengthy list of available options (an online version is found below in the links section).

====Usage with more complex DVB device configurations====
If you choose not to specify a device adapter and/or frontend, as was the case in the examples shown in the section above, then MPlayer will default to using <code>/dev/dvb/adapter0</code> and <code>/dev/dvb/adapter0/frontend0</code>. Alternatively, you can be very specific with MPlayer in terms of which hardware is to be used -- a point of interest to those:
* with multiple DVB device adapters in their system, or
* whose device adapter has multiple frontends, or
* who have multiple adapters and some, or even all, of which have multiple frontends!

If you have more than one DVB device adapter installed in your system you can specify the device to use by passing the device number in the command syntax. MPlayer uses device numbers of 1-4. For example:

$ mplayer dvb://"DEVICE NUMBER"@"STREAM NAME" <options>

Which will open the default frontend ("frontend0") on the adapter you specify.

Some device adapters also have multiple frontends. In which case, you can specify which frontend on the adapter to use by passing the frontend number along with the device adapter number. For example:
$ mplayer dvb://"DEVICE NUMBER":"FRONTEND NUMBER"@"STREAM NAME" <options>

Again, to avoid having to specify all the above parameters, it is recommended to write them to the ~/.mplayer/config file.

==== Limitations with DVB Streams ====
* Only free-to-air broadcasts are supported. Decryption through [[CAM]] is not implemented in MPlayer.
But you can use virtual interface such as sasc-ng or utilite ca_zap from dvb-apps/util:
cat ~/.mplayer/channels.conf:
#Eutelsat W4 36'
Sport 1:11727:h:0:27500:101:201:1
Sport 2:11727:h:0:27500:102:202:2
First Automotive:11727:h:0:27500:103:203:3
BIZ TV:11727:h:0:27500:105:205:5
RUTV:11727:h:0:27500:109:209:9
O2TV:11727:h:0:27500:110:210:10
RTVi:11727:h:0:27500:111:211:11

ca_zap -m -c ~/.mplayer/channels.conf -t sat -a 0 -n 'Sport 1'
mplayer dvb://'0@Sport 1'
* There is (presently) no DVB subtitle support in MPlayer.

==== Recording DVB Streams ====
If you want to record a DVB stream with MPlayer, you can use:

$ mplayer -dumpstream dvb://"STREAM NAME" -dumpfile stream.ts

This will dump the stream in MPEG-TS format to the file ''stream.ts'' ('''Note''' that this file can be very large - ~1GB for 30 minutes).

You can then use MPlayer or [[MEncoder]], a command-line encoder built on the MPlayer code, to convert that file to a usable video format.

There is even more functionality in [[MEncoder]] when it comes to recording streams.

==== MPlayer and Satellite Dishes ====
If you are using MPlayer with a satellite dish that has a C-Band lnb LO: 5150 or standard Ku Band lnb LO: 10750 such as are commonly used in North America, MPlayer will tune the channel if you use the L Band frequency in your .mplayer/channels.conf file instead of the C or Ku Band frequency. To calculate the L Band frequency for C Band, 5150 minus frequency in Mhz equals L Band frequency in Mhz. For Ku Band, frequency in Mhz minus 10750 equals L Band frequency in Mhz.

For example to tune C Band 4.060 Ghz

5150 - 4060 = 1090

Use 1090 for the frequency in channels.conf instead of 4060.

For Ku Band 11.799 Ghz

11799 - 10750 = 1049

==Using MPlayer for Radio Listening==
You can do a lot of things with MPlayer. An example of commandline syntax used for radio listening is:

mplayer -rawaudio rate=48000 radio://2/capture -radio adevice=hw=2:arate=48000:channels=93.8-Radio_Zones,94.7-SSR_1

Note that this command will work even without audio cable between the output of the radio card and a line input of the audio card.

This will start MPlayer with sample rate = 48 kHz (using the same sample rate that the sound card is using gives best results), listening to the second station on the list, the tuner is the third sound card (ALSA device hw:2). For more examples and syntax: [http://www.mplayerhq.hu/DOCS/HTML/en/radio-input.html#radio-tips MPlayer radio tips].

You can add as many stations as wanted and use LIRC to control MPlayer.

If you are, say, running JACK all the time, you can add
ao=jack,alsa
into ~.mplayer/config (for MPlayer) and mplayerplug-in.conf (for Firefox mplayerplug-in). For recording, you can use any JACK aware recording application.

A XDialog wrapper can be made for radio listening using MPlayer and v4l2-ctl. The authour found that it was so good that they decided to make it public under the name [http://slashdot.org/firehose.pl?op=view&id=5214989 XDRadio]. You will have to make a list of your stations during the installation (very easy to do). After that, all that is required is to just to run it and enjoy the radio.

==Using MPlayer for Webcam Viewing==
Can be used to view webcam video by invoking 'mplayer tv://'.

==High Quality Video Playback==

MPlayer will play almost anything with the default settings, but with careful selection of the command line parameters (i.e. test samples, trial-and-error and patience) it is possible to achieve very high quality video playback. When you are satisfied with the results provided by certain parameters, you can add them to the ~.mplayer/config file so that they are used persistently and don't have to be manually passed to the application. Type "man mplayer" for a detailed listing of available options. Pay particular attention to:

* Video Output Driver (-vo option)
** xv is reliable
** vdpau may be useful if you have an nvidia card (and not enough CPU)
* Deinterlacing
** See http://guru.multimedia.cx/deinterlacing-filters/
** -vf yadif=1 is good, doubles the frame rate to preserve information (at the cost of CPU)
* Upscaling
** -vf scale with -sws 9 is very good (at the cost of CPU)
* Buffering
* Vertical sync (check for tearing artefacts in the video)
** check video card options, desktop compositing, OpenGL
** video card frame rate should equal (or be a multiple of) video frame rate
* Audio sync
** -delay option
* Screensaver
** ensure it is disabled when playing video and reenabled afterwards
* Resolutions
** you will probably need different settings for SD and HD
* Smoothness
** check news tickers for smooth flow and readability

== Also See==
*[[BBC HD]] (Patches and Info for Watching BBC HD on Astra 28.8e)

== External Links ==
* [http://www.mplayerhq.hu MPlayer Home page]
* [http://www.mplayerhq.hu/DOCS/HTML/en/index.html MPlayer documentation]
* [http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html MPlayer man page (online version)]

[[Category:Software]]
[[Category:Apps & Utilities]]

MPlayer

2012-09-09T19:56:50Z

CityK: /* Usage with more complex DVB device configurations */ minor edit

The Linux video "Swiss Army knife", which plays almost every movie format imaginable [http://www.mplayerhq.hu/design7/info.html].

:''The player is rock solid playing damaged MPEG files (useful for some VCDs), and it plays bad AVI files which are unplayable with the famous windows media player. Even AVI files without index chunk are playable, and you can temporarily rebuild their indexes with the -idx option, or permanently with MEncoder, thus enabling seeking! As you see, stability and quality are the most important things, but the speed is also amazing. There is also a powerful filter system for video and audio manipulation.'' [http://www.mplayerhq.hu/DOCS/HTML/en/intro.html]

In addition, MPlayer can also serve as:
* a TV viewer application for both analogue TV or DVB.
* a Radio listening application
* a [[Webcam]] viewing application

==Using MPlayer to Watch TV==

=== Useful MPlayer Global Keyboard Hotkeys When Watching TV===
These are global settings applicable for either analogue or DVB.

You can change the channel and control the volume with those keys:
{| border="1" cellpadding="2"
!width="100"|Keys
!width="200"|Meaning
|-
| / and * || Decrease/increase volume
|-
| 9 and 0 || Decrease/increase volume
|-
| m || Mute sound
|-
| h and k || Select previous/next channel
|}

For more info about MPlayer command line parameters and other control keys, please read the [http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html MPlayer man page]

=== Watching Analogue TV===
A sample MPlayer command line that will play TV for Europe, channel E2, for devices that use analog audio wired from the TV card audio output into the aux or cd audio input on the motherboard or on the audio card:

mplayer tv:// -tv driver=v4l2:norm=PAL:input=0:amode=1:width=384:height=288:outfmt=yv12:device=/dev/video0:chanlist=europe-west:channel=E2

If your board provides a digital audio input, don't forget to load the alsa module for it. In this case, you'll need to teach mplayer to read the audio stream as well. This is an example of using mplayer for viewing TV on a NTSC video stream, reading also the audio stream:

mplayer -tv driver=v4l2:device=/dev/video0:norm=NTSC:chanlist=us-bcast:channel=10:alsa=1:adevice=hw.1:audiorate=48000:immediatemode=0:amode=1 tv://

In this case, it is assumed that the -alsa module created as the second audio adapter (hw:1), and supports an audio rate of 48 kHz. There are more useful information about audio setups with alsa modules on [[Saa7134-alsa]].

To avoid having to specify all the above parameters, it is recommended to write them to the ~/.mplayer/config:
zoom = yes
vo = x11
tv = "driver=v4l2:device=/dev/video0:norm=NTSC:chanlist=us-bcast:channel=10:alsa=1:adevice=hw.1:audiorate=48000:immediatemode=0:amode=1"
monitoraspect = "16:9"

=== Watching DVB Streams ===
One method of using MPlayer to watch DVB streams is outlined in the [[Testing your DVB device]] article. However, it is a convoluted solution, and is much more suited for testing purposes rather then daily use. A much simpler and convenient method is outlined below.

{{Note|The following methods require that you configure a ''channels.conf'' file and store it in ''~/.mplayer'' (instructions on how to do this are detailed in the [[Testing your DVB device]] article) before you can actually use MPlayer to view or record DVB streams.}}

If you have a single DVB device, which itself has a single [[Frontend|frontend]](a usage case which will be true for most persons; See, the section below for MPlayer [[MPlayer#Watching_DVB_Streams#Usage with more complex DVB device configurations|usage with more complex DVB device configurations]]), you can start watching DVB streams with MPlayer simply by typing:

$ mplayer dvb://

That command will result in your DVB device receiving the first channel listed in your channels.conf and displaying that stream's contents in MPlayer. You can then move forward through your channel list by pressing h (next) on your keyboard. Conversely, pressing k (previous) on your keyboard will move backwards through your channel list.

If you wish to open a specific DVB stream (as listed in the ''channels.conf'' file), type:

$ mplayer dvb://"STREAM NAME"

"STREAM NAME" is, of course, a generic descriptor and you will have to substitute the correct name accordingly (e.g. BBC, CBS, CBC, ....)
{{Note|Around the stream name you can use double parenthesis, single parenthesis, or none at all}}

Of course, for even better results, you may wish to run MPlayer with some options (<code>mplayer dvb:// <options></code>). For example, to utilise linear blend deinterlacing for display/playback, run:

$ mplayer dvb:// -vf pp=lb

You may have to force demuxer type for better results. For example, for a DVB-T device (all DVB devices?):

$ mplayer dvb:// -demuxer mpegts

See the MPlayer man page (i.e. in a console run "man mplayer") for a lengthy list of available options (an online version is found below in the links section).

====Usage with more complex DVB device configurations====
If you choose not to specify a device adapter and/or frontend, as was the case in the examples shown in the section above, then MPlayer will default to using <code>/dev/dvb/adapter0</code> and <code>/dev/dvb/adapter0/frontend0</code>. Alternatively, you can be very specific with MPlayer in terms of which hardware is to be used -- a point of interest to those:
* with multiple DVB device adapters in their system, or
* whose device adapter has multiple frontends, or
* who have multiple adapters and some, or even all, of which have multiple frontends!

If you have more than one DVB device adapter installed in your system you can specify the device to use by passing the device number in the command syntax. MPlayer uses device numbers of 1-4. For example:

$ mplayer dvb://"DEVICE NUMBER"@"STREAM NAME" <options>

Which will open the default frontend ("frontend0") on the adapter you specify.

Some device adapters also have multiple frontends. In which case, you can specify which frontend on the adapter to use by passing the frontend number along with the device adapter number. For example:
$ mplayer dvb://"DEVICE NUMBER":"FRONTEND NUMBER"@"STREAM NAME" <options>

Again, to avoid having to specify all the above parameters, it is recommended to write them to the ~/.mplayer/config file.

==== Limitations with DVB Streams ====
* Only free-to-air broadcasts are supported. Decryption through [[CAM]] is not implemented in MPlayer.
But you can use virtual interface such as sasc-ng or utilite ca_zap from dvb-apps/util:
cat ~/.mplayer/channels.conf:
#Eutelsat W4 36'
Sport 1:11727:h:0:27500:101:201:1
Sport 2:11727:h:0:27500:102:202:2
First Automotive:11727:h:0:27500:103:203:3
BIZ TV:11727:h:0:27500:105:205:5
RUTV:11727:h:0:27500:109:209:9
O2TV:11727:h:0:27500:110:210:10
RTVi:11727:h:0:27500:111:211:11

ca_zap -m -c ~/.mplayer/channels.conf -t sat -a 0 -n 'Sport 1'
mplayer dvb://'0@Sport 1'
* There is (presently) no DVB subtitle support in MPlayer.

==== Recording DVB Streams ====
If you want to record a DVB stream with MPlayer, you can use:

$ mplayer -dumpstream dvb://"STREAM NAME" -dumpfile stream.ts

This will dump the stream in MPEG-TS format to the file ''stream.ts'' ('''Note''' that this file can be very large - ~1GB for 30 minutes).

You can then use MPlayer or [[MEncoder]], a command-line encoder built on the MPlayer code, to convert that file to a usable video format.

There is even more functionality in [[MEncoder]] when it comes to recording streams.

==== MPlayer and Satellite Dishes ====
If you are using MPlayer with a satellite dish that has a C-Band lnb LO: 5150 or standard Ku Band lnb LO: 10750 such as are commonly used in North America, MPlayer will tune the channel if you use the L Band frequency in your .mplayer/channels.conf file instead of the C or Ku Band frequency. To calculate the L Band frequency for C Band, 5150 minus frequency in Mhz equals L Band frequency in Mhz. For Ku Band, frequency in Mhz minus 10750 equals L Band frequency in Mhz.

For example to tune C Band 4.060 Ghz

5150 - 4060 = 1090

Use 1090 for the frequency in channels.conf instead of 4060.

For Ku Band 11.799 Ghz

11799 - 10750 = 1049

==Using MPlayer for Radio Listening==
You can do a lot of things with MPlayer. An example of commandline syntax used for radio listening is:

mplayer -rawaudio rate=48000 radio://2/capture -radio adevice=hw=2:arate=48000:channels=93.8-Radio_Zones,94.7-SSR_1

Note that this command will work even without audio cable between the output of the radio card and a line input of the audio card.

This will start MPlayer with sample rate = 48 kHz (using the same sample rate that the sound card is using gives best results), listening to the second station on the list, the tuner is the third sound card (ALSA device hw:2). For more examples and syntax: [http://www.mplayerhq.hu/DOCS/HTML/en/radio-input.html#radio-tips MPlayer radio tips].

You can add as many stations as wanted and use LIRC to control MPlayer.

If you are, say, running JACK all the time, you can add
ao=jack,alsa
into ~.mplayer/config (for MPlayer) and mplayerplug-in.conf (for Firefox mplayerplug-in). For recording, you can use any JACK aware recording application.

A XDialog wrapper can be made for radio listening using MPlayer and v4l2-ctl. The authour found that it was so good that they decided to make it public under the name [http://slashdot.org/firehose.pl?op=view&id=5214989 XDRadio]. You will have to make a list of your stations during the installation (very easy to do). After that, all that is required is to just to run it and enjoy the radio.

==Using MPlayer for Webcam Viewing==
Can be used to view webcam video by invoking 'mplayer tv://'.

==High Quality Video Playback==

MPlayer will play almost anything with the default settings, but with careful selection of the command line parameters (i.e. test samples, trial-and-error and patience) it is possible to achieve very high quality video playback. When you are satisfied with the results provided by certain parameters, you can add them to the ~.mplayer/config file so that they are used persistently and don't have to be manually passed to the application. Type "man mplayer" for a detailed listing of available options. Pay particular attention to:

* Video Output Driver (-vo option)
** xv is reliable
** vdpau may be useful if you have an nvidia card (and not enough CPU)
* Deinterlacing
** See http://guru.multimedia.cx/deinterlacing-filters/
** -vf yadif=1 is good, doubles the frame rate to preserve information (at the cost of CPU)
* Upscaling
** -vf scale with -sws 9 is very good (at the cost of CPU)
* Buffering
* Vertical sync (check for tearing artefacts in the video)
** check video card options, desktop compositing, OpenGL
** video card frame rate should equal (or be a multiple of) video frame rate
* Audio sync
** -delay option
* Screensaver
** ensure it is disabled when playing video and reenabled afterwards
* Resolutions
** you will probably need different settings for SD and HD
* Smoothness
** check news tickers for smooth flow and readability

== Also See==
*[[BBC HD]] (Patches and Info for Watching BBC HD on Astra 28.8e)

== External Links ==
* [http://www.mplayerhq.hu MPlayer Home page]
* [http://www.mplayerhq.hu/DOCS/HTML/en/index.html MPlayer documentation]
* [http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html MPlayer man page (online version)]

[[Category:Software]]
[[Category:Apps & Utilities]]

MPlayer

2012-09-09T19:51:44Z

CityK: /* Watching DVB Streams */ some edits

The Linux video "Swiss Army knife", which plays almost every movie format imaginable [http://www.mplayerhq.hu/design7/info.html].

:''The player is rock solid playing damaged MPEG files (useful for some VCDs), and it plays bad AVI files which are unplayable with the famous windows media player. Even AVI files without index chunk are playable, and you can temporarily rebuild their indexes with the -idx option, or permanently with MEncoder, thus enabling seeking! As you see, stability and quality are the most important things, but the speed is also amazing. There is also a powerful filter system for video and audio manipulation.'' [http://www.mplayerhq.hu/DOCS/HTML/en/intro.html]

In addition, MPlayer can also serve as:
* a TV viewer application for both analogue TV or DVB.
* a Radio listening application
* a [[Webcam]] viewing application

==Using MPlayer to Watch TV==

=== Useful MPlayer Global Keyboard Hotkeys When Watching TV===
These are global settings applicable for either analogue or DVB.

You can change the channel and control the volume with those keys:
{| border="1" cellpadding="2"
!width="100"|Keys
!width="200"|Meaning
|-
| / and * || Decrease/increase volume
|-
| 9 and 0 || Decrease/increase volume
|-
| m || Mute sound
|-
| h and k || Select previous/next channel
|}

For more info about MPlayer command line parameters and other control keys, please read the [http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html MPlayer man page]

=== Watching Analogue TV===
A sample MPlayer command line that will play TV for Europe, channel E2, for devices that use analog audio wired from the TV card audio output into the aux or cd audio input on the motherboard or on the audio card:

mplayer tv:// -tv driver=v4l2:norm=PAL:input=0:amode=1:width=384:height=288:outfmt=yv12:device=/dev/video0:chanlist=europe-west:channel=E2

If your board provides a digital audio input, don't forget to load the alsa module for it. In this case, you'll need to teach mplayer to read the audio stream as well. This is an example of using mplayer for viewing TV on a NTSC video stream, reading also the audio stream:

mplayer -tv driver=v4l2:device=/dev/video0:norm=NTSC:chanlist=us-bcast:channel=10:alsa=1:adevice=hw.1:audiorate=48000:immediatemode=0:amode=1 tv://

In this case, it is assumed that the -alsa module created as the second audio adapter (hw:1), and supports an audio rate of 48 kHz. There are more useful information about audio setups with alsa modules on [[Saa7134-alsa]].

To avoid having to specify all the above parameters, it is recommended to write them to the ~/.mplayer/config:
zoom = yes
vo = x11
tv = "driver=v4l2:device=/dev/video0:norm=NTSC:chanlist=us-bcast:channel=10:alsa=1:adevice=hw.1:audiorate=48000:immediatemode=0:amode=1"
monitoraspect = "16:9"

=== Watching DVB Streams ===
One method of using MPlayer to watch DVB streams is outlined in the [[Testing your DVB device]] article. However, it is a convoluted solution, and is much more suited for testing purposes rather then daily use. A much simpler and convenient method is outlined below.

{{Note|The following methods require that you configure a ''channels.conf'' file and store it in ''~/.mplayer'' (instructions on how to do this are detailed in the [[Testing your DVB device]] article) before you can actually use MPlayer to view or record DVB streams.}}

If you have a single DVB device, which itself has a single [[Frontend|frontend]](a usage case which will be true for most persons; See, the section below for MPlayer [[MPlayer#Watching_DVB_Streams#Usage with more complex DVB device configurations|usage with more complex DVB device configurations]]), you can start watching DVB streams with MPlayer simply by typing:

$ mplayer dvb://

That command will result in your DVB device receiving the first channel listed in your channels.conf and displaying that stream's contents in MPlayer. You can then move forward through your channel list by pressing h (next) on your keyboard. Conversely, pressing k (previous) on your keyboard will move backwards through your channel list.

If you wish to open a specific DVB stream (as listed in the ''channels.conf'' file), type:

$ mplayer dvb://"STREAM NAME"

"STREAM NAME" is, of course, a generic descriptor and you will have to substitute the correct name accordingly (e.g. BBC, CBS, CBC, ....)
{{Note|Around the stream name you can use double parenthesis, single parenthesis, or none at all}}

Of course, for even better results, you may wish to run MPlayer with some options (<code>mplayer dvb:// <options></code>). For example, to utilise linear blend deinterlacing for display/playback, run:

$ mplayer dvb:// -vf pp=lb

You may have to force demuxer type for better results. For example, for a DVB-T device (all DVB devices?):

$ mplayer dvb:// -demuxer mpegts

See the MPlayer man page (i.e. in a console run "man mplayer") for a lengthy list of available options (an online version is found below in the links section).

====Usage with more complex DVB device configurations====
If you choose not to specify a device adapter and/or frontend, as was the case in the examples shown in the section above, then MPlayer will default to using <code>/dev/dvb/adapter0</code> and <code>/dev/dvb/adapter0/frontend0</code>. Alternatively, you can be very specific with MPlayer in terms of which hardware is to be used -- a point of interest to those:
* with multiple DVB device adapters in their system, or
* whose device adapter has multiple frontends, or
* whom might even have multiple adapters and some, or all, of which have multiple frontends!

If you have more than one DVB device adapter installed in your system you can specify the device to use by passing the device number in the command syntax. MPlayer uses device numbers of 1-4. For example:

$ mplayer dvb://"DEVICE NUMBER"@"STREAM NAME" <options>

Which will open the default frontend ("frontend0") on the adapter you specify.

Some device adapters also have multiple frontends. In which case, you can specify which frontend on the adapter to use by passing the frontend number along with the device adapter number. For example:
$ mplayer dvb://"DEVICE NUMBER":"FRONTEND NUMBER"@"STREAM NAME" <options>

Again, to avoid having to specify all the above parameters, it is recommended to write them to the ~/.mplayer/config file.

==== Limitations with DVB Streams ====
* Only free-to-air broadcasts are supported. Decryption through [[CAM]] is not implemented in MPlayer.
But you can use virtual interface such as sasc-ng or utilite ca_zap from dvb-apps/util:
cat ~/.mplayer/channels.conf:
#Eutelsat W4 36'
Sport 1:11727:h:0:27500:101:201:1
Sport 2:11727:h:0:27500:102:202:2
First Automotive:11727:h:0:27500:103:203:3
BIZ TV:11727:h:0:27500:105:205:5
RUTV:11727:h:0:27500:109:209:9
O2TV:11727:h:0:27500:110:210:10
RTVi:11727:h:0:27500:111:211:11

ca_zap -m -c ~/.mplayer/channels.conf -t sat -a 0 -n 'Sport 1'
mplayer dvb://'0@Sport 1'
* There is (presently) no DVB subtitle support in MPlayer.

==== Recording DVB Streams ====
If you want to record a DVB stream with MPlayer, you can use:

$ mplayer -dumpstream dvb://"STREAM NAME" -dumpfile stream.ts

This will dump the stream in MPEG-TS format to the file ''stream.ts'' ('''Note''' that this file can be very large - ~1GB for 30 minutes).

You can then use MPlayer or [[MEncoder]], a command-line encoder built on the MPlayer code, to convert that file to a usable video format.

There is even more functionality in [[MEncoder]] when it comes to recording streams.

==== MPlayer and Satellite Dishes ====
If you are using MPlayer with a satellite dish that has a C-Band lnb LO: 5150 or standard Ku Band lnb LO: 10750 such as are commonly used in North America, MPlayer will tune the channel if you use the L Band frequency in your .mplayer/channels.conf file instead of the C or Ku Band frequency. To calculate the L Band frequency for C Band, 5150 minus frequency in Mhz equals L Band frequency in Mhz. For Ku Band, frequency in Mhz minus 10750 equals L Band frequency in Mhz.

For example to tune C Band 4.060 Ghz

5150 - 4060 = 1090

Use 1090 for the frequency in channels.conf instead of 4060.

For Ku Band 11.799 Ghz

11799 - 10750 = 1049

==Using MPlayer for Radio Listening==
You can do a lot of things with MPlayer. An example of commandline syntax used for radio listening is:

mplayer -rawaudio rate=48000 radio://2/capture -radio adevice=hw=2:arate=48000:channels=93.8-Radio_Zones,94.7-SSR_1

Note that this command will work even without audio cable between the output of the radio card and a line input of the audio card.

This will start MPlayer with sample rate = 48 kHz (using the same sample rate that the sound card is using gives best results), listening to the second station on the list, the tuner is the third sound card (ALSA device hw:2). For more examples and syntax: [http://www.mplayerhq.hu/DOCS/HTML/en/radio-input.html#radio-tips MPlayer radio tips].

You can add as many stations as wanted and use LIRC to control MPlayer.

If you are, say, running JACK all the time, you can add
ao=jack,alsa
into ~.mplayer/config (for MPlayer) and mplayerplug-in.conf (for Firefox mplayerplug-in). For recording, you can use any JACK aware recording application.

A XDialog wrapper can be made for radio listening using MPlayer and v4l2-ctl. The authour found that it was so good that they decided to make it public under the name [http://slashdot.org/firehose.pl?op=view&id=5214989 XDRadio]. You will have to make a list of your stations during the installation (very easy to do). After that, all that is required is to just to run it and enjoy the radio.

==Using MPlayer for Webcam Viewing==
Can be used to view webcam video by invoking 'mplayer tv://'.

==High Quality Video Playback==

MPlayer will play almost anything with the default settings, but with careful selection of the command line parameters (i.e. test samples, trial-and-error and patience) it is possible to achieve very high quality video playback. When you are satisfied with the results provided by certain parameters, you can add them to the ~.mplayer/config file so that they are used persistently and don't have to be manually passed to the application. Type "man mplayer" for a detailed listing of available options. Pay particular attention to:

* Video Output Driver (-vo option)
** xv is reliable
** vdpau may be useful if you have an nvidia card (and not enough CPU)
* Deinterlacing
** See http://guru.multimedia.cx/deinterlacing-filters/
** -vf yadif=1 is good, doubles the frame rate to preserve information (at the cost of CPU)
* Upscaling
** -vf scale with -sws 9 is very good (at the cost of CPU)
* Buffering
* Vertical sync (check for tearing artefacts in the video)
** check video card options, desktop compositing, OpenGL
** video card frame rate should equal (or be a multiple of) video frame rate
* Audio sync
** -delay option
* Screensaver
** ensure it is disabled when playing video and reenabled afterwards
* Resolutions
** you will probably need different settings for SD and HD
* Smoothness
** check news tickers for smooth flow and readability

== Also See==
*[[BBC HD]] (Patches and Info for Watching BBC HD on Astra 28.8e)

== External Links ==
* [http://www.mplayerhq.hu MPlayer Home page]
* [http://www.mplayerhq.hu/DOCS/HTML/en/index.html MPlayer documentation]
* [http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html MPlayer man page (online version)]

[[Category:Software]]
[[Category:Apps & Utilities]]

MPlayer

2012-09-09T19:24:05Z

CityK: /* Watching DVB Streams */ rework the sections on dvb usage, to better highlight the usage with more complex device configurations

The Linux video "Swiss Army knife", which plays almost every movie format imaginable [http://www.mplayerhq.hu/design7/info.html].

:''The player is rock solid playing damaged MPEG files (useful for some VCDs), and it plays bad AVI files which are unplayable with the famous windows media player. Even AVI files without index chunk are playable, and you can temporarily rebuild their indexes with the -idx option, or permanently with MEncoder, thus enabling seeking! As you see, stability and quality are the most important things, but the speed is also amazing. There is also a powerful filter system for video and audio manipulation.'' [http://www.mplayerhq.hu/DOCS/HTML/en/intro.html]

In addition, MPlayer can also serve as:
* a TV viewer application for both analogue TV or DVB.
* a Radio listening application
* a [[Webcam]] viewing application

==Using MPlayer to Watch TV==

=== Useful MPlayer Global Keyboard Hotkeys When Watching TV===
These are global settings applicable for either analogue or DVB.

You can change the channel and control the volume with those keys:
{| border="1" cellpadding="2"
!width="100"|Keys
!width="200"|Meaning
|-
| / and * || Decrease/increase volume
|-
| 9 and 0 || Decrease/increase volume
|-
| m || Mute sound
|-
| h and k || Select previous/next channel
|}

For more info about MPlayer command line parameters and other control keys, please read the [http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html MPlayer man page]

=== Watching Analogue TV===
A sample MPlayer command line that will play TV for Europe, channel E2, for devices that use analog audio wired from the TV card audio output into the aux or cd audio input on the motherboard or on the audio card:

mplayer tv:// -tv driver=v4l2:norm=PAL:input=0:amode=1:width=384:height=288:outfmt=yv12:device=/dev/video0:chanlist=europe-west:channel=E2

If your board provides a digital audio input, don't forget to load the alsa module for it. In this case, you'll need to teach mplayer to read the audio stream as well. This is an example of using mplayer for viewing TV on a NTSC video stream, reading also the audio stream:

mplayer -tv driver=v4l2:device=/dev/video0:norm=NTSC:chanlist=us-bcast:channel=10:alsa=1:adevice=hw.1:audiorate=48000:immediatemode=0:amode=1 tv://

In this case, it is assumed that the -alsa module created as the second audio adapter (hw:1), and supports an audio rate of 48 kHz. There are more useful information about audio setups with alsa modules on [[Saa7134-alsa]].

To avoid having to specify all the above parameters, it is recommended to write them to the ~/.mplayer/config:
zoom = yes
vo = x11
tv = "driver=v4l2:device=/dev/video0:norm=NTSC:chanlist=us-bcast:channel=10:alsa=1:adevice=hw.1:audiorate=48000:immediatemode=0:amode=1"
monitoraspect = "16:9"

=== Watching DVB Streams ===
One method of using MPlayer to watch DVB streams is outlined in the [[Testing your DVB device]] article. However, it is a convoluted solution, and is much more suited for testing purposes rather then daily use. A much simpler and convenient method is outlined below.

{{Note|The following methods require that you configure a ''channels.conf'' file and store it in ''~/.mplayer'' (instructions on how to do this are detailed in the [[Testing your DVB device]] article) before you can actually use MPlayer to view or record DVB streams.}}

If you have a single DVB device, which itself has a single [[Frontend|frontends]](a usage case which will be true for most persons; See, the section below for MPlayer usage with more complex device configurations), you can start watching DVB streams with MPlayer simply by typing:

$ mplayer dvb://

That command will result in your DVB device receiving the first channel listed in your channels.conf and displaying that stream's contents in MPlayer. You can then move forward through your channel list by pressing h (next) on your keyboard. Conversely, pressing k (previous) on your keyboard will move backwards through your channel list.

If you wish to open a specific DVB stream (as listed in the ''channels.conf'' file), type:

$ mplayer dvb://"STREAM NAME"

"STREAM NAME" is, of course, a generic descriptor and you will have to substitute the correct name accordingly (e.g. BBC, CBS, CBC, ....)
{{Note|Around the stream name you can use double parenthesis, single parenthesis, or none at all}}

Of course, for even better results, you may wish to run MPlayer with some options (<code>mplayer dvb:// <options></code>). For example, to utilise linear blend deinterlacing for display/playback, run:

$ mplayer dvb:// -vf pp=lb

You may have to force demuxer type for better results. For example, for a DVB-T device (all DVB devices?):

$ mplayer dvb:// -demuxer mpegts

See the MPlayer man page (i.e. in a console run "man mplayer") for a lengthy list of available options (an online version is found below in the links section).

====MPlayer usage with multiple DVB device adapters, or device adapters with multiple frontends, or multiple adaptors with multiple frontends!====
If you choose not to specify a device adapter and/or frontend, as was the case in the examples shown in the section above, then MPlayer will default to using /dev/dvb/adapter0 and /dev/dvb/adapter0/frontend0

If you have more than one DVB device adapter installed in your system you can specify the device to use by passing the device number in the command syntax. MPlayer uses device numbers of 1-4. For example:

$ mplayer dvb://"DEVICE NUMBER"@"STREAM NAME" <options>

Which will open the default frontend ("frontend0") on the adapter you specify.

Some device adapters also have multiple frontends. In which case, you can specify which frontend on the adapter to use by passing the frontend number along with the device adapter number. For example:
$ mplayer dvb://"DEVICE NUMBER":"FRONTEND NUMBER"@"STREAM NAME" <options>

Again, to avoid having to specify all the above parameters, it is recommended to write them to the ~/.mplayer/config file.

==== Limitations with DVB Streams ====
* Only free-to-air broadcasts are supported. Decryption through [[CAM]] is not implemented in MPlayer.
But you can use virtual interface such as sasc-ng or utilite ca_zap from dvb-apps/util:
cat ~/.mplayer/channels.conf:
#Eutelsat W4 36'
Sport 1:11727:h:0:27500:101:201:1
Sport 2:11727:h:0:27500:102:202:2
First Automotive:11727:h:0:27500:103:203:3
BIZ TV:11727:h:0:27500:105:205:5
RUTV:11727:h:0:27500:109:209:9
O2TV:11727:h:0:27500:110:210:10
RTVi:11727:h:0:27500:111:211:11

ca_zap -m -c ~/.mplayer/channels.conf -t sat -a 0 -n 'Sport 1'
mplayer dvb://'0@Sport 1'
* There is (presently) no DVB subtitle support in MPlayer.

==== Recording DVB Streams ====
If you want to record a DVB stream with MPlayer, you can use:

$ mplayer -dumpstream dvb://"STREAM NAME" -dumpfile stream.ts

This will dump the stream in MPEG-TS format to the file ''stream.ts'' ('''Note''' that this file can be very large - ~1GB for 30 minutes).

You can then use MPlayer or [[MEncoder]], a command-line encoder built on the MPlayer code, to convert that file to a usable video format.

There is even more functionality in [[MEncoder]] when it comes to recording streams.

==== MPlayer and Satellite Dishes ====
If you are using MPlayer with a satellite dish that has a C-Band lnb LO: 5150 or standard Ku Band lnb LO: 10750 such as are commonly used in North America, MPlayer will tune the channel if you use the L Band frequency in your .mplayer/channels.conf file instead of the C or Ku Band frequency. To calculate the L Band frequency for C Band, 5150 minus frequency in Mhz equals L Band frequency in Mhz. For Ku Band, frequency in Mhz minus 10750 equals L Band frequency in Mhz.

For example to tune C Band 4.060 Ghz

5150 - 4060 = 1090

Use 1090 for the frequency in channels.conf instead of 4060.

For Ku Band 11.799 Ghz

11799 - 10750 = 1049

==Using MPlayer for Radio Listening==
You can do a lot of things with MPlayer. An example of commandline syntax used for radio listening is:

mplayer -rawaudio rate=48000 radio://2/capture -radio adevice=hw=2:arate=48000:channels=93.8-Radio_Zones,94.7-SSR_1

Note that this command will work even without audio cable between the output of the radio card and a line input of the audio card.

This will start MPlayer with sample rate = 48 kHz (using the same sample rate that the sound card is using gives best results), listening to the second station on the list, the tuner is the third sound card (ALSA device hw:2). For more examples and syntax: [http://www.mplayerhq.hu/DOCS/HTML/en/radio-input.html#radio-tips MPlayer radio tips].

You can add as many stations as wanted and use LIRC to control MPlayer.

If you are, say, running JACK all the time, you can add
ao=jack,alsa
into ~.mplayer/config (for MPlayer) and mplayerplug-in.conf (for Firefox mplayerplug-in). For recording, you can use any JACK aware recording application.

A XDialog wrapper can be made for radio listening using MPlayer and v4l2-ctl. The authour found that it was so good that they decided to make it public under the name [http://slashdot.org/firehose.pl?op=view&id=5214989 XDRadio]. You will have to make a list of your stations during the installation (very easy to do). After that, all that is required is to just to run it and enjoy the radio.

==Using MPlayer for Webcam Viewing==
Can be used to view webcam video by invoking 'mplayer tv://'.

==High Quality Video Playback==

MPlayer will play almost anything with the default settings, but with careful selection of the command line parameters (i.e. test samples, trial-and-error and patience) it is possible to achieve very high quality video playback. When you are satisfied with the results provided by certain parameters, you can add them to the ~.mplayer/config file so that they are used persistently and don't have to be manually passed to the application. Type "man mplayer" for a detailed listing of available options. Pay particular attention to:

* Video Output Driver (-vo option)
** xv is reliable
** vdpau may be useful if you have an nvidia card (and not enough CPU)
* Deinterlacing
** See http://guru.multimedia.cx/deinterlacing-filters/
** -vf yadif=1 is good, doubles the frame rate to preserve information (at the cost of CPU)
* Upscaling
** -vf scale with -sws 9 is very good (at the cost of CPU)
* Buffering
* Vertical sync (check for tearing artefacts in the video)
** check video card options, desktop compositing, OpenGL
** video card frame rate should equal (or be a multiple of) video frame rate
* Audio sync
** -delay option
* Screensaver
** ensure it is disabled when playing video and reenabled afterwards
* Resolutions
** you will probably need different settings for SD and HD
* Smoothness
** check news tickers for smooth flow and readability

== Also See==
*[[BBC HD]] (Patches and Info for Watching BBC HD on Astra 28.8e)

== External Links ==
* [http://www.mplayerhq.hu MPlayer Home page]
* [http://www.mplayerhq.hu/DOCS/HTML/en/index.html MPlayer documentation]
* [http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html MPlayer man page (online version)]

[[Category:Software]]
[[Category:Apps & Utilities]]

Talk:Hauppauge WinTV-Aero-m

2012-08-27T01:38:32Z

CityK: minor edit

'''When this device worked ... ''' 
it worked great ... though that comment comes with a few caveats:
* The bulk of my Linux user experience with the device was done while under a kernel 3.4 (will expand upon the possible importance of this point in the section below these bullet pts)
* Under Linux - I tried with the built-in antenna for OTA ATSC reception, but did so only under poor testing circumstances, and never was able to detect any ATSC channels ... never got around to testing under good circumstances, nor did I ever get around to attempting such under Windows
* Under Linux, using an external antenna for OTA ATSC reception, its tuning sensitivity was great in this regard. Never got around to testing this under Windows (have no reason to believe it would have been any different then the excellent results obtained with the device while running under Linux)
* I don't have cable TV any more, so did not get around to testing this feature (under either Linux or Windows)... in any regard, the provider in my area encrypts all but a barker channel or two, and maybe a few radio stations, so it is not really worth my time to bother checking except for being academic about it
* Nearest DVB-T source is likely 5,000km away ... would have had to go {insert stereotypical broken english accent here}"back to old country"{/end sterotype} to test this feature
* Under Linux, even if you switch to a v3.5 or better kernel, currently there are no userspace tools/apps that would allow for testing ATSC-M/H reception. I never got around to testing this under Windows. In any regard, there are only one or two M/H signals currently being tested with by broadcasters in my region, so it wasn't a pressing matter

'''Then it all went south''' 
Astute readers will naturally have picked up on the "when this device worked" qualifier of that last section. You can also find similar alarming statements made by others on, amongst other websites, Amazon and Newegg. You see, my device, running under kernel 3.4, was working wonderfully for OTA ATSC (for the less then 2 months that I had had it for) until that stopped working (NOT cool).

Here is my current thought: either it coincidently borked itself just a day after I updated to kernel v3.5, or there is something (programmatically) wrong with the drivers. I will assume that the users on AMZN and the egg (whom also reported that the ATSC section of the device suddenly stopped working) are Windows users and that the problem afflicting me (running under Linux) also exits there too.

Here is what dmesg gives you when its not detecting the LG DT3305 (along with my annotations):
[ 2.385654] usb 1-4.3: new high-speed USB device number 5 using ehci_hcd
[ 2.471694] usb 1-4.3: New USB device found, idVendor=2040, idProduct=c61b
[ 2.471696] usb 1-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.471697] usb 1-4.3: Product: WinTV Aero-M
[ 2.471698] usb 1-4.3: Manufacturer: Hauppauge
[ 2.471699] usb 1-4.3: SerialNumber: 4034349227
[ 5.928662] dvb-usb: found a 'Hauppauge WinTV-Aero-M' in warm state.
[ 5.928694] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.928695] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.928696] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.930549] DVB: registering new adapter (Hauppauge WinTV-Aero-M)
[ 6.150608] lgdt3305_read_reg: error (addr 59 reg 0001 error (ret == -121)
[ 6.150613] lgdt3305_attach: error -121 on line 1144
[ 6.150614] lgdt3305_attach: unable to detect LGDT3305 hardware
[ 6.150620] dvb-usb: no frontend was attached by 'Hauppauge WinTV-Aero-M'
[ 6.150893] dvb-usb: Hauppauge WinTV-Aero-M successfully initialized and connected.
[ 6.151369] mxl111sf: MxL111SF detected, v8_200 (0x18)
 ---> No LG2161 detected here either! <--- 
[ 6.173309] tveeprom 14-0050: Hauppauge model 126001, rev F1G4, serial# 7817387
[ 6.173313] tveeprom 14-0050: MAC address is 00:0d:fe:77:48:ab
[ 6.173314] tveeprom 14-0050: tuner model is MaxLinear 111 (idx 164, type 4)
[ 6.173316] tveeprom 14-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
[ 6.173317] tveeprom 14-0050: audio processor is None (idx 0)
[ 6.173318] tveeprom 14-0050: has no radio, has IR receiver, has no IR transmitter
[ 6.173755] usbcore: registered new interface driver dvb_usb_mxl111sf

'''Triage'''
* evidently the DT3305 can't be detected ... neither is the LG2161, but there is no mention of the M/H demod in the demesg output
* The MxL111SF (a multi-function SoC) provides an interface to external demodulators so that they can leverage the MaxLinear chip's built in tuner and usb bridge.
* M/H support was added to kernel 3.5 [http://www.mail-archive.com/linux-media@vger.kernel.org/msg45936.html]
* the problem was first encountered, the day after updating to kernel v3.5, after a failed attempt to awaken the system from sleep (S3)
* I have seen reports of problems with S3 on kernel v3.5
* the first time this happened, I was able to revive the device by doing a fresh installation of it, and the corresponding WinTV software, under Windows, ... not actually sure what step reinitialized the device, as I was actually unable to detect any channels with it under Windows while doing this, but plugging it back into the Linux system revealed a correct working state for the device again
* one day later, the device had gone south under Linux again (discovered after a cold boot)
* this second time, I was able to revive the device by doing the Windows trick again ... only it required multiple installation/deinstallation/scanning under Windows (and, again, without being able to detect channels while operating under Windows) before plugging it back into Linux revealed a working device
* a day or two later, after the second resuscitation, the device suffered a third cardiac arrest under Linux ... multiple attempts with the Windows defibrillator have failed to bring it back

'''Early Diagnosis''' 
Has my device taken those final few steps towards the shadowy figures in the light? Has its electrons truly passed on through to the other side, and will never return to spark life back upon my screens in this mortal coil?

While it looks grim at the moment, I actually think that there might be hope. Offhand, I'm thinking that problems with the ACPI event (sleep S3) have exposed a fundamental flaw in the programming of registers in the MxL111SF (both under Windows and Linux). Its either coincidental, or noteworthy that the 3.5 kernel added support for the M/H LG2161 demod. Investigation into how this touched upon the MxL111SF is in order, as well as to how its inclusion impacts the LGDT3305 demod, and how a S3 event might have played a part. In a sense, the MxL111SF is the gatekeeper to these two demods. And it is a MxL111SF register gate that I believe is being stuck, and, consequently, making it appear that the device is borked. The real question is [http://www.youtube.com/watch?v=JKQ-BpO4Gzo who is going to give her the shot?] (warning: link not suitable for work or most family situations)

'''Quick Follow Up''' 
Interesting -- just looking through the old log files. I think my analysis above is on track. Seeing stuff like:
[12269.117457] dvb-usb: bulk message failed: -19 (26/0)
[12269.117460] lgdt3305_read_reg: error (addr 59 reg 0002 error (ret == -121)
[12269.117461] lgdt3305_sleep: error -121 on line 573
[12269.117462] dvb-usb: bulk message failed: -19 (26/0)
and
[12286.621611] mxl111sf: error writing addr: 0x17, mask: 0x40, data: 0x00, retrying...
[12286.621613] dvb-usb: bulk message failed: -19 (2/0)
and other MxL111SF register writing errors.

Media_build (now 8 days old) doesn't help at all, as it results in a bunch of symbol related errors. (I don't think they are anything remotely related to the problem, but rather, are related to changes that Antti/Crope has been making to dvb_usb). For posterity sake, they are as follows:
[ 4.358211] dvb_usb: disagrees about version of symbol dvb_dmxdev_init
[ 4.358215] dvb_usb: Unknown symbol dvb_dmxdev_init (err -22)
[ 4.358231] dvb_usb: disagrees about version of symbol dvb_register_adapter
[ 4.358232] dvb_usb: Unknown symbol dvb_register_adapter (err -22)
[ 4.358249] dvb_usb: disagrees about version of symbol rc_register_device
[ 4.358250] dvb_usb: Unknown symbol rc_register_device (err -22)
[ 4.358254] dvb_usb: disagrees about version of symbol dvb_net_init
[ 4.358255] dvb_usb: Unknown symbol dvb_net_init (err -22)
[ 4.358261] dvb_usb: disagrees about version of symbol dvb_dmxdev_release
[ 4.358262] dvb_usb: Unknown symbol dvb_dmxdev_release (err -22)
[ 4.358264] dvb_usb: disagrees about version of symbol rc_free_device
[ 4.358265] dvb_usb: Unknown symbol rc_free_device (err -22)
[ 4.358271] dvb_usb: disagrees about version of symbol dvb_frontend_detach
[ 4.358272] dvb_usb: Unknown symbol dvb_frontend_detach (err -22)
[ 4.358274] dvb_usb: disagrees about version of symbol dvb_net_release
[ 4.358275] dvb_usb: Unknown symbol dvb_net_release (err -22)
[ 4.358278] dvb_usb: disagrees about version of symbol rc_allocate_device
[ 4.358279] dvb_usb: Unknown symbol rc_allocate_device (err -22)
[ 4.358283] dvb_usb: disagrees about version of symbol dvb_unregister_frontend
[ 4.358284] dvb_usb: Unknown symbol dvb_unregister_frontend (err -22)
[ 4.358287] dvb_usb: disagrees about version of symbol dvb_register_frontend
[ 4.358288] dvb_usb: Unknown symbol dvb_register_frontend (err -22)
[ 4.358291] dvb_usb: disagrees about version of symbol dvb_unregister_adapter
[ 4.358292] dvb_usb: Unknown symbol dvb_unregister_adapter (err -22)
[ 4.358297] dvb_usb: disagrees about version of symbol rc_unregister_device
[ 4.358298] dvb_usb: Unknown symbol rc_unregister_device (err -22)

'''Update 2''' 
Okay, in response to comments I left on the linuxtv IRC channel, Antti/Crope noted that his GSoC project changes only apply to "dvb_usb_v2", and not to the old/original "dvb_usb" (which is what is producing the errors; as seen above) and that they are likely the result of the recent file and directory structure re-organization within the media build. Ahh, good old fashioned re-orgs -- when does one not ever cause a problem? Anyway, one should expect that that will get sorted out soon enough.

On the good news front, Crope mentioned that he too has an Aero-m and that he has it coded up for dvb_usb_v2 (I look forward to testing that when I get a chance). Crope also remarked that he too has seen some of the errors I've mentioned above, though, as I wasn't actually conversing with him at the time, I'm not sure if he meant the problems I noted with the current state of affairs within the media_build repo, or specifically to the Aero-m related errors I've highlighted.

So, getting back on focus -- the Aero-m. I'm pretty confident that the device is not dead but that I just need to reinitialize some of the MaxLinear chip's registers. Hopefully debricking it at this point does not require the use of JTAG (I'm assuming the SoC has a JTAG interface). If that is the case, I simply don't have the time to do that, or experience to do that (or time to learn how to do that) so it will head back on the next train to Long Island so that a [http://fxb.worth1000.com/entries/427478/monkeying-around HCW engineering monkey may have such pleasure].

In the bigger picture, if my assumption is correct (drivers, both Windows and Linux, are not programming the MxL111SF correctly), everyone of these devices currently is ticking away to brick itself upon encountering certain conditions.

Talk:Hauppauge WinTV-Aero-m

2012-08-27T01:36:41Z

CityK: minor edit

Talk:Hauppauge WinTV-Aero-m

2012-08-27T01:34:33Z

CityK: update

'''When this device worked ... ''' 
it worked great ... though that comment comes with a few caveats:
* The bulk of my Linux user experience with the device was done while under a kernel 3.4 (will expand upon the possible importance of this point in the section below these bullet pts)
* Under Linux - I tried with the built-in antenna for OTA ATSC reception, but did so only under poor testing circumstances, and never was able to detect any ATSC channels ... never got around to testing under good circumstances, nor did I ever get around to attempting such under Windows
* Under Linux, using an external antenna for OTA ATSC reception, its tuning sensitivity was great in this regard. Never got around to testing this under Windows (have no reason to believe it would have been any different then the excellent results obtained with the device while running under Linux)
* I don't have cable TV any more, so did not get around to testing this feature (under either Linux or Windows)... in any regard, the provider in my area encrypts all but a barker channel or two, and maybe a few radio stations, so it is not really worth my time to bother checking except for being academic about it
* Nearest DVB-T source is likely 5,000km away ... would have had to go {insert stereotypical broken english accent here}"back to old country"{/end sterotype} to test this feature
* Under Linux, even if you switch to a v3.5 or better kernel, currently there are no userspace tools/apps that would allow for testing ATSC-M/H reception. I never got around to testing this under Windows. In any regard, there are only one or two M/H signals currently being tested with by broadcasters in my region, so it wasn't a pressing matter

'''Then it all went south''' 
Astute readers will naturally have picked up on the "when this device worked" qualifier of that last section. You can also find similar alarming statements made by others on, amongst other websites, Amazon and Newegg. You see, my device, running under kernel 3.4, was working wonderfully for OTA ATSC (for the less then 2 months that I had had it for) until that stopped working (NOT cool).

Here is my current thought: either it coincidently borked itself just a day after I updated to kernel v3.5, or there is something (programmatically) wrong with the drivers. I will assume that the users on AMZN and the egg (whom also reported that the ATSC section of the device suddenly stopped working) are Windows users and that the problem afflicting me (running under Linux) also exits there too.

Here is what dmesg gives you when its not detecting the LG DT3305 (along with my annotations):
[ 2.385654] usb 1-4.3: new high-speed USB device number 5 using ehci_hcd
[ 2.471694] usb 1-4.3: New USB device found, idVendor=2040, idProduct=c61b
[ 2.471696] usb 1-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.471697] usb 1-4.3: Product: WinTV Aero-M
[ 2.471698] usb 1-4.3: Manufacturer: Hauppauge
[ 2.471699] usb 1-4.3: SerialNumber: 4034349227
[ 5.928662] dvb-usb: found a 'Hauppauge WinTV-Aero-M' in warm state.
[ 5.928694] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.928695] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.928696] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.930549] DVB: registering new adapter (Hauppauge WinTV-Aero-M)
[ 6.150608] lgdt3305_read_reg: error (addr 59 reg 0001 error (ret == -121)
[ 6.150613] lgdt3305_attach: error -121 on line 1144
[ 6.150614] lgdt3305_attach: unable to detect LGDT3305 hardware
[ 6.150620] dvb-usb: no frontend was attached by 'Hauppauge WinTV-Aero-M'
[ 6.150893] dvb-usb: Hauppauge WinTV-Aero-M successfully initialized and connected.
[ 6.151369] mxl111sf: MxL111SF detected, v8_200 (0x18)
 ---> No LG2161 detected here either! <--- 
[ 6.173309] tveeprom 14-0050: Hauppauge model 126001, rev F1G4, serial# 7817387
[ 6.173313] tveeprom 14-0050: MAC address is 00:0d:fe:77:48:ab
[ 6.173314] tveeprom 14-0050: tuner model is MaxLinear 111 (idx 164, type 4)
[ 6.173316] tveeprom 14-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
[ 6.173317] tveeprom 14-0050: audio processor is None (idx 0)
[ 6.173318] tveeprom 14-0050: has no radio, has IR receiver, has no IR transmitter
[ 6.173755] usbcore: registered new interface driver dvb_usb_mxl111sf

'''Triage'''
* evidently the DT3305 can't be detected ... neither is the LG2161, but there is no mention of the M/H demod in the demesg output
* The MxL111SF (a multi-function SoC) provides an interface to external demodulators so that they can leverage the MaxLinear chip's built in tuner and usb bridge.
* M/H support was added to kernel 3.5 [http://www.mail-archive.com/linux-media@vger.kernel.org/msg45936.html]
* the problem was first encountered, the day after updating to kernel v3.5, after a failed attempt to awaken the system from sleep (S3)
* I have seen reports of problems with S3 on kernel v3.5
* the first time this happened, I was able to revive the device by doing a fresh installation of it, and the corresponding WinTV software, under Windows, ... not actually sure what step reinitialized the device, as I was actually unable to detect any channels with it under Windows while doing this, but plugging it back into the Linux system revealed a correct working state for the device again
* one day later, the device had gone south under Linux again (discovered after a cold boot)
* this second time, I was able to revive the device by doing the Windows trick again ... only it required multiple installation/deinstallation/scanning under Windows (and, again, without being able to detect channels while operating under Windows) before plugging it back into Linux revealed a working device
* a day or two later, after the second resuscitation, the device suffered a third cardiac arrest under Linux ... multiple attempts with the Windows defibrillator have failed to bring it back

'''Early Diagnosis''' 
Has my device taken those final few steps towards the shadowy figures in the light? Has its electrons truly passed on through to the other side, and will never return to spark life back upon my screens in this mortal coil?

While it looks grim at the moment, I actually think that there might be hope. Offhand, I'm thinking that problems with the ACPI event (sleep S3) have exposed a fundamental flaw in the programming of registers in the MxL111SF (both under Windows and Linux). Its either coincidental, or noteworthy that the 3.5 kernel added support for the M/H LG2161 demod. Investigation into how this touched upon the MxL111SF is in order, as well as to how its inclusion impacts the LGDT3305 demod, and how a S3 event might have played a part. In a sense, the MxL111SF is the gatekeeper to these two demods. And it is a MxL111SF register gate that I believe is being stuck, and, consequently, making it appear that the device is borked. The real question is [http://www.youtube.com/watch?v=JKQ-BpO4Gzo who is going to give her the shot?] (warning: link not suitable for work or most family situations)

'''Quick Follow Up''' 
Interesting -- just looking through the old log files. I think my analysis above is on track. Seeing stuff like:
[12269.117457] dvb-usb: bulk message failed: -19 (26/0)
[12269.117460] lgdt3305_read_reg: error (addr 59 reg 0002 error (ret == -121)
[12269.117461] lgdt3305_sleep: error -121 on line 573
[12269.117462] dvb-usb: bulk message failed: -19 (26/0)
and
[12286.621611] mxl111sf: error writing addr: 0x17, mask: 0x40, data: 0x00, retrying...
[12286.621613] dvb-usb: bulk message failed: -19 (2/0)
and other MxL111SF register writing errors.

Media_build (now 8 days old) doesn't help at all, as it results in a bunch of symbol related errors. (I don't think they are anything remotely related to the problem, but rather, are related to changes that Antti/Crope has been making to dvb_usb). For posterity sake, they are as follows:
[ 4.358211] dvb_usb: disagrees about version of symbol dvb_dmxdev_init
[ 4.358215] dvb_usb: Unknown symbol dvb_dmxdev_init (err -22)
[ 4.358231] dvb_usb: disagrees about version of symbol dvb_register_adapter
[ 4.358232] dvb_usb: Unknown symbol dvb_register_adapter (err -22)
[ 4.358249] dvb_usb: disagrees about version of symbol rc_register_device
[ 4.358250] dvb_usb: Unknown symbol rc_register_device (err -22)
[ 4.358254] dvb_usb: disagrees about version of symbol dvb_net_init
[ 4.358255] dvb_usb: Unknown symbol dvb_net_init (err -22)
[ 4.358261] dvb_usb: disagrees about version of symbol dvb_dmxdev_release
[ 4.358262] dvb_usb: Unknown symbol dvb_dmxdev_release (err -22)
[ 4.358264] dvb_usb: disagrees about version of symbol rc_free_device
[ 4.358265] dvb_usb: Unknown symbol rc_free_device (err -22)
[ 4.358271] dvb_usb: disagrees about version of symbol dvb_frontend_detach
[ 4.358272] dvb_usb: Unknown symbol dvb_frontend_detach (err -22)
[ 4.358274] dvb_usb: disagrees about version of symbol dvb_net_release
[ 4.358275] dvb_usb: Unknown symbol dvb_net_release (err -22)
[ 4.358278] dvb_usb: disagrees about version of symbol rc_allocate_device
[ 4.358279] dvb_usb: Unknown symbol rc_allocate_device (err -22)
[ 4.358283] dvb_usb: disagrees about version of symbol dvb_unregister_frontend
[ 4.358284] dvb_usb: Unknown symbol dvb_unregister_frontend (err -22)
[ 4.358287] dvb_usb: disagrees about version of symbol dvb_register_frontend
[ 4.358288] dvb_usb: Unknown symbol dvb_register_frontend (err -22)
[ 4.358291] dvb_usb: disagrees about version of symbol dvb_unregister_adapter
[ 4.358292] dvb_usb: Unknown symbol dvb_unregister_adapter (err -22)
[ 4.358297] dvb_usb: disagrees about version of symbol rc_unregister_device
[ 4.358298] dvb_usb: Unknown symbol rc_unregister_device (err -22)

'''Update 2''' 
Okay, in response to comments I left on the linuxtv IRC channel, Antti/Crope noted that his GSoC project changes only apply to "dvb_usb_v2", and not to the old/original "dvb_usb" (which is what is producing the errors; as seen above) and that they are likely the result of the recent file and directory structure re-organization within the media build. Ahh, good old fashioned re-orgs -- when does one not ever cause a problem? Anyway, one should expect that that will get sorted out soon enough.

On the good news front, Crope mentioned that he too has an Aero-m and that he has it coded up for dvb_usb_v2 (I look forward to testing that when I get a chance). Crope also remarked that he too has seen some of the errors I've mentioned above, though, as I wasn't actually conversing with him at the time, I'm not sure if he meant the problems I noted with current state of affairs with the media_build repo, or specifically to the Aero-m related errors I've highlighted.

So, getting back on focus -- the Aero-m. I'm pretty confident that the device is not dead but that I just need to reinitialize some of the MaxLinear chip's registers. Hopefully debricking it at this point does not require the use of JTAG (I'm assuming the SoC has a JTAG interface). If that is the case, I simply don't have the time to do that, or experience to do that (or time to learn how to do that) so it will head back on the next train to Long Island so that a [http://fxb.worth1000.com/entries/427478/monkeying-around HCW engineering monkey may have such pleasure].

In the bigger picture, if my assumption is correct (drivers, both Windows and Linux, are not programming the MxL111SF correctly), everyone of these devices currently is ticking away to brick itself.

Hauppauge WinTV-Aero-m

2012-08-27T00:52:38Z

CityK: /* Identification */ minor edit

[[Image:Hauppauge_WinTV-Aero-m_front.jpg|right|thumb|200px|WinTV-Aero-m front facia]]

A hybrid mulitple [[frontend]] (MFE) [[DTV|Digital TV]] USB 2.0 device, by [[Hauppauge]], featuring reception capabilities for [[ATSC USB Devices|ATSC, ATSC-M/H]] and [[DVB-T_USB_Devices|DVB-T]].

It is supported under Linux; since kernel 3.2 for ATSC & DVB-T and kernel 3.5 for ATSC-M/H support.

==Overview/Features==
* Very nice form factor (i.e. has a small physical footprint).
* A first of a kind type of device -- supports both DVB-T and ATSC (as well as the M/H subset) ... Note: this dual support is only available under Linux (Windows drivers will only expose the digital TV standard relative to the location it was purchased i.e. ATSC in N.A, DVB-T in Europe)
* Has a built-in, telescoping, aerial (i.e. a "whip" antenna)
* Credit card sized IR remote control (battery included), with the Aero-m itself sporting an IR receiver on its front
* Port for external antenna attachment (RF cable adapter plug included)
* Removable cap for the USB 2.0 connector
* USB 2.0 extension cable (roughly 13inches; one foot usable length once you plug both ends in)
* Windows driver CD and Installation guide

===Components Used===
* [[MaxLinear MxL111SF]] SoC
** tuner
** DVB-T demodulator
** USB 2.0 bridge
*''LG DT3305 demodulator (D)''
* ''LG LG2161 demodulator (D-m)''

===Identification===
The output of ''lsusb -v'' reveals that the device has a subsystem ID of: 2040:c61b

===Other Images===
<gallery perrow=5>
Image:Hauppauge_WinTV-Aero-m_box_and_contents.jpg|The retail box and contents
Image:Hauppauge_WinTV-Aero-m_remote.jpg|the Aero-m and its IR remote control
Image:Hauppauge_WinTV-Aero-m_device_and_attachments.jpg|the Aero-m, its attachments & the built-in aerial extended
</gallery>

==Making it Work==

===Firmware===
No firmware is required for this device

===Drivers===

===Sample Kernel Output===
Relevant dmesg output:

[ 3874.201858] usb 1-4.1.2: new high-speed USB device number 15 using ehci_hcd
[ 3874.288007] usb 1-4.1.2: New USB device found, idVendor=2040, idProduct=c61b
[ 3874.288011] usb 1-4.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3874.288013] usb 1-4.1.2: Product: WinTV Aero-M
[ 3874.288015] usb 1-4.1.2: Manufacturer: Hauppauge
[ 3874.288016] usb 1-4.1.2: SerialNumber: 4034349227
[ 3874.288293] dvb-usb: found a 'Hauppauge WinTV-Aero-M' in warm state.
[ 3874.288324] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 3874.288325] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 3874.288326] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. <-- only for kernel 3.5 and up
[ 3874.288648] DVB: registering new adapter (Hauppauge WinTV-Aero-M)
[ 3874.552658] DVB: registering adapter 0 frontend 0 (LG Electronics LGDT3305 VSB/QAM Frontend)...
[ 3874.570179] DVB: registering adapter 0 frontend 1 (MaxLinear MxL111SF DVB-T demodulator)...
[ 3874.738637] mxl111sf: MxL111SF detected, v8_200 (0x18)
[ 3874.741930] DVB: registering adapter 0 frontend 2 (LG Electronics LG2161 ATSC/MH Frontend)... <-- only for kernel 3.5 and up
[ 3874.742968] dvb-usb: Hauppauge WinTV-Aero-M successfully initialized and connected.
[ 3874.766943] tveeprom 14-0050: Hauppauge model 126001, rev F1G4, serial# 7817387
[ 3874.766946] tveeprom 14-0050: MAC address is 00:0d:fe:77:48:ab
[ 3874.766948] tveeprom 14-0050: tuner model is MaxLinear 111 (idx 164, type 4)
[ 3874.766950] tveeprom 14-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
[ 3874.766951] tveeprom 14-0050: audio processor is None (idx 0)
[ 3874.766952] tveeprom 14-0050: has no radio, has IR receiver, has no IR transmitter

Note: the above output is with a kernel version 3.5, and all 3 frontends on the adapter are registered. The output above is annotated to note the difference if you are using a pre version 3.5 kernel.

===Remote Control Support===
The remote has been successfully tested under Linux during driver development, however, said support is currently disabled, but will likely will be re-introduced in the near future.

===User Experience===
See the [[Talk:Hauppauge WinTV-Aero-m|article's discussion page]]

==External Links==
* [http://www.hauppauge.com/site/products/data_aero-m.html Hauppauge WinTV-Aero-m product page]
** [http://www.kernellabs.com/blog/?s=aero Some Linux driver background info from kernellabs]

[[Category:ATSC USB Devices]]

Hauppauge WinTV-Aero-m

2012-08-27T00:51:03Z

CityK: Some updates

[[Image:Hauppauge_WinTV-Aero-m_front.jpg|right|thumb|200px|WinTV-Aero-m front facia]]

A hybrid mulitple [[frontend]] (MFE) [[DTV|Digital TV]] USB 2.0 device, by [[Hauppauge]], featuring reception capabilities for [[ATSC USB Devices|ATSC, ATSC-M/H]] and [[DVB-T_USB_Devices|DVB-T]].

It is supported under Linux; since kernel 3.2 for ATSC & DVB-T and kernel 3.5 for ATSC-M/H support.

==Overview/Features==
* Very nice form factor (i.e. has a small physical footprint).
* A first of a kind type of device -- supports both DVB-T and ATSC (as well as the M/H subset) ... Note: this dual support is only available under Linux (Windows drivers will only expose the digital TV standard relative to the location it was purchased i.e. ATSC in N.A, DVB-T in Europe)
* Has a built-in, telescoping, aerial (i.e. a "whip" antenna)
* Credit card sized IR remote control (battery included), with the Aero-m itself sporting an IR receiver on its front
* Port for external antenna attachment (RF cable adapter plug included)
* Removable cap for the USB 2.0 connector
* USB 2.0 extension cable (roughly 13inches; one foot usable length once you plug both ends in)
* Windows driver CD and Installation guide

===Components Used===
* [[MaxLinear MxL111SF]] SoC
** tuner
** DVB-T demodulator
** USB 2.0 bridge
*''LG DT3305 demodulator (D)''
* ''LG LG2161 demodulator (D-m)''

===Identification===
The output of lsusb -v reveals that the device has a subsystem ID of:2040:c61b

===Other Images===
<gallery perrow=5>
Image:Hauppauge_WinTV-Aero-m_box_and_contents.jpg|The retail box and contents
Image:Hauppauge_WinTV-Aero-m_remote.jpg|the Aero-m and its IR remote control
Image:Hauppauge_WinTV-Aero-m_device_and_attachments.jpg|the Aero-m, its attachments & the built-in aerial extended
</gallery>

==Making it Work==

===Firmware===
No firmware is required for this device

===Drivers===

===Sample Kernel Output===
Relevant dmesg output:

[ 3874.201858] usb 1-4.1.2: new high-speed USB device number 15 using ehci_hcd
[ 3874.288007] usb 1-4.1.2: New USB device found, idVendor=2040, idProduct=c61b
[ 3874.288011] usb 1-4.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3874.288013] usb 1-4.1.2: Product: WinTV Aero-M
[ 3874.288015] usb 1-4.1.2: Manufacturer: Hauppauge
[ 3874.288016] usb 1-4.1.2: SerialNumber: 4034349227
[ 3874.288293] dvb-usb: found a 'Hauppauge WinTV-Aero-M' in warm state.
[ 3874.288324] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 3874.288325] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 3874.288326] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. <-- only for kernel 3.5 and up
[ 3874.288648] DVB: registering new adapter (Hauppauge WinTV-Aero-M)
[ 3874.552658] DVB: registering adapter 0 frontend 0 (LG Electronics LGDT3305 VSB/QAM Frontend)...
[ 3874.570179] DVB: registering adapter 0 frontend 1 (MaxLinear MxL111SF DVB-T demodulator)...
[ 3874.738637] mxl111sf: MxL111SF detected, v8_200 (0x18)
[ 3874.741930] DVB: registering adapter 0 frontend 2 (LG Electronics LG2161 ATSC/MH Frontend)... <-- only for kernel 3.5 and up
[ 3874.742968] dvb-usb: Hauppauge WinTV-Aero-M successfully initialized and connected.
[ 3874.766943] tveeprom 14-0050: Hauppauge model 126001, rev F1G4, serial# 7817387
[ 3874.766946] tveeprom 14-0050: MAC address is 00:0d:fe:77:48:ab
[ 3874.766948] tveeprom 14-0050: tuner model is MaxLinear 111 (idx 164, type 4)
[ 3874.766950] tveeprom 14-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
[ 3874.766951] tveeprom 14-0050: audio processor is None (idx 0)
[ 3874.766952] tveeprom 14-0050: has no radio, has IR receiver, has no IR transmitter

Note: the above output is with a kernel version 3.5, and all 3 frontends on the adapter are registered. The output above is annotated to note the difference if you are using a pre version 3.5 kernel.

===Remote Control Support===
The remote has been successfully tested under Linux during driver development, however, said support is currently disabled, but will likely will be re-introduced in the near future.

===User Experience===
See the [[Talk:Hauppauge WinTV-Aero-m|article's discussion page]]

==External Links==
* [http://www.hauppauge.com/site/products/data_aero-m.html Hauppauge WinTV-Aero-m product page]
** [http://www.kernellabs.com/blog/?s=aero Some Linux driver background info from kernellabs]

[[Category:ATSC USB Devices]]

File:Hauppauge WinTV-Aero-m device and attachments.jpg

2012-08-27T00:27:59Z

CityK:

File:Hauppauge WinTV-Aero-m box and contents.jpg

2012-08-27T00:26:38Z

CityK:

File:Hauppauge WinTV-Aero-m remote.jpg

2012-08-27T00:25:22Z

CityK:

File:Hauppauge WinTV-Aero-m front.jpg

2012-08-27T00:24:32Z

CityK:

Talk:Hauppauge WinTV-Aero-m

2012-08-25T19:56:22Z

CityK: update with info gleaned from logs

'''When this device worked ... ''' 
it worked great ... though that comment comes with a few caveats:
* The bulk of my Linux user experience with the device was done while under a kernel 3.4 (will expand upon the possible importance of this point in the section below these bullet pts)
* Under Linux - I tried with the built-in antenna for OTA ATSC reception, but did so only under poor testing circumstances, and never was able to detect any ATSC channels ... never got around to testing under good circumstances, nor did I ever get around to attempting such under Windows
* Under Linux, using an external antenna for OTA ATSC reception, its tuning sensitivity was great in this regard. Never got around to testing this under Windows (have no reason to believe it would have been any different then the excellent results obtained with the device while running under Linux)
* I don't have cable TV any more, so did not get around to testing this feature (under either Linux or Windows)... in any regard, the provider in my area encrypts all but a barker channel or two, and maybe a few radio stations, so it is not really worth my time to bother checking except for being academic about it
* Nearest DVB-T source is likely 5,000km away ... would have had to go {insert stereotypical broken english accent here}"back to old country"{/end sterotype} to test this feature
* Under Linux, even if you switch to a v3.5 or better kernel, currently there are no userspace tools/apps that would allow for testing ATSC-M/H reception. I never got around to testing this under Windows. In any regard, there are only one or two M/H signals currently being tested with by broadcasters in my region, so it wasn't a pressing matter

'''Then it all went south''' 
Astute readers will naturally have picked up on the "when this device worked" qualifier of that last section. You can also find similar alarming statements made by others on, amongst other websites, Amazon and Newegg. You see, my device, running under kernel 3.4, was working wonderfully for OTA ATSC (for the less then 2 months that I had had it for) until that stopped working (NOT cool).

Here is my current thought: either it coincidently borked itself just a day after I updated to kernel v3.5, or there is something (programmatically) wrong with the drivers. I will assume that the users on AMZN and the egg (whom also reported that the ATSC section of the device suddenly stopped working) are Windows users and that the problem afflicting me (running under Linux) also exits there too.

Here is what dmesg gives you when its not detecting the LG DT3305 (along with my annotations):
[ 2.385654] usb 1-4.3: new high-speed USB device number 5 using ehci_hcd
[ 2.471694] usb 1-4.3: New USB device found, idVendor=2040, idProduct=c61b
[ 2.471696] usb 1-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.471697] usb 1-4.3: Product: WinTV Aero-M
[ 2.471698] usb 1-4.3: Manufacturer: Hauppauge
[ 2.471699] usb 1-4.3: SerialNumber: 4034349227
[ 5.928662] dvb-usb: found a 'Hauppauge WinTV-Aero-M' in warm state.
[ 5.928694] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.928695] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.928696] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.930549] DVB: registering new adapter (Hauppauge WinTV-Aero-M)
[ 6.150608] lgdt3305_read_reg: error (addr 59 reg 0001 error (ret == -121)
[ 6.150613] lgdt3305_attach: error -121 on line 1144
[ 6.150614] lgdt3305_attach: unable to detect LGDT3305 hardware
[ 6.150620] dvb-usb: no frontend was attached by 'Hauppauge WinTV-Aero-M'
[ 6.150893] dvb-usb: Hauppauge WinTV-Aero-M successfully initialized and connected.
[ 6.151369] mxl111sf: MxL111SF detected, v8_200 (0x18)
 ---> No LG2161 detected here either! <--- 
[ 6.173309] tveeprom 14-0050: Hauppauge model 126001, rev F1G4, serial# 7817387
[ 6.173313] tveeprom 14-0050: MAC address is 00:0d:fe:77:48:ab
[ 6.173314] tveeprom 14-0050: tuner model is MaxLinear 111 (idx 164, type 4)
[ 6.173316] tveeprom 14-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
[ 6.173317] tveeprom 14-0050: audio processor is None (idx 0)
[ 6.173318] tveeprom 14-0050: has no radio, has IR receiver, has no IR transmitter
[ 6.173755] usbcore: registered new interface driver dvb_usb_mxl111sf

'''Triage'''
* evidently the DT3305 can't be detected ... neither is the LG2161, but there is no mention of the M/H demod in the demesg output
* The MxL111SF (a multi-function SoC) provides an interface to external demodulators so that they can leverage the MaxLinear chip's built in tuner and usb bridge.
* M/H support was added to kernel 3.5 [http://www.mail-archive.com/linux-media@vger.kernel.org/msg45936.html]
* the problem was first encountered, the day after updating to kernel v3.5, after a failed attempt to awaken the system from sleep (S3)
* I have seen reports of problems with S3 on kernel v3.5
* the first time this happened, I was able to revive the device by doing a fresh installation of it, and the corresponding WinTV software, under Windows, ... not actually sure what step reinitialized the device, as I was actually unable to detect any channels with it under Windows while doing this, but plugging it back into the Linux system revealed a correct working state for the device again
* one day later, the device had gone south under Linux again (discovered after a cold boot)
* this second time, I was able to revive the device by doing the Windows trick again ... only it required multiple installation/deinstallation/scanning under Windows (and, again, without being able to detect channels while operating under Windows) before plugging it back into Linux revealed a working device
* a day or two later, after the second resuscitation, the device suffered a third cardiac arrest under Linux ... multiple attempts with the Windows defibrillator have failed to bring it back

'''Early Diagnosis''' 
Has my device taken those final few steps towards the shadowy figures in the light? Has its electrons truly passed on through to the other side, and will never return to spark life back upon my screens in this mortal coil?

While it looks grim at the moment, I actually think that there might be hope. Offhand, I'm thinking that problems with the ACPI event (sleep S3) have exposed a fundamental flaw in the programming of registers in the MxL111SF (both under Windows and Linux). Its either coincidental, or noteworthy that the 3.5 kernel added support for the M/H LG2161 demod. Investigation into how this touched upon the MxL111SF is in order, as well as to how its inclusion impacts the LGDT3305 demod, and how a S3 event might have played a part. In a sense, the MxL111SF is the gatekeeper to these two demods. And it is a MxL111SF register gate that I believe is being stuck, and, consequently, making it appear that the device is borked. The real question is [http://www.youtube.com/watch?v=JKQ-BpO4Gzo who is going to give her the shot?] (warning: link not suitable for work or most family situations)

'''Quick Follow Up'''
Interesting -- just looking through the old log files. I think my analysis above is on track. Seeing stuff like:
[12269.117457] dvb-usb: bulk message failed: -19 (26/0)
[12269.117460] lgdt3305_read_reg: error (addr 59 reg 0002 error (ret == -121)
[12269.117461] lgdt3305_sleep: error -121 on line 573
[12269.117462] dvb-usb: bulk message failed: -19 (26/0)
and
[12286.621611] mxl111sf: error writing addr: 0x17, mask: 0x40, data: 0x00, retrying...
[12286.621613] dvb-usb: bulk message failed: -19 (2/0)
and other MxL111SF register writing errors.

Media_build (now 8 days old) doesn't help at all, as it results in a bunch of symbol related errors. (I don't think they are anything remotely related to the problem, but rather, are related to changes that Antti/Crope has been making to dvb_usb). For posterity sake, they are as follows:
[ 4.358211] dvb_usb: disagrees about version of symbol dvb_dmxdev_init
[ 4.358215] dvb_usb: Unknown symbol dvb_dmxdev_init (err -22)
[ 4.358231] dvb_usb: disagrees about version of symbol dvb_register_adapter
[ 4.358232] dvb_usb: Unknown symbol dvb_register_adapter (err -22)
[ 4.358249] dvb_usb: disagrees about version of symbol rc_register_device
[ 4.358250] dvb_usb: Unknown symbol rc_register_device (err -22)
[ 4.358254] dvb_usb: disagrees about version of symbol dvb_net_init
[ 4.358255] dvb_usb: Unknown symbol dvb_net_init (err -22)
[ 4.358261] dvb_usb: disagrees about version of symbol dvb_dmxdev_release
[ 4.358262] dvb_usb: Unknown symbol dvb_dmxdev_release (err -22)
[ 4.358264] dvb_usb: disagrees about version of symbol rc_free_device
[ 4.358265] dvb_usb: Unknown symbol rc_free_device (err -22)
[ 4.358271] dvb_usb: disagrees about version of symbol dvb_frontend_detach
[ 4.358272] dvb_usb: Unknown symbol dvb_frontend_detach (err -22)
[ 4.358274] dvb_usb: disagrees about version of symbol dvb_net_release
[ 4.358275] dvb_usb: Unknown symbol dvb_net_release (err -22)
[ 4.358278] dvb_usb: disagrees about version of symbol rc_allocate_device
[ 4.358279] dvb_usb: Unknown symbol rc_allocate_device (err -22)
[ 4.358283] dvb_usb: disagrees about version of symbol dvb_unregister_frontend
[ 4.358284] dvb_usb: Unknown symbol dvb_unregister_frontend (err -22)
[ 4.358287] dvb_usb: disagrees about version of symbol dvb_register_frontend
[ 4.358288] dvb_usb: Unknown symbol dvb_register_frontend (err -22)
[ 4.358291] dvb_usb: disagrees about version of symbol dvb_unregister_adapter
[ 4.358292] dvb_usb: Unknown symbol dvb_unregister_adapter (err -22)
[ 4.358297] dvb_usb: disagrees about version of symbol rc_unregister_device
[ 4.358298] dvb_usb: Unknown symbol rc_unregister_device (err -22)

Talk:Hauppauge WinTV-Aero-m

2012-08-25T19:13:56Z

CityK: a bunch of minor edits

Talk:Hauppauge WinTV-Aero-m

2012-08-25T19:06:00Z

CityK: where I think the problem may lay

Talk:Hauppauge WinTV-Aero-m

2012-08-25T18:11:24Z

CityK: intermediate save

Hauppauge WinTV-Aero-m

2012-08-25T17:05:27Z

CityK: prepare for images; minor edit

[[Image:Hauppauge_ WinTV-Aero-m_front.jpg|right|thumb|200px|breif description]]

A hybrid mulitple [[frontend]] (MFE) [[DTV|Digital TV]] USB 2.0 device, by [[Hauppauge]], featuring reception capabilities for [[ATSC USB Devices|ATSC, ATSC-M/H]] and [[DVB-T_USB_Devices|DVB-T]].

It is supported under Linux; since kernel 3.2 for ATSC & DVB-T and kernel 3.5 for ATSC-M/H support.

==Overview/Features==

===Components Used===
* [[MaxLinear MxL111SF]] SoC
** tuner
** DVB-T demodulator
** USB 2.0 bridge
*''LG DT3305 demodulator (D)''
* ''LG LG2161 demodulator (D-m)''

===Identification===
Output of lsusb -v:
</pre>

===Other Images===
<gallery perrow=5>
Image:Hauppauge_ WinTV-Aero-m_box_and_contents.jpg|Box and contents
Image:Hauppauge_ WinTV-Aero-m_remote.jpg|WinTV-Aero-m remote
</gallery>

==Making it Work==

===Firmware===
No firmware is required for this device

===Drivers===

===Sample Kernel Output===
Relevant dmesg output:

[ 3874.201858] usb 1-4.1.2: new high-speed USB device number 15 using ehci_hcd
[ 3874.288007] usb 1-4.1.2: New USB device found, idVendor=2040, idProduct=c61b
[ 3874.288011] usb 1-4.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3874.288013] usb 1-4.1.2: Product: WinTV Aero-M
[ 3874.288015] usb 1-4.1.2: Manufacturer: Hauppauge
[ 3874.288016] usb 1-4.1.2: SerialNumber: 4034349227
[ 3874.288293] dvb-usb: found a 'Hauppauge WinTV-Aero-M' in warm state.
[ 3874.288324] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 3874.288325] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 3874.288326] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. <-- only for kernel 3.5 and up
[ 3874.288648] DVB: registering new adapter (Hauppauge WinTV-Aero-M)
[ 3874.552658] DVB: registering adapter 0 frontend 0 (LG Electronics LGDT3305 VSB/QAM Frontend)...
[ 3874.570179] DVB: registering adapter 0 frontend 1 (MaxLinear MxL111SF DVB-T demodulator)...
[ 3874.738637] mxl111sf: MxL111SF detected, v8_200 (0x18)
[ 3874.741930] DVB: registering adapter 0 frontend 2 (LG Electronics LG2161 ATSC/MH Frontend)... <-- only for kernel 3.5 and up
[ 3874.742968] dvb-usb: Hauppauge WinTV-Aero-M successfully initialized and connected.
[ 3874.766943] tveeprom 14-0050: Hauppauge model 126001, rev F1G4, serial# 7817387
[ 3874.766946] tveeprom 14-0050: MAC address is 00:0d:fe:77:48:ab
[ 3874.766948] tveeprom 14-0050: tuner model is MaxLinear 111 (idx 164, type 4)
[ 3874.766950] tveeprom 14-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
[ 3874.766951] tveeprom 14-0050: audio processor is None (idx 0)
[ 3874.766952] tveeprom 14-0050: has no radio, has IR receiver, has no IR transmitter

Note: the above output is with a kernel version 3.5, and all 3 frontends on the adapter are registered. The output above is annotated to note the difference if you are using a pre version 3.5 kernel.

===Remote Control Support===
The remote has been successfully tested under Linux during driver development, however, said support is currently disabled, but will likely will be re-introduced in the near future.

===User Experience===
See the [[Talk:Hauppauge WinTV-Aero-m|article's discussion page]]

==External Links==
* [http://www.hauppauge.com/site/products/data_aero-m.html Hauppauge WinTV-Aero-m product page]

[[Category:ATSC USB Devices]]

Hauppauge WinTV-Aero-m

2012-08-25T16:59:30Z

CityK: change dmesg output to that generated by kernel 3.5 and up and annotate

A hybrid mulitple [[frontend]] (MFE) [[DTV|Digital TV]] USB 2.0 device, by [[Hauppauge]], featuring reception capabilities for [[ATSC USB Devices|ATSC, ATSC-M/H]] and [[DVB-T_USB_Devices|DVB-T]].

It is supported under Linux; since kernel 3.2 for ATSC & DVB-T and kernel 3.5 for ATSC-M/H support.

==Overview/Features==

===Components Used===
* [[MaxLinear MxL111SF]] SoC
** tuner
** DVB-T demodulator
** USB 2.0 bridge
*''LG DT3305 demodulator (D)''
* ''LG LG2161 demodulator (D-m)''

===Identification===
Output of lsusb -v:
</pre>

==Making it Work==

===Firmware===
No firmware is required for this device

===Drivers===

===Sample Kernel Output===
Relevant dmesg output:
[ 3874.201858] usb 1-4.1.2: new high-speed USB device number 15 using ehci_hcd
[ 3874.288007] usb 1-4.1.2: New USB device found, idVendor=2040, idProduct=c61b
[ 3874.288011] usb 1-4.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3874.288013] usb 1-4.1.2: Product: WinTV Aero-M
[ 3874.288015] usb 1-4.1.2: Manufacturer: Hauppauge
[ 3874.288016] usb 1-4.1.2: SerialNumber: 4034349227
[ 3874.288293] dvb-usb: found a 'Hauppauge WinTV-Aero-M' in warm state.
[ 3874.288324] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 3874.288325] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 3874.288326] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. <-- only for kernel 3.5 and up
[ 3874.288648] DVB: registering new adapter (Hauppauge WinTV-Aero-M)
[ 3874.552658] DVB: registering adapter 0 frontend 0 (LG Electronics LGDT3305 VSB/QAM Frontend)...
[ 3874.570179] DVB: registering adapter 0 frontend 1 (MaxLinear MxL111SF DVB-T demodulator)...
[ 3874.738637] mxl111sf: MxL111SF detected, v8_200 (0x18)
[ 3874.741930] DVB: registering adapter 0 frontend 2 (LG Electronics LG2161 ATSC/MH Frontend)... <-- only for kernel 3.5 and up
[ 3874.742968] dvb-usb: Hauppauge WinTV-Aero-M successfully initialized and connected.
[ 3874.766943] tveeprom 14-0050: Hauppauge model 126001, rev F1G4, serial# 7817387
[ 3874.766946] tveeprom 14-0050: MAC address is 00:0d:fe:77:48:ab
[ 3874.766948] tveeprom 14-0050: tuner model is MaxLinear 111 (idx 164, type 4)
[ 3874.766950] tveeprom 14-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
[ 3874.766951] tveeprom 14-0050: audio processor is None (idx 0)
[ 3874.766952] tveeprom 14-0050: has no radio, has IR receiver, has no IR transmitter

Note: the above output is with a kernel version 3.5, and all 3 frontends on the adapter are registered. The output above is annotated to note the difference if you are using a pre version 3.5 kernel.

===Remote Control Support===
The remote has been successfully tested under Linux during driver development, however, said support is currently disabled, but will likely will be re-introduced in the near future.

===User Experience===
See the [[Talk:Hauppauge WinTV-Aero-m|article's discussion page]]

==External Links==
* [http://www.hauppauge.com/site/products/data_aero-m.html Hauppauge WinTV-Aero-m product page]

[[Category:ATSC USB Devices]]

Hauppauge WinTV-Aero-m

2012-08-25T16:12:16Z

CityK: /* Making it Work */ minor edits

A hybrid mulitple [[frontend]] (MFE) [[DTV|Digital TV]] USB 2.0 device, by [[Hauppauge]], featuring reception capabilities for [[ATSC USB Devices|ATSC, ATSC-M/H]] and [[DVB-T_USB_Devices|DVB-T]].

It is supported under Linux; since kernel 3.2 for ATSC & DVB-T and kernel 3.5 for ATSC-M/H support.

==Overview/Features==

===Components Used===
* [[MaxLinear MxL111SF]] SoC
** tuner
** DVB-T demodulator
** USB 2.0 bridge
*''LG DT3305 demodulator (D)''
* ''LG LG2161 demodulator (D-m)''

===Identification===
Output of lsusb -v:
</pre>

==Making it Work==

===Firmware===
No firmware is required for this device

===Drivers===

===Sample Kernel Output===
Relevant dmesg output:
<pre>[ 12.857506] usb 1-2.1.2: new high-speed USB device number 7 using ehci_hcd
[ 12.944095] usb 1-2.1.2: New USB device found, idVendor=2040, idProduct=c61b
[ 12.944105] usb 1-2.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 12.944112] usb 1-2.1.2: Product: WinTV Aero-M
[ 12.944117] usb 1-2.1.2: Manufacturer: Hauppauge
[ 12.944122] usb 1-2.1.2: SerialNumber: 4034349227
[ 12.954361] dvb-usb: found a 'Hauppauge WinTV-Aero-M' in warm state.
[ 12.954397] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 12.954399] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 12.954898] DVB: registering new adapter (Hauppauge WinTV-Aero-M)
[ 13.213153] DVB: registering adapter 1 frontend 0 (LG Electronics LGDT3305 VSB/QAM Frontend)...
[ 13.234624] DVB: registering adapter 1 frontend 1 (MaxLinear MxL111SF DVB-T demodulator)...
[ 13.235245] dvb-usb: Hauppauge WinTV-Aero-M successfully initialized and connected.
[ 13.236864] mxl111sf: MxL111SF detected, v8_200 (0x18)
[ 13.258084] tveeprom 6-0050: Hauppauge model 126001, rev F1G4, serial# 7817387
[ 13.258088] tveeprom 6-0050: MAC address is 00:0d:fe:77:48:ab
[ 13.258090] tveeprom 6-0050: tuner model is MaxLinear 111 (idx 164, type 4)
[ 13.258092] tveeprom 6-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
[ 13.258093] tveeprom 6-0050: audio processor is None (idx 0)
[ 13.258095] tveeprom 6-0050: has no radio, has IR receiver, has no IR transmitter
[ 13.258261] usbcore: registered new interface driver dvb_usb_mxl111sf
</pre>

Note: the above output is with a kernel version 3.4, so the ATSC-M/H support is not included

===Remote Control Support===
The remote has been successfully tested under Linux during driver development, however, said support is currently disabled, but will likely will be re-introduced in the near future.

===User Experience===
See the [[Talk:Hauppauge WinTV-Aero-m|article's discussion page]]

==External Links==
* [http://www.hauppauge.com/site/products/data_aero-m.html Hauppauge WinTV-Aero-m product page]

[[Category:ATSC USB Devices]]

Talk:Hauppauge WinTV-Aero-m

2012-08-25T16:02:23Z

CityK: not working

And here is what dmesg gives you when its not detecting the LG DT3305:
<pre>[ 2.385654] usb 1-4.3: new high-speed USB device number 5 using ehci_hcd
[ 2.471694] usb 1-4.3: New USB device found, idVendor=2040, idProduct=c61b
[ 2.471696] usb 1-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.471697] usb 1-4.3: Product: WinTV Aero-M
[ 2.471698] usb 1-4.3: Manufacturer: Hauppauge
[ 2.471699] usb 1-4.3: SerialNumber: 4034349227
[ 5.928662] dvb-usb: found a 'Hauppauge WinTV-Aero-M' in warm state.
[ 5.928694] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.928695] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.928696] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 5.930549] DVB: registering new adapter (Hauppauge WinTV-Aero-M)
[ 6.150608] lgdt3305_read_reg: error (addr 59 reg 0001 error (ret == -121)
[ 6.150613] lgdt3305_attach: error -121 on line 1144
[ 6.150614] lgdt3305_attach: unable to detect LGDT3305 hardware
[ 6.150620] dvb-usb: no frontend was attached by 'Hauppauge WinTV-Aero-M'
[ 6.150893] dvb-usb: Hauppauge WinTV-Aero-M successfully initialized and connected.
[ 6.151369] mxl111sf: MxL111SF detected, v8_200 (0x18)
[ 6.173309] tveeprom 14-0050: Hauppauge model 126001, rev F1G4, serial# 7817387
[ 6.173313] tveeprom 14-0050: MAC address is 00:0d:fe:77:48:ab
[ 6.173314] tveeprom 14-0050: tuner model is MaxLinear 111 (idx 164, type 4)
[ 6.173316] tveeprom 14-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
[ 6.173317] tveeprom 14-0050: audio processor is None (idx 0)
[ 6.173318] tveeprom 14-0050: has no radio, has IR receiver, has no IR transmitter
[ 6.173755] usbcore: registered new interface driver dvb_usb_mxl111sf
</pre>
Note: that is under kernel version 3.5

Hauppauge WinTV-Aero-m

2012-08-25T15:44:20Z

CityK: /* Sample Kernel Output */ add dmesg output

A hybrid mulitple [[frontend]] (MFE) [[DTV|Digital TV]] USB 2.0 device, by [[Hauppauge]], featuring reception capabilities for [[ATSC USB Devices|ATSC, ATSC-M/H]] and [[DVB-T_USB_Devices|DVB-T]].

It is supported under Linux; since kernel 3.2 for ATSC & DVB-T and kernel 3.5 for ATSC-M/H support.

==Overview/Features==

===Components Used===
* [[MaxLinear MxL111SF]] SoC
** tuner
** DVB-T demodulator
** USB 2.0 bridge
*''LG DT3305 demodulator (D)''
* ''LG LG2161 demodulator (D-m)''

===Identification===
Output of lsusb -v:
</pre>

==Making it Work==

===Firmware===
No firmware is required for this device

===Drivers===

===Sample Kernel Output===
Relevant dmesg output:
<pre>[ 12.857506] usb 1-2.1.2: new high-speed USB device number 7 using ehci_hcd
[ 12.944095] usb 1-2.1.2: New USB device found, idVendor=2040, idProduct=c61b
[ 12.944105] usb 1-2.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 12.944112] usb 1-2.1.2: Product: WinTV Aero-M
[ 12.944117] usb 1-2.1.2: Manufacturer: Hauppauge
[ 12.944122] usb 1-2.1.2: SerialNumber: 4034349227
[ 12.954361] dvb-usb: found a 'Hauppauge WinTV-Aero-M' in warm state.
[ 12.954397] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 12.954399] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 12.954898] DVB: registering new adapter (Hauppauge WinTV-Aero-M)
[ 13.213153] DVB: registering adapter 1 frontend 0 (LG Electronics LGDT3305 VSB/QAM Frontend)...
[ 13.234624] DVB: registering adapter 1 frontend 1 (MaxLinear MxL111SF DVB-T demodulator)...
[ 13.235245] dvb-usb: Hauppauge WinTV-Aero-M successfully initialized and connected.
[ 13.236864] mxl111sf: MxL111SF detected, v8_200 (0x18)
[ 13.258084] tveeprom 6-0050: Hauppauge model 126001, rev F1G4, serial# 7817387
[ 13.258088] tveeprom 6-0050: MAC address is 00:0d:fe:77:48:ab
[ 13.258090] tveeprom 6-0050: tuner model is MaxLinear 111 (idx 164, type 4)
[ 13.258092] tveeprom 6-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
[ 13.258093] tveeprom 6-0050: audio processor is None (idx 0)
[ 13.258095] tveeprom 6-0050: has no radio, has IR receiver, has no IR transmitter
[ 13.258261] usbcore: registered new interface driver dvb_usb_mxl111sf
</pre>

Note: the above output is with a kernel version 3.4, so the ATSC-M/H support is not included

==External Links==
* [http://www.hauppauge.com/site/products/data_aero-m.html Hauppauge WinTV-Aero-m product page]

[[Category:ATSC USB Devices]]

Hauppauge WinTV-Aero-m

2012-08-25T01:45:44Z

CityK: minor edits

Hauppauge WinTV-HVR-850

2012-08-25T01:44:17Z

CityK: bullet pt

A hybrid [[ATSC]] [[ATSC USB Devices|USB 2.0 device]] by [[Hauppauge]].

{{Note|There are three significantly different devices being sold under the same "HVR-850" brand name. All three versions are supported, but the newest version (USB ID 2040:b140) requires kernel 2.6.37.}}

==Overview/Features==
There are three versions of this device.
* The first is essentially the older [[Hauppauge WinTV-HVR-950|WinTV-HVR-950]] model. Running lsusb -v will show the manufacturer:device code of 2040:651f.
* The second version is essentially a [[Hauppauge WinTV-HVR-950Q|WinTV-HVR-950Q]]. Running lsusb -v will show the manufacturer:device code of 2040:7240.
* The third version is unique, though it shares a tuner chip with the [[Hauppauge WinTV-HVR-1950|WinTV-HVR-1950]]. Running lsusb -v will show the manufacturer:device code of 2040:b140.

'''Note: The following information currently outlines only that pertaining to the second version (i.e. the 950Q analog).'''

Evidently, this device does not like USB 1.1 slots (see the [[Talk:Hauppauge_WinTV-HVR-850|discussion page]]).

===Components Used===
* [[Xceive]] [[Xceive XC5000|XC5000]] (tuner and analog demodulator)
* [[Auvitek International Ltd.|Auvitek]] AU8522 (A/V decoder, analog demodulator [not used], and digital demodulator)
* [[Auvitek International Ltd.|Auvitek]] AU0828 (USB bridge)

===Identification===
Output of lsusb -v:
<pre>
Bus 001 Device 002: ID 2040:7240 Hauppauge
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2040 Hauppauge
idProduct 0x7240
bcdDevice 0.05
iManufacturer 1
iProduct 2
iSerial 10
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 198
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 16
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 16
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0300 1x 768 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 16
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03fc 1x 1020 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 1 Audio
bInterfaceSubClass 1 Control Device
bInterfaceProtocol 0
iInterface 11
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 1 (HEADER)
bcdADC 1.00
wTotalLength 38
bInCollection 1
baInterfaceNr( 0) 2
AudioControl Interface Descriptor:
bLength 12
bDescriptorType 36
bDescriptorSubtype 2 (INPUT_TERMINAL)
bTerminalID 1
wTerminalType 0x0602 Digital Audio Interface
bAssocTerminal 0
bNrChannels 2
wChannelConfig 0x0003
Left Front (L)
Right Front (R)
iChannelNames 0
iTerminal 0
AudioControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 3 (OUTPUT_TERMINAL)
bTerminalID 2
wTerminalType 0x0101 USB Streaming
bAssocTerminal 0
bSourceID 3
iTerminal 0
AudioControl Interface Descriptor:
bLength 8
bDescriptorType 36
bDescriptorSubtype 6 (FEATURE_UNIT)
bUnitID 3
bSourceID 1
bControlSize 1
bmaControls( 0) 0x01
Mute
iFeature 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 1 Audio
bInterfaceSubClass 2 Streaming
bInterfaceProtocol 0
iInterface 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 1 Audio
bInterfaceSubClass 2 Streaming
bInterfaceProtocol 0
iInterface 11
AudioStreaming Interface Descriptor:
bLength 7
bDescriptorType 36
bDescriptorSubtype 1 (AS_GENERAL)
bTerminalLink 2
bDelay 1 frames
wFormatTag 1 PCM
AudioStreaming Interface Descriptor:
bLength 11
bDescriptorType 36
bDescriptorSubtype 2 (FORMAT_TYPE)
bFormatType 1 (FORMAT_TYPE_I)
bNrChannels 2
bSubframeSize 2
bBitResolution 16
bSamFreqType 1 Discrete
tSamFreq[ 0] 48000
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x0100 1x 256 bytes
bInterval 1
AudioControl Endpoint Descriptor:
bLength 7
bDescriptorType 37
bDescriptorSubtype 1 (EP_GENERAL)
bmAttributes 0x00
bLockDelayUnits 0 Undefined
wLockDelay 0 Undefined
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
</pre>

==Making it Work==

===Firmware===
In order to use the LinuxTV driver, you need to download and install the firmware for the xc5000.

wget http://www.steventoth.net/linux/xc5000/HVR-12x0-14x0-17x0_1_25_25271_WHQL.zip
wget http://www.steventoth.net/linux/xc5000/extract.sh
sh extract.sh
cp dvb-fe-xc5000-1.1.fw /lib/firmware

Note: Though the usual directory location in which the firmware file is placed is /lib/firmware, this may differ in the case of some distros; consult your distro's documentation for the appropriate location.

===Drivers===

The xc5000 driver needed for this WinTV-HVR-850 is already part of the latest Linux kernel (part of v4l-dvb drivers).

Analog support was merged into the mainline v4l-dvb tree on March 18, 2009.

===Sample Kernel Output===
dmesg output:
<pre>
usb 4-3: new high speed USB device using ehci_hcd and address 2
usb 4-3: configuration #1 chosen from 1 choice
...
au0828: i2c bus registered
tveeprom 2-0050: Hauppauge model 72301, rev B3F0, serial# 4752928
tveeprom 2-0050: MAC address is 00-0D-FE-48-86-20
tveeprom 2-0050: tuner model is Xceive XC5000 (idx 150, type 4)
tveeprom 2-0050: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88)
tveeprom 2-0050: audio processor is AU8522 (idx 44)
tveeprom 2-0050: decoder processor is AU8522 (idx 42)
tveeprom 2-0050: has no radio, has IR receiver, has no IR transmitter
hauppauge_eeprom: hauppauge eeprom: model=72301
xc5000 2-0061: creating new instance
xc5000: Successfully identified at address 0x61
xc5000: Firmware has not been loaded previously
DVB: registering new adapter (au0828)
DVB: registering adapter 1 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)...
Registered device AU0828 [Hauppauge HVR850]
usb 4-3: New USB device found, idVendor=2040, idProduct=7240
usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=10
usb 4-3: Product: WinTV HVR-850
usb 4-3: Manufacturer: Hauppauge
usb 4-3: SerialNumber: 4031284768
</pre>

==External Links==
* [http://www.hauppauge.com/site/products/data_hvr850.html Hauppauge HVR-850 product page]

[[Category:ATSC USB Devices]]

Hauppauge WinTV-Aero-m

2012-08-25T01:43:03Z

CityK: create initial skeleton page for device

A hybrid mulitple [[frontend]] (MFE) [[DTV|Digital TV]] USB 2.0 device, by [[Hauppauge]], featuring reception capabilities for [[ATSC USB Devices|ATSC & ATSC-M/H]] and [[DVB-T_USB_Devices|DVB-T]].

It is supported under Linux; since kernel 3.2 for ATSC & DVB-T and kernel 3.5 for ATSC-M/H support.

==Overview/Features==

===Components Used===
* [[MaxLinear MxL111SF]] SoC
** tuner
** DVB-T demodulator
** USB 2.0 bridge
*''LG DT3305 demodulator (D)''
* ''LG LG2161 demodulator (D-m)''

===Identification===
Output of lsusb -v:
</pre>

==Making it Work==

===Firmware===
No firmware is required for this device

===Drivers===

===Sample Kernel Output===
dmesg output:
<pre>
</pre>

==External Links==
[http://www.hauppauge.com/site/products/data_aero-m.html Hauppauge WinTV-Aero-m product page]

[[Category:ATSC USB Devices]]

ATSC USB Devices

2012-08-25T01:28:52Z

CityK: /* Supported ATSC USB Devices */ edit Aero entry

On this page you will find information regarding [[ATSC]] [[USB]] devices.

{{non-exhaustive list}}
 

__TOC__
 
==Supported ATSC USB Devices==
The following table lists the confirmed working ATSC USB devices and provides a brief summary of their features and components. If you need more technical information on a device, have a look at its specific wiki article.
 

If you are experiencing problems with USB devices, it may not be the fault of the tuner. The chipsets used on some computer motherboards can have problems with USB ports which results in tuners working or partially working or not working at all. This can be solved by using a separate USB adapter with a reliable chipset.
 

{| class="wikitable sortable"
|+'''Sortable List of Supported ATSC USB Adapters'''
|- align="left"
! '''Vendor & Model''' !! Added to Kernel !! - align="left" | '''Frontend''' !! '''Bridge Interface''' !! '''8VSB''' !! '''QAM''' !! '''NTSC''' !! class="unsortable" - align="left" | '''Other Features'''

|- align="center"
| align="left" valign="top" | '''[[ATI/AMD]] [[ATI/AMD TV Wonder HD 600 USB|TV Wonder HD 600 USB]]'''
| 2.6.27
| align="left"|
*''XC3028L tuner''
*''LG DT3303 demodulator (D)''
| Empia EM2883
| {{yes}}
| {{no}}
| {{yes}}
| align="left" valign="top" |
* S-Video & Composite inputs (breakout dongle)

|- align="center"
| align="left" valign="top" | ''' [[AVerMedia]] [[AVerMedia AVerTVHD Volar (A868R)|AVerTVHD Volar (A868R)]]'''
| 2.6.27 [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f5376adacc693155c24e4e7be3777bdd0eeb99f7]
| align="left"|
*''MXL5003S tuner''
*''LG DT3303 demodulator''
| Cypress FX2LP (CY7C68013A)
| {{yes}}
| {{no}}
| {{no}}
| align="left" valign="top" |
*

|- align="center"
| align="left" valign="top" | '''[[DViCO]] [[DViCO FusionHDTV5 USB Gold|FusionHDTV5 USB Gold]] [[DViCO FusionHDTV5 USB Master|FusionHDTV5 USB Master]]'''
| 2.6.16
| align="left"| LG Innotek TDVS-H064F
*''TAU6034 tuner''
*''TDA9887 demodulator (A)''
*''LG DT3303 demodulator (D)''
| Cypress FX2LP (CY7C68013A)
| {{yes}}
| {{yes}}
| {{no}}[[#fn_1|1]]
| align="left" valign="top" |
* S-Video & Composite inputs [[#fn_1|1]]

|- align="center"
| align="left" valign="top" | '''[[DViCO]] [[DViCO FusionHDTV7 USB|FusionHDTV7 USB]]'''
| 2.6.26
| align="left"|
*''XC5000 tuner''
*''[[Auvitek International Ltd.|Auvitek]]AU8522 demodulator (A/D)''
| [[Auvitek International Ltd.|Auvitek]] AU0828
| {{yes}}
| {{yes}}
| {{no}}[[#fn_1|1]]
| align="left" valign="top" |
* S-Video & Composite inputs [[#fn_1|1]] (breakout dongle)

|- align="center"
| align="left" valign="top" | '''[[Elgato]] [[Elgato EyeTV Hybrid US|EyeTV Hybrid US]]'''
| 2.6.26
| align="left"|
*''XC3028 tuner''
*''LG DT3303 demodulator (D)''
| Empia EM2883
| {{yes}}
| {{no}}
| {{yes}}
| align="left" valign="top" |
* S-Video & Composite inputs (breakout dongle)

|- align="center"
| align="left" valign="top" | '''EVGA [[EVGA inDtube]]'''
| 2.6.31
| align="left"|
*''XC3028L tuner''
*''S5H1409 (D)''
| Empia EM2882
| {{yes}}
| {{no}}
| {{yes}}
| align="left" valign="top" |
* S-Video & Composite inputs (breakout dongle)

|- align="center"
| align="left" valign="top" | '''[[Hauppauge]]''' '''[[Hauppauge WinTV-Aero-m|WinTV-Aero-m]]''' 
| 3.1 [http://www.kernellabs.com/blog/?p=1647]
| align="left"|
* [[MaxLinear MxL111SF]] SoC
** tuner
** DVB-T demodulator
*''LG DT3305 demodulator (D)''
* ''LG LG2161 demodulator (D-m)''
| [[MaxLinear MxL111SF]] SoC
| {{yes}}
| {{yes}}
| {{no}}
| align="left" valign="top" |
* also supports ATSC-M/H !
* also supports DVB-T !

|- align="center"
| align="left" valign="top" | '''[[Hauppauge]]''' '''[[Hauppauge WinTV-HVR-850|WinTV-HVR-850]]''' (2040:651f)
| 2.6.29
| align="left"|
*''XC3028 tuner
*''LG DT3303 demodulator (D)''
| Empia EM2883
| {{yes}}
| {{no}}
| {{yes}}
| align="left" valign="top" |
* S-Video & Composite inputs (breakout dongle)

|- align="center"
| align="left" valign="top" | '''[[Hauppauge]] ''' '''[[Hauppauge WinTV-HVR-850|WinTV-HVR-850]]''' (model 72301, 2040:7240)
| 2.6.32
| align="left"|
*''XC5000 tuner''
*''[[Auvitek International Ltd.|Auvitek]] AU8522 demodulator (A/D)''
| [[Auvitek International Ltd.|Auvitek]] AU0828
| {{yes}}
| {{yes}}
| {{yes}}
| align="left" valign="top" |
* S-Video & Composite inputs (breakout dongle)

|- align="center"
| align="left" valign="top" | '''[[Hauppauge]] ''' '''[[Hauppauge WinTV-HVR-850|WinTV-HVR-850]]''' (model 01200, 2040:b140)
| 2.6.37
| align="left"|
*''TDA18271 tuner''
*''LG LGDT3305''
| Conexant cx23102
| {{yes}}
| {{yes}}
| {{yes}}
| align="left" valign="top" |
* S-Video & Composite inputs (breakout dongle)

|- align="center"
| align="left" valign="top" | '''[[Hauppauge]] [[Hauppauge WinTV-HVR-950|WinTV-HVR-950]]'''
| 2.6.26
| align="left"|
*''XC3028 tuner''
*''LG DT3303 demodulator (D)''
| Empia EM2883
| {{yes}}
| {{no}}
| {{yes}}
| align="left" valign="top" |
* S-Video & Composite inputs (breakout dongle)

|- align="center"
| align="left" valign="top" | '''[[Hauppauge]] [[Hauppauge WinTV-HVR-950Q|WinTV-HVR-950Q]]'''
| 2.6.26
| align="left"|
*''XC5000 tuner''
*''[[Auvitek International Ltd.|Auvitek]] AU8522 demodulator (A/D)''
| [[Auvitek International Ltd.|Auvitek]] AU0828
| {{yes}}
| {{yes}}
| {{yes}}
| align="left" valign="top" |
* S-Video & Composite inputs (breakout dongle)

|- align="center"
| align="left" valign="top" | '''[[Hauppauge]] [[Hauppauge WinTV-HVR-1950|WinTV-HVR-1950]]'''
| 2.6.26
| align="left"|
*''TDA18271 tuner''
*''TDA8295 demodulator (A)''
*''S5H1411 demodulator (D)''
| Cypress FX2LP (CY7C68013A)
| {{yes}}
| {{yes}}
| {{yes}}
| align="left" valign="top" |
* S-Video & Composite inputs
* hardware analog mpeg2 encoder

|- align="center"
| align="left" valign="top" | '''[[KWorld]] [[KWorld ATSC 315U|ATSC 315U]]''' 
(eb1a:a313)
| 2.6.31
| align="left"| Thomson DTT 7611A tuner module
* ''? tuner''
* ''? analog demod''
*''LG LGDT3303 (digital demod)''

| Empia EM2882 (USB bridge)
| {{yes}}
| {{no}}
| ?
| align="left" valign="top" |
* aka KWorld PlusTV HD USB-315
* analog not fully tested?

|- align="center"
| align="left" valign="top" | '''[[KWorld]] [[KWorld ATSC 330U|ATSC 330U]]''' 
(eb1a:a316)
| 2.6.27
| align="left"|
*''Xceive XC3028 (tuner & analog demod)''
*''Samsung S5H1409 (digital demod)''

| Empia EM2883 (USB bridge)
| {{yes}}
| {{no}}
| ?
| align="left" valign="top" |
* aka KWorld PlusTV HD Hybrid Stick 330
* analog not fully tested?

|- align="center"
| align="left" valign="top" | '''[[KWorld]] [[KWorld ATSC 340U|ATSC 340U]]''' 
(1b80:a340)
| 2.6.36
| align="left"|
*''NXP TDA18271HD/C1 tuner''
*''LG LGDT3304 demodulator (D)''

| Empia EM2870
| {{yes}}
| {{yes}}
| ?
| align="left" valign="top" |
* is identical to the newer [[KWorld_UB435-Q_USB_ATSC_TV_Stick|UB435-Q USB ATSC TV Stick]], save for using the oler /C1 tuner rev.

|- align="center"
| align="left" valign="top" | '''[[KWorld]] [[KWorld_UB435-Q_USB_ATSC_TV_Stick|UB435-Q USB ATSC TV Stick]]''' 
(1b80:a340)
| 2.6.36
| align="left"|
*''NXP TDA18271HD/C2 tuner''
*''LG LGDT3304 demodulator (D)''

| Empia EM2870
| {{yes}}
| {{yes}}
| ?
| align="left" valign="top" |
* is identical to the older [[KWorld ATSC 340U|ATSC 340U]], save for using the newer /C2 tuner rev.
* '''Caution''': another model variant (1b80:e346] of the UB435-Q exists but is currently unsupported (see device page)

|- align="center"
| align="left" valign="top" | '''[[OnAir|OnAir/Sasem]] [[OnAir USB HDTV|USB HDTV]]'''
| 2.6.26
| align="left"|
*''FCV1236D tuner''
*''LG DT3302 demodulator (D)''
| Cypress FX2LP (CY7C68013A)
| {{yes}}
| {{yes}}
| {{yes}}
| align="left" valign="top" |
* S-Video & Composite inputs
* hardware analog mpeg2 encoder

|- align="center"
| align="left" valign="top" | '''[[OnAir]] [[OnAir USB HDTV Creator|USB HDTV Creator]]'''
| 2.6.26
| align="left"| LG Innotek TDVS-H064F
*''TAU6034 tuner''
*''TDA9887 demodulator (A)''
*''LG DT3303 demodulator (D)''
| Cypress FX2LP (CY7C68013A)
| {{yes}}
| {{yes}}
| {{yes}}
| align="left" valign="top" |
* S-Video & Composite inputs
* hardware analog mpeg2 encoder

|- align="center"
| align="left" valign="top" | '''[[Pinnacle]] [[Pinnacle PCTV HD Stick (801eSE)|PCTV HD Stick (801eSE)]]'''
| 2.6.28
| align="left"|
*''XC5000 tuner''
*''Samsung S5H1411 (D)''
| Dibcom DIB0700
| {{yes}}
| {{yes}}
| {{no}}[[#fn_1|1]]
| align="left" valign="top" |

|- align="center"
| align="left" valign="top" | '''[[Pinnacle]] [[Pinnacle PCTV HD Pro Stick (800e)|PCTV HD Pro Stick (800e)]]'''
| 2.6.27
| align="left"|
*''XC3028 tuner''
*''LG DT3303 demodulator (D)''
| Empia EM2883
| {{yes}}
| {{no}}
| {{yes}}
| align="left" valign="top" |
* S-Video & Composite inputs (breakout dongle)

|- align="center"
| align="left" valign="top" | '''[[Pinnacle]] [[Pinnacle PCTV HD Pro Stick (801e)|PCTV HD Pro Stick (801e)]]'''
| 2.6.28
| align="left"|
*''XC5000 tuner''
*''Samsung S5H1411 (D)''
| Dibcom DIB0700
| {{yes}}
| {{yes}}
| {{no}}[[#fn_1|1]]
| align="left" valign="top" |
* S-Video & Composite inputs [[#fn_1|1]] (breakout dongle)

|}

*<cite id="fn_1">[[#fn_1_back|Note 1:]] </cite> Hardware should allow it, but the driver has no analog support. 

===Experimental Support===
{{Note|Do not let the "experimental" tag scare you, as the level of device functionality may actually be quite high. After additional testing and/or feature work, the drivers for these devices may eventually make their way into the main V4L-DVB development repository and become candidates for inclusion into the Linux kernel.}}

Experimental support for the following devices can be found:
* [[DViCO]] [[DViCO FusionHDTV5 USB nano|FusionHDTV5 USB nano]] ... available in Korea only?
* [[Pinnacle]] [[Pinnacle PCTV HD Mini Stick (80e)|PCTV HD Mini Stick (80e)]]
* [[Sabrent]] [[Sabrent TV-USBHD|TV-USBHD]] .... [http://marc.info/?l=linux-dvb&m=122781416815646&w=2 see here] and [http://www.mail-archive.com/linux-media@vger.kernel.org/msg07239.html here]
* [[Shenzhen Forward Video]] [[Shenzhen Forward Video AnyTV-ATSC Stick|AnyTV-ATSC Stick]] (AUTV002) [http://marc.info/?l=linux-dvb&m=122781416815646&w=2 see here] ... you currently can easily find them on listed ebay
** Note: Shenzhen lists two models, AUTV001 & AUTV002. Visually, they appear to be the same, though they could differ .... Also based upon appearance, they resemble the LifeView TV Walker series, however, the AUTV002, at the very least, seems to lack the telltale signs of being a LifeView OEM [http://marc.info/?l=linux-dvb&m=122748897727068&w=2]

==Currently Unsupported ATSC USB Devices==
{{help to support}}

* [[ADS Tech]] [[ADS Tech Mini HDTV USB (PTV-384-EF)|Mini HDTV USB (PTV-384-EF)]]
* [[Aeromax]] [[Aeromax UAH3001 USB 2.0 ATSC Hybrid Receiver|UAH3001 USB 2.0 ATSC Hybrid Receiver]] ... you'll see them on ebay
* [[AITech]] [[AITech HDTV USB 2.0|HDTV USB 2.0]]
* [[Anysee]] [[Anysee K30|K30]] ... available in Korea only?
* [[Anysee]] [[Anysee K50|K50]] ... available in Korea only? (highly similar to the [[DViCO FusionHDTV5 USB Gold]])
* [[Artec]] [[Artec T14A|T14A]]
* [[ASUS]] [[ASUS My Cinema U3100Mini USB ATSC]]
* [[ATI/AMD]] [[ATI/AMD TV Wonder Digital Cable Tuner|TV Wonder Digital Cable Tuner]] ... will likely never be supported (i.e cablecard)
* [[ATI/AMD]] [[ATI/AMD TV Wonder 650 Combo USB|TV Wonder 650 Combo USB]]
** VisionTek TV Wonder 650 Combo USB & VisionTek TV Wonder 650 Combo USB for Mac
* [[AVerMedia]] [[AVerMedia AverTV Hybrid Ultra USB (AP6R)|AverTV Hybrid Ultra USB (AP6R)]]
* [[AVerMedia]] [[AVerMedia AverTV Hybrid Ultra USB (M039)|AverTV Hybrid Ultra USB (M039)]]
* [[AVerMedia]] [[AVerMedia AVerTV Hybrid Volar Max (H826)|AVerTV Hybrid Volar MAX (H826)]]
* Ceton 5102-DCT04EX-USB ... InfiniTV 4 USB: Quad-CableCARD TV Tuner
* [[Diamond Multimedia]] [[Diamond Multimedia XtremeTV HDTV100|XtremeTV HDTV100]] (this device may actually be similar to the above Hauppauge, Pinnicle and Elgato devices though, so it might work)
* Diamond TV Wonder HD 750 USB
* [[DViCO]] [[DViCO FusionDMB2|FusionDMB2]] ... available in Korea only?
* Encore ENUTV-DAT
* Encore ENUTV-DAQ
* [[FujiPlus]] [[FujiPlus FD-USB728|FD-USB728]]
* [[Geniatech]] [[Geniatech HDTV THRILLER USB A680|HDTV THRILLER USB A680]] ... a usb box
* [[Geniatech]] [[Geniatech HDTV THRILLER USB U6800A|HDTV THRILLER USB U6800A]] ... a usb box ... (no idea how it differs from the visually identical A680 model)
* [[Geniatech]] [[Geniatech HDTV THRILLER USB U6010A|HDTV THRILLER USB U6010A]] (this device may actually be similar to the above Hauppauge, Pinnicle and Elgato usb stick devices, so it might work or be made to work with an addition of its subsystem ID to the driver)
** also sold as the Anyware GT-U6010A [http://www.anywareus.com/products/usb/gtu6010a.html]
* [[Geniatech]] [[Geniatech HDTV THRILLER USB U6012A|HDTV THRILLER USB U6012A]]
* Hauppauge WinTV-DCR-2650 (CableCARD TV Tuner) 1450
* [[KWorld]] [[KWorld ATSC 310U|ATSC 310U]]
* [[KWorld UB445-U ATSC Hybrid TV Stick|UB445-U ATSC Hybrid TV Stick]] 1b80:e421 (Afatech bridge?)
* [[Miglia]] [[Miglia TVMini HD|TVMini HD]]
* [[Miglia]] [[Miglia TVMini HD+|TVMini HD+]]
* MSI DIGIVOX ATSC
* MyGica U5072 .. rebranded Geniatech products
* MyGica U6012B ... rebranded Geniatech products
* [[OnAir]] [[OnAir GT|GT]] ... (highly similar to the [[DViCO FusionHDTV5 USB Gold]])
* [[Pinnacle]] [[Pinnacle PCTV HD Ultimate Stick (880e)|PCTV HD Ultimate Stick (880e)]]
* [[Plextor]] [[Plextor PX-HDTV500U|PX-HDTV500U]]
* [[SIGMACOM]] [[SIGMACOM SIGMA HDTV5 USB v1|SIGMA HDTV5 USB v1]] ... available in Korea only?
* [[TechniSat]] [[TechniSat Air2PC-ATSC-USB|Air2PC-ATSC-USB]] (BCM version)
* [[TechniSat]] [[TechniSat Air2PC-ATSC-USB|Air2PC-ATSC-USB]] (Nxt2002 version)
* [[TechniSat]] [[TechniSat AirStar-HD5000-USB|AirStar-HD5000-USB]]
* [[10Moons]] [[UAC880Q]] ... catch them on ebay
* [[TwinHan]] [[TwinHan TwinhanDTV ATSC / NTSC Dongle|TwinhanDTV ATSC / NTSC Dongle]]
* [[VBox]] [[VBox Cat's Eye USB-A 3560|Cat's Eye USB-A 3560]]
 

==Also See==
* [[DVB via USB|General Information Regarding DVB via USB]]
[[Category:ATSC]]
[[Category:USB]]

Technical Background

2012-08-14T21:31:18Z

CityK: add some analogue video/tv standards

__NOTOC__
__NOEDITSECTION__
<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;">
{| style="background-color:#F7F9FB;" cellspacing=0 cellpadding=5 border=0
| valign=top | [[Image:Technical_background_icon.png|50px|]]
|
=='''Technical Background:'''==
|}

{|valign=top cellpadding=0 cellspacing=0 width=100%

|valign=top bgcolor=#F7F9FB width=48%|
[[Image:Systems_icon.png|50px]] '''Systems:''' 

* [[Analog TV]]
** [[NTSC]]
** [[PAL]]
** [[SECAM]]
* [[Radio Data System (RDS)]]
* [[Digital TV|Digital TV (DTV)]]
** [[ATSC|ATSC Standards]]
** [[DVB Standards]]
** [[DMB-T/H|DMB-T/H Standard]]
** [[ISDB|ISDB Standards]]
* [[Modulation Scheme]]s used for Analog & DTV
* [[MPEG-2 Standard]]
** [[DSM-CC Object Carousel Protocol]]
* [[DiSEqC|DiSEqC Protocols]]

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|

[[Image:Chipset_icon.png|50px]]'''Hardware Component/Chipsets Related:''' 

* [[List of Chipset Vendors|Sortable List of Chipset Vendors]]
* [[Anatomy of V4L-DVB devices]]
** [[Tuner]]s
** [[Demodulator]]s
** [[A/V Decoders]]
*** [[Radio devices|Radio Decoder Chipsets]]
** [[GPIO pins]]
** [[I²C Protocol]]
** [[Hardware or Software Decoder?]] (MPEG)
** [[Hardware vs software encoders]] (MPEG)
** [[Remote Controller chipsets]]
** [[Interface chipsets]]
|}

</div>

Digital Video Broadcasting

2012-08-14T21:29:41Z

CityK: minor descriptional fixes

The term '''Digital Video Broadcasting''' (short '''DVB''') is originally a synonym for '''Digital TV''' (short '''DTV'''), and refers to telecommunication systems that send TV signals by way of digital transmission schemes, in contrast to the older, traditional, methods of signal transmission employed by [[Analog TV]] systems.

In general, Digital TV, or if you prefer '''D'''igital '''V'''ideo '''B'''roadcasting, consists of the transmission of data packets which carry encoded video/audio, and other payload data (such as EPG information), that has been combined and encapsulated within [[MPEG-2 Transport Stream]]s. Digital TV signals will adhere to a particular standard which will, suiting to the type of transmission pathway involved, define the specific way the digital video streams used in transmissions are encoded. Specifically, for each standard, the [[Modulation Scheme]], [[Frequency|frequencies]], transmission parameters and other factors are outlined and optimized for different transmission networks and target devices.

On the technical side, the acronym "DVB" is a synonym for the suite of [[DVB Standards]] developed and maintained by the [[DVB Project]]. Key standards from that aggregate include:
* [[DVB-S]] - Digital Video Broadcasting - Satellite -- the DVB standard for satellite based digital television transmission
* [[DVB-S2]] -Digital Video Broadcasting - Satellite - Second Generation
* [[DVB-C]] - Digital Video Broadcasting - Cable -- the DVB standard for digital television transmissions over Cable Networks ... also see ITU-T J.83 Annex A
* [[DVB-T]] - Digital Video Broadcasting - Terrestrial -- the DVB standard for digital television transmission over terrestrial airwaves ... i.e. [[OTA|Over/off-the-air ("OTA")]] signals received with a normal TV antenna
** [[DVB-H]] - Digital Video Broadcasting - Handheld -- the DVB standard for digital television transmission over terrestrial airwaves ... i.e. [[OTA|Over/off-the-air ("OTA")]] signals received with a handheld mobile device
* [[DVB-T2]] - Digital Video Broadcasting - Terrestrial -- Second Generation

While much of the world utilises the above mentioned [[DVB Standards]], other regions have opted for other Digital TV systems instead. For example:
* [[ATSC]] - The standard used in North America and S.Korea for digital television broadcast over terrestrial airwaves ([[OTA]])
** [[ATSC-M/H]] - the ATSC standard for digital television transmission over terrestrial airwaves received with a mobile device
** ITU-T J.83, Annex B [http://www.itu.int/rec/T-REC-J.83-200712-I/en] / ANSI/SCTE 07 (formerly SCTE DVS-031) [http://www.scte.org/content/index.cfm?pID=102] / OpenCable™ / DOCSISTM -- defining the standard for digital television transmission over cable networks in North America
* [[DTMB]] - Digital Terrestrial Multimedia Broadcast (formerly known as DMB-T/H) -- The standard used in China and Hong Kong for digital television broadcast over terrestrial airwaves ([[OTA]]), for both fixed location and mobile devices
* [[ISDB]] (Integrated Services Digital Broadcasting) - The standards used in Japan and many South American countries, for digital television broadcasting. Key standards from that aggregate include:
** [[ISDB-T]] -- the ISDB standard for digital television transmission over terrestrial airwaves ... i.e. [[OTA|Over/off-the-air ("OTA")]] signals received with a normal TV antenna
*** [[1seg]] -- the ISDB standard for digital television transmission over terrestrial airwaves received with a handheld mobile device
** [[ISDB-S]] -- the ISDB standard for satellite based digital television transmission
** [[ISDB-C]] -- the ISDB standard for digital television transmissions over Cable Networks

== External Links ==
* [[Wikipedia:DTV|Digital Television Article on Wikipedia, includes some nice historical Facts]]
* [http://www.dvb.org/ The DVB Consortium]
* [[wikipedia:DVB|Wikipedia's DVB article]]
* [http://www.dba.org.au/ DVB information site in Australia]
* [http://www.atsc.org/ The Advanced Television Systems Committee, specifies the ATSC standards]
* [http://www.scte.org/home.cfm SCTE homepage]
* [[wikipedia:SCTE|wikipedia's SCTE article]]
* [http://www.itu.int/ITU-T/ ITU-T homepage]
* [[wikipedia:ITU-T|wikipedia's ITU-T article]]
* [[wikipedia:ISDB|wikipedia's ISDB article]]

[[Category:Technology]]
[[Category:Shorthand]]

TV Related Software

2012-08-14T21:25:03Z

CityK: add ktv (another MPlayer FE) to the analogue tv list

__NOEDITSECTION__
<div style="margin:0; border:1px solid #6289AB; padding:0.5em; background-color:#F7F9FB;">
{| style="background-color:#F7F9FB;" cellspacing=0 cellpadding=5 border=0
| valign=top | [[Image:Software_viewing_apps_icon.png|50px]]
|
= '''TV Related Software:'''=
|}
Here, we aim to provide useful information about software applications that are directly related to or which are generally useful in some respect to the reception and manipulation of TV signals on Linux based computer systems.

In order to be most useful for the reader, this page is divided into two sections:
* A categorical overview of software
* An alphabetical listing of software

{{Note|''If you're new to this aspect of computing, rather than trying single programs one after another, you might be more interested in how to quickly get a fully working system as described in the "[[Example setups]]" page. Or perhaps instead you may simply want to perform some quick tests on your system, such as like those outlined in the "[[Testing your DVB device]]" article.''}} 

__TOC__
=A Categorical Overview=
==Utility Suites and Standalone Tools==
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|

===Analogue Utility Suites or Standalone Tools===
* [[dov4l2]] [http://www.vanheusden.com/dov4l2/]
* [[v4l2-utils]]
* [[v4l2ucp]]
* [[V4L Test Suite]]
* [[xawtv]]

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|

===DVB Utility Suites and Standalone Tools===

* [[LinuxTV dvb-apps]]
* [[DVB tools]]
* [[dvbsak]]
* [[ZapDvb]]
* [[dvbd]]
* [[JustDvb-It]]
|}

==Tools for performing frequency scans==
* [[Frequency scan|Frequency Scanning]]
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue Tools for performing frequency scans===
* [[scantv]] (part of the [[Xawtv#Associated_Utilities|xawtv package]])
|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===DVB Tools for performing frequency scans===
... also see [[Testing your DVB device]] (PCI, USB, ...) ... scan & zap stuff
* [[scan]]
* [[dvbscan|dvbscan/scandvb/atscscan]]
* [[w_scan]]
* [[scan-s2]]
* [[scte65scan]] [http://www.mythtv.org/wiki/Scte65scan] [http://forums.sagetv.com/forums/showthread.php?t=45474] [http://scte65scan.sourceforge.net/]
|}

==Tools for tuning==
* [[Tuning]]
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue Tools for tuning===
|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===DVB Tools for tuning===
... also see [[Testing your DVB device]] (PCI, USB, ...) ... scan & zap stuff
* [[zap|{a,s,c,t}zap]]
* [[dvbsnoop]]
* [[dvbtune]]
* [[szap-s2]]
|}

==Tools for signal strength==
* [[Testing reception quality]]
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue Tools for signal strength===
|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===DVB Tools for signal strength===
* [[femon]]
|}

==Standalone Software to Watch & Record TV==
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|

===Standalone Software to Watch Analogue TV===
* [[fftv]] [http://fftv.sourceforge.net/] -- tv/radio viewer/recorder -- [http://sourceforge.net/project/showfiles.php?group_id=71197 sourcecode]
* [[Gnometv]] [http://gnometv.sourceforge.net/]
* [[Gv4l]] [http://gv4l.sourceforge.net/]
* [[kdetv]] (also formerly known as [[QtVision]], the rewrite of the former [[KWinTV]])
* [[ktv]] [http://jerous.thimhallan.org/static//ktv/]
* [[LinTV]]
* [[MPlayer]]
** [[SMPlayer]] [http://smplayer.sourceforge.net/]
* [[tvtime]] [http://tvtime.sourceforge.net/]
* [[TV-Viewer]] (for Hardware MPEG2 Encoder cards)
* [[VLC media player]]
* [[xawtv]]
** [[MoTV]]
* [[XdTV]]
* [[Xine]]
* [[Zapping]] [http://zapping.sourceforge.net/Zapping/index.html] - a TV viewer for the Gnome desktop.
... also see [[V4L TV Viewing]]

===Analogue Capturing / Frame Grabbing Utilities===
* [[V4L capturing]] ... also see [[Transcode]]

* [[DVR]] [http://www.pierrox.net/dvr/]
* [[Grabby]] [http://www.vanheusden.com/grabby/]
* [[Streamer]]
* VideoDog [http://linux.softpedia.com/get/Multimedia/Video/VideoDog-9261.shtml] [http://linux.die.net/man/1/videodog]
* [[WebVCR+]] [http://webvcrplus.sourceforge.net/index.html]

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|

===Standalone Software to Watch Digital TV ===
* [[Antenna DTV]]
* [[gdvb]]
* [[gnutv]]
* [[Kaffeine]]
** [[KaxTV]]
* [[Klear]]
* [[Me TV]]
* [[MPlayer]]
** [[SMPlayer]] [http://smplayer.sourceforge.net/]
* [[VLC media player]]
* [[xawtv]] ... (only version 4 for DVB)
* [[XdTV]]
* [[Xine]]
** [[gxine]]

===DVB Tools for unattended/headless recording===
* [[dvbsched]] (in [[dvbd]])
* [[dvbrecord]] (in [[dvbsak]])
* [[atscap]]
* [[DvbCronRecordingPlugin]] for Trac

''Misc ''Tutorials, Howtos, Usage Info & Guides:''
* Howto record [[multiple programs]] at once
|}

==Media Player Software==
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Media Center Software===
In addition to offline playback of captured & downloaded media material, many will feature live TV viewing and capturing facilities
* [[Elisa]] [http://elisa.fluendo.com/]
* [[Entertainer Project]] [http://www.entertainer-project.com/features.php]
* [[Freevo]]
* [[GeeXboX]]
* [[Home Theater System]]
** showtime (OpenGL-based media player)
** tvheadend (TV streaming server)
* [[LinuxMCE]] [http://www.linuxmce.com/] Linux media center - A forked project from [[pluto]]
* [[Morphine.TV]] [http://wiki.morphine.tv/tiki-custom_home.php]
* [[My Media System]] [http://mymediasystem.org/]
* [[MythTV]]
* [[Mini DVB Linux]] ??
* [[oxine]] [http://oxine.sourceforge.net/]
* [[pluto]]
* [[Rage]] [http://www.rasterman.com/index.php?page=News (see the Monday, 27 March 2006 entry)]
* [[SageTV]] [http://sagetv.com/linuxOEMedition.html]
* [[VDR]] - VDR is one of the most popular TV applications. It features watching TV, recording storage on disk, EPG, Dolby Digital, playback, multi language and much more. VDR, although originally written for FF cards, works also with budget cards, if one installs the [[VDR Software Decoder Plugin]].
* XBMC [http://xbmc.org/]
* [[Yahdr]] 
...
|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===Media Center Distributions===
Complete operating systems tailored for easy installation of everything required to have a media centre.
* [[iMedia MythTV Linux]] [http://www.mini-box.com/iMediaMythTV]
* Knoppmyth
* [[LinVDR]] [http://www.linvdr.org/projects/linvdr/index.en.php] -- this was a Linux distro based around VDR. Now ancient history
* [[MiniMyth]] [http://linpvr.org/minimyth/]
* Mythbuntu
* MythDora
...

===Standalone Media Players===
i.e. for offline playback of captured materials
* [[Kaffeine]]
* [[Wikipedia:KMPlayer|KMPlayer]]
* [[MPlayer]]
** [[SMPlayer]] [http://smplayer.sourceforge.net/]
* [[Totem]]
* [[VLC media player]]
* [[Xine]]
...

|}

==Network and Streaming Tools==
* [[Streaming]]
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue TV Streaming Utilities===
* [[Streaming-V4L]]
* [[GStreamer]]

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===Network Tools for DVB Streams===
* [[dvbshout]]
* [[dvbsnoop]]
* [[dvbstream]]
* [[DVBStreamer]]
* [[dvbyell]]
* [[getstream]]
* [[Me TV]]
* [[mumudvb]]
* [[Home Theater System|TVheadend]]

===Streaming Software for Digital TV===
* [[dvbice]]
* [[VLC media player]]
|}

==Tools to Show Videotext/Teletext/Interactive Content/Closed Captioning==
* [[Text capture]]
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue TV Tools to Show Videotext/Teletext/Interactive Content/Closed Captioning===
* [[AleVT]]
* [[mtt]] (part of the [[Xawtv#Associated_Utilities|xawtv package]] ... both v3 and v4)

|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
===DVB Tools to Show Videotext/Teletext/Interactive Content/Closed Captioning===
* [[AleVT]] - v1.7.0 or a patched v1.6.2
* [[mtt]] - (part of the [[Xawtv#Associated_Utilities_2|xawtv package]]... v4 only )
* [[RedButton MHEG Engine]]
|}

==Electronic Program Guide / EIT tools==
{|valign=top cellpadding=0 cellspacing=0 width=100%
|valign=top bgcolor=#F7F9FB width=32%|
===Analogue TV Program Guide Tools===
|valign=top bgcolor=#F7F9FB width=4%|
|valign=top bgcolor=#F7F9FB width=48%|
=== DVB Program Guide Tools===
* atsc_epg - included within the [[LinuxTV dvb-apps]]
* [[tv_grab_dvb]]
* [[dvbsnoop]]
* [[DVBStreamer]]
* LoadEPG [http://lukkinosat.altervista.org/]
* MediaHighWay EPG, mhwepg [http://jrepetto.free.fr/] [http://www.linuxtv.org/vdrwiki/index.php/Mhwepg]
* tv_grab_dvb_plus ( was tvgrabeit ) [http://sourceforge.net/projects/tvgrabeit/]
* [[XMLTV]]
|}

==Tools for Editing Captured TV content==
* [[Avidemux2]]
* [[dvbcut]]
* [[ProjectX]]
* [[MEncoder]]
''Misc ''Tutorials, Howtos, Usage Info & Guides:''
* [[Post-processing]] of recorded material
....

'''Examples of User TV Device Hardware and Software Configurations:'''
* [[Example setups]]

</div>

= An Alphabetical Listing =

{| class="wikitable sortable"
|+'''A Overview of Software Applications which are useful in regards to TV on a Linux based Computer System'''
|-
! Software Application !! Supports Analogue !! Supports DVB !! Recording Capabilities !! Offline Playback !! Editing Capabilities !! Channel storage !! Language !! class="unsortable"| Comments
|-
| [[AleVT]] || y || y || || || || || || Program to use Teletext/Videotext on analog and digital TV
|-
| [[Antenna DTV]] || n || y || y || n || n || t channels.conf format || Python || Watch, record and monitor signal level of digital TV
|-
| [[dvbd]] || || y || || || || || C++ || Traditional UNIX daemon for DVB
|-
| [[dvbice]] || n || y || y || || || || C || Recompress and stream audio and video to Icecast/HTTP in Theora/Vorbis
|-
| [[dvbsak]] || n || y || || || || || ||
|-
| [[dvbshout]] || n || y || || || || || || Stream radio to Icecast/multicast
|-
| [[dvbsnoop]] || n || y || || || || || C ||
|-
| [[dvbstream]] || n || y || y || n || n || || || a streaming utilitity. Part of the [[DVB tools]] project
|-
| [[DVBStreamer]] || n || y || || || || sqlite, XMLTV format || C || PSI/SI tracking and correctly streams all PIDs including PCR
|-
| [[dvbyell]] || n || y || n || n || n || || || A DVB streaming service.
|-
| [[gdvb]] || || || || || || || ||
|-
| [[GeeXboX]] || || || || || || || ||
|-
| [[getstream]] || n || y || || || || || ||
|-
| [[GStreamer]] || n || y || || || || || ||
|-
| [[Gv4l]] || || || || || || || || A GUI frontend for [[Transcode]]'s V4L functions
|-
| [[Kaffeine]] || n || y || y || y || n || own text format || C++ || Desktop TV Solution
|-
| [[KaxTV]] || || || || || || || || obsoleted
|-
| [[Klear]] || || y || || || || || ||
|-
| [[LinuxTV dvb-apps]] || n || y || y || ? || ? || {a,c,t,s} channels.conf formats|| C || contains dvbscan, {a,c,t,s}zap ...
|-
| [[MEncoder]] || y || y || y || n || y || || C || encoding suite of tools
|-
| [[Me TV]] || n || y || y || n || n || SQLite || C++ || GNOME based DVB TV viewer
|-
| [[Mini DVB Linux]] || || y || || || || || || Distribution with live-CD
|-
| [[MPlayer]] || y || y || y || y || n || channels.conf || C || multi-functional media player
|-
| [[mumudvb]] || n || y || n || n || n || || || Stream multiples channels in multicast (each channel in different group)
|-
| [[MythTV]] || y || y || y || y || y || mysql || C++ || Media Center
|-
| [[pluto]] || || || || || || || ||
|-
| [[ProjectX]] || || || || || || || ||
|-
| [[RedButton MHEG Engine]] || || || || || || || || [[MHEG-5]] engine
|-
| [[scan-s2]] || n || y || n || n || n || || C || frequency scanning utility which supports DVB APIv5 (for DVB-S2)
|-
| [[Home Theater System | showtime]] || || || || || || || C || OpenGL-based media player
|-
| [[szap-s2]] || || y || y || || || || C || tuning utility which supports DVB APIv5 (for DVB-S2)
|-
| [[tv_grab_dvb]] || || y || || || || [[XMLTV]] format || C || dumps DVB [[EPG]] info in [[XMLTV]] format
|-
| [[Home Theater System | HTS Tvheadend]] || y || y || y || y || y || [[XMLTV]] format || C || TV streaming server
|-
| [[VDR]] || y * || y || y || y || y || VDR format channels.conf || C++ || analogue with plugins only DVB APIv5 since 1.7.2
|-
| [[VLC media player]] || || || || || || || ||
|-
| [[w_scan]] || n || y || n || n || n || VDR channels.conf kaffeine zap/xine tuning data for scan|| C || ATSC/DVB-C/S/S2/T frequency scanner
|-
| [[xawtv]] || y || y * || y || y || n || || || * only v4 supports DVB
|-
| [[XdTV]] || y || y || y || || || || || TV viewing app. Development stopped
|-
| [[xine]] || || y || y || y || || || || multi-functional media player
|-
| [[ZapDvb]] || || || || || || || ||

|}

[[Category:Software]]

Wiki - New Device Copy & Paste Template

2012-08-14T21:02:04Z

CityK: minor descriptional fix

{{Note|In essence, this page is a "copy and paste" template which users should use when establishing a new device article within the wiki. Its intended purpose is to serve as the basis for the format/layout of device articles; thereby striving to establish a general consistency throughout the wiki.

Usage:
* Once you have logged in to the wiki, open another browser tab or window and, in which, start creating a new device article
* Next, return to this article and click the "view source" tab at the top of the page. Then, copy the entire contents from the box displaying this page's wiki source code
* Then switch back to the new device page you are creating and, within the editing box at the bottom of it's page, paste the entire page code contents that you've just copied from the "New Device Copy & Paste Template" article
* Proceed then to edit your new device article page by filling in the various sections, replacing the template examples, with information relevant for the new device you are adding to the wiki. Be sure to delete ''=</nowiki>"#009000">the green italic directional comment sections'' provided by the template (as well as this notice)}} 

 ''First, if possible, we would like a good overall image of what the device looks like (Note: do NOT use proprietary images unless you have obtained permission to do so). 
''Next, provide a brief summary of what the device is and by whom it is provided (include wiki links to the card type and the vendor -- and, ideally, after you have finished editing this page, you should add links from those pages back to this one).'' 
''The last introductory piece of information is the all important indication of whether or not the device is supported under Linux. Here's an example:'' 

[[Image:Kworld_ATSC_115_front.jpg|right|thumb|200px|Example Image: Add a good overall image of what the device looks like here and perhaps a very brief description]]

An [[ATSC]] [[ATSC PCI Cards|PCI Card]] from [[KWorld]].

The ATSC 115 is supported under Linux since kernel 2.6.24.

''Note: The page contents menu will automagically build itself, so you need not worry about it''

==Overview/Features==
''Discuss the features and facets of the device here. For example:'' 

* PCI interface
* Inputs: Antenna (Composite), Remote and S-Video In

===Components Used===
''List the hardware ICs used by the device here. For example:'' 
* [[Quantek QT1010]] (tuner)
* [[Zarlink MT352|Intel/Zarlink MT352]] (demodulator)
* [[Philips SAA7134|NXP/Philips SAA7130HL]] (A/V decoder and PCI Interface)

===Other Images===
''Use the included code to insert other images if necessary. Add as many high resolution pictures as you can i.e the card, the original box, the remote and, when uploading the files to the wiki, give them detailed specific names. Note: only use images taken by yourself or those 3rd party images for which you have received express written consent (such as from a vendor) that permits their usage. For example:'' 
<gallery perrow=5>
Image:VideoMate_DVB-T220_box.jpg|VideoMate DVB-T220 Box
Image:VideoMate_DVB-T220_remote.jpg|VideoMate DVB-T220 Remote
</gallery>

===Identification===
''Provide here, for PCI/PCIe devices, the relevant output of <code>lspci -vnn</code> or, in the case of USB devices, <code>lsusb -v </code>. We're particularly interested in the subsystem ID's. To make a code block simply make the first character of each line a space. For example:'' 
# lspci -vvvnn
04:03.0 Multimedia controller [0480]: Philips Semiconductors SAA7130 Video Broadcast Decoder [1131:7130] (rev 01)
Subsystem: Compro Technology, Inc. Videomate DVB-T200 [185b:c901]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 84 (21000ns min, 8000ns max)
Interrupt: pin A routed to IRQ 20
Region 0: Memory at fdcfe000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-

==Making it Work==
''Is it supported under Linux? Are there experimental drivers? Does it partially work or identify as another card? (if yes, add this information below)''

===Firmware===
''Is there any firmware specific information for this device? if so, list it here. If your device doesn't require a firmware, simply mention that this is the case.''

===Drivers===
''Discuss the kernel driver modules used by the device here. Provide the details of where the drivers, any patches, and any other necessary tools are available.''

===Sample Kernel Output===
''Provide the '''relevant''' portion of dmesg here. For example:'' 
# dmesg
[ 45.569669] saa7130/34: v4l2 driver version 0.2.14 loaded
[ 45.569739] saa7130[0]: found at 0000:04:03.0, rev: 1, irq: 20, latency: 84, mmio: 0xfdcfe000
[ 45.569745] saa7130[0]: subsystem: 185b:c901, board: Compro Videomate DVB-T200 [card=71,autodetected]
[ 45.569753] saa7130[0]: board init: gpio is 843f00
[ 45.569809] input: saa7134 IR (Compro Videomate DV as /devices/pci0000:00/0000:00:1e.0/0000:04:03.0/input/input7
[ 45.755429] saa7130[0]: i2c eeprom 00: 5b 18 01 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
[ 45.755437] saa7130[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff
[ 45.755443] saa7130[0]: i2c eeprom 20: 01 40 01 03 03 ff 03 01 08 ff 00 88 ff ff ff ff
[ 45.755449] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 45.755454] saa7130[0]: i2c eeprom 40: ff d5 00 c4 86 1e ff ff ff ff ff ff ff ff ff ff
[ 45.755460] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb
[ 45.755466] saa7130[0]: i2c eeprom 60: 30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 45.755471] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 45.755478] saa7130[0]: Unexpected tuner type info: d5 in eeprom
[ 45.755532] saa7130[0]: registered device video0 [v4l2]
[ 45.755550] saa7130[0]: registered device vbi0
[ 45.873425] saa7134 ALSA driver for DMA sound loaded
[ 45.873448] saa7130[0]/alsa: saa7130[0] at 0xfdcfe000 irq 20 registered as card -2
[ 45.943354] saa7130[0]/dvb: frontend initialization failed

===Remote Control Support===
''Discuss support for the remote control here.''

===An Appropriate Title===
''If deemed necessary, create an additional heading (using an appropriate title) and add anything else that you think might be relevant''

==External Links==
''Provide a link to the vendor's product page here along with any other external link to information that is generally helpful in relation to the device. For example:'' 
* [http://www.comprousa.com/en/product/t100t220/t220.html Compro T-220 product page]

''Finally, the very last thing is to add a category. (Remove the nowiki tags). For example'' 
<nowiki>[[Category:DVB-T PCI Devices]]</nowiki>

Wiki - New Device Copy & Paste Template

2012-08-14T20:59:45Z

CityK: minor descriptional fixes

{{Note|In essence, this page is a "copy and paste" template which users should use when establishing a new device article within the wiki. Its intended purpose is to serve as the basis for the format/layout of device articles; thereby striving to establish a general consistency throughout the wiki.

Usage:
* Once you have logged in to the wiki, open another browser tab or window and in that start creating a new device article
* Next, return to this article and click the "view source" tab at the top of the page. Then, copy the entire contents from the box displaying this page's wiki source code
* Then switch back to the new device page you are creating and, within the editing box at the bottom of it's page, paste the entire page code contents that you've just copied from the "New Device Copy & Paste Template" article
* Proceed then to edit your new device article page by filling in the various sections, replacing the template examples, with information relevant for the new device you are adding to the wiki. Be sure to delete ''=</nowiki>"#009000">the green italic directional comment sections'' provided by the template (as well as this notice)}} 

 ''First, if possible, we would like a good overall image of what the device looks like (Note: do NOT use proprietary images unless you have obtained permission to do so). 
''Next, provide a brief summary of what the device is and by whom it is provided (include wiki links to the card type and the vendor -- and, ideally, after you have finished editing this page, you should add links from those pages back to this one).'' 
''The last introductory piece of information is the all important indication of whether or not the device is supported under Linux. Here's an example:'' 

[[Image:Kworld_ATSC_115_front.jpg|right|thumb|200px|Example Image: Add a good overall image of what the device looks like here and perhaps a very brief description]]

An [[ATSC]] [[ATSC PCI Cards|PCI Card]] from [[KWorld]].

The ATSC 115 is supported under Linux since kernel 2.6.24.

''Note: The page contents menu will automagically build itself, so you need not worry about it''

==Overview/Features==
''Discuss the features and facets of the device here. For example:'' 

* PCI interface
* Inputs: Antenna (Composite), Remote and S-Video In

===Components Used===
''List the hardware ICs used by the device here. For example:'' 
* [[Quantek QT1010]] (tuner)
* [[Zarlink MT352|Intel/Zarlink MT352]] (demodulator)
* [[Philips SAA7134|NXP/Philips SAA7130HL]] (A/V decoder and PCI Interface)

===Other Images===
''Use the included code to insert other images if necessary. Add as many high resolution pictures as you can i.e the card, the original box, the remote and, when uploading the files to the wiki, give them detailed specific names. Note: only use images taken by yourself or those 3rd party images for which you have received express written consent (such as from a vendor) that permits their usage. For example:'' 
<gallery perrow=5>
Image:VideoMate_DVB-T220_box.jpg|VideoMate DVB-T220 Box
Image:VideoMate_DVB-T220_remote.jpg|VideoMate DVB-T220 Remote
</gallery>

===Identification===
''Provide here, for PCI/PCIe devices, the relevant output of <code>lspci -vnn</code> or, in the case of USB devices, <code>lsusb -v </code>. We're particularly interested in the subsystem ID's. To make a code block simply make the first character of each line a space. For example:'' 
# lspci -vvvnn
04:03.0 Multimedia controller [0480]: Philips Semiconductors SAA7130 Video Broadcast Decoder [1131:7130] (rev 01)
Subsystem: Compro Technology, Inc. Videomate DVB-T200 [185b:c901]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 84 (21000ns min, 8000ns max)
Interrupt: pin A routed to IRQ 20
Region 0: Memory at fdcfe000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-

==Making it Work==
''Is it supported under Linux? Are there experimental drivers? Does it partially work or identify as another card? (if yes, add this information below)''

===Firmware===
''Is there any firmware specific information for this device? if so, list it here. If your device doesn't require a firmware, simply mention that this is the case.''

===Drivers===
''Discuss the kernel driver modules used by the device here. Provide the details of where the drivers, any patches, and any other necessary tools are available.''

===Sample Kernel Output===
''Provide the '''relevant''' portion of dmesg here. For example:'' 
# dmesg
[ 45.569669] saa7130/34: v4l2 driver version 0.2.14 loaded
[ 45.569739] saa7130[0]: found at 0000:04:03.0, rev: 1, irq: 20, latency: 84, mmio: 0xfdcfe000
[ 45.569745] saa7130[0]: subsystem: 185b:c901, board: Compro Videomate DVB-T200 [card=71,autodetected]
[ 45.569753] saa7130[0]: board init: gpio is 843f00
[ 45.569809] input: saa7134 IR (Compro Videomate DV as /devices/pci0000:00/0000:00:1e.0/0000:04:03.0/input/input7
[ 45.755429] saa7130[0]: i2c eeprom 00: 5b 18 01 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
[ 45.755437] saa7130[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff
[ 45.755443] saa7130[0]: i2c eeprom 20: 01 40 01 03 03 ff 03 01 08 ff 00 88 ff ff ff ff
[ 45.755449] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 45.755454] saa7130[0]: i2c eeprom 40: ff d5 00 c4 86 1e ff ff ff ff ff ff ff ff ff ff
[ 45.755460] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb
[ 45.755466] saa7130[0]: i2c eeprom 60: 30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 45.755471] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 45.755478] saa7130[0]: Unexpected tuner type info: d5 in eeprom
[ 45.755532] saa7130[0]: registered device video0 [v4l2]
[ 45.755550] saa7130[0]: registered device vbi0
[ 45.873425] saa7134 ALSA driver for DMA sound loaded
[ 45.873448] saa7130[0]/alsa: saa7130[0] at 0xfdcfe000 irq 20 registered as card -2
[ 45.943354] saa7130[0]/dvb: frontend initialization failed

===Remote Control Support===
''Discuss support for the remote control here.''

===An Appropriate Title===
''If deemed necessary, create an additional heading (using an appropriate title) and add anything else that you think might be relevant''

==External Links==
''Provide a link to the vendor's product page here along with any other external link to information that is generally helpful in relation to the device. For example:'' 
* [http://www.comprousa.com/en/product/t100t220/t220.html Compro T-220 product page]

''Finally, the very last thing is to add a category. (Remove the nowiki tags). For example'' 
<nowiki>[[Category:DVB-T PCI Devices]]</nowiki>

Wiki - New Device Copy & Paste Template

2012-08-14T03:52:16Z

CityK: change to 'view source'

{{Note|In essence, this page is a "copy and paste" template which users should use when establishing a new device article within the wiki. Its intended purpose is to serve as the basis for the format/layout of device articles; thereby striving to establish a general consistency throughout the wiki.

Usage:
* Once you have logged in, start creating a new device article in another browser tab or window.
* Next, return to this article and click the View Source tab at the top of its page. Then, copy the entire contents of this article from within the article's source box
* Switch back to the new device page you are creating and within the editing box at the bottom of it's page, paste the entire page contents you've copied from the "New Device Copy & Paste Template" article
* Proceed to edit your new device article page by filling in the various sections, replacing the template examples, with information relevant for the new device you are adding to the wiki. Be sure to delete ''=</nowiki>"#009000">the green italic directional comment sections'' provided by the template (as well as this notice)}} 

 ''First, if possible, we would like a good overall image of what the device looks like (Note: do NOT use proprietary images unless you have obtained permission to do so). 
''Next, provide a brief summary of what the device is and by whom it is provided (include wiki links to the card type and the vendor -- and, ideally, after you have finished editing this page, you should add links from those pages back to this one).'' 
''The last introductory piece of information is the all important indication of whether or not the device is supported under Linux. Here's an example:'' 

[[Image:Kworld_ATSC_115_front.jpg|right|thumb|200px|Example Image: Add a good overall image of what the device looks like here and perhaps a very brief description]]

An [[ATSC]] [[ATSC PCI Cards|PCI Card]] from [[KWorld]].

The ATSC 115 is supported under Linux since kernel 2.6.24.

''Note: The page contents menu will automagically build itself, so you need not worry about it''

==Overview/Features==
''Discuss the features and facets of the device here. For example:'' 

* PCI interface
* Inputs: Antenna (Composite), Remote and S-Video In

===Components Used===
''List the hardware ICs used by the device here. For example:'' 
* [[Quantek QT1010]] (tuner)
* [[Zarlink MT352|Intel/Zarlink MT352]] (demodulator)
* [[Philips SAA7134|NXP/Philips SAA7130HL]] (A/V decoder and PCI Interface)

===Other Images===
''Use the included code to insert other images if necessary. Add as many high resolution pictures as you can i.e the card, the original box, the remote and, when uploading the files to the wiki, give them detailed specific names. Note: only use images taken by yourself or those 3rd party images for which you have received express written consent (such as from a vendor) that permits their usage. For example:'' 
<gallery perrow=5>
Image:VideoMate_DVB-T220_box.jpg|VideoMate DVB-T220 Box
Image:VideoMate_DVB-T220_remote.jpg|VideoMate DVB-T220 Remote
</gallery>

===Identification===
''Provide here, for PCI/PCIe devices, the relevant output of <code>lspci -vnn</code> or, in the case of USB devices, <code>lsusb -v </code>. We're particularly interested in the subsystem ID's. To make a code block simply make the first character of each line a space. For example:'' 
# lspci -vvvnn
04:03.0 Multimedia controller [0480]: Philips Semiconductors SAA7130 Video Broadcast Decoder [1131:7130] (rev 01)
Subsystem: Compro Technology, Inc. Videomate DVB-T200 [185b:c901]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 84 (21000ns min, 8000ns max)
Interrupt: pin A routed to IRQ 20
Region 0: Memory at fdcfe000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [40] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-

==Making it Work==
''Is it supported under Linux? Are there experimental drivers? Does it partially work or identify as another card? (if yes, add this information below)''

===Firmware===
''Is there any firmware specific information for this device? if so, list it here. If your device doesn't require a firmware, simply mention that this is the case.''

===Drivers===
''Discuss the kernel driver modules used by the device here. Provide the details of where the drivers, any patches, and any other necessary tools are available.''

===Sample Kernel Output===
''Provide the '''relevant''' portion of dmesg here. For example:'' 
# dmesg
[ 45.569669] saa7130/34: v4l2 driver version 0.2.14 loaded
[ 45.569739] saa7130[0]: found at 0000:04:03.0, rev: 1, irq: 20, latency: 84, mmio: 0xfdcfe000
[ 45.569745] saa7130[0]: subsystem: 185b:c901, board: Compro Videomate DVB-T200 [card=71,autodetected]
[ 45.569753] saa7130[0]: board init: gpio is 843f00
[ 45.569809] input: saa7134 IR (Compro Videomate DV as /devices/pci0000:00/0000:00:1e.0/0000:04:03.0/input/input7
[ 45.755429] saa7130[0]: i2c eeprom 00: 5b 18 01 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
[ 45.755437] saa7130[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff
[ 45.755443] saa7130[0]: i2c eeprom 20: 01 40 01 03 03 ff 03 01 08 ff 00 88 ff ff ff ff
[ 45.755449] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 45.755454] saa7130[0]: i2c eeprom 40: ff d5 00 c4 86 1e ff ff ff ff ff ff ff ff ff ff
[ 45.755460] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb
[ 45.755466] saa7130[0]: i2c eeprom 60: 30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 45.755471] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[ 45.755478] saa7130[0]: Unexpected tuner type info: d5 in eeprom
[ 45.755532] saa7130[0]: registered device video0 [v4l2]
[ 45.755550] saa7130[0]: registered device vbi0
[ 45.873425] saa7134 ALSA driver for DMA sound loaded
[ 45.873448] saa7130[0]/alsa: saa7130[0] at 0xfdcfe000 irq 20 registered as card -2
[ 45.943354] saa7130[0]/dvb: frontend initialization failed

===Remote Control Support===
''Discuss support for the remote control here.''

===An Appropriate Title===
''If deemed necessary, create an additional heading (using an appropriate title) and add anything else that you think might be relevant''

==External Links==
''Provide a link to the vendor's product page here along with any other external link to information that is generally helpful in relation to the device. For example:'' 
* [http://www.comprousa.com/en/product/t100t220/t220.html Compro T-220 product page]

''Finally, the very last thing is to add a category. (Remove the nowiki tags). For example'' 
<nowiki>[[Category:DVB-T PCI Devices]]</nowiki>