Sur d’autres sites (10379)

• Could not write header for output file #0 (incorrect codec parameters ?) : No such file or directory

  1er juillet 2019, par playmaker420

  Im trying to trans code a mp4 file using the following command using a ffmpeg static build

  ./ffmpeg -i /tmp/tools/file_example.mp4 -map 0 -map 0 -map 0 -map 0 -c:v libx265 -f dash \
  
  -b:v:0 25M -b:v:1 15M -b:v:2 6M -b:v:3 1M -maxrate 25M -bufsize 1835k -s:v:0 3840x2160 \
  
  -s:v:1 3840x2160 -s:v:2 1920x1080 -s:v:3 1920x1080 -keyint_min 150 -g 150 \ /tmp/tools/example/4k.mpd

  On executing the command im getting the following exception

   ./ffmpeg -i /tmp/tools/file_example.mp4 -map 0 -map 0 -map 0 -map 0 -c:v libx265 -f dash -b:v:0 25M -b:v:1 15M -b:v:2 6M -b:v:3 1M -maxrate 25M -bufsize 1835k -s:v:0 3840x2160 -s:v:1 3840x2160 -s:v:2 1920x1080 -s:v:3 1920x1080 -keyint_min 150 -g 150 \ /tmp/tools/example/
  
  ffmpeg version 4.1.3-static https://johnvansickle.com/ffmpeg/  Copyright (c) 2000-2019 the FFmpeg developers
  
    built with gcc 6.3.0 (Debian 6.3.0-18+deb9u1) 20170516
  
    configuration: --enable-gpl --enable-version3 --enable-static --disable-debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio --cc=gcc-6 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gmp --enable-gray --enable-libaom --enable-libfribidi --enable-libass --enable-libvmaf --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband --enable-libsoxr --enable-libspeex --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzvbi --enable-libzimg
  
    libavutil      56. 22.100 / 56. 22.100
  
    libavcodec     58. 35.100 / 58. 35.100
  
    libavformat    58. 20.100 / 58. 20.100
  
    libavdevice    58.  5.100 / 58.  5.100
  
    libavfilter     7. 40.101 /  7. 40.101
  
    libswscale      5.  3.100 /  5.  3.100
  
    libswresample   3.  3.100 /  3.  3.100
  
    libpostproc    55.  3.100 / 55.  3.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/tmp/tools/file_example.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42mp41isomavc1
  
      creation_time   : 2015-08-07T09:13:36.000000Z
  
    Duration: 00:00:30.53, start: 0.000000, bitrate: 4675 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 4486 kb/s, 30 fps, 30 tbr, 30 tbn, 60 tbc (default)
  
      Metadata:
  
        creation_time   : 2015-08-07T09:13:36.000000Z
  
        handler_name    : L-SMASH Video Handler
  
        encoder         : AVC Coding
  
      Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 256 kb/s (default)
  
      Metadata:
  
        creation_time   : 2015-08-07T09:13:36.000000Z
  
        handler_name    : L-SMASH Audio Handler
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> hevc (libx265))
  
    Stream #0:1 -> #0:1 (aac (native) -> aac (native))
  
    Stream #0:0 -> #0:2 (h264 (native) -> hevc (libx265))
  
    Stream #0:1 -> #0:3 (aac (native) -> aac (native))
  
    Stream #0:0 -> #0:4 (h264 (native) -> hevc (libx265))
  
    Stream #0:1 -> #0:5 (aac (native) -> aac (native))
  
    Stream #0:0 -> #0:6 (h264 (native) -> hevc (libx265))
  
    Stream #0:1 -> #0:7 (aac (native) -> aac (native))
  
  Press [q] to stop, [?] for help
  
  x265 [info]: HEVC encoder version 3.0ed72af837053
  
  x265 [info]: build info [Linux][GCC 6.3.0][64 bit] 8bit+10bit+12bit
  
  x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
  
  x265 [info]: Main profile, Level-5 (Main tier)
  
  x265 [info]: Thread pool created using 4 threads
  
  x265 [info]: Slices                              : 1
  
  x265 [info]: frame threads / pool features       : 2 / wpp(34 rows)
  
  x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
  
  x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
  
  x265 [info]: ME / range / subpel / merge         : hex / 57 / 2 / 2
  
  x265 [info]: Keyframe min / max / scenecut / bias: 25 / 250 / 40 / 5.00
  
  x265 [info]: Lookahead / bframes / badapt        : 20 / 4 / 2
  
  x265 [info]: b-pyramid / weightp / weightb       : 1 / 1 / 0
  
  x265 [info]: References / ref-limit  cu / depth  : 3 / on / on
  
  x265 [info]: AQ: mode / str / qg-size / cu-tree  : 2 / 1.0 / 32 / 1
  
  x265 [info]: Rate Control / qCompress            : ABR-25000 kbps / 0.60
  
  x265 [info]: VBV/HRD buffer / max-rate / init    : 1835 / 25000 / 0.750
  
  x265 [info]: tools: rd=3 psy-rd=2.00 rskip signhide tmvp strong-intra-smoothing
  
  x265 [info]: tools: lslices=8 deblock sao
  
  x265 [info]: HEVC encoder version 3.0ed72af837053
  
  x265 [info]: build info [Linux][GCC 6.3.0][64 bit] 8bit+10bit+12bit
  
  x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
  
  x265 [info]: Main profile, Level-5 (Main tier)
  
  x265 [info]: Thread pool created using 4 threads
  
  x265 [info]: Slices                              : 1
  
  x265 [info]: frame threads / pool features       : 2 / wpp(34 rows)
  
  x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
  
  x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
  
  x265 [info]: ME / range / subpel / merge         : hex / 57 / 2 / 2
  
  x265 [info]: Keyframe min / max / scenecut / bias: 25 / 250 / 40 / 5.00
  
  x265 [info]: Lookahead / bframes / badapt        : 20 / 4 / 2
  
  x265 [info]: b-pyramid / weightp / weightb       : 1 / 1 / 0
  
  x265 [info]: References / ref-limit  cu / depth  : 3 / on / on
  
  x265 [info]: AQ: mode / str / qg-size / cu-tree  : 2 / 1.0 / 32 / 1
  
  x265 [info]: Rate Control / qCompress            : ABR-15000 kbps / 0.60
  
  x265 [info]: VBV/HRD buffer / max-rate / init    : 1835 / 25000 / 0.750
  
  x265 [info]: tools: rd=3 psy-rd=2.00 rskip signhide tmvp strong-intra-smoothing
  
  x265 [info]: tools: lslices=8 deblock sao
  
  x265 [info]: HEVC encoder version 3.0ed72af837053
  
  x265 [info]: build info [Linux][GCC 6.3.0][64 bit] 8bit+10bit+12bit
  
  x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
  
  x265 [info]: Main profile, Level-4 (High tier)
  
  x265 [info]: Thread pool created using 4 threads
  
  x265 [info]: Slices                              : 1
  
  x265 [info]: frame threads / pool features       : 2 / wpp(17 rows)
  
  x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
  
  x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
  
  x265 [info]: ME / range / subpel / merge         : hex / 57 / 2 / 2
  
  x265 [info]: Keyframe min / max / scenecut / bias: 25 / 250 / 40 / 5.00
  
  x265 [info]: Lookahead / bframes / badapt        : 20 / 4 / 2
  
  x265 [info]: b-pyramid / weightp / weightb       : 1 / 1 / 0
  
  x265 [info]: References / ref-limit  cu / depth  : 3 / on / on
  
  x265 [info]: AQ: mode / str / qg-size / cu-tree  : 2 / 1.0 / 32 / 1
  
  x265 [info]: Rate Control / qCompress            : ABR-6000 kbps / 0.60
  
  x265 [info]: VBV/HRD buffer / max-rate / init    : 1835 / 25000 / 0.750
  
  x265 [info]: tools: rd=3 psy-rd=2.00 rskip signhide tmvp strong-intra-smoothing
  
  x265 [info]: tools: lslices=6 deblock sao
  
  x265 [info]: HEVC encoder version 3.0ed72af837053
  
  x265 [info]: build info [Linux][GCC 6.3.0][64 bit] 8bit+10bit+12bit
  
  x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
  
  x265 [info]: Main profile, Level-4 (High tier)
  
  x265 [info]: Thread pool created using 4 threads
  
  x265 [info]: Slices                              : 1
  
  x265 [info]: frame threads / pool features       : 2 / wpp(17 rows)
  
  x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
  
  x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
  
  x265 [info]: ME / range / subpel / merge         : hex / 57 / 2 / 2
  
  x265 [info]: Keyframe min / max / scenecut / bias: 25 / 250 / 40 / 5.00
  
  x265 [info]: Lookahead / bframes / badapt        : 20 / 4 / 2
  
  x265 [info]: b-pyramid / weightp / weightb       : 1 / 1 / 0
  
  x265 [info]: References / ref-limit  cu / depth  : 3 / on / on
  
  x265 [info]: AQ: mode / str / qg-size / cu-tree  : 2 / 1.0 / 32 / 1
  
  x265 [info]: Rate Control / qCompress            : ABR-1000 kbps / 0.60
  
  x265 [info]: VBV/HRD buffer / max-rate / init    : 1835 / 25000 / 0.750
  
  x265 [info]: tools: rd=3 psy-rd=2.00 rskip signhide tmvp strong-intra-smoothing
  
  x265 [info]: tools: lslices=6 deblock sao
  
  [dash @ 0x5f21000] Opening ' /tmp/tools/example/init-stream0.m4s' for writingtrate=N/A speed=N/A    
  
  Could not write header for output file #0 (incorrect codec parameters ?): No such file or directory
  
  Error initializing output stream 0:7 -- 
  
  x265 [info]: consecutive B-frames: 100.0% 0.0% 0.0% 0.0% 0.0% 
  
  
  
  encoded 0 frames
  
  [aac @ 0x5f30d00] Qavg: -nan
  
  [aac @ 0x5f30d00] 1 frames left in the queue on closing
  
  x265 [info]: consecutive B-frames: 100.0% 0.0% 0.0% 0.0% 0.0% 
  
  
  
  encoded 0 frames
  
  [aac @ 0x5f24ac0] Qavg: -nan
  
  [aac @ 0x5f24ac0] 1 frames left in the queue on closing
  
  x265 [info]: consecutive B-frames: 100.0% 0.0% 0.0% 0.0% 0.0% 
  
  
  
  encoded 0 frames
  
  [aac @ 0x5f33ec0] Qavg: -nan
  
  [aac @ 0x5f33ec0] 1 frames left in the queue on closing
  
  x265 [info]: consecutive B-frames: 100.0% 0.0% 0.0% 0.0% 0.0% 
  
  
  
  encoded 0 frames
  
  [aac @ 0x5f434c0] Qavg: -nan
  
  Conversion failed!

  ffmpeg -version

  ./ffmpeg -version
  
  ffmpeg version 4.1.3-static https://johnvansickle.com/ffmpeg/  Copyright (c) 2000-2019 the FFmpeg developers
  
  built with gcc 6.3.0 (Debian 6.3.0-18+deb9u1) 20170516
  
  configuration: --enable-gpl --enable-version3 --enable-static --disable-debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio --cc=gcc-6 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gmp --enable-gray --enable-libaom --enable-libfribidi --enable-libass --enable-libvmaf --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband --enable-libsoxr --enable-libspeex --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzvbi --enable-libzimg
  
  libavutil      56. 22.100 / 56. 22.100
  
  libavcodec     58. 35.100 / 58. 35.100
  
  libavformat    58. 20.100 / 58. 20.100
  
  libavdevice    58.  5.100 / 58.  5.100
  
  libavfilter     7. 40.101 /  7. 40.101
  
  libswscale      5.  3.100 /  5.  3.100
  
  libswresample   3.  3.100 /  3.  3.100
  
  libpostproc    55.  3.100 / 55.  3.100

  Can someone help me to rectify the issue ?

