Sur d’autres sites (14583)

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

  11 mai 2019, par Slim

  I’m struggling with this issue since a couple of days.
  I’m trying to convert an mkv movie and ffmpeg fail with this error when he try to write to the *.ts file.
  I have tried the same command on many hosts (Mac, CentOS, Unraid) but the results was the same. Here the command :

  $ ffmpeg -i MYMOVIE\ FRENCH\ HDLight\ 1080p\ x264\ AC3.mkv -vf "pad=ceil(iw/2)*2:ceil(ih/2)*2" -c:a aac -ar 48000 -b:a 128k -c:v h264 -profile:v main -crf 20 -g 48 -keyint_min 48 -sc_threshold 0 -b:v 2500k -maxrate 2675k -bufsize 3750k -hls_time 4 -hls_playlist_type vod -hls_segment_filename mymovie/720p_%03d.ts mymovie/720p.m3u8

  Please find below the entire output of the ffmpeg command :

  ffmpeg version 3.3.3 Copyright (c) 2000-2017 the FFmpeg developers
  
    built with Apple LLVM version 8.1.0 (clang-802.0.42)
  
    configuration: --prefix=/usr/local/Cellar/ffmpeg/3.3.3 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-libmp3lame --enable-libx264 --enable-libxvid --enable-opencl --disable-lzma --enable-vda
  
    libavutil      55. 58.100 / 55. 58.100
  
    libavcodec     57. 89.100 / 57. 89.100
  
    libavformat    57. 71.100 / 57. 71.100
  
    libavdevice    57.  6.100 / 57.  6.100
  
    libavfilter     6. 82.100 /  6. 82.100
  
    libavresample   3.  5.  0 /  3.  5.  0
  
    libswscale      4.  6.100 /  4.  6.100
  
    libswresample   2.  7.100 /  2.  7.100
  
    libpostproc    54.  5.100 / 54.  5.100
  
  Input #0, matroska,webm, from 'MYMOVIE FRENCH HDLight 1080p x264 AC3.mkv':
  
    Metadata:
  
      title           : ˜”*°• Wita •°*”˜
  
      encoder         : libebml v1.3.3 + libmatroska v1.4.4
  
      creation_time   : 2016-01-18T20:04:46.000000Z
  
    Duration: 02:28:06.88, start: 0.000000, bitrate: 3276 kb/s
  
      Chapter #0:0: start 0.000000, end 369.119000
  
      Metadata:
  
        title           : 00:00:00.000
  
      Chapter #0:1: start 369.119000, end 784.784000
  
      Metadata:
  
        title           : 00:06:09.119
  
      Chapter #0:2: start 784.784000, end 1138.471000
  
      Metadata:
  
        title           : 00:13:04.784
  
      Chapter #0:3: start 1138.471000, end 1486.777000
  
      Metadata:
  
        title           : 00:18:58.471
  
      Chapter #0:4: start 1486.777000, end 1684.057000
  
      Metadata:
  
        title           : 00:24:46.777
  
      Chapter #0:5: start 1684.057000, end 1935.559000
  
      Metadata:
  
        title           : 00:28:04.057
  
      Chapter #0:6: start 1935.559000, end 2218.591000
  
      Metadata:
  
        title           : 00:32:15.559
  
      Chapter #0:7: start 2218.591000, end 2516.639000
  
      Metadata:
  
        title           : 00:36:58.591
  
      Chapter #0:8: start 2516.639000, end 2773.145000
  
      Metadata:
  
        title           : 00:41:56.639
  
      Chapter #0:9: start 2773.145000, end 3051.924000
  
      Metadata:
  
        title           : 00:46:13.145
  
      Chapter #0:10: start 3051.924000, end 3223.220000
  
      Metadata:
  
        title           : 00:50:51.924
  
      Chapter #0:11: start 3223.220000, end 3621.368000
  
      Metadata:
  
        title           : 00:53:43.220
  
      Chapter #0:12: start 3621.368000, end 4008.213000
  
      Metadata:
  
        title           : 01:00:21.368
  
      Chapter #0:13: start 4008.213000, end 4258.963000
  
      Metadata:
  
        title           : 01:06:48.213
  
      Chapter #0:14: start 4258.963000, end 4514.093000
  
      Metadata:
  
        title           : 01:10:58.963
  
      Chapter #0:15: start 4514.093000, end 4735.648000
  
      Metadata:
  
        title           : 01:15:14.093
  
      Chapter #0:16: start 4735.648000, end 5171.041000
  
      Metadata:
  
        title           : 01:18:55.648
  
      Chapter #0:17: start 5171.041000, end 5380.000000
  
      Metadata:
  
        title           : 01:26:11.041
  
      Chapter #0:18: start 5380.000000, end 5803.548000
  
      Metadata:
  
        title           : 01:29:40.000
  
      Chapter #0:19: start 5803.548000, end 6104.390000
  
      Metadata:
  
        title           : 01:36:43.548
  
      Chapter #0:20: start 6104.390000, end 6546.415000
  
      Metadata:
  
        title           : 01:41:44.390
  
      Chapter #0:21: start 6546.415000, end 6952.821000
  
      Metadata:
  
        title           : 01:49:06.415
  
      Chapter #0:22: start 6952.821000, end 7179.214000
  
      Metadata:
  
        title           : 01:55:52.821
  
      Chapter #0:23: start 7179.214000, end 7459.744000
  
      Metadata:
  
        title           : 01:59:39.214
  
      Chapter #0:24: start 7459.744000, end 7768.511000
  
      Metadata:
  
        title           : 02:04:19.744
  
      Chapter #0:25: start 7768.511000, end 8045.663000
  
      Metadata:
  
        title           : 02:09:28.511
  
      Chapter #0:26: start 8045.663000, end 8382.374000
  
      Metadata:
  
        title           : 02:14:05.663
  
      Chapter #0:27: start 8382.374000, end 8886.880000
  
      Metadata:
  
        title           : 02:19:42.374
  
      Stream #0:0(fre): Audio: ac3, 48000 Hz, 5.1(side), fltp, 448 kb/s (default) (forced)
  
      Metadata:
  
        title           : AC3 Fr
  
        BPS             : 448000
  
        BPS-eng         : 448000
  
        DURATION        : 02:28:06.880000000
  
        DURATION-eng    : 02:28:06.880000000
  
        NUMBER_OF_FRAMES: 277715
  
        NUMBER_OF_FRAMES-eng: 277715
  
        NUMBER_OF_BYTES : 497665280
  
        NUMBER_OF_BYTES-eng: 497665280
  
        _STATISTICS_WRITING_APP: mkvmerge v8.8.0 ('Wind at my back') 64bit
  
        _STATISTICS_WRITING_APP-eng: mkvmerge v8.8.0 ('Wind at my back') 64bit
  
        _STATISTICS_WRITING_DATE_UTC: 2016-01-18 20:04:46
  
        _STATISTICS_WRITING_DATE_UTC-eng: 2016-01-18 20:04:46
  
        _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
  
        _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
  
      Stream #0:1(fre): Subtitle: subrip (default) (forced)
  
      Metadata:
  
        title           : FR Forcé
  
        BPS             : 1
  
        BPS-eng         : 1
  
        DURATION        : 02:27:01.396000000
  
        DURATION-eng    : 02:27:01.396000000
  
        NUMBER_OF_FRAMES: 53
  
        NUMBER_OF_FRAMES-eng: 53
  
        NUMBER_OF_BYTES : 1254
  
        NUMBER_OF_BYTES-eng: 1254
  
        _STATISTICS_WRITING_APP: mkvmerge v8.8.0 ('Wind at my back') 64bit
  
        _STATISTICS_WRITING_APP-eng: mkvmerge v8.8.0 ('Wind at my back') 64bit
  
        _STATISTICS_WRITING_DATE_UTC: 2016-01-18 20:04:46
  
        _STATISTICS_WRITING_DATE_UTC-eng: 2016-01-18 20:04:46
  
        _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
  
        _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
  
      Stream #0:2(fre): Video: h264 (High), yuv420p(progressive), 1920x808 [SAR 1:1 DAR 240:101], 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default) (forced)
  
      Metadata:
  
        title           : ˜”*°• Wita •°*”˜
  
        BPS             : 2826414
  
        BPS-eng         : 2826414
  
        DURATION        : 02:28:06.837000000
  
        DURATION-eng    : 02:28:06.837000000
  
        NUMBER_OF_FRAMES: 213071
  
        NUMBER_OF_FRAMES-eng: 213071
  
        NUMBER_OF_BYTES : 3139735201
  
        NUMBER_OF_BYTES-eng: 3139735201
  
        _STATISTICS_WRITING_APP: mkvmerge v8.8.0 ('Wind at my back') 64bit
  
        _STATISTICS_WRITING_APP-eng: mkvmerge v8.8.0 ('Wind at my back') 64bit
  
        _STATISTICS_WRITING_DATE_UTC: 2016-01-18 20:04:46
  
        _STATISTICS_WRITING_DATE_UTC-eng: 2016-01-18 20:04:46
  
        _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
  
        _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
  
  Stream mapping:
  
    Stream #0:2 -> #0:0 (h264 (native) -> h264 (libx264))
  
    Stream #0:0 -> #0:1 (ac3 (native) -> aac (native))
  
    Stream #0:1 -> #0:2 (subrip (srt) -> webvtt (native))
  
  Press [q] to stop, [?] for help
  
  [libx264 @ 0x7f967102da00] using SAR=1/1
  
  [libx264 @ 0x7f967102da00] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
  
  [libx264 @ 0x7f967102da00] profile Main, level 4.0
  
  [hls @ 0x7f9671037200] Opening 'mymovie/720p_000.ts' for writing
  
  Could not write header for output file #0 (incorrect codec parameters ?): No such file or directory
  
  Error initializing output stream 0:0 -- 
  
  [aac @ 0x7f967102f200] Qavg: 27242.438
  
  [aac @ 0x7f967102f200] 2 frames left in the queue on closing
  
  Conversion failed!

  Could you help please ?

