Implement generation of and handling of Jitter Reduction Timestamps
Open
Nobody has claimed this yet.
area-sdk :wrench:
area-service-or-api :desktop_computer:
feature request :bulb:
needs-investigation :mag:
wontfix
- Dominant language
- C++
- Stars
- 679
- Forks
- 72
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 59
Description
Note that the various OS and DAW companies agreed to just pass these through in our initial implementations while we all sort out how these are likely to be used. However, in the future, we may want to intercept these in the service and do something meaningful with the information. This will also help reduce the amount of traffic these can generate.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. First clarify how Jitter Reduction Timestamps should be generated and handled, including whether they remain pass-through or are intercepted by the service; done should be defined by an agreed implementation and validation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100