public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: David Liontooth <lionteeth@cogweb.net>
To: linux-media@vger.kernel.org
Subject: Reliable work-horse capture device?
Date: Mon, 14 Sep 2009 19:41:13 -0700	[thread overview]
Message-ID: <4AAEFEC9.3080405@cogweb.net> (raw)


We're setting up NTSC cable television capture devices in a handfull of 
remote locations, using four devices to capture around fifty hours a day 
on each location. Capture is scripted and will be ongoing for several 
years. We want to minimize the need for human intervention.

I'm looking for advice on which capture device to use.  My main 
candidates are ivtv (WinTV PVR 500) and USB, but I've not used any of 
the supported USB devices.

Are there USB devices that are sufficiently reliable to hold up under 
continuous capture for years? Are the drivers robust?

I need zvbi-ntsc-cc support, so a big thanks to Michael Krufty for just 
now adding it to em28xx. Do any other USB device chipsets have raw 
closed captioning support?

I would also consider using the PCIe device Hauppauge WinTV-HVR-2200, 
but I need analog support.

Appreciate any advice.

Dave



             reply	other threads:[~2009-09-15  2:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15  2:41 David Liontooth [this message]
2009-09-15  3:08 ` Reliable work-horse capture device? Mauro Carvalho Chehab
2009-09-15  4:02   ` David Liontooth
2009-09-15  4:21     ` hermann pitton
2009-09-15  5:16       ` Audio drop on saa7134 David Liontooth
2009-09-15  5:36         ` hermann pitton
2009-09-15  6:07           ` David Liontooth
2009-09-20  8:24             ` David Liontooth
2009-09-20  9:02               ` Mauro Carvalho Chehab
2009-09-21  1:30                 ` hermann pitton
2009-09-21  7:53                   ` David Liontooth
2009-09-23  0:42                     ` hermann pitton
2009-09-21  7:40                 ` David Liontooth
2009-09-15  4:34     ` Reliable work-horse capture device? Mauro Carvalho Chehab
2009-09-15  5:03       ` David Liontooth
2009-09-15 10:39     ` Andy Walls
2009-09-15 14:48       ` David Liontooth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AAEFEC9.3080405@cogweb.net \
    --to=lionteeth@cogweb.net \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox