The target market for this box is studios that produce spatial audio recordings. It will be pretty bare bones for home theatre use.I do hope it will have other ip control opportunities, not just Crestron, Crestron is way too expensive. Adding cec support to control volume would be a game changer (really no option to leave it out with an earc hdmi port). Cec to support Hdmi switching (aggregate multiple hdmi inputs before the arvus) would also be a use case. Also hope Dirac support is still in as mentioned in another thread, no mention anymore on the webpage. I would strongly prefer this above a jbl sdp, if volume control would be less barebones as it now seems to be.
You aren't the only one.Looks like he switched from Dante to Merging’s implementation of Ravenna over ADI SHARC after I had a Skype call with him.
Matthew has loads of studios on-board. He decided to make this box based on demand from studios, not the home theatre market. That being said it can work as a bare bones theatre solution.Well, then the h24d article in stereophile seems little value added, target audience there is not so much studios
?? It is for anyone interested.Well, then the h24d article in stereophile seems little value added, target audience there is not so much studios
It was interesting. Too bad you didn’t get to test it with Dante.?? It is for anyone interested.
It was interesting. Too bad you didn’t get to test it with Dante.
Was the breakfast before or after the switch from Dante to Ravenna?I was not prepared to do so at that time. I am now.
We had breakfast together when he was in NY and this was one of the topics we discussed.
I can't say what was in his mind but I questioned his choice of Dante. Could that have been before or after your discussion, I don't know. We were both on the right side.Was the breakfast before or after the switch from Dante to Ravenna?
Yup.This is very important when you must sync the system clock with the incoming HDMI to the AES67 stream. As this clock must be assigned grandmaster, otherwise everything downstream won’t be in sync.
It’s for people who simply want to decode all the spatial sound bitstreams from HDMI, and have AES67 compatible dacs downstream from the device. Could be standalone dacs, digital input amps, or active speakers with AES67.FWIW the arvus site made my security software block stuff....altho not sure what use case this unit would have otoh.
So what is at the other end of the hdmi particularly? (just trying to imagine what a typical system using such might be....the downstream part is kind of a why?, too)It’s for people who simply want to decode all the spatial sound bitstreams from HDMI, and have AES67 compatible dacs downstream from the device. Could be standalone dacs, digital input amps, or active speakers with AES67.
You may need to plug the connected TV or monitor into that output in order for the incoming HDMI to sync with the outgoing. Because there’s likely some sort of async that goes on to reclock the incoming HDMI clock to the AES67 clock. This would cause some latency, also there’s likely some latency from the bitstream decoding as well. So reclocking everything would bring the timing altogether.So what is at the other end of the hdmi particularly?
A tv as source wouldn't have occurred to me, I just use them as monitors. Or ?You may need to plug the connected TV or monitor into that output in order for the incoming HDMI to sync with the outgoing. Because there’s likely some sort of async that goes on to reclock the incoming HDMI clock to the AES67 clock. This would cause some latency, also there’s likely some latency from the bitstream decoding as well. So reclocking everything would bring the timing altogether.
So HDMI in from source, and then the audio and video are split sending the decoded bitstream out via AES67, and the video out via the HDMI out port.
The TV would connect to the output. And source like an Apple TV, Amazon fire cube, bluray player, PlayStation etc would be the source.A tv as source wouldn't have occurred to me, I just use them as monitors. Or ?