• How to fix ffmpeg complex filters "Invalid stream specifier" [duplicate]

  15 mai 2019, par Chase

  This question already has an answer here :

  • FFmpeg filter_complex concat gives only first input on crop
    
    1 answer
    
  • Problems building Image slideshow with sliding transition using ffmpeg
    
    1 answer
    
  • ffmpeg : chain of multiple filter_complex, re-using intermediate output stream
    
    1 answer
    

  I’m attempting to scale and blur (sections of) a video with ffmpeg complex filters. This has actually been working in production for years.

  I’m now running a newer build of ffmpeg on Ubuntu 18.04 and getting an error relating to the filters where the same command works fine on Ubuntu 16.04’s ffmpeg against the same video.

  
  Specifically, I’m seeing the following error :

  mov,mp4,m4a,3gp,3g2,mj2 @ 0x56055a5902c0] Invalid stream specifier: vs0.
  
      Last message repeated 1 times
  
  Stream specifier 'vs0' in filtergraph description ... matches no streams.

  Has something about the complex filter API changed that would make this same input invalid in a newer version of ffmpeg ?

  ---

  The command in question is just running the following in a Bash terminal.

  ffmpeg -ss 60 -i ~/test.mp4 -y -filter_complex "[0:v]scale=-2:'min(320,ih)'[vs0];[vs0]crop=in_w/9:in_h/2:0:0,boxblur=5:1:cr=3:ar=3[b0];[vs0]crop=in_w/9:in_h/2:in_w-out_w:0,boxblur=5:1:cr=3:ar=3[b1];[vs0]crop=(in_w-2*in_w/9):in_h/20:in_w/9:0,boxblur=5:1:cr=3:ar=3[b2];[vs0][b0]overlay=0:0[ovr0];[ovr0][b1]overlay=main_w-overlay_w:0[ovr1];[ovr1][b2]overlay=main_w/9:0[vs1]" -map [vs1] -an -ac 2 -b:a 128k -acodec aac -b:v 1024k -r 30 -vcodec libx264 -t 300 -y -preset slow -movflags faststart -pix_fmt yuv420p -f mp4 ~/out.mp4

  If we break up the complex filter statement, it looks like :

  [0:v]scale=-2:'min(320,ih)'[vs0];
  
  [vs0]crop=in_w/9:in_h/2:0:0,boxblur=5:1:cr=3:ar=3[b0];
  
  [vs0]crop=in_w/9:in_h/2:in_w-out_w:0,boxblur=5:1:cr=3:ar=3[b1];
  
  [vs0]crop=(in_w-2*in_w/9):in_h/20:in_w/9:0,boxblur=5:1:cr=3:ar=3[b2];
  
  [vs0][b0]overlay=0:0[ovr0];[ovr0][b1]overlay=main_w-overlay_w:0[ovr1];
  
  [ovr1][b2]overlay=main_w/9:0[vs1]

  ---

  On ffmpeg version N-86980-g62b7553 (Ubuntu 16.04), everything works great as it has done for years.

  $ ffmpeg -ss 60 -i ~/test.mp4 -y -filter_complex "[0:v]scale=-2:'min(320,ih)'[vs0];[vs0]crop=in_w/9:in_h/2:0:0,boxblur=5:1:cr=3:ar=3[b0];[vs0]crop=in_w/9:in_h/2:in_w-out_w:0,boxblur=5:1:cr=3:ar=3[b1];[vs0]crop=(in_w-2*in_w/9):in_h/20:in_w/9:0,boxblur=5:1:cr=3:ar=3[b2];[vs0][b0]overlay=0:0[ovr0];[ovr0][b1]overlay=main_w-overlay_w:0[ovr1];[ovr1][b2]overlay=main_w/9:0[vs1]" -map [vs1] -an -ac 2 -b:a 128k -acodec aac -b:v 1024k -r 30 -vcodec libx264 -t 300 -y -preset slow -movflags faststart -pix_fmt yuv420p -f mp4 ~/out.mp4
  
  ffmpeg version N-86980-g62b7553 Copyright (c) 2000-2017 the FFmpeg developers
  
    built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4) 20160609
  
    configuration: --prefix=/root/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/root/ffmpeg_build/include --extra-ldflags=-L/root/ffmpeg_build/lib --bindir=/root/bin --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-openssl --enable-nonfree
  
    libavutil      55. 73.100 / 55. 73.100
  
    libavcodec     57.102.100 / 57.102.100
  
    libavformat    57. 76.100 / 57. 76.100
  
    libavdevice    57.  7.100 / 57.  7.100
  
    libavfilter     6. 98.100 /  6. 98.100
  
    libswscale      4.  7.102 /  4.  7.102
  
    libswresample   2.  8.100 /  2.  8.100
  
    libpostproc    54.  6.100 / 54.  6.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/home/cmaier/test.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf57.76.100
  
    Duration: 00:10:00.00, start: 0.000000, bitrate: 1036 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 768x480, 1033 kb/s, 30 fps, 30 tbr, 15360 tbn, 60 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
  Stream mapping:
  
    Stream #0:0 (h264) -> scale
  
    Stream #0:0 (h264) -> crop
  
    Stream #0:0 (h264) -> crop
  
    Stream #0:0 (h264) -> overlay:main
  
    overlay -> Stream #0:0 (libx264)
  
  Press [q] to stop, [?] for help
  
  [libx264 @ 0x27b2ca0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
  
  [libx264 @ 0x27b2ca0] profile High, level 3.1
  
  [libx264 @ 0x27b2ca0] 264 - core 148 r2643 5c65704 - H.264/MPEG-4 AVC codec - Copyleft 2003-2015 - http://www.videolan.org/x264.html - options: cabac=1 ref=5 deblock=1:0:0 analyse=0x3:0x113 me=umh subme=8 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=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=2 b_bias=0 direct=3 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=50 rc=abr mbtree=1 bitrate=1024 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  Output #0, mp4, to '/home/cmaier/out.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf57.76.100
  
      Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv420p, 768x480, q=-1--1, 1024 kb/s, 30 fps, 15360 tbn, 30 tbc (default)
  
      Metadata:
  
        encoder         : Lavc57.102.100 libx264
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/1024000 buffer size: 0 vbv_delay: -1
  
  [mp4 @ 0x27b5a60] Starting second pass: moving the moov atom to the beginning of the file3.9x    
  
  frame= 9000 fps=117 q=-1.0 Lsize=   37827kB time=00:04:59.90 bitrate=1033.3kbits/s speed= 3.9x    
  
  video:37721kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.282333%
  
  [libx264 @ 0x27b2ca0] frame I:36    Avg QP:15.21  size: 50944
  
  [libx264 @ 0x27b2ca0] frame P:2723  Avg QP:20.12  size:  9593
  
  [libx264 @ 0x27b2ca0] frame B:6241  Avg QP:24.23  size:  1710
  
  [libx264 @ 0x27b2ca0] consecutive B-frames:  3.6%  6.9% 14.5% 75.0%
  
  [libx264 @ 0x27b2ca0] mb I  I16..4: 17.3% 58.5% 24.2%
  
  [libx264 @ 0x27b2ca0] mb P  I16..4:  0.5%  4.4%  0.9%  P16..4: 31.1% 20.7% 12.1%  0.0%  0.0%    skip:30.3%
  
  [libx264 @ 0x27b2ca0] mb B  I16..4:  0.0%  0.3%  0.1%  B16..8: 28.9%  5.5%  1.1%  direct: 1.1%  skip:63.1%  L0:37.5% L1:52.6% BI: 9.9%
  
  [libx264 @ 0x27b2ca0] final ratefactor: 19.69
  
  [libx264 @ 0x27b2ca0] 8x8 transform intra:72.8% inter:68.3%
  
  [libx264 @ 0x27b2ca0] direct mvs  spatial:99.9% temporal:0.1%
  
  [libx264 @ 0x27b2ca0] coded y,uvDC,uvAC intra: 74.5% 73.0% 30.4% inter: 13.0% 10.7% 0.2%
  
  [libx264 @ 0x27b2ca0] i16 v,h,dc,p: 49% 30%  3% 17%
  
  [libx264 @ 0x27b2ca0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu:  7% 14% 11%  7% 11%  8% 19%  8% 15%
  
  [libx264 @ 0x27b2ca0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu:  9% 13%  5%  8% 14% 10% 17%  9% 16%
  
  [libx264 @ 0x27b2ca0] i8c dc,h,v,p: 42% 29% 15% 15%
  
  [libx264 @ 0x27b2ca0] Weighted P-Frames: Y:7.4% UV:2.9%
  
  [libx264 @ 0x27b2ca0] ref P L0: 59.2% 20.2% 11.5%  3.7%  4.3%  1.0%  0.1%
  
  [libx264 @ 0x27b2ca0] ref B L0: 87.5%  8.8%  2.7%  1.0%
  
  [libx264 @ 0x27b2ca0] ref B L1: 96.5%  3.5%
  
  [libx264 @ 0x27b2ca0] kb/s:1030.01

  ---

  On ffmpeg version N-93862-gf49cec2 (Ubuntu 18.04), the command fails immediately.

  # ffmpeg -ss 60 -i ~/test.mp4 -y -filter_complex "[0:v]scale=-2:'min(320,ih)'[vs0];[vs0]crop=in_w/9:in_h/2:0:0,boxblur=5:1:cr=3:ar=3[b0];[vs0]crop=in_w/9:in_h/2:in_w-out_w:0,boxblur=5:1:cr=3:ar=3[b1];[vs0]crop=(in_w-2*in_w/9):in_h/20:in_w/9:0,boxblur=5:1:cr=3:ar=3[b2];[vs0][b0]overlay=0:0[ovr0];[ovr0][b1]overlay=main_w-overlay_w:0[ovr1];[ovr1][b2]overlay=main_w/9:0[vs1]" -map [vs1] -an -ac 2 -b:a 128k -acodec aac -b:v 1024k -r 30 -vcodec libx264 -t 300 -y -preset slow -movflags faststart -pix_fmt yuv420p -f mp4 ~/out.mp4
  
  ffmpeg version N-93862-gf49cec2 Copyright (c) 2000-2019 the FFmpeg developers
  
    built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04)
  
    configuration: --prefix=/root/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/root/ffmpeg_build/include --extra-ldflags=-L/root/ffmpeg_build/lib --bindir=/root/bin --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-openssl --enable-nonfree
  
    libavutil      56. 27.100 / 56. 27.100
  
    libavcodec     58. 52.101 / 58. 52.101
  
    libavformat    58. 27.103 / 58. 27.103
  
    libavdevice    58.  7.100 / 58.  7.100
  
    libavfilter     7. 53.100 /  7. 53.100
  
    libswscale      5.  4.101 /  5.  4.101
  
    libswresample   3.  4.100 /  3.  4.100
  
    libpostproc    55.  4.100 / 55.  4.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/root/test.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf57.76.100
  
    Duration: 00:10:00.00, start: 0.000000, bitrate: 1036 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 768x480, 1033 kb/s, 30 fps, 30 tbr, 15360 tbn, 60 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 0x56055a5902c0] Invalid stream specifier: vs0.
  
      Last message repeated 1 times
  
  Stream specifier 'vs0' in filtergraph description [0:v]scale=-2:'min(320,ih)'[vs0];[vs0]crop=in_w/9:in_h/2:0:0,boxblur=5:1:cr=3:ar=3[b0];[vs0]crop=in_w/9:in_h/2:in_w-out_w:0,boxblur=5:1:cr=3:ar=3[b1];[vs0]crop=(in_w-2*in_w/9):in_h/20:in_w/9:0,boxblur=5:1:cr=3:ar=3[b2];[vs0][b0]overlay=0:0[ovr0];[ovr0][b1]overlay=main_w-overlay_w:0[ovr1];[ovr1][b2]overlay=main_w/9:0[vs1] matches no streams.

• Easily track Events within Matomo Analytics thanks to Matomo Tag Manager

  7 juin 2019, par Matomo Core Team — Analytics Tips

  Easily track Events within Matomo Analytics thanks to Matomo Tag Manager

  Introduction

  In this article we’ll cover what events in Matomo Analytics are ; and how you can easily set them up thanks to Matomo Tag Manager.

  Key concepts within this article

  • Events
  • Quick definition of the Tag Management System
  • Matomo config
  • Creating triggers
  • Variables

  What are events in Matomo Analytics and why are they useful ?

  Events allow you to measure interactions on your website which are not defined by default. With them you can measure clicks on some elements of a page, such as, how visitors are interacting with dropdown menus, media players, scrolling behaviours etc. You can also use them to define goals which make them a key feature in Matomo Analytics. Learn more about tracking events in Matomo.

  You can easily access the Events report in Matomo Analytics by clicking on the Behaviour category :

  

  And you may read the following message and feel a bit frustrated :

  

  “There is no data for this report” is a nice way to say, “Hey, you are tracking just a tiny part of what Matomo Analytics can do for you.”

  Matomo is a great software, but it can’t guess what you want to track.

  In order for Matomo to register those event tracking interactions, you’ll need to explain it by adding a line of code similar to this one when the interaction happens :

   

  _paq.push(['trackEvent', 'Here you enter whatever you want', 'Here too', 'and here also']);

   

  Let’s imagine you want to track a click on an HTML button, your code will look something similar to this at the moment of the interaction :

  Click Me !

  As you can imagine, two main challenges will arise for non developers :

  1. How to access the source code ?
  2. How to define the interaction ?

  Luckily, Matomo Tag Manager makes those steps easy for you. Let’s see how the same tracking is implemented with Matomo Tag Manager.

  A quick definition of what Matomo Tag Manager is

  Matomo Tag Manager lets you manage all your tracking and marketing tags in one easy-to-access place. Please visit this page to learn more about Matomo Tag Manager. In order to start using it, you’ll need to copy/paste a tracking code, named a “container”, within the section of your pages.

  Once the container is on your website, all you need to do is to follow these simple steps :

  1. Add a Matomo Tag.
  2. Assign the condition to fire the tag (what we call the trigger).
  3. Publish your work.
  4. And enjoy

  1 – Add a Matomo Event tracking code

  All you have to do here is click on “CREATE NEW TAG”

  

  Once selected, just mention how you’d like this tag to be named (it is for your internal purpose here so always use an explicit tag name) and the Matomo configuration (the default configuration setting will be fine in most of the cases) :

  

  Then Matomo Tag Manager will ask you the type of tracking you’d like to deploy, in this case, this is an event so select “Event” :

  

  Then all you need is to indicate the values you’d like to push through your event :

  

  To put it in perspective, all we did here through Matomo Tag Manager was implement the equivalent of the following line of code :

  _paq.push(['trackEvent', 'Element interactions', 'Click button', 'Click Me']);

  Let’s now see how can we do this on click code part which we call a trigger.

  2 – Assign the condition to fire the tag

  In order to execute the event we’ll need to define when it will happen. You do this by clicking on Create a new trigger now :

  

  As the interaction we’d like to track is happening when a click occurs, it will be a click trigger, and as our button is not a link, we’ll select All Elements Click :

  

  Once selected you’ll need to be precise on the condition in which the event will be triggered. In this case we do not want to have events pushed every time someone is clicking on something on our website. We only want to track when they click on this specific button. That’s the reason why our trigger is set to fire only when the click occurs on an element which has an id and has the value “cta” :

  Once you click on the green button named CREATE NEW TRIGGER, you validate the tag by clicking on CREATE NEW TAG :

  

  

  Then you can move to the last part.

  3 – Publish your work

  Tag Managers are very powerful as they allow you to easily execute any JavaScript code, CSS or even text content on your websites.

  That’s why when you create your tag it doesn’t go live straight away on your website. In order to do this you need to publish your tag and this is what the “Publish” category is designed for :

  

  After that, click on the second button if you’re confident your tag and trigger are both ready to go live :

  

  4 – Enjoy

  Well done. As your tag is now live, every click made on this button will now be pushed to your Matomo Analytics account within :
  

  1. The visitor log report :

  

  2. The events report :

  

  You may now be asking, “That’s great, but can I collect something more exciting than clicks ?” 

  Of course you can ! This is what the Matomo Tag Manager is all about.

  As long as you can express it through a trigger you can really push whatever you want to Matomo Analytics. You can track scrolling patterns, an element visible on the page like an image, an ad or the time spent on the page. The options are now open to you with Tag Manager.

  Give them a try ! Change the triggers, start playing around with variables and discover that the possibilities are endless.

  Happy analytics,
  Matomo team