AW: rtpjitterbuffer problem

Thornton, Keith keith.thornton at zeiss.com
Tue Jun 26 06:19:17 UTC 2018


Hi,
from your code example I can't see what you are doing differently from just setting splitmuxsink location directly to <path>/video%04d.avi and letting splitmuxsink increment the fragment number.
Regards

-----Ursprüngliche Nachricht-----
Von: gstreamer-devel [mailto:gstreamer-devel-bounces at lists.freedesktop.org] Im Auftrag von killerrats
Gesendet: Dienstag, 26. Juni 2018 01:25
An: gstreamer-devel at lists.freedesktop.org
Betreff: Re: rtpjitterbuffer problem

okay I think i figured out that the problem is when I go to return the next file in the signal "format-location". The difference between them is in bold. If i use the working_splitmux_cb method then could there be a memory leak on that one. if there is what is the better way of doing it.

gchar* videoPipeline::*notWorking_splitmux_cb*(GstElement* element, guint fragment_id, gpointer user_data) {
	std::string root = "", file = "", filePath = "";
	unsigned __int64 sizeOfFile = 0;
	std::string temp = "video%04d.avi";
	char* newFile = new char[strlen(temp.c_str())];

	strcpy(newFile, temp.c_str());
	newFile = g_strdup_printf(newFile, fragment_id);

	*temp = std::string(newFile);*
	*delete[] newFile;*
	return g_strdup_printf("%s", newFile);
}

gchar* videoPipeline::*working_splitmux_cb*(GstElement* element, guint fragment_id, gpointer user_data) {
	unsigned __int64 sizeOfFile = 0;
	std::string temp = "video%04d.avi";
	char* newFile = new char[strlen(temp.c_str())];

	strcpy(newFile, temp.c_str());
	newFile = g_strdup_printf(newFile, fragment_id);
	
	return g_strdup_printf("%s", newFile);
}




-----
------------------------------
Gstreamer 1.14.1
------------------------------
Windows
--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
gstreamer-devel at lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel


More information about the gstreamer-devel mailing list