Recherche avancée

Sur d’autres sites (6512)

• avcodec/aacdec_fixed : Move fixed-point sinewin tables to its only user

  30 décembre 2020, par Andreas Rheinhardt

  avcodec/aacdec_fixed : Move fixed-point sinewin tables to its only user
  The fixed-point AAC decoder is the only user of the fixed-point sinewin
  
  tables from sinewin ; and it only uses a few of them (about 10% when
  
  counting by size). This means that guarding initializing these tables by
  
  an AVOnce (as done in 3719122065863f701026632f610175980d42b05a) is
  
  unnecessary for them. Furthermore the array of pointers to the
  
  individual arrays is also unneeded.
  Therefore this commit moves these tables directly into aacdec_fixed.c ;
  
  this is done by ridding the original sinewin.h and sinewin_tablegen.h
  
  headers completely of any fixed-point code at the cost of a bit of
  
  duplicated code (the alternative is an ugly ifdef-mess).
  This saves about 58KB from the binary when using hardcoded tables (as
  
  these tables are hardcoded in this scenario) ; when not using hardcoded
  
  tables, most of these savings only affect the .bss segment, but the rest
  
  (< 1KB) contains relocations (i.e. savings in .data.rel.ro).
  Reviewed-by : Lynne <dev@lynne.ee>
  
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] configure
  • [DH] libavcodec/Makefile
  • [DH] libavcodec/aac_defines.h
  • [DH] libavcodec/aacdec_fixed.c
  • [DH] libavcodec/aacdec_template.c
  • [DH] libavcodec/sinewin.c
  • [DH] libavcodec/sinewin.h
  • [DH] libavcodec/sinewin_fixed.c
  • [DH] libavcodec/sinewin_fixed_tablegen.c
  • [DH] libavcodec/sinewin_fixed_tablegen.h
  • [DH] libavcodec/sinewin_tablegen.c
  • [DH] libavcodec/sinewin_tablegen.h
  • [DH] libavcodec/sinewin_tablegen_template.c

• The ultimate solution to knowing how your business is performing overall

  8 janvier 2018, par InnoCraft — Community, Plugins

  Would you like to know how your business is performing overall at a glance ? Guess what, you can now do this easily with Roll-Up Reporting.

  What is Roll-Up Reporting about ?

  Roll-Up Reporting is a premium feature which you can acquire through the Piwik Marketplace. Developed by InnoCraft, the professional company behind Piwik, this plugin will :

  1. Save you heaps of time and gives you completely new insights
  2. Make this process easy as pie
  3. Reflect the structure of your business or organization

  1 – Roll-Up Reporting does the maths for you

  Yes, you read it right. Compared to having to sum reports of multiple websites manually, you can get aggregated results for your business or departments instantly with a single click directly in Piwik. Not only does this save you heaps of time compared to doing this complicated work in a spreadsheet, you also avoid human errors. With this feature, you get a clear overview over all your websites, apps, and shops performances.

  For example, if you want to know which referrers bring you the most value across all websites, then you will get the answer in a report. Same results for e-commerce reports, actions, and other metrics.

  2 – Easy as pie, no tracking code involved

  The best part of this feature is that you do not need to push data through additional tracking code. The setup is simple and made through the UI of the plugin.

  3 – Roll-Up Reporting meets even the hardest requirements

  You can also create “nested roll-ups”. This feature allows you to create a roll-up consisting of several other roll-ups. With a nested roll-up, you can create a roll-up for each department in your company (and assign all the websites of a department to that roll-up), then group several departments easily into a new roll-up simply by assigning several department roll-ups to this new roll-up.

  

  For example, a company with multiple brands can assign multiple websites to each brand, and then get aggregated results for each brand and for the business overall. As a roll-up is basically the same as a website, you can give users access to a roll-up without having to give them access to each site, and the other way around.

  How does it work ?

  As with all premium features, this plugin is straightforward to use. Once activated in your Piwik administrator panel, you will notice that when you add a website, you have the choice between two possibilities :

  

  When you select the “Roll-Up” option, a new window will appear asking you which websites and mobile apps you would like to aggregate into a roll-up :

  

  The created roll-up will then be shown just like any other website that you have in Piwik. You can create as many roll-up entities as you want.

  

  Features, such as custom alerts, segments, and e-mail reports work for a roll-up just like for any website.

  Real-Time reports

  One of the most interesting features of Roll-Up Reporting is, that you can view all the Real-Time reports, such as the “Visitors in Real-Time” widget, the “Real-Time Map”, and the “Visitor Log” across several websites making it much easier to keep an eye on your business :

  

  How to get the Roll-up reporting plugin ?

  Developed by InnoCraft, the makers of Piwik, Roll-Up Reporting is a premium feature which you can purchase on the Piwik Marketplace. You can also try it for free on the Piwik Cloud for 30 days.

  Learn more about the Roll-Up Reporting feature

