I'm being PHBed into a VOIP project, and Speex sprang to mind. Bandwidth is going to be a fairly serious issue for us. With regards to a Speex enc/decoder, I was wondering: Rick Kane and David Siebert have already asked about this, but seem to have gotten very different responses - the former a call to arms, and the latter a "well, if you do it, it'll get done." What's the status of Speex as a fixed point codec? Is anything done at all? I did find some rumblings on the dev list from April between Mark Borgerding and B. Mitchell Loebel talking about handling fixed point, but I'm as of yet unsure how to check on their progress, whether it's done, whether I can help, etc. They both seemed pretty confident, and I have high hopes that they got it done. ;) The homepage suggests that Speex is appropriate for VOIP. It seems that most of the iPaqs, Intermecs, and Symbols (Your FAQ explicitly mentions iPaqs as slow - ack!) use ~200mHz or ~400mHz ARM CPUs. Is that enough for realtime encoding *while* decoding? If so, is there an estimate of how much free CPU time will remain? Enough for other simultaneous compression/decompression? How much effect would a fixed-point encoder have on performance? Should I start considering commercial codecs, such as Nellymoser's SASE and ASAO? Are there other free or commercial codecs I should be looking at? Is there maybe an analog to the comparison chart at the website that gives performance characteristics, etc? Or, maybe, even just an idea of the baseline CPU that's realistic for realtime full duplex VOIP? Also, IANAL. The xiph.org variant of the BSD license looks *really* simple, but I'd like to check and be sure. If I were to use Speex in a closed source binary-only commercial product, it would be sufficient to note the copyright and the list of conditions in the manual, yes? (I also intend to put the copyright notice in the about box, but since it's a handheld I wasn't going to give up screen real estate to the stipulations.) <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'speex-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> Also, IANAL. The xiph.org variant of the BSD license looks > *really* simple, but I'd like to check and be sure. If I > were to use Speex in a closed source binary-only commercial > product, it would be sufficient to note the copyright and > the list of conditions in the manual, yes?IANAL though we shipped UT2003 with Ogg Vorbis and are going to ship UT2004 with Ogg Vorbis and Speex and according to our lawyers that's sufficient. -- Daniel, Epic Games Inc. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'speex-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
John Haugeland wrote: > (...) > The homepage suggests that Speex is appropriate for VOIP. It seems > that most of the iPaqs, Intermecs, and Symbols (Your FAQ explicitly > mentions iPaqs as slow - ack!) use ~200mHz or ~400mHz ARM CPUs. I'm using Speex on a VoIP development platform almost successfully. I have troubles only on some Duron and Pentium processors (~800Mhz): on Windows NT (4.0, 2000 or XP), there isn't enough time to process the encoding thread, still using THREAD_PRIORITY_TIME_CRITICAL (it takes about 10-20% of overall processor time using the 5900kbps bitrate). A symptom (on these platforms) is to get some processing jitter when you exchange the foreground application. <p>Regards, -- Guilherme Balena Versiani Tecnologia e Desenvolvimento ComunIP - Soluções VoIP --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'speex-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
>>>>> "John" == John Haugeland <JohnH@senscom.com> writes:John> Are there other free or commercial codecs I should be looking at? The other notable free voice codecs are ilbc and rgl. RGL is very cpu friendly, but does lossless compression. As such, it probably, given what you wrote, will use too much bandwidth. It is documented in the internet drafts draft-ramalho-rgl-desc-01.txt and draft-ramalho-rgl-rtpformat-01.txt as well as at: http://www.vovida.org/applications/downloads/rgl/index.html ILBC uses 15.2 or 13.33 kbit/s, works well w/ less-than-perfect net connections. Internet drafts draft-ietf-avt-ilbc-codec-02.txt and draft-ietf-avt-rtp-ilbc-02.txt document the codec -- including src code -- and there is a website at: http://www.ilbcfreeware.org/ For very tight bandwidth applications speex is probably better, if you have the cpu. -JimC --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'speex-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.