Recherche avancée

Sur d’autres sites (5333)

• Need help to compile FFmpeg with MSVC tools

  30 janvier 2018, par Antwane

  I need to compile FFmpeg on Windows 10 using MSVC 2017 compiler. I followed some guides from :

  • https://trac.ffmpeg.org/wiki/CompilationGuide/MSVC
  • https://www.ffmpeg.org/platform.html#Microsoft-Visual-C_002b_002b-or-Intel-C_002b_002b-Compiler-for-Windows
  • https://pracucci.com/compile-ffmpeg-on-windows-with-visual-studio-compiler.html

  I installed current stable version of MSYS, fixed link.exe and use of PATH environment, installed make diffutils gcc pkg-config and downloaded c99-to-c89, nasm, and inttypes.h

  I think my environment is now correctly set up, I ran MSYS shell from MSVC Command prompt and have everything reachable.

  $ which cl
  
  /c/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/cl
  
  
  
  $ which link
  
  /c/Program Files (x86)/Microsoft Visual Studio/2017/Professional/VC/Tools/MSVC/14.12.25827/bin/HostX64/x64/link
  
  
  
  $ which yasm
  
  /home/Antoine/bin/yasm
  
  
  
  $ which c99conv
  
  /home/Antoine/bin/c99conv
  
  
  
  $ which c99wrap
  
  /home/Antoine/bin/c99wrap

  Now I configure the build

  $ ./configure --toolchain=msvc
  
  install prefix            /usr/local
  
  source path               .
  
  C compiler                cl
  
  C library                 msvcrt
  
  ARCH                      x86 (generic)
  
  big-endian                no
  
  runtime cpu detection     yes
  
  standalone assembly       yes
  
  x86 assembler             nasm
  
  MMX enabled               yes
  
  MMXEXT enabled            yes
  
  3DNow! enabled            yes
  
  3DNow! extended enabled   yes
  
  SSE enabled               yes
  
  SSSE3 enabled             yes
  
  AESNI enabled             yes
  
  AVX enabled               yes
  
  AVX2 enabled              yes
  
  XOP enabled               yes
  
  FMA3 enabled              yes
  
  FMA4 enabled              yes
  
  i686 features enabled     yes
  
  CMOV is fast              yes
  
  EBX available             no
  
  EBP available             no
  
  debug symbols             yes
  
  strip symbols             no
  
  optimize for size         no
  
  optimizations             yes
  
  static                    yes
  
  shared                    no
  
  postprocessing support    no
  
  network support           yes
  
  threading support         w32threads
  
  safe bitstream reader     yes
  
  texi2html enabled         no
  
  perl enabled              no
  
  pod2man enabled           no
  
  makeinfo enabled          no
  
  makeinfo supports HTML    no
  
  
  
  External libraries:
  
  schannel                 xlib
  
  
  
  External libraries providing hardware acceleration:
  
  cuda                     cuvid                    d3d11va                  dxva2                    nvenc
  
  
  
  Libraries:
  
  avcodec                  avdevice                 avfilter                 avformat                 avutil                   swresample               swscale
  
  
  
  Programs:
  
  ffmpeg                   ffprobe
  
  
  
  [...]
  
  Hundreds of modules, library, etc.
  
  [...]
  
  
  
  License: LGPL version 2.1 or later
  
  Creating configuration files ...
  
  config.h is unchanged
  
  config.asm is unchanged
  
  libavutil/avconfig.h is unchanged
  
  libavcodec/bsf_list.c is unchanged
  
  libavformat/protocol_list.c is unchanged

  But when I run make it stops very quickly

  $ make
  
  Makefile:47: la cible « qt-faststart » ne correspond pas au motif de cible
  
  Makefile:47: la cible « trasher » ne correspond pas au motif de cible
  
  Makefile:47: la cible « uncoded_frame » ne correspond pas au motif de cible
  
  Makefile:91: ffbuild/library.mak: No such file or directory
  
  make: *** Aucune règle pour fabriquer la cible « ffbuild/library.mak ». Arrêt.

  Sorry for the french wording, I don’t know how to tell MSVC print its output in english. Basically, the error means :

  Makefile:47: target « qt-faststart » doesn't match the target pattern
  
  make: *** No rule to make target « ffbuild/library.mak ». Stopped.

  Side notes :

  $ tree ffbuild
  
  ffbuild
  
  ├── config.fate
  
  ├── config.log
  
  ├── config.mak
  
  └── config.sh

  That’s right, library.mak were not generated into ffbuild, but I don’t know why, and configure script didn’t output any error message...

  Does anybody can help me to find out what am I doing wrong ?

  Edit :

  make distclean doesn’t help

  $ make distclean
  
  Makefile:47: la cible « qt-faststart » ne correspond pas au motif de cible
  
  Makefile:47: la cible « trasher » ne correspond pas au motif de cible
  
  Makefile:47: la cible « uncoded_frame » ne correspond pas au motif de cible
  
  Makefile:91: ffbuild/library.mak: No such file or directory
  
  make: *** Aucune règle pour fabriquer la cible « ffbuild/library.mak ». Arrêt.

