Recherche avancée

Sur d’autres sites (5742)

• Appending a list of movies MP4s causes the sound to be dropped or garbled at some point

  9 février 2020, par Marie

  Update I am able to reproduce the issue by concatenating 10 Hello.mp4 clips and see the audio drop out/garbled at about 5 seconds playback. This is via VLC latest 3.0.8 on Windows7 64bit. Window Player zero sound. Media Player Classic it plays fine all 10 audio or the word "Hello". The same movie when dragged onto Whatsapp the PC app plays OK but no sound if played from the Phone Whatsapp. Perhaps its my computer too slow in the production of this clip ??? I don’t know what to trust anymore.

  I copied the same ffmpeg.exe onto my kid’s Windows10 laptop and was able to produce the same behavior with sound dropping out with VLC however Windows10 media player is able to play the audio without a glitch.

  You can reproduce the same on your end with this batch file

  _HELLO_MP4s.CMD

  rem 2:07 AM 2/8/2020
  
  rem 
  
  rem  
  
  SET EXE="S:\_BINS\FFmpeg 4.2.1 20200112\bin\ffmpeg.exe"
  
  
  
  SET ROOTPATH=.\
  
  
  
  SET OUT_FILE="%ROOTPATH%HELLOs.MP4"
  
  
  
  SET IN_FILES_LIST="%ROOTPATH%IN_FILES_LIST.TXT"
  
  ECHO file '%ROOTPATH%HELLO.mp4' > %IN_FILES_LIST% 
  
  ECHO file '%ROOTPATH%HELLO.mp4' >> %IN_FILES_LIST% 
  
  ECHO file '%ROOTPATH%HELLO.mp4' >> %IN_FILES_LIST% 
  
  ECHO file '%ROOTPATH%HELLO.mp4' >> %IN_FILES_LIST% 
  
  ECHO file '%ROOTPATH%HELLO.mp4' >> %IN_FILES_LIST% 
  
  ECHO file '%ROOTPATH%HELLO.mp4' >> %IN_FILES_LIST% 
  
  ECHO file '%ROOTPATH%HELLO.mp4' >> %IN_FILES_LIST% 
  
  ECHO file '%ROOTPATH%HELLO.mp4' >> %IN_FILES_LIST% 
  
  ECHO file '%ROOTPATH%HELLO.mp4' >> %IN_FILES_LIST% 
  
  ECHO file '%ROOTPATH%HELLO.mp4' >> %IN_FILES_LIST% 
  
  
  
  SET OPTIONS= -f concat -safe 0 -i  %IN_FILES_LIST%  -c copy -y  %OUT_FILE%
  
  
  
  SET INFO_FILE="INFO.TXT"
  
  
  
  %EXE% %OPTIONS%  1> %INFO_FILE% 2>&1 
  
  
  
  ECHO ======================== >> %INFO_FILE% 
  
  ECHO OUT_FILE=%OUT_FILE%  >> %INFO_FILE% 
  
  ECHO EXE=%EXE%  >> %INFO_FILE%
  
  ECHO OPTIONS=%OPTIONS%  >> %INFO_FILE% 
  
  ECHO ======================== >> %INFO_FILE%

  Original Post
  My process is in 3 steps
  Step 1) Corresponding to each bitmap I have 00.JPG ... NN.JPG I combine a list of "SOURCE" mp3 audio into a single audio mp3 to produce matching 00.MP3 ... NN.MP3

  I had glitch here where one my mp3 was not of the correct Sample Rate, however a kind soul in this forum helped me fix that.
  You can read the details here :

  When I append a silent audio (mp3) to an existing list of audio it garbles the final audio ?

  Step 2) combine each mp3 from previous with a the filename matching bitmap to produce a movie .MP4

  IOW,

  • 00.JPG + 00.MP3 >> 00.MP4
  • 01.JPG + 01.MP3 >> 01.MP4
  • and so on

  From this run of 24 subparts, I hand tested some of these movies against Whatsapp and they are accepted fine.
  However, the final MOVIE.MP4 is not.
  I will list below their info from ffprobe.

  Step 3) combine the list of movies from previous into a final MOVIE.MP4
  This is where I have been having random issues typically with audio, currently this audio drops at about 20s from start. Corresponding to roughly movies parts 04.mp4 to 07.mp4

  I play the videos via VLC but Windows Media Player has even worse playback.

  I am able to reproduce Step3 and thus MOVIE.MP4 with following batch file

  rem 10:33 PM 2/6/2020
  
  SET EXE="S:\_BINS\FFmpeg 4.2.1 20200112\bin\ffmpeg.exe"
  
  
  
  SET ROOTPATH=.\
  
  
  
  SET OUT_FILE="%ROOTPATH%MOVIE.MP4"
  
  
  
  SET IN_FILES_LIST="%ROOTPATH%IN_FILES_LIST.TXT"
  
  
  
  SET OPTIONS= -f concat -safe 0 -i  %IN_FILES_LIST%  -c copy -y  %OUT_FILE%
  
  
  
  SET INFO_FILE="INFO.TXT"
  
  
  
  %EXE% %OPTIONS%  1> %INFO_FILE% 2>&1 
  
  
  
  rem PAUSE

  The content of IN_FILES_LIST.TXT

  file '00.mp4'
  
  file '01.mp4'
  
  file '02.mp4'
  
  ...
  
  file '23.mp4'
  
  file '24.mp4'

  (Step 2) uses the following :)
  

  The following is ffprobe on the source audio MP3s (Step 1)

  MP3s_ORIGINAL.TXT
  
  ========================BEGIN 
  
  [mp3 @ 0000000000513100] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, mp3, from '.\PLAY\00.mp3':
  
    Duration: 00:00:03.36, start: 0.000000, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  [mp3 @ 00000000003f3180] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, mp3, from '.\PLAY\01.mp3':
  
    Duration: 00:00:00.46, start: 0.000000, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  [mp3 @ 00000000004a3180] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, mp3, from '.\PLAY\02.mp3':
  
    Duration: 00:00:00.58, start: 0.000000, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  [mp3 @ 0000000000623180] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, mp3, from '.\PLAY\03.mp3':
  
    Duration: 00:00:00.84, start: 0.000000, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  [mp3 @ 00000000003a3180] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, mp3, from '.\PLAY\04.mp3':
  
    Duration: 00:00:00.86, start: 0.000000, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  [mp3 @ 0000000000433180] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, mp3, from '.\PLAY\05.mp3':
  
    Duration: 00:00:00.98, start: 0.000000, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  [mp3 @ 0000000000683180] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, mp3, from '.\PLAY\06.mp3':
  
    Duration: 00:00:00.98, start: 0.000000, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  [mp3 @ 00000000004d3180] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, mp3, from '.\PLAY\07.mp3':
  
    Duration: 00:00:00.98, start: 0.000000, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  [mp3 @ 00000000004c3180] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, mp3, from '.\PLAY\08.mp3':
  
    Duration: 00:00:00.98, start: 0.000000, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  [mp3 @ 0000000000573180] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, mp3, from '.\PLAY\09.mp3':
  
    Duration: 00:00:00.98, start: 0.000000, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  [mp3 @ 0000000000583180] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, mp3, from '.\PLAY\10.mp3':
  
    Duration: 00:00:00.98, start: 0.000000, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  [mp3 @ 00000000005e3180] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, mp3, from '.\PLAY\11.mp3':
  
    Duration: 00:00:00.98, start: 0.000000, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  [mp3 @ 0000000000553180] Estimating duration from bitrate, this may be inaccurate
  
  Input #0, mp3, from '.\PLAY\12.mp3':
  
    Duration: 00:00:00.98, start: 0.000000, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  [mp3 @ 0000000000563180] Estimating duration from bitrate, this may be inaccurate
  
  
  
  
  
  trimmed because SO limits post to 30000 chars

  The following is ffprobe on the MP3s concatenated with 2second Silence. All their Sample Rate 24K and Bit Rate 32k seems OK ?? (Also Step 1)

  MP3s_withSilenceAppended.TXT
  
  ========================BEGIN 
  
  Input #0, mp3, from '00.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:05.42, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '01.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:02.52, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '02.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:02.64, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '03.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:02.90, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '04.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:02.93, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '05.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.05, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '06.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.05, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '07.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.05, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '08.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.05, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '09.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.05, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '10.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.05, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '11.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.05, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '12.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.05, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '13.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:05.81, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '14.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:02.93, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '15.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:02.66, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '16.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:02.66, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '17.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:02.66, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '18.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:02.83, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '19.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:06.50, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '20.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.05, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '21.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.05, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '22.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.14, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '23.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:06.12, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s
  
  Input #0, mp3, from '24.mp3':
  
    Metadata:
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.14, start: 0.046042, bitrate: 32 kb/s
  
      Stream #0:0: Audio: mp3, 24000 Hz, mono, fltp, 32 kb/s

  The following is ffmpeg info output during the production of final movie MOVIE.MP4
  (Step 3)

  ========================BEGIN 
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\00.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:05.54, start: 0.000000, bitrate: 174 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 137 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\01.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:02.71, start: 0.000000, bitrate: 269 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 242 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\02.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:02.71, start: 0.000000, bitrate: 285 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 245 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\03.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.04, start: 0.000000, bitrate: 275 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 239 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\04.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.04, start: 0.000000, bitrate: 286 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 250 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\05.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.21, start: 0.000000, bitrate: 281 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 249 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\06.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.21, start: 0.000000, bitrate: 281 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 249 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\07.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.21, start: 0.000000, bitrate: 150 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 115 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\08.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.21, start: 0.000000, bitrate: 201 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 166 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\09.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.21, start: 0.000000, bitrate: 247 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 214 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\10.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.21, start: 0.000000, bitrate: 247 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 214 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\11.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.21, start: 0.000000, bitrate: 131 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 95 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\12.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.21, start: 0.000000, bitrate: 194 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 159 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\13.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:05.88, start: 0.000000, bitrate: 207 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 169 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\14.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.04, start: 0.000000, bitrate: 335 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 300 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\15.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:02.88, start: 0.000000, bitrate: 365 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 342 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\16.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:02.88, start: 0.000000, bitrate: 384 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 362 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\17.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:02.88, start: 0.000000, bitrate: 390 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 368 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\18.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.04, start: 0.000000, bitrate: 386 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 363 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\19.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:06.71, start: 0.000000, bitrate: 204 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 169 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\20.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.21, start: 0.000000, bitrate: 194 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 159 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\21.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.21, start: 0.000000, bitrate: 194 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 159 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\22.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.21, start: 0.000000, bitrate: 208 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 169 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\23.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:06.21, start: 0.000000, bitrate: 204 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 166 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\24.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:00:03.21, start: 0.000000, bitrate: 173 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 134 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 32 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '\VID\MOVIE.mp4':
  
    Metadata:
  
      major_brand     : isom
  
      minor_version   : 512
  
      compatible_brands: isomiso2avc1mp41
  
      encoder         : Lavf58.35.101
  
    Duration: 00:01:29.05, start: 0.000000, bitrate: 239 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 203 kb/s, 23.53 fps, 24 tbr, 24k tbn, 48 tbc (default)
  
      Metadata:
  
        handler_name    : VideoHandler
  
      Stream #0:1(und): Audio: mp3 (mp4a / 0x6134706D), 24000 Hz, mono, fltp, 30 kb/s (default)
  
      Metadata:
  
        handler_name    : SoundHandler

  I have not been able yet to reproduce the issue with a smaller set of movies, in the meantime if you would to get a copy I would have to upload an archive to a link so you can have them on your side.

  Alternatively, if you would like me to provide additional info from these steps let me know what commands and I will be happy to provide.

  Thank you.

