Skip to main content
Topic: Opus 1.2 alpha (Read 17148 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Opus 1.2 alpha

Hiyas,

New version is available for testing - alot of improvements:

Quote
This Opus 1.2-alpha alpha release of the upcoming Opus 1.2 brings many quality improvements, new features, and bug fixes, including:

  • Speech quality improvements especially in the 12-20 kbit/s range
  • Improved VBR encoding for hybrid mode
  • More aggressive use of wider speech bandwidth, including fullband speech starting at 14 kbit/s
  • Music quality improvements in the 32-48 kb/s range
  • Generic and SSE CELT optimizations
  • Support for directly encoding packets up to 120 ms
  • DTX support for CELT mode
  • SILK CBR
  • Support for all of the fixes in draft-ietf-codec-opus-update-04 (the mono downmix and the folding fixes need –enable-update-draft)
  • Many bug fixes, including integer overflows discovered through fuzzing (no security implications)

For testing:   :D




Re: Opus 1.2 alpha

Reply #3
Sure, props to Lord Mulder. That build is based on GIT sources, the other is built on sources from opus-codec.org announced yesterday, don't know if there's difference.


Re: Opus 1.2 alpha

Reply #5
Is opus-1.2-alpha.rar an AVX2 compile? Doesn't work for me.

Re: Opus 1.2 alpha

Reply #6
Yes using AVX2 (selectively)
Should work on any configuration
QaxSSE2,SSE3,SSSE3,SSE4.2,AVX,CORE-AVX2,CORE-AVX-I,MIC-AVX512,CORE-AVX512

A new Lord Mulder's tools for updated git master.


Re: Opus 1.2 alpha

Reply #8
I've just made an attempt to build libraries for phone.
What I've got are files lib/libopus.so.0.5.3 and lib64/libopus.so.0.5.3.
How can I test if they work and can I replace libopus.so in /system/lib and /system/lib64 ?
The OS seems not to use them anyway.

Re: Opus 1.2 alpha

Reply #9
Yes using AVX2 (selectively)
Should work on any configuration
QaxSSE2,SSE3,SSSE3,SSE4.2,AVX,CORE-AVX2,CORE-AVX-I,MIC-AVX512,CORE-AVX512

A new Lord Mulder's tools for updated git master.

Thanks, the AVX build from that one works for me. I'm using an AMD 8320 btw so it has AVX but not AVX2.

EDIT: I want to one day do my own compiles (just for testing) but couldn't seem to work out how to get it working in VS2015 :/




Re: Opus 1.2 alpha

Reply #13
I've been using 1.2 alpha on CentOS 7 for about a week now and so far have not had any problems with it. I can't verify the improvements, I'm not set up for A/B tests, but I have not noticed any breakage as a result of updating to this version.

Re: Opus 1.2 alpha

Reply #14
Opus-tools 0.1.9-36-gbd7489f (using libopus 1.2-alpha-18-gefcdeb9)
Code: [Select]
http://www38.zippyshare.com/v/WDkvD8fI/file.html

Re: Opus 1.2 alpha

Reply #15
Opus-tools 0.1.9-37-g3862c10 (using libopus 1.2-alpha-18-gefcdeb9)
Code: [Select]
http://www5.zippyshare.com/v/2swk6lW1/file.html



Re: Opus 1.2 alpha

Reply #18
Was a constant quality mode ever considered for opus tools?
It'd be nice if I could just set a parameter and get audio with a predictable quality.
Though wiki claims 192kbps for transparency, I expect that 96kbps*channel-numbers doesn't make much.
Which brings up the question: What to set for 5.1/7.1, etc?



Re: Opus 1.2 alpha

Reply #21
  • Support for directly encoding packets up to 120 ms
I tried, but if I choose more than 60 ms, just closing the program.

Re: Opus 1.2 alpha

Reply #22
  • Support for directly encoding packets up to 120 ms
I tried, but if I choose more than 60 ms, just closing the program.
What program? Also, note that support for 120-ms packets was added only to the Opus library, not necessarily to all the software using Opus. Last thing... are you sure you actually want to use 120-ms frames? If you're encoding files, then you'll get better results with the default (20 ms). The only reason to use 120-ms packets is when you're doing VoIP over RTP and your bitrate is so low that you need to save on the RTP headers.

Re: Opus 1.2 alpha

Reply #23
These programs. Opusenc in
Opus-tools-0.1.9-37-g3862c10_(using libopus 1.2-alpha-21-gc9ba552)_x86_x64_gcc630;
Opus-tools-0.1.9-56-g5aecfed_(using libopus 1.2-alpha2)_x86_x64_gcc630;
Opus-tools-0.1.10_(using libopus 1.2-alpha2-2-g32b302c)_x86_x64_gcc630

I try the 120ms because the
  • Music quality improvements in the 32-48 kb/s range
not enough fine for me, but I trying minimal filesize.

Re: Opus 1.2 alpha

Reply #24
I try the 120ms because the
  • Music quality improvements in the 32-48 kb/s range
not enough fine for me, but I trying minimal filesize.
If you want smaller files for the same quality, use the default. 120ms will give you *bigger* files. If 120 ms (or 60 ms before that) was the best option, we would have made it the default. We don't hide good options behind flags, we try to have the best quality by default. Almost any option you can use with opusenc (except for --bitrate of course) means "I'm willing to get slightly worse quality/bigger files to get this particular feature".

 
SimplePortal 1.0.0 RC1 © 2008-2018