xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.


Changes between Initial Version and Version 1 of Ticket #1178, comment 6


Ignore:
Timestamp:
04/22/16 03:31:01 (5 years ago)
Author:
Antoine Martin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1178, comment 6

    initial v1  
    22Are you seeing underrun messages in the log output?
    33
    4 If so, r12454 + r12455 may help: you can adjust {{{XPRA_SOUND_UNDERRUN_MIN_LEVEL}}} up from the default of 50, which will allow us to force the buffer to fill up more before the rest of the pipeline is allowed to pull data from it.
    5 Note: it is still capped by other values: the range of the measured levels (which may be part of the problem if it's empty), the maximum queue level (can't have min>max).
     4If so, r12454 + r12455 may help: you can adjust {{{XPRA_SOUND_UNDERRUN_MIN_LEVEL}}} up from the default of 50 milliseconds, which will allow us to force the buffer to fill up more before the rest of the pipeline is allowed to pull data from it and empty it again.
     5Note: it is still capped by other values: the range of the measured levels (which may be part of the problem if it's empty - bumped to 150ms r12456), the maximum queue level (can't have min>max).
     6
     7Another thing worth trying is changing the default sound sink on the client using {{{XPRA_SOUND_SINK}}} (try autoaudiosink, pulseaudiosink and alsasink, maybe even osssink, oss4sink), it probably uses pulseaudiosink by default.