Recherche avancée

Sur d’autres sites (7549)

• Is it possible to use ffmpeg in nwjs native addon in linux ?

  16 octobre 2016, par Sergey Yakimov

  I’ve created native addon for encoding video from IDS camera. It work in nodejs but after rebuilding it with nw-gyp it stop working. I checked available encoders and there is none. When nwjs loads addon I think it using ffmpeg which come with nwjs and it have only few decoders compiled in and no encoders. In nwjs docs they only describe how one can enable h264 codec, but if I understand it right it will work only as decoder.

  So is there a way to make addon use system ffmpeg instead of that what come with nwjs or at least rebuild ffmpeg used in nwjs to include encoders in it ?

• Introducing Matomo SEO Web Vitals

  13 septembre 2021, par Ben Erskine — About, Analytics Tips, Plugins

  SEO Web Vitals track your critical website performance metrics and are a core element of SEO best practice. 

  Start using Matomo SEO Web Vitals to monitor your website performance, optimise your visitor experience, improve your search result rankings, and see how your site compares to your competitors.

  

  What are SEO Web Vitals ?

  Web Vitals are made up of a number of important metrics, such as your website’s page speed and loading performance, these metrics all play an important role in search engine optimisation. 

  The more technical terms for these metrics are Page Speed Score, First Contentful Paint (FCP), Final Input Delay (FID), Last Contentful Paint (LCP) and Cumulative Layout Shift (CLS).

  Why should you use SEO Web Vitals ?

  SEO Web Vitals are being used more and more by search engines such as Google to rank websites so they help ensure a great page experience for users who arrive via links from their search results. 

  By monitoring your SEO Web Vitals you can see how good or bad a single page performs and then prioritise the optimisation of strategically important pages to help improve the ranking position within search engine results.

  For ease of use you can receive regular reports in your email inbox and you can configure custom alerts to automatically notify you when a page score changes significantly. This saves time by not having to check page performance scores manually while ensuring you will be notified should there be any important change that needs to be actioned.

  You should use SEO Web Vitals to understand how your site performance is impacting your overall visitor experience.

  Four key benefits of using SEO Web Vitals :

  Improve your search result rankings

  • SEO Web Vitals are a core element of SEO best practice and directly impact your search rankings.
  • Pages that load quickly and are more stable deliver a better user experience, so they’re ranked higher by search engines.

  Optimise your website visitor experience

  • Know how quickly pages on your website load to ensure you deliver an optimal visitor experience.
  • Identify page stability issues and implement the changes needed to enhance your visitor experience.

  Automate your website performance monitoring

  • Have peace of mind knowing if your metrics decrease, you can find and fix the root cause quickly.
  • Configure performance alerts and get automated reports sent to you.

  Incorporate website performance into your competitor analysis

  • These performance metrics are essentially open for anyone to inspect, so you can measure and benchmark your site against competitors. 

  How can I improve my SEO Web Vitals ?

  There are so many ways to improve these performance metrics, here are five of the common contributing factors.

  1. Your page speed score is a weighted average of your other performance metrics, so focus on improving the underlying metrics that contribute to this score.
  2. Ensure you use a high quality web host with an appropriate plan for your level of traffic to help improve your FCP time.
  3. Try removing large elements that aren’t required on your page to improve your LCP time.
  4. Optimise against Total Blocking Time to Improve your FID score.
  5. Consider using a Layout Shift Debugger to improve Your CLS Score

  Guide to Matomo SEO Web Vitals

  For more information and to learn how to configure SEO Web Vitals in Matomo, check out our full guide to SEO Web Vitals.

  You will learn :

  • What’s required to measure your SEO Web Vitals
  • How to configure SEO Web Vitals
  • How to analyse your SEO Web Vitals
  • How to understanding SEO Web Vitals metrics
  • How to analyse your page’s SEO Web Vitals over time
  • How to improve your SEO Web Vitals
  • How to monitor changes in your scores with custom alerts

  Need more resources ?

  Matomo Plugin SEO Web Vitals

  Matomo SEO Web Vitals FAQs

• Call system package with Go on App Engine Standard

  8 novembre 2019, par reidreid46

  I’m trying to use FFmpeg in a Go application thats running on Google App Engine Standard. I can get this to run locally, when I point to a local instance of the FFmpeg binary using exec.Command()

  cmd := exec.Command(
  
      "/Users/justin/Desktop/conversion/ffmpeg", // this won't work on a remote server
  
      "-i", "pipe:0",
  
      "-ac", "1",
  
      "-codec:a", "libmp3lame",
  
      "-b:a", "48k",
  
      "-ar", "24000",
  
      "-f", "mp3",
  
      "pipe:1",
  
    )
  
  
  
    cmd.Stdin = bytes.NewReader(synthResp.AudioContent)
  
  
  
    var output bytes.Buffer
  
    cmd.Stdout = &output
  
    err = cmd.Run()

  Obviously, this won’t work when I deploy the application, so I need a way to point to a hosted version of the FFmpeg binary. It seems ffmpeg is a system package for the go1.11 App Engine Standard environment.

  What are "System packages" and how do I use them ?
  When I look for documentation, I find a lot of documentation on apt-get, and no documentation on how to use them, App Engine or otherwise. Do I need to install it, or should it already be part of the container(?) that App Engine is running ?

  Do I call it, like I’d call other executables ? If so, that I’d expect this to work, but it doesn’t

  cmd := exec.Command(
  
      "ffmpeg", // <------ what should this be?
  
      "-i", "pipe:0",
  
      "-ac", "1",
  
      "-codec:a", "libmp3lame",
  
      "-b:a", "48k",
  
      "-ar", "24000",
  
      "-f", "mp3",
  
      "pipe:1",
  
    )
  
  
  
    cmd.Stdin = bytes.NewReader(synthResp.AudioContent)
  
  
  
    var output bytes.Buffer
  
    cmd.Stdout = &output
  
    err = cmd.Run()

  Logging err, I see exec: "ffmpeg": executable file not found in $PATH