• ffmpeg -Video live feed

  22 juin 2019, par Rajeev

  I am using AMCREST security camera at my home. My objective is to get a live feed one of IP camera attached to my NVR to a webportal using rtsp ://My environment is Raspberry pi.

  I am able to successfully start the ffserver but conversion is failing when I am trying pass the input video and stream it to video.ffm

  I have tried various combination of parameters in the command but the below one seems to be very close where I got only one error ( av_interleaved_write_frame() : Connection reset by peer)

  $ffmpeg  -thread_queue_size 800  -i "rtsp://home:Home1234@192.168.1.32:554/cam/realmonitor?channel=4&subtype=0" -f lavfi -i aevalsrc=0  http://127.0.0.1:8090/video.ffm 

  ******* ffmpeg server configuration file content : etc/livestream.conf

  #Default port
  
  HTTPPort 8090
  
  HTTPBindAddress 0.0.0.0
  
  MaxHTTPConnections 2000
  
  MaxClients 1000
  
  MaxBandwidth 100000
  
  CustomLog -
  
  
  
  #############################################################
  
  
  
  <feed>
  
    File /tmp/video.ffm                    # this creates a temp video.ffm file where streams are read/write
  
    FileMaxSize 0.5G
  
    ACL allow localhost
  
    ACL allow 127.0.0.1
  
    ACL allow 192.168.0.0 192.168.255.255
  
  </feed>
  
  
  
  <stream stream="stream">
  
  # streaming for webm file
  
  # run : ffserver -f /etc/ffserver.conf
  
  # run : ffmpeg -i videoname.mp4 http://localhost:8090/video.ffm
  
  # error : encoder setup failed
  
    Feed video.ffm
  
    Format webm
  
  
  
  # Audio settings
  
    AudioCodec vorbis
  
    AudioBitRate 64                             # Audio bitrate
  
  
  
  # Video settings
  
    VideoCodec libvpx
  
    VideoSize 720x486                           # Video resolution
  
    VideoFrameRate 30                           # Video FPS
  
    AVOptionVideo flags +global_header          # Parameters passed to encoder
  
  
  
    AVOptionVideo cpu-used 0
  
    AVOptionVideo qmin 10                       # lower the better, min 0
  
    AVOptionVideo qmax 42                       # higher outputs bad quality, max 63
  
    AVOptionVideo quality good
  
    AVOptionAudio flags +global_header
  
    PreRoll 15
  
    StartSendOnKey
  
    VideoBitRate 400                            # Video bitrate
  
  </stream>
  
  
  
  
  
  
  
  ###########################################################################
  
  
  
  # Audio only
  
  # run ffmpeg -i audio.mp3 http://localhost:8090/audio.ffm
  
  # run http://localhost:8090/audio in vlc or browser
  
  
  
  <feed>
  
    File /tmp/audio.ffm
  
    FileMaxSize 1G
  
    ACL allow localhost
  
    ACL allow 127.0.0.1
  
    ACL allow 192.168.0.0 192.168.255.255
  
  </feed>
  
  
  
  <stream audio="audio">
  
    Feed audio.ffm
  
    Format mp2                                     #audio format
  
    AudioCodec libmp3lame                          #audio codec
  
    AudioBitRate 64                                #audio bitrate
  
    AudioChannels 1                                #audio channel, 1 for mono and 2 for stereo
  
    AudioSampleRate 44100
  
    NoVideo                                        #discard video
  
  </stream>
  
  
  
  ####################################################################
  
  #view status of ffserver
  
  <stream>
  
    Format status
  
    ACL allow localhost
  
    ACL allow 192.168.0.0 192.168.255.255
  
  </stream>
  
  
  
  
  
  
  
  # Redirect index.html to the appropriate site
  
  
  
  <redirect>
  
    URL http://www.ffmpeg.org/
  
  </redirect>

  *****output of ffmpeg server running successfully on separate console***

  $ ffserver -f /etc/livestream.conf

  ffserver version 3.2.14-1 deb9u1+rpt1 Copyright (c) 2000-2019 the FFmpeg developers
  built with gcc 6.3.0 (Raspbian 6.3.0-18+rpi1+deb9u1) 20170516
  configuration : —prefix=/usr —extra-version=’1 deb9u1+rpt1’ —toolchain=hardened —libdir=/usr/lib/arm-linux-gnueabihf —incdir=/usr/include/arm-linux-gnueabihf —enable-gpl —disable-stripping —enable-avresample —enable-avisynth —enable-gnutls —enable-ladspa —enable-libass —enable-libbluray —enable-libbs2b —enable-libcaca —enable-libcdio —enable-libebur128 —enable-libflite —enable-libfontconfig —enable-libfreetype —enable-libfribidi —enable-libgme —enable-libgsm —enable-libmp3lame —enable-libopenjpeg —enable-libopenmpt —enable-libopus —enable-libpulse —enable-librubberband —enable-libshine —enable-libsnappy —enable-libsoxr —enable-libspeex —enable-libssh —enable-libtheora —enable-libtwolame —enable-libvorbis —enable-libvpx —enable-libwavpack —enable-libwebp —enable-libx265 —enable-libxvid —enable-libzmq —enable-libzvbi —enable-omx —enable-omx-rpi —enable-mmal —enable-openal —enable-opengl —enable-sdl2 —enable-libdc1394 —enable-libiec61883 —arch=armhf —enable-chromaprint —enable-frei0r —enable-libopencv —enable-libx264 —enable-shared
  libavutil 55. 34.101 / 55. 34.101
  libavcodec 57. 64.101 / 57. 64.101
  libavformat 57. 56.101 / 57. 56.101
  libavdevice 57. 1.100 / 57. 1.100
  libavfilter 6. 65.100 / 6. 65.100
  libavresample 3. 1. 0 / 3. 1. 0
  libswscale 4. 2.100 / 4. 2.100
  libswresample 2. 3.100 / 2. 3.100
  libpostproc 54. 1.100 / 54. 1.100
  /etc/livestream.conf:45 : Setting default value for audio sample rate = 22050. Use NoDefaults to disable it.
  /etc/livestream.conf:45 : Setting default value for audio channel count = 1. Use NoDefaults to disable it.
  /etc/livestream.conf:45 : Setting default value for video bit rate tolerance = 100000. Use NoDefaults to disable it.
  /etc/livestream.conf:45 : Setting default value for video rate control equation = tex^qComp. Use NoDefaults to disable it.
  /etc/livestream.conf:45 : Setting default value for video max rate = 13749264. Use NoDefaults to disable it.
  /etc/livestream.conf:45 : Setting default value for video buffer size = 800000. Use NoDefaults to disable it.
  Fri Jun 21 19:43:59 2019 FFserver started.

  ---

  2nd Console

  $$ffmpeg  -thread_queue_size 800  -i "rtsp://home:Home1234@192.168.1.32:554/cam/realmonitor?channel=4&subtype=0" -f lavfi -i aevalsrc=0  http://127.0.0.1:8090/video.ffm 

  *************************Output**********

  Input #0, rtsp, from 'rtsp://home:Home1234@192.168.1.32:554/cam/realmonitor?channel=4&subtype=0':
  
    Metadata:
  
      title           : Media Server
  
    Duration: N/A, start: 0.290000, bitrate: N/A
  
      Stream #0:0: Video: h264 (High), yuvj420p(pc, bt709, progressive), 2304x1296 [SAR 1:1 DAR 16:9], 20 fps, 250 tbr, 90k tbn, 40 tbc
  
  Input #1, lavfi, from 'aevalsrc=0':
  
    Duration: N/A, start: 0.000000, bitrate: 2822 kb/s
  
      Stream #1:0: Audio: pcm_f64le, 44100 Hz, mono, dbl, 2822 kb/s
  
  [swscaler @ 0x256dd80] deprecated pixel format used, make sure you did set range correctly
  
  [libvpx @ 0x2564190] v1.6.1
  
  Output #0, ffm, to 'http://127.0.0.1:8090/video.ffm':
  
    Metadata:
  
      title           : Media Server
  
      creation_time   : now
  
      encoder         : Lavf57.56.101
  
      Stream #0:0: Audio: vorbis (libvorbis), 22050 Hz, mono, fltp, 64 kb/s
  
      Metadata:
  
        encoder         : Lavc57.64.101 libvorbis
  
      Stream #0:1: Video: vp8 (libvpx), yuv420p, 720x486 [SAR 6:5 DAR 16:9], q=10-42, 400 kb/s, 20 fps, 1000k tbn, 30 tbc
  
      Metadata:
  
        encoder         : Lavc57.64.101 libvpx
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/0 buffer size: 800000 vbv_delay: -1
  
  Stream mapping:
  
    Stream #1:0 -> #0:0 (pcm_f64le (native) -> vorbis (libvorbis))
  
    Stream #0:0 -> #0:1 (h264 (native) -> vp8 (libvpx))
  
  Press [q] to stop, [?] for help
  
  frame=    2 fps=1.2 q=0.0 size=       8kB time=00:00:00.03 bitrate=1966.0kbits/s dup=1 drop=0 speed=0.0av_interleaved_write_frame(): Connection reset by peer
  
  Error writing trailer of http://127.0.0.1:8090/video.ffm: Connection reset by peer frame=    2 fps=1.1 q=0.0 Lsize=      40kB time=00:00:00.03 bitrate=9830.2kbits/s dup=1 drop=0 speed=0.0189x    
  
  video:29kB audio:0kB subtitle:0kB other streams:0kB global headers:4kB muxing overhead: 36.183796%
  
  Conversion failed

  My expectation is that ffmpeg will start writing data to video.ffm located in /tmp directory so that I can read the data from our browser or vlc media player by just entering the following link
  http://localhost:8090/stream

  ****** Update after 2 hr******

  I made slight change to the command parameter and my out changed as well.What it looks like the temporary video file that got generated in /tmp folder is not getting consumes by video.ffm ( I may be wrong in my analysis)

  ffmpeg  -thread_queue_size 1200  -i "rtsp://home:Home1234@192.168.1.32:554/cam/realmonitor?channel=4&subtype=0" -f lavfi -i aevalsrc=0 -override_ffserver  http://127.0.0.1:8090/video.ffm

  ***************** Output ****

  Past duration 0.660332 too large     376kB time=00:00:01.03 bitrate=2978.9kbits/s dup=3 drop=5 speed=0.171x    
  
  Past duration 0.637352 too large     840kB time=00:00:03.72 bitrate=1847.5kbits/s dup=14 drop=5 speed=0.213x    
  
  Past duration 0.678307 too large
  
  Past duration 0.713280 too large    1180kB time=00:00:05.52 bitrate=1749.0kbits/s dup=21 drop=5 speed=0.218x    
  
  Past duration 0.901085 too large    1372kB time=00:00:06.72 bitrate=1670.4kbits/s dup=26 drop=5 speed=0.22x     
  
  Past duration 0.948051 too large    2456kB time=00:00:12.97 bitrate=1551.1kbits/s dup=51 drop=5 speed=0.226x    
  
  [rtsp @ 0x1fd7670] Thread message queue blocking; consider raising the thread_queue_size option (current value: 1200)
  
  Past duration 0.713280 too large    3336kB time=00:00:17.64 bitrate=1549.0kbits/s dup=70 drop=5 speed=0.228x    
  
  [rtsp @ 0x1fd7670] max delay reached. need to consume packetbitrate=1537.0kbits/s dup=76 drop=5 speed=0.229x    
  
  [rtsp @ 0x1fd7670] RTP: missed 30 packets
  
  [rtsp @ 0x1fd7670] max delay reached. need to consume packetbitrate=1533.3kbits/s dup=78 drop=5 speed=0.228x    
  
  [rtsp @ 0x1fd7670] RTP: missed 134 packets
  
  [rtsp @ 0x1fd7670] max delay reached. need to consume packetbitrate=1539.5kbits/s dup=82 drop=5 speed=0.229x    
  
  [rtsp @ 0x1fd7670] RTP: missed 111 packets
  
  [rtsp @ 0x1fd7670] max delay reached. need to consume packetbitrate=1526.3kbits/s dup=84 drop=5 speed=0.229x    
  
  [rtsp @ 0x1fd7670] RTP: missed 19 packets
  
  [rtsp @ 0x1fd7670] max delay reached. need to consume packetbitrate=1521.7kbits/s dup=92 drop=5 speed=0.23x     
  
  [rtsp @ 0x1fd7670] RTP: missed 626 packets
  
  Past duration 0.651329 too large    4408kB time=00:00:23.64 bitrate=1527.0kbits/s dup=94 drop=5 speed=0.23x    
  
  [rtsp @ 0x1fd7670] max delay reached. need to consume packetbitrate=1516.7kbits/s dup=94 drop=5 speed=0.23x    
  
  [rtsp @ 0x1fd7670] RTP: missed 134 packets
  
  [rtsp @ 0x1fd7670] max delay reached. need to consume packetbitrate=1521.3kbits/s dup=98 drop=5 speed=0.231x    
  
  [rtsp @ 0x1fd7670] RTP: missed 123 packets
  
  Past duration 0.633354 too large    4608kB time=00:00:24.98 bitrate=1511.0kbits/s dup=99 drop=5 speed=0.23x     
  
  [rtsp @ 0x1fd7670] max delay reached. need to consume packetbitrate=1523.4kbits/s dup=99 drop=5 speed=0.231x    

