Re: [Peep-develop] Re: Peep-develop digest, Vol 1 #2 - 2 msgs

[Michael G. <mg...@ee...>]

On Tue, Dec 12 @ 20:00, Nolan Darilek wrote:
> Peck doesn't work for me at all, either. It doesn't do anything. I've
> tried running it on everything from 2000-2003, but no luck. I also
> scrapped my peep.conf and started over, but that didn't work either.
> 
>     Michael>   I suggest compiling with ./configure --enable-debug=0
>     Michael> to help diagnose your problem.
> 
> Done. When I run ./Peck without the -server/-port options, I receive:
> Server received a packet: Received size: 10 and struct Packet size: 136
> Packet header:
> Major ver: 1
> Minor ver: 0
> Type: 4
> Reserved: 0
> Got client event
> 
> Received Event:
> Event.type -> 1
> Event.sound -> 0
> Event->location -> 128
> Event->volume -> 0.501961
> Event->priority -> 0
> Event->dither -> 255
> Event->mix_in_time -> 0
> 
> Fade value was 255. Ignoring...
> Set StateVolumes[0] to 0.050196
> Set StateFade[0] to 0.700000
> <and a bit later>
> Received alarm. Letting valid clients know we're still alive...
> Have 0 host entries prior to purge...
> Purged 0 hosts...
> 
> This also looks the same when I use -server/port.
> 
> Hmmm...the plot thickens. :)
>
   Heh. That sort of output means it received the packet correctly.
By default, Peck sends a singla for a state sound (type == 1) with
(sound == 0)... 

  The alarm is just the mechanism which tells Peep to wake up and
check it's hostlist to see if it no longer needs to keep track
of clients. 

  In other words, it looks great. So, now I'd start looking at your
sound stuff. What system you on? If on redhat, check aumix or something
of that sort. Make sure you can play mp3s.. Hopefully, you've compiled
with /dev/audio support (DEVICE_DRIVER) - try using /dev/dsp instead.
But your peck is working .. it's just having problems playing sounds.
At least now you know where the problem is. 

-- 
Michael Gilfix
mg...@ee...