Recherche avancée

Médias (1)

Mot : - Tags -/musée

Autres articles (97)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

Sur d’autres sites (8657)

  • 5 perfect feature combinations to use with Heatmaps and Session Recordings

    28 janvier 2020, par Jake Thornton — Uncategorized

    Gaining valuable insights by simply creating a heatmap or setting up recordings on your most important web pages is a good start, but using the Heatmaps and Session Recordings features in combination with other Matomo features is where the real magic happens.

    If you’re serious about significantly increasing conversions on your website to impact your bottom line, you need to accurately answer these questions :

    With Matomo Analytics, you have the ability to integrate heatmaps and session recordings with all the features of a powerful web analytics platform, which means you get the complete picture of your visitor’s experience of your website.

    Here are five features that work with Heatmaps and Session Recordings to maximise conversions :

    1. Behaviour feature with Heatmaps

    Before creating heatmaps on pages you think are most important to your website, first check out Behaviour – Pages. Here you get valuable information around unique pageviews, bounce rate, average time on page and exit rates for every page on your website.

    Use this data as your starting point for heatmaps. Here you’ll identify current pain points for your visitors before using heatmaps to analyse their interactions on these pages.

    Here’s how to use the behaviour feature to determine which pages to setup heatmaps on :

    • Make sure you know what pages are generating the most unique page views, it could be your blog rather than your homepage
    • Which pages have the highest bounce rates – can you make some quick changes above-the-fold and see if this makes a difference
    • When the average time on page is high, why are visitors so engaged with these pages ? What keeps them reading ? Setup a heatmap to learn more
    • Reduce exit rates by moving them along to other pages on your website
    • Determine some milestones you want to achieve e.g. use heatmaps as your visual guide to improve average time on page, bounce rates and exit rates. A milestone could be that the exit rate for your previous blog was 34%, work towards getting this down to 30%

    2. Ecommerce feature and Custom Segments

    If you run an ecommerce business, you may want to learn only about visitors who are more likely to be your customers. For example, if you find 65% of product sales come from customers based in New York, but visits to your product pages are from every state in the USA, how can you learn more specifically about visitors only from New York ?

    Using Segments to target a particular audience :

    • First, make sure you have created heatmaps and recordings on the popular product pages you want to learn about your visitor’s interactions
    • Note : Make sure the segment you create generates enough pageviews to apply a heatmap for more accurate results. We recommend a minimum of 1,000 page views per sample size.
    • Then create a custom Segment – search Ecommerce and find the Product Name and select the product. Learn how to do this here.

    Click on ‘Add a new segment’ or on the ‘edit’ link next to an existing segment name to open the segment editor :

    Click on any item on the left to see the list of information you can segment by. In this case search “City”, then select “Is” and in the third column search “New York” (example in the image above) :

    You can also use the search box at the bottom to search through the whole list.

    • This will give you insights across the Matomo platform based only on customers who purchased this product
    • Then go to the Ecommerce feature – and find Sales. Here you will learn what your most popular locations are for your product sales.
    • Once you know the location you want to segment, go back and update the custom Segment you just created. Click on the edit pencil icon and update it by selecting Add AND condition, and add the sub group you would like to track on the product page. In this example, select City – New York. Click Save & Apply.

    Now you should have successfully created a segment for your popular product page with visitors only from New York.

    Check out the heatmap or recordings you created for this page. You may be very surprised to see how this segment engaged with your website compared to all website visitors.

    Note : If you run a lead generation website you can use the Goals feature instead of Ecommerce to track the success metrics you need.

    3. Visitor Profiles within Session Recordings

    Seeing visitor location, device, OS and browser for your recordings is very valuable, but it’s even more valuable to integrate visitor profiles with session recordings as you get to see everything that visitor has done on your website … ever ! 

    What pages they visited before/after the recording, what actions they took, how long they spent on your website etc. All this is captured in the visitor profile of every individual session recording so you can see where exactly engaged viewers are in their journey with your business, for example :

    • How has this visitor behaved on your website in the past ? 
    • Is this visitor already a customer ? 
    • Is this the visitors first time to your website and
    • What other pages on your website are they interested in seeing in this session ?

    Use the visitor profiles feature within session recordings to understand the users better when watching each session.

    You get the full picture of what role the page you recorded played in the overall experience of your website’s visitor. And more importantly, to see if they took the desired action you wanted them to take.

    4. Funnels feature (premium feature)

    The Funnels feature lets you see the customer journey from the first entry page through to the conversion page.

    Once you create a funnel, you can see the % of visitors who drop off between pages on their way to converting.

    In our example, you may then see page one to page two has a drop-off rate of 47%. Page two to page three 95% users drop-off rate and page three to page four 97.3% users drop-off rate.

    Why is the drop-off rate so high from page two to page three and why is the drop-off rate so low from page three to page four ?

    So, you may need to simplify things on page one because you may unknowingly be offering your visitor an easy way out of the funnel. Maybe the visitor is stuck reading your content and not understanding the value of your offering.

    Small tip for session recordings …

    With session recordings especially you can see firsthand through live recordings where exactly visitors click away from the page which exits them from your conversion funnel. Take note to see if this is a recurring issue with other visitors, then take action into fixing this hole.

    Whatever the case, work towards reducing drop-off rates through your conversion funnels by discovering where the problems exist, make changes and learn how these changes affect engagement through heatmaps and recordings.

    5. A/B Testing feature (premium feature)

    Following on from the example with the Funnels feature, once you identify there is a problem in your conversion funnel, how do you know what is preventing visitors from taking an action that pushes them to the next page in the funnel ? You need to test different variations of content to see what works best for your visitors.

    A/B Testing lets you test a variety of things, including :

    • different headlines 
    • less copy vs more copy 
    • different call-to-actions
    • different colour schemes
    • entirely different page layouts

    Once you’ve created two or more variations of specific landing pages in the conversion funnel, see how visitors interacted differently between the variations of landing pages through your heatmaps and recordings.

    You may see that your visitors have scrolled further down the page because more content was provided or an important CTA button was clicked more due to a colour change. Whatever the case, using A/B testing with heatmaps and session recordings is an effective combination for increasing user engagement.

    The conversion rate optimization (CRO) strategy

    CRO is the process of learning what the most valuable content/aspect of your website is and how to best optimize this for your visitors to increase conversion chances. 

    Heatmaps and session recordings play a vital role in this strategy, but it’s how you work these features in tandem with other valuable Matomo features that will give you the most actionable insights you need to grow your business.

    Want to learn how to create an effective CRO strategy ?

  • FFMPEG - How to pipe RMS_level and pts_time metadata without generating unwanted metadata

    6 février 2020, par Tovi Newman

    I am trying to find the loudest (highest rms_level) moment in an audio file, but I need to pipe the metadata rather than write to a file.

    I converted the answer found here : [https://superuser.com/questions/1183663/determining-audio-level-peaks-with-ffmpeg][1]

    By removing the write to file command and adding a pipe.
    Here’s what I’ve got.

    ffmpeg -i loudSoft.mp3 -af astats=metadata=1:reset=1,ametadata=print:key=lavfi.astats.Overall.RMS_level -f null - 2> result.txt

    The only problem is, now I’ve got a lot of unwanted metadata before and after the RMS_level and pts_time data as well as [Parsed_ametadata_1 @ 0x7f9d42c37500] being printed on each line. None of that was being written when I was writing to a file instead of piping. (all I need is the time and the rms.)

    Here is an abridged version of what I get when I write to file :

    frame:0    pts:0       pts_time:0
    lavfi.astats.Overall.RMS_level=-inf
    frame:1    pts:47      pts_time:0.00106576
    lavfi.astats.Overall.RMS_level=-165.163347
    frame:2    pts:1199    pts_time:0.0271882
    lavfi.astats.Overall.RMS_level=-99.736394
    frame:3    pts:2351    pts_time:0.0533107
    lavfi.astats.Overall.RMS_level=-88.112282
    frame:4    pts:3503    pts_time:0.0794331
    lavfi.astats.Overall.RMS_level=-86.554314
    frame:5    pts:4655    pts_time:0.105556
    lavfi.astats.Overall.RMS_level=-82.977501
    frame:6    pts:5807    pts_time:0.131678
    lavfi.astats.Overall.RMS_level=-79.698739
    frame:7    pts:6959    pts_time:0.1578
    lavfi.astats.Overall.RMS_level=-76.629393
    frame:8    pts:8111    pts_time:0.183923
    lavfi.astats.Overall.RMS_level=-71.581211
    frame:9    pts:9263    pts_time:0.210045
    lavfi.astats.Overall.RMS_level=-75.038503
    frame:10   pts:10415   pts_time:0.236168

    And here is what I’m looking at :

    ffmpeg version 4.2.2 Copyright (c) 2000-2019 the FFmpeg developers
     built with Apple clang version 11.0.0 (clang-1100.0.33.16)
     configuration: --prefix=/usr/local/Cellar/ffmpeg/4.2.2_1 --enable-shared --enable-pthreads --enable-version3 --enable-avresample --cc=clang --host-cflags='-I/Library/Java/JavaVirtualMachines/adoptopenjdk-13.0.1.jdk/Contents/Home/include -I/Library/Java/JavaVirtualMachines/adoptopenjdk-13.0.1.jdk/Contents/Home/include/darwin -fno-stack-check' --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libmp3lame --enable-libopus --enable-librubberband --enable-libsnappy --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librtmp --enable-libspeex --enable-libsoxr --enable-videotoolbox --disable-libjack --disable-indev=jack
     libavutil      56. 31.100 / 56. 31.100
     libavcodec     58. 54.100 / 58. 54.100
     libavformat    58. 29.100 / 58. 29.100
     libavdevice    58.  8.100 / 58.  8.100
     libavfilter     7. 57.100 /  7. 57.100
     libavresample   4.  0.  0 /  4.  0.  0
     libswscale      5.  5.100 /  5.  5.100
     libswresample   3.  5.100 /  3.  5.100
     libpostproc    55.  5.100 / 55.  5.100
    Input #0, mp3, from 'loudSoft2.mp3':
     Metadata:
       encoder         : Lavf58.29.100
     Duration: 00:00:09.85, start: 0.025057, bitrate: 128 kb/s
       Stream #0:0: Audio: mp3, 44100 Hz, stereo, fltp, 128 kb/s
       Metadata:
         encoder         : Lavc58.54
    Stream mapping:
     Stream #0:0 -> #0:0 (mp3 (mp3float) -> pcm_s16le (native))
    Press [q] to stop, [?] for help
    [Parsed_ametadata_1 @ 0x7f9d42c37500] frame:0    pts:0       pts_time:0
    [Parsed_ametadata_1 @ 0x7f9d42c37500] lavfi.astats.Overall.RMS_level=-inf
    Output #0, null, to 'pipe:':
     Metadata:
       encoder         : Lavf58.29.100
       Stream #0:0: Audio: pcm_s16le, 44100 Hz, stereo, s16, 1411 kb/s
       Metadata:
         encoder         : Lavc58.54.100 pcm_s16le
    [Parsed_ametadata_1 @ 0x7f9d42c37500] frame:1    pts:47      pts_time:0.00106576
    [Parsed_ametadata_1 @ 0x7f9d42c37500] lavfi.astats.Overall.RMS_level=-165.163347
    [Parsed_ametadata_1 @ 0x7f9d42c37500] frame:2    pts:1199    pts_time:0.0271882
    [Parsed_ametadata_1 @ 0x7f9d42c37500] lavfi.astats.Overall.RMS_level=-99.736394
    [Parsed_ametadata_1 @ 0x7f9d42c37500] frame:3    pts:2351    pts_time:0.0533107


    *** MIDDLE OMITTED FOR BREVITY ***


    [Parsed_ametadata_1 @ 0x7f9d42c37500] lavfi.astats.Overall.RMS_level=-88.532185
    [Parsed_ametadata_1 @ 0x7f9d42c37500] frame:375  pts:430895  pts_time:9.77086
    [Parsed_ametadata_1 @ 0x7f9d42c37500] lavfi.astats.Overall.RMS_level=-88.594276
    [Parsed_ametadata_1 @ 0x7f9d42c37500] frame:376  pts:432047  pts_time:9.79698
    [Parsed_ametadata_1 @ 0x7f9d42c37500] lavfi.astats.Overall.RMS_level=-88.654138
    size=N/A time=00:00:09.82 bitrate=N/A speed=82.6x    
    video:0kB audio:1692kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
    [Parsed_astats_0 @ 0x7f9d42c37280] Channel: 1
    [Parsed_astats_0 @ 0x7f9d42c37280] DC offset: 0.000001
    [Parsed_astats_0 @ 0x7f9d42c37280] Min level: -0.000106
    [Parsed_astats_0 @ 0x7f9d42c37280] Max level: 0.000115
    [Parsed_astats_0 @ 0x7f9d42c37280] Min difference: 0.000000
    [Parsed_astats_0 @ 0x7f9d42c37280] Max difference: 0.000077
    [Parsed_astats_0 @ 0x7f9d42c37280] Mean difference: 0.000017
    [Parsed_astats_0 @ 0x7f9d42c37280] RMS difference: 0.000022
    [Parsed_astats_0 @ 0x7f9d42c37280] Peak level dB: -78.752617
    [Parsed_astats_0 @ 0x7f9d42c37280] RMS level dB: -88.654138
    [Parsed_astats_0 @ 0x7f9d42c37280] RMS peak dB: -88.654138
    [Parsed_astats_0 @ 0x7f9d42c37280] RMS trough dB: -88.654138
    [Parsed_astats_0 @ 0x7f9d42c37280] Crest factor: 3.126627
    [Parsed_astats_0 @ 0x7f9d42c37280] Flat factor: 0.000000
    [Parsed_astats_0 @ 0x7f9d42c37280] Peak count: 2
    [Parsed_astats_0 @ 0x7f9d42c37280] Bit depth: 32/32
    [Parsed_astats_0 @ 0x7f9d42c37280] Dynamic range: 76.274252
    [Parsed_astats_0 @ 0x7f9d42c37280] Zero crossings: 246
    [Parsed_astats_0 @ 0x7f9d42c37280] Zero crossings rate: 0.222624
    [Parsed_astats_0 @ 0x7f9d42c37280] Number of NaNs: 0
    [Parsed_astats_0 @ 0x7f9d42c37280] Number of Infs: 0
    [Parsed_astats_0 @ 0x7f9d42c37280] Number of denormals: 0
    [Parsed_astats_0 @ 0x7f9d42c37280] Channel: 2
    [Parsed_astats_0 @ 0x7f9d42c37280] DC offset: 0.000001
    [Parsed_astats_0 @ 0x7f9d42c37280] Min level: -0.000106
    [Parsed_astats_0 @ 0x7f9d42c37280] Max level: 0.000115
    [Parsed_astats_0 @ 0x7f9d42c37280] Min difference: 0.000000
    [Parsed_astats_0 @ 0x7f9d42c37280] Max difference: 0.000077
    [Parsed_astats_0 @ 0x7f9d42c37280] Mean difference: 0.000017
    [Parsed_astats_0 @ 0x7f9d42c37280] RMS difference: 0.000022
    [Parsed_astats_0 @ 0x7f9d42c37280] Peak level dB: -78.752617
    [Parsed_astats_0 @ 0x7f9d42c37280] RMS level dB: -88.654138
    [Parsed_astats_0 @ 0x7f9d42c37280] RMS peak dB: -88.654138
    [Parsed_astats_0 @ 0x7f9d42c37280] RMS trough dB: -88.654138
    [Parsed_astats_0 @ 0x7f9d42c37280] Crest factor: 3.126627
    [Parsed_astats_0 @ 0x7f9d42c37280] Flat factor: 0.000000
    [Parsed_astats_0 @ 0x7f9d42c37280] Peak count: 2
    [Parsed_astats_0 @ 0x7f9d42c37280] Bit depth: 32/32
    [Parsed_astats_0 @ 0x7f9d42c37280] Dynamic range: 76.274252
    [Parsed_astats_0 @ 0x7f9d42c37280] Zero crossings: 246
    [Parsed_astats_0 @ 0x7f9d42c37280] Zero crossings rate: 0.222624
    [Parsed_astats_0 @ 0x7f9d42c37280] Number of NaNs: 0
    [Parsed_astats_0 @ 0x7f9d42c37280] Number of Infs: 0
    [Parsed_astats_0 @ 0x7f9d42c37280] Number of denormals: 0
    [Parsed_astats_0 @ 0x7f9d42c37280] Overall
    [Parsed_astats_0 @ 0x7f9d42c37280] DC offset: 0.000001
    [Parsed_astats_0 @ 0x7f9d42c37280] Min level: -0.000106
    [Parsed_astats_0 @ 0x7f9d42c37280] Max level: 0.000115
    [Parsed_astats_0 @ 0x7f9d42c37280] Min difference: 0.000000
    [Parsed_astats_0 @ 0x7f9d42c37280] Max difference: 0.000077
    [Parsed_astats_0 @ 0x7f9d42c37280] Mean difference: 0.000017
    [Parsed_astats_0 @ 0x7f9d42c37280] RMS difference: 0.000022
    [Parsed_astats_0 @ 0x7f9d42c37280] Peak level dB: -78.752617
    [Parsed_astats_0 @ 0x7f9d42c37280] RMS level dB: -88.654138
    [Parsed_astats_0 @ 0x7f9d42c37280] RMS peak dB: -88.654138
    [Parsed_astats_0 @ 0x7f9d42c37280] RMS trough dB: -88.654138
    [Parsed_astats_0 @ 0x7f9d42c37280] Flat factor: 0.000000
    [Parsed_astats_0 @ 0x7f9d42c37280] Peak count: 2.000000
    [Parsed_astats_0 @ 0x7f9d42c37280] Bit depth: 32/32
    [Parsed_astats_0 @ 0x7f9d42c37280] Number of samples: 1105
    [Parsed_astats_0 @ 0x7f9d42c37280] Number of NaNs: 0.000000
    [Parsed_astats_0 @ 0x7f9d42c37280] Number of Infs: 0.000000
    [Parsed_astats_0 @ 0x7f9d42c37280] Number of denormals: 0.000000
  • pip install av produces a LINK 1181 error

    6 février 2020, par user8606643

    initially, pip install av asked me to download visual C++ 14 build tools which I did
    but it is still showing me LINK 1181 errors

    I need this pyAV pakcage which is obtained by pip install av for a project, but it always shows some kind of error linked with C++ and i also have ffmpeg installed.

    C:\Users\manop>pip install av
    Collecting av
     Using cached av-7.0.0.tar.gz (2.3 MB)
    Building wheels for collected packages: av
     Building wheel for av (setup.py) ... error
     ERROR: Command errored out with exit status 1:
      command: 'c:\users\manop\appdata\local\programs\python\python37\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\\Users\\manop\\AppData\\Local\\Temp\\pip-install-rydo0uqj\\av\\setup.py'"'"'; __file__='"'"'C:\\Users\\manop\\AppData\\Local\\Temp\\pip-install-rydo0uqj\\av\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d 'C:\Users\manop\AppData\Local\Temp\pip-wheel-oti9y28m'
          cwd: C:\Users\manop\AppData\Local\Temp\pip-install-rydo0uqj\av\
     Complete output (38 lines):
     running bdist_wheel
     running build
     running build_py
     creating build
     creating build\lib.win-amd64-3.7
     creating build\lib.win-amd64-3.7\av
     copying av\datasets.py -> build\lib.win-amd64-3.7\av
     copying av\deprecation.py -> build\lib.win-amd64-3.7\av
     copying av\__init__.py -> build\lib.win-amd64-3.7\av
     copying av\__main__.py -> build\lib.win-amd64-3.7\av
     creating build\lib.win-amd64-3.7\av\audio
     copying av\audio\__init__.py -> build\lib.win-amd64-3.7\av\audio
     creating build\lib.win-amd64-3.7\av\codec
     copying av\codec\__init__.py -> build\lib.win-amd64-3.7\av\codec
     creating build\lib.win-amd64-3.7\av\container
     copying av\container\__init__.py -> build\lib.win-amd64-3.7\av\container
     creating build\lib.win-amd64-3.7\av\data
     copying av\data\__init__.py -> build\lib.win-amd64-3.7\av\data
     creating build\lib.win-amd64-3.7\av\filter
     copying av\filter\__init__.py -> build\lib.win-amd64-3.7\av\filter
     creating build\lib.win-amd64-3.7\av\sidedata
     copying av\sidedata\__init__.py -> build\lib.win-amd64-3.7\av\sidedata
     creating build\lib.win-amd64-3.7\av\subtitles
     copying av\subtitles\__init__.py -> build\lib.win-amd64-3.7\av\subtitles
     creating build\lib.win-amd64-3.7\av\video
     copying av\video\__init__.py -> build\lib.win-amd64-3.7\av\video
     running build_ext
     running config
     writing build\temp.win-amd64-3.7\Release\include\pyav\config.h
     running cythonize
     building 'av.buffer' extension
     creating build\temp.win-amd64-3.7\Release\src
     creating build\temp.win-amd64-3.7\Release\src\av
     C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\cl.exe /c /nologo /Ox /W3 /GL /DNDEBUG /MD -Ic:\users\manop\appdata\local\programs\python\python37\include -Ibuild\temp.win-amd64-3.7\Release\include -Iinclude -Ic:\users\manop\appdata\local\programs\python\python37\include -Ic:\users\manop\appdata\local\programs\python\python37\include -Ibuild\temp.win-amd64-3.7\Release\include "-IC:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.16.27023\Include" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\ucrt" /Tcsrc\av\buffer.c /Fobuild\temp.win-amd64-3.7\Release\src\av\buffer.obj
     buffer.c
     C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\link.exe /nologo /INCREMENTAL:NO /LTCG /DLL /MANIFEST:EMBED,ID=2 /MANIFESTUAC:NO /LIBPATH:c:\users\manop\appdata\local\programs\python\python37\PCbuild\amd64 /LIBPATH:c:\users\manop\appdata\local\programs\python\python37\libs /LIBPATH:c:\users\manop\appdata\local\programs\python\python37\libs /LIBPATH:c:\users\manop\appdata\local\programs\python\python37\PCbuild\amd64 "/LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.16.27023\Lib\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.18362.0\um\x64" /LIBPATH:C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319 "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.18362.0\ucrt\x64" swresample.lib swscale.lib avdevice.lib avutil.lib avcodec.lib avformat.lib avfilter.lib /EXPORT:PyInit_buffer build\temp.win-amd64-3.7\Release\src\av\buffer.obj /OUT:build\lib.win-amd64-3.7\av\buffer.cp37-win_amd64.pyd /IMPLIB:build\temp.win-amd64-3.7\Release\src\av\buffer.cp37-win_amd64.lib /OPT:NOREF
     LINK : fatal error LNK1181: cannot open input file 'swresample.lib'
     error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.16.27023\\bin\\HostX64\\x64\\link.exe' failed with exit status 1181
     ----------------------------------------
     ERROR: Failed building wheel for av
     Running setup.py clean for av
    Failed to build av
    Installing collected packages: av
       Running setup.py install for av ... error
       ERROR: Command errored out with exit status 1:
        command: 'c:\users\manop\appdata\local\programs\python\python37\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\\Users\\manop\\AppData\\Local\\Temp\\pip-install-rydo0uqj\\av\\setup.py'"'"'; __file__='"'"'C:\\Users\\manop\\AppData\\Local\\Temp\\pip-install-rydo0uqj\\av\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record 'C:\Users\manop\AppData\Local\Temp\pip-record-xac0xiy4\install-record.txt' --single-version-externally-managed --compile --install-headers 'c:\users\manop\appdata\local\programs\python\python37\Include\av'
            cwd: C:\Users\manop\AppData\Local\Temp\pip-install-rydo0uqj\av\
       Complete output (38 lines):
       running install
       running build
       running build_py
       creating build
       creating build\lib.win-amd64-3.7
       creating build\lib.win-amd64-3.7\av
       copying av\datasets.py -> build\lib.win-amd64-3.7\av
       copying av\deprecation.py -> build\lib.win-amd64-3.7\av
       copying av\__init__.py -> build\lib.win-amd64-3.7\av
       copying av\__main__.py -> build\lib.win-amd64-3.7\av
       creating build\lib.win-amd64-3.7\av\audio
       copying av\audio\__init__.py -> build\lib.win-amd64-3.7\av\audio
       creating build\lib.win-amd64-3.7\av\codec
       copying av\codec\__init__.py -> build\lib.win-amd64-3.7\av\codec
       creating build\lib.win-amd64-3.7\av\container
       copying av\container\__init__.py -> build\lib.win-amd64-3.7\av\container
       creating build\lib.win-amd64-3.7\av\data
       copying av\data\__init__.py -> build\lib.win-amd64-3.7\av\data
       creating build\lib.win-amd64-3.7\av\filter
       copying av\filter\__init__.py -> build\lib.win-amd64-3.7\av\filter
       creating build\lib.win-amd64-3.7\av\sidedata
       copying av\sidedata\__init__.py -> build\lib.win-amd64-3.7\av\sidedata
       creating build\lib.win-amd64-3.7\av\subtitles
       copying av\subtitles\__init__.py -> build\lib.win-amd64-3.7\av\subtitles
       creating build\lib.win-amd64-3.7\av\video
       copying av\video\__init__.py -> build\lib.win-amd64-3.7\av\video
       running build_ext
       running config
       writing build\temp.win-amd64-3.7\Release\include\pyav\config.h
       running cythonize
       building 'av.buffer' extension
       creating build\temp.win-amd64-3.7\Release\src
       creating build\temp.win-amd64-3.7\Release\src\av
       C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\cl.exe /c /nologo /Ox /W3 /GL /DNDEBUG /MD -Ibuild\temp.win-amd64-3.7\Release\include -Iinclude -Ic:\users\manop\appdata\local\programs\python\python37\include -Ic:\users\manop\appdata\local\programs\python\python37\include -Ic:\users\manop\appdata\local\programs\python\python37\include -Ibuild\temp.win-amd64-3.7\Release\include "-IC:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.16.27023\Include" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\ucrt" /Tcsrc\av\buffer.c /Fobuild\temp.win-amd64-3.7\Release\src\av\buffer.obj
       buffer.c
       C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64\link.exe /nologo /INCREMENTAL:NO /LTCG /DLL /MANIFEST:EMBED,ID=2 /MANIFESTUAC:NO /LIBPATH:c:\users\manop\appdata\local\programs\python\python37\PCbuild\amd64 /LIBPATH:c:\users\manop\appdata\local\programs\python\python37\libs /LIBPATH:c:\users\manop\appdata\local\programs\python\python37\libs /LIBPATH:c:\users\manop\appdata\local\programs\python\python37\PCbuild\amd64 "/LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.16.27023\Lib\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.18362.0\um\x64" /LIBPATH:C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319 "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.18362.0\ucrt\x64" avutil.lib avfilter.lib swresample.lib swscale.lib avformat.lib avcodec.lib avdevice.lib /EXPORT:PyInit_buffer build\temp.win-amd64-3.7\Release\src\av\buffer.obj /OUT:build\lib.win-amd64-3.7\av\buffer.cp37-win_amd64.pyd /IMPLIB:build\temp.win-amd64-3.7\Release\src\av\buffer.cp37-win_amd64.lib /OPT:NOREF
       LINK : fatal error LNK1181: cannot open input file 'avutil.lib'
       error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.16.27023\\bin\\HostX64\\x64\\link.exe' failed with exit status 1181
       ----------------------------------------
    ERROR: Command errored out with exit status 1: 'c:\users\manop\appdata\local\programs\python\python37\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\\Users\\manop\\AppData\\Local\\Temp\\pip-install-rydo0uqj\\av\\setup.py'"'"'; __file__='"'"'C:\\Users\\manop\\AppData\\Local\\Temp\\pip-install-rydo0uqj\\av\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record 'C:\Users\manop\AppData\Local\Temp\pip-record-xac0xiy4\install-record.txt' --single-version-externally-managed --compile --install-headers 'c:\users\manop\appdata\local\programs\python\python37\Include\av' Check the logs for full command output.

    These are my visual C++ selections :
    my visual studio installer individual components selection