I find the idea of an embedded pi attractive as an audio player (maybe server) because there are lots of developers and existing audio software. I have the impression that i am not alone in this. Is this the case with the other boards being suggested?
The case with other boards is basically like a new PC without an OS. This allows you to install an OS of your choice (winxp, win7, win8.1, bsd, linux, ..) as well as all the applications you want (firefox vs chrome vs opera vs ..., microsoft office vs openoffice vs libreoffice vs ibm lotus vs ..., etc.). The upside is that you get to choose exactly what software you want, the downside is that it's not nicely packaged for you (meaning you have to invest some effort into making it work).
In this case - RPi is more like an iMac - you just copy a ready-made SD card "image" onto the card and are ready to go. The downside being that if there's something you don't like about it, it can be harder to change it.
Not saying that you cannot hack your iMac or build your own application set based on bare Raspian, but if you do, you might as well buy a platform suited for that.
The other use for the embedded micro was to allow access to setup and monitor the m_dac. Does this require significant developer input? (genuine question not rhetorical: I have no idea)
Yes.
I would have thought that it would be better to have something which definitely worked and was likely to work for the foreseeable future rather than having something technically better but for which there was no support.
Well, that depends on your definition. This exactly is the reason why I'd like hardware (like the MDAC) to use as much standard interfaces and connectors as possible - it's much easier for me to ensure that it will remain working than it is with custom components or interfaces. I have no doubt that John will support his products in the future, I guess I just come from a culture where people are actually *proud* that their products don't need their presence to live on. One of the reasons why "open source" and "open hardware" exist, btw.
My point is that a board, which has all the drivers in the upstream Linux kernel, is more likely to "work for the forseeable future" (and further) compared to a board, which needs a custom kernel (which can get outdated when the company behind it discontinues the product, etc.).
Therefore I guess it depends on how you define "support".
This is also my question! again I have no idea about the Linux software Eco system, it seem very fragmented - with various builds for different platforms, its all very confusing.
The microprocessor hardware manufacturer ecosystem seems very fragmented to me, so many choices - Samsung, Motorola, Qualcomm, Broadcom, Fujitsu, TI, Altera, MediaTek, Huawei, Atmel, ..., all very confusing.
![Smile :) :)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
It's just about the point of view.
At least with the RPi there seems to be a dedicated community. The way I see it is that we need software support, not the greatest processing power and the latest features... it just needs to be a Streamer + DNLA support & internet radio etc.
Exactly, if RPi, then because of the community. It has virtually no other advantage (well, price perhaps).