similar to: libopus 1.1.3. exe

Hi All, We are using libopus 1.0.2 lib version currently and observing one crash issue in opus_encode() function some times. ------------------------------------------- (gdb) bt #0 0x00007fcdf7c90ea2 in opus_encode () from /usr/lib64/libopus.so.0 -------------------------------------------- Anybody faced this problem earlier and have any idea whether its solved in the latest version libopus

Hello Jean-Marc, yes, it works for both 32 and 48 kb/s. Also this option marginally increases the size of the file which is understandable. I tried a few other music files and found that this stereo narrowing happens not only in the case of track I submitted (although in smaller scale) so it would be great if the final libopus 1.2 had officialy a parameter to force music "mode" of

OK, so at the link : https://uloz.to/!yyVrCY2Y8sn1/devil-s-elbow-opus-7z (https://uloz.to/%21yyVrCY2Y8sn1/devil-s-elbow-opus-7z) (change the language to English by clicking at the flag at the right upper side of the web page or just simply click at "Stáhnout pomalu" - it may take some time as the file is 55 MB+ and the download service is free) there is 7zip archive with 5 music

Hello, I'm not a programmer or Opus developer but I tried to test the sound quality of a music file (Nick Warren - Devil's Elbow, freely available from the author's Soundcloud account) encoded with libopus 1.2 RC1. I used Windows binaries from free-codecs.com. I noticed that in the case of my selected music file (which is generally harsh on lossy codecs as it's necessary to

The libopus encoder's opus_encode() method is documented as "Encodes an Opus frame". Does that mean that it always produces a single Opus frame (i.e. the number of frames in the TOC byte will always be 0)? It's not clear from the documentation, but the fact that it cannot produce a 120ms Opus packet makes me wonder if that was the intention and any multi-frame Opus packets must

I was digging around and saw a bunch of different people have created ways of building libopus for android (even I did one back in the CELT days). Is there an official one somewhere that I missed? I even notice this is the Google sources, but it seems to be a touch long in tooth at this point: https://android.googlesource.com/platform/external/libopus/+/android-wear-5.1.1_r1 I am happy to build

Hi, I'm looking for the description of possible combinations of libopus parameters. For instance in case of low bitrate encoding (voip application, SILK part) it does not have sense to set 2 channels. Audio applications (CELT part) widely use 2 channels. What about HYBRID mode? Is it closer to voip or audio applications? What is the typical number of channels? Can constant bitrate be used in

1，you say “libopusenc depends only on libopus.”but 2，so，i add speexdsp source code ， but 3，so，i 。。。 but now，what can i do。i use libopus 1.2 and 1.2beta and 1.1.3 test -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/opus/attachments/20171101/40680ea1/attachment-0001.html> -------------- next part -------------- A

Hi Matěj, I had a look at your files and it seems like the issue is that the speech/music detector thinks that some segments are speech rather than music and at low bitrates SILK tends to significantly narrow the stereo image. We're planning on adding an option to opusenc to force it to treat the input as speech/music. Just to confirm that's the issue, can you try encoding with the

I just recently found that opus_multistream_encode_float is returning -1 (OPUS_BAD_ARG) with the libopus 1.1 build but works just fine with the libopus 1.0.1 and libopus 1.1-beta builds. I tried using opus_multistream_encoder_create and opus_multistream_surround_encoder_create. Tried with coupled and uncoupled quadraphonic and uncoupled stereo encodes. I'm dynamically loading the libopus

Hello all! I'm having trouble with a cross compiled libopus for an embedded application and would like some help. preamble: embedded details: processor: bf537 kernel: Linux release 3.0.8-ADI-2011R1-svn4693, build #2834 Fri Apr 22 12:35:34 ADT 2016 toolchain: bfin-linux-uclibc-gcc release gcc version 4.3.5 (ADI-2011R1-RC4) audio interface: ALSA

Hi Jean-Marc, A simpler question. How does opus_encode() generate packets of 20ms (SILK-only or Hybrid)? Concatenating two 10ms frames or doing it straight with just one 20ms frame?

I am developing an arm based application which is soon to be released. I noticed on this list mention of neon instruction optimisations in the git version of libopus (which I will be testing shortly) whose speed improvements I would very much like to benefit from in my application. However I would also very much like to be able to release my application based on an official libopus release,

Hi I'm having a problem compiling opus-tools-0.1.7. Version opus-tools-0.1.6 seems to compile OK. I've tried with opus-1.0.3 and opus-1.1-beta. The errors are like this:- "undefined reference to `sqrtf'" etc. This OS is Peppermint Three, similar to Ubuntu 12.04. It uses:- gcc --version gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 Google says it's maybe something to do

On 10/26/2013 01:11 PM, Wang, Chris wrote: > A simpler question. How does opus_encode() generate packets of 20ms > (SILK-only or Hybrid)? Concatenating two 10ms frames or doing it > straight with just one 20ms frame? Just one 20 ms frame. It always returns a single frame except when it just can't (e.g. 60 ms CELT). > From your explanations below, opus_encode() will concatenate

Thanks Jean-Marc and Benjamin for the answers. One follow-up question. If I use a repacketizer as Jean-Marc suggested by combining two 60ms frames to form a 120ms frame, without extracting individual frames and using a new TOC, I would need to have a "de-packetizer" that does the exact opposite of repacketizer. De-packetizer would need to separate this 120ms frame into two 60ms frames

Hello everyone, For a private project I would like to make a new Internet Intercom device (for my kids and me). At the moment I use a separate DSP with Ogg/Vorbis (VS1053) but I like a challenge ;-) Is a eg. ST32F10x (cortex m3) or a new ST32F40x (cortex m4) powerful enough to do encoding and decoding ? Any existing projects to learn from? Thanks for your time, Edwin van den Oetelaar

Hi, I'm working on porting libopus to some specific platforms. Due to some restrictions of the platform and to improve the performance I had to change a bit the accuracy of some functions (fft, mdct and so on). With a help of tools provided with the source code, I can check that my changes in the code are not the cause of serious damages during decoding, and all decoding tests are passed.

Hi, I am interested in this part of the answer: "Make sure both are also linked to the same libopus (opusenc could be using the system libopus 1.0.x while opus_demo is from git)" I dowloaded a tarball distrib of libopus (1.1-beta),build and installed it,and afterwards did the same with opus-tools (0.1.7),using the former installed libopus library (also using libogg 1.3.1). When I execute

Hi Drew, I think the libopusenc patch is better, but there's still a few issues left: 1) The static MAX_PACKET_BUFFER_SIZE value is still problematic because if you link libopusenc with a new version of libopus that supports higher order projection or just more projection channels for order 3, then you will overflow the buffer. I think what you'd want is a _ope_opus_header_get_size() call