Recherche avancée

Sur d’autres sites (7156)

• recording yuv data which is converted from a bitmap and images are changed constantly on this bitmap

  3 février 2016, par UserAx

  I am trying to record images which are changed at a set time interval. These are displayed on an imageview. (something like a movie maker)

  For this I am :

  1. Drawing these images on a bitmap, this method is repeated over a 50ms interval

     private void BitmapUpdate() {
     
            timer = new Timer();
     
     timer.scheduleAtFixedRate(new TimerTask() {
     
         public void run() {
     
             try {
     
                 new Task1().execute();
     
             } catch (Exception e) {
     
                 // TODO: handle exception
     
             }
     
         }
     
     }, 0, 50);
     
     }
     
     
     
     class Task1 extends AsyncTask {
     
     
     
     @Override
     
     protected void onPreExecute() {
     
         super.onPreExecute();
     
         clearBitmap();
     
     
     
     }
     
     
     
     @Override
     
     protected String doInBackground(Void... arg0) {
     
     
     
         onImageDisplayed();
     
         return null;
     
     }
     
     
     
     @Override
     
     protected void onPostExecute(String result) {
     
         super.onPostExecute(result);
     
     
     
     }
     
     }
     
     
     
     public void clearBitmap(){
     
     if (imageview != null){
     
     //All the 3 methods below give same error - can't call getpixels() on recycled bitmap
     
     imageview.setDrawingCacheEnabled(false);
     
     //OR
     
     imageview.destroyDrawingCache();
     
     //OR
     
     bitmap.recycle();
     
     
     
     }
     
        }
     
     
     
     
     
     
     
      public void onImageDisplayed(){
     
     
     
     if (imageview != null) {
     
         imageview.setDrawingCacheEnabled(true);
     
         imageview.buildDrawingCache();
     
         bitmap = imageview.getDrawingCache();
     
         System.out.println(bitmap.getByteCount() + " is bitmap size ");
     
         }
     
        }

  2. Using the bitmap data to convert it to yuv data
     By using getNV21 method :

  Convert bitmap array to YUV (YCbCr NV21)

  3. Finally this yuv data is passed FFmpeg recorder, through a method similar to onPreviewFrame, except that the data is from getNV21 method. This method is started by a button click.

  What I have achieved :

  1. If i dont use clearBitmap() ; i get only the first image recorded in the video, even on changing to next image only first image is present throughout the video.

  2. So After research on stack overflow many developers suggested clearing the previous imageCache for the next Image. But in my case if i use any of these methods, anywhere,

     imageview.setDrawingCacheEnabled(false);
     
     //OR
     
     imageview.destroyDrawingCache();
     
     //OR
     
     bitmap.recycle();

  I get the error ; mostly because the getNV21 method is running non stop, and always is expecting pixels flow from the Bitmap.

  3. If i try running the methods one after another, by stopping getpixels for a moment by a boolean, i only get a black screen.

  Kindly help...!

  THANKS.

