Skip to content

fix #807 #821: add --packet-encoding and --packet-mtu to roc-send#837

Open
Ayoub-glitsh wants to merge 1 commit intoroc-streaming:masterfrom
Ayoub-glitsh:fix/807-821-packet-encoding-mtu
Open

fix #807 #821: add --packet-encoding and --packet-mtu to roc-send#837
Ayoub-glitsh wants to merge 1 commit intoroc-streaming:masterfrom
Ayoub-glitsh:fix/807-821-packet-encoding-mtu

Conversation

@Ayoub-glitsh
Copy link
Copy Markdown

  • Add --packet-encoding option to roc-send (e.g. 96:s16/48000/stereo) Registers a custom RTP payload type in the encoding map and sets it as the sender payload type. When the encoding rate matches the input rate, no resampler is created, fixing issue Can't disable resampling with rec-send command line #807.

  • Add --packet-mtu option to roc-send When --packet-len is not set, packet_length is auto-derived from the MTU using the encoding's sample spec. When both are set, the smaller value is used with a warning. Fixes issue Multitrack packets too big per default ("packetizer: can't prepare packet") #821.

  • Add packet_mtu field to SenderSinkConfig

  • Derive effective_packet_length in sender_session before packetizer init

…packet-mtu to roc-send

- Add --packet-encoding option to roc-send (e.g. 96:s16/48000/stereo)
  Registers a custom RTP payload type in the encoding map and sets it
  as the sender payload type. When the encoding rate matches the input
  rate, no resampler is created, fixing issue roc-streaming#807.

- Add --packet-mtu option to roc-send
  When --packet-len is not set, packet_length is auto-derived from the
  MTU using the encoding's sample spec. When both are set, the smaller
  value is used with a warning. Fixes issue roc-streaming#821.

- Add packet_mtu field to SenderSinkConfig
- Derive effective_packet_length in sender_session before packetizer init
@rocstreaming-bot rocstreaming-bot added the contrib PR not by a maintainer label Apr 25, 2026
@rocstreaming-bot
Copy link
Copy Markdown

🤖 Pull request is not targeted to develop branch, which is usually wrong.
If this was not intentional, please rebase on fresh develop branch, force-push, and re-target pull request using github web interface. Remember to use rebase with force-push instead of regular merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contrib PR not by a maintainer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants