GstBuffer error?

[killerrats]

<http://gstreamer-devel.966125.n4.nabble.com/file/t377034/gstbuffer_return_0_without_timestamp.jpg>

I get this error long term. anybody know why this shows up? It will
disappear after awhile which is like hours later but then will come back. I
have two sources that are using the same source for video and audio side.

pipeline:
rtspsrc location=[IP] - rtph264depay - h264parse - multiqueue.video
rtspsrc location=[ip] - rtpmp4gdepay - aacparse - multiqueue.audio_1

multiqueue - multiqueue.src_1 - splitmuxsink.video splitmuxsink
multiqueue.src_2 - splitmuxsink.audio_1



-----
------------------------------
Gstreamer 1.14.2
------------------------------
Windows
--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[rachelgomez161999]

It's difficult to determine the exact cause of the error without more information, but the error message "buffer pool full" suggests that one of the elements in your pipeline is not processing data fast enough, causing the buffer pool to fill up and eventually leading to a crash.

One possible cause could be that the multiqueue element is not configured properly, leading to a bottleneck in the pipeline. You could try adjusting the buffer sizes or the number of threads used by the multiqueue element to see if it improves the performance.

Another possible cause could be related to the network connection or the sources themselves. For example, if the network connection is not stable or there is a lot of latency, it could cause the pipeline to slow down and eventually fail. Similarly, if the sources are producing data at different rates or with different codecs, it could cause the pipeline to become unbalanced and result in buffer pool errors.

You could try running the pipeline with only one of the sources at a time to see if one of them is causing the issue. You could also try adding debug messages to the pipeline to see where the data flow is slowing down or getting stuck.

Overall, this issue requires a detailed analysis of the pipeline and the sources to determine the exact cause and find a solution.

Regards,
Rachel Gomez