similar to: [PATCH] opus_demo: remove unused but set values

Hi, so here it is, LZ4 compression method inside btrfs. The patchset is based on top of current Chris'' for-linus + Andi''s snappy implementation + the fixes from Li Zefan. Passes xfstests and stresstests. I haven''t measured performance on wide range of hardware or workloads, rather wanted to publish the patches before I get distracted again. I''d like to ask

- Replaced blanket #define of 8 & 64 bit types with typedefs for each platform to match 16 & 32 bit types. - Updated existing typedefs for each platform to fix odd values and improve consistency. --- include/opus_types.h | 125 ++++++++++++++++++++++++++++++++++++++++----------- 1 file changed, 100 insertions(+), 25 deletions(-) diff --git a/include/opus_types.h

opus1.1.2's bug opus1.1.2's effect is poor in a set of parameters when processing a specific audio file. input file:data.pcm some changed parameters in opus_demo.c is :use_vbr = 0; complexity = 0; packet_loss_perc = 16. opus_demo.exe command line:voip ?16000 1 17000?-cbr -framesize 20 E:/data.pcm E:/dec_data.pcm if the bitrate_bps is changerd from 17000 to 16999,the

Hello all, after FOMS I decided to take a look at the opus library and I found that I could improve a bit the build system and cleanup the code a little bit. Most of the changes to the code has been suggested by my two tools cowstats and missingstatic (part of the ruby-elf gem if you care). HTH, Diego

If you encode with int iByteSizeEncoded = opus_encode(m_enc, m_ShortsInput, (1920/sizeof(short)), m_EncodedBytes, (960*6)); ... the byte size is 120. I thought that an odd value like 359 has to be a fault on my side. I thought it would be a multiple of something. So 359 is really correct??? Thank you for clearing this up. Am 06.10.2013 16:50, schrieb Jean-Marc Valin: > Why

Hello everyone, I'm evaluating the Celt in terms of robustness against bit errors. So what I have done is encoding a wav file using the \tools\celtenc.exe and then manipulated the wav file according a desired bit error rate or burst error length. But the Celt decoder stops decoding with the first bit I manipulated even if this bit is not in the header. So is there a way to do the test