After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 749058 - Sending large video frames over RTSP loses some data
Sending large video frames over RTSP loses some data
Status: RESOLVED DUPLICATE of bug 673794
Product: GStreamer
Classification: Platform
Component: documentation
git master
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-05-07 09:01 UTC by Vivia Nikolaidou
Modified: 2015-05-21 09:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vivia Nikolaidou 2015-05-07 09:01:50 UTC 
I try playing back this pipeline using gst-play-1.0 :
./test-launch "videotestsrc pattern=snow ! video/x-raw,width=1920,height=1080 ! jpegenc quality=100 ! rtpjpegpay name=pay0"
and it doesn't play with UDP. TCP works (until it explodes), but it lags.

Trying some more pipelines that can send huge frames results to corrupted frames, e.g.
./test-launch "videotestsrc pattern=snow ! video/x-raw,width=1920,height=1080 ! avenc_mpeg2video bitrate=9900000 ! rtpmpvpay name=pay0"
./test-launch "videotestsrc pattern=snow ! video/x-raw,width=1920,height=1080 ! rtpvrawpay name=pay0"
Comment 1 Tim-Philipp Müller 2015-05-08 09:56:24 UTC 
What is the size of your udp send buffer? (check log)

You will have to make sure it's sufficiently large (ie. as large as possible).
Comment 2 Tim-Philipp Müller 2015-05-08 09:58:15 UTC 
Duplicate of bug #673794 IMHO, unless you have specific suggestions how to remedy this in gst-rtsp-server.
Comment 3 Sebastian Dröge (slomo) 2015-05-08 10:18:29 UTC 
This might've become worse with the sendmmsg() changes btw, but I also think it's a duplicate of that other bug.
Comment 4 Sebastian Dröge (slomo) 2015-05-21 09:30:54 UTC 

*** This bug has been marked as a duplicate of bug 673794 ***