On 06/06/2011 03:16 AM, Mark Knecht wrote:
just as a small reminder before we all go misty-eyed over the horrible
state of linux audio: in the universe i live in, there's this basic
assumption that hardware vendors should care for proper driver and
userspace support, because they want to sell their gear.
if they don't, that's their problem, take your money elsewhere.
this whole situation where people hack up drivers in their free time to
open markets to ignorant vendors is totally ass backwards. it's what
we've gotten used to, and i'm happy to have open-source drivers for the
pro gear i have to use, but let's not fool ourselves into thinking that
it's all fine and dandy this way.
don't whine here, whine on .
> Anyway, as this device is part of the HDSP family - I own an HDSP 9652
hdspconf won't support the new AIO and raydats afaik, use alsamixer
instead. i've tried to hack it a bit and actually got it to support the
hdsp madi, but it's messy and not really worth the effort imho...
but not rocket science either.
the problem is that everyone i talked to told me fltk is on its way out,
fast, and i don't really feel motivated to redo everything in gtk when i
only have two rme cards and can do everything i need with alsamixer, if
> The HDSP family has a
i know for certain that hdspmixer supports at least the hdsp pci devices
and the hdspm madi pcie, and i'm pretty sure it also supports the AIO
> There is no command line way to access the router, TTBOMK and
i guess the problem is that rme are a bit difficult to work with -
there's no-one in particular you could talk to, it's just a bunch of
freelance designer hotshots and a marketing department. they have been
helpful with specs on and off (sometimes quite late, as in the case of
the firefaces), but there has been no established relationship to any
team of driver maintainers...
> It would be great to find another developer with the interest that we
get in touch with adi. do you have any of the recent pcie rme devices?
> That said, it's possible that all you need is a new PCI device IDs
i heard the raydat and aio drivers basically work. there used to be the
problem that they would only run at 1024 frames, but looking at the
commit log, adi tackled that one a while ago.
frankly, with bug reports like "As expected, now ALSA is broken.", what
do you expect? that's really a huge waste of time. i've seen alsa break
in a hundred shiny different ways from the subtle to the spectacular,
and unless the OP gets his act together and provides some real
information, PEBKAC is what i'll be assuming.
Linux-audio-user mailing list