Recherche avancée

Sur d’autres sites (3747)

• iOS 17’s Impact on Marketing : Navigating Privacy Changes

  22 septembre 2023, par Erin — Analytics Tips, Marketing

  In the ever-evolving landscape of digital marketing, staying up-to-date with the latest changes is paramount. One such significant change came on 18 September 2023, in the form of iOS 17, Apple’s latest operating system update. With iOS 17, Apple has introduced new privacy features that are set to have a profound impact on marketers and how they track and analyse user behaviour. 

  In this blog, we will explore what iOS 17 is, how it affects tracking, which tracking parameters are impacted, what remains unaffected, and most importantly, how marketers can future-proof their campaign tracking URLs.

  What is iOS 17 ?

  iOS 17 is the latest update to Apple’s mobile operating system, used on millions of iPhones worldwide. While iOS updates often bring new features and improvements, iOS 17 has made waves in the digital marketing community due to its emphasis on user privacy.

  How does iOS 17 affect tracking ?

  One of the key features of iOS 17 that concerns marketers is its impact on tracking. Apple’s new update aims to enhance user privacy by limiting the information that can be tracked and collected by third-party entities, particularly through query parameters in URLs. This means that certain tracking mechanisms that marketers have relied on for years are now rendered ineffective on iOS 17 devices.

  Campaign tracking URLs, also known as tracking parameters or UTM parameters, are special codes added to the end of URLs. They are used by marketers to track various aspects of a user’s interaction with a digital marketing campaign. These parameters provide valuable data, such as the source of traffic, the medium through which users arrived and specific campaign details.

  For example, with Matomo (mtm) tracking parameters, a campaign tracking URL might look like this :

  https://www.example.com/products/example_product?mtm_campaign=summer-sale

  

  Understanding the impact of iOS 17 on campaign tracking URLs is essential for marketers who rely on this data to measure the effectiveness of their marketing campaigns.

  Which campaign tracking parameters are affected by iOS 17 ?

  Several tracking parameters commonly used by marketers will no longer work as expected on iOS 17. Some of these include :

  • Facebook (fbclid) : Employed for tracking Facebook advertising campaigns. 
  • Instagram (igshid) : Used to track user interactions with Instagram ads.
  • Google Ads (gclid) : Used to track Google Ads campaigns. 
  • Twitter (twclid) : Used to track user interactions with Twitter ads. 
  • Microsoft Ads (msclkid) : Employed for tracking Microsoft Ads campaigns. 
  • Mailchimp (mc_eid) : Used by Mailchimp for email campaign tracking. 

  These changes are significant, as they disrupt many of the common tracking methods that marketers rely on to measure the effectiveness of their campaigns.

  Which campaign tracking parameters are not affected by iOS 17 ?

  While many tracking parameters have been impacted, there are still some that remain unaffected on iOS 17. However, it’s important to note that the status of these parameters might change in the future as Apple continues to prioritise user privacy. Some of the tracking parameters that are still working as of now include :

  • Matomo (mtm) : Matomo campaign tracking parameters. 
  • Google Analytics (UTMs) : Google Analytics campaign tracking parameters.
  • Pinterest (epik) : Used for tracking Pinterest campaigns. 
  • Klaviyo (_kx) : Klaviyo for email marketing tracking. 
  • TikTok (tt-) : Used for tracking TikTok ad interactions. 
  • Hubspot (hsa) : Used for tracking Hubspot campaigns. 

  While these parameters offer some reprieve for marketers, it’s essential to keep a close eye on any potential changes in their functionality as Apple continues to roll out privacy-friendly features.

  How are Matomo users impacted ?

  Fortunately, Matomo, as a leading privacy-friendly web analytics solution, remains unaffected by the changes introduced by iOS 17. Specifically :

  For Matomo users who rely on mtm or UTMs

  If you’re using Matomo or GA tracking parameters, you can rest assured that iOS 17’s changes won’t affect your tracking capabilities in Matomo.

  Attention to gclids (Google Ads) and msclkid (Bing Ads)

  If you use Google Ads or Bing Ads tracking parameters with Matomo’s Advertising Conversion Export feature for tracking, iOS 17 presents a challenge. Your gclids and msclkids may not provide the same level of tracking accuracy on Apple mobile devices. This is a critical consideration, especially if your ad campaigns target mobile users.

  To stay informed about changes in the digital marketing landscape, including updates related to iOS 17, sign up for our newsletter where we regularly provide updates and insights on adapting your tracking and marketing strategies to ensure compliance and respect user privacy.

  How to future-proof your campaign tracking

  Given the impact of iOS 17 on tracking, it’s crucial for marketers to adapt and future-proof their campaign tracking strategies. Here are some steps you can take to mitigate the affects of iOS 17 on your marketing campaigns :

  Monitor platform updates

  Expect updates from advertising and analytics platforms in response to Apple’s privacy changes. These platforms are likely to develop alternative tracking methods or adapt existing ones to comply with iOS 17’s restrictions. Stay informed about these updates and incorporate them into your tracking strategy.

  Prioritise privacy-friendly tech stacks

  In the ever-evolving digital marketing landscape, it’s crucial to prioritise privacy-friendly tech stacks. Privacy-friendly tracking tools like Matomo are essential for maintaining trust and respecting user privacy.

  Matomo ensures the privacy of your users and analytics data. When using Matomo, you retain control of your data ; nobody else does. This commitment to user privacy aligns with the changing digital marketing landscape, where privacy is taking centre stage.

  Transition from affected campaign tracking parameters

  If you’ve been using tools like Mailchimp, whose campaign tracking URLs have been affected by iOS 17, consider transitioning to the campaign tracking URL parameters of your analytics solution. Whether you choose Matomo or Google Analytics, these solutions can help you understand how your email marketing campaigns are performing.

  Focus on data privacy compliance

  Embrace data privacy compliance practices. As privacy regulations evolve, it’s essential to prioritise transparency in data collection. Ensure that your tracking methods align with privacy standards to maintain trust with your audience.

  Regularly review and adapt

  The digital marketing landscape is dynamic, and iOS 17 is just one example of how quickly things can change. Regularly review your tracking methods and adapt to new developments in the industry. Staying agile and informed is key to long-term success.

  Marketers’ path forward

  iOS 17 has reshaped mobile user privacy, challenging marketers to adapt. While some tracking parameters are affected, savvy marketers can still thrive by embracing unique tracking solutions, staying informed about platform updates, and prioritising data privacy. 

  Explore Matomo for privacy-friendly analytics and navigate this evolving landscape successfully with our 21-day free trial – no credit card required. 