• The First Problem

  19 janvier 2011, par Multimedia Mike — HTML5

  A few years ago, The Linux Hater made the following poignant observation regarding Linux driver support :

  Drivers are only just the beginning... But for some reason y’all like to focus on the drivers. You know why lusers do that ? Because it just happens to be the problem that people notice first.

  And so it is with the HTML5 video codec debate, re-invigorated in the past week by Google’s announcement of dropping native H.264 support in their own HTML5 video tag implementation. As I read up on the fiery debate, I kept wondering why people are so obsessed with this issue. Then I remembered the Linux Hater’s post and realized that the video codec issue is simply the first problem that most people notice regarding HTML5 video.

  I appreciate that the video codec debate has prompted Niedermayer to post on his blog once more. Otherwise, I’m just munching popcorn on the sidelines, amused and mildly relieved that the various factions are vociferously attacking each other rather than that little project I help with at work.

  Getting back to the "first problem" aspect— there’s so much emphasis on the video codec ; I wonder why no one ever, ever mentions word one about an audio codec. AAC is typically the codec that pairs with H.264 in the MPEG stack. Dark Shikari once mentioned that "AAC’s licensing terms are exponentially more onerous than H.264′s. If Google didn’t want to use H.264, they would sure as hell not want to use AAC." Most people are probably using "H.264" to refer to the entire MPEG/H.264/AAC stack, even if they probably don’t understand what all of those pieces mean.

  Anyway, The Linux Hater’s driver piece continues :

  Once y’all have drivers, the fight will move to the next layer up. And like I said, it’s a lot harder at that layer.

  A few months ago, when I wanted to post the WebM output of my new VP8 encoder and thought it would be a nice touch to deliver it via a video tag, I ignored the video codec problem (just encoded a VP8/WebM file) only to immediately discover a problem at a different layer— specifically, embedding a file using a video tag triggers a full file download when the page is loaded, which is unacceptable from end user and web hosting perspectives. This is a known issue but doesn’t get as much attention, I guess because there are bigger problems to solve first (c.f. video codec issue).

  For other issues, check out the YouTube blog’s HTML5 post or Hulu’s post that also commented on HTML5. Issues such as video streaming flexibility, content protection, fullscreen video, webcam/microphone input, and numerous others are rarely mentioned in the debates. Only "video codec" is of paramount importance.

  But I’m lending too much weight to the cacophony of a largely uninformed internet debate. Realistically, I know there are many talented engineers down in the trenches working to solve at least some of these problems. To tie this in with the Linux driver example, I’m consistently stunned these days regarding how simple it is to get Linux working on a new computer— most commodity consumer hardware really does just work right out of the box. Maybe one day, we’ll wake up and find that HTML5 video has advanced to the point that it solves all of the relevant problems to make it the simple and obvious choice for delivering web video in nearly all situations.

  It won’t be this year.