After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 157217 - [esdsink] doesn't flush correctly
[esdsink] doesn't flush correctly
Status: RESOLVED INVALID
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-11-03 12:00 UTC by Christian Fredrik Kalager Schaller
Modified: 2005-02-08 18:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Fredrik Kalager Schaller 2004-11-03 12:00:22 UTC
Tested 
esound and 
artsd 

and both seem to kill seeking
Comment 1 Tim-Philipp Müller 2004-11-03 18:24:29 UTC
+ nas 
 
 
Comment 2 Tim-Philipp Müller 2004-11-04 11:53:39 UTC
- nas 
 
Apologies, please ignore my previous post. nassink still works same as before 
and doesn't have its own clock anyway (could use one though, it's really 
half-broken now, esp. with regard to seeking). 
 
(Switching off the traffic shaper that limited bandwidth between the nas 
client and daemon machines to 25kB/s resolved my issues). 
 
Cheers 
 -Tim 
 
Comment 3 Ronald Bultje 2004-11-05 14:24:46 UTC
I cannot reproduce esound. It works fine here. Although it takes a few (1-2)
seconds for it to pick up seeks (like it doesn't flush correctly), it works fine
after a seek, both forward and backward... Please re-confirm.
Comment 4 Ronald Bultje 2004-11-05 16:15:54 UTC
That's not clear at all. ;).

The problem is that after a seek, esd seems to continue playing what it was
playing. Video will hang for 1-2 seconds. Only after it's cache is cleared, does
it actually process the seek. After that, everything works fine and as expected.
Comment 5 Ronald Bultje 2005-02-08 18:26:16 UTC
No longer reproduceable. Please give me a clear testcase and feel free to reopen.