Recherche avancée

Sur d’autres sites (4368)

• Quick stream from file which exists

  4 mai 2017, par parsa

  I implement live streaming from mp4 video file which exists on the path with ffmpeg under hls format.
  When my video file have the quality greater than hd720 , in encoding there are so many delays for creating .ts fragments.
  I mean the .ts fragments slowly produced on my path,and because of it I have so many delays in showing the stream.
  Here is my ffmpeg code for streaming :

  ffmpeg -re -i 123.mp4 -s cga -f hls -hls_list_size 0 -c:v libx264 -c:a aac 200p/out.m3u8 
  
                -s nhd -f hls -hls_list_size 0 -c:v libx264 -c:a aac 360p/out.m3u8 
  
                -s hd480 -f hls -hls_list_size 0 -c:v libx264 -c:a aac 480p/out.m3u8 
  
                -s hd720 -f hls -hls_list_size 0 -c:v libx264 -c:a aac 720p/out.m3u8
  
                -s hd1080 -f hls -hls_list_size 0 -c:v libx264 -c:a aac 1080p/out.m3u8

  And here is the console output :

      ffmpeg -re -i ../files/412-887123464/video/412-887123464.mp4 -s cga -f hls -hls_list_size 0 -c:v libx264 -c:a aac ../fil
  
          es/412-887123464/video/200p/out.m3u8  -s nhd -f hls -hls_list_size 0 -c:v libx264 -c:a aac ../files/412-887123464/video/360p/out.m3u8 -s hd480 -f hls -
  
          hls_list_size 0 -c:v libx264 -c:a aac ../files/412-887123464/video/480p/out.m3u8 -s hd720 -f hls -hls_list_size 0 -c:v libx264 -c:a aac ../files/412-88
  
          7123464/video/720p/out.m3u8 -s hd1080 -f hls -hls_list_size 0 -c:v libx264 -c:a aac ../files/412-887123464/video/1080p/out.m3u8
  
          ffmpeg version N-82225-gb4e9252 Copyright (c) 2000-2016 the FFmpeg developers
  
            built with gcc 5.4.0 (GCC)
  
            configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --e
  
          nable-libebur128 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcac
  
          a --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-lib
  
          opencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsnappy --enable-libsoxr
  
           --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwa
  
          vpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zl
  
          ib
  
            libavutil      55. 35.100 / 55. 35.100
  
            libavcodec     57. 66.101 / 57. 66.101
  
            libavformat    57. 57.100 / 57. 57.100
  
            libavdevice    57.  2.100 / 57.  2.100
  
            libavfilter     6. 66.100 /  6. 66.100
  
            libswscale      4.  3.100 /  4.  3.100
  
            libswresample   2.  4.100 /  2.  4.100
  
            libpostproc    54.  2.100 / 54.  2.100
  
          Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '../files/412-887123464/video/412-887123464.mp4':
  
            Metadata:
  
              major_brand     : isom
  
              minor_version   : 512
  
              compatible_brands: isomiso2avc1mp41
  
              encoder         : Lavf57.31.100
  
            Duration: 00:05:04.07, start: 0.000000, bitrate: 3108 kb/s
  
              Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x1080 [SAR 1:1 DAR 16:9], 2976 kb/s, 25 fps, 25 tbr, 90k tbn, 50
  
          tbc (default)
  
              Metadata:
  
                handler_name    : VideoHandler
  
              Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 125 kb/s (default)
  
              Metadata:
  
                handler_name    : SoundHandler
  
          [libx264 @ 0000000001c53f00] using SAR=10/9
  
          [libx264 @ 0000000001c53f00] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
  
          [libx264 @ 0000000001c53f00] profile High, level 1.3
  
          Output #0, hls, to '../files/412-887123464/video/200p/out.m3u8':
  
            Metadata:
  
              major_brand     : isom
  
              minor_version   : 512
  
              compatible_brands: isomiso2avc1mp41
  
              encoder         : Lavf57.57.100
  
              Stream #0:0(und): Video: h264 (libx264), yuv420p, 320x200 [SAR 10:9 DAR 16:9], q=-1--1, 25 fps, 90k tbn, 25 tbc (default)
  
              Metadata:
  
                handler_name    : VideoHandler
  
                encoder         : Lavc57.66.101 libx264
  
              Side data:
  
                cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
              Stream #0:1(und): Audio: aac (LC), 44100 Hz, stereo, fltp, 128 kb/s (default)
  
              Metadata:
  
                handler_name    : SoundHandler
  
                encoder         : Lavc57.66.101 aac
  
          [libx264 @ 0000000001f87180] using SAR=1/1
  
          [libx264 @ 0000000001f87180] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
  
          [libx264 @ 0000000001f87180] profile High, level 3.0
  
          Output #1, hls, to '../files/412-887123464/video/360p/out.m3u8':
  
            Metadata:
  
              major_brand     : isom
  
              minor_version   : 512
  
              compatible_brands: isomiso2avc1mp41
  
              encoder         : Lavf57.57.100
  
              Stream #1:0(und): Video: h264 (libx264), yuv420p, 640x360 [SAR 1:1 DAR 16:9], q=-1--1, 25 fps, 90k tbn, 25 tbc (default)
  
              Metadata:
  
                handler_name    : VideoHandler
  
                encoder         : Lavc57.66.101 libx264
  
              Side data:
  
                cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
              Stream #1:1(und): Audio: aac (LC), 44100 Hz, stereo, fltp, 128 kb/s (default)
  
              Metadata:
  
                handler_name    : SoundHandler
  
                encoder         : Lavc57.66.101 aac
  
          [libx264 @ 0000000001c55ba0] using SAR=640/639
  
          [libx264 @ 0000000001c55ba0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
  
          [libx264 @ 0000000001c55ba0] profile High, level 3.0
  
          Output #2, hls, to '../files/412-887123464/video/480p/out.m3u8':
  
            Metadata:
  
              major_brand     : isom
  
              minor_version   : 512
  
              compatible_brands: isomiso2avc1mp41
  
              encoder         : Lavf57.57.100
  
              Stream #2:0(und): Video: h264 (libx264), yuv420p, 852x480 [SAR 640:639 DAR 16:9], q=-1--1, 25 fps, 90k tbn, 25 tbc (default)
  
              Metadata:
  
                handler_name    : VideoHandler
  
                encoder         : Lavc57.66.101 libx264
  
              Side data:
  
                cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
              Stream #2:1(und): Audio: aac (LC), 44100 Hz, stereo, fltp, 128 kb/s (default)
  
              Metadata:
  
                handler_name    : SoundHandler
  
                encoder         : Lavc57.66.101 aac
  
          [libx264 @ 0000000001ca0220] using SAR=1/1
  
          [libx264 @ 0000000001ca0220] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
  
          [libx264 @ 0000000001ca0220] profile High, level 3.1
  
          Output #3, hls, to '../files/412-887123464/video/720p/out.m3u8':
  
            Metadata:
  
              major_brand     : isom
  
              minor_version   : 512
  
              compatible_brands: isomiso2avc1mp41
  
              encoder         : Lavf57.57.100
  
              Stream #3:0(und): Video: h264 (libx264), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 25 fps, 90k tbn, 25 tbc (default)
  
              Metadata:
  
                handler_name    : VideoHandler
  
                encoder         : Lavc57.66.101 libx264
  
              Side data:
  
                cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
              Stream #3:1(und): Audio: aac (LC), 44100 Hz, stereo, fltp, 128 kb/s (default)
  
              Metadata:
  
                handler_name    : SoundHandler
  
                encoder         : Lavc57.66.101 aac
  
          [libx264 @ 0000000001ca23e0] using SAR=1/1
  
          [libx264 @ 0000000001ca23e0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2
  
          [libx264 @ 0000000001ca23e0] profile High, level 4.0
  
          Output #4, hls, to '../files/412-887123464/video/1080p/out.m3u8':
  
            Metadata:
  
              major_brand     : isom
  
              minor_version   : 512
  
              compatible_brands: isomiso2avc1mp41
  
              encoder         : Lavf57.57.100
  
              Stream #4:0(und): Video: h264 (libx264), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], q=-1--1, 25 fps, 90k tbn, 25 tbc (default)
  
              Metadata:
  
                handler_name    : VideoHandler
  
                encoder         : Lavc57.66.101 libx264
  
              Side data:
  
                cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
              Stream #4:1(und): Audio: aac (LC), 44100 Hz, stereo, fltp, 128 kb/s (default)
  
              Metadata:
  
                handler_name    : SoundHandler
  
                encoder         : Lavc57.66.101 aac
  
          Stream mapping:
  
            Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
  
            Stream #0:1 -> #0:1 (aac (native) -> aac (native))
  
            Stream #0:0 -> #1:0 (h264 (native) -> h264 (libx264))
  
            Stream #0:1 -> #1:1 (aac (native) -> aac (native))
  
            Stream #0:0 -> #2:0 (h264 (native) -> h264 (libx264))
  
            Stream #0:1 -> #2:1 (aac (native) -> aac (native))
  
            Stream #0:0 -> #3:0 (h264 (native) -> h264 (libx264))
  
            Stream #0:1 -> #3:1 (aac (native) -> aac (native))
  
            Stream #0:0 -> #4:0 (h264 (native) -> h264 (libx264))
  
            Stream #0:1 -> #4:1 (aac (native) -> aac (native))
  
          Press [q] to stop, [?] for help
  
  frame= 7600 fps= 21 q=-1.0 Lq=-1.0 q=-1.0 q=-1.0 q=-1.0 size=N/A time=00:05:04.06 bitrate=N/A speed=0.835x
  
  video:294980kB audio:23995kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
  
  [libx264 @ 0000000001d33f00] frame I:33    Avg QP:19.93  size: 11412
  
  [libx264 @ 0000000001d33f00] frame P:2281  Avg QP:23.72  size:  3112
  
  [libx264 @ 0000000001d33f00] frame B:5286  Avg QP:28.59  size:   446
  
  [libx264 @ 0000000001d33f00] consecutive B-frames:  4.3%  6.9%  5.9% 82.8%
  
  [libx264 @ 0000000001d33f00] mb I  I16..4: 12.9% 42.9% 44.2%
  
  [libx264 @ 0000000001d33f00] mb P  I16..4:  1.3%  4.4%  2.3%  P16..4: 41.4% 22.0% 15.5%  0.0%  0.0%    skip:13.1%
  
  [libx264 @ 0000000001d33f00] mb B  I16..4:  0.0%  0.1%  0.0%  B16..8: 35.2%  5.9%  2.1%  direct: 3.0%  skip:53.6%  L0:35.3% L1:48.0% BI:16.8%
  
  [libx264 @ 0000000001d33f00] 8x8 transform intra:53.4% inter:57.9%
  
  [libx264 @ 0000000001d33f00] coded y,uvDC,uvAC intra: 70.6% 89.7% 67.6% inter: 18.1% 20.3% 7.2%
  
  [libx264 @ 0000000001d33f00] i16 v,h,dc,p: 24% 24%  6% 45%
  
  [libx264 @ 0000000001d33f00] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 27% 14% 19%  5%  5%  7%  5% 10%  7%
  
  [libx264 @ 0000000001d33f00] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 31% 15% 15%  6%  6%  7%  6%  8%  6%
  
  [libx264 @ 0000000001d33f00] i8c dc,h,v,p: 42% 17% 28% 14%
  
  [libx264 @ 0000000001d33f00] Weighted P-Frames: Y:26.3% UV:12.9%
  
  [libx264 @ 0000000001d33f00] ref P L0: 58.7% 24.7% 10.9%  4.8%  1.0%
  
  [libx264 @ 0000000001d33f00] ref B L0: 92.6%  5.8%  1.6%
  
  [libx264 @ 0000000001d33f00] ref B L1: 96.3%  3.7%
  
  [libx264 @ 0000000001d33f00] kb/s:258.68
  
  [aac @ 00000000005fc9e0] Qavg: 686.637
  
  [libx264 @ 0000000002017180] frame I:31    Avg QP:19.77  size: 29228
  
  [libx264 @ 0000000002017180] frame P:2040  Avg QP:23.08  size:  8765
  
  [libx264 @ 0000000002017180] frame B:5529  Avg QP:27.28  size:  1471
  
  [libx264 @ 0000000002017180] consecutive B-frames:  1.3%  4.2%  2.4% 92.1%
  
  [libx264 @ 0000000002017180] mb I  I16..4:  8.3% 58.8% 32.9%
  
  [libx264 @ 0000000002017180] mb P  I16..4:  3.2%  9.5%  2.6%  P16..4: 41.5% 19.5% 11.4%  0.0%  0.0%    skip:12.2%
  
  [libx264 @ 0000000002017180] mb B  I16..4:  0.2%  0.3%  0.1%  B16..8: 34.5%  5.8%  1.7%  direct: 2.7%  skip:54.7%  L0:35.9% L1:49.5% BI:14.6%
  
  [libx264 @ 0000000002017180] 8x8 transform intra:61.2% inter:67.3%
  
  [libx264 @ 0000000002017180] coded y,uvDC,uvAC intra: 55.8% 84.8% 51.3% inter: 15.6% 19.3% 3.9%
  
  [libx264 @ 0000000002017180] i16 v,h,dc,p: 24% 29%  8% 39%
  
  [libx264 @ 0000000002017180] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 27% 17% 21%  5%  5%  7%  5%  8%  6%
  
  [libx264 @ 0000000002017180] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 29% 18% 15%  6%  7%  7%  6%  7%  5%
  
  [libx264 @ 0000000002017180] i8c dc,h,v,p: 42% 18% 27% 13%
  
  [libx264 @ 0000000002017180] Weighted P-Frames: Y:22.3% UV:12.2%
  
  [libx264 @ 0000000002017180] ref P L0: 58.5% 23.4% 12.2%  5.2%  0.8%
  
  [libx264 @ 0000000002017180] ref B L0: 93.1%  5.3%  1.6%
  
  [libx264 @ 0000000002017180] ref B L1: 96.6%  3.4%
  
  [libx264 @ 0000000002017180] kb/s:708.47
  
  [aac @ 0000000001d35200] Qavg: 686.637
  
  [libx264 @ 0000000001d35ba0] frame I:31    Avg QP:19.63  size: 41522
  
  [libx264 @ 0000000001d35ba0] frame P:2025  Avg QP:22.86  size: 13415
  
  [libx264 @ 0000000001d35ba0] frame B:5544  Avg QP:26.52  size:  2471
  
  [libx264 @ 0000000001d35ba0] consecutive B-frames:  1.1%  3.9%  2.8% 92.2%
  
  [libx264 @ 0000000001d35ba0] mb I  I16..4: 10.6% 62.4% 26.9%
  
  [libx264 @ 0000000001d35ba0] mb P  I16..4:  4.7% 12.4%  2.6%  P16..4: 41.1% 17.8%  9.4%  0.0%  0.0%    skip:11.9%
  
  [libx264 @ 0000000001d35ba0] mb B  I16..4:  0.3%  0.5%  0.1%  B16..8: 34.0%  5.5%  1.4%  direct: 2.9%  skip:55.3%  L0:36.7% L1:50.2% BI:13.1%
  
  [libx264 @ 0000000001d35ba0] 8x8 transform intra:61.7% inter:71.6%
  
  [libx264 @ 0000000001d35ba0] coded y,uvDC,uvAC intra: 48.0% 81.9% 43.3% inter: 14.7% 19.7% 2.6%
  
  [libx264 @ 0000000001d35ba0] i16 v,h,dc,p: 27% 29%  9% 35%
  
  [libx264 @ 0000000001d35ba0] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 27% 19% 22%  5%  5%  6%  5%  7%  5%
  
  [libx264 @ 0000000001d35ba0] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 26% 25% 16%  5%  6%  7%  6%  6%  4%
  
  [libx264 @ 0000000001d35ba0] i8c dc,h,v,p: 42% 20% 26% 12%
  
  [libx264 @ 0000000001d35ba0] Weighted P-Frames: Y:18.1% UV:10.8%
  
  [libx264 @ 0000000001d35ba0] ref P L0: 59.5% 22.6% 12.6%  4.8%  0.5%
  
  [libx264 @ 0000000001d35ba0] ref B L0: 93.6%  5.0%  1.4%
  
  [libx264 @ 0000000001d35ba0] ref B L1: 97.1%  2.9%
  
  [libx264 @ 0000000001d35ba0] kb/s:1109.23
  
  [aac @ 0000000001d828a0] Qavg: 686.637
  
  [libx264 @ 0000000001d7f880] frame I:32    Avg QP:19.45  size: 64737
  
  [libx264 @ 0000000001d7f880] frame P:2104  Avg QP:22.44  size: 23985
  
  [libx264 @ 0000000001d7f880] frame B:5464  Avg QP:25.65  size:  4999
  
  [libx264 @ 0000000001d7f880] consecutive B-frames:  1.2%  7.7%  3.2% 87.8%
  
  [libx264 @ 0000000001d7f880] mb I  I16..4: 12.5% 70.0% 17.5%
  
  [libx264 @ 0000000001d7f880] mb P  I16..4:  6.7% 17.1%  1.8%  P16..4: 40.7% 14.9%  6.6%  0.0%  0.0%    skip:12.2%
  
  [libx264 @ 0000000001d7f880] mb B  I16..4:  0.6%  0.9%  0.1%  B16..8: 32.5%  4.7%  1.0%  direct: 2.9%  skip:57.4%  L0:37.6% L1:51.6% BI:10.8%
  
  [libx264 @ 0000000001d7f880] 8x8 transform intra:65.7% inter:77.5%
  
  [libx264 @ 0000000001d7f880] coded y,uvDC,uvAC intra: 39.5% 76.4% 32.4% inter: 13.2% 19.8% 1.5%
  
  [libx264 @ 0000000001d7f880] i16 v,h,dc,p: 32% 27% 10% 31%
  
  [libx264 @ 0000000001d7f880] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 30% 18% 23%  4%  5%  5%  4%  5%  4%
  
  [libx264 @ 0000000001d7f880] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 29% 20% 15%  5%  7%  7%  6%  6%  4%
  
  [libx264 @ 0000000001d7f880] i8c dc,h,v,p: 42% 19% 27% 12%
  
  [libx264 @ 0000000001d7f880] Weighted P-Frames: Y:10.5% UV:6.7%
  
  [libx264 @ 0000000001d7f880] ref P L0: 62.3% 20.4% 12.7%  4.3%  0.3%
  
  [libx264 @ 0000000001d7f880] ref B L0: 93.4%  5.2%  1.4%
  
  [libx264 @ 0000000001d7f880] ref B L1: 97.7%  2.3%
  
  [libx264 @ 0000000001d7f880] kb/s:2101.26
  
  [aac @ 0000000001d81560] Qavg: 686.637
  
  [libx264 @ 0000000001d7fd60] frame I:33    Avg QP:18.36  size: 98904
  
  [libx264 @ 0000000001d7fd60] frame P:3180  Avg QP:21.67  size: 33377
  
  [libx264 @ 0000000001d7fd60] frame B:4387  Avg QP:24.61  size:  7729
  
  [libx264 @ 0000000001d7fd60] consecutive B-frames:  2.7% 55.9% 15.6% 25.9%
  
  [libx264 @ 0000000001d7fd60] mb I  I16..4: 22.4% 66.9% 10.7%
  
  [libx264 @ 0000000001d7fd60] mb P  I16..4:  9.9% 17.8%  0.7%  P16..4: 40.4%  9.2%  3.0%  0.0%  0.0%    skip:19.0%
  
  [libx264 @ 0000000001d7fd60] mb B  I16..4:  0.8%  1.3%  0.1%  B16..8: 30.2%  2.6%  0.4%  direct: 1.7%  skip:63.0%  L0:38.1% L1:54.9% BI: 7.0%
  
  [libx264 @ 0000000001d7fd60] 8x8 transform intra:62.5% inter:82.9%
  
  [libx264 @ 0000000001d7fd60] coded y,uvDC,uvAC intra: 25.4% 59.5% 11.6% inter: 9.6% 16.3% 0.7%
  
  [libx264 @ 0000000001d7fd60] i16 v,h,dc,p: 33% 28% 15% 24%
  
  [libx264 @ 0000000001d7fd60] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 34% 20% 29%  3%  3%  4%  3%  3%  3%
  
  [libx264 @ 0000000001d7fd60] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 30% 25% 16%  4%  6%  6%  5%  5%  4%
  
  [libx264 @ 0000000001d7fd60] i8c dc,h,v,p: 39% 21% 28% 12%
  
  [libx264 @ 0000000001d7fd60] Weighted P-Frames: Y:5.7% UV:3.6%
  
  [libx264 @ 0000000001d7fd60] ref P L0: 70.0% 18.6%  8.3%  3.1%  0.1%
  
  [libx264 @ 0000000001d7fd60] ref B L0: 91.4%  7.6%  1.0%
  
  [libx264 @ 0000000001d7fd60] ref B L1: 99.0%  1.0%
  
  [libx264 @ 0000000001d7fd60] kb/s:3771.31
  
  [aac @ 0000000001d823e0] Qavg: 686.637

  But I don’t have any problem for streaming files with creating resolutions from a file which have lower orginal quality than hd1080
  What I can to do ?

• OCPA, FDBR and TDPSA – What you need to know about the US’s new privacy laws

  22 juillet 2024, par Daniel Crough

  On July 1, 2024, new privacy laws took effect in Florida, Oregon, and Texas. People in these states now have more control over their personal data, signaling a shift in privacy policy in the United States. Here’s what you need to know about these laws and how privacy-focused analytics can help your business stay compliant.

  Consumer rights are front and centre across all three laws

  The Florida Digital Bill of Rights (FDBR), Oregon Consumer Privacy Act (OCPA), and Texas Data Privacy and Security Act (TDPSA) grant consumers similar rights.

  Access : Consumers can access their personal data held by businesses.

  Correction : Consumers can correct inaccurate data.

  Deletion : Consumers may request data deletion.

  Opt-Out : Consumers can opt-out of the sale of their personal data and targeted advertising.

  Oregon Consumer Privacy Act (OCPA)

  The Oregon Consumer Privacy Act (OCPA), signed into law on June 23, 2023, and effective as of July 1, 2024, grants Oregonians new rights regarding their personal data and imposes obligations on businesses. Starting July 1, 2025, authorities will enforce provisions that require data protection assessments, and businesses must recognize universal opt-out mechanisms by January 1, 2026. In Oregon, the OCPA applies to business that :

  • Either conduct business in Oregon or offer products and services to Oregon residents

  • Control or process the personal data of 100,000 consumers or more, or

  • Control or process the data of 25,000 or more consumers while receiving over 25% of their gross revenues from selling personal data.

  Exemptions include public bodies like state and local governments, financial institutions, and insurers that operate under specific financial regulations. The law also excludes protected health information covered by HIPAA and other specific federal regulations.

  Business obligations

  Data Protection Assessments : Businesses must conduct data protection assessments for high-risk processing activities, such as those involving sensitive data or targeting children.

  Consent for Sensitive Data : Businesses must secure explicit consent before collecting, processing, or selling sensitive personal data, such as racial or ethnic origin, religious beliefs, health information, biometric data, and geolocation.

  Universal Opt-out : Starting January 1, 2025, businesses must acknowledge universal opt-out mechanisms, like the Global Privacy Control, that allow consumers to opt out of data collection and processing activities.

  Enforcement

  The Oregon Attorney General can issue fines up to $7,500 per violation. There is no private right of action.

  Unique characteristics of the OCPA

  The OCPA differs from other state privacy laws by requiring affirmative opt-in consent for processing sensitive and children’s data, and by including nonprofit organisations under its scope. It also requires global browser opt-out mechanisms starting in 2026.

  Florida Digital Bill of Rights (FDBR)

  The Florida Digital Bill of Rights (FDBR) became law on June 6, 2023, and it came into effect on July 1, 2024. This law targets businesses with substantial operations or revenues tied to digital activities and seeks to protect the personal data of Florida residents by granting them greater control over their information and imposing stricter obligations on businesses. It applies to entities that :

  • Conduct business in Florida or provide products or services targeting Florida residents,

  • Have annual global gross revenues exceeding $1 billion,

  • Receive 50% or more of their revenues from digital advertising or operate significant digital platforms such as app stores or smart speakers with virtual assistants.

  Exemptions include governmental entities, nonprofits, financial institutions covered by the Gramm-Leach-Bliley Act, and entities covered by HIPAA.

  Business obligations

  Data Security Measures : Companies are required to implement reasonable data security measures to protect personal data from unauthorised access and breaches.

  Handling Sensitive Data : Explicit consent is required for processing sensitive data, which includes information like racial or ethnic origin, religious beliefs, and biometric data.

  Non-Discrimination : Entities must ensure they do not discriminate against consumers who exercise their privacy rights.

  Data Minimisation : Businesses must collect only necessary data.

  Vendor Management : Businesses must ensure that their processors and vendors also comply with the FDBR, regarding the secure handling and processing of personal data.

  Enforcement

  The Florida Attorney General can impose fines of up to $50,000 per violation, with higher penalties for intentional breaches.

  Unique characteristics of the FDBR

  Unlike broader privacy laws such as the California Consumer Privacy Act (CCPA), which apply to a wider range of businesses based on lower revenue thresholds and the volume of data processed, the FDBR distinguishes itself by targeting large-scale businesses with substantial revenues from digital advertising. The FDBR also emphasises specific consumer rights related to modern digital interactions, reflecting the evolving landscape of online privacy concerns.

  Texas Data Privacy and Security Act (TDPSA)

  The Texas Data Privacy and Security Act (TDPSA), signed into law on June 16, 2023, and effective as of July 1, 2024, enhances data protection for Texas residents. The TDPSA applies to entities that :

  • Conduct business in Texas or offer products or services to Texas residents.

  • Engage in processing or selling personal data.

  • Do not fall under the classification of small businesses according to the U.S. Small Business Administration’s criteria, which usually involve employee numbers or average annual receipts. 

  The law excludes state agencies, political subdivisions, financial institutions compliant with the Gramm-Leach-Bliley Act, and entities compliant with HIPAA.

  Business obligations

  Data Protection Assessments : Businesses must conduct data protection assessments for processing activities that pose a heightened risk of harm to consumers, such as processing for targeted advertising, selling personal data, or profiling.

  Consent for Sensitive Data : Businesses must get explicit consent before collecting, processing, or selling sensitive personal data, such as racial or ethnic origin, religious beliefs, health information, biometric data, and geolocation.

  Companies must have adequate data security practices based on the personal information they handle.

  Data Subject Access Requests (DSARs) : Businesses must respond to consumer requests regarding their personal data (e.g., access, correction, deletion) without undue delay, but no later than 45 days after receipt of the request.

  Sale of Data : If businesses sell personal data, they must disclose these practices to consumers and provide them with an option to opt out.

  Universal Opt-Out Compliance : Starting January 1, 2025, businesses must recognise universal opt-out mechanisms like the Global Privacy Control, enabling consumers to opt out of data collection and processing activities.

  Enforcement

  The Texas Attorney General can impose fines up to $25,000 per violation. There is no private right of action.

  Unique characteristics of the TDPSA

  The TDPSA stands out for its small business carve-out, lack of specific thresholds based on revenue or data volume, and requirements for recognising universal opt-out mechanisms starting in 2025. It also mandates consent for processing sensitive data and includes specific measures for data protection assessments and privacy notices.

  Try Matomo for Free

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

  Start for free

  No credit card required

  Privacy notices across Florida, Oregon, and Texas

  All three laws include a mandate for privacy notices, though there are subtle variations in their specific requirements. Here’s a breakdown of these differences :

  FDBR privacy notice requirements

  Clarity : Privacy notices must clearly explain the collection and use of personal data.

  Disclosure : Notices must inform consumers about their rights, including the right to access, correct, delete their data, and opt-out of data sales and targeted advertising.

  Specificity : Businesses must disclose if they sell personal data or use it for targeted advertising.

  Security Practices : The notice should describe the data security measures in place.

  OCPA privacy notice requirements

  Comprehensive Information : Notices must provide information about the personal data collected, the purposes for processing, and any third parties that can access it.

  Consumer Rights : Must plainly outline consumers’ rights to access, correct, delete their data, and opt-out of data sales, targeted advertising, and profiling.

  Sensitive Data : To process sensitive data, businesses or entities must get explicit consent and communicate it.

  Universal Opt-Out : Starting January 1, 2026, businesses must recognise and honour universal opt-out mechanisms.

  TDPSA privacy notice requirements

  Detailed Notices : Must provide clear and detailed information about data collection practices, including the data collected and the purposes for its use.

  Consumer Rights : Must inform consumers of their rights to access, correct, delete their data, and opt-out of data sales and targeted advertising.

  High-Risk Processing : Notices should include information about any high-risk processing activities and the safeguards in place.

  Sensitive Data : To process sensitive data, entities and businesses must get explicit consent.

  What these laws mean for your businesses

  Businesses operating in Florida, Oregon, and Texas must now comply with these new data privacy laws. Here’s what you can do to avoid fines :

  1. Understand the Laws : Familiarise yourself with the specific requirements of the FDBR, OCPA, and TDPSA, including consumer rights and business obligations.

  2. Implement Data Protection Measures : Ensure you have robust data security measures in place. This includes conducting regular data protection assessments, especially for high-risk processing activities.

  3. Update Privacy Policies : Provide clear and comprehensive privacy notices that inform consumers about their rights and how their data is processed.

  4. Obtain Explicit Consent : For sensitive data, make sure you get explicit consent from consumers. This includes information like health, race, sexual orientation, and more.

  5. Manage Requests Efficiently : Be prepared to handle requests from consumers to access, correct, delete their data, and opt-out of data sales and targeted advertising within the stipulated timeframes.

  6. Recognise Opt-Out Mechanisms : For Oregon, businesses must be ready to implement and recognise universal opt-out mechanisms by January 1, 2026. In Texas, opt-out enforcement begins in 2026. In Florida, the specific opt-out provisions began on July 1, 2024.

  7. Stay Updated : Keep abreast of any changes or updates to these laws to ensure ongoing compliance. Keep an eye on the Matomo blog or sign up for our newsletter to stay in the know.

  Are we headed towards a more privacy-focused future in the United States ?

  Florida, Oregon, and Texas are joining states like California, Virginia, Colorado, Connecticut, Utah, Iowa, Indiana, Tennessee, and Montana in strengthening consumer privacy protections. This trend could signify a shift in US policy towards a more privacy-focused internet, underlining the importance of consumer data rights and transparent business practices. Even if these laws do not apply to your business, considering updates to your data and privacy policies is wise. Fortunately, there are tools and solutions designed for privacy and compliance to help you navigate these changes.

  Avoid fines and get better data with Matomo

  Most analytics tools don’t prioritize safeguarding user data. At Matomo, we believe everyone has the right to data sovereignty, privacy and amazing analytics. Matomo offers a solution that meets privacy regulations while delivering incredible insights. With Matomo, you get :

  100% Data Ownership : Keep full control over your data, ensuring it is used according to your privacy policies.

  Privacy Protection : Built with privacy in mind, Matomo helps businesses comply with privacy laws.

  Powerful Features : Gain insights with tools like heatmaps, session recordings, and A/B testing.

  Open Source : Matomo’s is open-source and committed to transparency and customisation.

  Flexibility : Choose to host Matomo on your servers or in the cloud for added security.

  No Data Sampling : Ensure accurate and complete insights without data sampling.

  Privacy Compliance : Easily meet GDPR and other requirements, with data stored securely and never sold or shared.

  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

  

  Disclaimer : This content is provided for informational purposes only and is not intended as legal advice. While we strive to ensure the accuracy and timeliness of the information provided, the laws and regulations surrounding privacy are complex and subject to change. We recommend consulting with a qualified legal professional to address specific legal issues related to your circumstances. 

• Matomo Launches Global Partner Programme to Deepen Local Connections and Champion Ethical Analytics

  25 juin, par Matomo Core Team — Press Releases

  Matomo introduces a global Partner Programme designed to connect organisations with trusted local experts, advancing its commitment to privacy, data sovereignty, and localisation.

  Wellington, New Zealand – 25 June 2025 — Matomo, the leading web analytics platform, is
  proud to announce the launch of the Matomo Partner Programme. This new initiative marks a significant step in Matomo’s global growth strategy, bringing together a carefully selected
  network of expert partners to support customers with localised, high–trust analytics services
  rooted in shared values.
  
  As privacy concerns rise and organisations seek alternatives to mainstream analytics solutions, the need for regional expertise has never been more vital. The Matomo Partner Programme ensures that customers around the world are supported not just by a world–class platform, but by trusted local professionals who understand their specific regulatory, cultural, and business needs.
  
  “Matomo is evolving. As privacy regulations become more nuanced and the need for regional
  understanding grows, we’ve made localisation a central pillar of our strategy. Our partners are
  the key to helping customers navigate these complexities with confidence and care,” said
  Adam Taylor, Chief Operating Officer at Matomo.

  Local Experts, Global Values

  At the heart of the Matomo Partner Programme is a commitment to connect clients with local experts who live and breathe their markets. These partners are more than service
  providers—they’re trusted advisors who bring deep insight into their region’s privacy
  legislation, cultural norms, sector–specific requirements, and digital trends.
  
  The programme empowers partners to act as extensions of Matomo’s core teams :
  
  • As Customer Success allies, delivering personalised training, support, and technical
  services in local languages and time zones.

  • As Sales ambassadors, raising awareness of ethical analytics in both public and private

  sectors, where trust, compliance, and transparency are crucial.
  
  This decentralised, values–aligned approach ensures that every Matomo customer benefits
  from localised delivery with global consistency.

  A Programme Designed for Impactful Partnerships

  The Matomo Partner Programme is open to organisations who share a commitment to ethical, open-source analytics and can demonstrate :

  • Technical excellence in deploying, configuring, and supporting Matomo Analytics in diverse environments.
  • Deep market understanding, allowing them to tell the Matomo story in ways that
  resonate locally.
  • Commercial strength to position Matomo across key industries, particularly in sectors with complex compliance and data sovereignty demands.

  Partners who meet these standards will be recognised as ‘Official Matomo Partners’— a symbol of excellence, credibility, and shared purpose. With this status, they gain access to :

  • Brand alignment and trust : Strengthen credibility with clients by promoting their
  connection to Matomo and its globally respected ethical stance.
  • Go-to-market support : Access to qualified leads, joint marketing, and tools to scale their business in a privacy-first market.
  • Strategic collaboration : Early insights into the product roadmap and direct
  engagement with Matomo’s core team.
  • Meaningful local impact : Help regional organisations reclaim control of their data and embrace ethical analytics with confidence.

  Ethical Analytics for Today’s World
  

  Matomo was founded in 2007 with the belief that people should have full control over their data. As the first open–source web analytics platform of its kind, Matomo continues to challenge the dominance of opaque, centralised tools by offering a transparent and flexible alternative that puts users first.
  
  In today’s landscape—marked by increased regulatory scrutiny, data protection concerns, and rapid advancements in AI—Matomo’s approach is more relevant than ever. Open–source technology provides the adaptability organisations need to respond to local expectations while reinforcing digital trust with users.

  Whether it’s a government department, healthcare provider, educational institution, or
  commercial business—Matomo partners are on the ground, ready to help organisations
  transition to analytics that are not only powerful but principled.