Recherche avancée

Sur d’autres sites (6882)

• Resizing AVIF images with transparency with FFmpeg [closed]

  4 octobre 2024, par Calebmer

  I'm trying to resize an image with transparency with FFmpeg, however the output looks to only be a resized version of the alpha layer.

  


  When I try to do a noop transform of the AVIF image with an alpha layer :

  


  ffmpeg -i input.avif output.avif


  


  output.avif appears to be the alpha layer with black representing alpha 0 and white representing alpha 1.

  


  ffprobe input.avif gives me :

  


  ffprobe version 7.0.2 Copyright (c) 2007-2024 the FFmpeg developers
  built with Apple clang version 15.0.0 (clang-1500.3.9.4)
  configuration: --prefix=/opt/homebrew/Cellar/ffmpeg/7.0.2 --enable-shared --enable-pthreads --enable-version3 --cc=clang --host-cflags= --host-ldflags='-Wl,-ld_classic' --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libaribb24 --enable-libbluray --enable-libdav1d --enable-libharfbuzz --enable-libjxl --enable-libmp3lame --enable-libopus --enable-librav1e --enable-librist --enable-librubberband --enable-libsnappy --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libspeex --enable-libsoxr --enable-libzmq --enable-libzimg --disable-libjack --disable-indev=jack --enable-videotoolbox --enable-audiotoolbox --enable-neon
  libavutil      59.  8.100 / 59.  8.100
  libavcodec     61.  3.100 / 61.  3.100
  libavformat    61.  1.100 / 61.  1.100
  libavdevice    61.  1.100 / 61.  1.100
  libavfilter    10.  1.100 / 10.  1.100
  libswscale      8.  1.100 /  8.  1.100
  libswresample   5.  1.100 /  5.  1.100
  libpostproc    58.  1.100 / 58.  1.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'input.avif':
  Metadata:
    major_brand     : avif
    minor_version   : 0
    compatible_brands: avifmif1miaf
  Duration: N/A, start: 0.000000, bitrate: N/A
  Stream #0:0[0x1]: Video: av1 (libdav1d) (Main) (av01 / 0x31307661), gray(pc), 336x252 [SAR 1:1 DAR 4:3], 1 fps, 1 tbr, 1 tbn (default)
  Stream #0:1[0x2]: Video: av1 (libdav1d) (High) (av01 / 0x31307661), yuv444p(pc, smpte170m/bt709/iec61966-2-1), 336x252 [SAR 1:1 DAR 4:3], 1 fps, 1 tbr, 1 tbn


  


  Seeing there are two streams (the first stream being gray(pc), probably the alpha layer) I next tried :

  


  ffmpeg -i input.avif -map 0:v:1 output.avif


  


  To see the second stream and it gave me the image without any alpha channel. Transparent pixels were black.

  


  Ultimately I want to resize the AVIF file with ffmpeg -i input.avif -vf "scale=iw/2:-1" output.avif but that appears to only resize the greyscale alpha channel. Furthermore, this will be part of a script that operates on some AVIF files without an alpha channel and some AVIF files with an alpha channel and I don't know which files have an alpha channel ahead of time. ffmpeg -i input.avif -vf "scale=iw/2:-1" output.avif works for files without an alpha channel.

  


