<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - audio broken in 24Hz/24p since 3.11 (regression)" href="https://bugs.freedesktop.org/show_bug.cgi?id=69675#c30">Comment # 30</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - audio broken in 24Hz/24p since 3.11 (regression)" href="https://bugs.freedesktop.org/show_bug.cgi?id=69675">bug 69675</a> from <a class="email" href="mailto:agd5f@yahoo.com" title="Alex Deucher <agd5f@yahoo.com>"> Alex Deucher</a> <pre>(In reply to <a href="show_bug.cgi?id=69675#c29">comment #29</a>) > Hm, so actual problems were confirmed fixed with this? That seems rather > strange, since that would mean the hardware counted the clock cycles wrong > for the CTS value... Maybe the HW doesn't do it per-spec, instead > calculating CTS in some other way? Yes. Using the sw cts/n values resulted in better results across asics compared to the alternative fix (using the actual pll clock for the dto calculation). Using the hw cts/n values lead to playback speed issues on some asics.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>