• A Guide to Ethical Web Analytics in 2024

  17 juin 2024, par Erin

  User data is more valuable and sought after than ever. 

  Ninety-four percent of respondents in Cisco’s Data Privacy Benchmark Study said their customers wouldn’t buy from them if their data weren’t protected, with 95% saying privacy was a business imperative. 

  Unfortunately, the data collection practices of most businesses are far from acceptable and often put their customers’ privacy at risk. 

  But it doesn’t have to be this way. You can ethically collect valuable and insightful customer data—you just need the right tools.

  In this article, we show you what an ethical web analytics solution can look like, why Google Analytics is a problem and how you can collect data without risking your customers’ privacy.

  What is ethical web analytics ?

  Ethical web analytics put user privacy first. These platforms prioritise privacy and transparency by only collecting necessary data, avoiding implicit user identification and openly communicating data practices and tracking methods. 

  Ethical tools adhere to data protection laws like GDPR as standard (meaning businesses using these tools never have to worry about fines or disruptions). In other words, ethical web analytics refrain from exploiting and profiting from user behaviour and data. 

  Unfortunately, most traditional data solutions collect as much data as possible without users’ knowledge or consent.

  Why does digital privacy matter ?

  Digital privacy matters because companies have repeatedly proven they will collect and use data for financial gain. It also presents security risks. Unsecured user data can lead to identity theft, cyberattacks and harassment. 

  Big tech companies like Google and Meta are often to blame for all this. These companies collect millions of user data points — like age, gender, income, political beliefs and location. Worse still, they share this information with interested third parties.

  After public outrage over data breaches and other privacy scandals, consumers are taking active steps to disallow tracking where possible. IAPP’s Privacy and Consumer Trust Report finds that 68% of consumers across 19 countries are somewhat or very concerned about their digital privacy. 

  There’s no way around it : companies of all sizes and shapes need to consider how they handle and protect customers’ private information. 

  Why should you use an ethical web analytics tool ?

  When companies use ethical web analytics tools they can build customer trust, boost their brand reputation, improve data security practices and future proof their website tracking solution. 

  Boost brand reputation

  The fallout from a data privacy scandal can be severe. 

  Just look at what happened to Facebook during the Cambridge Analytica data scandal. The eponymous consulting firm harvested 50 million Facebook profiles and used that information to target people with political messages. Due to the instant public backlash, Facebook’s stock tanked, and use of the “delete Facebook” hashtag increased by 423% in the following days.

  That’s because consumers care about data privacy, according to Deloitte’s Connected Consumer Study :

  • Almost 90 percent agree they should be able to view and delete data companies collect 
  • 77 percent want the government to introduce stricter regulations
  • Half feel the benefits they get from online services outweigh data privacy concerns.

  If you can prove you buck the trend by collecting data using ethical methods, it can boost your brand’s reputation. 

  Build trust with customers

  At the same time, collecting data in an ethical way can help you build customer trust. You’ll go a long way to changing consumer perceptions, too. Almost half of consumers don’t like sharing data, and 57% believe companies sell their data. 

  This additional trust should generate a positive ROI for your business. According to Cisco’s Data Privacy Benchmark Study, the average company gains $180 for every $100 they invest in privacy. 

  Improve data security

  According to IBM’s Cost of a Data Breach report, the average cost of a data breach is nearly $4.5 million. This kind of scenario becomes much less likely when you use an ethical tool that collects less data overall and anonymises the data you do collect. 

  Futureproof your web analytics solution

  The obvious risk of not complying with privacy regulations is a fine — which can be up to €20 million, or 4% of worldwide annual revenue in the case of GDPR.

  It’s not just fines and penalties you risk if you fail to comply with privacy regulations like GDPR. For some companies, especially larger ones, the biggest risk of non-compliance with privacy regulations is the potential sudden need to abandon Google Analytics and switch to an ethical alternative.

  If Data Protection Authorities ban Google Analytics again, as has happened in Austria, France, and other countries, businesses will be forced to drop everything and make an immediate transition to a compliant web analytics solution.

  When an organisation’s entire marketing operation relies on data, migrating to a new solution can be incredibly painful and time-consuming. So, the sooner you switch to an ethical tool, the less of a headache the process will be. 

  The problem with Google Analytics

  Google Analytics (GA) is the most popular analytics platform in the world, but it’s a world away from being an ethical tool. Here’s why :

  You don’t have data ownership

  Google Analytics is attractive to businesses of all sizes because of its price. Everyone loves getting something for free, but there’s still a cost — your and your customers’ data.

  That’s because Google combines the data you collect with information from the millions of other websites it tracks to inform its advertising efforts. It may also use your data to train large language models like Gemini. 

  It has a rocky history with GDPR laws

  Google and EU regulators haven’t always got along. For example, the German Data Protection Authority is investigating 200,000 pending cases against websites using GA. The platform has also been banned and added back to the EU-US Data Privacy Framework several times over the past few years. 

  You can use GA to collect data about EU customers right now, but there’s no guarantee you’ll be able to do so in the future. 

  It requires a specific setup to remain compliant

  While you can currently use GA in a GDPR-compliant way — owing to its inclusion in the EU-US Data Privacy Framework — you have to set it up in a very specific way. That’s because the platform’s compliance depends on what data you collect, how you inform users and the level of consent you acquire. You’ll still need to include an extensive privacy policy on your website. 

  What does ethical web analytics look like ?

  An ethical web analytics solution should put user privacy first, ensure compliance with regulations like GDPR, give businesses 100% control of the data they collect and be completely transparent about data collection and storage practices. 

  

  100% data ownership

  You don’t fully control customer data when you use Google Analytics. The search giant uses your data for its own advertising purposes and may also use it to train large language models like Gemini. 

  When you choose an ethical web analytics alternative like Matomo, you can ensure you completely own your data.

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  Respects user privacy

  It’s possible to track and measure user behaviour without collecting personally identifiable information (PII). Just look at the ethical web analytics tools we’ve reviewed below. 

  These platforms respect user privacy and conform to strict privacy regulations like GDPR, CCPA and HIPAA by incorporating some or all of the following features :

  • Opt-out mechanisms to let users refuse tracking
  • IP addresses anonymisation and other data anonymisation techniques
  • DoNotTrack options
  • Shorter expiration dates for tracking cookies

  In Matomo’s case, it’s all of the above. Better still, you can check our privacy credentials yourself. Our software’s source code is open source on GitHub and accessible to anyone at any time. 

  Compliant with government regulations

  While Google’s history with data regulations is tumultuous, an ethical web analytics platform should follow even the strictest privacy laws, including GDPR, HIPAA, CCPA, LGPD and PECR.

  But why stop there ? Matomo has been approved by the French Data Protection Authority (CNIL) as one of the few web analytics tools that French sites can use to collect data without tracking consent. So you don’t need an annoying consent banner popping up on your website anymore. 

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  Complete transparency 

  Ethical web analytics tools will be upfront about their data collection practices, whether that’s in the U.S., EU, or on your own private servers. Look for a solution that refrains from collecting personally identifiable information, shows where data is stored, and lets you alter tracking methods to increase privacy even further. 

  Some solutions, like Matomo, will increase transparency further by providing open source software. Anyone can find our source code on GitHub to see exactly how our platform tracks and stores user data. This means our code is regularly examined and reviewed by a community of developers, making it more secure, too.

  Ethical web analytics solutions

  There are several options for an ethical web analytics tool. We list three of the best providers below. 

  Matomo

  Matomo is an open source web analytics tool and privacy-focused Google Analytics alternative used by over one million sites globally. 

  

  Matomo is fully compliant with prominent global privacy regulations like GDPR, CCPA and HIPAA, meaning you never have to worry about collecting consent when tracking user behaviour. 

  The data you collect is completely accurate since Matomo doesn’t use data sampling and is 100% yours. We don’t share data with third parties but can prove it. Our product source code is publicly available on GitHub. As a community-led project, you can download and install it yourself for free. 

  With Matomo, you get a full range of web analytics capabilities and behavioural analytics. That includes your standard metrics (think visitors, traffic sources, bounce rates, etc.), advanced features to analyse user behaviour like A/B Testing, Form Analytics, Heatmaps and Session Recordings. 

  Migrating to Matomo is easy. You can even import historical Google Analytics data to generate meaningful insights immediately. 

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  Fathom

  Fathom Analytics is a lightweight privacy-focused analytics solution that launched in 2018. It aims to be an easy-to-use Google Analytics alternative that doesn’t compromise privacy. 

  

  Like Matomo, Fathom complies with all major privacy regulations, including GDPR and CCPA. It also provides 100% accurate, unsampled reports and doesn’t share your data with third parties. 

  While Fathom provides fairly comprehensive analytics reports, it doesn’t have some of Matomo’s more advanced features. That includes e-commerce tracking, heatmaps, session recordings, and more. 

  Plausible

  Plausible Analytics is another open source Google Analytics alternative that was built and hosted in the EU. 

  

  Launched in 2019, Plausible is a newer player in the privacy-focused analytics market. Still, its ultra-lightweight script makes it an attractive option for organisations that prioritise speed over everything else. 

  Like Matomo and Fathom, Plausible is GDPR and CCPA-compliant by design. Nor is there any cap on the amount of data you collect or any debate over whether the data is accurate (Plausible doesn’t use data sampling) or who owns the data (you do). 

  Matomo makes it easy to migrate to an ethical web analytics alternative

  There’s no reason to put your users’ privacy at risk, especially when there are so many benefits to choosing an ethical tool. Whether you want to avoid fines, build trust with your customers, or simply know you’re doing the right thing, choosing a privacy-focused, ethical solution like Matomo is taking a massive step in the right direction. 

  Making the switch is easy, too. Matomo is one of the few options that lets you import historical Google Analytics data, so starting from scratch is unnecessary. 

  Get started today by trying Matomo for free for 21-days. No credit card required. 

  Try Matomo for Free

  21 day free trial. No credit card required.

  
  

  Your email address
  

  Your website address
  

  Your Analytics subdomain will be .matomo.cloud (change)

  Choose your analytics subdomain
  

  .matomo.cloud

  I accept the terms and conditions and data processing agreement (DPA)

  
  Your information will be used to create an account on our cloud service. For more information please consult our privacy policy.
  
  
  

  Start improving your websites now

  

