That would not make a difference; it's the exact same protocol, just different cables and a bit more hardware needed in front of the receiver/transmitter chips.AES/EBU?
That would not make a difference; it's the exact same protocol, just different cables and a bit more hardware needed in front of the receiver/transmitter chips.AES/EBU?
Impedance doesn't have anything to do with a binary wire protocol. They are the same for AES, Toslink, and coax. The difference is only the physical connections. All fall under IEC 60958.I don't think it's the same protocol (but I'm no expert), starting with the different impedance.
I have limited knowledge having looked into it a bit out of interest, but never having tried implementing it. A white paper from Lattice about eARC says that one of the problems eARC was intended to fix was interoperability with ARC. IIRC it put this down to vendor-specific variations in CEC behaviour. From memory of a quick read of an HDMI spec version found on archive.org the CEC part is mandatory in ARC both for capability discovery and for flow control (start/stop of audio stream etc.) I got the impression that if the discovery fails, or there isn't a start of stream, the devices are supposed to not work. I wouldn't be surprised if some implementations are a bit more flexible about this though. Looking back it would have been useful to take notes, but I didn't.Is CEC itself or the lack of it is the cause of these compatibility problems? I found an implementation of it for Arduino, so doing the same on the Duo board shouldn't be too hard/expensive. https://github.com/floe/CEC
It's similar to TCP/IP remaining the same irrespective of the physical layer which could be wired, wireless, optical or even virtual. And each of those broad types has multiple variations.Impedance doesn't have anything to do with a binary wire protocol. They are the same for AES, Toslink, and coax. The difference is only the physical connections. All fall under IEC 60958.
From web: […] AES/EBU uses ten times the signal level of SPDIF, meaning it can tolerate more loss in long cables and if a receiver circuit has been optimised for AES/EBU it will work better as SPDIF will be at the lower limits (too much noise). […]The difference is only the physical connections. All fall under IEC 60958.
At least a pair of SUB out DSP? (been doing 2 subs since the late 1970s) one way or another.We are locked and loaded for some seriously low-cost R&D!
Hoping that this will only be true for the cheapest/simplest option but it looks like adding a passable DAC for 2 more channels would only cost a dollar more.
Yes, that's all physical...From web: […] AES/EBU uses ten times the signal level of SPDIF, meaning it can tolerate more loss in long cables and if a receiver circuit has been optimised for AES/EBU it will work better as SPDIF will be at the lower limits (too much noise). […]
That's a physical layer difference. Say I have a chip putting out an IEC 60958 compliant bit stream on a logic level pin. I could connect this output pin to one or more physical layer adapters to convert from logic level signal to AES/EBU on BNC, RCA or XLR, to toslink or to spdif coax, ARC (although that requires other stuff in parallel), Meridian's interface using network cables, or whatever proprietary thing I dream up. Even if they have the same connector they may have different voltage levels.From web: […] AES/EBU uses ten times the signal level of SPDIF, meaning it can tolerate more loss in long cables and if a receiver circuit has been optimised for AES/EBU it will work better as SPDIF will be at the lower limits (too much noise). […]
Open source HDMI implementation: not a thing AFAIKI really like your enthusiasm and wish you good luck with this project. My obvious use case for such a device would be in between HDMI devices so I hope that can be implemented.
Not fully, but maybe close enough to implement something like this. There are SBCs available with HDMI input and output that run linux but need proprietary drivers for the HDMI input. That means you're stuck with their BSP kernel (usually android) rather than an upstream one, at least so far. I don't know how this interacts with HDCP though.Open source HDMI implementation: not a thing AFAIK
It doesn’t. These boards all work only on non HDCP content as far as I know. Nevermind eARC support. There is also basically zero information to be found that might help to hack something yourself.I don't know how this interacts with HDCP though
eARC in which direction? https://forum.khadas.com/t/amlogic-kernel-5-4-on-vim3l/15869/4 claims receiving eARC 7.1 LPCM from TV.It doesn’t. These boards all work only on non HDCP content as far as I know. Nevermind eARC support. There is also basically zero information to be found that might help to hack something yourself.
This could be included at near zero additional cost as the board I ordered includes an internal stereo ADC/DAC. Assuming they're not so great quality, dual sub outs is completely practical with how unimportant distortion/FR is to them.At least a pair of SUB out DSP? (been doing 2 subs since the late 1970s) one way or another.
Ah, someone managed to get it working. That’s cool! So there is some hope after all!eARC in which direction? https://forum.khadas.com/t/amlogic-kernel-5-4-on-vim3l/15869/4 claims receiving eARC 7.1 LPCM from TV.
The chips are not the problem with HDCP, getting a decryption key is.I don't know if anybody else has looked, but you can get actual HDMI decoder chips from Analog Devices with real HDCP support for a solid $25. If one of those worked in a setup then it would be possible to have such an HDMI audio box but it would be a lot more expensive.