From: Wes M. <wm...@sd...> - 2010-04-29 12:01:32
|
I have a nicely working gstparsed pipeline that is mostly this: gstoarse( "souphttpsrc timestamp=true ! multipartdemux ! image/jpeg,width=640,height=480 ! matroskamux ! filesink" ) Works great. Does just what I want. Now, I thought I'd like to record information about my data so I redid y pipeline to be: gstoarse( "souphttpsrc timestamp=trye ! multipartdemux ! image/jpeg,width=640,height=480 ! matroskamux ! tee name=fred. ! queue ! filesink fred. ! queue ! appsink" ). With some stuf to catch the frames and eos-es In both cases these are in C/C++ code and I inject an eos to halt the pipeline. The second pipe does not seem to "hear" the eos. It just keeps going. It also seems to loose the timestamp nfo that souphttpsrc put into the data.. Thanks for any help. Wes -- View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Behabior-of-gstparse-tp2075346p2075346.html Sent from the GStreamer-devel mailing list archive at Nabble.com. |
From: Benjamin O. <ot...@re...> - 2010-04-29 20:06:21
|
On Thu, 2010-04-29 at 05:01 -0700, Wes Miller wrote: > image/jpeg,width=640,height=480 ! matroskamux ! tee name=fred. ! queue ! ^ Remove that dot. Dots are used by the parser to differentiate between elements (before the dot) and pads (after the dot). So putting dots in names will likely confuse gst-launch and make it not work. Benjamin |
From: Wes M. <wm...@sd...> - 2010-04-30 14:17:39
|
Nope, doesn't look like that's the answer. Here is the exact pipeline I tried. /*--- build the pipeline ---*/ this->pipeline = gst_parse_launch( " souphttpsrc name=my_src " "! multipartdemux name=my_demux " "! image/jpeg,width=640,height=480 " "! matroskamux name=my_mux " "! tee name=my_tee" "! queue name=my_queue1" "! appsink name=my_appsink my_tee." "! queue name=my_queue2" "! filesink name=my_sink", &error ); I attach to the bus to check for EOS and call a callback that should shutdown the pipeline. Also, i poll the output of appsink looking for EOS. Neither detector finds and EOS. And the filesink writes no data. Neither do the writes to file I do inside the while not eos loop. Feels like everything is backing up at the tee or the queues. Thanks for any help. Wes -- View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Behabior-of-gstparse-tp2075346p2076974.html Sent from the GStreamer-devel mailing list archive at Nabble.com. |