[Bug 651182] BPM detection is horrendous

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=651182
  GStreamer | don't know | unspecified

Andrés G. Aragoneses (IRC: knocte) <knocte> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|2.0.0                       |unspecified
          Component|general                     |don't know
                 CC|                            |knocte at gmail.com,
                   |                            |slomo at circular-chaos.org
         AssignedTo|banshee-maint at gnome.bugs    |gstreamer-bugs at lists.freede
                   |                            |sktop.org
          QAContact|banshee-maint at gnome.bugs    |gstreamer-bugs at lists.freede
                   |                            |sktop.org
   Target Milestone|1.x                         |HEAD
            Product|banshee                     |GStreamer
           Severity|enhancement                 |normal

--- Comment #3 from Andrés G. Aragoneses (IRC: knocte) <knocte at gmail.com> 2011-10-19 15:11:07 UTC ---
(In reply to comment #2)
> I also had an example, the
> song "Sing it back" by Moloko, which I knew was 168 BPM. The command line : 
> gst-launch -m filesrc location=/path/to/my.mp3 ! decodebin2 ! audioconvert !
> bpmdetect ! fakesink which replicates how banshee does, gives me 61.

If the problem is given by gst-launch outside Banshee, then it's not a bug that
can be fixed in Banshee core source code or extensions.

> As I have a personal interest in this, I will try to see with slomo, the
> creator of the plugin, what he thinks about that.

Adding him to the CC then.

And retargetting bug to gstreamer.

-- 
Configure bugmail: https://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.