Bug 251258 - kmix id always muted upon reboot, and kmix volume slider is choppy
Summary: kmix id always muted upon reboot, and kmix volume slider is choppy
Status: RESOLVED DUPLICATE of bug 250281
Alias: None
Product: kmix
Classification: Applications
Component: Backend: Pulseaudio (show other bugs)
Version: 3.7
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Colin Guthrie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-15 02:49 UTC by cjae
Modified: 2010-09-15 10:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cjae 2010-09-15 02:49:41 UTC
Version:           3.7 (using KDE 4.5.1) 
OS:                Linux

This after installing the ubuntu-desktop package in kubuntu 10.04, the pulse audio will let me pick hdmi output and spdif, it defaults to hdmi which is not optimal in my situation. Also upon reboot the volume slider is choppy at best, only volumes0,5,14 and such produce any result and usually caps at 20 or so

Reproducible: Always

Steps to Reproduce:
reboot



OS: Linux (x86_64) release 2.6.32-24-generic
Compiler: cc
Comment 1 Colin Guthrie 2010-09-15 10:15:33 UTC
Yeah the "Master" is not really selected properly in kmix. There is already a bug for that.

The actual volume thing is likely an alsa issue as most times we'll just be handing over to the alsa master slider. Try running alsamixer -c n (where n is the hdmi card number) and see what happens when you adjust the PA volume. If the scale is completely off, then chances are it's just reporting incorrect dB information and it needs to be fixed in the driver. Anyway this represents two separate issues so please report them separately (and in actual fact the choppy volume is very unlikely to be anything to do with KDE so probably not the right bug tracker to report it under :) - you can confirm that the same problems are present with other PA mixers - e.g. pavucontrol to rule out kmix's involvement!)

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