Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3948 - fluidsynth hogs CPU when running with alsa-lib>1.0.8

Attached to Project: Arch Linux
Opened by Nicolai Lissner (blackpenguin) - Saturday, 11 February 2006, 18:09 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 06 December 2007, 16:03 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Damir Perisa (damir.perisa)
Architecture All
Severity Medium
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

fluidsynth does not work correctly anymore since alsa-1ib-1.0.9 (even not with 1.0.10) - it hogs the CPU

I investigated this problem a bit more and found it runs perfectly with alsa-lib-1.0.8 - however just recompiling fluidsynth with newer alsa-lib does not work here. So I am stuck to alsa-lib-1.0.8 for now. Not sure if this is a problem inside fluidsynth or alsa-lib
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Thursday, 06 December 2007, 16:03 GMT
Reason for closing:  Fixed
Comment by Nicolai Lissner (blackpenguin) - Friday, 14 April 2006, 06:28 GMT
just a short update - the new version of fluidsynth-1.0.7a-1 still hogs the cpu with any alsa-lib>1.0.8 here, so either use alsa-lib-1.0.8 or stop using fluidsynth if you run into the same problem.
Comment by Roman Kyrylych (Romashka) - Saturday, 07 April 2007, 16:09 GMT
status?
Comment by Nicolai Lissner (blackpenguin) - Saturday, 07 April 2007, 17:55 GMT
still the same problem. However, it doesn't happen with jack as output, so it doesn't bug me that much anymore. But with alsa (which is the default output of fluidsynth) it still hogs the CPU
Comment by Real Name (Michel F) - Monday, 09 July 2007, 15:28 GMT
This is fixed in fluidsynth CVS.
Comment by Allan McRae (Allan) - Saturday, 01 December 2007, 06:05 GMT
v1.0.8 is out so this _should_ be fixed once package is updated
Comment by Nicolai Lissner (blackpenguin) - Thursday, 06 December 2007, 09:46 GMT
Yay! The problem actually disappeared with v1.0.8

Loading...