Recherche avancée

Sur d’autres sites (10962)

• Generate fmp4 chunks for HLS with ffmpeg

  11 mai 2018, par genxstylez

  I am trying to generate fragmented MP4 as the chunks for HLS as introduced by apple last year.

  See link -> https://bitmovin.com/hls-news-wwdc-2016/

  Does ffmpeg supports this ?

  Thanks !

• How to save rtsp stream without packet loss by using FFMPEG

  11 avril 2021, par sumit singh

  I am saving stream of live camera by using FFMPEG. When i am trying to save the video some data packets are loss so the video is not playing properly.I am using following FFMPEG Library

  



  The command which i am sending is-

  



   String[] cmd = {"-y", "-i", "rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mov", "-c:v", "libx264", "-acodec", "aac","-t", time, file_path};
 execFFmpegBinary(cmd);


  



  I am also try this command but the result is same

  



  String[] cmd = { "-y", "-rtsp_transport", "tcp", "-i",  "rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mov", "-c:v", "libx264", "-preset", "slow", "-b:v", "500k", "-maxrate", "500k", "-bufsize", "3000k", "-vf", "scale=-1:480", "-threads", "0", "-codec:a", "libfdk_aac", "-b:a", "128k", "-t", time, file_path};


  



  Here is the log of command output-

  



  07-15 15:16:55.180 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:16:55.180 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 455 packets
        07-15 15:16:55.190 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:16:55.190 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 16 packets
        07-15 15:16:55.300 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:16:55.300 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 13 packets
        07-15 15:16:55.310 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45c42680] mb_type 58 in P slice too large at 31 16
        07-15 15:16:55.320 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45c42680] error while decoding MB 31 16
        07-15 15:16:55.330 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45c42680] concealing 918 DC, 918 AC, 918 MV errors in P frame
        07-15 15:16:55.330 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:16:55.330 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 55 packets
        07-15 15:16:55.340 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:16:55.340 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 19 packets
        07-15 15:16:55.340 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:16:55.350 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 1 packets
        07-15 15:16:55.350 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x458737c0] out of range intra chroma pred mode at 7 28
        07-15 15:16:55.350 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x458737c0] error while decoding MB 7 28
        07-15 15:16:55.360 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x458737c0] concealing 402 DC, 402 AC, 402 MV errors in P frame
        07-15 15:16:55.360 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45ab8020] P sub_mb_type 8 out of range at 28 14
        07-15 15:16:55.370 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45ab8020] error while decoding MB 28 14
        07-15 15:16:55.370 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45ab8020] concealing 1011 DC, 1011 AC, 1011 MV errors in P frame
        07-15 15:16:55.380 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45afe200] cbp too large (132) at 12 20
        07-15 15:16:55.380 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45afe200] error while decoding MB 12 20
        07-15 15:16:55.390 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45afe200] concealing 757 DC, 757 AC, 757 MV errors in P frame
        07-15 15:16:55.640 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  173 fps=3.6 q=28.0 size=     657kB time=00:00:23.84 bitrate= 225.8kbits/s speed=0.502x
        07-15 15:16:55.840 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:16:55.910 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 520 packets
        07-15 15:16:55.920 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:16:55.920 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 2 packets
        07-15 15:16:55.920 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:16:55.920 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 56 packets
        07-15 15:16:55.930 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x4581bb60] concealing 800 DC, 800 AC, 800 MV errors in P frame
        07-15 15:16:56.010 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45c42680] concealing 311 DC, 311 AC, 311 MV errors in P frame
        07-15 15:16:56.720 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  174 fps=3.6 q=28.0 size=     674kB time=00:00:23.88 bitrate= 231.0kbits/s speed=0.497x
        07-15 15:16:57.050 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  175 fps=3.6 q=28.0 size=     675kB time=00:00:29.00 bitrate= 190.6kbits/s speed=0.596x
        07-15 15:16:57.350 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  177 fps=3.6 q=28.0 size=     686kB time=00:00:30.36 bitrate= 185.1kbits/s speed=0.617x
        07-15 15:16:58.610 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  182 fps=3.6 q=28.0 size=     703kB time=00:00:30.56 bitrate= 188.3kbits/s speed=0.609x
        07-15 15:16:59.120 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:16:59.120 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 23 packets
        07-15 15:16:59.190 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  184 fps=3.6 q=28.0 size=     709kB time=00:00:30.64 bitrate= 189.6kbits/s speed=0.602x
        07-15 15:16:59.200 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45c42680] concealing 69 DC, 69 AC, 69 MV errors in P frame
        07-15 15:16:59.370 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:16:59.440 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 35 packets
        07-15 15:16:59.440 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x458737c0] concealing 338 DC, 338 AC, 338 MV errors in I frame
        07-15 15:16:59.920 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  187 fps=3.6 q=28.0 size=     716kB time=00:00:30.76 bitrate= 190.7kbits/s speed=0.595x
        07-15 15:16:59.920 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:16:59.990 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 20 packets
        07-15 15:16:59.990 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45afe200] concealing 489 DC, 489 AC, 489 MV errors in P frame
        07-15 15:17:01.980 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  190 fps=3.5 q=28.0 size=     737kB time=00:00:30.88 bitrate= 195.4kbits/s speed=0.575x
        07-15 15:17:01.980 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:01.980 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 35 packets
        07-15 15:17:02.060 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:02.060 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 10 packets
        07-15 15:17:02.230 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:02.230 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 10 packets
        07-15 15:17:02.270 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45ab8020] dquant out of range (124) at 15 35
        07-15 15:17:02.270 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45ab8020] error while decoding MB 15 35
        07-15 15:17:02.280 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45ab8020] concealing 79 DC, 79 AC, 79 MV errors in P frame
        07-15 15:17:02.280 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:02.280 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 76 packets
        07-15 15:17:02.290 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45c42680] concealing 805 DC, 805 AC, 805 MV errors in P frame
        07-15 15:17:02.510 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:02.510 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 40 packets
        07-15 15:17:02.600 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  194 fps=3.6 q=28.0 size=     747kB time=00:00:31.04 bitrate= 197.1kbits/s speed=0.57x
        07-15 15:17:02.610 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:02.610 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 60 packets
        07-15 15:17:02.610 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x458737c0] concealing 526 DC, 526 AC, 526 MV errors in P frame
        07-15 15:17:02.620 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x4581bb60] concealing 197 DC, 197 AC, 197 MV errors in P frame
        07-15 15:17:03.380 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  195 fps=3.5 q=28.0 size=     751kB time=00:00:31.08 bitrate= 198.1kbits/s speed=0.562x
        07-15 15:17:03.570 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:03.640 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 474 packets
        07-15 15:17:03.640 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:03.650 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 109 packets
        07-15 15:17:03.650 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x4581bb60] negative number of zero coeffs at 28 22
        07-15 15:17:03.650 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x4581bb60] error while decoding MB 28 22
        07-15 15:17:03.660 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x4581bb60] concealing 651 DC, 651 AC, 651 MV errors in P frame
        07-15 15:17:03.660 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x458737c0] concealing 1074 DC, 1074 AC, 1074 MV errors in P frame
        07-15 15:17:03.920 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  195 fps=3.5 q=28.0 size=     751kB time=00:00:31.08 bitrate= 198.1kbits/s speed=0.557x
        07-15 15:17:05.530 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  199 fps=3.5 q=25.0 size=     766kB time=00:00:32.84 bitrate= 191.2kbits/s speed=0.573x
        07-15 15:17:06.250 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  202 fps=3.5 q=22.0 size=     784kB time=00:00:32.96 bitrate= 194.8kbits/s speed=0.568x
        07-15 15:17:07.130 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  205 fps=3.5 q=28.0 size=     800kB time=00:00:33.08 bitrate= 198.2kbits/s speed=0.562x
        07-15 15:17:08.960 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  207 fps=3.4 q=28.0 size=     811kB time=00:00:35.32 bitrate= 188.0kbits/s speed=0.581x
        07-15 15:17:09.560 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:09.560 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 133 packets
        07-15 15:17:09.660 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  210 fps=3.4 q=28.0 size=     817kB time=00:00:35.84 bitrate= 186.8kbits/s speed=0.584x
        07-15 15:17:09.670 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:09.670 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 14 packets
        07-15 15:17:09.680 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45c42680] concealing 410 DC, 410 AC, 410 MV errors in I frame
        07-15 15:17:09.770 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x4581bb60] concealing 72 DC, 72 AC, 72 MV errors in P frame
        07-15 15:17:10.730 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:10.730 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 24 packets
        07-15 15:17:10.740 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:10.740 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 56 packets
        07-15 15:17:11.410 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  212 fps=3.4 q=28.0 size=     819kB time=00:00:35.92 bitrate= 186.8kbits/s speed=0.574x
        07-15 15:17:11.510 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:11.510 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 14 packets
        07-15 15:17:11.510 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45ab8020] concealing 77 DC, 77 AC, 77 MV errors in P frame
        07-15 15:17:11.520 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  213 fps=3.4 q=28.0 size=     820kB time=00:00:35.96 bitrate= 186.8kbits/s speed=0.568x
        07-15 15:17:11.520 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:11.520 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 10 packets
        07-15 15:17:11.670 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:11.720 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 82 packets
        07-15 15:17:11.730 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:11.730 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 41 packets
        07-15 15:17:11.740 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45c42680] concealing 1343 DC, 1343 AC, 1343 MV errors in I frame
        07-15 15:17:11.740 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:11.750 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 240 packets
        07-15 15:17:11.890 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:11.900 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 7 packets
        07-15 15:17:11.900 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:11.900 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 63 packets
        07-15 15:17:11.940 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45ab8020] out of range intra chroma pred mode at 42 32
        07-15 15:17:11.950 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45ab8020] error while decoding MB 42 32
        07-15 15:17:11.960 25713-25713/com.github.sampleffmpeg V/output: progress : [h264 @ 0x45ab8020] concealing 187 DC, 187 AC, 187 MV errors in P frame
        07-15 15:17:12.420 25713-25713/com.github.sampleffmpeg V/output: progress : [rtsp @ 0x420391c0] max delay reached. need to consume packet
        07-15 15:17:12.420 25713-25713/com.github.sampleffmpeg V/output: progress : [NULL @ 0x4203ba00] RTP: missed 9 packets
        07-15 15:17:12.830 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  217 fps=3.4 q=24.0 size=     881kB time=00:00:36.12 bitrate= 199.7kbits/s speed=0.562x
        07-15 15:17:32.710 25713-25713/com.github.sampleffmpeg V/output: progress : frame=  217 fps=2.6 q=-1.0 Lsize=    1192kB time=00:00:59.48 bitrate= 164.2kbits/s speed=0.703x
        07-15 15:17:32.720 25713-25713/com.github.sampleffmpeg V/output: progress : video:1190kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.207405%
        07-15 15:17:32.820 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] frame I:4     Avg QP:17.76  size: 23826
        07-15 15:17:32.820 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] frame P:141   Avg QP:20.25  size:  7361
        07-15 15:17:32.830 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] frame B:72    Avg QP:23.59  size:  1173
        07-15 15:17:32.830 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] consecutive B-frames: 54.4%  1.8%  6.9% 36.9%
        07-15 15:17:32.840 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] mb I  I16..4: 23.2% 42.9% 34.0%
        07-15 15:17:32.840 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] mb P  I16..4:  3.6%  3.2%  1.9%  P16..4: 27.9%  6.4%  4.8%  0.0%  0.0%    skip:52.3%
        07-15 15:17:32.850 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] mb B  I16..4:  0.1%  0.1%  0.0%  B16..8: 20.2%  1.0%  0.3%  direct: 1.1%  skip:77.2%  L0:42.5% L1:53.9% BI: 3.7%
        07-15 15:17:32.860 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] 8x8 transform intra:38.4% inter:29.9%
        07-15 15:17:32.860 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] coded y,uvDC,uvAC intra: 49.0% 31.1% 15.6% inter: 12.9% 10.5% 1.3%
        07-15 15:17:32.870 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] i16 v,h,dc,p: 72%  6%  5% 17%
        07-15 15:17:32.870 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 45% 16% 17%  2%  4%  3%  4%  5%  3%
        07-15 15:17:32.880 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 26% 19% 15%  5%  6%  4% 10%  9%  6%
        07-15 15:17:32.880 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] i8c dc,h,v,p: 46% 12% 40%  3%
        07-15 15:17:32.880 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] Weighted P-Frames: Y:0.0% UV:0.0%
        07-15 15:17:32.890 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] ref P L0: 78.9%  6.1%  9.5%  5.6%
        07-15 15:17:32.890 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] ref B L0: 87.4%  9.5%  3.1%
        07-15 15:17:32.890 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] ref B L1: 95.5%  4.5%
        07-15 15:17:32.900 25713-25713/com.github.sampleffmpeg V/output: progress : [libx264 @ 0x420a54c0] kb/s:163.45
        07-15 15:17:32.900 25713-25713/com.github.sampleffmpeg V/output: SUCCESS with output : ffmpeg version n3.0.1 Copyright (c) 2000-2016 the FFmpeg developers
        built with gcc 4.8 (GCC)
        configuration: --target-os=linux --cross-prefix=/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/bin/i686-linux-android- --arch=x86 --cpu=i686 --enable-runtime-cpudetect --sysroot=/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-libass --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-fontconfig --enable-pthreads --disable-debug --disable-ffserver --enable-version3 --enable-hardcoded-tables --disable-ffplay --disable-ffprobe --enable-gpl --enable-yasm --disable-doc --disable-shared --enable-static --pkg-config=/home/vagrant/SourceCode/ffmpeg-android/ffmpeg-pkg-config --prefix=/home/vagrant/SourceCode/ffmpeg-android/build/x86 --extra-cflags='-I/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all -march=i686' --extra-ldflags='-L/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-libs='-lpng -lexpat -lm' --extra-cxxflags=
        libavutil      55. 17.103 / 55. 17.103
        libavcodec     57. 24.102 / 57. 24.102
        libavformat    57. 25.100 / 57. 25.100
        libavdevice    57.  0.101 / 57.  0.101
        libavfilter     6. 31.100 /  6. 31.100
        libswscale      4.  0.100 /  4.  0.100
        libswresample   2.  0.101 /  2.  0.101
        libpostproc    54.  0.100 / 54.  0.100
        [udp @ 0x4203b040] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
        [udp @ 0x4203c040] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required)
        Input #0, rtsp, from 'rtsp://81.109.95.91:3000/stream':
        Metadata:
        title           : Session streamed with GStreamer
        comment         : rtsp-server
        Duration: N/A, start: 0.080000, bitrate: N/A
        Stream #0:0: Video: h264 (Constrained Baseline), yuv420p, 720x576, 25 fps, 25 tbr, 90k tbn, 180k tbc
        [libx264 @ 0x420a54c0] using cpu capabilities: none!
        [libx264 @ 0x420a54c0] profile High, level 3.0
        [libx264 @ 0x420a54c0] 264 - core 148 - H.264/MPEG-4 AVC codec - Copyleft 2003-2015 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
        Output #0, matroska, to '/storage/emulated/0/recording15072016-031605.mkv':
        Metadata:
        title           : Session streamed with GStreamer
        comment         : rtsp-server
        encoder         : Lavf57.25.100
        Stream #0:0: Video: h264 (libx264) (H264 / 0x34363248), yuv420p, 720x576, q=-1--1, 25 fps, 1k tbn, 25 tbc
        Metadata:
        encoder         : Lavc57.24.102 libx264
        Side data:
        unknown side data type 10 (24 bytes)
        Stream mapping:
        Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
        Press [q] to stop, [?] for help
        frame=   23 fps=0.0 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x
        [rtsp @ 0x420391c0] max delay reached. need to consume packet
        [NULL @ 0x4203ba00] RTP: missed 29 packets
        [h264 @ 0x45afe200] concealing 104 DC, 104 AC, 104 MV errors in P frame
        frame=   42 fps= 41 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x
        frame=   47 fps= 17 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x
        frame=   52 fps= 14 q=28.0 size=      36kB time=00:00:00.24 bitrate=1231.4kbits/s speed=0.0655x
        frame=   55 fps= 12 q=28.0 size=      46kB time=00:00:00.36 bitrate=1036.1kbits/s speed=0.0783x
        [rtsp @ 0x420391c0] max delay reached. need to con


  



  How to save rtsp stream without packet loss with good quality ? Any help will be appreciated.

  


