Message: previous - next
Month: February 2014

Sound System Notifications Not Playing After Selected

From: "David C. Rankin" <drankinatty@...>
Date: Sun, 02 Feb 2014 14:19:41 -0600

  Since sound is now working on my install, I was setting sound system
notifications for events I like feedback on, i.e. shade/unshade,
maximize/minimize/restore, etc.. After clicking the '[ ] play sound' for the
event and confirming the sound file was present and working by pressing the '|>'
button before the sound filename, and then clicking [Apply] I was surprised to
find that TDE did not play anything on the events I configured.

  Playing the sound file with the test '|>' button worked find, but TDE was not
responding to the sound events I chose at all. What to check?

  Also, artsd has gone back to eating 10-17% of the CPU for the 60 second
'autosusped if idle for' period after a sound event. After the 60 second
autosuspend period, artsd quiets back down. Why are we setting a 60 second
autosuspend by default? Why not set it to 1 or 5 seconds. It would sure make TDE
run better giving users back 10-20% of their CPU for the remaining 55 seconds of
the timeout. Further, if the user has sound events enabled for a bulk of the
events as many sound themes do for TDE, then with an autosuspend set at 60,
artsd will be basically grinding away full time.

  Can we set that to 5 sec by default instead of 60? What are the pros/cons of
shortening the autosuspend period? I've seen some of the sound server pages
(pulse - perfect setup page) recommending 1 second for the setting. Thoughts?

David C. Rankin, J.D.,P.E.