Recherche avancée

Sur d’autres sites (5952)

• lavc/ccaption_dec : implement real_time option

  9 janvier 2016, par Aman Gupta

  lavc/ccaption_dec : implement real_time option
  This new mode is useful for realtime decoding of closed captions so they
  
  can be display along with mpeg2 frames.
  Closed caption streams contain two major types of captions :
   POPON captions, which are buffered off-screen and displayed
  
    only after EOC (end of caption, aka display buffer)
   PAINTON/ROLLUP captions, which are written to the display as soon as
  
    they arrive.
  In a typical real-time eia608 decoder, commands like EOC (end of
  
  caption ; display buffer), EDM (erase display memory) and EBM (erase
  
  buffered memory) perform their expected functions as soon as the
  
  commands are processed. This is implemented in the real_time branches
  
  added in this commit.
  Before this commit, and in the !real_time branches after this commit,
  
  the decoder cleverly implements its own version of the decoder which is
  
  specifically geared towards buffered decoding. It does so by actively
  
  ignoring commands like EBM (erase buffered memory), and then re-using
  
  the non-display buffer to hold the previous caption while the new one is
  
  received. This is the opposite of the real-time decoder, which uses the
  
  non-display buffer to hold the new caption while the display buffer is
  
  still showing the current caption.
  In addition to ignoring EBM, the buffered decoder also has custom
  
  implementations for EDM and EOC. An EDM (erase display memory) command
  
  flushes the existing contents before clearing the screen, and EOC
  
  similarly always flushes the active buffer (the previous subtitle)
  
  before flipping buffers.
  

  • [DH] libavcodec/ccaption_dec.c

• lavd/v4l2 : don’t use avpriv_ prefix for internal functions

  21 octobre 2014, par James Almer

  lavd/v4l2 : don’t use avpriv_ prefix for internal functions
  No need to keep the old symbols around until a major bump since lavd functions
  
  with the avpriv_ prefix were never exposed.
  Signed-off-by : James Almer <jamrial@gmail.com>
  
  Reviewed-by : Derek Buitenhuis <derek.buitenhuis@gmail.com>
  
  Reviewed-by : Stefano Sabatini <stefasab@gmail.com>
  
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavdevice/v4l2-common.c
  • [DH] libavdevice/v4l2-common.h
  • [DH] libavdevice/v4l2.c
  • [DH] libavdevice/v4l2enc.c

• Piwik now integrated within CloudFlare

  8 novembre 2017, par Piwik Core Team — Development

  Would you like to know some quick fix in order to make your website load faster ? Would you like your users to have a better experience on your website ? One answer to that is what we call a CDN. Content Delivery Network (CDN) is a system of distributed servers that deliver content to a user based on various criterias such as geolocation.

  And the good news for you is that Piwik got recently integrated to a popular CDN : CloudFlare.

  What is CloudFlare ?

  As previously said, CloudFlare is a content delivery network (CDN).

  

  The three major advantages of using CloudFlare as a CDN are :

  • it is making your website load faster by providing a nearby location to your files to users
  • it also help detecting potential attacks like DDoS and takes away these risks for you
  • it runs one of the largest, fastest, and most reliable managed DNS service in the world

  Automatically add Piwik tracking code to your website

  With the integration of Piwik to CloudFlare, you can now deploy the Piwik tracking code directly through your CloudFlare account instead of tweaking the source code of your website.

  In order to do that, all you need is to log in to your CloudFlare account and click on “Apps”. Then look for Piwik within the search bar :

  

  Once done, click on “Preview” on your site to enter your credentials (Piwik URL and website ID) :

  

  Click “install” to finish the setup. The Piwik tracking code is now installed on each page of your website.

  If you have previously added the tracking code manually to your website and now use the Piwik app, don’t forget to remove the tracking code from your website. Otherwise you end up tracking every user twice.

  Important note : the Piwik CloudFlare integration only concerns the Piwik tracking code integration. For the Piwik app on Cloudflare to work you will need to have a running Piwik installed on your server, or you can start a free trial on the Piwik Analytics Cloud.

  To learn more about what Piwik integration to CloudFlare can do for you.