Which version?
Sounds are there in Elyssa, but not quite as they should be...
No System Sounds!
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
Husse
Re: No System Sounds!
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
-
nepmak2000
Re: No System Sounds!
I have noticed that under circumstances Gnome Alsa Mixer produces an OSS error message: SigmaTel STAC 9721,23 error ( , ) not allowed...! Although I use my Audigy 2 ZS!!!
This is a persistent thing most likely due to keyboard layouts (wellknown from that 'other' OS). The , must be a . Question is where to tackle this minute typo? It causes however uncontrollable (not to save new Prefs) sound if at all! Particularly when intializing Elyssa you get a thunderous roar 100% or none at all... Great when the family is in bed and Dad wants to work late night... I assume that the problem described has to do with this. The work-around is using to open 'Volume Control' (right click on it), Open Volume Control and File-> Change Device to use: Playback ..... (your set-up). Yet, this OSS SigmaTel error persists. How to correct that bloody , ???
This is a persistent thing most likely due to keyboard layouts (wellknown from that 'other' OS). The , must be a . Question is where to tackle this minute typo? It causes however uncontrollable (not to save new Prefs) sound if at all! Particularly when intializing Elyssa you get a thunderous roar 100% or none at all... Great when the family is in bed and Dad wants to work late night... I assume that the problem described has to do with this. The work-around is using to open 'Volume Control' (right click on it), Open Volume Control and File-> Change Device to use: Playback ..... (your set-up). Yet, this OSS SigmaTel error persists. How to correct that bloody , ???
-
nepmak2000
Re: No System Sounds!
Husse, this is what I read after failing to initialize Prefs for Gnome Alsa Mixer.
This refers only to this bloody , phenomenon. Weren't that there most of us won't have silly sound troubles, I am sure!
I saw more such freak reports, like low volumes etc. With me it is the reverse - thunderous roar at start up.... (I know how to handle that!).
But the phenomena with this programme are related to that , STAC 9721,21 xx21 . 23 it should be!
John
28 June 2008 06:59:50 Received signal 6
28 June 2008 06:59:50 GNUsound crashed or was killed.
28 June 2008 06:59:50 ------ Dumping backtrace to logfile ------
/usr/bin/gnusound.real(emergency_sighandler+0x11d)[0x805bbfd]
[0xb7efd440]
/lib/tls/i686/cmov/libc.so.6(abort+0x101)[0xb7223a01]
/lib/tls/i686/cmov/libc.so.6(__assert_fail+0xee)[0xb721b10e]
/usr/lib/libasound.so.2[0xb6d3c72d]
/usr/lib/libasound.so.2(snd_pcm_close+0x76)[0xb6d21d76]
/usr/lib/gnusound/modules/player_alsa.so(alsa_close+0x36)[0xb6addb06]
/usr/bin/gnusound.real(player_thread+0x41d)[0x8071e5d]
/lib/tls/i686/cmov/libpthread.so.0[0xb734b4fb]
/lib/tls/i686/cmov/libc.so.6(clone+0x5e)[0xb72cde5e]
28 June 2008 06:59:50 Trying to save unsaved data...
28 June 2008 06:59:50 Attempting to salvage shell 1 of 1
28 June 2008 06:59:50 Writing Untitled1.crashed.wav...done (0 of 0 frames)
28 June 2008 06:59:50 Finished, continuing with default signal handler
This refers only to this bloody , phenomenon. Weren't that there most of us won't have silly sound troubles, I am sure!
I saw more such freak reports, like low volumes etc. With me it is the reverse - thunderous roar at start up.... (I know how to handle that!).
But the phenomena with this programme are related to that , STAC 9721,21 xx21 . 23 it should be!
John
28 June 2008 06:59:50 Received signal 6
28 June 2008 06:59:50 GNUsound crashed or was killed.
28 June 2008 06:59:50 ------ Dumping backtrace to logfile ------
/usr/bin/gnusound.real(emergency_sighandler+0x11d)[0x805bbfd]
[0xb7efd440]
/lib/tls/i686/cmov/libc.so.6(abort+0x101)[0xb7223a01]
/lib/tls/i686/cmov/libc.so.6(__assert_fail+0xee)[0xb721b10e]
/usr/lib/libasound.so.2[0xb6d3c72d]
/usr/lib/libasound.so.2(snd_pcm_close+0x76)[0xb6d21d76]
/usr/lib/gnusound/modules/player_alsa.so(alsa_close+0x36)[0xb6addb06]
/usr/bin/gnusound.real(player_thread+0x41d)[0x8071e5d]
/lib/tls/i686/cmov/libpthread.so.0[0xb734b4fb]
/lib/tls/i686/cmov/libc.so.6(clone+0x5e)[0xb72cde5e]
28 June 2008 06:59:50 Trying to save unsaved data...
28 June 2008 06:59:50 Attempting to salvage shell 1 of 1
28 June 2008 06:59:50 Writing Untitled1.crashed.wav...done (0 of 0 frames)
28 June 2008 06:59:50 Finished, continuing with default signal handler
-
nepmak2000
Re: No System Sounds!
I got so angry this morning not able to find the "bug" that I dissected the whole 'root' to find a -as usual- simple solution for the users of ONE sound-card. The Elyssa builders assumed possibly that most users apply more than 1 SoundCard. Just that caused the mix up for us simple users of but one such card 
. Here we go:
In the ROOT 'File System' (so be careful) find: /etc/pulse/default.pa
Then see the marked-out (#) line: # load-module module-alsa-sink remove now this # token to activate the line upon restarting.
OR: select the line you would prefer in this small section instead. I assume you would want to work with Alsa..!
Then # mark out the next whole paragraph about "automatic load driver modules depending.... " Disable only that paragraph!
It now looks like this:
### Automatically load driver modules depending on the hardware available
#.ifexists module-hal-detect.so
#load-module module-hal-detect
#.else
### Alternatively use the static hardware detection module (for systems that
### lack HAL support)
#load-module module-detect
#.endif
I strongly suppose that this automatic selection causes a lot of trouble in "older" equipment... But who am I to say so as "learned novice".
Ok, then save and restart. Go into your personal user "Home".
Goto Main Menu: Sound & Video -> PulseAudio Manager
Now we SYSTEMATICALLY CLICK all TABbed Items for their VOLUME setting, which may be way to soft or much too LOUD...!!!
Critically important to click the words "reset" next to the various windows per item. This takes a few minutes to do.
Nextly go to the (Gnome) Volume Applet and select its 'Preferences' to select the DEVICE (which should be setup correctly now) and the varius controllers you would use to SET-UP your tone and balances for your sound system. For now you may select any controllerset you wish...
Then select in this applet "Open Volume Control" and see all your controllers, some at their bottom NOT chained for LR adjustment if needed!
Now run a nice Wiener Walz or some HipHop on your RhythmBox and adjust the controllers. When satisfied with your 7.1 stereo, or 5.1 surround or 2 channels pingpong , or whatever, GO BACK TO PREFERENCES in the Volume Applet to only select MASTER and deselect the rest!
If not, you would influence ALL selected controllers for your sound when manipulating the volume control (via a keyboard) or in the applet or otherwise! This is vitally important I find. Having adjusted thngs to your liking make a restart for safety and a clean memory to begin with.
This method solved the sound crisis I faced and hopefully you'll find some intriguing hints in this to enjoy excellent AudioPulse sounds!
John
. Here we go:In the ROOT 'File System' (so be careful) find: /etc/pulse/default.pa
Then see the marked-out (#) line: # load-module module-alsa-sink remove now this # token to activate the line upon restarting.
OR: select the line you would prefer in this small section instead. I assume you would want to work with Alsa..!
Then # mark out the next whole paragraph about "automatic load driver modules depending.... " Disable only that paragraph!
It now looks like this:
### Automatically load driver modules depending on the hardware available
#.ifexists module-hal-detect.so
#load-module module-hal-detect
#.else
### Alternatively use the static hardware detection module (for systems that
### lack HAL support)
#load-module module-detect
#.endif
I strongly suppose that this automatic selection causes a lot of trouble in "older" equipment... But who am I to say so as "learned novice".
Ok, then save and restart. Go into your personal user "Home".
Goto Main Menu: Sound & Video -> PulseAudio Manager
Now we SYSTEMATICALLY CLICK all TABbed Items for their VOLUME setting, which may be way to soft or much too LOUD...!!!
Critically important to click the words "reset" next to the various windows per item. This takes a few minutes to do.
Nextly go to the (Gnome) Volume Applet and select its 'Preferences' to select the DEVICE (which should be setup correctly now) and the varius controllers you would use to SET-UP your tone and balances for your sound system. For now you may select any controllerset you wish...
Then select in this applet "Open Volume Control" and see all your controllers, some at their bottom NOT chained for LR adjustment if needed!
Now run a nice Wiener Walz or some HipHop on your RhythmBox and adjust the controllers. When satisfied with your 7.1 stereo, or 5.1 surround or 2 channels pingpong , or whatever, GO BACK TO PREFERENCES in the Volume Applet to only select MASTER and deselect the rest!
If not, you would influence ALL selected controllers for your sound when manipulating the volume control (via a keyboard) or in the applet or otherwise! This is vitally important I find. Having adjusted thngs to your liking make a restart for safety and a clean memory to begin with.
This method solved the sound crisis I faced and hopefully you'll find some intriguing hints in this to enjoy excellent AudioPulse sounds!
John