Recherche avancée

Sur d’autres sites (6524)

• How to convert from AV_PIX_FMT_BGRA to PIX_FMT_PAL8 ?

  29 juillet 2014, par Jona

  I’m having a hard time converting my images from AV_PIX_FMT_BGRA to PIX_FMT_PAL8. Unfortunately sws_getCachedContext doesn’t support the conversion to PIX_FMT_PAL8.

  What I’m trying to do is convert my images into a GIF video with higher quality output. It seems that PIX_FMT_PAL8 could potentially provide the higher quality output I’m looking for.

  According to this documentation I need to palettize the pixel data, but I have no clue how to do that.

  When the pixel format is palettized RGB (PIX_FMT_PAL8), the palettized
  image data is stored in AVFrame.data[0]. The palette is transported in
  AVFrame.data[1], is 1024 bytes long (256 4-byte entries) and is
  formatted the same as in PIX_FMT_RGB32 described above (i.e., it is
  also endian-specific). Note also that the individual RGB palette
  components stored in AVFrame.data[1] should be in the range 0..255.
  This is important as many custom PAL8 video codecs that were designed
  to run on the IBM VGA graphics adapter use 6-bit palette components.

  Any help or direction would be appreciated.

• Java Runtime Command with disrupt/additonal command

  11 juin 2014, par oneofakind

  Actually the example below is not what I want to do, its sort of related to what I really wanna do. Its basically having to execute a shell command or a cmd command and executing another command relating to the first command. Somehow it stops/proceeds/respond to the first command executed.

  It’s actually ffmpeg execution what I wanna do, recording the screen. Problem is that I cannot execute a "q" key to stop the recording. Example above is sort of a simple, but I hope applicable, to my main problem.

  Here is the simplified problem :

  StringBuffer output = new StringBuffer();
  
  String domainName = "google.com";
  
  String command = "ping -t " + domainName;
  
  Process p;
  
  try {
  
      p = Runtime.getRuntime().exec(command);
  
      p.waitFor();
  
      BufferedReader reader = new BufferedReader(new InputStreamReader(p.getInputStream()));
  
  
  
                  String line = "";           
  
      while ((line = reader.readLine())!= null) {
  
          output.append(line + "\n");
  
      }
  
  
  
  } catch (Exception ec) {
  
      ec.printStackTrace();
  
  }
  
  
  
  
  
  System.out.println(output);

  What will happen here is that it will ping endlessly unless interrupted to end the ping, what will happen to the code is that it will get stuck in the line :

   p.waitFor();

  That is because, I believe, it is waiting for the command to finish before it releases it. What I want to do is to execute a "ctrl+C" or command that will stop this execution and then manipulate the result continuing through

   BufferedReader reader = new BufferedReader(new InputStreamReader(p.getInputStream()));
  
   ........
  
   ........

  I hope you guys got what I am trying to say. :D

  Please help. Thanks.

• Piwik 2.1 – Changes for Plugin developers

  24 février 2014, par Piwik Core Team — Development

  This blog post is aimed at developers of Piwik Plugins. If you are simply using Piwik and not developing plugins for Piwik, you do not need to read this post.

  Piwik 2.1 will be released in a few days . This blog post will inform Piwik Plugin developers of the changes in Piwik 2.1 that may require that you update your plugin to work with this latest version.

  Breaking API changes

  Piwik can now handle an unlimited number of users having Super User access (#2589 #4564). In the past Piwik was limited to one Super User who was defined in the config file. From now on all users with Super User access are defined in the database the same way a regular user is. This brought some API changes but we will stay backward compatible until the first of April 2014. This gives you some time to migrate any custom plugins you may use. Although there is a layer for backward compatibility we recommend to make sure your plugin works with Piwik as soon as possible before April 1st.

  List of changes

  Deprecated methods

  The following methods are deprecated and we recommend to use the new methods from now on. There are also some methods which won’t be replaced so make sure to adjust the logic of your plugin.

  \Piwik\Piwik::isUserIsSuperUser => \Piwik\Piwik::hasUserSuperUserAccess
  
  \Piwik\Piwik::setUserIsSuperUser => \Piwik\Piwik::setUserHasSuperUserAccess
  
  \Piwik\Piwik::checkUserIsSuperUser => \Piwik\Piwik::checkUserHasSuperUserAccess
  
  \Piwik\Access::isSuperUser => \Piwik\Access::hasSuperUserAccess
  
  \Piwik\Access::checkUserIsSuperUser => \Piwik\Access::checkUserHasSuperUserAccess
  
  \Piwik\Access::setSuperUser => \Piwik\Access::setSuperUserAccess
  
  \FakeAccess::checkUserIsSuperUser => FakeAccess::checkUserHasSuperUserAccess
  
  \FakeAccess::setSuperUser => FakeAccess::setSuperUserAccess
  
  \Piwik\Piwik::isUserIsSuperUserOrTheUser => \Piwik\Piwik::hasUserSuperUserAccessOrIsTheUser
  
  \Piwik\Piwik::checkUserIsSuperUserOrTheUser => \Piwik\Piwik::checkUserHasSuperUserAccessOrIsTheUser
  
  \FakeAccess::getSuperUserLogin => No replacement
  
  \Piwik\Piwik::getSuperUserLogin => No replacement, returns the userLogin of the first Super User we find in the database 
  
  \Piwik\Piwik::getSuperUserEmail => No replacement, returns an empty string from now on
  
  \Piwik\Access::getSuperUserLogin => No replacement, returns the userLogin of the first Super User we find in the database

  Config Super User

  As mentioned, the Super User was defined in the config and you have accessed the Super User’s data either by using a convenient method like Piwik::getSuperUserLogin or directly via the Config object as follows :

  \Piwik\Config::getInstance->superUser

  As the config user is no longer defined in the config this will no longer work in the future. To stay backward compatible we return the first super user found in the database. This is not necessarily always the same user. So if you have used the super user login in some way in your plugin, make sure you are using the new function such as Piwik::getSuperUserLogin

  Extended Auth Interface

  The last change affects plugins who specify their own Authentication mechanism, for instance when using the custom LoginLDAP plugin. From now on the interface \Piwik\Auth (​https://github.com/piwik/piwik/blob/master/core/Auth.php) requires the methods setTokenAuth and setLogin. There is no backward compatibility layer but we had a look at some plugins defining a custom Authentication adapter to make sure those methods are already defined there as expected.

  For another example of a Login plugin, check out the LoginHttpAuth plugin on the Marketplace.

  After updating the plugin

  After you have made changes in your plugin to keep it compatible with Piwik 2.1, your plugin will no longer work with previous Piwik versions. Therefore you should define the minimum required version in your plugin.json file as follows :

  "require": {
  
   "piwik": ">=2.1" 
  
  }

  Summary

  Piwik 2.1 introduces some changes in the Piwik Core APIs. This blog post explains how to modify any Plugins compatible with Piwik 2.0 to be compatible with Piwik 2.1. Thank you for taking the time to update your plugins !

  Let us know if you have any feedback. Happy hacking !

  PS : if you use the Web Analytics APIs and the Web Tracking APIs, we guarantee that we will support backwards compatibility of our Web APIs.