Announcement

Collapse
No announcement yet.

PulseAudio 4.0 Brings Many Changes

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Originally posted by newwen View Post
    Pulseaudio is a great piece of software.

    My biggest complaint is that the hardware volume buttons of my usb headset change the master volume instead of the headphone volume. I can't file a bug because I really don't know where to track the problem, if it is related to gnome-settings-daemon or pulseaudio.
    My headset sends volume up/down keypresses and my mixer uses those for whatever the default channel is. I fix this on my headset by setting the headset as the fallback device (default device) when I plug it in.



    Originally posted by BO$$ View Post
    The question is: Will now the sound in linux be almost as good as in windows? Are we there yet? Or almost there yet?
    We hit that a couple years ago. They still can't do things like transparently move streams between channels, split/join channels, or send audio over the network. In addition, it is much easier to get consistant low latency and Jack blows away anything available on the Windows platform for pro-audio. Every time I use windows I wonder why they still haven't gotten it at least close to feature parity with Pulse.

    Comment


    • #17
      Originally posted by newwen View Post
      Pulseaudio is a great piece of software.

      My biggest complaint is that the hardware volume buttons of my usb headset change the master volume instead of the headphone volume. I can't file a bug because I really don't know where to track the problem, if it is related to gnome-settings-daemon or pulseaudio.
      As an end user, you can file a bug with your distribution's bug tracking system. As long as they're not ubuntu, they'll either fix it (if it is a real bug) and push the patch upstream, or communicate the bug to the appropriate upstream for you.

      Comment


      • #18
        Originally posted by Mike Frett View Post
        I honestly can't tell if you guys are being serious or not. I have had at least five different Audio Cards and all of them worked just fine with Pulse. Everything from a Fortissimo 3 to MAudio 7.1 and way back to a Soundblaster PCI 512.

        Sometimes, if you have Audio Issues, try moving your Sound Card to a different slot on your Mobo. I have found that usually resolves the issues. Also try to set things up with alsamixer from the terminal. Hey Bo$$, go back to Neowin and stop trolling.
        I don't use a dedicated sound card (and haven't used one for years), PA works fine too. But again, you get noticeable latency if you're not using HT.

        Comment


        • #19
          On my netbook killing pulseaudio was the difference between mumble taking 75% vs 25% of the available cpu. I saw similar although not as dramatic results when killing pulseaudio on an athlonII x4 I was using for a recording appliance. And the sound worked better off with it as well.

          Comment


          • #20
            Originally posted by Awesomeness View Post
            PA simply does not offer a single benefit for me over pure ALSA.
            Perhaps you are one of the lucky few that are able to get audio mixing directly from your hardware. Unless I am mistaken for everyone else the software mixing is the only option then...

            Comment


            • #21
              except that most people don't need a mixer at all.

              I have my sound card plugged into a receiver with an optical spdif. The receiver is then plugged into the tv with an optical spdif. This way i can have audio output from the receivers speakers or the tv speakers. With pa either one results in multiple seconds of lag and pops and skips and crackles.. Literally seconds out of sync.. Just plain alsa works perfect. I'm tired of people blaming it on the alsa driver when alsa is what works. Obviously the fault is somewhere in pa not alsa. Alsa works PA does -NOT-.

              Comment


              • #22
                FWIW, PulseAudio works fine on all my Slackware systems, without lag, crackles and stuff. Blaming your problems on PA when it possibly is the configuration of your distro, maybe?

                Comment


                • #23
                  Originally posted by Vim_User View Post
                  FWIW, PulseAudio works fine on all my Slackware systems, without lag, crackles and stuff. Blaming your problems on PA when it possibly is the configuration of your distro, maybe?
                  that's probably the cause


                  I experimented compiling PA with different CFLAGS/CXXFLAGS and in certain cases sound crackles a lot & other stuff - so it's pretty picky & fragile in that department

                  Comment


                  • #24
                    Originally posted by Vim_User View Post
                    FWIW, PulseAudio works fine on all my Slackware systems, without lag, crackles and stuff. Blaming your problems on PA when it possibly is the configuration of your distro, maybe?
                    Or how about we put the blame where it belongs? Alsa by itself works perfectly as expected. PA results in multiple seconds of lag. Clearly the problem is somewhere with PA. I suspect the lag has something to do with how much cpu usage PA uses. When playing back music with mplayer PA cpu usage is around 30% on one core. When playing back on vlc it's usage is nearly 100% on one core.

                    No matter how I look at it the problems all come down to PA.
                    Last edited by duby229; 06-04-2013, 12:05 PM.

                    Comment


                    • #25
                      Originally posted by duby229 View Post
                      No matter how I look at it the problems all come down to PA.
                      So have you tested it on a different distro or maybe even compiled it yourself (not using your distro's defaults), to see if it is actually the software or only a misconfiguration?

                      Comment


                      • #26
                        Originally posted by Awesomeness View Post
                        Why? At least on openSUSE deactivating PA is just as easy as unchecking a single checkbox in YaST
                        Like I said, *if* you want bugs fixed, you report them rather than just hope. In this case, you clearly don't care about whether they are fixed or not and you prefer to deactivate instead.

                        Comment


                        • #27
                          Originally posted by duby229 View Post
                          Or how about we put the blame where it belongs? Alsa by itself works perfectly as expected. PA results in multiple seconds of lag. Clearly the problem is somewhere with PA.
                          That is a often made erroneous conclusion. If component B works on top of A and A works independently fine but has problems working in tandem with B, the problem can be B but also be an integration issue between A and B. For instance, PulseAudio uses more of the ALSA API than any other software and some of the ALSA issues have been found and fixed over the last few years because of it.

                          Comment


                          • #28
                            Controversy generating heat faster than bugfixes

                            Originally posted by phoronix View Post
                            Phoronix: PulseAudio 4.0 Brings Many Changes

                            PulseAudio 4.0 is now available and with it comes many changes to this commonly used but sometimes controversial audio server...

                            http://www.phoronix.com/vr.php?view=MTM4MzM
                            It's one thing to point out that Pulseaudio add latency and lowers performance in an application where CPU capacity is tight, e.g 720p video on a netbook. The latter requires both no PA and no desktop compositing to work. It's quite another thing to simply talk hate about PA and people who worked their tails off to create it. That makes heat but little light and could even delay bugfixes by driving off developers.

                            Before PA existed, I wondered why Windoze machines could mix sound but my Linux boxes could only have one device at a time claiming the sound card. Newer onboard sound on good desktop motherboards have hardware mixing, but my old $7 soundcards did not. Every added running service will use up CPU and add latency while also adding its own features. That means some folks will need to use it, others will need to not use it.

                            I don't run PA on most of my machines, but it will work on all of them. The reason I don't is that 4 core processors playing AVCHD files use up all the available CPU performance, as does 720P H264 video on my netbook. My 8-core AMD can play even the "difficult" AVCHD files with PA running, but I keep my OS setups as clones of each other.

                            On the other hand, I am not about to set up a machine with no hardware mixer for a "non-geek" end user without installing PA and making it work. Hell, without PA, my netbook requires JACK to be started just to play a mono sound file, as it's sound card lacks a mono channel. PA and JACK are literally the only way that machine can play a mono audio file. I use Jack for mixing on it, as I don't mind dealing with complexity to get 720p video playback on it, but that's not really something a distro could demand of all it's userbase. To distros: just don't make so many things depend on PA that users can't remove it for more performance or to deal with software that doesn't get along with PA.

                            Yes, there are problems with PA. Use it if it works for you, remove it if it doesn't, and REPORT bugs, same as all other software. The goal should be to fix the problems, not drive off the devs so PA never gets improved again or disappears entirely.

                            Comment


                            • #29
                              Originally posted by Vim_User View Post
                              So have you tested it on a different distro or maybe even compiled it yourself (not using your distro's defaults), to see if it is actually the software or only a misconfiguration?
                              why would I want to test it on a distro that I don't use?

                              Comment


                              • #30
                                Originally posted by RahulSundaram View Post
                                That is a often made erroneous conclusion. If component B works on top of A and A works independently fine but has problems working in tandem with B, the problem can be B but also be an integration issue between A and B. For instance, PulseAudio uses more of the ALSA API than any other software and some of the ALSA issues have been found and fixed over the last few years because of it.
                                So in other words "PA improperly uses untested features of Alsa and so it must be Alsa's fault"

                                That is also the most common erroneous defense used.

                                EDIT: The fact is, whether you like it or not, Alsa works and PA does not.
                                Last edited by duby229; 06-04-2013, 04:23 PM.

                                Comment

                                Working...
                                X