On Sun, Jul 19, 2009 at 5:00 PM, Paul Davis<paul@xxxxxxxxxxxxxxxxxxxxx> wrote: > On Sun, Jul 19, 2009 at 7:26 PM, Justin Smith<noisesmith@xxxxxxxxx> wrote: >> I have an ensoniq audiopci card that I have been using successfully at >> 48000 hz for a while now. I have just started working on a project >> with prerecorded material at 44100 hz, so I reconfigured jack in order >> to avoid needless sample rate conversion. Somehow jack thinks that my >> card is running at 44099 hz, so it is resampling the source material >> anyway. >> >> Why would my card be running at 44099 hz, is this a software or >> hardware problem? I am going to just edit the wav headers to say 44099 >> so they agree with the engine sample rate for now, but would be >> interested to know what the source of this weirdness would be. > > its reported by the ALSA driver, which in turn is written based on > information available about the h/w. its debatable what ALSA should > report in these situations, but its a driver-level issue, and not > something in JACK's domain. > > JACK does NOT resample audio, ever. neither does ALSA if you use the > hw:N device(s). > Sorry, I was conflating jack and ardour, I meant that ardour was wanting to resample. I used sox to copy the audio files to .raw, and then converted the .raw files to .wav at 44099 sampling rate. I had a suspicion it may have been the alsa backend, thanks for the info. _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
