BUGS:
Low frequenzy buzz:
I had a few problems on an amplifier I was trying to use in my car.
Apparently in normal operation mode when bothe amp and cp are connected 
to the same power source a very loud low frequenzy buzz gets into the amp.
If you start the mixer from within the client this buzz dissapears.
I do non really know why but I'll try to work it around having a bogus 
mixer running all the time.

Broken pipes at startup:
Sometimes, immediately after loading the first song mpg123 gets muddled up and
dies, this causes a broken pipe malfuntion in cm3s. This may not be an mpg123
bug and could actually have something to do with the way I chose to dialog
with mpg123 (via pipes). Well if I want anyone to be able to write clients
easily for this app then I cannot do much about that. On the other hand I could
try to implement a version that uses shared memory for eg ... but this would 
encrease the difficulty of making clients. I'm open to any suggestions.


Buzz after some time of playback:
It seems that since I introduced some of the features that mpg321 has
I also got this side effect. Maybe I'm skipping too many frame status
outputs. If you restart cm3s on the same track the problem disappears 
so I don't think it is strictly a mpg321 bug. I'm working on this.
I have found 2 mp3 that if played in the same sequence they reproduce 
the problem which is giving me some concern about it being an mpg321
bug or a bug in my code. 
Please let me know if you get the same problem on mpg123.
N.B. Sometimes the problem mysteriously disappears as if you let the track 
finish naturally.
I reduced the skipped frame status printing to a default of 10 but the 
problem still persists sporadically :-<

jam:
Sometimes cm3s seems to stop reading from status pipe ... 
this eventually puts mpg123 in sleep coz the pipe is full 
and waiting to be read.
This only happens if you are using the client and not if you let cm3s
work by itself.
It is probably due to bothe client and mpg123 writing to the same pipe
maybe I should use some semaphore or induce mpg123 to produce less trash 
as playing frames.
mpg321 already supports this, but mpg123 does not, the configure script 
should sort this type of problem for you and make the best out of the
player found on your system!

On some platforms cm3s fails to start in daemon mode from at boot time 
(trough the rc scripts)
You will never notice this unless you want to start cm3s automatically at
boot time.
If you want to do this, which is likely if you intend to use this in a car, 
you need to leave cm3s run as root.
At present the install process also puts in prefix/bin/cm3s_boot a copy of 
cm3s that belongs to root and does not drop root privileges nor set user on
execution.
N.B. before doing this you should check that cm3s has write permissions on 
bothe audio device and tmpdir.

broken pipes:
It is not really a bug, but can happen if the player on your system 
closes down real brutally due to some unhandled internal error.
It happens coz after the player terminates the pipes get closed at the end 
that was handled by the player while the father process (cm3s) still
has the other end of the pipes open.

There are many more bugs for you to discover :-) 
If you find one please let me know (even if you fixed it yourself)
You can send me an email at louigi600@yahoo.it