rhythmbox fails to play ape files properly

[leiyou]

Binary package hint: rhythmbox

after upgrading to jaunty, rhythmbox is no longer able to play ape files properly.

the ape file plays but not smoothly, the cpu usage is roughly 60% constant, and it feels as though that the computer + sound is frozen.

the same file played properly in totem-gstreamer, any suggestions?

[Pedro Villavicencio (pedro)]

Thanks for the report, are you using the crossfading backend? does it happens without it ? weird that works fine in totem but not in rhythmbox since they're using the same backend.

[leiyou (leiyangyou)]

Thanks a lot Pedro,

It was indeed the fault of crossfade backend... Actually, I could not confirm that the same problem didn't occur before the jaunty upgrade...

[Pedro Villavicencio (pedro)]

Thanks for the quick response leiyou, may you open a bug upstream where the software authors can read about it at bugzilla.gnome.org since you're getting the issue? Please read the following instructions on how to do it https://wiki.ubuntu.com/Bugs/Upstream/GNOME , thanks for your help.

[Sebastien Bacher (seb128)]

did you open a GNOME bug?

[leiyou (leiyangyou)]

Sorry, but not really, just haven't had the time, I will do it soonish.

2009/5/14 Sebastien Bacher <email address hidden>

> did you open a GNOME bug?
>
> --
> rhythmbox fails to play ape files properly
> https://bugs.launchpad.net/bugs/360976
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “rhythmbox” source package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: rhythmbox
>
> after upgrading to jaunty, rhythmbox is no longer able to play ape files
> properly.
>
> the ape file plays but not smoothly, the cpu usage is roughly 60% constant,
> and it feels as though that the computer + sound is frozen.
>
> the same file played properly in totem-gstreamer, any suggestions?
>

[Nigel Babu (nigelbabu)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu development version, this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 360976, and any other logs that are relevant for this particular issue.

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem. Please reopen it if you encounter that this issue is still occurring in latest Ubuntu version. To reopen the bug report you can click under the Status column, and change the Status back to "New". Thanks again!