• Help us to improve Piwik by sending anonymous usage data (and get usage data yourself)

  22 octobre 2015, par Thomas Steur — Community, Plugins

  At Piwik we have developed a new plugin named AnonymousPiwikUsageMeasurement. The opt-in and anonymised usage tracking information will be used by us to build a better product and a great user experience. The plugin can be installed via the Piwik Marketplace with just a few clicks in your Piwik installation. As a Super User simply go to the Administration and select Marketplace in the left menu. There you will find the plugin and can install it with just one click.

  The plugin allows you to track usage data into up to three Piwik installations :

  • demo-anonymous.piwik.org (enabled by default, can be disabled).
  • your own Piwik (can be configured optionally)
  • a custom Piwik (can be configured optionally)

  The usage data that is sent to Piwik can be publicly viewed by anyone under demo-anonymous.piwik.org.

  What are the advantages by tracking the data into my own installation ?

  You can see how your Piwik installation is used and how well your Piwik performs by checking the average generation time of pages and API calls. Use the Row Evolution feature to see how your Piwik is performing over time.

  What is Piwik doing to make sure the data is anonymized ?

  We are very careful in what we track and we make sure to anonymize data that could contain user data.

  • We overwrite the page title as the title could contain the name of the viewed website
  • We remove any referrer information
  • We replace URL paramaters with a predefined value apart from a few whitelisted ones to make sure no actual token_auth, CSRF token or user defined value will be tracked
  • On demo-anonymous.piwik.org 3 bytes of the IP are anonymised (eg when IP is 192.168.1.1 we track only 192.0.0.0). We do not track nor collect your location and provider information.
  • We do not track clicks on outlinks or downloads

  When should I not install this plugin ?

  If you have developed a custom Piwik plugin that contains for example the name of your business in any of the following names we recommend to not install this plugin as it might be tracked :

  • name of a plugin
  • name of a controller action
  • name of a report
  • name of a widget
  • name of an API method

  Plugins that are installed via the Marketplace should not pose a problem as their names don't contain any user specific information such as the name of your business.

  The data is tracked as efficiently as possible as to not slow down your Piwik server. If you already have some performance challenges with your Piwik, we recommend not to install this plugin.

  Which data is tracked ?

  When the plugin is activated, the following data will be tracked :

  • The pages and reports that are viewed
  • The visitors' software and devices data like the used browser and the resolution
  • Some clicks or interactions with certain selectors or buttons. For example we track an event when a segment is selected (but we do not track the actual segment name or value).
  • In a daily task we track the following data :
    • Piwik version
    • PHP version
    • Number of websites
    • Number of users
    • Number of segments
    • How often which API method was called (only plugin name and method name but no parameters) and how long the API calls took on average.

  Are there any prerequisites ?

  • If sending usage data to Piwik is enabled, the Piwik installation must be connected to the internet
  • If tracking to a custom Piwik installation is enabled, your Piwik installation and your Piwik users must be able to connect to this instance

  Where can I report any issues with the plugin ?

  If you experience any issues with the plugin please create a new issue. The source code is available under GPL v3+ on GitHub. We always appreciate pull requests and suggestions to improve this plugin.

• Préférence donnée à mp4 sur webm quand le fichier mp4 est chargé en tant que conversion d’un fichier webm

  21 janvier 2016

  Bonjour,
  le site AlterInfos - América latina (www.alterinfos.org) utilise depuis un an le plugin "Lecteur multimédia HTML5 pour MediaSPIP" qui marche super bien. Merci.
  Jusqu’à présent, les vidéos étaient surtout au format mp4. Mais dans un article récent, les vidéos ont été téléversés au format webm (VP9+Opus), puis, à partir de ces vidéos de référence, une conversion en mp4 a aussi été téléversée. Quand on visualise les vidéos dans Firefox (43, Debian Jessie 64) ou dans Chromium, c’est toujours le fichier mp4 qui est visualisé. Si on met la vidéo au format webm seulement, la vidéo est visualisée dans ce format.
  Ce n’est donc pas un problème de compatibilité du navigateur, mais plutôt peut-être que le fichier "conversion" (mp4) est traité avant le fichier "original" (webm). Si on regarde le code source de la page, le lien vers le mp4 apparaît avant celui en webm.
  Téléverser d’abord le fichier en mp4 puis charger ensuite en tant que "conversion du document" le fichier en webm règle le problème : c’est désormais le fichier en webm qui est joué "par défaut" quand on visualise la vidéo.
  Mais il me semble que ce serait plus logique que ce soit le document de référence et non sa conversion qui soit joué par défaut quand on visualise une vidéo.
  Ça permettrait aussi de choisir la vidéo qu’on souhaite diffuser "par défaut" (dans notre cas, la vidéo webm est beaucoup plus légère [car VP9 et opus], donc c’est assez logique de vouloir que ce soit la vidéo par défaut…
  Cordialement,
  Nicolas