Skip to content
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

Handle unbounded processing time for generating content #10

Open
laurent-radoux opened this issue Dec 22, 2023 · 0 comments · May be fixed by #11
Open

Handle unbounded processing time for generating content #10

laurent-radoux opened this issue Dec 22, 2023 · 0 comments · May be fixed by #11
Assignees
Labels
bug Something isn't working

Comments

@laurent-radoux
Copy link
Collaborator

Currently, there is very hard constraint on the processing time which cannot exceed the time between two frames.

This is due to the nature of the synchronisation between the RX and TX threads where the processing is never parallelized.
It implies that should the processing be longer, frames will be constantly dropped.

The synchronisation needs to be adapted in order to make it possible for multiple RX frames to be processed at the same time while still ensuring that the latency between the live content and the generated overlay is minimal.

@laurent-radoux laurent-radoux added the bug Something isn't working label Dec 22, 2023
@laurent-radoux laurent-radoux self-assigned this Dec 22, 2023
@laurent-radoux laurent-radoux linked a pull request Dec 22, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant