Using libmpv to play multiple RTSP streams leads to RTP lost
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
Important Information
Provide following Information:
- mpv version: 0.33
- Windows Version: Windows 7 & Windows 10(20H2 19042.985)
- Source of the mpv binary: ea89e81
- If known which version of mpv introduced the problem
- Possible screenshot or video of visual glitches

Reproduction steps
A libmpv based Qt program, if required, I can write a sample.
the properties set are:
hwdec = no;rtsp-transport = udp, same iftcp;profile = low-latency&untimed = 1, same if without;osc = 0input-default-bindings = noinput-vo-keyboard = no
Expected behavior
Actual behavior
[ffmpeg/demuxer] warn: rtsp: max delay reached. need to consume packet
[ffmpeg/demuxer] warn: rtsp: RTP: missed 2 packets
The CPU/GPU is enough to play with 9 mpv instances without problem.
And there is no report about rtp lost by the wireshark.
Log file
log files of each mpv_handle, the first log contains more contents.
output-0.log
output-1.log
output-2.log
output-3.log
output-4.log
output-5.log
output-6.log
output-7.log
output-8.log
The issue will be closed for ignoring the issue template.
Sample files
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing output-0.log through output-8.log and the reported libmpv settings, then reproduce the nine-stream Qt/libmpv setup with both UDP and TCP RTSP transport. Compare the RTSP/RTP warnings with Wireshark, and treat the investigation as complete only when the cause of the reported missed packets is identified and a verified result is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100