Re: Video renderer stops rendering at reaching the former stop pos
- From: Geraint Davies <geraintd@xxxxxxxxxx>
- Date: Fri, 25 May 2007 09:38:18 +0100
On Thu, 24 May 2007 10:01:02 -0700, Andreas Korn wrote:
It did not work. Regardless of the stop position value in NewSegment (which
does not get called at the beginnning), the filtergraph always sets the
position to stop position when it is maxed at the last start/seek/flush and
stops the video display when not.
I don't understand this paragraph. I thought the problem was that the
decoder/renderer stopped rendering data after the stop time, even if you
updated the stop time. My understanding is that this behaviour is triggered
by the NewSegment call. NewSegment originates in the parser as a result of
the seek call from the app. You seem to be implying that the NewSegment
affects subsequent Seek calls, which is not my understanding and also not
relevant?
G
.
- References:
- Re: Video renderer stops rendering at reaching the former stop positio
- From: Geraint Davies
- Re: Video renderer stops rendering at reaching the former stop pos
- From: Geraint Davies
- Re: Video renderer stops rendering at reaching the former stop pos
- From: Andreas Korn
- Re: Video renderer stops rendering at reaching the former stop positio
- Prev by Date: Re: Strange behavior with Quartz.dll
- Next by Date: Please help me
- Previous by thread: Re: Video renderer stops rendering at reaching the former stop pos
- Next by thread: Re: IGraphBuilder::Connect concept
- Index(es):