On Sun, 2011-03-13 at 00:26 -0500, Devin Heitmueller wrote:
> On Sun, Mar 13, 2011 at 12:06 AM, <[email protected]> wrote:
> > > Date: Sat, 12 Mar 2011 19:36:04 -0500
> > > From: Devin Heitmueller <[email protected]>
> >
> > > On Sat, Mar 12, 2011 at 7:05 PM, Andy Walls <[email protected]>
> > wrote:
> > > > I'm really busy for the next 2 weeks, so I won't be able to look into
> > > > any possible problem myself until then. Even then I'll have to jump
> > > > through hoops to get a device that can receive S-Video near my
> > PVR-350.
> >
> > > Or just spend $20.00 and buy an Nvidia card with VDPAU and S-video
> > > output. Given how cheap they are nowadays, it probably isn't worth
> > > the effort to debug.
> >
> > Are there any?
> >
> > S-video output on a VDPAU-capable card seems increasingly difficult
> > to find, especially for newer feature sets. Any recommendations for
> > (a) PCI (not PCIe), (b) passively cooled or very quiet fan, (c) recent
> > feature set, (d) S-video? The combo of all of these seemed impossible
> > the last time I looked. Even dropping (b) didn't help much. And, in
> > my case, dropping (a) means a new frontend. But to continue using my
> > Sony CRT, I'd require S-Video, and that wasn't looking promising
> > post-8400 or so, if 8400's are even still on the market.
> >
> > (Also, for someone who only does SD and has limited PCI slots, not
> > using the 350's decoder means you need an extra slot for that new
> > card, so abandoning the 350's output may present difficulties for
> > the OP. We don't know his configuration.)
>
> Yeah, a quick search on newegg has some 6200s in PCI with S-video out,
> but they don't do VDPAU.
>
> I guess if his PC is 5+ years old and cannot handle SD MPEG decoding
> in software, then his best bet is to not upgrade. Or track it down
> himself and submit a patch.
> Or pay Andy a few thousand bucks to track
> down the issue for him (let's not forget that Andy's time is
> incredibly valuable and you could argue is much better spent on newer
> devices).
For the record, my time is non-existant ATM. Two different divisions of
$VERY_BIG_CUSTOMER need products from me in the immediate future.
$VERY_BIG_CUSTOMER pays the bills....
> Ultimately this is a matter of priorities: is Andy's time better
> spent making current hardware work or tracing down regressions in six
> year old devices that are largely obsolete?
To be fair, obsolete hardware (standard PCI and CX2341[56] chips) is
implied in the name of the ivtv mailing lists, so it is on-topic, and
valid to ask.
But yes, this comic strip captures the technology price trends nicely:
http://www.dilbert.com/fast/2002-06-08/
> It's ultimately his
> decision what he wants to waste^H^H^H^H^H spend his time on, but I
> certainly couldn't blame him if this issue isn't it.
1. Old kernel and driver versions
2. A problem I am unlikely to reproduce
3. A card that is obsolete and could be starting to fail due to age
4. No free time
5. Compsite out works
6. A user who has "an itch to scratch"
7. A publicly available datasheet
8. S-Video fixes already applied in more modern kernels
All those factors do drive this to a low-prioirty problem for me.
>From a system perspective, which includes human eyes and grey-matter,
the big difference between CVBS and S-Video is the high frequency notch
in the CVBS Luminance. A receiver's "sharpness" control can
perceptually make the image better. We're talking about interlaced
video, with digitally undersampled color, potentially sourced from
decompressed MPEG which is lossy, so human perception is already being
greatly exploited anyway.
Regards,
Andy
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
