All,
With the latest R14 builds, I am experiencing crazyness with the sound. Critical stops/errors are very very loud, while normal sound events are low. Changing the volume with kmix has NO effect on the volume of the Control Center -> Sound -> Sound System -> Test Sound volume. Sound System uses ALSA. If alsamixer is run from the cli, then volume can be controlled. However using kmix to adjust sound levels and switching back and forth between pulse/ICH6 on the mixer causes sound to be reset to high level for errors.
The sound processes are:
18:48 supersff:~> ps ax | grep "pulse|arts" 3390 ? Sl 1:26 /usr/bin/pulseaudio --start 3400 ? S 0:00 /usr/lib/pulse/gconf-helper 14133 ? S 0:06 /opt/trinity/bin/artsd -F 10 -S 4096 -a alsa -d -s 60 -m artsmessage -c drkonqi -l 3 -f
There is also a 1-2 second delay between the sound event being triggered and the sound actually happening. What could cause such symptoms?
All,
With the latest R14 builds, I am experiencing crazyness with the sound. Critical stops/errors are very very loud, while normal sound events are low. Changing the volume with kmix has NO effect on the volume of the Control Center -> Sound -> Sound System -> Test Sound volume. Sound System uses ALSA. If alsamixer is run from the cli, then volume can be controlled. However using kmix to adjust sound levels and switching back and forth between pulse/ICH6 on the mixer causes sound to be reset to high level for errors.
The sound processes are:
18:48 supersff:~> ps ax | grep "pulse|arts" 3390 ? Sl 1:26 /usr/bin/pulseaudio --start 3400 ? S 0:00 /usr/lib/pulse/gconf-helper 14133 ? S 0:06 /opt/trinity/bin/artsd -F 10 -S 4096 -a alsa -d -s 60 -m artsmessage -c drkonqi -l 3 -f
There is also a 1-2 second delay between the sound event being triggered and the sound actually happening. What could cause such symptoms?
PulseAudio itself? ;-) In my experience PulseAudio only works correctly on a (random) handful of computers.
Tim
On 07/18/2012 03:50 PM, Timothy Pearson wrote:
All,
With the latest R14 builds, I am experiencing crazyness with the sound. Critical stops/errors are very very loud, while normal sound events are low. Changing the volume with kmix has NO effect on the volume of the Control Center -> Sound -> Sound System -> Test Sound volume. Sound System uses ALSA. If alsamixer is run from the cli, then volume can be controlled. However using kmix to adjust sound levels and switching back and forth between pulse/ICH6 on the mixer causes sound to be reset to high level for errors.
The sound processes are:
18:48 supersff:~> ps ax | grep "pulse|arts" 3390 ? Sl 1:26 /usr/bin/pulseaudio --start 3400 ? S 0:00 /usr/lib/pulse/gconf-helper 14133 ? S 0:06 /opt/trinity/bin/artsd -F 10 -S 4096 -a alsa -d -s 60 -m artsmessage -c drkonqi -l 3 -f
There is also a 1-2 second delay between the sound event being triggered and the sound actually happening. What could cause such symptoms?
PulseAudio itself? ;-) In my experience PulseAudio only works correctly on a (random) handful of computers.
Tim
Been working with 3.5.12 for a long time. I can kill it, and I'll test that way and report back.
I think I have found the reason why the error were so darn loud and the rest of the sound wasn't.
http://www.3111skyline.com/dl/dt/trinity/ss/tde-sound-player-setting.jpg
In Sound -> System Notifications -> Player Settings (button) volume is 100% and is NOT slaved to the mixer volume. This is a bug. This has always tracked the mixer controls. Some hook got broke somewhere.
Also, the 'TDE is exiting' sound needs changing from the current Logout_3.ogg. The KDE_Logout_new.wav is much, much better and it is what I'm used to seeing as the default logout sound.
On 07/18/2012 04:25 PM, David C. Rankin wrote:
Been working with 3.5.12 for a long time. I can kill it, and I'll test that way and report back.
NOT Good. Killing pulse causes kmix to take 100% CPU until the desktop is killed.
http://www.3111skyline.com/dl/dt/trinity/ss/kmix-killingPulse-100pctCPU.jpg
On 07/18/2012 05:50 PM, David C. Rankin wrote:
On 07/18/2012 04:25 PM, David C. Rankin wrote:
Been working with 3.5.12 for a long time. I can kill it, and I'll test that way and report back.
NOT Good. Killing pulse causes kmix to take 100% CPU until the desktop is killed.
http://www.3111skyline.com/dl/dt/trinity/ss/kmix-killingPulse-100pctCPU.jpg
Also, after killing pulse, TDE hangs badly on shutdown, the stuck process is:
/opt/trinity/bin/artsshell -q terminate
Something is rotten in Denmark with artsd :(
On 07/18/2012 03:50 PM, Timothy Pearson wrote:
PulseAudio itself? ;-) In my experience PulseAudio only works correctly on a (random) handful of computers.
Tim
Forgot to mention - this is with ALSA (pulseaudio-alsa). See:
https://wiki.archlinux.org/index.php/PulseAudio
If users have gnome, or other desktop installed on newer systems, then they will likely have pulse started. The config is the same on Arch as with my SuSE kde3 installs.
We need to insure that the sound in TDE will play (no pun intended) nicely with this setup ;-)
-
David C. Rankin -
Timothy Pearson