-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
FFmpeg-WHIP: Initially, the latency was about 150ms, but it later increased to approximately 480ms #3222
Comments
An increased delay suggests that something may be wrong with respect to the RTCP exchange. How advanced is RTCP support in your WHIP integration? |
v0.10.10 is from two years ago, please try to experiment with a recent Janus version or you might encounter other issues that could have already been solved! My advice for debugging the issue is to do a pcap through the admin API of both pub and sub legs, then study the RTP timestamps and check the origin of the skew. |
I hadn't noticed the test was made against v0.10.10... then obviously yes, test the latest 0.x or master. |
Closing as apparently not an issue. |
I conducted a test on version 1.1.4 and found that the latency remains the same, at approximately 520ms.
To replicate the problem, you can follow the instructions provided at ossrs/ffmpeg-webrtc#1 (comment) |
I already saw the instructions: how do you think I tested it the last time? 😉 |
What version of Janus is this happening on?
0.10.10. The bug is present in version 0.10.10, but it may also exist in other versions, including the latest one.
Have you tested a more recent version of Janus too?
No. Since we haven't tested it with the latest version, it doesn't appear to be related to the version.
Was this working before?
No.
Is there a gdb or libasan trace of the issue?
No.
Additional context
We are currently exploring ways to enable ffmpeg to support WHIP. We conducted tests using Janus and the results were positive, with very low subsecond latency.
At first, the latency was around 150ms, but it later rose to approximately 480ms, as depicted in the images below.
As we do not possess extensive knowledge of Janus, we are unable to debug the code ourselves. Therefore, we would greatly appreciate your assistance in identifying potential solutions to address this issue.
Replay steps
We have provided a step-by-step reproduction of this issue, which should allow you to reliably reproduce it. This issue is not occurring randomly.
The text was updated successfully, but these errors were encountered: