similar to: Plans for libopus-1.2 release?

I am working on a project that transports audio in realtime from a linux box to a windows box throuh libcelt. The windows client program is written in C# and C++ and I therefore need the celt library in its most recent version (0.7) to be able to compile in Visual Studio 2008. In order to do this I, as I understand it, need a .vcproj file for the project. Are there any plans on making such a

Hi list I'm writing some unit tests for a piece of software using the opus library for audio encoding before transfering though RTP. In order to test my RTP implementation I thought I would transfer an encoded 440Hz sinus, and then do a diff of the received/decoded signal. However, my strategy seems to fail completely since the recreated sinus looks nothing like the one in the decoded

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

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We just released Opus 1.1-rc, which should be the last step before the final 1.1 release. Compared to 1.1-beta, this new release further improves surround encoding quality. It also includes better tuning of surround and stereo for lower bitrates. The complexity has been reduced on all CPUs, but especially ARM, which now has Neon assembly for 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

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

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

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 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'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

how can i obtain an exe of the newest libopus? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/opus/attachments/20160716/c742a84a/attachment.html>

Folks, I am having difficulty building libopus from source and am in need of assistance. The reported error shown below appears to indicate the build requires additional command line arguments. I've tried adding "-fPIC" and "-shared" to the makefile "LDFLAGS" and "CFLAGS" environment variables without success. An exhaustive web search has not

On 2014-06-04 1:25 PM, Alpha Thinktink wrote: > Ok, this seems contradictory to the output that the build log is > telling me. The log is showing a fatal error and the build doesn't > succeed. You're right. Doesn't work on the libopus-1.1 source tarball. Sorry about that! -r

#2027: multistream_encode(_float) fails on hard cbr encodes in libopus v1.1 -----------------------------------------+------------------------------ Reporter: thinktink | Owner: jmvalin@? Type: defect | Status: closed Priority: P3 | Milestone: Component: Opus |

#2027: multistream_encode(_float) fails on hard cbr encodes in libopus v1.1 -----------------------------------------+------------------------------ Reporter: thinktink | Owner: jmvalin@? Type: defect | Status: closed Priority: P3 | Milestone: Component: Opus |