- Moderator
- #31
I can see 2 benefits from knowing if the current playback's byte-position in the stream:
a) If buffering is a tad slower than playback, buffer will drain often and playback will be juttery. This could be detected and the graph paused to allow more to download before resuming playback.
b) --not sure on this one though-- If a seek operation goes beyond the buffer, that this seek could be canceled Right now, if I seek almost to the end of the clip in MediaPortal, the playback will freeze until the buffer has reached that position and I can't "seek back".
Right now, I can only manually watch the buffer progress and decide if I need to pause or can seek from the look of the progress bar in MediaPortal.
Does the "Render Pin" action work on your filter? Currently I'm adding the FileSourceUrl manually and then render the pin to build the graph automatically.
One more thing to think about:
If you use the flash player on YouTube for example, you can set the playback postion somewhere in the file and it jumps pretty fast. I think what they are doing is another http request of the file but starting at a certain byte range, like resuming. If we had a source filter that could mimic that, it would also be really nice
a) If buffering is a tad slower than playback, buffer will drain often and playback will be juttery. This could be detected and the graph paused to allow more to download before resuming playback.
b) --not sure on this one though-- If a seek operation goes beyond the buffer, that this seek could be canceled Right now, if I seek almost to the end of the clip in MediaPortal, the playback will freeze until the buffer has reached that position and I can't "seek back".
Right now, I can only manually watch the buffer progress and decide if I need to pause or can seek from the look of the progress bar in MediaPortal.
Does the "Render Pin" action work on your filter? Currently I'm adding the FileSourceUrl manually and then render the pin to build the graph automatically.
One more thing to think about:
If you use the flash player on YouTube for example, you can set the playback postion somewhere in the file and it jumps pretty fast. I think what they are doing is another http request of the file but starting at a certain byte range, like resuming. If we had a source filter that could mimic that, it would also be really nice