After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 703367 - Banshee Crashing on gstreamer detect BPM
Banshee Crashing on gstreamer detect BPM
Status: RESOLVED DUPLICATE of bug 722551
Product: banshee
Classification: Other
Component: GStreamer
2.6.1
Other Linux
: Normal critical
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-07-01 07:29 UTC by mh00h
Modified: 2014-02-28 16:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description mh00h 2013-07-01 07:29:52 UTC 
When I attempt to start Banshee it immediately closes. I ran "banshee --debug" and discovered the following:

[1 Debug 00:15:03.699] Starting - Detecting BPM
[18 Debug 00:15:03.728] GStreamer running beat detection on /home/user/Music/iTunes Music/Gordon Goodwin's Big Phat Band/The Phat Pack/08 Get In Line.m4a
banshee: PeakFinder.cpp:150: int soundtouch::PeakFinder::findCrossingLevel(const float*, float, int, int) const: Assertion `peaklevel >= level' failed.


Deleting this file allows Banshee to operate normally.

Further, I saw a very recent discussion about this issue here with other users: https://mail.gnome.org/archives/banshee-list/2013-May/msg00021.html

I did not, however, see an official bug report on this and so am making this one. Though it seems this is a bug with GStreamer, Banshee should be able to accommodate this exception without crashing as recommended in the above thread.

Thanks.
Comment 1 Andrés G. Aragoneses (IRC: knocte) 2014-02-28 16:06:20 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version of SoundTouch (1.7.1-5). You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 722551 ***