Hi,
With the latest changes to pcm.h and pcm.c, the CVS
version of aplay now works OK, thanks. However, the
CVS alsamixer seems to be displaying its graphics
incorrectly. Some of the columns (with the SB Live!
card) have no numbers underneath them, and the "Mic
Select" and "Mono Output Select" co
On Friday 20 September 2002 20:18, Chris Rankin wrote:
> I have installed the brand new libasound.so.2 and
> compiled the CVS alsa-utils against it. However, the
> new aplay binary just "hangs" and does not make any
> sound. The old aplay works against the new
> libasound.so.2 just fine.
--- Jar
On Sat, 21 Sep 2002, Niek van der Maas wrote:
> On Friday 20 September 2002 20:18, Chris Rankin wrote:
> > Hi,
> >
> > I have installed the brand new libasound.so.2 and
> > compiled the CVS alsa-utils against it. However, the
> > new aplay binary just "hangs" and does not make any
> > sound. The
>
>
>Sep 20 17:32:48 JOHN-ANDREWS kernel: ALSA
>../../alsa-kernel/pci/cs46xx/cs46xx_lib.c:767: BUG? (cpcm->pcm_channel)
>(called from d087abc1)
>Sep 20 17:32:48 JOHN-ANDREWS kernel: ALSA
>../alsa-kernel/core/pcm_lib.c:176: BUG: stream = 0, pos = 0xfffa,
>buffer size = 0x400, period size = 0x20
On Friday 20 September 2002 20:18, Chris Rankin wrote:
> Hi,
>
> I have installed the brand new libasound.so.2 and
> compiled the CVS alsa-utils against it. However, the
> new aplay binary just "hangs" and does not make any
> sound. The old aplay works against the new
> libasound.so.2 just fine.
>
Takashi Iwai wrote:
> the resolution of usb-audio device is 1ms. this value is fixed.
> thus you need to adjust the period size according to the sample rate
> if you want to achieve the real-time response with a small period
> size.
>
> that means:
> - the sample rate should be 48kHz (or 32kHz)
