Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Opus v1.5.2 (Read 41762 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Opus v1.5.2

Reply #2 –
Is there any reason to stick to multiples of 16/32 for target bitrate in opus encoder or does it not matter? I noticed qaac/Apple AAC forces 112-128-160-192 etc.

Re: Opus v1.5.2

Reply #3 –
Quote from: jdimsa on
Is there any reason to stick to multiples of 16/32 for target bitrate in opus encoder or does it not matter? I noticed qaac/Apple AAC forces 112-128-160-192 etc.

Unless it's a special use-case which also requires hard CBR, it does not matter.

Re: Opus v1.5.2

Reply #5 –
Quote from: jdimsa on
Is there any reason to stick to multiples of 16/32 for target bitrate in opus encoder or does it not matter? I noticed qaac/Apple AAC forces 112-128-160-192 etc.

Opus does have some built-in bitrate thresholds that affect how it encodes - some, but not all of of these are at 16kbps multiples, probably for historical reasons.
https://wiki.xiph.org/Opus_Recommended_Settings#Bandwidth_Transition_Thresholds
https://github.com/xiph/opus/blob/main/src/opus_encoder.c

Re: Opus v1.5.2

Reply #6 –
Quote from: NetRanger on
Opus-tools v0.2-34-g98f3ddc (using libopus 1.5.2-2-gdfd4175)
Built on April 22, 2024, GCC 13.2.0

Why is there such a huge difference in size between the encoder (676 352 bytes) and the decoder (5 625 344)?
• Join our efforts to make Helix MP3 encoder great again
• Opus complexity & qAAC dependence on Apple is an aberration from Vorbis & Musepack breakthroughs
• Let's pray that D. Bryant improve WavPack hybrid, C. Helmrich update FSLAC, M. van Beurden teach FLAC to handle non-audio data

Re: Opus v1.5.2

Reply #7 –
Quote from: Kraeved on
Why is there such a huge difference in size between the encoder (676 352 bytes) and the decoder (5 625 344)?

It's at least partly due to the LACE/noLACE postprocessing for low bitrate voice.

"Building with --enable-osce increases the binary size by about 1.6 MB, roughly 0.5 MB for LACE and 1.1 MB for NoLACE. " https://opus-codec.org/demo/opus-1.5/

Re: Opus v1.5.2

Reply #8 –
Quote from: Marsu42 on
It's at least partly due to the LACE/noLACE postprocessing for low bitrate voice.

Low bitrate voice? It reminds me of this topic where we were looking for a way to compress 11025 Hz 16 bit mono file (history.wav) with speech and some music in the background. We started with 24 kbps, went down to 16 kbps, and ended with 12 kbps MP3 and AAC SBR, which sound not just intelligible, but satisfying. What can Opus offer here?
• Join our efforts to make Helix MP3 encoder great again
• Opus complexity & qAAC dependence on Apple is an aberration from Vorbis & Musepack breakthroughs
• Let's pray that D. Bryant improve WavPack hybrid, C. Helmrich update FSLAC, M. van Beurden teach FLAC to handle non-audio data

Re: Opus v1.5.2

Reply #10 –
@NetRanger, where can I see the history of changes? Tried three places:
* https://github.com/xiph/opus-tools/ last commit 5 months ago
* https://github.com/xiph/libopusenc/ last commit 2 years ago
* https://github.com/xiph/opus/ last verified commit on Apr 10, 2024, but no g98f3ddc around
• Join our efforts to make Helix MP3 encoder great again
• Opus complexity & qAAC dependence on Apple is an aberration from Vorbis & Musepack breakthroughs
• Let's pray that D. Bryant improve WavPack hybrid, C. Helmrich update FSLAC, M. van Beurden teach FLAC to handle non-audio data

Re: Opus v1.5.2

Reply #12 –
@NetRanger, err, so the difference between the 2 builds of yours (April 22 and April 26) are 2 unverified commits?

• Join our efforts to make Helix MP3 encoder great again
• Opus complexity & qAAC dependence on Apple is an aberration from Vorbis & Musepack breakthroughs
• Let's pray that D. Bryant improve WavPack hybrid, C. Helmrich update FSLAC, M. van Beurden teach FLAC to handle non-audio data

Re: Opus v1.5.2

Reply #13 –
I use media-autobuild_suite for my compile 'needs' and dont really check the changes of what it puts out. It's as simple as that.

Re: Opus v1.5.2

Reply #17 –
Hello,
the Opus website talks about the major improvements in Opus 1.5. However, when I download the Opus Tools from Gitlab and find the Opusenc.1 or Opusdec.1 files, the last modification date appears to be November 2023 and the file contents themselves even say "2019-09-07".
Does it mean that these new features are not available in Opusenc or Opusdec or does it mean their usage there is just not documented?
Thanks.

Re: Opus v1.5.2

Reply #18 –
Quote from: harmonion on
Hello,
the Opus website talks about the major improvements in Opus 1.5. However, when I download the Opus Tools from Gitlab and find the Opusenc.1 or Opusdec.1 files, the last modification date appears to be November 2023 and the file contents themselves even say "2019-09-07".
Does it mean that these new features are not available in Opusenc or Opusdec or does it mean their usage there is just not documented?
Thanks.

The opus-tools is depending on libopus, so most of the new features are available when you compile opus-tools with new libopus, however, since some new parameters were not reflected, you can't directly config DRED and LACE/NoLACE in opusdec

Re: Opus v1.5.2

Reply #21 –
Quote from: NetRanger on
Opus-tools v0.2-34-g98f3ddc (using libopus 1.5.2-21-gff6dea5)
Built on September 12, 2024, GCC 14.2.0

https://github.com/xiph/opus
https://github.com/xiph/opusfile
https://github.com/xiph/libopusenc
https://github.com/xiph/opus-tools
Man am I r tarded or what? I go to the github links and everything latest there is from a year or two ago.
And I simply can't find these builds.
Can you post not only the latest opus-tools but the libopus as well?

Re: Opus v1.5.2

Reply #22 –
Nothing wrong with you. The official releases are announced on https://opus-codec.org/ and all the releases apart from libopus are ancient. Some Xiph person probably know why for example commits to opus-tools aren't worth official release. My guess is that no one cares about such stuff anymore.

Re: Opus v1.5.2

Reply #23 –
@Case sure. Do you know what or from where @NetRanger is getting those builds from?

Re: Opus v1.5.2

Reply #24 –
Quote from: Sietrutium on
@Case sure. Do you know what or from where @NetRanger is getting those builds from?
From here: https://github.com/m-ab-s/media-autobuild_suite

Download and run the scripts. It contains all you need and updates the compiler and the libraries from time to time. You need no great knowledge, just a reasonably modern, fast system and the time to allow it run to completion. Will build a lot more than you are probably looking for, but it's a great tool.