• FFmpeg matlab error : At least one output file must be specified ? [closed]

  3 mars, par as moh

  I'm trying to get I frames from a video using Matlab using this command system(sprintf('ffmpeg -i testVid.mp4 -vf "select=eq(pict_type\,I)" -vsync vfr output_%03d.png')); ,but i get this message

  


   ffmpeg version 7.1-full_build-www.gyan.dev Copyright (c) 2000-2024 the FFmpeg developers 
  built with gcc 14.2.0 (Rev1, Built by MSYS2 project) 
  configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-bzlib --enable-lzma --enable-libsnappy --enable-zlib --enable-librist --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libaribb24 --enable-libaribcaption --enable-libdav1d --enable-libdavs2 --enable-libopenjpeg --enable-libquirc --enable-libuavs3d --enable-libxevd --enable-libzvbi --enable-libqrencode --enable-librav1e --enable-libsvtav1 --enable-libvvenc --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxeve --enable-libxvid --enable-libaom --enable-libjxl --enable-libvpx --enable-mediafoundation --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libharfbuzz --enable-liblensfun --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-dxva2 --enable-d3d11va --enable-d3d12va --enable-ffnvcodec --enable-libvpl --enable-nvdec --enable-nvenc --enable-vaapi --enable-libshaderc --enable-vulkan --enable-libplacebo --enable-opencl --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libcodec2 --enable-libilbc --enable-libgsm --enable-liblc3 --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint 
  libavutil      59. 39.100 / 59. 39.100 
  libavcodec     61. 19.100 / 61. 19.100 
  libavformat    61.  7.100 / 61.  7.100 
  libavdevice    61.  3.100 / 61.  3.100 
  libavfilter    10.  4.100 / 10.  4.100 
  libswscale      8.  3.100 /  8.  3.100 
  libswresample   5.  3.100 /  5.  3.100 
  libpostproc    58.  3.100 / 58.  3.100 
Trailing option(s) found in the command: may be ignored. 
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'testVid.mp4': 
  Metadata: 
    major_brand     : isom 
    minor_version   : 512 
    compatible_brands: isomiso2avc1mp41 
    encoder         : Lavf57.83.100 
  Duration: 00:00:02.02, start: 0.000000, bitrate: 12798 kb/s 
  Stream #0:0[0x1](eng): Video: h264 (Baseline) (avc1 / 0x31637661), yuvj420p(pc, progressive), 1280x720 [SAR 1:1 DAR 16:9], 12662 kb/s, 29.74 fps, 30 tbr, 90k tbn (default) 
      Metadata: 
        handler_name    : VideoHandler 
        vendor_id       : [0][0][0][0] 
  Stream #0:1[0x2](eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 121 kb/s (default) 
      Metadata: 
        handler_name    : SoundHandler 
        vendor_id       : [0][0][0][0] 
At least one output file must be specified 


  


  i searched and tried many cases but i don't know where is the problem, any help please ?

  


