-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
multi-frame transport #7
Labels
enhancement
New feature or request
Comments
The frame structure may be encoded only with first (or last) packet and needs:
|
The frame structure may be encoded in the current payload:
Now, there is no need to copy any data to subframes when decoding. |
bmegli
added a commit
that referenced
this issue
Apr 5, 2020
- library interface - mlsp_frame carries array of subframe sizes and data pointers - library implementation - for send the data is packetized on the fly (constructed from subframes without preparing continous payload data) - for receive the data is reconstructed by setting pointers to data sections in the receive buffer This means that all avoid unecessary copies: - library interface - sending - receiving Related to #7
bmegli
added a commit
that referenced
this issue
Apr 19, 2020
- consistently return relative offset by functions - add some comments in the code - multi-frame compatible readme - data buffer padding (e.g. FFmpeg compatibility without copying data) Related to #7
Merged
bmegli
added a commit
that referenced
this issue
Apr 19, 2020
- library interface - mlsp_frame carries array of subframe sizes and data pointers - library implementation - data buffer padding (e.g. FFmpeg compatibility without copying data) - for send the data is packetized on the fly (constructed from subframes without preparing continous payload data) - for receive the data is reconstructed by setting pointers to data sections in the receive buffer - documentation - updated readme and header All avoid unnecessary copies: - library interface (pointers to subframes) - sending (packetizing on the fly) - receiving (partitioning by pointers to data buffer) - data consumption (already padded buffer) Closes #7
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related to hardware-video-streaming#5
The idea is to make MLSP aware of transporting multiple logical subframes in a single frame.
The gains are:
The disadvantages are:
The text was updated successfully, but these errors were encountered: