280
280
"spare" hardware may be an exercise in frustration and can waste many hours
281
281
of valuable time.
283
For more detail about actual configurations that others have used, Mark
284
Cooper has setup a hardware database at <url
285
url="http://pvrhw.goldfish.org/" name="http://pvrhw.goldfish.org/">. The
286
website will let you browse what other users have reported as their hardware
287
configuration, and how happy they are with the results.
289
283
If you have specific questions about the suitability of specific hardware
290
284
choices, you can consult the archives of the mythtv-users mailing list at
291
285
<url url="http://www.gossamer-threads.com/lists/mythtv/"
340
334
The second mode of operation is where MythTV is paired with a hardware-based
341
video encoder, such as a Matrox G200 or a Hauppauge
342
WinTV-PVR-150/250/350/500. In this mode, because the video encoding is
343
being done by a dedicated video processor, the host CPU requirements are
344
quite low. See the <ref id="video_capture_device" name="Video Capture
345
Device"> section for details.
347
The price differential between a frame grabber and a card that implements
348
hardware MPEG-2 encoding, such as the Hauppauge PVR-x50 series, is now less
349
than $30 US. Primary development in MythTV has transitioned to supporting
350
MPEG-2 capture devices and HDTV, so if given the option, go with the
351
hardware MPEG-2 encoder.
353
If you have a Via M10000 series or a Hauppauge PVR-350, MythTV can use the
354
hardware-based video decoder for playback, which further reduces CPU
335
video encoder, in which case MythTV will primarily be I/O bound. There are
336
several examples of such devices, like the Hauppauge
337
WinTV-PVR-150/250/350/500 series, the Hauppauge HD-PVR, or the Silicon Dust
338
HDHomerun. In this mode, because the video encoding is being done by a
339
dedicated video processor (the Hauppauges), or the device is simply writing
340
the data to disk (the HDHR and other digital devices, such as DVB cards) the
341
host CPU requirements are quite low. See the <ref id="video_capture_device"
342
name="Video Capture Device"> section for details.
344
Primary development in MythTV has transitioned to supporting MPEG-2 capture
345
devices and HDTV, so if given the option, go with the hardware MPEG-2
346
encoder or ATSC. Because of the transition to digital broadcast in
347
the United States, most television stations are now digital-only. There are
348
still analog stations in the U.S., but a majority are low-powered. Canada
349
still has analog broadcasts.
351
Analog encoding or hardware MPEG-2 encoding may still be required if you are
352
trying to capture standard definition video sources, such as set-top-boxes.
358
355
<p>A MythTV host that is both a backend and a frontend and using software
359
encoding with a single capture card should run adequately in 256MB of RAM.
360
Additional RAM above 256MB will not necessarily increase performance, but
356
encoding with a single capture card should run adequately in 512MB of RAM.
357
Additional RAM above 512MB will not necessarily increase performance, but
361
358
may be useful if you are running multiple encoders.
363
360
<sect2>Hard Disk(s)
391
388
and ReiserFS (versions 3 and 4).
393
390
Because MythTV creates very large files, a filesystem that does well at
394
deleting large files is important. Numerous benchmarks show that XFS and
395
JFS do very well at this task. You are <em>strongly</em> encouraged to
396
consider one of these for your MythTV filesystem. JFS is the absolute best
397
at deletion, so you may want to try it if XFS gives you problems. MythTV
398
.21 incorporates a "slow delete" feature, which progressively shrinks
399
the file rather than attempting to delete it all at once, so if you're more
391
deleting them is important. Numerous benchmarks show that XFS and JFS do
392
very well at this task. You are <em>strongly</em> encouraged to consider
393
one of these for your MythTV filesystem. JFS is the absolute best at
394
deletion, so you may want to try it if XFS gives you problems. MythTV
395
incorporates a "slow delete" feature, which progressively shrinks the file
396
rather than attempting to delete it all at once, so if you're more
400
397
comfortable with a filesystem such as ext3 (whose delete performance for
401
398
large files isn't that good) you may use it rather than one of the
402
399
known-good high-performance file systems. There are other ramifications to
472
469
</verb></tscreen>
474
471
You want to see the <tt>bttv</tt> module listed.
475
473
<sect3>Hardware MPEG-2 encoders.
476
474
<p>While inexpensive video-capture cards simply capture raw frames, leaving
477
475
encoding to software, some higher-end cards incorporate hardware-based
478
encoding. Using either a G200 MJPEG encoder card, or a MPEG-2 encoder card
476
encoding. Using either a G200 MJPEG encoder card, or a MPEG-2 encoder card
479
477
supported by the IvyTV project <url url="http://ivtvdriver.org/"
480
name="http://ivtvdriver.org"> such as the Hauppauge
481
PVR-150/250/350/500, Avermedia M179, Hauppauge "Freestyle" or Yuan M600
482
cards will allow you to use dedicated hardware encoders rather than your
483
CPU. (The PVR-350 can simultaneously be used as an output device.) Using the
484
on-board MPEG-2 encoder greatly reduces the CPU requirements for
478
name="http://ivtvdriver.org"> such as the Hauppauge PVR-150/250/350/500,
479
Avermedia M179, Hauppauge "Freestyle" or Yuan M600 cards will allow you to
480
use dedicated hardware encoders rather than your CPU. Using the on-board
481
MPEG-2 encoder greatly reduces the CPU requirements for encoding.
487
483
<bf>NOTE</bf>: Motherboards with the Via chipset are notoriously bad with
488
484
DMA and have caused numerous issues with ivtv, including hard locks. See
525
521
<p>There are a number of HDTV cards with Linux drivers which are known to
526
522
operate in the United States; a complete list of cards with DVB drivers can
527
be found at <url url="http://www.linuxtv.org/wiki/index.php/ATSC_devices"
528
name="http://www.linuxtv.org/wiki/index.php/ATSC_devices"> Some cards support
523
be found at <url url="http://www.linuxtv.org/"
524
name="http://www.linuxtv.org/"> Some cards support
529
525
capture of unencrypted digital cable TV (utilizing QAM256), others will only
530
526
work with Over The Air signals captured with an antenna (with 8VSB).
532
Cards that have been reported to work include:
534
<item>pcHDTV HD-2000, Air2PC PCI rev 1-3 (8VSB only)
535
<item>SiliconDust HDHomeRun (8VSB, QAM256)
536
<item>pcHDTV HD-3000/5500 (8VSB, QAM256)
537
<item>Air2PC HD-5000 (8VSB, QAM256)
538
<item>DViCO Fusion HDTV Lite/Gold 5 (8VSB, QAM256)
541
<bf>NOTE</bf>: There are no known consumer-level capture devices which will
542
allow you to capture the HDTV output (DVI, HDMI, VGA, YPbPr / Component)
543
from a set-top box commonly found with digital cable systems or satellite
544
systems. <em>None</em> of the capture devices listed above
528
<em>None</em> of the capture devices listed above
545
529
perform any encoding; they merely allow your computer to save a copy of a
546
530
HDTV stream which has already been converted to MPEG-2 at the broadcast
555
539
ATSC mode. The HDHomeRun should be configured as two HDHomeRun cards, one
558
To playback HDTV content, plan on a powerful CPU. "How powerful?" depends
559
on a number of factors, such as the capture resolution, whether the video is
560
progressive or interlaced, and whether your display card has hardware-assist
542
<sect3>Hauppauge HD PVR
543
<p>Hauppuage makes a device called the HD PVR, which accepts component HDTV
544
signals and performs a real-time encode into H.264. See <url
545
url="http://www.hauppauge.com/site/products/data_hdpvr.html"
546
name="http://www.hauppauge.com/site/products/data_hdpvr.html"> for
547
additional information.
549
<sect2>Playback of HDTV
550
To playback HDTV content, plan on a powerful CPU if your video card does not
551
provide support for offloading video decode. (See below for a description of VDPAU)
553
"How powerful?" depends on a number of factors, such as the capture
554
resolution, whether the video is progressive or interlaced, and whether your
555
display card has hardware-assist support for Linux.
563
557
The Simple Answer: Once you are in the 3.2 Ghz P4-class of CPU you should have
564
558
no issues with viewing HDTV.