John Goerzen wrote: > After the upgrade from audacious 2.0.1 to 2.1, I started seeing this. > This did not happen at the same time as a kernel upgrade, so I feel > fairly justified in seeing this bug filed against audacious.
Started seeing what? Please elaborate. If you mean that you are using a high-quality resampling method, then you can expect Audacious to consume a lot of CPU. Likewise, if you mean that you started seeing the Audacious process take 15-30% of CPU time in system calls when outputting through DMix, but not when outputting to hardware directly, then I can confirm, both on an Intel ICH6 and an HDA. But that is a problem with DMix, not Audacious. Peace, John Lindgren -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
