[Bug 234196] New: kmilo volume module has annoying rounding problems
https://bugzilla.novell.com/show_bug.cgi?id=234196 Summary: kmilo volume module has annoying rounding problems Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers@suse.de ReportedBy: seife@novell.com QAContact: qa@suse.de OtherBugsDependingO 215208 nThis: If you use kmilo with a standard keyboard with volume keys (many "multimedia desktops" and many notebook models) in conjunction with a soundcard that has less than 100 steps for the mixer (my intel_8x0 has 32), then you get hit by rounding problems: - pressing "volume up" tries to increase the volume by 10%, but the next matching value (rounded down) is stored in the mixer hardware - pressing "volume down" then does subtract 10% from the current value and stores it, again it is rounded down. This leads to e.g. 12 steps "up" from 0 to 100% but only 7 steps down. If you press ctrl-volume up/down, then it should increase or decrease by 1%, but in fact it never increases because 1% is not enough to step up the hardware (which only has 32 steps =~ 3% steps). There is even a FIXME comment in the code for this. This is easily fixed with the attached patch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=234196 ------- Comment #1 from seife@novell.com 2007-01-12 10:58 MST ------- Created an attachment (id=112758) --> (https://bugzilla.novell.com/attachment.cgi?id=112758&action=view) fix the generic_monitor to use steps that match the hardware patch is tested against kdelibs3-3.5.5-47 as of today, i can submit a package if you want. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=234196 ------- Comment #2 from seife@novell.com 2007-01-18 05:48 MST ------- i submitted the package -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=234196 ------- Comment #3 from seife@novell.com 2007-01-27 01:48 MST ------- i also created https://bugs.kde.org/show_bug.cgi?id=140707 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=234196 ------- Comment #4 from stbinner@novell.com 2007-01-28 05:25 MST ------- So any reason to keep this report open? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=234196 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |behlert@novell.com Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #5 from seife@novell.com 2007-01-28 14:51 MST ------- Well, a minimal comment like "ok, we'll take it" or "omg, we'll drop this patch immediately because $FOO" in conjunction with a "resolved fixed" or "resolved invalid", whatever the outcome, would have been expected. But well, different team, different bug-style ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com