Replies: 2 comments
-
This is fragment from h264 processor |
Beta Was this translation helpful? Give feedback.
0 replies
-
Yes, we are always fragmenting payloads in order for them to be compatible with any client, any L4 transport (UDP / TCP), any physical transport. This doesn't affect performance or required bandwidth. Regarding the Blocksize header, it would be a nice feature but it would significantly decrease performance since it requires a dedicated byte stream for each connected reader. Currently we are generating a single byte stream that we are then broadcasting to all connected readers. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Question
I look in code and find this fragment.
![image](https://private-user-images.githubusercontent.com/34924546/405342978-6441faac-939c-4d54-8ec3-6ac90e3ba6cc.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxODk4MDAsIm5iZiI6MTczOTE4OTUwMCwicGF0aCI6Ii8zNDkyNDU0Ni80MDUzNDI5NzgtNjQ0MWZhYWMtOTM5Yy00ZDU0LThlYzMtNmFjOTBlM2JhNmNjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEwVDEyMTE0MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc0YmM3YjIzMDQ4OWUwZGJmZGVhNzc1YTg5MWFhMGNhZGI5Y2M3NTc0Y2RhNTdmZjY3YmM4YmJmOThjODcwYmYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.umcwZZp7fzW5Nyp2UnrWzSkPlSzqNOYxNyfgfB-UvB8)
Do I understand correctly, that regardless of the parameter Blocksize, that I specify in the SETUP request, the payload in the rtp packets will be divided by "udpMaxPayloadSize" value?
Beta Was this translation helpful? Give feedback.
All reactions