• How to track Google AdWords campaigns with Matomo

  19 décembre 2017, par InnoCraft

  In 2016, Google AdWords was the most popular ad service on earth. As a result, it may be your first source for ad spending. Are you interested in knowing whether you are making a profit out of it ? Would you like to know how to track users coming from AdWords with Matomo (Piwik) efficiently ? This is what this article is about.

  

  What you need to know about Google AdWords

  By default, each ad you create in Google AdWords is not tracked. Even worse than that, every click on your ad is identified in Matomo (Piwik) as an organic result coming from Google with the following value : “Keyword not defined”.

  To make it simple, if you do not track your AdWords campaigns both your paid and organic traffic will be biased within your Matomo (Piwik) account. It will be impossible for you to measure your return on investment and it means that you are throwing your money down the drain.

  In order to avoid this, we will show you how to track Google AdWords traffic into Matomo (Piwik).

  How to track paid Google AdWords campaigns into Matomo

  If you want to analyze Google AdWords campaigns within Matomo (Piwik) properly, you need to add additional tracking parameters to the final URL of each of your ads.

  We recommend using the following tool to add the needed additional tracking parameters : https://matomo.org/docs/tracking-campaigns-url-builder/

  You will then be able to push additional data to Matomo (Piwik) such as :

  • pk_campaign : the name of your ad campaign
  • pk_kwd : the keyword associated to this campaign
  • pk_source : the source of your campaign
  • pk_medium : the type of source, in our case either cpc, cpm, cpa
  • pk_content : the content of your ad

  If your campaign URL looks like this : https://your-website.com/, your campaign URL will then look like this after adding the campaign parameters :

  https://your-website.com/?pk_campaign=Name-Of-Your-Campaign&pk_kwd=Your-Keyword&pk_source=google&pk_medium=cpc&pk_content=My-Ad-Headline

  As each ad URL can be fired by different keywords and can correspond to different campaigns or headlines, you will need to customize the campaign parameters for each URL.

  Customizing all of your URLs individually would take you a lot of time under circumstances. That’s why you should know, that each URL parameter can be filled automatically in AdWords with a feature called “Tracking template”.

  Simplifying the campaign URL parameters with tracking templates

  You can define tracking templates either at the account, campaign or ad group level. For example, by using a tracking template at the account level, all your campaigns will have the same landing page with the URL parameters you defined in the tracking template. By defining it at the campaign level, it means that all your ad groups within the campaign will have the same landing page and so on and so forth. Any tracking template defined in a campaign, will overwrite a tracking template defined at the account level.

  Tracking template at the account level

  To edit the template at the account level, you need to click on “Settings”, then click on the “Account” settings tab and define your tracking template pattern. For example :

  https://your-website.com/?url={lpurl}&pk_campaign=AdWords&pk_kwd=Your-Keyword&pk_source=google&pk_medium=cpc&pk_content=My-Ad-Headline

  

  This will apply to all your URLs within your account. So it is only useful if your website domain is the same across all your ads. The URL parameter is compulsory here.

  It can be limiting to have a static value for “pk_campaign” and “pk_kwd” so Google allows you to use dynamic insertion, such as follows :

  https://your-landing-page.com/?url={lpurl}&pk_campaign={campaignid}&pk_kwd={keyword}&pk_source=google&pk_medium=cpc&pk_content={creative}

  The “keyword” means that the data is automatically replaced with the keyword which fired the ad within your account.

  Visit the following page if you want to know more about the different dynamic tags that AdWords supports : https://support.google.com/adwords/answer/6305348#urlinsertion

  Tracking template at the campaign level

  If you wish to define a tracking template at the campaign level, you will find this option within the “Campaign” settings under the campaign URL options :

  

  Tracking template at the Ad Group level

  You can also set it at the Ad Group level within the “Ad Group” settings :

  

  As Google mentions : “If you set up URL options at the campaign level, ad group level, or ad level, those settings will override the account-level options“.

  Now that your URLs are properly configured, you will be able to analyze AdWords traffic performances within Matomo (Piwik) once a click is coming from those sources.

  

  Did you like this article ? If yes, do not hesitate to share it or give us your feedback about the topic you would like us to write about.

