Skip to main content

Topic: Opus and CPU (Read 2481 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • lithopsian
  • [*][*][*][*]
Opus and CPU
I've written a plugin to play Opus and noticed that it uses more CPU than other formats I looked at, about 3x Flac and about 50% more than Ogg Vorbis and AAC.  Does that seem about right, or did I make some big booboo in there?

  • saratoga
  • [*][*][*][*][*]
Opus and CPU
Reply #1
What CPU?

  • Garf
  • [*][*][*][*][*]
  • Developer (Donating)
Opus and CPU
Reply #2
50% more on decode sounds reasonable. I mean it is doing more stuff after all.

  • lithopsian
  • [*][*][*][*]
Opus and CPU
Reply #3

  • lithopsian
  • [*][*][*][*]
Opus and CPU
Reply #4
50% more on decode sounds reasonable. I mean it is doing more stuff after all.

Thanks.  Just wanted to be sure that this was expected for the codec.

  • saratoga
  • [*][*][*][*][*]
Opus and CPU
Reply #5
What CPU?

Doesn't seem to matter.


ARM vs. x86 will matter enormously given the different level of optimization for each platform.  I'm guessing though that you mean x86?

Opus complexity is actually not that great, but most optimization has been for ARM CPUs, as very few people care about a few MHz on multicore PC running in the GHz.

  • lithopsian
  • [*][*][*][*]
Opus and CPU
Reply #6
About half the extra CPU turns out to be down to resampling.  My system is set up for 44.1 kHz by default, since that is mostly what I listen to, but Opus is strictly 48kHz.