[Mono-bugs] [Bug 356051] progressive stream buffering calculation flawed

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Thu Jan 24 17:47:44 EST 2008


User rkvinge at novell.com added comment

--- Comment #3 from Rolf Bjarne Kvinge <rkvinge at novell.com>  2008-01-24 15:47:44 MST ---
The demuxer reads 1 byte for whatever reason, which is not downloaded yet, and
will block waiting for the byte to be downloaded.

This causes buffering to start, which will reach 100% once that byte is

And then the demuxer reads another byte, and the circle is continues.

This is mitigated a bit by your caching in the file streams, however the real
problem is that the demuxer seeks by reading the file and dropping frames until
it finds the desired frame.

The fix is of course to make the demuxer calculate where it should start
reading (i.e. create an index and use it, and if no index make an educated
guess, which isn't too hard with asf).

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the mono-bugs mailing list