[asterisk-bugs] [JIRA] (ASTERISK-21195) Transcoding makes bad choice in high-rate translations

Michael L. Young (JIRA) noreply at issues.asterisk.org
Thu Feb 28 20:29:18 CST 2013


    [ https://issues.asterisk.org/jira/browse/ASTERISK-21195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203570#comment-203570 ] 

Michael L. Young commented on ASTERISK-21195:
---------------------------------------------

Asterisk 10 is no longer supported for bug fixes (https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions).  For continued maintenance support please move to a branch which is a long term support (LTS) branch.

If you find that this problem has not been resolved in a supported branch (1.8 or 11), then we can take a look at this for you against that version of Asterisk.

Thanks
                
> Transcoding makes bad choice in high-rate translations
> ------------------------------------------------------
>
>                 Key: ASTERISK-21195
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21195
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Codecs/General
>    Affects Versions: 10.7.1
>            Reporter: Richard Kenner
>
> In main/translate.c, generate_table_costs considers any upsample equivalent if the slin in/out profile is the same.  But that's wrong.  The cost should be adjusted depending on how far apart the rate are.  For example siren14 to slin32 should be via slin16, not slin.  I modified that table to just add to the cost the difference in the rates and that fixes this problem, but I'm not sure enough of the scaling to know if that's the right amount to adjust it by.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list