|
|
Dear All,
I'm using gstreamer1.0 (1.19) and I'm studying the splitmuxsink because it seems the best tool to save a H264 streaming. I ran the following pipeline:
GST_DEBUG="GST_TRACER:7" GST_TRACERS="leaks" gst-launch-1.0 -e rtspsrc location=rtsp://user:pwd@192.168.1.17/media/video2 ! rtph264depay ! h264parse ! splitmuxsink max-files=3 location=%ds.mp4 max-size-time=10000000000 max-size-bytes=1000000
and I got:
------------
...
Setting pipeline to NULL ...
Freeing pipeline ...
0:00:22.897508084 7947 0x1a76e10 TRACE GST_TRACER :0:: object-alive, type-name=(string)GstBuffer, address=(gpointer)0x7f1fd8079ad0, description=(string)buffer: 0x7f1fd8079ad0, pts 0:00:07.993455218, dts 99:99:99.999999999, dur 99:99:99.999999999, size 28652, offset 192457, offset_end none, flags 0x0, ref-count=(uint)1, trace=(string);
0:00:22.897657010 7947 0x1a76e10 TRACE GST_TRACER :0:: object-alive, type-name=(string)GstMemory, address=(gpointer)0x7f1fc405a0a0, description=(string)0x7f1fc405a0a0, ref-count=(uint)1, trace=(string);
0:00:22.897677789 7947 0x1a76e10 TRACE GST_TRACER :0:: object-alive, type-name=(string)GstPad, address=(gpointer)0x1aa9010, description=(string)<queue0:src>, ref-count=(uint)2, trace=(string);
0:00:22.897689903 7947 0x1a76e10 TRACE GST_TRACER :0:: object-alive, type-name=(string)GstPad, address=(gpointer)0x1aa8dd0, description=(string)<queue0:sink>, ref-count=(uint)2, trace=(string);
0:00:22.897701441 7947 0x1a76e10 TRACE GST_TRACER :0:: object-alive, type-name=(string)GstQueue, address=(gpointer)0x1ad4040, description=(string)<queue0>, ref-count=(uint)1, trace=(string);
** (gst-launch-1.0:7947): WARNING **: Leaks detected
------------------------
Where I wrong?
I've searched using google, but I don't understand the reason for this leak.
B-plan: is there another plugin capable to save a H264 splitted on a defined number of files ?
Thanks for any advice.
Cristiano
|
Locked
