ATSC PCI cards: Difference between revisions
Jump to navigation
Jump to search
(Update status of DViCO cards) |
(Add source locations for DViCO) |
||
| Line 10: | Line 10: | ||
My experience with capturing using the pcHDTV is that it uses 1.3% of CPU (azap + cat + cx88[0] dvb on an athlon64 3500). Actually watching live or captured streams does take a lot of CPU, though, especially without xvmc. --[[User:Mitchskin|Mitch]] 21:50, 14 May 2005 (CEST) |
My experience with capturing using the pcHDTV is that it uses 1.3% of CPU (azap + cat + cx88[0] dvb on an athlon64 3500). Actually watching live or captured streams does take a lot of CPU, though, especially without xvmc. --[[User:Mitchskin|Mitch]] 21:50, 14 May 2005 (CEST) |
||
The ATSC frontend of the DViCO cards has been tested with 8-VSB (OTA) and QAM-256 (Cable) in the US. |
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 CVS and latest Linux -mm tree. |
||
Revision as of 13:11, 7 July 2005
As of right now there are 4 confirmed working cards.
- The PCHDTV card
- The air2pc card
- The DViCO FusionHDTV 3 GOLD-Q
- The DViCO FusionHDTV 3 GOLD-T
The air2pc seems to take some work off the processor while I have read the PCHDTV uses 80-90% on an athalon64 3000.
My experience with capturing using the pcHDTV is that it uses 1.3% of CPU (azap + cat + cx88[0] dvb on an athlon64 3500). Actually watching live or captured streams does take a lot of CPU, though, especially without xvmc. --Mitch 21:50, 14 May 2005 (CEST)
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 CVS and latest Linux -mm tree.