On Dec 26, 2007 8:33 AM, Jonathan Matthew <[EMAIL PROTECTED]> wrote: > On Dec 26, 2007 10:59 PM, Andrew Conkling <[EMAIL PROTECTED]> > wrote: > > > > On Dec 26, 2007 6:32 AM, Jonathan Matthew <[EMAIL PROTECTED]> > wrote: > > > > > > > > On Dec 25, 2007 10:18 AM, Andrew Conkling <[EMAIL PROTECTED]> > > wrote: > > > > Also, not to doubt you, but that seems like just a workaround. Is > there > > an > > > > underlying (gstreamer?) bug behind this? > > > > > > Yes, this is just a workaround. It's probably a bug in dmix. I haven't > > > investigated any further. > > > > > > > I'm willing to do the legwork, though I'm not sure how to determine > that. If > > I run RB in debug mode, gdb, etc., would that avail anything useful to > > determine what the problem is? > > The first thing to do is to narrow it down a bit. If you can reproduce > the problem with gst-launch, it eliminates rhythmbox as a cause. If > you can reproduce it with aplay (or some other simple alsa program), > it eliminates gstreamer as a cause. >
Well, short of coming up with a 12-hour playlist for gst-launch or aplay, I haven't been able to test this yet. Just wondering though: with Ubuntu Hardy, they'll be switching the main sound "backend" (is that the right word?) to PulseAudio. Would that have any effect on this behavior? Cheers, Andrew
_______________________________________________ rhythmbox-devel mailing list [email protected] http://mail.gnome.org/mailman/listinfo/rhythmbox-devel
