20 Jun
2006
20 Jun
'06
4:27 p.m.
On Tue, 20 Jun 2006 13:29:18 -0400
Lee Revell <rlrevell(a)joe-job.com> wrote:
On Tue, 2006-06-20 at 10:24 -0700, Mark Knecht wrote:
Hmm, is this it:
Index: drivers/alsa/alsa_driver.c
===================================================================
--- drivers/alsa/alsa_driver.c (revision 976)
+++ drivers/alsa/alsa_driver.c (working copy)
@@ -445,13 +445,13 @@
frame_rate = driver->frame_rate ;
err = snd_pcm_hw_params_set_rate_near (handle, hw_params,
&frame_rate, NULL) ;
- driver->frame_rate = frame_rate ;
- if (err < 0) {
+ if (err < 0 || (driver->frame_rate != frame_rate)) {
jack_error ("ALSA: cannot set sample/frame rate to %"
PRIu32 " for %s", driver->frame_rate,
stream_name);
return -1;
}
+ driver->frame_rate = frame_rate ;
if (!*nchns) {
/*if not user-specified, try to find the maximum
* number of channels */
--
Palimm Palimm!
http://tapas.affenbande.org
Many built-in/inexpensive sound cards are stuck
at 48K. Possibly this
one is also?
It's still a bug for JACK not to report any error.
Does aplay report any errors with a 44100Hz file?