<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [AMD Fusion E-350] HDMI refresh rates doesn't match expectations" href="https://bugs.freedesktop.org/show_bug.cgi?id=76564#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [AMD Fusion E-350] HDMI refresh rates doesn't match expectations" href="https://bugs.freedesktop.org/show_bug.cgi?id=76564">bug 76564</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=76564#c6">comment #6</a>) > (In reply to <a href="show_bug.cgi?id=76564#c5">comment #5</a>) > > Probably a duplicate of <a class="bz_bug_link bz_status_NEW " title="NEW --- - Radeon Audio clock running wrong speed" href="show_bug.cgi?id=71753">bug 71753</a>. > > Yes I read that report. What I don't understand is how the audio clock, uvd > clock, hdmi clock, etc relate to each other. > > For audio I use the realtek chip and it's SPDIF. I guess with the audio > clock, the HDMI audio clock is used? Which in my case is not used I guess. They are not really related on the hw side. UVD decodes as fast as it can based on it's own clocks. When the decoded frame is displayed is up to the application. The audio chip has it's own clock and the display has it's own clock. The hdmi audio information is embedded in the display stream. The monitor uses special packets that the GPU embeds in the display stream to reconstruct the audio stream on the monitor based on the display clock. There seem to be cases where the hdmi stream is not set up properly so the audio clock is not recovered properly on the monitor side.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>