>From: Billy Biggs <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: [V4L] Support for ViewCast Osprey or Winnov Videum 1000/II
capture cards?
>Date: Sun, 14 Apr 2002 12:19:42 -0500
>
...
>
>The Osprey-100 and Osprey-200 use the BT878 chip which is well
>supported under linux (and used in many many cards!).
>Uncompressed recording from this card is well supported.
>
>However, I wouldn't call it perfect quality. It would be nice
>to have component video input (not just S-Video), a breakout box
Has anyone done testing of V4L-supported cards, and posted the results?
I've been thinking about this, and I really like the idea of working on an
app that generates test patterns and then analyzes them. You could do all
sorts of things, like testing the S/N, frequency response, gamma, THD,
superblack support, and frame cropping. With that, you could even do
auto-calibration! You could also use those tests to measure all sorts of
video equipment and compressors. With a little more work you could do
latency and frame drop detection, topology discovery, and detection of
intermittent failures. Of course, latency detection and topology discovery
would require some sort of watermarking, for the analyzer to be able to
determine the sequence of test frames, and recognize which frames correspond
to which streams.
>I'm considering purchasing a high quality VCR with TBC
>and stuff that outputs S-Video for VHS recording. Maybe it could
>be a tuner too... (anyone else have any recommendations?)
Recommendations for what? The VCR? I have a JVC HR-S9600U, and I'm about
to get a Panasonic AG-1980. They both have 3D Y/C separation, comb filters,
DTBC and DNR. People say lots of good things about the anti-ghosting tuners
in the JVC 9xxx series, and they're cheap now, too. Otherwise, the
Panasonic is a better VCR, but like 2.5 times as expensive.
>and that's what my recording app uses. Wanna help? Of course I'm
>looking for help with my app, but there are lots of other recorder
>apps you could help with too.
Hmmm... everyone seems to want to write apps. I like well written apps, but
get easily annoyed when they're clearly not built on a robust, scalable
infrastructure (inevitably, I will run into some annoying limitation). I
like building scalable infrastructure and wrapping it with command-line
tools, so that I can script up whatever sort of automation I want.
Windows/Mac people just don't seem to get that. They tend to be content
with the model that every app has its own scripting language, and lives in
its own universe.
If there were people using V4L in broadcast studios, today, you'd have the
benefit of their contribution, and they might even be able to get drivers
for hardware supporting digital transports. But, there's a bootstrapping
problem. Also, NT seems to be making inroads, here. A friend of mine
builds transcoder boxes that run NT, but some of the streaming codecs they
support are NT-only.
I could live with those drivers not being open source, so long as they do
everything anyone needs, for non-protected content. Of course, then there's
the whole issue that I should have "fair-use" rights to protected content
that I own, and a means to exercise those rights. But, even closed-source
drivers that don't support that model would arguably be better than nothing.
Matt
_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com
_______________________________________________
Video4linux-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/video4linux-list
