Excellent addition indeed. I've seen so many people requesting this
feature that it became a must.
As per the "File naming convention and output options", the simpler the
better. You can always rename and move things around through scripting
in a later stage, but that's just me.
On Tuesday,
I suppose that embedding my stream in an avi/wmv container should fix
this ?
It does ! And it is actually an easy job with the tool named avc2avi :)
Thank you so much for your help Ross, much appreciated !
Julien
___
live-devel mailing list
live-deve
If your input stream is H.264 video only (i.e., with no audio), then
another solution would be to write your own "MediaSink" subclass
(perhaps similar to the existing "H264VideoFileSink" class) that
writes a sequence of raw (i.e., elementary stream) H.264 video files.
You should be able to easily
I didn't suggest "closing and reopening the RTSP stream". My
suggestion was to keep the RTSP stream open, but close just the
"QuickTimeFileSink" object, then create a new one and call
"startPlaying()" on it - from the existing source. This doesn't
involve any RTSP commands at all.
My bad, I wa
But closing and re-opening the RTSP stream will create a gap between
the files.
Anyhow, I just tested your suggestion and unfortunately it doesn't
solve my
problem of having the start of file not being aligned on a KeyFrame.
In other words the video remains still until it finds a full frame to
I need to split an RTSP feed into multiple files of 30 seconds. I have
done
what has been suggested in the thread by sub-classing "QuickTimeFileSink"
and in the "QuickTimeFileSink::afterGettingFrame" ( after sync point )
re-open a new file without stopping the RTSP session.
I indeed get the da
Hi,
I'm trying to do exactly what Matteo Lisi has tried to do a few years back
( 20th Dec 2010 - Under the same post title, but different thread ).
I need to split an RTSP feed into multiple files of 30 seconds. I have done
what has been suggested in the thread by sub-classing "QuickTimeFileSink
