Finally found the reason why. There were multiple active-input-changed signals
being sent which was causing the stop and create monitoring methods to get
muddled. Fixed in commit
http://bazaar.launchpad.net/~cjcurran/+junk/soundnua-gtk-warnings/revision/19
** Changed in: gnome-control-center (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/987626
Title:
peak detection on input tab doubles up on level
Status in “gnome-control-center” package in Ubuntu:
Fix Committed
Bug description:
To recreate:
1. Open input tab.
2. Connect alternative input device
3. Move between streams.
Expected behaviour:
- input peak detection accurately represents input level
Instead the peak detection will represent the summed level from all
devices which at one point it was expected to monitor.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/987626/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
