[Alsaplayer-devel]Alsaplayer and Hammerfall

patrick reardon spatrick@flash.net
Sat, 16 Feb 2002 20:36:13 -0600

Andy Lo A Foe wrote:
> On Sat, Feb 16, 2002 at 01:36:14PM -0600, patrick reardon wrote:
> > i just installed jackd last week and the commmand you sent worked immediately!!
> > thanks!  i tried Alsaplayer with a few WAV files made here with "arecord -f cd"
> > (cd option = S16_LE @ 44100, stereo).  there is some difficulty so far with
> Great! You should update jackd from CVS since there was some changes
> made in the last couple of days (and hours).
okay, updated jack.  then started jackd as root to run with realtime scheduling.

#jackd -d hammerfall -r 44100 --realtime --verbose

but then alsaplayer wouldn't connect to jack as a normal user.  i got this.

$ alsaplayer -o jack
AlsaPlayer 0.99.53
(C) 1999-2001 Andy Lo A Foe <andy@alsaplayer.org> and others.
cannot connect to jack server
cannot connect to default JACK server
jack server not running?
failed to load output add-on. Exiting...

so i started alsaplayer as root too.

#alsaplayer -o jack

it sounds perfect!!  speed is just right and i can't cause a dropout or pop even
with lots of other activity.

BTW, without the -r 44100 option to jackd, the PCM device defaulted (i guess
that's what happened) to 48000 KHz which alsaplayer reported when it started
up.  that must be why the WAV's i tested (all recorded at 44100) seemed about
10% too slow.  

i also tried (again running jackd without the option -r 44100) passing
alsaplayer the option "--frequency 44100" but it made no difference and the
WAV's still ran slow.  

thanks again,