search for: burg_modified_fix

Hello Opus, I?d like to report a bug in the fixed point OPUS code: line 336 (or thereabouts), operand FIND_LPC_COND_FAC should be replaced with SILK_FIX_CONST(FIND_LPC_COND_FAC ,32), otherwise multiplication by zero typically occurs. please confirm. Cliff -------------- next part -------------- An HTML attachment was scrubbed... URL:

...t 6 seconds of audio after transcoding sound Ok. After that artefacts are introduced all the way to the end of the file. The floating point version does not have the issue (even though the quality is subjectively worse roughly from the same point). I believe I narrowed down the problem to the file burg_modified_FIX.c ? if I make sure the input signal is scaled down to 14 bits before processing the coefficients of the predictor are calculated correctly and no artefact is introduced. Is anyone experiencing the same problem or has a proper fix for this? (I can work around the bug with input scaling for now). T...

...Ok. After that >> artefacts are introduced all the way to the end of the file. >> The floating point version does not have the issue (even though the >> quality is subjectively worse roughly from the same point). >> >> I believe I narrowed down the problem to the file burg_modified_FIX.c ? >> if I make sure the input signal is scaled down to 14 bits before >> processing the coefficients of the predictor are calculated correctly >> and no artefact is introduced. >> >> Is anyone experiencing the same problem or has a proper fix for this? (I >> c...

...ts are introduced all the way to the end of the file. >>>> The floating point version does not have the issue (even though the >>>> quality is subjectively worse roughly from the same point). >>>> >>>> I believe I narrowed down the problem to the file burg_modified_FIX.c >>>>? >>>> if I make sure the input signal is scaled down to 14 bits before >>>> processing the coefficients of the predictor are calculated correctly >>>> and no artefact is introduced. >>>> >>>> Is anyone experiencing the s...

...r transcoding sound Ok. After that > artefacts are introduced all the way to the end of the file. > The floating point version does not have the issue (even though the > quality is subjectively worse roughly from the same point). > > I believe I narrowed down the problem to the file burg_modified_FIX.c ? > if I make sure the input signal is scaled down to 14 bits before > processing the coefficients of the predictor are calculated correctly > and no artefact is introduced. > > Is anyone experiencing the same problem or has a proper fix for this? (I > can work around the bug w...

...>> artefacts are introduced all the way to the end of the file. >>> The floating point version does not have the issue (even though the >>> quality is subjectively worse roughly from the same point). >>> >>> I believe I narrowed down the problem to the file burg_modified_FIX.c ? >>> if I make sure the input signal is scaled down to 14 bits before >>> processing the coefficients of the predictor are calculated correctly >>> and no artefact is introduced. >>> >>> Is anyone experiencing the same problem or has a proper fix for...

...>> artefacts are introduced all the way to the end of the file. >>> The floating point version does not have the issue (even though the >>> quality is subjectively worse roughly from the same point). >>> >>> I believe I narrowed down the problem to the file burg_modified_FIX.c ? >>> if I make sure the input signal is scaled down to 14 bits before >>> processing the coefficients of the predictor are calculated correctly >>> and no artefact is introduced. >>> >>> Is anyone experiencing the same problem or has a proper fix for...

...d all the way to the end of the file. >>>>> The floating point version does not have the issue (even though the >>>>> quality is subjectively worse roughly from the same point). >>>>> >>>>> I believe I narrowed down the problem to the file burg_modified_FIX.c >>>>> ? >>>>> if I make sure the input signal is scaled down to 14 bits before >>>>> processing the coefficients of the predictor are calculated correctly >>>>> and no artefact is introduced. >>>>> >>>>> Is...

...end of the file. > >>>>> The floating point version does not have the issue (even though the > >>>>> quality is subjectively worse roughly from the same point). > >>>>> > >>>>> I believe I narrowed down the problem to the file burg_modified_FIX.c > >>>>> ? > >>>>> if I make sure the input signal is scaled down to 14 bits before > >>>>> processing the coefficients of the predictor are calculated correctly > >>>>> and no artefact is introduced. > >>>>>...

> Have you tried compiling it yourself? I just installed git for the first time and downloaded all of the latest source code packages directly from the site. I'm getting the following every time I try to (re)build any of the projects: 1>------ Build started: Project: opus, Configuration: Release Win32 ------ 1> fatal: Not a git repository: 'C:\My

...C:\My Documents\Opus\win32\config.h(43): fatal error C1083: Cannot open include file: 'version.h': No such file or directory 5> autocorr_FIX.c 5>C:\My Documents\Opus\win32\config.h(43): fatal error C1083: Cannot open include file: 'version.h': No such file or directory 5> burg_modified_FIX.c 5>C:\My Documents\Opus\win32\config.h(43): fatal error C1083: Cannot open include file: 'version.h': No such file or directory 5> corrMatrix_FIX.c 5>C:\My Documents\Opus\win32\config.h(43): fatal error C1083: Cannot open include file: 'version.h': No such file or directo...