Ashhar Farhan wrote:> > dear Anders, > > the speex encoder really does not know when you are ending a wave file. > most probably there is a one-off error in your loop that reads the wave > file and you are incorrectly reading the end of the wave file.Hmmm, I am using code ripped verbatim from speexenc. Are there any known bugs of this kind in that?> btw, it will be much better to use the 1.1.6 version. it is clean and > the binary is avaialbe from the website. very few of us remember 1.1.6. > Any particular reason why you have to use 1.0.4?Well, it /is/ the latest stable release :) A
Anders S. Johansen (SecondGuess ApS)
2005-Feb-02 16:27 UTC
[Speex-dev] BUMP: "Click" at end of SPX files?
Hi, I need to re-state my question, as I never found a solution to my problem (described below in original text). One suggestion was to use the encoder from the newer, unstable, 1.1.6 release, but I need to know if I can use decoder code I grabbed from the speexdec enclosed in v. 1.0.4, and if not, what I should do then. Obviously I'd like to avoid breaking my build, by introducing new code into my project at a late state... It is kinda urgent - this is code for a commercial product, which /was/ on the verge of release, when this problem was discovered. I do not have the expertise to solve it myself. I /am/ willing to pay for a solution, if need be. Sincerely, Anders S. Johansen, SecondGuess ApS Original post follows: "I am experiencing some unfortunate problems when encoding WAV files to spx using version 1.0.4. A "click" which is not present in the original WAV file is added to the end of the spx file. Is this a known problem, and if so, which version of the encoder should I switch to... and if I have to switch the encoder, will I also have to switch the version of the decoder?"
Hi Jean-MArc (and others), As I say in my mail, signal processing is NOT my area of expertise, and I am lost. I haven't the faintes clue about what you mean by "DC offset". This is why I offer paying someone (ANYONE!!!) to solve the problem. I am aware it's beyond my abilities right now, and am willing to pay someone who /does/ know what he is doing to fix it for me. I am sure I could fix it myselv, given the time to enter a new field of expertise, but I am simply too busy doing other code on the project AND finishing my ph.d. :( Sincerely, Anders S. Johansen Jean-Marc Valin wrote:> Hi Anders, > > As (I think) I said earlier, did you check that you have no DC offset in > the file. That's the most likely cause I see for that problem (along > with not removing the last few samples as you should do). > > Jean-Marc > > Le mardi 11 janvier 2005 ? 08:16 +0100, Anders S. Johansen (SecondGuess > ApS) a ?crit : > >>Hi, >> >>I need to re-state my question, as I never found a solution to my >>problem (described below in original text). >> >>One suggestion was to use the encoder from the newer, unstable, 1.1.6 >>release, but I need to know if I can use decoder code I grabbed from the >>speexdec enclosed in v. 1.0.4, and if not, what I should do then. >>Obviously I'd like to avoid breaking my build, by introducing new code >>into my project at a late state... >> >>It is kinda urgent - this is code for a commercial product, which /was/ >>on the verge of release, when this problem was discovered. I do not have >>the expertise to solve it myself. I /am/ willing to pay for a solution, >>if need be. >> >>Sincerely, >> Anders S. Johansen, SecondGuess ApS >> >>Original post follows: >>"I am experiencing some unfortunate problems when encoding WAV files to >>spx using version 1.0.4. A "click" which is not present in the original >>WAV file is added to the end of the spx file. >> >>Is this a known problem, and if so, which version of the encoder should >>I switch to... and if I have to switch the encoder, will I also have to >>switch the version of the decoder?" >> >> >> >>_______________________________________________ >>Speex-dev mailing list >>Speex-dev@xiph.org >>http://lists.xiph.org/mailman/listinfo/speex-dev >>
Jean-Marc Valin wrote:> Hi Anders, > > The first thing would be to mention what encoder and decoder you are > using. What I suspect is that the bug is simply in the decoder, although > there are possible workarounds in the encoder.I am using speexenc/speexdec from the stable version 1.0.4. The problem is found both when using pre-compiled binaries and when using a re-compiled version. I re-compile using Borland C++ Builder version 6, patched with the newest updates (update 4). A
Can you provide me with: 1) The original wav (or raw) file 2) The encoded (.spx) file 3) The decoded file (wav or raw) Either send it to me by email (< 2MB), or put them up somewhere I can get them. Jean-Marc Le mercredi 09 f?vrier 2005 ? 22:10 +0100, Anders S. Johansen a ?crit :> Jean-Marc Valin wrote: > > Hi Anders, > > > > The first thing would be to mention what encoder and decoder you are > > using. What I suspect is that the bug is simply in the decoder, although > > there are possible workarounds in the encoder. > > I am using speexenc/speexdec from the stable version 1.0.4. The problem > is found both when using pre-compiled binaries and when using a > re-compiled version. I re-compile using Borland C++ Builder version 6, > patched with the newest updates (update 4). > > A > > _______________________________________________ > Speex-dev mailing list > Speex-dev@xiph.org > http://lists.xiph.org/mailman/listinfo/speex-dev-- Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca> Universite de Sherbrooke