Re: Capture Graph with VMR9 in Windowless mode
- From: "Andrew" <4brown@xxxxxxxxx>
- Date: 23 Mar 2007 15:06:52 -0700
On Mar 15, 12:13 pm, Colin White <c...@xxxxxxxxxxxxxxxxxxxx> wrote:
it's on my list to look at when I have some spare time. However, in this
case I think you would be ok using the bridge. The graph containing the
renderer is stopped -- but you would have the mux and file writer in a
separate graph which is therefore not stopped. You can handle the
renderdevice-set event by stopping and restarting the source graph or
whatever, and the mux/writer graph will continue ok.
G
Thanks for the assistance Geraint. I have to keep the support
in-house so I can't use the GMF Bridge. If it's of any interest to
anyone facing a similar problem, I've put the following work-around in
place:
Use CancelDefaultHandling onEC_DISPLAY_CHANGED, added an handler in
my app, detach the currently open file, then unbuild and re-build the
graph and re-start capturing.
Thanks for posting your workaround. I've also seen this problem in my
application and after implementing your suggestion the
EC_DISPLAY_CHANGED message is posted again right after I re-start.
It's like the event wasn't cleared or something even though the entire
graph was unloaded and reloaded.
Has anyone else seen this behavior?
Andy
.
- Follow-Ups:
- Re: Capture Graph with VMR9 in Windowless mode
- From: Colin White
- Re: Capture Graph with VMR9 in Windowless mode
- References:
- Capture Graph with VMR9 in Windowless mode
- From: Colin White
- Re: Capture Graph with VMR9 in Windowless mode
- From: Geraint Davies
- Re: Capture Graph with VMR9 in Windowless mode
- From: Colin White
- Capture Graph with VMR9 in Windowless mode
- Prev by Date: Re: Time not changing while fast forwarding
- Next by Date: how can i hide the FFDSHOW decoder configuring icon in the taskbark
- Previous by thread: Re: Capture Graph with VMR9 in Windowless mode
- Next by thread: Re: Capture Graph with VMR9 in Windowless mode
- Index(es):
Relevant Pages
|
Loading