Sur d’autres sites (10496)

• How to reduce the bitrate loss from video processing via FFMPEG ?

  17 juin 2017, par Neo Herakles

  so I use this code to add an intro, outro and watermark to a video but the final result has a loss in bitrate from 2108 bps to 705 bps, how can I keep the bitrate in the 2000 bps range ?

  for %%I in ("C:\Users\Administrator\Desktop\work\*.mp4") do ffmpeg.exe
  
  -y -i "%%I" -i white.png -i out1.ts -filter_complex "[1:v][0:v]scale2ref=iw/6:ih/18[logo][0v];[0v][logo]overlay=W-w-3:H-h-1,scale=hd720,setsar=1[vl];[2:v][2:a][vl][0:a][2:v][2:a]concat=n=3:v=1:a=1[v][a]"
  
  -map "[v]" -map "[a]" -r 20 -c:v libx264 -ar 48000 "C:\Users\Administrator\Desktop\Complete-videos\%%~nI.mp4"
  
  
  
  pause

  Thank you for your help.

• How to analyse 404 pages

  1er juillet 2019, par Matomo Core Team — Development, Plugins

  How to analyse “not found” pages (404) in digital analytics

  Have you ever sent out a newsletter and one link wasn’t active yet ? Would you like to know how many users get affected when this happens ? Would you like to know if your visitors are encountering 404 pages ? 

  In this article we’re describing an easy way to analyse “not found” pages on your website with Matomo to increase your visitors’ user experience, user acquisition, and SEO (search engine optimization).

  How to know the number of 404s on my website ?

  There are different ways to get this information. Depending on how your website is built, you may or may not collect this data.

  The easiest way to answer this question is to fire a 404 page on your website, you do this by accessing a wrong url :

  

  As you can see here, in our case, the page title starts with “Page non trouvée” which stands for “Page not found” when translated in English (as the website we are considering here is in French) :

  

  In this example 19 page views have been fired and it generated a bounce rate of 67%. As a result ⅔ of the visits ended here.

  In some cases, the information related to a “not found” page can be found either within the title or within the URL, as some websites redirect you to a specific web page when a page can’t be found.

  If you can’t identify “not found” pages via a page title or a page URL, we strongly advise you to use this specific tracking code method on your 404 page : “How to track error pages in Matomo ?”. 

  You can easily set it with Matomo Tag Manager with a custom HTML tag :

  

  where the trigger is the following :

  

  You will however, have to define this trigger as an exclusion for all the other tags which may conflict with it (here below is the new trigger defined for the generic Matomo tags we are inserting on all pages) :

  

  Once this specific tracking is set, you will be able to track the source of the 404 and will gather all the “not found” pages in a specific group within your Page Title report :

  

  Here, for example, you can identify that the homepage of this website had a link pointing to a 404, in our case it was https://www.webassoc.org/pro-du-web.

  Note that this is just one technique. You could also create a custom dimension report and decide to send the 404 there also.

  How to get notified when a 404 page is visited ?

  Trust us, you’re not going to check everyday whether a 404 page has been visited. In order to avoid checking it manually, you can define custom alerts.

  There are three possible scenarios when “not found” pages can be fired :

  • internal 404 : one link within your website is pointing to a wrong url on the same website.
  • external 404 : someone from an external website made a link to yours and the link is not correct.
  • direct access 404 : someone access directly to a not found page on your website.

  You can define all those three within Matomo, but in your case, you will only have to focus on the first two only. In fact, you can’t really fix the third scenario. That’s the reason why we’re not focusing on it. It would result in irrelevant alerts.

  Custom alert for internal 404

  An internal 404 is defined from a 404 where the source is an internal web page. As a result, it will look like the following in your report :

  

  In this example, we’re using this specific custom implementation, the title of the page will contain “From = https://www.webassoc.org/”. So set our custom alert accordingly :

  

  Now every time a 404 page will be fired from an internal page, you’ll be notified by email.

  Note that you can also decide to not receive any email and track the evolution of alerts with the History of triggered alerts feature.

  Custom alert for external 404

  External 404 is almost the same setup. The only thing you need to keep in mind is that we want to exclude the 404 where the source is not indicated. As a result, your configuration will look like the following :

  

  Here your regular expression pattern is the following one :

  404/URL = .*From = (?!https://www.webassoc.org)[^\s]+

  as you’ll want to have any referrer coming from a website which is not Matomo and not a direct 404.

   

  You can now be notified every time that a 404 is fired from any link.

  Note that this configuration may slightly differ from website to website. So always double check your tracking code and the way the values are sent to your reports. Also try to trigger those alerts first before validating them.

  How to follow the evolution of your 404 over time ?

  It may be interesting to know how good or how bad you are performing in terms of 404.

  In order to check this information, you can click on the evolution icon near the 404 title :

  

  But you may be interested in accessing this information more regularly without having to create this report each time.

  So, one way to analyse the evolution of your 404 is to create a segment such as :

  

  and to click after that on evolution icon :

  

  As you can see below the number of “not found” pages is quite low in general, but we can also notice that a period received an increase in terms of 404 not found pages on May 27. It may be interesting to investigate it :

  

  You can start from the overview of referrers :

  

  As you can notice here the main source of 404 is coming from direct entries which is the most difficult channel to analyse as we don’t really know where the visitors are coming from.

  How to perform your analysis even faster ?

  As you can see analysing reports in Matomo in order to detect 404 pages is a time-consuming activity. In order to make it faster, you can already create a report about it within the Email reports feature with the following settings :

  • Segment : 404
  • Email schedule : never.
  • Visits summary and Page titles as selected report.

  You will then end up with a saved report listing all the URLs concerned :

  

  You can also have a look at the “Custom reports” premium feature.

  It will provide you with more flexibility. You will then be able to focus on the most important thing : the cause of 404.

  Good luck and happy analytics !

• all : use designated initializers for AVOption.unit

  11 février 2024, par Anton Khirnov

  all : use designated initializers for AVOption.unit
  Makes it robust against adding fields before it, which will be useful in
  
  following commits.
  Majority of the patch generated by the following Coccinelle script :
  @@
  
  typedef AVOption ;
  
  identifier arr_name ;
  
  initializer list il ;
  
  initializer list[8] il1 ;
  
  expression tail ;
  
  @@
  
  AVOption arr_name[] =  il,  il1,
  
   tail
  
  + .unit = tail
  
  , ...   ;
  with some manual changes, as the script :
  
  * has trouble with options defined inside macros
  
  * sometimes does not handle options under an #else branch
  
  * sometimes swallows whitespace
  

  • [DH] fftools/ffmpeg_mux_init.c
  • [DH] libavcodec/aacdec_template.c
  • [DH] libavcodec/aacenc.c
  • [DH] libavcodec/ac3dec_float.c
  • [DH] libavcodec/ac3enc.c
  • [DH] libavcodec/amfenc_av1.c
  • [DH] libavcodec/amfenc_h264.c
  • [DH] libavcodec/amfenc_hevc.c
  • [DH] libavcodec/apedec.c
  • [DH] libavcodec/audiotoolboxenc.c
  • [DH] libavcodec/avdct.c
  • [DH] libavcodec/bsf/av1_metadata.c
  • [DH] libavcodec/bsf/dump_extradata.c
  • [DH] libavcodec/bsf/dv_error_marker.c
  • [DH] libavcodec/bsf/filter_units.c
  • [DH] libavcodec/bsf/h264_metadata.c
  • [DH] libavcodec/bsf/h265_metadata.c
  • [DH] libavcodec/bsf/hapqa_extract.c
  • [DH] libavcodec/bsf/prores_metadata.c
  • [DH] libavcodec/bsf/remove_extradata.c
  • [DH] libavcodec/bsf/vp9_metadata.c
  • [DH] libavcodec/cbs_bsf.h
  • [DH] libavcodec/ccaption_dec.c
  • [DH] libavcodec/cfhdenc.c
  • [DH] libavcodec/cuviddec.c
  • [DH] libavcodec/dcadec.c
  • [DH] libavcodec/dnxhdenc.c
  • [DH] libavcodec/dolby_e.c
  • [DH] libavcodec/dxvenc.c
  • [DH] libavcodec/exr.c
  • [DH] libavcodec/exrenc.c
  • [DH] libavcodec/ffv1enc.c
  • [DH] libavcodec/flacenc.c
  • [DH] libavcodec/gif.c
  • [DH] libavcodec/hapenc.c
  • [DH] libavcodec/huffyuvenc.c
  • [DH] libavcodec/j2kenc.c
  • [DH] libavcodec/jpeglsenc.c
  • [DH] libavcodec/libaomenc.c
  • [DH] libavcodec/libaribb24.c
  • [DH] libavcodec/libaribcaption.c
  • [DH] libavcodec/libfdk-aacdec.c
  • [DH] libavcodec/libfdk-aacenc.c
  • [DH] libavcodec/libopenh264enc.c
  • [DH] libavcodec/libopenjpegenc.c
  • [DH] libavcodec/libopusenc.c
  • [DH] libavcodec/libsvtav1.c
  • [DH] libavcodec/libtwolame.c
  • [DH] libavcodec/libvpxenc.c
  • [DH] libavcodec/libwebpenc_common.c
  • [DH] libavcodec/libx264.c
  • [DH] libavcodec/libxavs.c
  • [DH] libavcodec/libxeve.c
  • [DH] libavcodec/libxvid.c
  • [DH] libavcodec/libzvbi-teletextdec.c
  • [DH] libavcodec/ljpegenc.c
  • [DH] libavcodec/magicyuvenc.c
  • [DH] libavcodec/mediacodecenc.c
  • [DH] libavcodec/mfenc.c
  • [DH] libavcodec/mjpegenc.c
  • [DH] libavcodec/mlpenc.c
  • [DH] libavcodec/mpeg12enc.c
  • [DH] libavcodec/mpegvideoenc.h
  • [DH] libavcodec/nvenc_av1.c
  • [DH] libavcodec/nvenc_h264.c
  • [DH] libavcodec/nvenc_hevc.c
  • [DH] libavcodec/omx.c
  • [DH] libavcodec/options.c
  • [DH] libavcodec/options_table.h
  • [DH] libavcodec/opusenc.c
  • [DH] libavcodec/pngenc.c
  • [DH] libavcodec/profiles.h
  • [DH] libavcodec/proresenc_kostya.c
  • [DH] libavcodec/qsvdec.c
  • [DH] libavcodec/qsvenc.h
  • [DH] libavcodec/qsvenc_av1.c
  • [DH] libavcodec/qsvenc_h264.c
  • [DH] libavcodec/qsvenc_hevc.c
  • [DH] libavcodec/qsvenc_mpeg2.c
  • [DH] libavcodec/qsvenc_vp9.c
  • [DH] libavcodec/s302m.c
  • [DH] libavcodec/snowenc.c
  • [DH] libavcodec/svq1enc.c
  • [DH] libavcodec/tiffenc.c
  • [DH] libavcodec/utvideoenc.c
  • [DH] libavcodec/vaapi_encode.h
  • [DH] libavcodec/vaapi_encode_av1.c
  • [DH] libavcodec/vaapi_encode_h264.c
  • [DH] libavcodec/vaapi_encode_h265.c
  • [DH] libavcodec/vaapi_encode_mpeg2.c
  • [DH] libavcodec/vbnenc.c
  • [DH] libavcodec/vc2enc.c
  • [DH] libavcodec/videotoolboxenc.c
  • [DH] libavdevice/bktr.c
  • [DH] libavdevice/caca.c
  • [DH] libavdevice/decklink_dec_c.c
  • [DH] libavdevice/decklink_enc_c.c
  • [DH] libavdevice/iec61883.c
  • [DH] libavdevice/libcdio.c
  • [DH] libavdevice/openal-dec.c
  • [DH] libavdevice/v4l2.c
  • [DH] libavdevice/xcbgrab.c
  • [DH] libavfilter/af_aap.c
  • [DH] libavfilter/af_acrossover.c
  • [DH] libavfilter/af_acrusher.c
  • [DH] libavfilter/af_adeclick.c
  • [DH] libavfilter/af_adenorm.c
  • [DH] libavfilter/af_adynamicequalizer.c
  • [DH] libavfilter/af_aemphasis.c
  • [DH] libavfilter/af_afade.c
  • [DH] libavfilter/af_afftdn.c
  • [DH] libavfilter/af_afir.c
  • [DH] libavfilter/af_afwtdn.c
  • [DH] libavfilter/af_agate.c
  • [DH] libavfilter/af_aiir.c
  • [DH] libavfilter/af_amix.c
  • [DH] libavfilter/af_anequalizer.c
  • [DH] libavfilter/af_anlmdn.c
  • [DH] libavfilter/af_anlms.c
  • [DH] libavfilter/af_aphaser.c
  • [DH] libavfilter/af_apulsator.c
  • [DH] libavfilter/af_arls.c
  • [DH] libavfilter/af_asoftclip.c
  • [DH] libavfilter/af_aspectralstats.c
  • [DH] libavfilter/af_astats.c
  • [DH] libavfilter/af_axcorrelate.c
  • [DH] libavfilter/af_biquads.c
  • [DH] libavfilter/af_bs2b.c
  • [DH] libavfilter/af_deesser.c
  • [DH] libavfilter/af_firequalizer.c
  • [DH] libavfilter/af_flanger.c
  • [DH] libavfilter/af_haas.c
  • [