GNOME Bugzilla – Bug 141670
Totem + alsasink == A/V sync problems after seek/pause
Last modified: 2009-08-15 18:40:50 UTC
Using totem-0.99.11 with gstreamer/gst-plugins 0.8.1, i'm having issues with A/V sinking after seeking/pausing a video (seeking/pausing display different problems). My setup: using xvimagesink and alsasink device=dmixed where "dmixed" is defined in /etc/asound.conf to use the dmix plugin. When first starting the video, audio and video are perfectly synced. Two different problems show up when manipulating things: Seek: After seeking to any other location in the video, the video stream seems to be lagging by 1/4 to 1/2 a second behind the audio. When playing the same video using esdsink, the A/V stays synced fine (although the video is consistently jumpy with esdsink (thus me using alsasink)). Confirmed that this same sync issue exists when using device=hw:0 directly. I also don't think dmix is to blame, as mplayer can play multiple streams to dmixed and have no syncing issues. Pause: After pausing a video, and resuming playback, the video shoots of at about 3x speed and the audio stops altogether. Sometimes, things get restored after it zips like this for a few seconds, other times it continues on indefinitely. If using device=hw:0 instead of device=dmixed, then resuming from a pause just doesn't work at all, and hangs there. alsasink+dmix seem to be really nice (using muine and totem together, etc, etc) in general, but i can't really use totem with the gstreamer backend until the A/V is consistently synced. what other info do you need from me?
Me and benjamin recently traced a bug in alsasink that is probably related to the hang using hw:0 that you're referring to. You could wait for 0.8.2 to come out or try current CVS. I don't know if it's related to the dmix problem, but it might. If not, please let us know and we'll focus on that separately.
I'm just upgrading to gstreamer-0.8.2, is it worth using CVS gst-plugins, or should i just wait for a new (soon to be released?) 0.8.2 of the plugins?
Depends on how much in a hurry you are. The fix is obviously in gst-plugins, so in order to test it you'd need to use CVS. If you're scared for CVS, it's ok to wait for 0.8.2. However, if it's still bugged then that means we can only fix it for 0.8.3. ;).
I'll put this on NEEDINFO awaiting comments, since there's not much we can do right now...
Can this be marked as closed/fixed now?
Nothing heard so marking as closed, please reopen if you still have issues.
Sorry for the silense. Yes, this is now fixed with the fixes that went into the alsa stuff a while back. Thanks.