[PlanetCCRMA] alsaplayer failure

[Fernando Pablo Lopez-Lezcano]

>    I tried your command but got the same failure. Still an assertion
> failure in pcm.c.

Yuck, I guess this is on the new Hammerfall right? Not much I can do
save for trying a newer version of alsa cvs to see what happens. Maybe
this should be reported on alsa-devel. "pcm.c" sounds like the generic
pcm code inside the alsa driver package, most probably some bug in the
Hammerfall code is triggering this?

Have you tried other alsa applications that play sound through alsa
other than jack and alsaplayer?

-- Fernando

> On Mon, 2002-12-23 at 12:54, Fernando Pablo Lopez-Lezcano wrote:
> > >    The current version of alsplayer seems to be failing when I try and
> > > start it without jack. It works fine with jack.
> > > 
> > >    Is anyone else seeing this?
> > > 
> > >    I've also noticed that pd doesn't work on it's own, but does work
> > > with jack.
> > > 
> > > [mark@Godzilla mark]$ alsaplayer
> > > alsaplayer: pcm.c:6293: snd_pcm_unlink_ptr: Assertion `0' failed.
> > > AlsaPlayer interrupted by signal 6
> > > [mark@Godzilla mark]$
> > 
> > This is what I get here:
> > 
> > > alsaplayer -d plughw:0 -F 44100 -f 512 -g 3 -r
> > error on set_periods (13)
> > Unavailable hw params:
> > ACCESS:  RW_INTERLEAVED
> > FORMAT:  S16_LE
> > SUBFORMAT:  STD
> > SAMPLE_BITS: 16
> > FRAME_BITS: 32
> > CHANNELS: 2
> > RATE: 44100
> > PERIOD_TIME: (11609 11610)
> > PERIOD_SIZE: 512
> > PERIOD_BYTES: 2048
> > PERIODS: [1 13)
> > BUFFER_TIME: (11609 148595)
> > BUFFER_SIZE: [512 6553]
> > BUFFER_BYTES: [2048 26212]
> > TICK_TIME: 10000
> > ***NOTE***: please consider scheduling real-time!
> > xrun of at least 4.961 msecs. resetting stream
> > xrun of at least 20.493 msecs. resetting stream
> > xrun of at least 0.481 msecs. resetting stream
> > xrun of at least 2.920 msecs. resetting stream