Re: [ecasound] Samplerate fascism?

New Message Reply Date view Thread view Subject view Author view Other groups

Subject: Re: [ecasound] Samplerate fascism?
From: Jeremy Hall (jhall@uu.net )
Date: Tue Nov 02 1999 - 16:22:11 EET


hey that 1/s is important!

perhaps a #define to allow broken cards to work. I definitely think a
warning should be initiated. I also think it might cause underuns, then
you will be asked to read /usr/lib/oss/docs/README.performance.

The more precise, the better.

_J

Arto Hamara said:
> Kai Vehmanen <kaiv@wakkanet.fi> writes:
>
> >> > Ecasound really should lighten up when it comes to checking
> > > samplerates. After a long while of pondering I found out that my new
> > > card (sb pci128) actually _does_ work, but supports samplerates one
> > > lower than standard (ie. 44099, 22049 etc), which ecasound happily
> > > flunks as not being worth its output.
> >
> > Hmm, if I understood right, pci128's 44099 does still mean 44100...?
> > I hope other soundcard manufactures don't have similar habits
> > (of course 12345 means 22050 samples per second! :)) Of course you
>
> OSS Programmer's Manual states:
>
> Codec devices usually generate the sampling clock by dividing
> frequency of a high speed crystal oscillator. In this way it is not
> possible to generate all possible frequencies in the valid range. For
> this reason the driver always computes the valid frequency which is
> closest to the requested one and returns it to the calling program.
> The application should check the returned frequency and to compare it
> * with the requested one. Differences of few percents should be ignored
> * since they are usually not audible.
>
> So there. (OSS Program of the Month, alright ;))
>
> > could set the internal sample rate to 44099, but I don't know how
> > useful the resulting 44099 samples/sec wav files are. ;)
>
> Well, I was just trying to listen to mp3s, so that wouldn't be a problem.
> However, something tells me resampling just because of that one 1/s
> would be less than optimal thing to do. =)
>
> > Well, yesterday I spent the whole day working on ecasound and eventually
> > got it to compile... but as expected: no sound. Aarggh! It appears
> > to work normally, but something in the signal chain mutes everything
>
> Hey, kinda like my soundcard. =)
>
> --
> ,--------------------------------------------------------------,
> ,' Arto Hamara * artham@utu.fi * http://slayground.yok.utu.fi/ ,-'
> `--------------------------------------------------------------'
>


New Message Reply Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2a24 : Tue Nov 02 1999 - 16:24:54 EET