Jack O'Quin wrote: > Samuel S Chessman <[EMAIL PROTECTED]> writes: > > > This is caused by snd_pcm_hw_params_set_rate_near parameter val needing > > to be a pointer, and alsa_driver passing in the frame rate instead. > > > > This occurs against current CVS of alsa. (2004-03-02) > > I think this is the wrong fix, Sam. > > Apparently, that parameter was changed in ALSA between 0.9 and 1.0. > For compatibility with the maximum number of systems, the JACK > alsa_driver is still compiled using ALSA_PCM_OLD_HW_PARAMS_API, which > selects the older (non-pointer) interface.
To elaborate on this: both ALSA 0.9 and 1.0 support both versions of these functions, and allow selecting between them by defining ALSA_PCM_OLD_HW_PARAMS_API or ALSA_PCM_NEW_HW_PARAMS_API. Without one of these symbols defined, the default would be the old API when compiling with 0.9 headers and the new one with 1.0 headers. All versions of the library are binary compatible with both old and new applications. > So, maybe this is an ALSA bug in emulating the older interface? In theory, this should not happen. Sam, which version of ALSA are your ALSA headers/libraries from? Regards, Clemens ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
