-- [ Picked text/plain from multipart/alternative ] The thing is, as things currently stand with the default miles codec is that nobody can use it effectively. At least with speex you would be satisfying 90%??? of you user base with a codec that people can actually use and understand. Our CS 1.6 Servers have no complaints from people with it set to: sv_voicecodec voice_speex sv_voicequality 4 So unless its a Source specific problem with speex, I personally do not see what the problem really is? Is it not worth the minor hassle of a disgruntled 10% (from our experience with speex it would be considerably less) and have a codec that was useful rather than the current default codec that nobody can understand. Moreover, how about letting Server Admins have the opportunity to find out just how big a problem this is for you, by at least offering it as an option in SRCDS. Just put in the cmd notes a warning that there could be problems. Is that a good idea Alfred? Cheers
On 7/23/05, Alfred Reynolds <[EMAIL PROTECTED]> wrote: > > Speex has some ugly coding artifacts when the incoming voice stream is > clipped (i.e the volume exceeds the bounds of the mic device). We have > been looking for a better behaving codec but haven't found one yet. When > we do we will add it. > > - Alfred -- _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
