Since you were using an SDP-55 before, I presume you're using Dante?
I was using Dante with the JBL, yes. As you can probably read elsewhere, it is not a great Dante implementation, unfortunately. It was
extremely slow when switching codecs. I think the DSP solution they used is slower than average at detecting it, and then there is some kind of weird clocking reset going on with Dante. Ironically, though, it did not have this issue when just sticking with stereo, unlike the weird issue I described above with the Arvus.
I really wanted the SDP-58 to work out, because it has built-in HDMI switching and HDMI-CEC and other consumer AV processor niceties that pro gear doesn't have. But it was nothing but trouble, really. Firmware updates are weirdly complicated – the option to do it in the management web app just doesn't work – and I'm not sure why my unit wasn't fully updated from the factory in the first place, since I got it years after the most recent firmware update. The DSP hardware itself actually failed, first slowly and then completely over time. JBL fixed it under warranty, but the bad Dante implementation and absurdly slow codec switching that I was hoping would be fixed unfortunately remained. Incidentally, it
was very nice to be able to email or call JBL Synthesis and actually get a response. And the warranty process was painless.
Did you get any benefits from using the Arvus instead of the JBL?
The Arvus
would have been a little cheaper, if I'd done that from the beginning. It also seems to have a much better Dante implementation. It has a Dante Broadway board in it that supports higher sample rates – the JBL is limited to 48 kHz, which is fine, really, given the content that's available. The Arvus also has a word clock input that's tied into the Dante board, so I have that connected directly to the clock out of the internal clock on the DAD Core 256. This is, of course, totally unnecessary, as Dante's whole thing is precise clocking over the network via PTP, but it's a neat "pro" feature.
I also decided to rely entirely on GLM for volume control, so the digital volume control the JBL was doing was an unnecessary feature at that point. And finally, the Arvus is only 1U instead of ~4U. I have no idea why the SDP-58 with no amps is so huge, but given the DSP chip failure, it maybe has something to do with heat management. The HDMI boards seemed to get
very hot.
The Arvus still has annoying delays when switching codecs – I think sadly everything does? – But it's way better than the JBL and probably on-par with say Denon/Marantz. Except, of course, the horribly annoying 2-channel PCM bug described above.
Could you elaborate on "it supports up to 192 kHz if you really want it to"?
I just mean you
can set the Dante sample rate to 192 kHz, but I don't think you can actually get any input at 192 kHz over HDMI (2.0), and certainly not from the sources I'm using. I guess this would still be helpful if you wanted to integrate the Arvus into a bigger network of Dante devices that are clocked at 192k for other reasons.
To be honest, I'm not sure where in the Arvus sample rate conversion takes places, but I'm thinking it's in the Dante board. You can't configure sample rate anywhere other than Dante Controller, even if you aren't using the Dante outputs. If you want, say 96 kHz on the AES outputs, you have to tell the Arvus to sync the clock to Dante and configure its Dante device to 96k.
The only other option on the Arvus is to sync to the HDMI clock, which means the output sample rate matches whatever the HDMI input is. In theory this seems great, and I tried it, using the AES3 outputs on the Arvus instead of Dante, but the Genelec speakers took a long while, several seconds, to deal with the AES clock rate change, flashing their LEDs red multiple times in the process, and still seemingly trying to output at the existing rate. The results were not good. I don't know who's at fault there or if that's just par for the course with on-the-fly AES3 clock changes. Regardless, the Genelec speaker internal DSP does SRC on the input to 96 kHz anyway, as far as I know, so it makes sense to me to just send the speakers 96k.