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 Version 1 and Version 2 of Ticket #1178, comment 20


Ignore:
Timestamp:
05/11/16 07:18:32 (5 years ago)
Author:
Antoine Martin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1178, comment 20

    v1 v2  
    11Very interesting. What happened was that those logging errors were cutting out all the queue self tuning code.
    2 I think we have at least a workaround: r12544 + r12545 + r12546. This has been running for hours here on centos6 without any problems. But we may still need to increase {{{XPRA_SOUND_MARGIN}}} by default..
     2I think we have at least a workaround: r12544 + r12545 + r12546. This has been running for hours here on centos6 without any problems. But we may still need to increase {{{XPRA_SOUND_QUEUE_TIME}}} by default so it never hits overruns.
    33It disables all sound queue events (or at least on centos6, we ignore them since we can't turn them off).
    44r12547 makes this the default on all outdated versions of gstreamer (0.10.x branch) like the one found on centos6. {{{XPRA_QUEUE_SILENT}}} can be used to toggle this (-1 is "auto" which is the default, 1 disables the tuning code, 0 enables it)
     5r12548 catches one place where we were still adjusting min/max, causing scratchy sound to occur (just harder to hit).
    56
    67The problem with this fix is that it disables the queue tuning code added for #849, so the queue may grow large as jitter accumulates and we will never do anything to bring it back down again. This can make av-sync more difficult and cost more server side RAM.