ffmpeg can´t handle udp rstp streams

[Torsten73]

ok, that means, you use this patch with 1.26 and you are now able to use ffmpeg with mkv for mpeg live and replay format?

I know the old thread, but it hasn´t included in 1.26? I i didn´t thought that this is a solution for ffmpeg h264 generally.

Who had donne this decission, or better say who should be contacted that it will be inclouded into git?

[Basildane]

pok: thanks for posting the patch.

Thing is, I compiled zoneminder from the puppet and Linux is not my primary environment.
I'm assuming I'll use git to patch the source with your patch, and then run "puppet apply" or something to recompile, but I'm not sure where to start.

[Torsten73]

puppet installs from source. so inside of the puppet installer the patch must be included. i have asked fixxxermet to include it for testing.

[Basildane]

I would prefer to compile everything from source myself, and not use puppet.
I just have not found any clear documentation on how to do that.

Ubuntu 12.0.4
zm 1.26.3

[secur]

Did you try adding this to the end of the RTSP stream URL: ?tcp

Example: 192.168.1.200/rtsp?realtimemonitor?channel=1
Would be: 192.168.1.200/rtsp?realtimemonitor?channel=1?tcp

[Torsten73]

i had tried this parameter ?tcp on the command line of ffmpeg, it doesn´t work and says the stream couldn´t be found.
I have now tried rtsp:..192.168.115.201:554/channel1?tcp inside of zm camera source address and amazing here the parameter is acepted.

And the stream of h264 is working (sometime i see the distorsion when havy changes happens), but now i have a very poor frame rate of less than 2 frames in web live view.

I try now to adjust ffmpeg output option from -vcodec libx264 -tune zerolatency -f mp4 to another format.
I think the workload is ok and below 2 for quad core.

But why is the framerate in live view so poor now. i have choosen 10 frames /s in camera and in my options profil low bandwith

[Basildane]

Did you try adding this to the end of the RTSP stream URL: ?tcp

Example: 192.168.1.200/rtsp?realtimemonitor?channel=1
Would be: 192.168.1.200/rtsp?realtimemonitor?channel=1?tcp

I tried it, same smearing problem exists.

[Torsten73]

i havent´t installed the patch yet now, in fact enabling ?tcp reduced the framerate to less than 2 frames/s wich is also shown in webif. it has nothing to do with ffmpeg_output_options

I still can´t see a differenz in ffmpeg_output_option. Anyway what i take there is has nowhere an effect. its exactly the same like i disable the checkbox of ffmpeg.
So i still believe there is something wrong and the output options seems to be ignored.

Can somebody explan how it works to see the live stream and storing an event using h264 or mpeg?
-> stream from cam is h264, so ffmpeg is needed to encode it to mjpeg ?

What is used to send the stream to web_live_view? the original input stream from cam or the decoded input stream from ffmpeg?

I still needs to know how to controll if ffmpeg is working and what option is given to it. I see nothing in syslog and nothing in log of zm.

to many options for live stream and output to configure without knowing what i do. it´s still try and error and this will cost to much time.

[Basildane]

I'm not following how ?tcp is changing anything.
As far as I can tell, my Grandstream cameras ignore it.

What exactly is it supposed to affect?

[Torsten73]

it should advise ffmpeg to force tcp connection to rstp stream instead of udp. With udp we get brocken streams.

[whatboy]

OLD ffmpeg verion... problems...

Code: Select all

FFmpeg version SVN-r26402, Copyright (c) 2000-2011 the FFmpeg developers
  built on Jun 15 2013 17:28:03 with gcc 4.5.1 20100924 (Red Hat 4.5.1-4)
  configuration: --enable-shared --enable-pthreads --enable-gpl --prefix=/usr/local --enable-swscale
  libavutil     50.36. 0 / 50.36. 0
  libavcore      0.16. 1 /  0.16. 1
  libavcodec    52.108. 0 / 52.108. 0
  libavformat   52.93. 0 / 52.93. 0
  libavdevice   52. 2. 3 / 52. 2. 3
  libavfilter    1.74. 0 /  1.74. 0
  libswscale     0.12. 0 /  0.12. 0
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

Use -h to get full help or, even better, run 'man ffmpeg'

NEW ffmpeg version, no problems!!!

Code: Select all

ffmpeg version N-56254-gb7bd688 Copyright (c) 2000-2013 the FFmpeg developers
  built on Sep 28 2013 19:20:33 with gcc 4.5.1 (GCC) 20100924 (Red Hat 4.5.1-4)
  configuration: --enable-shared --enable-pthreads --enable-gpl --prefix=/usr/local --enable-swscale
  libavutil      52. 43.100 / 52. 43.100
  libavcodec     55. 31.101 / 55. 31.101
  libavformat    55. 16.102 / 55. 16.102
  libavdevice    55.  3.100 / 55.  3.100
  libavfilter     3. 84.100 /  3. 84.100
  libswscale      2.  5.100 /  2.  5.100
  libswresample   0. 17.103 /  0. 17.103
  libpostproc    52.  3.100 / 52.  3.100
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

Use -h to get full help or, even better, run 'man ffmpeg'

[Basildane]

I already have a newer version than that.

ffmpeg version N-56712-g07da085 Copyright (c) 2000-2013 the FFmpeg developers
built on Sep 28 2013 13:29:30 with gcc 4.6 (Ubuntu/Linaro 4.6.3-1ubuntu5)
configuration: --enable-shared --enable-swscale --enable-gpl --enable-libx264 --enable-libvpx --enable-libvorbis --enable-libtheora
libavutil 52. 46.100 / 52. 46.100
libavcodec 55. 33.101 / 55. 33.101
libavformat 55. 18.104 / 55. 18.104
libavdevice 55. 3.100 / 55. 3.100
libavfilter 3. 88.100 / 3. 88.100
libswscale 2. 5.100 / 2. 5.100
libswresample 0. 17.103 / 0. 17.103
libpostproc 52. 3.100 / 52. 3.100