• How to make Matomo GDPR compliant in 12 steps

  3 avril 2018, par InnoCraft

  Important note : this blog post has been written by digital analysts, not lawyers. The purpose of this article is to briefly show you where Matomo is entering into play within the GDPR process. This work comes from our interpretation of the UK privacy commission : ICO. It cannot be considered as professional legal advice. So as GDPR, this information is subject to change. We strongly advise you to have a look at the different privacy authorities in order to have up to date information.

  The General Data Protection Regulation (EU) 2016/679, also referred to RGPD in French, Datenschutz-Grundverordnung, DS-GVO in German, is a regulation on data protection and privacy for all individuals within the European Union. It concerns organizations worldwide dealing with EU citizens and will come into force on the 25th May 2018.

  The GDPR applies to ‘personal data’ meaning any information relating to an identifiable person who can be directly or indirectly identified in particular by reference to an identifier. It includes cookies, IP addresses, User ID, location, and any other data you may have collected.

  We will list below the 12 steps recommended by the UK privacy commissioner in order to be GDPR compliant and what you need to do for each step.

  The 12 steps of GDPR compliance according to ICO and how it fit with Matomo

  As mentioned in one of our previous blog post about GDPR, if you are not collecting any personal data with Matomo, then you are not concerned about what is written below.

  If you are processing personal data in any way, here are the 12 steps to follow along with some recommendations on how to be GDPR compliant with Matomo :

  1 – Awareness

  Make sure that people within your organization know that you are using Matomo in order to analyze traffic on the website/app. If needed, send them the link to the “What is Matomo ?” page.

  2 – Information you hold

  List all the personal data you are processing with Matomo within your record of processing activities. We are personally using the template provided by ICO which is composed of a set of 30 questions you need to answer regarding your use of Matomo. We have published an article which walks you through the list of questions specifically in the use case of Matomo Analytics. Please be aware that personal data may be also tracked in non-obvious ways for example as part of page URLs or page titles.

  3 – Communicating privacy information

  a – Add a privacy notice

  Add a privacy notice wherever you are using Matomo in order to collect personal data. Please refer to the ICO documentation in order to learn how to write a privacy notice. You can learn more in our article about creating your privacy notice for Matomo Analytics. Make sure that a privacy policy link is always available on your website or app.

  b – Add Matomo to your privacy policy page

  Add Matomo to the list of technologies you are using on your privacy policy page and add all the necessary information to it as requested in the following checklist. To learn more check out our article about Privacy policy.

  4 – Individuals’ rights

  Make sure that your Matomo installation respects all the individuals’ rights. To make it short, you will need to know the features in Matomo that you need to use to respect user rights (right of access, right of rectification, right of erasure…). These features are available starting in Matomo 3.5.0 released on May 8th : GDPR tools for Matomo (User guide).

  5 – Subject access requests

  Make sure that you are able to answer an access request from a data subject for Matomo. For example, when a person would like to access her or his personal data that you have collected about her or him, then you will need to be you able to provide her or him with this information. We recommend you design a process for this like “Who is dealing with it ?” and check that it is working. If you can answer to the nightmare letter, then you are ready. The needed features for this in Matomo will be available soon.

  6 – Lawful basis for processing personal data

  There are different lawful basis you can use under GDPR. It can be either “Legitimate interest” or “Explicit consent”. Do not forget to mention it within your privacy policy page. Read more in our article about lawful basis.

  7 – Consent

  Users should be able to remove their consent at any time. By chance, Matomo is providing a feature in order to do just that : add the opt-out feature to your privacy policy page.
  We are also offering a tool that allows you optionally to require consent before any data is tracked. This will be useful if a person should be only tracked after she or he has given explicit consent to be tracked.

  8 – Children

  If your website or app is targeted for children and you are using Matomo, extra measures will need to be taken. For example you will need to write your privacy policy even more clear and moreover getting parents consent if the child is below 13. As it is a very specific case, we strongly recommend you to follow this link for further information.

  9 – Data breaches

  As you may be collecting personal data with Matomo, you should also check your “data breach procedure” to define if a leak may have consequences on the privacy of the data subject. Please consult ICO’s website for further information.

  10 – Data Protection by Design and Data Protection Impact Assessments

  Ask yourself if you really need to process personal data within Matomo. If the data you are processing within Matomo is sensitive, we strongly recommend you to make a Data Protection Impact Assessment. A software is available from the The open source PIA software helps to carry out data protection impact assessment, by French Privacy Commissioner : CNIL.

  11 – Data Protection Officers

  If you are reading this article and you are the Data Protection Officer (DPO), you will not be concerned by this step. If that’s not the case, your duty is to provide to the DPO (if your business has a DPO) our blog post in order for her or him to ask you questions regarding your use of Matomo. Note that your DPO can also be interested in the different data that Matomo can process : “What data does Matomo track ?” (FAQ).

  12 – International

  Matomo data is hosted wherever you want. So according to the location of the data, you will need to show specific safeguard except for EU. For example regarding the USA, you will have to check if your web hosting platform is registered to the Privacy Shield : privacyshield.gov/list
  Note : our Matomo cloud infrastructure is based in France.

  That’s the end of this blog post. As GDPR is a huge topic, we will release many more blog posts in the upcoming weeks. If there are any Matomo GDPR topic related posts you would like us to write, please feel free to contact us.

  The post How to make Matomo GDPR compliant in 12 steps appeared first on Analytics Platform - Matomo.