similar to: About wideband encode

Hi Jean-Marc and All, Two things need your confirmation/suggestion. 1) First, I think there is a bug in libspeex/lsp.c line 512. /* hard limit ak's to +/- 32767 */ if (a < -32767) a =32767; // This line should be changed to if (a < -32767) a = -32767; if (a > 32767) a = 32767; ak[j-1] = (short)a; 2) About the RTP wrapper for VoIP I'd like to use the

In a word, I don't what's the standard of speex payload format. The file doc/rtp.txt is for what? Is it not for rtp payload? I find that rtp.txt is more detail that draft02.txt Which rtp docment should be followed? Anyone else has written the RTP wrapper already? Lianghu On 11/22/06, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > > > 1) First, I think there is

if the new draft in the manual is used. I don't find how to tell the decoder which mode(NB/WB/UWB) is used in the encoder. The RTP header don't contain the mode field and I don't find the mode information in the coded frame either. Does this mean we have to use NB decoder in all cases? Lianghu On 11/22/06, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > >

Hi, I'm about finished developing a QuickTime component that supports Speex (on MacOS X and Windows).. As it is now the user can set complexity (SPEEX_SET_COMPLEXITY) and quality (SPEEX_SET_QUALITY / SPEEX_SET_VBR_QUALITY) and to wether to use VBR or not. Will these options make it possible to produce all combinations of bitrates/qualities? Or should I also use

> 1) First, I think there is a bug in libspeex/lsp.c line 512. > > /* hard limit ak's to +/- 32767 */ > if (a < -32767) a =32767; // This line should be changed to if > (a < -32767) a = -32767; > if (a > 32767) a = 32767; > ak[j-1] = (short)a; Oops. Thanks for pointing that out. It's fixed in svn. > 2) About the RTP wrapper for VoIP

Hi Jean-Marc, Hi Jim, I have also seen some problems with the 1.1.8 release on the C55x. So far I have boiled down the issues to the following: 1) We need our own "fixed_xx.h" header file. I don't know why, and haven't had time to investigate, but there is a definite improvement when I use the attached fixed_c55x.h file which has turned all the maths into inline functions.

lianghu xu wrote: > In a word, I don't what's the standard of speex payload format. > The file doc/rtp.txt is for what? Is it not for rtp payload? > I find that rtp.txt is more detail that draft02.txt > > Which rtp docment should be followed? > Anyone else has written the RTP wrapper already? Oh, I see. doc/rtp.txt was a very, very early draft. See the manual for a

There's a field in the SDP description for narrowband/wideband/ultrawideband. Jean-Marc lianghu xu wrote: > if the new draft in the manual is used. I don't find how to tell the > decoder which mode(NB/WB/UWB) is used > in the encoder. The RTP header don't contain the mode field and I don't > find the mode information in the > coded frame either. > >

Add a copy of the libvirt-ocaml library, currently available at: https://libvirt.org/git/?p=libvirt-ocaml.git;a=summary This is a snapshot at commit d3ed8dcf1b0a6a8a855ceecbe0bb97f21e6665e3, which has all the features we need (and that builds fine). It is expected to stay synchronized with upstream, until there is a new upstream release, and it will be widespread enough. --- .gitignore

Dear Jean-Marc and Peter: Thank you both very much for your time and advice. I did not realize that Lame MP3 code has a -r option (without reading its code). I have tried the suggested command lines verbatim with the added -r option, along with other combination of option settings. I could not figure out how to eliminate the distortion in the result, like voice turning either high or low

> I'm about finished developing a QuickTime component that supports Speex > (on > MacOS X and Windows).. As it is now the user can set complexity > (SPEEX_SET_COMPLEXITY) and quality (SPEEX_SET_QUALITY / > SPEEX_SET_VBR_QUALITY) and to wether to use VBR or not. Will these > options > make it possible to produce all combinations of bitrates/qualities? Or > should I

Hi, I think what happened is that you did not write the "message" length. With user-callbacks, you also need to say how large the message. The size is in bytes and encoded in 4 bits. Besides, you're probably the first one to use user-callbacks. BTW, why didn't you want to use Ogg. It's much simpler to use and overhead can be made minimal anyway. Jean-Marc Le ven

Hi, Sorry! Marc Gimpel. I wrote it in a false thread before. It was my first time. :-) I have to write a small programm which should be able to record speeches and in addition synchronize the recorded speeches with measuring data. My idea is to record the speech in the normal way with speex and without ogg. If a sync message was received, i write a custom in-band messages using mode 13

Thanks! Btw, have you tried using SBR-technology or similar with speech codecs? That might be a good idea I thought.. But I don't know if it produces as good quality with speech codecs as it does for music codecs. Do you know if there is any open source variant of SBR? /Pontus -----Ursprungligt meddelande----- Från: owner-speex-dev@xiph.org [mailto:owner-speex-dev@xiph.org]För Jean-Marc

On Fri, Apr 4, 2008 at 12:19 AM, Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> wrote: > Jahn, Ray (R.) a ?crit : > > > Dear Speex codec community: > > > > I am working on conversion of voice files. I could not figure out how to use speexdec.exe 1.2.3 in piped mode in order to avoid the creation of the potentially large intermediate *.wav or *.pcm files. Any

libvirt-ocaml is used only by virt-v2v, so move it to this repository, instead of having it around in the common submodule. The removal from common will happen later. Pino Toscano (2): common: Bundle the libvirt-ocaml library for use by virt-v2v build: switch embedded copy of libvirt-ocaml .gitignore | 2 + 3rdparty/libvirt-ocaml/Makefile.am |

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all