<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 31.07.2018 10:22, Harish Gaddameedi
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAF=7OnKCcvPf+VAWL77zyZJd5JeYV2ZFaayh_+SO2T5ZLECE=A@mail.gmail.com">
      <div dir="ltr"><br>
        <div class="gmail_quote">
          <div dir="ltr">On Tue, Jul 31, 2018 at 12:42 PM Harish
            Gaddameedi <<a
              href="mailto:harish.gaddameedi@smartron.com"
              moz-do-not-send="true">harish.gaddameedi@smartron.com</a>>
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="ltr">
              <div class="gmail_quote">
                <div dir="ltr">On Tue, Jul 31, 2018 at 12:11 PM Harish
                  Gaddameedi <<a
                    href="mailto:harish.gaddameedi@smartron.com"
                    target="_blank" moz-do-not-send="true">harish.gaddameedi@smartron.com</a>>
                  wrote:<br>
                </div>
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  <div dir="ltr">
                    <blockquote style="margin:0 0 0
                      40px;border:none;padding:0px"><font
                        color="#741b47"><i>Please do not top-post.<br>
                          To me it looks like that is an issue in the
                          ALSA driver and not related to pulseaudio.<br>
                          The driver must be reporting the wrong
                          latency. Did you set the loopback latency to</i></font>
                      <div
                        class="m_-1577037038960146023m_-3451819389912464530gmail_signature"
                        data-smartmail="gmail_signature">
                        <div>
                          <div>
                            <div>
                              <div>
                                <div>
                                  <div><span
style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><font
                                        color="#741b47"><i>300 ms?
                                          Default is 200 ms.</i></font></span></div>
                                </div>
                              </div>
                            </div>
                          </div>
                        </div>
                      </div>
                    </blockquote>
                    <font color="#741b47"><i><br>
                      </i></font>
                    <div><font color="#000000">Sorry, I use default
                        settings, gmail is doing top posting. </font></div>
                    <div>No, i didn't set any loopback latency. I'll
                      check with the alsa driver and get back to you.</div>
                    <div><br>
                    </div>
                    <div>--</div>
                    <div>Thanks,</div>
                    <div>Harish Gaddameedi</div>
                  </div>
                </blockquote>
              </div>
            </div>
          </blockquote>
        </div>
        <div><br>
        </div>
        <div>Hi Georg,</div>
        <div><br>
        </div>
        <div>There is one more important point i wanted to discuss, this
          is which we have capture from your reply of clock
          synchronisation. Can you conform whether the system clock and
          audio clock both are same or different?</div>
        <div><br>
        </div>
      </div>
    </blockquote>
    <br>
    System clock and audio clock need not be equal. Each sound card has
    its own<br>
    clock which might not be synchronized with system clock or wall
    clock.<br>
    Basically, if your sound card claims to run on 44100 Hz, it may be
    slightly<br>
    more or less if measured in "real" (wall clock) time.<br>
    module-loopback is normally capable of detecting the clock
    difference and<br>
    adjusts the sink-input sample rate so that the latency remains
    constant. This<br>
    is why you see in the log, that the module is not using 44100 Hz but
    in fact<br>
    some other (in your case lower) sample rate. PA then does
    re-sampling<br>
    from that rate to your sound card rate.<br>
    <br>
    For the A2DP sink (bluetooth headset or speaker) the system clock is
    used<br>
    for timing, so for this special case the audio clock matches system
    clock.<br>
  </body>
</html>