Hello Benny, Well...WAV is actually only a container format. The wav-player (as well the wav-writer) always already had support for CCITT u-Law and a-Law for long time. More specific, the used tags are PJMEDIA_WAVE_FMT_TAG_ULAW and PJMEDIA_WAVE_FMT_TAG_ALAW. As I understand this is also written somewhere, but I cannot remember where. It mentions that 16-bit PCM (WAV) is default, but also CCITT a+u-law, 8kHz, 8bit, mono (WAV) is supported. A follow-up ticket on #597 (#3407) was even addressing an padding issue on those formats. But for my notice and future projects... You you now mentioning that this format will be dropped? With regards, Eize Slange > Well, actually the WAV player never supports non-PCM data, so how > could you do that is a mystery! When opening the file, the player > should reject non-PCM WAV, no? > > Benny >> Hello all, >> >> With the introduction of ticket #597 (Error reading WAV files when there is >> extra chunk AFTER data chunk), the wav-player is now broken for CCITT >> u/a-law encoded WAV-files. The default 16-bit PCM files are handled OK. >> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20111019/107b70df/attachment.html>
