Re: Component Video capture in MCE application ?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Jaime, you're right, I meant capture.

- An update -

Since I opened this thread, I read up Peter Rosser's article about Tuner's
in his '16.7ms in the Life' blog. You can see the article here :
http://tinyurl.com/3d8594

I privately mailed him and had the following response :
---------------------------------------------------------------------------------------------

That's a really interesting question. I don't have one of those cards handy,
so I can't tell you definitively which registry keys to change. Basically
what you need to do is fool the tuner driver into sending a "use component
input" when we try to build an S-Video graph.

I can describe the process a little, though... I think a hack here is
possible, but it depends on Leadtek's driver / how they configure the driver.

The way this all works is we use MsVidCtl.dll to build a DShow graph by
enumerating pins on the DShow filters and connecting them up in compatible
ways. Filters are organized into graph compositing groups in 3 categories:
input, "feature", and render/output. All configuration for your case would be
on the input segment, unless the driver puts stuff into the feature segment,
which I doubt.

Analog tuners, by and large, have 2-3 filters that get inserted into the
graph: a tuner filter that exposes controls on changing the channel /
frequency, a crossbar filter for selecting inputs, and a capture filter for
controlling the encode process and outputting that encoded video to the
downstream filters. Sometimes the crossbar filter and tuner filter are
combined into a single filter. What you need to do is make the crossbar
filter think that the S-Video input is actually the component input, plus
tweak any encoding settings that need to be different between the two.

Actually making this hack work might take a bit of wizardry, though. DShow
filters are COM registered, so you can find their keys by digging around in
HKLM\CLSID, and tuner configuration is *sometimes* stored in the registry,
but not always. If you know how to back-track CLSIDs to configuration
sections, you can check that route. Another route would be hacking the driver
INF file. You may see separate sections for the S-Video vs. Component in
there, and swap their entries (or something akin) to fool the driver. You'd
install that by editing the INF file and reinstalling the driver for the card
to use your hacked INF.

Without the card, though, I can't get more specific.

// Peter
---------------------------------------------------------------------------------------------

Personally, I'm no familiar with DShow or Graphs, so I'll attmept the Tuner
driver hack.

The theoretical side certainly sounds plaussible. Just hope I can get this
hack to work!

Just surprised this hasn't been attempted before.

Cheers


"Jaime" wrote:

I'm not understanding something, you said MCE Playback using component. The
playback is a function of the video card, not the tuner card.
--
James
Orlando (Goofy says "Hey!"), Florida

"DarkKnight" <DarkKnight@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:42F35EAE-FFE3-432D-AE5B-EEB9F0C79396@xxxxxxxxxxxxxxxx
"Component Video capture is not an option for MCE 2005 or Vista Media
Center."

I'm aware Component Video capture is not an option.

But I have nevertheless been able to get this to work. If I capture
S-Video
in MCE, and then run the PVR software that comes with my Tuner card, it
makes
MCE playback using Component video. (But the PVR software bombs out with a
'Failure to build Graph error')

So it's just that the option isn't presented in MCE's TV Set Up.

Surely this would just require a registry hack ?



.

Relevant Pages

  • Re: pushdesktop filter in driver
    ... so basically i connected the push source filter to a WMV ... i could able to capture whuts going on thedesktop. ... >> So I started to create a VfW driver. ... > code from the PushSource filter inside you driver. ...
    (microsoft.public.win32.programmer.directx.video)
  • Re: Help on Tuner+USB+Directshow
    ... And then directshow to emulate the device as a capture source ... I have a USB device driver usb.sys which handles data sending, ... that i need a capture filter in directshow, i also read about video capture ... You can use that code as a base for your AVStream driver. ...
    (microsoft.public.development.device.drivers)
  • Re: Why Lowerfilter for "MEDIA" Class?
    ... They are probably just trying to filter data from their device. ... driver will be seeing very different IRPs from a PCI audio driver. ... What I meant is how they really capture all these different kind of MEDIA ... if I want to capture PCI audio data out from IRPs ...
    (microsoft.public.development.device.drivers)
  • Pinnacle PCTV - no channel tunning
    ... So after lurking around a bit I tried several bttv cards (39 Pinnacl ... Linux video capture interface: v1.00 ... not found tvaudio: TV audio decoder + audio/video mux driver tvaudio: ... think I caught the problem down to the tuner type, ...
    (comp.os.linux.hardware)
  • Re: What is "nVidia WDM Video Capture"?
    ... After reinstalling the nVidia driver, "nVidia WDM Video Capture" ... So i know my Hauppauge tuners work, ... probably has a tuner. ...
    (microsoft.public.windows.mediacenter)