• Consent Mode v2 : Everything You Need to Know

  7 mai 2024, par Alex — Analytics Tips

  Confused about Consent Mode v2 and its impact on your website analytics ? You’re not the only one. 

  Google’s latest update has left many scratching their heads about data privacy and tracking. 

  In this blog, we’re getting straight to the point. We’ll break down what Consent Mode v2 is, how it works, and the impact it has.

  What is Consent Mode ?

  What exaclty is Google Consent Mode and why is there so much buzz surrounding it ? This question has been frustrating analysts and marketers worldwide since the beginning of this year. 

  Consent Mode is the solution from Google designed to manage data collection on websites in accordance with user privacy requirements.

  This mode enables website owners to customise how Google tags respond to users’ consent status for cookie usage. At its core, Consent Mode adheres to privacy regulations such as GDPR in Europe and CCPA in California, without significant loss of analytical data.

  

  How does Consent Mode work ?

  Consent Mode operates by adjusting the behaviour of tags on a website depending on whether consent for cookie usage is provided or not. If a user does not consent to the use of analytical or advertising cookies, Google tags automatically switch to collecting a limited amount of data, ensuring privacy compliance.

  This approach allows for continued valuable insights into website traffic and user behavior, even if users opt out of most tracking cookies.

  What types of consent are available in Consent Mode ?

  As of 6 March 2024, Consent Mode v2 has become the current standard (and in terms of utilising Google Advertising Services, practically mandatory), indicating the incorporation of four consent types :

  1. ad_storage : allows for the collection and storage of data necessary for delivering personalised ads based on user actions.
  2. ad_user_data : pertains to the collection and usage of data that can be associated with the user for ad customisation and optimisation.
  3. ad_personalization : permits the use of user data for ad personalisation and providing more relevant content.
  4. analytics_storage : relates to the collection and storage of data for analytics, enabling websites to analyse user behaviour and enhance user experience.

  Additionally, in Consent Mode v2, there are two modes :

  1. Basic Consent Mode : in which Google tags are not used for personalised advertising and measurements if consent is not obtained.
  2. Advanced Consent Mode : allows Google tags to utilise anonymised data for personalised advertising campaigns and measurements, even if consent is not obtained.

  What is Consent Mode v2 ? (And how does it differ from Consent Mode v1 ?)

  Consent Mode v2 is an improved version of the original Consent Mode, offering enhanced customisation capabilities and better compliance with privacy requirements. 

  The new version introduces additional consent configuration parameters, allowing for even more precise control over which data is collected and how it’s used. The key difference between Consent Mode v2 and Consent Mode v1 lies in more granular consent management, making this tool even more flexible and powerful in safeguarding personal data.

  In Consent Mode v2, the existing markers (ad_storage and analytics_storage) are accompanied by two new markers :

  1. ad_user_data – does the user agree to their personal data being utilized for advertising purposes ?
  2. ad_personalization – does the user agree to their data being employed for remarketing ?

  In contrast to ad_storage and analytics_storage, these markers don’t directly affect how the tags operate on the site itself. 

  They serve as additional directives sent alongside the pings to Google services, indicating how user data can be utilised for advertising purposes.

  While ad_storage and analytics_storage serve as upstream qualifiers for data (determining which identifiers are sent with the pings), ad_user_data and ad_personalization serve as downstream instructions for Google services regarding data processing.

  How is the implementation of Consent Mode v2 going ?

  The implementation of Consent Mode v2 is encountering some issues and bugs (as expected). The most important thing to understand :

  1. Advanced Consent Mode v2 is essential if you have traffic and campaigns with Google Ads in the European Union.
  2. If you don’t have substantially large traffic, enabling Advanced Consent Mode v2 will likely result in a traffic drop in GA4 – because this version of consent mode (unlike the basic one) applies behavioural modelling to users who haven’t accepted the use of cookies. And modelling the behaviour requires time.

  The aspect of behavioural modelling in Consent Mode v2 implies the following : the data of users who have declined tracking options begin to be modelled using machine learning. 

  However, training the model requires a suitable data volume. As the Google’s documentation states :

  The property should collect at least 1,000 events per day with analytics_storage=’denied’ for at least 7 days. The property should have at least 1,000 daily users submitting events with analytics_storage=’granted’ for at least 7 of the previous 28 days.

  Largely due to this, the market’s response to the Consent Mode v2 implementation was mixed : many reported a significant drop in traffic in their GA4 and Google Ads reports upon enabling the Advanced mode. Essentially, a portion of the data was lost because Google’s models lacked enough data for training. 

  And from the very beginning of implementation, users regularly report about a few examples of that scenario. If your website doesn’t have enough traffic for behaviour modelling, after Consent Mode v2 switching you will face significant drop in your traffic in Google Ads and GA4 reports. There are a lot of cases of observing 90-95% drop in metrics of users and sessions.

  In a nutshell, you should be prepared for significant data losses if you are planning to switch to Google Consent Mode v2.

  How does Consent Mode v2 impact web analytics ? 

  The transition to Consent Mode v2 alters the methods of user data collection and processing. The main concerns arise from the potential loss of accuracy and completeness of analytical data due to restrictions on the use of cookies and other identifiers when user consent is absent. 

  With Google Consent Mode v2, the data of visitors who have not agreed to tracking will be modelled and may not accurately reflect your actual visitors’ behaviours and actions. So as an analyst or marketer, you will not have true insights into these visitors and the data acquired will be more generalised and less accurate.

  Google Consent Mode v2 appears to be a kind of compromise band-aid solution. 

  It tries to solve these issues by using data modelling and anonymised data collection. However, it’s critical to note that there are specific limitations inherent to the modelling mechanism.

  This complicates the analysis of visitor behavior, advertising campaigns, and website optimisation, ultimately impacting decision-making and resulting in poor website performance and marketing outcomes.

  Wrap up

  Consent Mode v2 is a mechanism of managing Google tag operations based on user consent settings. 

  It’s mandatory if you’re using Google’s advertising services, and optional (at least for Advanced mode) if you don’t advertise on Google Ads. 

  There are particular indications that this technology is unreliable from a GDPR perspective. 

  Using Google Consent Mode will inevitably lead to data losses and inaccuracies in its analysis. 

  In other words, it in some sense jeopardises your business.