Comment # 8
on bug 76564
from jeroen
(In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #5) > > > Probably a duplicate of bug 71753. > > > > 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. Okay, but doesnt that mean in this case it is a problem with the display (HDMI?) clock, as I am not using HDMI audio? Is there a way I could get more detailed logging of what is happening on my system?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
