Recherche avancée

Sur d’autres sites (7891)

• aaccoder : Implement Perceptual Noise Substitution for AAC

  15 avril 2015, par Rostislav Pehlivanov

  aaccoder : Implement Perceptual Noise Substitution for AAC
  This commit implements the perceptual noise substitution AAC extension. This is a proof of concept
  
  implementation, and as such, is not enabled by default. This is the fourth revision of this patch,
  
  made after some problems were noted out. Any changes made since the previous revisions have been indicated.
  In order to extend the encoder to use an additional codebook, the array holding each codebook has been
  
  modified with two additional entries - 13 for the NOISE_BT codebook and 12 which has a placeholder function.
  
  The cost system was modified to skip the 12th entry using an array to map the input and outputs it has. It
  
  also does not accept using the 13th codebook for any band which is not marked as containing noise, thereby
  
  restricting its ability to arbitrarily choose it for bands. The use of arrays allows the system to be easily
  
  extended to allow for intensity stereo encoding, which uses additional codebooks.
  The 12th entry in the codebook function array points to a function which stops the execution of the program
  
  by calling an assert with an always ’false’ argument. It was pointed out in an email discussion with
  
  Claudio Freire that having a ’NULL’ entry can result in unexpected behaviour and could be used as
  
  a security hole. There is no danger of this function being called during encoding due to the codebook maps introduced.
  Another change from version 1 of the patch is the addition of an argument to the encoder, ’-aac_pns’ to
  
  enable and disable the PNS. This currently defaults to disable the PNS, as it is experimental.
  
  The switch will be removed in the future, when the algorithm to select noise bands has been improved.
  
  The current algorithm simply compares the energy to the threshold (multiplied by a constant) to determine
  
  noise, however the FFPsyBand structure contains other useful figures to determine which bands carry noise more accurately.
  Some of the sample files provided triggered an assertion when the parameter to tune the threshold was set to
  
  a value of ’2.2’. Claudio Freire reported the problem’s source could be in the range of the scalefactor
  
  indices for noise and advised to measure the minimal index and clip anything above the maximum allowed
  
  value. This has been implemented and all the files which used to trigger the asserion now encode without error.
  The third revision of the problem also removes unneded variabes and comparisons. All of them were
  
  redundant and were of little use for when the PNS implementation would be extended.
  The fourth revision moved the clipping of the noise scalefactors outside the second loop of the two-loop
  
  algorithm in order to prevent their redundant calculations. Also, freq_mult has been changed to a float
  
  variable due to the fact that rounding errors can prove to be a problem at low frequencies.
  
  Considerations were taken whether the entire expression could be evaluated inside the expression
  
  , but in the end it was decided that it would be for the best if just the type of the variable were
  
  to change. Claudio Freire reported the two problems. There is no change of functionality
  
  (except for low sampling frequencies) so the spectral demonstrations at the end of this commit’s message were not updated.
  Finally, the way energy values are converted to scalefactor indices has changed since the first commit,
  
  as per the suggestion of Claudio Freire. This may still have some drawbacks, but unlike the first commit
  
  it works without having redundant offsets and outputs what the decoder expects to have, in terms of the
  
  ranges of the scalefactor indices.
  Some spectral comparisons : https://trac.ffmpeg.org/attachment/wiki/Encode/AAC/Original.png (original),
  
  https://trac.ffmpeg.org/attachment/wiki/Encode/AAC/PNS_NO.png (encoded without PNS),
  
  https://trac.ffmpeg.org/attachment/wiki/Encode/AAC/PNS1.2.png (encoded with PNS, const = 1.2),
  
  https://trac.ffmpeg.org/attachment/wiki/Encode/AAC/Difference1.png (spectral difference).
  
  The constant is the value which multiplies the threshold when it gets compared to the energy, larger
  
  values means more noise will be substituded by PNS values. Example when const = 2.2 :
  
  https://trac.ffmpeg.org/attachment/wiki/Encode/AAC/PNS_2.2.png
  Reviewed-by : Claudio Freire <klaussfreire@gmail.com>
  
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavcodec/aaccoder.c
  • [DH] libavcodec/aacenc.c
  • [DH] libavcodec/aacenc.h

• Révision 23266 : validation des comptes nouveau : on appelle la fonction confirmer_statut_inscript...

  14 novembre 2016, par cedric@yterium.com

  Dans auth_init_droits on fait appel a une autorisation autoriser(loger) qui par defaut autorise tous les statuts sauf 5poubelle
  En surchargeant cette autorisation on peut interdire le login au auteur ’nouveau’ a confirmer, et les obliger a utiliser le lien de confirmation par email
  + gestion de l’echec login dans le formulaire de login pour afficher un message d’erreur (on affiche une erreur classique du type mot de passe incorrect pour ne pas donner d’information sur l’existence d’un login)

