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 310575 - alsasink a/v sync is bad once again
alsasink a/v sync is bad once again
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins
0.8.x
Other Linux
: Normal blocker
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-07-16 10:52 UTC by Ronald Bultje
Modified: 2006-01-27 15:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ronald Bultje 2005-07-16 10:52:40 UTC
Play an ogm/mkv with alsasink, it's borked. Play with osssink, it's fine... Can
reproduce with several movies on my HD. I can't recall this being a problem
several weeks/months ago, but it's definitely several seconds off... Default
discont handling and timing in alsasink seems fine, so hard to say what causes
it. :-(.
Comment 1 Ronald Bultje 2005-07-16 11:16:31 UTC
the matroska movies with which I reproduce it, all have vorbis audio... May be
related.
Comment 2 Ronald Bultje 2005-07-16 12:14:41 UTC
And removing the filler handling fixes it... Here's my guess:
* fillers are events
* at first data, we get a discont at data-time
* those two don't match

We'll have to add manual disconts at stream-start to make sure core's disconts
don't blow us up. Bleh. Who invented this crap?
Comment 3 Ronald Bultje 2005-07-16 12:25:46 UTC
Actually, removing the invent_event in core doesn't make a difference. So it's
something else. Still, removing the filler-handling in alsasink fixes it...
Comment 4 Ronald Bultje 2005-07-16 14:22:37 UTC
Ok, so it appears more like a race condition, I can irregularly not reproduce
it... May be related to the weird scheduling (loop-based) that alsasink does, or
something else, but removing fillers sometimes does and sometimes does not fix
it. I don't know what causes it.
Comment 5 Andy Wingo 2005-07-18 12:04:53 UTC
Setting to NEW. Setting version to 0.8.x.
Comment 6 Andy Wingo 2006-01-13 17:39:47 UTC
Ronald, what's your feeling on this one? I'd be inclined to obsolete it...
Comment 7 Andy Wingo 2006-01-27 15:25:02 UTC
Going ahead and obsoleting. Please reopen if someone intends to fix this in 0.8.