[asterisk-bugs] [JIRA] (ASTERISK-26615) Create a version of codec_opus that is not statically linked with libopus
Sean Bright (JIRA)
noreply at issues.asterisk.org
Wed Dec 13 10:06:07 CST 2017
[ https://issues.asterisk.org/jira/browse/ASTERISK-26615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Bright updated ASTERISK-26615:
-----------------------------------
Comment: was deleted
(was: Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.
A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.
Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].)
> Create a version of codec_opus that is not statically linked with libopus
> -------------------------------------------------------------------------
>
> Key: ASTERISK-26615
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-26615
> Project: Asterisk
> Issue Type: Improvement
> Security Level: None
> Components: Codecs/codec_opus
> Reporter: Sean Bright
> Severity: Minor
>
> libopus has support for SIMD instructions that are not being enabled when codec_opus is built. It would be nice to have a version of codec_opus that dynamically linked against an external libopus library so that hardware specific optimizations can be used.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list