Is Dirac the frog who aspired to become as big as the ox?

[Todd Anderson]

I may be wrong, but the way I've always viewed Dirac is that they have a technology and a server-side software and they license to hardware manufacturers the API to communicate with their software, but the user hardware-side integration is the responsibility of the hardware manufacturer to develop. If Dirac works with some products but not with others, that seems like a hardware manufacturer responsibility to address.

Similarly, I think we're finding hardware manufacturers discovering that when they licensed the tech, promised customers the feature, and sold them hardware and licenses, they did so before implementing Dirac and later found their hardware to be incapable of performing the task at hand. I've been watching this happen since Emotiva started implementing Dirac in the XMC-1. Big promises, underpowered hardware, shampoo rinse repeat.

Admittedly I don't know anything about the crossover bug mentioned in the first post.

This is how I understand it as well. This isn't sold as a plug and play solution, but rather something that manufacturers implement. Its up to them to code. A company like StormAudio is likely unique, where the coding is done in-house. I don't think you can say the same for brands like Onkyo. Not picking on Onkyo - just using them as an example.

When you outsource, it's a lot more difficult to quality control.

Following this.