Page 5 of 5 FirstFirst ... 345
Results 41 to 44 of 44

Thread: PulseAudio 5.0 Supports BlueZ 5, Native Log Target For Systemd

  1. #41
    Join Date
    May 2013
    Posts
    477

    Default You can blacklist the drivers for the "wrong" sound card

    Quote Originally Posted by Awesomeness View Post
    Flash is the sole reason I have to use PulseAudio. Flash is hardcoded to use the first sound card. Too bad on my Lenovo laptop the first output is HDMI, not the internal PCH.
    I don't know if you can do this on your laptop without killing your video driver, but in many cases you can get around a "wrong soundcard" default by blacklisting the driver for it. I had that problem on a Pentium 4 in which I had dropped an Nvidia GT520 with the blob to play 1080p video in VDPAU, causing the sound to default to an Intel device that did not work. Blacklisting that driver made the installed sound card come up first. On a laptop with AMD and open AMD drivers, HDMI sound can be disabled in the video driver itself. Don't know what the Nouveau situation is on that.

    Pull up the output of dmesg, look for your soundcard drivers. If the HDMI shows any driver other than your video driver, blacklist it in /etc/modprobe.d and reboot. Now the sound you want to use is the only soundcard and should come right up

  2. #42
    Join Date
    May 2012
    Posts
    431

    Default

    better yet check out the alsa documetation
    http://alsa.opensrc.org/MultipleCard...nstalled_cards

  3. #43
    Join Date
    Apr 2014
    Posts
    1

    Default

    Quote Originally Posted by Awesomeness View Post
    Flash is the sole reason I have to use PulseAudio. Flash is hardcoded to use the first sound card. Too bad on my Lenovo laptop the first output is HDMI, not the internal PCH.
    One of the cool things about PA is that you can redirect sound sources to whatever device, on the fly! You can't even do that in Windows. Well, maybe you can in 8 but I haven't used 8 yet. Did you not install the apps like Pulseaudio Manager or Volume Control? You can use Volume Control to send your Flash audio to either card or devices on the card (like analog or optical). KDE Kmix will also redirect audio to specific devices. On the other hand, I have three devices (onboard Intel HDA, a PCI HT Omega Claro Halo card, and the HDMI on my video card) and I have to configure PA manually because to this day it will not add the Claro Halo or the HDA digital outputs to the list of devices by itself. Grrr.

  4. #44
    Join Date
    May 2013
    Posts
    477

    Default Pulseaudio seems to be maturing nicely-and good for grabbing web audio

    I reinstalled Pulseaudio in my main system today due to a new use case: Recording the output of the sound card when the hardware does not support recording the "mix" output.

    On my big 8 core, Pulseaudio 4.0 shows less CPU use than Cinnamon does, sometimes less than X. We don't have Pulseaudio 5 yet, looking forward to it. I made once change to version 4: changed "autospawn" from "yes" to "no" in /etc/pulse/client.conf so I could turn it on and off. Cinnamon's volume control applet will show up when it's running, disappear when it's not as an indicator of pulseaudio's status. I then found that the old issue of audio stutter when playing 1080p AVCHD clips in Kdenlive seems to be entirely gone, and since I didn't get a boatload of pulseaudio CPU use this should be true on the 4 cores as well. If not, I can turn it off until I am done with that job.

    The pavucontrol package gives a really nice GUI for controlling Pulseaudio-including the ability to record from the mics or from the output, which busts any and all attempts by webhosts like Google to control recording sound from the Web. Now no publisher of some news video I need a clip from can defeat the combination of gtk-recordmydesktop, Audacity, and pulseaudio, at least not without going to outright DRM that in my case means it's entirely blocked. If I can stream it, I can grab it. For that matter, I don't think ANY of the cross-platform DRM schemes that are denied a "protected path" on the bus could defeat the screen grab-audio output monitor combination anyway.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •