Hacker News new | ask | show | jobs
by gizmo 659 days ago
Don't you also need ARC because of video post-processing that adds frames of latency? The TV needs to send audio back to the receiver otherwise video and audio will not be in sync anymore. Receivers/amplifiers can process audio with practically no latency so it makes sense for them to be at the end of the chain.
2 comments

You don't need ARC to address a/v sync. HDMI has (optional) metadata somewhere (edid?) where the display device indicates its delay and the audio device can adjust accordingly. It's helpful if the display device has fixed delay for this feature to be most effective; it's fine if there's different modes with different delays and the current delay is communicated, but some modes have variable delay depending on content which is terrible in several ways.

IMHO, ARC is primarily useful when the display device is also acquiring the content: it's running the TV tuner or internet streaming or content off a usb drive. It's also useful if you have a 1080p capable receiver and upgrade to a 2160p(4k) display and sources: if you put the receiver in the middle, you lose on video quality, but with eARC the display can route full quality audio from all your sources. Some sources do have two HDMI outs, so you could wire to the display and the receiver, but that's not very common.

Ugh, DisplayPort already has the audio channel. As far as sync, neither protocol provides for effective reclocking or supplies the audio clocks, and you need VRR to provide sort of display clocks.
DisplayPort has the audio channel but AFAIK has no _return_ channel. Which is not needed in the typical computer setup but quite useful in a TV + soundbar or AVR setup.
I admire your exasperation on this issue :)