On 8/24/15, Michael Niedermayer wrote:
> On Mon, Aug 24, 2015 at 10:55:07PM +0200, Máté Sebők wrote:
>> Oops, forgot to mention, in dshow_pin.c the libAVPin_QueryAccept() have
>> to
>> be edited to almost the same as libAVPin_ReceiveConnection() just without
>> the pin management.
>
> maybe roger
On Mon, Aug 24, 2015 at 10:55:07PM +0200, Máté Sebők wrote:
> Oops, forgot to mention, in dshow_pin.c the libAVPin_QueryAccept() have to
> be edited to almost the same as libAVPin_ReceiveConnection() just without
> the pin management.
maybe roger or others can help, i dont have a windows box here
Oops, forgot to mention, in dshow_pin.c the libAVPin_QueryAccept() have to
be edited to almost the same as libAVPin_ReceiveConnection() just without
the pin management.
On Mon, Aug 24, 2015 at 10:44 PM, Máté Sebők wrote:
> I did a dirty little hack to attempt to fix it.
> Don't call the dshow_ad
I did a dirty little hack to attempt to fix it.
Don't call the dshow_add_device() just in build time, but run the graph and
sleep() a bit, then call dshow_add_device() at the end of the
dshow_read_header().
Sadly, it does not work, it does not goes beyond the dshow "chit-chat"
between filters/pins
On Mon, Aug 24, 2015 at 02:09:28PM -0600, Roger Pack wrote:
> I've run into the case today where (if we understand it correctly) you
> setup a directshow graph, it advertises media types, then when you
> "start" the graph, it actually calls through and says "here's your
> *real* media type".
> Does
I've run into the case today where (if we understand it correctly) you
setup a directshow graph, it advertises media types, then when you
"start" the graph, it actually calls through and says "here's your
*real* media type".
Does ffmpeg internals have any concept of or support for a "changing
media
