Quote:
Code:
/usr/bin/pulseaudio --start --log-target=syslog Quote:
|
Some things sound very weird here and definitely hint towards some issues specific to your system.
The pulseaudio init script by default is not used, you have to specifically enable it if you have a use case that needs it. Normal recommendation is to not use it. I'm running KDE and have KDE starts pulseaudio, I have exactly one process running. Are you starting timidity from an init script? If yes, you might have to change that to start timidity on login of your user instead. |
I think that one way to suppress this stuff...
Code:
Mar 16 12:27:00 MySys pulseaudio[825]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="1" card_name="alsa_card.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1""): initialization failed. Code:
### Automatically load driver modules depending on the hardware available I haven't tried it on my systems, so I don't know what else will complain if you do it. |
Have had some success, but not totally.
Discovered by pure desperation that pacmd has an "info" command that will dump who is connected to it. I did not find this documented anywhere, not even in the PulseAudio man pages. So if you are having problems too, write it down or memorize it. Best way to examine PulseAudio >> pacmd >>> help >>> info >>> stat >>> dump Figured out something about the PulseAudio error messages. Guessing about this because they do not document any of this stuff. ** If you have a built-in sound device on your Motherboard, watch out ** ** ALSA has detection that can find it. ** PulseAudio does NOT detect it, so no cards. ** To PulseAudio, ALSA is NOT A CARD, so it does not detect it using udev and does not detect anything using module-alsa-card either. ** You must manually load module-alsa-sink to get sound to go to ALSA NOT-A-CARD. ** After manual configuration, udev detect and many other modules are extraneous. They can be commented out to simplify things (optional). ** You will get the ALSA-sink as an output (but it is not a card). This is likely a problem for anyone with an AC97 on their motherboard. This setup is bad enough that there ought to be some menu selection in a setup tool to select (real card, AC97, other on-board sound device, external device) etc.. and let the tool set this mess up. Can play music file using audacious (ALSA), and amarok (pulseaudio). Amarok has settled down now that there is no CD in the CDROM drive. Still do not know what it was doing, but have found two songs from the CDROM that mysteriously appeared in my directory. I can have dragonplayer play simultaneous with audacious playing different music. The Pairs game has sound again. It still cannot pronounce half of the Linux names, gets stuck. Has a serious defect in its text to speech converter that fails with the shipped game sounds. ALSA direct does sound better than through PulseAudio. I can use audacious->ALSA to play a song at much higher volume with full richness than dragonplayer->PulseAudio. For the same music, PulseAudio seems to clip when set over 110%, a level that is much quieter at the speakers than ALSA direct. The fuser command does not seem to indicate ownership of the device. > fuser -v /dev/snd/* I have seen fuser list three users of one device at the same time. I think they are all mixing through ALSA though. TiMidity is one reported and I know that goes through ALSA. Have not figured what fuser is actually indicating with that name, or how it gets it. If it is just a search of what programs think they are outputting to that device (indirectly) then its meaning is quite different that what I initially would have thought. Slackware shipped an SDL library that is connecting to pulseaudio. That is why SDL sound was not working (because pulseaudio was not working). I got sound effects from SDL now, but not SDL MIDI music. ** NO SDL MIDI ** I DO NOT have MIDI music for SDL. Whatever they did does not route MIDI to TiMidity anymore. I have TiMidity working, I can play songs using aplaymidi, so that is not the problem. Installing the SDL library for Linux 2.6 may be an answer. I will get better sound and less hassle getting it away from PulseAudio. Thanks for the help. Will post more later if any more real revelations are discovered. |
I don't wish to do anything even remotely like hijacking this thread but it seems OP would be just as happy as I would be to eliminate Pulseaudio altogether. Any benefits it may offer are either of no benefit to me or are not worth the tradeoffs. I have no Bluetooth gear nor do I intend to start. While there is now a version of Jack that will function with Puleaudio they've had to leave out function I prefer to keep and I NEED Jack or I'm back to regular dual-booting to Windows, something I have been happily free from for over 5 years.
I have tried recommended means of removing Pulseaudio but I get errors and erratic behaviour. Can anyone tell me what 14.2 Mutilib has that is currently dependent on Pulseaudio so I can either eliminate or reconfigure it/them and dump this POS. |
Quote:
Then someone could take those packages and host them so people could use slackpkg+ to install a pulseaudio free system. If no one would be willing to host them, but someone else would be willing to do the work of building the packages, I could host them. Quote:
|
Quote:
So much for pulseaudio multiplexing sound. It can't even handle the startup of a VM. I could be wrong, of course, but this is the first problem I've had with sound since I bought my microphone last year, when pulseaudio in its infinite wisdom decided my microphone was my new playback device. |
Quote:
|
Quote:
But this pavucontrol is new to me and might come in useful some time, so thanks. |
Code:
** If you have a built-in sound device on your Motherboard, watch out ** Code:
lspci reports: |
Quote:
As for the second, can you not understand the need to communicate frustration and even anger for the strong-arm adoption imperative that, at least for some, creates so many more problems than it solves (and mostly to benefit crappy onboard sound, leaving those of us who spend for actual quality in audio, which matters so much to those of us that work in it) that it seems like a solution searching for a problem? Please tell me why it' a good thing to suppress one's honest opinion in some attempt at phony politeness that is far from truthful or accurate. I think OTOH it is important to communicate that some people in fact DO find it a POS. It has certainly cost me many hours of hair pulling nastiness, and for what? Bottom line - I fully understand and agree with the availability of enough options to suit even the lowest common denominator. What I don't understand nor approve is exclusion where it becomes required to have it AND a huge mess to uninstall and switch. That does not seem at all like the Linux that won me over and kept me pleased for going on decades. |
Quote:
Would you mind adding a bit more info about your sound device so we can research a bit more based on that? lspci output should be fine. dmesg output would also be nice so we can see what udev does on boot with the sound device. This is important because theoretically pulseaudio should do the same. Quote:
Quote:
Quote:
Seriously though, this is not some proprietary shit. This is open source software built by a community that's accessible and trying to help. If this is such a big deal to you, why don't you spend some effort and figure out how to make it better? For example, the pulseaudio <-> jack integration is just waiting for someone to write a SlackBuild and submit it to SlackBuilds.org. I'm pretty sure you'd make a whole bunch of people happy with that. |
SDL2 now goes into -Current
Code:
Sun Mar 19 05:27:13 UTC 2017 |
Quote:
|
1 Attachment(s)
It's easy to remove if you don't have KDE, just get rid of the libpulse package and see what breaks.
I think on my machine it was only mpg123 that depended on it, but I only install like 20% of the system libs and build custom XFCE on that. |
All times are GMT -5. The time now is 01:41 AM. |