similar to: files missing in source - cannot build in vs 2005 or 2008

Look, how about you start from the testresample.c file? Oh, and you seem to be reading 320 samples at a time and processing 640, so that can't be good (and even beyond that your code is wrong for other reasons). Jean-Marc On 11/6/19 1:56 AM, zhouyuchen at iauto.com wrote: > Hello, > I printed the log, in/out len is not truncated, which means that the > input and output are not

Hello all I using 1.2beta3 on Windows and implementing resampler. Audio signals are being retrieved by Windows Core Audio API (e.g. *IAudioCaptureClient::GetBuffer* <http://msdn.microsoft.com/en-us/library/windows/desktop/dd370859%28v=vs.85%29.aspx>) that are interleaved 32-bit floating point signals (-1.0 - 1.0). Then, speex_resampler_process_interleaved_float returns NaN in the output

Hi all, it seems that the source for the Speex specific jitter buffer (where you put the decoder on initialisation) is missing from the source of version 1.2rc1. I can find documentation about that functionality but nothing in the code. Has anyone the source files for this functionality? thanks, Chris -------------- next part -------------- An HTML attachment was scrubbed... URL:

CentOS Errata and Security Advisory 2008:0235 https://rhn.redhat.com/errata/RHSA-2008-0235.html The following updated files have been uploaded and are currently syncing to the mirrors: s390: updates/s390/RPMS/speex-1.0.4-4.c4.1.s390.rpm updates/s390/RPMS/speex-devel-1.0.4-4.c4.1.s390.rpm s390x: updates/s390x/RPMS/speex-1.0.4-4.c4.1.s390x.rpm

Hello to all, I am trying to build speex for the Windows Mobile platform. However I am not able to build it even on Windows x86 because a source file (medfilter.c) while declared in the project settings is missing. So linker cannot find medfilter.obj and I am not able to build it. Please could anyone tell me if this is an error that I should fix manually (for example ignore the file and fix

Hello, > 2. I don't have a good source of wav data for testing. I've noticed that > introducing bugs into speex (even gross ones like returning completely > incorrect codebook entries) tends to, sometimes subtly, degrade quality > instead of blowing up. Is there an existing set of source data - and > maybe even a test harness that will do binary comparison, so I can avoid

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

The ocfs2 directory index updates two blocks when we remove an entry - the dx root and the dx leaf. OCFS2_DELETE_INODE_CREDITS was only accounting for the dx leaf. This shows up when ocfs2_delete_inode() runs out of credits in jbd2_journal_dirty_metadata() at "J_ASSERT_JH(jh, handle->h_buffer_credits > 0);". The test that caught this was running dirop_file_racer from the

In order to develop a Voip application, today i should make it robust to bit-errors over wireless networks. This is an actually lack of Speex, infact what i've understood is that if a packet arrives corrupted, i must pass NULL to the decoder in order to let it know. My target is to use UDP (with checksum field disabled) and exploit also corrupted packets giving them to the AMR codec. Otherwise

Hello speex-dev, Like several others who develop in Delphi I have searched for the speex.dll or speex.pas file to no avail. Its a pity that this compilation is not available as many developers use Delphi, and this codec does seem to be an excellent free alternative. Do you know if anyone has been able to contact John Villar the author of the delphi example? -- Regards, Alistair+

Hey everyone, We're coming up on the next merge window, and I only have a couple tiny fixes for ocfs2. I thought I'd list up what I know is outstanding, and I was hoping to find out if I was missing anything. If I am, I need to get it in linux-next and set for the merge window ASAP. - metaecc-stats This is a trivial patch I put together to track errors seen by the blockcheck code.

After successfully building R on Slackware Linux v11.0 I went to make the documentation; the texi files went fine and then I hopefully issued make dvi after having gotten the warning to the effect of "You cannot build the DVI or PDF manuals" during compilation. And, as expected I got the error ERROR: 'latex' needed but missing on your system. The problem is that latex is on

Hi All, I have downloaded libogg-1.3.0 along with speex.But,during build speex is exiting with ogg.h missing.Any suggestions will be highly appreciated. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Hi Farhan, What is the purpose of the protocol? Just to be a binary form a SIP? I mean conferencing, PTT, chat we have in h.323, sip, jingle, iax? What is the reason for a new one? The NAT traversal has been fixed for a while for all those protocols also. Diana farhan@phonestack.com wrote: > Dear All, > > I have finished documenting my Lightweight Telephony Protocol. It is > now

I ran into a similar problem. The OGG lib and header files need to be in a standard location. To get around this problem I passed the following options to the configure script. --with-ogg-libraries=<libogg_root>/src/.libs --with-ogg-includes=<libogg_root>/include. In this case I built libogg and left all of the files in the default place (so I just did make not make install).

oddcast currently doesn't do speex, or ogg-speex. One of the biggest problems currently with speex (and flac too) is client support. I've just recently added ogg-flac support to oddcast (not yet available) and in my testing found that client support for this format is horrible. On windows, Winamp and Foobar choke on it (most likely assuming that if it's ogg, it must be vorbis)

Rethinking to BER in UMTS, it seems acceptable to use speex on it do you agree? ----- Messaggio originale ----- Da: marzullo maio <marzullo63@yahoo.it> A: Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> Cc: speex-dev@xiph.org Inviato: Sabato 5 maggio 2007, 23:06:40 Oggetto: Re: [Speex-dev] AMR vs Speex on wireless networks. NB for CSD/HSCSD and WB for UMTS/HSDPA. The UMTS/HSDPA

Hello Jean-Marc, I have completed some very basic testing with unexpectedly excellent results. I am posting this to the reflector to encourage others into similar experiments. My experiment consisted of processing a 200-second long sample taken from a ham radio shortwave receiver, with a variety of signals (some strong, some weak - that is, weaker signals have more noise, and the noise is

Mainline commit a5a0a630922a2f6a774b6dac19f70cb5abd86bb0 In ocfs2_dentry_attach_lock(), if unable to get the dentry lock, we need to call iput(inode) because a failure here means no d_instantiate(), which means the normally matching iput() will not be called during dput(dentry). This patch fixes the oops that accompanies the following message: (3996,1):dlm_empty_lockres:2708 ERROR: lockres

hi this code gives me a warning: SpeexStereoState stereo = SPEEX_STEREO_STATE_INIT; modules/speex/mod.c: In function 'alloc': modules/speex/mod.c:61: warning: missing initializer modules/speex/mod.c:61: warning: (near initialization for 'stereo_init.reserved1') would it be possible to add this patch to you svn ? Index: include/speex/speex_stereo.h