• 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 ?

• Anomalie #3035 (Nouveau) : Association de mots-clés et autorisation

  6 août 2013, par Joseph Larmarange

  Création d’un ticket suite à http://permalink.gmane.org/gmane.comp.web.spip.devel/64550

  Cas de figure :
  - des groupes de mots-clés pour lesquels les rédacteurs ont les droits pour ajouter un mot clé de ces groupes.
  - un rédacteur qui visualise un article dont il n’est pas l’auteur et par conséquent pour lequel il n’a pas les droits d’ajouter ou de supprimer un mot-clé.

  Néanmoins, ce rédacteur va voir la liste des mots-clés associés à cet article, avec un lien pour supprimer les mots-clés en question, un lien ’Ajouter des mots-clés’ lui permettant de charger le formulaire d’ajout de mot-clé.

  Si ce rédacteur décide de faire l’une de ces actions (ajout ou suppression), le bloc va se recharger, l’action ne sera pas exécutée et il n’y aura aucun message d’erreur, par exemple pour avertir que l’on n’a pas les droits nécessaires. On a donc une incohérence de l’interface.

  En investigant, j’aperçois plusieurs points qui font défaut.

  En premier lieu, la fonction autoriser_associermots_dist() regarde simplement si un auteur à le droit en général d’associer des mots-clés d’un groupe en fonction de son statut (admin ou rédacteur) mais ne prends pas en compte si l’individu a le droit de modifier l’objet en question.

  Le formulaire EDITER_LIENS du core regarde dans sa fonction charger l’autorisation associerobjets (donc associermots dans notre cas de figure) pour savoir si le formulaire est editable ou non. Dans sa fonction traiter, le formulaire regarde simplement si l’individu a le droit de modifier l’objet en question ou non (mais ne revérifie pas qu’il a les droits d’associer l’objet en question). Par ailleurs, si on n’a pas les droits requis, la fonction traiter ne renvoie pas de message d’erreur.

  Le squelette prive/objets/liste/mots_lies.html ne tient compte ni de #ENVeditable ni d’une quelconque autorisation pour afficher ou non un lien de suppression d’un mot-clé.

  La fonction autoriser_groupemots_afficherselecteurmots_dist renvoie toujours true.

  Propositions d’évolution

  • Faire évoluer l’autorisation associermots pour qu’elle vérifie également, si un $id_objet est passé, que l’invidu a les droits de modifier l’objet en question. Cela permettra que la propriété editable soit correctement renseignée dans le formulaire d’ajout de mot-clé. Par ailleurs, pour les plugins ayant besoin de savoir si quelqu’un a le droit d’associer un mot-clé, cela fera une seule auorisation à vérifier (le problème s’est posé avec coche_mots).
  • La fonction traiter de éditer_liens devrait dépendre de associermot (il faut vérifier que cela n’a pas d’incidence pour les autres tables de liens) et non des droits de modification d’un objet. Ces droits peuvent être différents dans un contexte d’autorisations personnalisées.
  • Cette même fonction traiter doit renvoyer un message d’erreur si on n’a pas les droits suffisants.
  • Le squelette prive/objets/liste/mots_lies.html doit vérifier l’autorisation associermots pour afficher un lien de suppression d’un mot-clé.
  • Par cohérence, la fonction autoriser_groupemots_afficherselecteurmots_dist est modifiée pour renvoyer, par défaut, le résultat de l’autorisation associermots.