• Exceeded GA’s 10M hits data limit, now what ?

  21 juin 2019, par Joselyn Khor
  Exceeded GA’s 10M hits data limit, now what ? Matomo has the answers

  “Your data volume (1XXM hits) exceeds the limit of 10M hits per month as outlined in our Terms of Service. If you continue to exceed the limit, we will stop processing new data on XXX 21, 2019. Learn more about possible solutions.”

  Yikes. Alarm bells were ringing when a Google Analytics free user came to us faced with this notice. Let’s call him ‘Mark’. Mark had reached the limits on the data he could collect through Google Analytics and was shocked by the limited options available to fix the problem, without blowing the budget. The thoughts racing through his head were :

  • “What happens to all my data ?”
  • “What if Google starts charging USD150K now ?”

  Then he came across Matomo and decided to get in touch with our support team …

  “Can you fix this issue ?” he asked us.

  “Absolutely !” we said.

  We’ll get back to helping Mark in a minute. For now let’s go over why this was such a dilemma for him.

  In order to resolve this data limits issue, one of the solutions was for him to upgrade to Google Analytics 360, which meant shelling out USD150,000 per year for their 1 billion hits per month option. Going from free to USD150,000 was too much of a stretch for a growing company.

  “Your data volume (1XXM hits) exceeds the limit of 10M hits per month …”, what did this message mean ?

  With the free version, Mark could collect up to 10 million “hits” per month, per account. Going over meant Google Analytics could stop collecting any more data for free as outlined in their Terms.

  Google Analytics’ Terms of Service (2018, sec. 2) states, “Subject to Section 15, the Service is provided without charge to You for up to 10 million Hits per month per account.”[1]

  In general, what’s a "hit" ?

  Data being sent to Google Analytics. It can be a transaction, event, social interaction or pageview - these all produce what Google calls a “hit”.

  

  And their Analytics Help Data Limits (n.d.) support page makes clear that : “If a property sends more hits per month to Analytics than allowed by the Analytics Terms of Service, there is no assurance that the excess hits will be processed. If the property’s hit volume exceeds this limit, a warning may be displayed in the user interface and you may be prevented from accessing reports.”[2]

  

  Possible solutions

  So the possible solutions given by Google Analytics’ Data Limits support page were (also shown in image below) :

  • To pay USD150K to upgrade to Google Analytics 360
  • To send fewer hits by setting up sampling
  • Or choose the slightly less relevant option to upgrade mobile app tracking to Google Analytics for Firebase.

  Without the means to pay, the free version was fast becoming inaccessible for Mark as he was facing a future where he risked no longer having access to up-to-date data used in his business’ reporting.

  Mark was facing a problem that potentially didn’t have a cost-effective solution.

  

  So what can you really do about it ?

  This is where we can help provide some assistance. If you’re reading this article, we’ll assume you can relate to Mark and share with you the advice on options we gave him.

  Options :

  One option posed by Google is for you to send fewer hits by auditing your data collection processes

  If you really don’t have the budget, you’ll need to reassess your data collection priorities and go over your strategies to see what is necessary to track, and what isn’t.

  • Make sure you know what you’re tracking and why. Look at what websites are being tracked by Google and into what properties.
  • Go through what data you’re tracking and decide what is or isn’t of value.
  • Set up data sampling, this however, will lead to inaccurate data.

  From here you can start to course correct. If you’ve found data you’re not using for analysis, get rid of these events/pageviews in your Google Analytics.

  But the limitations here are that eventually, you’re going to run out of irrelevant metrics and everything you’re tracking will be essential. So you’ll hit another brick wall and return to the same situation.

  Option 2 – Ignore and continue using the free version of Google Analytics

  With this option, you’ll have to bear the business risks involved by basing decisions off of analytics reports that may or may not be updated. In this case, you may still get contacted about exceeding the limits. As the free service is provided for only up to 10 million hits, once you’ve gone over them, you’re violating what’s stipulated in the Terms of Service. 

  There’s also the warning that “… you may be prevented from accessing reports” (Data limits, n.d.). So while we may not know for certain what Google Analytics will do, in this case it may be better to be safe rather than sorry by acting quickly to resolve it. 

  Option 3 –The Matomo solution. Upgrade to a web analytics platform that can handle your demanding data requirements

  Save money while continuing to gain valuable insights by moving over to Matomo Analytics (recommended)

  This is where you can save up to USD130,000 a year. As well as that, the transition from Google Analytics to the Matomo Cloud is a seamless experience as setup and maintenance is taken care of by our experts.

  For example, you can get up to 15M pageviews for USD1,612.50/month (or USD19,350/year) on the Essentials plan.

  Or even 25M pageviews for USD2400/month (or USD24000/year) on the Business plan – which offers additional web analytics and conversion optimization resources.

  Matomo Cloud is a great option if you’re looking for a secure, cost-effective and powerful analytics solution. You also get what Google Analytics could never offer you : full control and ownership of your own data and privacy. 

  No need to worry about losing your Google Analytics data because …

  Now you can import your historic Google Analytics data directly into your Matomo with the Google Analytics Importer tool. Simply follow the step-by-step guide to get started for free.

  Along with savings you can get :

  • A solution for the data limits issue forever. You choose the right plan to suit your data needs and adapt as you continue growing
  • 100% accurate data (no data sampling)
  • 100% data ownership of all your information without signing away your data to a third party
  • Powerful web analytics and conversion optimization features
  • Matomo Tag Manager
  • Easy setup
  • Support from Matomo’s specialists

  Learn more about Matomo Cloud pricing.

  

  Or go for Matomo On-Premise

  If you have the in-house infrastructure to support self-hosting Matomo on your own servers then there’s also the option of Matomo On-Premise. Here you’ll get full security knowing the data is on your own servers. 

  Setup will also require technical knowledge. There will also be costs associated with acquiring your own servers, and keeping up with regular maintenance and updates. With On-Premise you get maximum flexibility, with no data limits whatsoever. But if you’re coming over from Google Analytics and don’t have the infrastructure and team to host On-Premise, the Matomo Cloud could be right for you.

  Learn more about Matomo On-Premise.

  Where do you go from here ?

  Getting 10 millions hits per month is no small feat, it’s actually pretty fantastic. But if it means having to shell out USD150,000 just to be able to continue with Google Analytics, we feel your problem could be fixed with Matomo Cloud. You could then put the rest of the money you save to better use.

  If you choose Matomo, you now have the option to : 

  • Raise your data limits for a fraction of Google Analytics 360’s price
  • Get a comprehensive range of analytics features for the most impactful insights to ensure your website continues excelling
  • Get data that’s not sampled – meaning 100% accuracy in your reports
  • Migrate your data easily with the help of Matomo’s support team

  We’ll have you covered. 

  By sharing with you the options and advice we gave to Mark, we hope you’ll be able to find a solution that makes your life easier and solves the issue of data restrictions forever.

  The team at Matomo is here to help you every step of the way to ensure a stress-free transition from Google Analytics if that is what works best for you.

  For next steps, why not check out our pricing page to see what could suit your needs !

  References :

  [1] Terms of Service. (2018, July 24). In Google Analytics Terms of Service. Retrieved June 12, 2019, from https://www.google.com/analytics/terms/us.html

  [2] Data limits. (n.d.). In Analytics Help Data limits. Retrieved June 12, 2019, from https://support.google.com/analytics/answer/1070983?hl=en