** Changed in: gstreamer
Importance: Unknown = Wishlist
--
rhythmbox is slow!
https://bugs.launchpad.net/bugs/73744
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I've do some research today about this problem as I find it really
annoying.
On my side the problem wasn't solved in Jaunty. Rythmbox or Tomet was
using 17% of the CPU. My research lead my to alsa. It's seams to be an
issue of the sample rate withing the dmix of default alsa device use by
the new version is in jaunty now
** Changed in: gstreamer0.10 (Ubuntu)
Status: Fix Committed = Fix Released
--
rhythmbox is slow!
https://bugs.launchpad.net/bugs/73744
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
this has been fixed upstream now, thanks for reporting.
** Changed in: gstreamer0.10 (Ubuntu)
Status: Triaged = Fix Committed
--
rhythmbox is slow!
https://bugs.launchpad.net/bugs/73744
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
** Changed in: gstreamer
Status: Confirmed = Fix Released
--
rhythmbox is slow!
https://bugs.launchpad.net/bugs/73744
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I still experience this on Intrepid Ibex.
--
rhythmbox is slow!
https://bugs.launchpad.net/bugs/73744
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Changed in: gstreamer0.10 (Ubuntu)
Status: Confirmed = Triaged
--
rhythmbox is slow!
https://bugs.launchpad.net/bugs/73744
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
This no-longer seem to effect me so much has anyone else noticed a
marked improvement?
--
rhythmbox is slow!
https://bugs.launchpad.net/bugs/73744
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
yes, I still experience this issue especially when using the music
applet.
--
rhythmbox is slow!
https://bugs.launchpad.net/bugs/73744
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
I still experience this issue on a current Hardy system (all updates
accepted since it was originally installed), on an Intel Pentium M
laptop (Dell Latitude D610).
When the CPU usage reaches a certain threshold, the CPU usage of
rhythmbox and pulsaudio increases to take up the rest of the
This has been improved incrementally. I no longer have such an issue
with Rhythmbox. How about the others on this bug.
--
rhythmbox is slow!
https://bugs.launchpad.net/bugs/73744
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
same problem here too on a 1,6 ghz duo 2 core with 2 gig ram.
eats away between 20-50 % constant.
No problems with gutsy, only since I updated to Hardy.
--
rhythmbox is slow!
https://bugs.launchpad.net/bugs/73744
You received this bug notification because you are a member of Ubuntu
Desktop
I have the same experience as Lionel Dricot: RM takes from 10-30% CPU,
sound is choppy, and pulseaudio takes around 10-15%CPU.
This happens when playing podcast MP3s on Hardy, but did not happen on
Gutsy on the same hardware (Dell Latitude D610 laptop, with an Intel
Pentium M processor).
--
Steinar Bang [EMAIL PROTECTED]:
I have the same experience as Lionel Dricot: RM takes from 10-30% CPU,
sound is choppy, and pulseaudio takes around 10-15%CPU.
This happens when playing podcast MP3s on Hardy, but did not happen on
Gutsy on the same hardware (Dell Latitude D610 laptop, with
I didn't had any problem with RB under Gutsy but since I upgraded to
Hardy, RB takes all the time between 10 and 20% of the CPU ! (I don't
use the crossfade plugin).
When my computer does something else, the sound is sometimes garbled by
lack of CPU time. This never happened in Gutsy !
--
May not be related, but recently I'm expericencing glitches while
hearing music with rbox: no sound for a fraction of second at about
every 20 seconds. Local mp3 playing, no CPU load at all ...
--
rhythmbox is slow!
https://launchpad.net/bugs/73744
--
desktop-bugs mailing list
Ok, forwarded upstream with some more times...
** Changed in: gstreamer0.10 (Ubuntu)
Importance: Undecided = Wishlist
Status: Needs Info = Confirmed
** Bug watch added: GNOME Bug Tracker #385061
http://bugzilla.gnome.org/show_bug.cgi?id=385061
** Also affects: gstreamer (upstream)
** Changed in: gstreamer (upstream)
Status: Unknown = Confirmed
--
rhythmbox is slow!
https://launchpad.net/bugs/73744
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Sure, MPlayer (using also alsa autio output) playing from the same
streaming source:
real3m9.331s
user0m0.444s
sys 0m0.132s
During playback CPU usage is constant 0%, TIME reported by top just
before interrupting playback to get the result was 0.53sec (so about
half a sec).
--
Ok... sounds better ;)
What about gst-launch-0.10 playbin uri=file:///path/to/file?
--
rhythmbox is slow!
https://launchpad.net/bugs/73744
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
As I've already written, it does not make too much difference if I play
a streaming URL or a local mp3 file ...
Here is the result of gst-launch-0.10 playbin uri=file://... playing
an mp3 for local harddisk (it's a 128kbit mp3 stream):
real3m0.855s
user0m12.177s
sys 0m1.372s
It's
OK, I've just tried this:
time gst-launch-0.10 playbin uri=http://205.188.215.225:8006
real3m53.003s
user0m15.509s
sys 0m1.484s
If you even ignore system time, user/real*100.0 gives about 6%.
Also, I've checked TIME field just before exiting from playing
(CTRL-C), it's the same
Also, I've checked TIME field just before exiting from playing
(CTRL-C), it's the same time that 'user' field reported by 'time'.
I mean TIME field of command top :)
--
rhythmbox is slow!
https://launchpad.net/bugs/73744
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Yes, its version is 0.10.2.debian-1
--
rhythmbox is slow!
https://launchpad.net/bugs/73744
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
full list:
[EMAIL PROTECTED]:~ $ dpkg-query -W gstreamer0.10*
gstreamer0.10-alsa 0.10.10-1ubuntu1
gstreamer0.10-audiosink
gstreamer0.10-colorspace
gstreamer0.10-doc 0.10.10-1ubuntu2
gstreamer0.10-esd 0.10.4-0ubuntu3
gstreamer0.10-ffmpeg0.10.1-2ubuntu1
gstreamer0.10-fluendo-mp3
Ok, I've just removed gstreamer0.10-fluendo-mp3 and gstreamer0.10
-fluendo-mpegdemux just for testing. Playing mp3 and/or a shutcast
stream seems to require about half amount of CPU than before removing
those packages, however I think ithis CPU usage (about 6-8%) remains too
high (on a 1.7GHz P4
Definitely too much... but how do you measure the cpu usage btw?
--
rhythmbox is slow!
https://launchpad.net/bugs/73744
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Reported by 'top'. Ok, I know it's not the best method. I've got some
complex math software, I tried to run with niced to +10 or such (to
avoid r.box to glitch by lacking enough cpu time slice), and discovers
that time needed to compute somehing grows while running r.box as well
compared to the
Well, top only reports cpu usage in the exact moment of measurement or
at least something very similar to this... i.e. you could even get 100%
cpu usage by a app that is sleeping most of the time.
A better way would be something like gkrellm's cpu usage graph or just
the cpu time of the progress
You need ugly for mp3 playback anyway.
Do you have gstreamer0.10-fluendo-mp3 installed?
--
rhythmbox is slow!
https://launchpad.net/bugs/73744
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: gstreamer0.10 (Ubuntu)
Status: Unconfirmed = Needs Info
--
rhythmbox is slow!
https://launchpad.net/bugs/73744
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Mine isn't moving off 0% amd64bit. Running rhythmbox and playing virgin
radio feed.
--
rhythmbox is slow!
https://launchpad.net/bugs/73744
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Thank you for your bug. Does totem do the same? What about playing with
gst-launch-0.10 playbin uri=.? Do you use esd or alsa? What
process is using the CPU according to top?
** Changed in: rhythmbox (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: Unconfirmed = Needs
According to 'top', it's rhythmbox itself. If I try using gst-launch, it
uses (I mean process 'gst-launch-0.10') around 10-20% CPU, again. So
maybe it's not rhythmbox related, but gstreamer? I've just checked out
svn repository of beep-media-player-2 uses gstreamer as well: it uses
about the same
reassigning to gstreamer0.10 then
** Changed in: rhythmbox (Ubuntu)
Sourcepackagename: rhythmbox = gstreamer0.10
Status: Needs Info = Unconfirmed
--
rhythmbox is slow!
https://launchpad.net/bugs/73744
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Just tried on an AMD64 box (2GHz CPU), the same, somewhat smaller CPU
usage, but 10% is far more than it should be , I think (and it's now
only a 128kbit/s mp3 file). Since both the i386 - I've reported the bug
from - and this machine is installed by me, I'm thinking about if it's
my fault ...
36 matches
Mail list logo
