ATSC PCI cards: Difference between revisions
(Split off into sections) |
mNo edit summary |
||
| Line 25: | Line 25: | ||
|style="background:#FFDEAD;"| VSB || yes || yes || yes || yes || yes || yes || yes || yes || yes || yes || yes || yes |
|style="background:#FFDEAD;"| VSB || yes || yes || yes || yes || yes || yes || yes || yes || yes || yes || yes || yes |
||
|- align="center" |
|- align="center" |
||
|style="background:#FFDEAD;"| QAM || yes || no || no<sup id="fn_5_back">[[#fn_5|5]]</sup> || yes || yes || yes || yes || yes || yes || |
|style="background:#FFDEAD;"| QAM || yes || no || no<sup id="fn_5_back">[[#fn_5|5]]</sup> || yes || yes || yes || yes || yes || yes || no<sup id="fn_6_back">[[#fn_6|6]]</sup> || yes || ? |
||
|- align="center" |
|- align="center" |
||
|style="background:#FFDEAD;"| NTSC || yes || no || no || no || yes || yes || yes || yes || no<sup id="fn_4_back">[[#fn_4|4]]</sup> || yes || no || yes |
|style="background:#FFDEAD;"| NTSC || yes || no || no || no || yes || yes || yes || yes || no<sup id="fn_4_back">[[#fn_4|4]]</sup> || yes || no || yes |
||
| Line 41: | Line 41: | ||
<cite id="fn_4">[[#fn_4_back|Note 4:]] </cite> Hardware should allow it, but the driver has no support yet.<br> |
<cite id="fn_4">[[#fn_4_back|Note 4:]] </cite> Hardware should allow it, but the driver has no support yet.<br> |
||
<cite id="fn_5">[[#fn_5_back|Note 5:]] </cite> The demodulator supports QAM-64/256, but the tuner can't handle cable frequencies.<br> |
<cite id="fn_5">[[#fn_5_back|Note 5:]] </cite> The demodulator supports QAM-64/256, but the tuner can't handle cable frequencies.<br> |
||
<cite id="fn_6">[[#fn_6_back|Note 6:]] </cite> Some may have had sucess. Recent attempts using currently shipping boards have failed<br> |
|||
==Air2PC== |
==Air2PC== |
||
The Air2PC cards usually consume less PCI and memory bandwidth than the other cards because they have a hardware PID filter. The hardware only handles a few streams, which may be limiting if collecting EIT data. The PID filtering is most useful when recording one program in a QAM-256 stream, or when recording low resolution streams. It doesn't save much bandwidth when recording an HDTV stream encoded with 8-VSB, since that set of streams consumes most of the bandwidth anyway. |
The Air2PC cards usually consume less PCI and memory bandwidth than the other cards because they have a hardware PID filter. The hardware only handles a few streams, which may be limiting if collecting EIT data. The PID filtering is most useful when recording one program in a QAM-256 stream, or when recording low resolution streams. It doesn't save much bandwidth when recording an HDTV stream encoded with 8-VSB, since that set of streams consumes most of the bandwidth anyway. |
||
Revision as of 02:58, 25 April 2006
As of right now there are 12 confirmed working devices.
- The pcHDTV HD-3000 card
- The air2pc (1st gen)
- The air2pc (2nd gen)
- The air2pc hd5000 (3rd gen)
- The DViCO FusionHDTV 3 GOLD-Q
- The DViCO FusionHDTV 3 GOLD-T
- The DViCO FusionHDTV 5 GOLD
- The DViCO FusionHDTV 5 LITE
- The DViCO FusionHDTV 5 USB GOLD
- The ATi HDTV Wonder
- The AVerMedia AVerTVHD A180
- The Kworld ATSC110
Here is a feature matrix to help keep track of what card does what:
| pcHDTV HD-3000 | Air2PC 1st | Air2PC 2nd | Air2PC HD5000 3rd | Fusion HDTV3 Gold-Q | Fusion HDTV3 Gold-T | Fusion HDTV5 Lite | Fusion HDTV5 Gold | Fusion HDTV5 USB Gold | HDTV Wonder | AVerTV HD A180 | Kworld ATSC 110 | |
| Frontend | or51132 | bcm3510 | nxt2002 | lgdt3303 | lgdt3302 | lgdt3302 | lgdt3303 | lgdt3303 | lgdt3303 | nxt2004 | nxt2004 | nxt2004 |
| Bridge Interface | cx23882 | flexcop | flexcop | flexcop | cx23882 | cx23882 | bt878 | cx23882 | Cypress FX2LP | cx23882 | saa7135 | saa7135 |
| VSB | yes | yes | yes | yes | yes | yes | yes | yes | yes | yes | yes | yes |
| QAM | yes | no | no5 | yes | yes | yes | yes | yes | yes | no6 | yes | ? |
| NTSC | yes | no | no | no | yes | yes | yes | yes | no4 | yes | no | yes |
| Comp/S-video | yes | no | no | no | yes | yes | yes1 | yes | no4 | yes | yes | yes |
| Analog CC | no2 | no | no | no | no2 | no2 | yes | no2 | ? | no2 | ? | ? |
| PID filtering3 | sw | hw | hw | hw | sw | sw | sw | sw | sw | sw | sw | sw |
Note 1: Has a working comp/s-video port hidden behind the card-plate.
Note 2: Hardware should allow it, but the cx88 driver has no support yet.
Note 3: 'hw' = hardware, 'sw' = software. Hardware PID filtering allows the card to discard unwanted packets. This typically amounts to saving <10% of the bitrate of a 8-VSB or QAM-64 broadcast, and >55% of the bitrate of a QAM-256 broadcast.
Note 4: Hardware should allow it, but the driver has no support yet.
Note 5: The demodulator supports QAM-64/256, but the tuner can't handle cable frequencies.
Note 6: Some may have had sucess. Recent attempts using currently shipping boards have failed
Air2PC
The Air2PC cards usually consume less PCI and memory bandwidth than the other cards because they have a hardware PID filter. The hardware only handles a few streams, which may be limiting if collecting EIT data. The PID filtering is most useful when recording one program in a QAM-256 stream, or when recording low resolution streams. It doesn't save much bandwidth when recording an HDTV stream encoded with 8-VSB, since that set of streams consumes most of the bandwidth anyway.
DViCO
The ATSC frontend of the DViCO cards has been tested with 8-VSB (OTA) and QAM-256 (Cable) in the US. Source code is in video4linux + dvb-kernel CVS and kernel sources 2.6.13 and later for Gold, 2.6.15 and later for Lite.