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 767852 - hlssink: first item in the playlist.m3u8 is always a deleted file
hlssink: first item in the playlist.m3u8 is always a deleted file
Status: RESOLVED DUPLICATE of bug 752863
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.8.2
Other Windows
: Normal major
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-06-20 03:12 UTC by Abu Abdulla
Modified: 2016-06-20 07:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Abu Abdulla 2016-06-20 03:12:49 UTC 
Hi,

I'm streaming from my Raspberry camera using:
raspivid -n -vf -fl -t 0 -w 640 -h 480 -b 1200000 -fps 20 -pf baseline -o - | gst-launch-1.0 -v fdsrc ! h264parse ! rtph264pay pt=96 config-interval=10 ! multiudpsink clients=192.168.2.3:5000,192.168.2.3:5001


client side (windows PC):
gst-launch-1.0 -e udpsrc port=5000 ! application/x-rtp,payload=96 ! rtph264depay ! h264parse ! mux. audiotestsrc wave=silence ! voaacenc ! aacparse ! mux. mpegtsmux name=mux ! hlssink max-files=5 target-duration=8 location=C:/xampp/htdocs/live/segment%%05d.ts playlist-location=C:/xampp/htdocs/live/playlist.m3u8

the problem is with the playlist.m3u8 having always the first item to be the last deleted file. some players fails to play this stream.

it is only working if the player starts at the beginning of creating playlist.m3u8 i.e. the segments didn't reach max-files; it is working simply because the first file is still not deleted.
Comment 1 Tim-Philipp Müller 2016-06-20 07:51:11 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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