[gstreamer-bugs] [Bug 340282] New: Goom visualization is unusable at 'Normal' size and higher
bugzilla-daemon at bugzilla.gnome.org
Mon May 1 05:45:06 PDT 2006
Do not reply to this via email (we are currently unable to handle email
responses and they get discarded). You can add comments to this bug at
GStreamer | gst-plugins-good | Ver: 0.10.2
Summary: Goom visualization is unusable at 'Normal' size and
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: seb128 at debian.org
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME version: 2.13/2.14
GNOME milestone: Unspecified
That bug has been opened on
"Goom visualization works as expected as 'Small' size. But if I increase it to
'Normal', 'Large' or 'Extra Large', totem sucks up 1 CPU to 100% (I use P4 HT),
and the sound output becomes choppy or no output at all. Visualization is
However, sometimes it is possible to restore it to working normally by dragging
the possition slider, pausing/unpausing etc. Then CPU usage drops back to ~10%
on 'Normal' size, ~25% on Large size (average from both virtual processors). So
CPU it is capable of doing those Gooms at realtime, the problems lie somewhere
Im not sure, but IIRC it is a regression from Flight5-6 where it worked fine.
I attach the part of GST_DEBUG=3 totem output.
No special information here though, just warnings like
WARN (0x8504118 - 0:00:06.240627000) mad( 9806) gstmad.c(1411):gst_mad_chain:
mad_header_decode had an error: input buffer too small (or EOF)"
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the Gstreamer-bugs