Note that there are some explanatory texts on larger screens.

plurals
  1. PODirectShow stop/resume live stream
    primarykey
    data
    text
    <p>I'm using DirectShow to play audio/video files in my application. I use <a href="http://msdn.microsoft.com/en-us/library/dd390090(VS.85).aspx" rel="nofollow noreferrer">IGraphBuilder::RenderFile()</a> to build the filter graph and the <a href="http://msdn.microsoft.com/en-us/library/dd390170(VS.85).aspx" rel="nofollow noreferrer">IMediaControl</a> interface to play/pause/stop the media. This works fine for local media files, but causes problems with live mms streams.</p> <p>If I call <a href="http://msdn.microsoft.com/en-us/library/dd390178(VS.85).aspx" rel="nofollow noreferrer">IMediaControl::Stop()</a> on a live stream, the stream will stop playing as expected. However, if I call <a href="http://msdn.microsoft.com/en-us/library/dd390177(VS.85).aspx" rel="nofollow noreferrer">IMediaControl::Run()</a> to resume the stream, nothing happens. The graph generates an EC_COMPLETE event, but the video does not play anymore.</p> <p>Calling <a href="http://msdn.microsoft.com/en-us/library/dd390175(VS.85).aspx" rel="nofollow noreferrer">IMediaControl::Pause()</a> followed by <a href="http://msdn.microsoft.com/en-us/library/dd390177(VS.85).aspx" rel="nofollow noreferrer">IMediaControl::Run()</a> will resume the stream where it left off, but will eventually stop. It seems to just playback the data that was in the buffer when <a href="http://msdn.microsoft.com/en-us/library/dd390175(VS.85).aspx" rel="nofollow noreferrer">IMediaControl::Pause()</a> was called, instead of re-syncing with the live stream.</p> <p>Does anybody know how to resume playing a live stream without destroying and rebuilding the filter graph?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload