Samuel S Chessman <[EMAIL PROTECTED]> writes: > In building and running jack 0.94 from current tar, segfault traced to > alsa_driver at snd_pcm_hw_params_set_rate_near (line 388). > > This occurs when switching to 16 bit or starting with 16 bit (-S option) > > 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. So, maybe this is an ALSA bug in emulating the older interface? The patch you sent breaks JACK users still running ALSA 0.9, AFAICT. It does at least generate this compiler warning... alsa_driver.c: In function `alsa_driver_configure_stream': alsa_driver.c:394: warning: passing arg 3 of `snd_pcm_hw_params_set_rate_near' makes integer from pointer without a cast I am copying this response to alsa-devel. If I'm wrong, someone there will probably set me straight. :-) -- joq ------------------------------------------------------- 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
