[Peep-develop] Re: Segfault fixed, now what? :)

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

> I fixed my broadcast address, and now the server seems to find my IP
> and bind to it, but now I'm having more problems. :)
> 
> I'm a bit confused about what's supposed to happen when I launch
> peepd. Will it create a fairly constant mix of ambient sound, or does
> it only make sounds occasionally? It's been running for several
> minutes and, though I can play MP3's and such nicely, I don't receive
> any sound. I'll include my config file below; I was a bit confused and
> may have mucked with something that I shouldn't have. I had to change
> some ports as to not conflict with some of the stuff that I'm running
> locally.

  The peep server just waits to receive sound data and then plays
them.  You need to run the utilities (Namely LogParser and Uptime) to
produce sound. You might also want to experiment with KeyTest, which
maps all the events and states to keys (you can change the volume and
stereo and stuff with the numbers keys and a shift combination).


> I'm a bit confused about:
> #a /usr/local/lib/peep/sounds/unk9.* 1                 # bah..
> and lines like that. Are those sounds which I can use for other
> events?

  Yeah.. the comments next to them detail the sound work I need to do
to fix some of them up. But they're guidlines on what Alva couch and I
felt were the quality of the sounds. Use the valid entries as examples.
So that:
a /usr/local/lib/peep/sounds/unk9.*    1 #comment

is 

mail /usr/local/lib/peep/sounds/unk9.* 1 #This is a mail event

  I suggest looking at the paper for now (Available off the website)
in order to figure out how this works..

> 
> And, out of curiosity, where does peepd get its logging information? I
> don't recall being able to specify a logfile to read from. What does
> the client LogParser section handle?

  LogParser reads logging information and produces sound event stuff .
The server just plays arbitrary sound data                           .

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