Skip to content

RTP Codecs implementations are spaghettifying(?) #1554

@ha-ves

Description

@ha-ves

I haven't had time to think of proper solution, but the problem is as more PR of adding codecs (and/or its transport mechanism) I feel like the codebase is turning into bigger and bigger spaghetti.

e.g., RTP framing are a growing if/else statements for all supported codecs.

Maybe should also pull the de/packetizer to framing instead of branching-off on receive/send.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions