Frames parsing acts weird being used to write down a stream

[Alex Bolotin]

 Hi. If I got it right than this mailing list just what I need to have some
suggestions on my problem.

I'm using GST 1.6.3 C++ interfaces. I have a problem with writing incoming
stream to a hard drive. I'm using such pipeline - [uridecodebin queue2
h264parse queue2 aacparse mpegtsmux queue2 multifilesink], where
uridecodebin just breaks stream down to h264/video and aac/audio (did so
with signals). So you can see I'm writing many chunks using multifilesink.

If I use hls incoming source then the 1st chunk opens file but the rest
won't play using a playback pipeline, which restreams written chunks. In
the same time if I use this pipeline [uridecodebin videoconvert x264enc
audioconvert faac mpegtsmux queue2 multifilesink], the restreaming pipeline
works fine. In addition I can say that if I open bad chunks with VLC it
seems playing without video/audio output. Usually playback starts only
after a 30 secs of video. I tried to write 1 minute chunks.

I would like to parse frames and store them as it is, cause it consumes way
less cpu and mem, then encoding.

I believe I don't understand how parsing works at least how data flows
within it. Could you help me with it?

Best wish,
AlexB.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20160222/44a9ee0a/attachment.html>