Max
Wed Sep 22 17:58:26 CDT 2004
Yes, you can program demux. Check out IMPEG2PIDMap interface. Each output
pin of the demux supports it.
Still you are on your own. Timeshifting engine can unofficially support your
scenario, but it will be unofficial. You can't expect them to support TS
just because they know how to handle PS.
Try supporting MEPG2PS on your output and see if it helps. Just don't be
surprised if it doesn't.
-- Max.
"Amit" <Amit@discussions.microsoft.com> wrote in message
news:81E3DF6F-C9EE-4C8A-8904-69921043F1B2@microsoft.com...
>
>
> "Max Paklin" wrote:
>
>> What PVR app are you referring to?
>> To the best of my knowledge all PVR engines on the market today work with
>> analog streams. What they do is that they encode into MPEG2 on the fly
>> and
>> then put resulting MPEG2PS on the disk.
>>
>> With your capture driver being digital receiver, you fall out of
>> supported
>> realm.
>>
>> -- Max.
>
> Well, I am using a variety of them like SnapStream, PVRVideo and a few
> others. I know that they all support analog Video.
>
> But considering that there is a downstream filter that supports
> MPEG_TRANSPORT_STREAM, shouldnt they just connect it to that ?
>
> The MPEG Demux needs to be programmed for the correct P-ID and output pin.
> So, if the application doesnt handle that, does my capture driver need to
> handle that ? Does the output pin on my capture driver need to program
> the
> input pin on the Demux ? If yes, is there any documentation that says how
> this can be done ?
>
> Thanks.
>
>>
>>
>>
>> "virenpratapsingh" <anilkfan@yahoo.com> wrote in message
>> news:aa50956b.0409211651.5778764a@posting.google.com...
>> > All,
>> >
>> > I am running into a problem while exposing a tranpsort stream from the
>> > output pin of a capture driver.
>> > I have started from the DDK sample and have modified it to accomodate
>> > my needs and basically I have configured the capture and preview
>> > output pins of the capture driver to support MPEG-2 transport streams.
>> > The pins being confgured as
>> > STATIC_KSDATAFORMAT_TYPE_STREAM,
>> > STATIC_KSDATAFORMAT_TYPE_MPEG2_TRANSPORT,
>> > STATIC_KSDATAFORMAT_SPECIFIER_NONE
>> >
>> > being the majortype, subtype and the datformat resp.
>> >
>> > For some reason when using some PVR general purpose DirectShow
>> > compliant apps, I do get a call to open the input streams(pins) via
>> > SRB_OPEN_STREAM but never get a call to open the output stream. This I
>> > understand could be because the downstream filter( which would be the
>> > Demux in this vase) doesnt accept the connections and hence the
>> > problem.
>> >
>> > Would anyone know why this would happen ?
>> >
>> > On a side note, when I try to manually connect the filters through
>> > graphedit, I can connect the capture to ademux and so on and the MPEG
>> > stream is rendered correctly, provided I have to manually set the
>> > DEmux filter to the correct P-ID and then it configures its output
>> > ipin and then connects to any downstream decoder filter and so on. So,
>> > within graphedit, I can connnect and things are fine.
>> >
>> > However, with PVR apps and I have tried a variety of them(which all
>> > have support for transport streams and I have verified them with other
>> > capture drivers that do support transport streams possibly), things
>> > dont work.
>> >
>> > Any help appreciated.
>> >
>> > Thanks.
>>
>>
>>