>Is this is a design flaw? How to tell the input frequency? Need some >additionnal hardware?
the ALSA h/w parameters are things set by an application (and perhaps later read by the same or a different application). what ALSA supports (and the hdsp driver in particular; the digi9652 is not so good here) is the notion of defining the clock source. if the clock source is internal, then some h/w (i think this applies to the digi9652) can't tell you the external rate for the ADAT signal. if the clock source is external, then you can't set the rate from an application. of course, you might want to know what it is. in which case, you have to read the relevant control, which is called "External Rate" on the hdsp series. unfortunately, an equivalent control does not exist for the digi9652 series, though it would be easy to write (i would do it if i wasn't so busy with other projects right now). i think it would have been good for ALSA to have considered this more early on; as it is, only a few cards support external clocking, and the drivers for those cards have had to make it up as they were written. >I checked it again, ADAT is only defined for 44.1/48 kHz. I mixed it up >with the Hammerfall specifications in the manual. The supported >frequencies ranges from 32 to 96kHz (SPDIF mode?) as explained, ADAT can be used up to 96kHz but it halves the number of available channels. ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
