<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hello All,<div class=""><br class=""></div><div class="">As discussed in Hamburg, I tried some settings now to fix Airplay audio output.</div><div class=""><br class=""></div><div class="">The problem is that (the original) Airplay specification defines a fixed 2 seconds latency for each audio device. Additionally, the auhal audio output has an internal buffer, which adds more delay. While we can try to keep the second latency down to a small value, we need to cope with a audio latency of some value slightly bigger than 2 secs in some way, to support Airplay.</div><div class=""><br class=""></div><div class="">Remi said that 2 sec is the maximum value supported by VLC, so this seems not to be sufficient for Airplay. As advised, I tried the following patch:</div><div class=""><br class=""></div><div class=""><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class=""><b class="">diff --git a/include/vlc_aout.h b/include/vlc_aout.h</b></div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class=""><b class="">index 630be72..86117fd 100644</b></div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class=""><b class="">--- a/include/vlc_aout.h</b></div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class=""><b class="">+++ b/include/vlc_aout.h</b></div><div style="margin: 0px; font-size: 11px; font-family: Menlo; color: rgb(52, 187, 199);" class="">@@ -37,7 +37,7 @@</div><p style="margin: 0px; font-size: 11px; font-family: Menlo; min-height: 13px;" class=""> <br class="webkit-block-placeholder"></p><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class=""> /* Buffers which arrive in advance of more than AOUT_MAX_PREPARE_TIME</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class=""> * will cause the calling thread to sleep */</div><div style="margin: 0px; font-size: 11px; font-family: Menlo; color: rgb(195, 55, 32);" class="">-#define AOUT_MAX_PREPARE_TIME (2 * CLOCK_FREQ)</div><div style="margin: 0px; font-size: 11px; font-family: Menlo; color: rgb(52, 189, 38);" class="">+#define AOUT_MAX_PREPARE_TIME (3 * CLOCK_FREQ)</div><p style="margin: 0px; font-size: 11px; font-family: Menlo; min-height: 13px;" class=""> <br class="webkit-block-placeholder"></p><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class=""> /* Buffers which arrive after pts - AOUT_MIN_PREPARE_TIME will be trashed</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class=""> * to avoid too heavy resampling */</div></div><div class=""><br class=""></div><div class="">But unfortunately, this does not seem to help as the only change.</div><div class="">The only way to improve the situation, seems to also increase the input caching size. Until now, I suggested people to increase caching to „high latency“ in the settings, which seems to fixed the issue so far.</div><div class=""><br class=""></div><div class="">As we cannot let the user change such values manually, last year I suggested to increase the default caching values for OS X: <a href="https://mailman.videolan.org/pipermail/vlc-devel/2014-April/097833.html" class="">https://mailman.videolan.org/pipermail/vlc-devel/2014-April/097833.html</a> But this patch was found ugly and was rejected.</div><div class=""><br class=""></div><div class="">Any idea how this problem can be solved? Currently, I only see the possibility to increase the default caching values, in one way or another.</div><div class=""><br class=""></div><div class="">Best regards,</div><div class="">David</div></body></html>