[pulseaudio-tickets] [Bug 48307] New: Volume changes can be delayed a lot

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=48307

             Bug #: 48307
           Summary: Volume changes can be delayed a lot
    Classification: Unclassified
           Product: PulseAudio
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: core
        AssignedTo: pulseaudio-bugs at lists.freedesktop.org
        ReportedBy: tanuk at iki.fi
         QAContact: pulseaudio-bugs at lists.freedesktop.org
                CC: lennart at poettering.net


Created attachment 59487
  --> https://bugs.freedesktop.org/attachment.cgi?id=59487
Log of delayed rewind

This was reported in IRC by "uau". For him, sink volume changes happen with a
large delay (like after a second). I have spotted one obvious bug in the source
code: when the sink volume is changed, but the software volume doesn't need
adjustment, the hardware volume is changed after whatever latency there happens
to be at the moment of the volume change request, which tends to be large. If
the software volume needs to be changed also, the sink is rewound, which will
make the hw volume change happen earlier. So, the missing rewind is messing
things up.

That is not the only problem, however. uau is having delays also when the
rewind is happening. When I try changing the sink volume on my machine (with
the current git master), the rewind happens before the volume change is
applied, as expected. But for uau, the rewind appears to happen after the hw
volume has been changed, i.e. about a second late. I haven't really
investigated yet how that could be possible. uau is using Pulseaudio 1.1, the
"current debian unstable version". Here's a log sample: http://fpaste.org/DVTW/

I'll also attach that log, in case the pastebin url becomes stale.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.