• How to verify user permissions – Introducing the Piwik Platform

  9 novembre 2014, par Thomas Steur — Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform (our previous post was How to make your plugin multilingual). This time you’ll learn how to verify user permissions. For this tutorial you will need to have basic knowledge of PHP and the Piwik platform.

  When should a plugin verify permissions ?

  Usually you want to do this before executing any action – such as deleting or fetching data – and before rendering any sensitive information that should not be accessible by everyone. For instance in an API method or Controller action. You sometimes also need to verify permissions before registering menu items or widgets.

  How does Piwik’s user management work ?

  It is quite simple as it only differentiates between a few roles : View permission, Admin permission and Super User permission. If you manage multiple websites with Piwik a user can be assigned to different roles as a user might have no permission for some websites but view or admin permission for another set of websites.

  Worth mentioning is that roles inherit from each other. This means the role admin automatically includes the role view and a super user automatically covers the view and admin role.

  Getting started

  In this post, we assume that you have already set up your development environment and created a plugin. If not, visit the Piwik Developer Zone where you’ll find the tutorial Setting up Piwik and other Guides that help you to develop a plugin.

  Verifying user permissions

  To protect your data the platform offers many convenient methods in the \Piwik\Piwik class. There you will find methods that either start with check, is or has. While methods that start with check throw an exception in case a condition is not met, the other methods return a boolean true or false.

  Use methods that throw an exception if you want to stop any further execution in case a user does not have an appropriate role. The platform will catch the exception and display an error message or ask the user to log in.

  public function deleteAllMessages()
  {
      // delete messages only if user has super user access, otherwise show an error message
      Piwik::checkUserSuperUserAccess();
   
      $this->getModel()->deleteAllMessages();
  }
  Télécharger

  Use methods that return a boolean for instance when registering menu items or widgets.

  public function configureAdminMenu(MenuAdmin $menu)
  {
      if (Piwik::hasUserSuperUserAccess()) {
          $menu->addPlatformItem('Plugins', $this->urlForDefaultAction());
      }
  }
  Télécharger

  It is important to be aware that just because the menu item won’t be displayed in the UI a user can still open the registered URL manually. Therefore you have to check for permissions in the actual controller action as well.

  View permission

  A user having a view permission should be only able to view reports but not make any changes apart from his personal settings. The methods that end with UserHasSomeViewAccess make sure a user has at least view permission for one website whereas the methods *UserHasViewAccess($idSites = array(1,2,3)) check whether a user has view access for all of the given websites.

  Piwik::checkUserHasSomeViewAccess();
   
  Piwik::checkUserHasViewAccess($idSites = array(1,2,3));
  Télécharger

  As a plugin developer you would usually use the latter example to verify the permissions for specific websites. Use the first example in case you develop something like an “All Websites Dashboard” where you only want to make sure the user has a view permission for at least one website.

  Admin permission

  A user having an admin permission cannot only view reports but also change website related settings. The methods to check for this role are similar to the ones before, just swap the term View with Admin.

  Piwik::checkUserHasSomeAdminAccess();
   
  Piwik::checkUserHasAdminAccess($idSites = array(1,2,3));
  Télécharger

  Super user permission

  A user having the super user permission is allowed to access all of the data stored in Piwik and change any settings. To check if a user has this role use one of the methods that end with UserSuperUserAccess.

  Piwik::checkUserHasSuperUserAccess();

  As a plugin developer you would check for this permission for instance in places where your plugin shows an activity log over all users or where it offers the possibility to change any system wide settings.

  Getting information about the currently logged in user

  Sometimes you might want to know which user is currently logged in. This can be useful if you want to persist user related information in the database or if you want to send an email to the currently logged in user. You can easily get this information by calling the following methods :

  $login = Piwik::getCurrentUserLogin()
  $email = Piwik::getCurrentUserEmail()
  Télécharger

  Advanced features

  Of course there is more that you can do. For instance you can verify whether a user is an anonymous user or whether a user has a specific role. You can also perform any operation in the context of a super user even if the current user does not have this role. Would you like to know more about those features ? Check out the Piwik class reference, the Security guide and the Manage Users user guide.

  If you have any feedback regarding our APIs or our guides in the Developer Zone feel free to send it to us.