• Data Privacy Regulations : Essential Knowledge for Global Business

  6 mars, par Daniel Crough

  If you run a website that collects visitors’ data, you might be violating privacy regulations somewhere in the world. At last count, over 160 countries have privacy laws — and your customers in those countries know about them.

  A recent survey found that 53% of people who answered know about privacy rules in their country and want to follow them. This is up from 46% two years ago. Furthermore, customers increasingly want to buy from businesses they can trust with their data.

  That’s why businesses must take data privacy seriously. In this article, we’ll first examine data privacy rules, why we need them, and how they are enforced worldwide. Finally, we’ll explore strategies to ensure compliance and tools that can help.

  What are data privacy regulations ?

  Let’s first consider data privacy. What is it ? The short answer is individuals’ ability to control their personal information. That’s why we need laws and rules to let people decide how their data is collected, used, and shared. Crucially, the laws empower individuals to withdraw permission to use their data anytime.

  The UNCTAD reports that only 13 countries had data protection laws or rules before the 2000s. Many existed before businesses could offer online services, so they needed updating. Today, 162 national laws protect data privacy, half of which emerged in the last decade.

  Why is this regulation necessary ?

  There are many reasons, but the impetus comes from consumers who want their governments to protect their data from exploitation. They understand that participating in the digital economy means sharing personal information like email addresses and telephone numbers, but they want to minimise the risks of doing so.

  Data privacy regulation is essential for :

  • Protecting personal information from exploitation with transparent rules and guidelines on handling it securely.
  • Implementing adequate security measures to prevent data breaches.
  • Enforcing accountability for how data is collected, stored and processed.
  • Giving consumers control over their data.
  • Controlling the flow of data across international borders in a way that fully complies with the regulations.
  • Penalising companies that violate privacy laws.

  Isn’t it just needless red tape ?

  Data breaches in recent years have been one of the biggest instigators of the increase in data privacy regulations. A list of the top ten data breaches illustrates the point.

  #	Company	Location	Year	# of Records	Data Type
  1	Yahoo	Global	2013	3B	user account information
  2	Aadhaar	India	2018	1.1B	citizens’ ID/biometric data
  2	Alibaba	China	2019	1.1B	users’ personal data
  4	LinkedIn	Global	2021	700M	users’ personal data
  5	Sina Weibo	China	2020	538M	users’ personal data
  6	Facebook	Global	2019	533M	users’ personal data
  7	Marriott Int’l	Global	2018	500M	customers’ personal data
  8	Yahoo	Global	2014	500M	user account information
  9	Adult Friend Finder	Global	2016	412.2M	user account information
  10	MySpace	USA	2013	360M	user account information

  And that’s just the tip of the iceberg. Between November 2005 and November 2015, the US-based Identity Theft Resource Center counted 5,754 data breaches that exposed 856,548,312 records, mainly in that country.

  It’s no wonder that citizens worldwide want organisations they share their personal data with to protect that data as if it were their own. More specifically, they want their governments to :

  • Protect their consumer rights
  • Prevent identity theft and other consumer fraud
  • Build trust between consumers and businesses
  • Improve cybersecurity measures
  • Promote ethical business practices
  • Uphold international standards

  Organisations using personal data in their operations want to minimise financial and reputational risk. That’s common sense, especially when external attacks cause 68% of data breaches.

  The terminology of data privacy

  With 162 national laws already in place, the legal space surrounding data privacy grows more complex every day. Michalsons has a list of different privacy laws and regulations in force in significant markets around the world.

  Fortunately, there’s plenty of commonality for two reasons : first, all countries want to solve the same problem ; second, those drafting the legislation have adopted much of what other countries have already developed. As a result, the terminology remains almost the same, even when the language changes.

  These are the core concepts at play :

  Term	Definition
  Access and control	Consumers can access, review, edit and delete their data
  Data protection	Organisations must protect data from being stolen or compromised
  Consumer consent	Consumers can grant and withdraw or refuse access to their data
  Deletion	Consumers can request to have their data erased
  Data breach	When the security of data has been compromised
  Data governance	The management of data within an organisation
  Double opt-in	Two-factor authentication to add a layer of confirmation
  GDPR	Governing data privacy in Europe since 2016
  Personally identifiable information (PII)	Data used to identify, locate, or contact an individual
  Pseudonymisation	Replace personal identifiers with artificial identifiers or pseudonyms
  Publicly available information	Data from official sources, without restrictions on access or use
  Rectification	Consumers can request to have errors in their data corrected

  Overview of current data privacy legislation

  Over three-quarters of the world has formulated and rolled out data privacy legislation — or is currently doing so. Here’s a breakdown of the laws and regulations you can expect to find in most significant markets worldwide.

  Europe

  Thoughts of protecting data privacy first occurred in Europe when the German government became concerned about automated data processing in 1970. A few years later, Sweden was the first country to enact a law requiring permits for processing personal data, establishing the first data protection authority.

  General Data Protection Regulation (GDPR)

  Sweden’s efforts triggered a succession of European laws and regulations that culminated in the European Union (EU) GDPR, enacted in 2016 and enforced from 25 May 2018. It’s a detailed and comprehensive privacy law that safeguards the personal data and privacy of EU citizens.

  The main objectives of GDPR are :

  • Strengthening the privacy rights of individuals by empowering them to control their data.
  • Establishing a uniform data framework for data privacy across the EU.
  • Improving transparency and accountability by mandating businesses to handle personal data responsibly and fully disclose how they use it.
  • Extending the regulation’s reach to organisations external to the EU that collect, store and process the data of EU residents.
  • Requiring organisations to conduct Protection Impact Assessments (PIAs) for “high-risk” projects.

  ePrivacy Regulation on Privacy and Electronic Communications (PECR)

  The second pillar of the EU’s strategy to regulate the personal data of its citizens is the ePrivacy Regulation on Privacy and Electronic Communications (EU PECR). Together with the GDPR, it will comprise data protection law in the union. This regulation applies to :

  • Providers of messaging services like WhatsApp, Facebook and Skype
  • Website owners
  • Owners of apps that have electronic communication components
  • Commercial direct marketers
  • Political parties sending promotional messages electronically
  • Telecommunications companies
  • ISPs and WiFi connection providers

  The EU PECR was intended to commence with GDPR on 25 May 2018. That didn’t happen, and as of January 2025, it was in the process of being redrafted.

  EU Data Act

  One class of data isn’t covered by GDPR or PECR : internet product-generated data. The EU Data Act provides the regulatory framework to govern this data, and it applies to manufacturers, suppliers, and users of IoT devices or related services.

  The intention is to facilitate data sharing, use, and reuse and to facilitate organisations’ switching to a different cloud service provider. The EU Data Act entered into force on 11 January 2024 and is applicable from September 2025.

  GDPR UK

  Before Brexit, the EU GDPR was in force in the UK. After Brexit in 2020, the UK opted to retain the regulations as UK GDPR but asserted independence to keep the framework under review. It’s part of a wider package of reform to the data protection environment that includes the Data Protection Act 2018 and the UK PECR.

  In the USA

  The primary federal law regarding data privacy in the US is the Privacy Act of 1974, which has been in revision for some time. However, rather than wait for the outcome of that process, many business sectors and states have implemented their own measures.

  Sector-specific data protection laws

  This sectoral approach to data protection relies on a combination of legislation, regulation and self-regulation rather than governmental control. Since the mid-1990s, the country has allowed the private sector to lead on data protection, resulting in ad hoc legislation arising when circumstances require it. Examples include the Video Privacy Protection Act of 1988, the Cable Television Protection and Competition Act of 1992 and the Fair Credit Reporting Act.

  

  California Consumer Privacy Act (CCPA)

  California was the first state to act when federal privacy law development stalled. In 2018, it enacted the California Consumer Privacy Act (CCPA) to protect and enforce Californians’ rights regarding the privacy of their personal information. It came into force in 2020.

  California Privacy Act (CPRA)

  In November of that same year, California voters approved the California Privacy Rights Act (CPRA). Billed as the strongest consumer privacy law ever enacted in the US, CPRA works with CCPA and adds the best elements of laws and regulations in other jurisdictions (Europe, Japan, Israel, New Zealand, Canada, etc.) into California’s personal data protection regime.

  Virginia Consumer Data Protection Act (CDPA)

  In March 2021, Virginia became the next US state to implement privacy legislation. The Virginia Consumer Data Protection Act (VCDPA), which is also informed by global legislative developments, tries to strike a balance between consumer privacy protections and business interests. It governs how businesses collect, use, and share consumer data.

  Colorado Privacy Act (CPA)

  Developed around the same time as VCDPA, the Colorado Privacy Act (CPA) was informed by that law and GDPR and CCPA. Signed into law in July 2021, the CPA gives Colorado residents more control over their data and establishes guidelines for businesses on handling the data.

  Other states generally

  Soon after, additional states followed suit and, similar to Colorado, examined existing legislation to inform the development of their own data privacy laws and regulations. At the time of writing, the states with data privacy laws at various stages of development were Connecticut, Florida, Indiana, Iowa, Montana, New York, Oregon, Tennessee, Texas, and Utah.

  By the time you read this article, more states may be doing it, and the efforts of some may have led to laws and regulations coming into force. If you’re already doing business or planning to do business in the US, you should do your own research on the home states of your customers.

  Globally

  Beyond Europe and the US, other countries are also implementing privacy regulations. Some were well ahead of the trend. For example, Chile’s Law on the Protection of Private Life was put on the books in 1999, while Mauritius enacted its first Data Protection Act in 2004 — a second one came along in 2017 to replace it.

  Canada

  The regulatory landscape around data privacy in Canada is as complicated as it is in the US. At a federal government level, there are two laws : The Privacy Act for public sector institutions and the Personal Information Protection and Electronic Documents Act (PIPEDA) for the private sector.

  PIPEDA is the one to consider here. Like all other data privacy policies, it provides a framework for organisations handling consumers’ personal data in Canada. Although not quite up to GDPR standard, there are moves afoot to close that gap.

  The Digital Charter Implementation Act, 2022 (aka Bill C-27) is proposed legislation introduced by federal agencies in June 2022. It’s intended to align Canada’s privacy framework with global standards, such as GDPR, and address emerging digital economy challenges. It may or may not have been finalised when you read this.

  At the provincial level, three of Canada’s provinces—Alberta, British Columbia, and Quebec—have introduced laws and regulations of their own. Their rationale was similar to that of Bill C-27, so they may become redundant if and when that bill passes.

  Japan

  Until recently, Japan’s Act on the Protection of Personal Information (APPI) was considered by many to be the most comprehensive data protection law in Asia. Initially introduced in 2003, it was significantly amended in 2020 to align with global privacy standards, such as GDPR.

  APPI sets out unambiguous rules for how businesses and organisations collect, use, and protect personal information. It also sets conditions for transferring the personal information of Japanese residents outside of Japan.

  

  China

  The new, at least for now, most comprehensive data privacy law in Asia is China’s Personal Information Protection Law (PIPL). It’s part of the country’s rapidly evolving data governance framework, alongside the Cybersecurity Law and the Data Security Law.

  PIPL came into effect in November 2021 and was informed by GDPR and Japan’s APPI, among others. The data protection regime establishes a framework for protecting personal information and imposes significant compliance obligations on businesses operating in China or targeting consumers in that country.

  Other countries

  Many other nations have already brought in legislation and regulations or are in the process of developing them. As mentioned earlier, there are 162 of them at this point, and they include :

  Argentina	Costa Rica	Paraguay
  Australia	Ecuador	Peru
  Bahrain	Hong Kong	Saudi Arabia
  Bermuda	Israel	Singapore
  Brazil	Mauritius	South Africa
  Chile	Mexico	UAE
  Colombia	New Zealand	Uruguay

  Observant readers might have noticed that only two countries in Africa are on that list. More than half of the 55 countries on the continent have or are working on data privacy legislation.

  It’s a complex landscape

  Building a globalised business model has become very complicated, with so much legislation already in play and more coming. What you must do depends on the countries you plan to operate in or target. And that’s before you consider the agreements groups of countries have entered into to ease the flow of personal data between them.

  In this regard, the EU-US relationship is instructive. When GDPR came into force in 2016, so did the EU-US Privacy Shield. However, about four years later, the Court of Justice of the European Union (CJEU) invalidated it. The court ruled that the Privacy Shield didn’t adequately protect personal data transferred from the EU to the US.

  The ruling was based on US laws that allow excessive government surveillance of personal data transferred to the US. The CJEU found that this conflicted with the basic rights of EU citizens under the European Union’s Charter of Fundamental Rights.

  A replacement was negotiated in a new mechanism : the EU-US Data Privacy Framework. However, legal challenges are expected, and its long-term viability is uncertain. The APEC Privacy Framework and the OECD Privacy Framework, both involving the US, also exist.

  

  Penalties for non-compliance

  Whichever way you look at it, consumer data privacy laws and regulations make sense. But what’s really interesting is that many of them have real teeth to punish offenders. GDPR is a great example. It was largely an EU concern until January 2022 when the French data protection regulator hit Google and Facebook with serious fines and criminal penalties.

  Google was fined €150M, and Facebook was told to pay €60M for failing to allow French users to reject cookie tracking technology easily. That started a tsunami of ever-larger fines.

  The largest so far was the €1.2B fine levied by the Irish Data Protection Commission on Meta, the owner of Instagram, Facebook, and WhatsApp. It was issued for transferring European users’ personal data to the US without adequate data protection mechanisms. This significant penalty demonstrated the serious financial implications of non-compliance.

  These penalties follow a structured approach rather than arbitrary determinations. The GDPR defines an unambiguous framework for fines. They can be up to 4% of a company’s total global turnover in the previous fiscal year. That’s a serious business threat.

  What should you do ?

  For businesses committed to long-term success, accepting and adapting to regulatory requirements is essential. Data privacy regulations and protection impact assessments are here to stay, with many national governments implementing similar frameworks.

  However, there is some good news. As you’ve seen, many of these laws and regulations were informed by GDPR or retrospectively aligned. That’s a good place to start. Choose tools to handle your customer’s data that are natively GDPR-compliant.

  For example, web analytics is all about data, and a lot of that data is personal. And if, like many people, you use Google Analytics 4, you’re already in trouble because it’s not GDPR-compliant by default. And achieving compliance requires significant additional configuration.

  A better option would be to choose a web analytics platform that is compliant with GDPR right off the bat. Something like Matomo would do the trick. Then, complying with any of the tweaks individual countries have made to the basic GDPR framework will be a lot easier—and may even be handled for you.

  Privacy-centric data strategies

  Effective website data analysis is essential for business success. It enables organisations to understand customer needs and improve service delivery.

  But that data doesn’t necessarily need to be tied to their identity — and that’s at the root of many of these regulations.

  It’s not to stop companies from collecting data but to encourage and enforce responsible and ethical handling of that data. Without an official privacy policy or ethical data collection practices, the temptation for some to use and abuse that data for financial gain seems too great to resist.

  

  Cookie usage and compliance

  There was a time when cookies were the only way to collect reliable information about your customers and prospects. But under GDPR, and in many countries that based or aligned their laws with GDPR, businesses have to give users an easy way to opt out of all tracking, particularly tracking cookies.

  So, how do you collect the information you need without cookies ? Easy. You use a web analytics platform that doesn’t depend wholly on cookies. For example, in certain countries and when configured for maximum privacy, Matomo allows for cookieless operation. It can also help you manage the cookie consent requirements of various data privacy regulations.

  Choose the right tools

  Data privacy regulations have become a permanent feature of the global business landscape. As digital commerce continues to expand, these regulatory frameworks will only become more established. Fortunately, there is a practical approach forward.

  As mentioned several times, GDPR is considered by many countries to be a particularly good example of effective data privacy regulation. For that reason, many of them model their own legislation on the EU’s effort, making a few tweaks here and there to satisfy local requirements or anomalies.

  As a result, if you comply with GDPR, the chances are that you’ll also comply with many of the other data privacy regulations discussed here. That also means that you can select tools for your data harvesting and analytics that comply with the GDPR out of the box, so to speak. Tools like Matomo.

  Matomo lets website visitors retain full control over their data.

  Before deciding whether to go with Matomo On-premise or the EU-hosted cloud version, why not start your 21-day free trial ? No credit card required.