search for: fixedpoint

Hello Jean-Marc, > Could you try mixing the encoders and decoders (encode with one > version, > decode with the other) to see whether the problem is in the > encoder, the > decoder or both. I tested that,and the results are: The fixedpoint+blackfin encoder used together with the fixedpoint-only decoder produces an bad sounding file (for all the combinations for quality and complexity I mentioned in my previous postings, and also for both WB and UWB mode). The combination fixedpoint-only encoder together with the fixedpoint +bl...

...oint or B) fixed-point only on Blackfin. Then A) sounds bad and > B) sounds good. If you do the same in narrowband, it sounds OK. Is > that > correct? If that's the case, it's *probably* some kind of bug and/or Yes, that's right, except one thing: I always use the blackfin +fixedpoint optimized encoder *and* decoder or the fixedpoint-only optimized encoder *and* decoder at one time. And I do every encoding/ decoding on the Blackfin. > invalid assumption in the blackfin assembly. Could you check if that > happens on all wideband modes (and none of the narrowband modes...

The latest SVN version breaks mdf.c when running without fixed point. Patch: Index: mdf.c =================================================================== --- mdf.c (revision 10563) +++ mdf.c (working copy) @@ -169,6 +169,8 @@ acc[i+1] += (X[i+1]*Y[i] + X[i]*Y[i+1]); } acc[i] += X[i]*Y[i]; + X += N; + Y += N; } } #endif

Hi, I was testing floating point Opus encoder. But it's calling few functions which are implemented in fixed point . I tried to find corresponding floating point functions in source. But not available. Please help me on this. Vega -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hmm, what these instructions do? (I know nothing about ARMs; I have some knowlege about x86 assemblers and programming). Cant we use pure standard C++ or Java? Does Speex work with fixedpoint math? (As far as I know Java on 6600 has no builtin floatingpoint, there is emulation class somewhere on the net, but it is probably painfully slow.) I do not know if this processor has builtin floatingpoint math module. When "current" code would be able to do it in Your opinion? &lt...

Hello all, I'm testing the Speex codec for my diploma thesis on a BF-533 Blackfin under uCLinux (2005R3 RC3 release). I successfully compiled the Speex (1.1.11-svn) and I can encode/decode wav-files on my STAMP-board using the speexenc/speexdec sample apps. But I encountered that the decoded file sounds strange/noisy, when compiling with "--enable-blackfin-asm" +

...contribution from > the sponsors in other areas would also be a key factor. I'm not sure how to interpret that, but our team here at Ericsson is fairly large, we have been working with this out-of-tree backend since 2011 and as a group, we contribute to upstream e.g. by helping out with the fixedpoint upstreaming, by solving and filing TRs (we're pretty good at testing I'd say), improving debug information and more. > > > > > Cheers. > > > > Tim. > > _______________________________________________ > > LLVM Developers mailing list > > llvm-...

Speex 1.2beta1 announcement: This new release brings many significant improvements. The quality has been improved, both at the encoder level and the decoder level. These include enhancer improvements (now on by default), input/output high-pass filters, as well as fixing minor regressions in previous 1.1.x releases. A strange and rare instability problem with pure sinusoids has also been fixed. On

Hi, I saw earlier correspondence (e.g. http://www.xiph.org/archives/vorbis-dev/200202/0131.html) on this list about porting the Ogg Vorbis libs to Symiban EPOC. I'm wondering if anyone really succeeded in doing this, and would share his experiences with me. Thanks, <p>Akos --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/

...ng? Can uclibc influence speed? We want to use speex and are considering a few ARM cpu's and the sis550 cpu (forerunner currently). Now I have to try and verify that it will encode from the soundcard on this device in realtime and transmit the data (multicasting). I was hoping that the non fixedpoint performance would be better, can it be my fault or is this expected behaviour/performance? Is there a timeframe for the 1.2.0 stable release? Ballpark? Thanks, Kobus Wolvaardt Kreon Technology On Monday 04 September 2006 16:09, Jean-Marc Valin wrote: > Speex 1.2beta1 announcement: > >...

*From: *JF Bastien via llvm-dev <llvm-dev at lists.llvm.org> *Date: *Thu, May 9, 2019 at 1:30 PM *To: *Jesper Antonsson *Cc: *dag at cray.com, llvm-dev at lists.llvm.org I don’t think you have consensus to move forward at this point in time. My > expectation, which I think represents LLVM’s historical approach, is that a > path to full support be planned out before this effort starts.

Hi, I have one question: Will Speex run in realtime (both encode / decode probably simulateusly) on Nokia 6600 --- basicaly ARM9 104MHz with Symbian 7s after porting to its C++ or Java? I am thinking mostly about the worst quality encoding (optionally duplex). Can this processor make it? Oh 6600 has something about 6mb memory if I remember good. Plase cc kangur@polcom.net in replies.

...The equivalent C struct: typedef struct { real32_T s; real_T d; int8_T i8[4]; uint16_T ui16[4]; int32_T i32[100]; uint64_T ui64[6]; int64_T i64[64]; char_T c[3]; creal_T mycomplex; int32_T enumeration_int32; int8_T enumeration_int8; uint16_T enumeration_uint16; cint32_T fixedpoint; int32_T fixedpoint2; int128m_T fimw[10]; real_T fisd1; real_T fisd2; real_T fisd3; int8_T fisb; real_T fid; real32_T fis; } struct0_T; In C the offsets are computed as: 8 16 20 28 432 << This was 428 in LLVM; 432 is divisible by 8, but 428 is not. 480 992 1000 1016 1020 102...

...gt; > > > I'm not sure how to interpret that, but our team here at Ericsson > > is > > fairly large, we have been working with this out-of-tree backend > > since > > 2011 and as a group, we contribute to upstream e.g. by helping out > > with > > the fixedpoint upstreaming, by solving and filing TRs (we're pretty > > good at testing I'd say), improving debug information and more. > > Ok. > > p.s. If my wording came across as implying any disrespect, sorry! I > was > making a general point, not thinking about how it might...

...areas would also be a key factor. > > > I'm not sure how to interpret that, but our team here at Ericsson > is > fairly large, we have been working with this out-of-tree backend > since > 2011 and as a group, we contribute to upstream e.g. by helping out > with > the fixedpoint upstreaming, by solving and filing TRs (we're pretty > good at testing I'd say), improving debug information and more. > > > Ok. > > p.s. If my wording came across as implying any disrespect, sorry! I > was > making a general point, not thinking about how it might b...

...udio path, and also give users much more detailed information on what part of their audio system they should improve. It also adds a #define SPEEX_API_VERSION, which allows compile-time checking and #ifdef'ing for whether these (and other new) functions are available. Last time I programmed fixedpoint was on a 68000, and that was democode where speed>>>correctness. I've compiled the library with both FIXED_POINT and FLOATING_POINT, and verified that both give approximately the same results, but my conversion of the weights in fixed-point desperately need some work. --------------...

On Mon, 6 May 2019 at 10:13, James Courtier-Dutton via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Although the above is mentioning bytes, looking at the "/ 8" and "& 0x7" makes it look like the author meant octets and not bytes. > Bytes can be any size of bits. I don't think you'll have much luck trying to make that stick for a general audience,

hi there, I am about to embark on a mission critical financial web application, and was wondering weather ruby on rails is the best fit for this type of project. More specifically I am worried about floating point errors. Would it be more appropriate to use a more statically typed framework (.NET)? thankyou. -- Posted via http://www.ruby-forum.com/.