You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To test the end-to-end latency of a WIHP stream published using FFmpeg, you can capture your desktop using FFmpeg, open a stopwatch or miaobiao in the browser, and compare the player with the original stopwatch.
Note: The parameter -i "2:0" is formatted as a video:audio device ID. Please use the ~/git/ffmpeg-webrtc/ffmpeg -f avfoundation -list_devices true -i "" command to list device ID and information.
Note: It is recommended to keep the threads=1 setting to prevent the occurrence of the Multiple Slices Issue. Please refer to Known Issues for more information.
The test results are incredible! The image below shows that the latency is around 150ms.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
To test the end-to-end latency of a WIHP stream published using FFmpeg, you can capture your desktop using FFmpeg, open a stopwatch or miaobiao in the browser, and compare the player with the original stopwatch.
The test results are incredible! The image below shows that the latency is around 150ms.
Beta Was this translation helpful? Give feedback.
All reactions