• How to track Google AdWords campaigns with Piwik

  19 décembre 2017, par InnoCraft

  In 2016, Google AdWords was the most popular ad service on earth. As a result, it may be your first source for ad spending. Are you interested in knowing whether you are making a profit out of it ? Would you like to know how to track users coming from AdWords with Piwik efficiently ? This is what this article is about.

  

  What you need to know about Google AdWords

  By default, each ad you create in Google AdWords is not tracked. Even worse than that, every click on your ad is identified in Piwik as an organic result coming from Google with the following value : “Keyword not defined”.

  To make it simple, if you do not track your AdWords campaigns both your paid and organic traffic will be biased within your Piwik account. It will be impossible for you to measure your return on investment and it means that you are throwing your money down the drain.

  In order to avoid this, we will show you how to track Google AdWords traffic into Piwik.

  How to track paid Google AdWords campaigns into Piwik

  If you want to analyze Google AdWords campaigns within Piwik properly, you need to add additional tracking parameters to the final URL of each of your ads.

  We recommend using the following tool to add the needed additional tracking parameters : https://piwik.org/docs/tracking-campaigns-url-builder/

  You will then be able to push additional data to Piwik such as :

  • pk_campaign : the name of your ad campaign
  • pk_kwd : the keyword associated to this campaign
  • pk_source : the source of your campaign
  • pk_medium : the type of source, in our case either cpc, cpm, cpa
  • pk_content : the content of your ad

  If your campaign URL looks like this : https://your-website.com/, your campaign URL will then look like this after adding the campaign parameters :

  https://your-website.com/?pk_campaign=Name-Of-Your-Campaign&pk_kwd=Your-Keyword&pk_source=google&pk_medium=cpc&pk_content=My-Ad-Headline

  As each ad URL can be fired by different keywords and can correspond to different campaigns or headlines, you will need to customize the campaign parameters for each URL.

  Customizing all of your URLs individually would take you a lot of time under circumstances. That’s why you should know, that each URL parameter can be filled automatically in AdWords with a feature called “Tracking template”.

  Simplifying the campaign URL parameters with tracking templates

  You can define tracking templates either at the account, campaign or ad group level. For example, by using a tracking template at the account level, all your campaigns will have the same landing page with the URL parameters you defined in the tracking template. By defining it at the campaign level, it means that all your ad groups within the campaign will have the same landing page and so on and so forth. Any tracking template defined in a campaign, will overwrite a tracking template defined at the account level.

  Tracking template at the account level

  To edit the template at the account level, you need to click on “Settings”, then click on the “Account” settings tab and define your tracking template pattern. For example :

  https://your-website.com/?url={lpurl}&pk_campaign=AdWords&pk_kwd=Your-Keyword&pk_source=google&pk_medium=cpc&pk_content=My-Ad-Headline

  

  This will apply to all your URLs within your account. So it is only useful if your website domain is the same across all your ads. The URL parameter is compulsory here.

  It can be limiting to have a static value for “pk_campaign” and “pk_kwd” so Google allows you to use dynamic insertion, such as follows :

  https://your-landing-page.com/?url={lpurl}&pk_campaign={campaignid}&pk_kwd={keyword}&pk_source=google&pk_medium=cpc&pk_content={creative}

  The “keyword” means that the data is automatically replaced with the keyword which fired the ad within your account.

  Visit the following page if you want to know more about the different dynamic tags that AdWords supports : https://support.google.com/adwords/answer/6305348#urlinsertion

  Tracking template at the campaign level

  If you wish to define a tracking template at the campaign level, you will find this option within the “Campaign” settings under the campaign URL options :

  

  Tracking template at the Ad Group level

  You can also set it at the Ad Group level within the “Ad Group” settings :

  

  As Google mentions : “If you set up URL options at the campaign level, ad group level, or ad level, those settings will override the account-level options“.

  Now that your URLs are properly configured, you will be able to analyze AdWords traffic performances within Piwik once a click is coming from those sources.

  

  Did you like this article ? If yes, do not hesitate to share it or give us your feedback about the topic you would like us to write about.