From: David Liontooth <lionteeth@cogweb.net>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: linux-media@vger.kernel.org
Subject: Re: Reliable work-horse capture device?
Date: Mon, 14 Sep 2009 22:03:55 -0700 [thread overview]
Message-ID: <4AAF203B.3010304@cogweb.net> (raw)
In-Reply-To: <20090915013430.61ad5889@pedra.chehab.org>
Mauro Carvalho Chehab wrote:
> Em Mon, 14 Sep 2009 21:02:52 -0700
> David Liontooth <lionteeth@cogweb.net> escreveu:
>
>
>> As for the ventilation issue for USB devices, that may not be a serious
>> obstacle. If the USB sticks such as Hauppauge HVR-950 have reliable
>> components, we could strip the plastic casing and mount the unit next to
>> a fan inside the case.
>>
>
> Yes, this may work.
>
> Don't forget that, if you use USB devices, you'll probably need one separate USB
> buses per each device, due to USB limits in terms of the maximum number of isoc
> packets per second. If you don't require high quality, you could try to use
> a format that requires less than 16 bits per pixel or 320x240 pixels, in order
> to have more than one device per bus.
>
Thanks for pointing this out.
>
>> I would be happy to use bttv, but I can't find cards. I also need to
>> grab audio off the PCI bus, which only some bttv cards support.
>>
>> We've been using saa7135 cards for several years with relatively few
>> incidents, but they occasionally drop audio.
>> I've been unable to find any pattern in the audio drops, so I haven't
>> reported it -- I have no way to reproduce the error, but it happens
>> regularly, affecting between 3 and 5% of recordings. Audio will
>> sometimes drop in the middle of a recording and then resume, or else
>> work fine on the next recording.
>>
>
> saa7134 has a thread to detect audio audio stereo mode. Maybe there is a bug
> somewhere there.
>
Interesting idea -- anything I can do to debug?
>
>> Our fallback is ivtv. I was hoping to use USB so that we could get
>> blades instead of 3U cases; it's also getting hard to find good
>> motherboards with four PCI slots.
>>
>
> The current best relation in terms of slots is the new cx25821. It has 8
> simultaneous inputs at 60 fps per each PCIe board. If you don't need a tuner,
> this design could be very interesting. The driver was written by Conexant, and
> it is not yet present on any distribution (I just committed it today - at
> staging - since it needs some cleanups to match kernel CodingStyle).
>
Wow, that's great to get support for this powerful device. We do need
tuners, though -- we're capturing straight from RF television cable.
Otherwise a beautiful product, even with h264 compression, which is what
we need.
Cheers,
Dave
next prev parent reply other threads:[~2009-09-15 5:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 2:41 Reliable work-horse capture device? David Liontooth
2009-09-15 3:08 ` 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 [this message]
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=4AAF203B.3010304@cogweb.net \
--to=lionteeth@cogweb.net \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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