RTSP server using v4l2src

yusuf.husainy yusuf.husainy at gmail.com
Mon Apr 15 02:52:36 PDT 2013


Thanks Aleix for the help,

This worked for me:

server pipeline:
1. vfl2src device=/dev/video1 ! ffenc_mpeg4 ! rtpmmp4vpay name=pay0 pt=96
2. vfl2src device=/dev/video1 ! x264enc profile=baseline aud=true
byte-stream=false speed-preset=ultrafast intra-refresh=true
sliced-threads=true *tune=zerolatency*(this is the property that made the
4sec delay go away) key-int-max=30 bitrate=3000 ! rtph264pay name=pay0 pt=96

client pipeline:
1. gst-launch -v --eos-on-shutdown(this is important bcoz it make the
filesink to make the file correctly, i.e. EOF is entered on EOS after SIGINT
is received...if not specified, this may lead to an error during playback
saying: no EOS detected) rtspsrc location=rtsp://192.168.1.45:8554/test !
rtpmp4vdepay ! mpeg4videoparse ! matroskamuxx ! filesink=testing7.mkv (this
file opened with VLC as well as totem) ==> with server-1 pipeline

2. gst-launch -v --eos-on-shutdown(this is important bcoz it make the
filesink to make the file correctly, i.e. EOF is entered on EOS after SIGINT
is received...if not specified, this may lead to an error during playback
saying: no EOS detected) rtspsrc location=rtsp://192.168.1.45:8554/test !
rtpmp4vdepay ! mpeg4videoparse ! qtmux ! filesink=testing8.mp4 (this file
opened with VLC as well as totem) ==> with server-1 pipeline.......(fails to
link if I use mp4mux in place qtmux)

3. gst-launch -v --eos-on-shutdown(this is important bcoz it make the
filesink to make the file correctly, i.e. EOF is entered on EOS after SIGINT
is received...if not specified, this may lead to an error during playback
saying: no EOS detected) rtspsrc location=rtsp://192.168.1.45:8554/test !
rtph264depay *byte-stream=false access-unit=true*(important if we want to
use qtmux and mp4mux..provided on server, x264enc has been set with similar
props.) ! h264parse ! qtmux/mp4mux/matroskamux !
filesink=testing9.mp4/testing10.mp4/testing11.mkv (this file opened with VLC
as well as totem) ==> with server-2 pipeline


I still have a doubt, about the dependancy of the bit-rate property of
x264enc with the compatibility of the above rx pipelines (wrt server-2
pipeline). I mean what is the meaning of target-bitrate, what dictates this
value, how will it affect other quality measurements of the h264 encoded
stream. 

I would appreciate if any one has some information on this. Maybe a link or
example that shows this. 

Thanks everyone for the replies.


Regards, 
Yusuf Husainy.



--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/RTSP-server-using-v4l2src-tp4659459p4659498.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.


More information about the gstreamer-devel mailing list