Sur d’autres sites (7133)

• C# FFmpeg Dynamic-Link Library

  25 juillet 2022, par iltan

  I need FFmpeg as dll for C#. I want to do something like ;

  


  static void Convert(Stream onlyAudioStream, Stream onlyVideoStream, string path)
{
    FFmpegNameSpace.FFmpeg ff = new FFmpegNameSpace.FFmpeg();
    ff.AddInput(onlyAudioStream);
    ff.AddInput(onlyVideoStream);
    ff.Save(path);
}


  


  And the problem is I don't know how can i get ffmpeg dll.

  


  Example :
I did this before in libwebp. Things we need to do to get libwebp dll ;
1- Download libwebp source
2- Open Visual Studio 2019 Developer Tools
3- Run command in libwebp source directory "nmake /f Makefile.vc CFG=release-static RTLIBCFG=static OBJDIR=output"
4- Done you will find dll in output directory

  


  Edit : I searched a lot and couldn't find the solution. I decided to use ffmpeg.exe whenever I need it.
Thank you all

  


• 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

• Easily track Events within Matomo Analytics thanks to Matomo Tag Manager

  7 juin 2019, par Matomo Core Team — Analytics Tips

  Easily track Events within Matomo Analytics thanks to Matomo Tag Manager

  Introduction

  In this article we’ll cover what events in Matomo Analytics are ; and how you can easily set them up thanks to Matomo Tag Manager.

  Key concepts within this article

  • Events
  • Quick definition of the Tag Management System
  • Matomo config
  • Creating triggers
  • Variables

  What are events in Matomo Analytics and why are they useful ?

  Events allow you to measure interactions on your website which are not defined by default. With them you can measure clicks on some elements of a page, such as, how visitors are interacting with dropdown menus, media players, scrolling behaviours etc. You can also use them to define goals which make them a key feature in Matomo Analytics. Learn more about tracking events in Matomo.

  You can easily access the Events report in Matomo Analytics by clicking on the Behaviour category :

  

  And you may read the following message and feel a bit frustrated :

  

  “There is no data for this report” is a nice way to say, “Hey, you are tracking just a tiny part of what Matomo Analytics can do for you.”

  Matomo is a great software, but it can’t guess what you want to track.

  In order for Matomo to register those event tracking interactions, you’ll need to explain it by adding a line of code similar to this one when the interaction happens :

   

  _paq.push(['trackEvent', 'Here you enter whatever you want', 'Here too', 'and here also']);

   

  Let’s imagine you want to track a click on an HTML button, your code will look something similar to this at the moment of the interaction :

  Click Me !

  As you can imagine, two main challenges will arise for non developers :

  1. How to access the source code ?
  2. How to define the interaction ?

  Luckily, Matomo Tag Manager makes those steps easy for you. Let’s see how the same tracking is implemented with Matomo Tag Manager.

  A quick definition of what Matomo Tag Manager is

  Matomo Tag Manager lets you manage all your tracking and marketing tags in one easy-to-access place. Please visit this page to learn more about Matomo Tag Manager. In order to start using it, you’ll need to copy/paste a tracking code, named a “container”, within the section of your pages.

  Once the container is on your website, all you need to do is to follow these simple steps :

  1. Add a Matomo Tag.
  2. Assign the condition to fire the tag (what we call the trigger).
  3. Publish your work.
  4. And enjoy

  1 – Add a Matomo Event tracking code

  All you have to do here is click on “CREATE NEW TAG”

  

  Once selected, just mention how you’d like this tag to be named (it is for your internal purpose here so always use an explicit tag name) and the Matomo configuration (the default configuration setting will be fine in most of the cases) :

  

  Then Matomo Tag Manager will ask you the type of tracking you’d like to deploy, in this case, this is an event so select “Event” :

  

  Then all you need is to indicate the values you’d like to push through your event :

  

  To put it in perspective, all we did here through Matomo Tag Manager was implement the equivalent of the following line of code :

  _paq.push(['trackEvent', 'Element interactions', 'Click button', 'Click Me']);

  Let’s now see how can we do this on click code part which we call a trigger.

  2 – Assign the condition to fire the tag

  In order to execute the event we’ll need to define when it will happen. You do this by clicking on Create a new trigger now :

  

  As the interaction we’d like to track is happening when a click occurs, it will be a click trigger, and as our button is not a link, we’ll select All Elements Click :

  

  Once selected you’ll need to be precise on the condition in which the event will be triggered. In this case we do not want to have events pushed every time someone is clicking on something on our website. We only want to track when they click on this specific button. That’s the reason why our trigger is set to fire only when the click occurs on an element which has an id and has the value “cta” :

  Once you click on the green button named CREATE NEW TRIGGER, you validate the tag by clicking on CREATE NEW TAG :

  

  

  Then you can move to the last part.

  3 – Publish your work

  Tag Managers are very powerful as they allow you to easily execute any JavaScript code, CSS or even text content on your websites.

  That’s why when you create your tag it doesn’t go live straight away on your website. In order to do this you need to publish your tag and this is what the “Publish” category is designed for :

  

  After that, click on the second button if you’re confident your tag and trigger are both ready to go live :

  

  4 – Enjoy

  Well done. As your tag is now live, every click made on this button will now be pushed to your Matomo Analytics account within :
  

  1. The visitor log report :

  

  2. The events report :

  

  You may now be asking, “That’s great, but can I collect something more exciting than clicks ?” 

  Of course you can ! This is what the Matomo Tag Manager is all about.

  As long as you can express it through a trigger you can really push whatever you want to Matomo Analytics. You can track scrolling patterns, an element visible on the page like an image, an ad or the time spent on the page. The options are now open to you with Tag Manager.

  Give them a try ! Change the triggers, start playing around with variables and discover that the possibilities are endless.

  Happy analytics,
  Matomo team