Recherche avancée

Sur d’autres sites (11818)

• Announcing Long Term Support in Piwik 2 – The analytics platform for your mission critical projects

  11 janvier 2016, par Matthieu Aubry — About, Development

  We are proud to announce our Long Term Support (LTS) for Piwik 2.X !

  Why Long Term Support (LTS) ?

  Part of our mission is to ready Piwik for the enterprise — and ready the enterprise for Piwik. Our fast release cycle and our ability to quickly innovate has served us well for the past seven years and has lead Piwik to being one of the most popular open source projects, used by over one million websites worldwide. But Piwik’s success today has also shown us that this fast release cycle is not suited for all users and customers. Like most large open source projects (such as Ubuntu, Firefox, Debian, Symfony, Node.js, etc.) at Piwik we now also offer a Long Term Support release which gives users the confidence that Piwik can be used for mission critical projects for months to come.

  What does LTS mean for Piwik ?

  For the duration of the LTS period, Piwik 2.X will continue to receive the following fixes :

  • Critical bugs causing data loss or data corruption.
  • Major and Critical security issues.

  Our goal is to offer you a Piwik LTS release that you can trust for all your mission critical projects.

  How long will Piwik 2.X be supported ?

  Piwik 2.X will be supported for at least 12 months after the initial release of Piwik 3.0.0.
  Piwik 3.0.0 is expected to be released in the second half of 2016.
  This means that Piwik 2.X will be supported at least until the second half of 2017.

  Which Piwik version is LTS ?

  The latest Piwik 2.16.X release is our Long Term Support version.

  How do I benefit from the LTS version ?

  To get the full benefits of Piwik LTS, please make sure you are using the latest LTS version. First, update to the latest Piwik 2.X version, then Configure Piwik to use the LTS release channel and then update to the latest LTS version.

  How do I configure Piwik to use the LTS version ?

  By default, Piwik will not use the LTS version. When you use the one-click update your Piwik instance will be updated to the very latest release : when Piwik 3.0.0 will be released, the one click update will update your instance to 3.0.0. It is however possible to configure your Piwik so that you will stay on Piwik 2.X and keep using the LTS Long Term Support version :

  • Login Piwik as the Super User,
  • Go to Settings > General > Update settings,
  • Under “Release channel” click “Latest stable 2.X Long Term Support version”, and click “Save”.
    

  How do I get professional Piwik Support ?

  If you need professional support for your Piwik service get in touch with the Piwik experts.

  ---

  For other questions, feedback or discussion, feel free to join our forums and comment on this LTS forum post.

  We wish you all a fantastic year 2016 !

• bitmap to yuv , video recorded has only green pixels

  19 janvier 2016, par UserAx

  I am trying to convert a bitmap to yuv, and recording this yuv in the ffmpeg frame recorder...
  I am getting the video output with only green pixels, though when i check the properties of this video it shows the set Frame rate and the resolution...

  The yuv encoding part is correct, but i feel i am making mistake somewhere else, mostly in returning the yuv bytes to recording part ( getByte(byte [] yuv ) because only there the yuv.length displayed in console is 0,, rest all methods return a big value in console ...

  Kindly help...

   @Override
  
  public void onCreate(Bundle savedInstanceState) {
  
      super.onCreate(savedInstanceState);
  
      setContentView(R.layout.activity_main);
  
      directory.mkdirs();
  
  
  
      addListenerOnButton();
  
  
  
      play=(Button)findViewById(R.id.buttonplay);
  
      stop=(Button)findViewById(R.id.buttonstop);
  
      record=(Button)findViewById(R.id.buttonstart);
  
  
  
      stop.setEnabled(false);
  
      play.setEnabled(false);
  
  
  
  
  
      record.setOnClickListener(new View.OnClickListener() {
  
          @Override
  
          public void onClick(View v) {
  
              startRecording();
  
              getByte(new byte[]{});
  
          }
  
      });
  
  
  
      stop.setOnClickListener(new View.OnClickListener() {
  
          @Override
  
          public void onClick(View v) {
  
              stopRecording();
  
          }
  
      });
  
  
  
  
  
      play.setOnClickListener(new View.OnClickListener() {
  
          @Override
  
          public void onClick(View v) throws IllegalArgumentException, SecurityException, IllegalStateException {
  
              Intent intent = new Intent(Intent.ACTION_VIEW, Uri.parse(String.valueOf(asmileys)));
  
              intent.setDataAndType(Uri.parse(String.valueOf(asmileys)), "video/mp4");
  
              startActivity(intent);
  
              Toast.makeText(getApplicationContext(), "Playing Video", Toast.LENGTH_LONG).show();
  
          }
  
      });
  
  
  
   }
  
  
  
  ......//......
  
  
  
  
  
  
  
  public void getByte(byte[] yuv) {
  
      getNV21(640, 480, bitmap);
  
      System.out.println(yuv.length + " ");
  
      if (audioRecord == null || audioRecord.getRecordingState() != AudioRecord.RECORDSTATE_RECORDING) {
  
          startTime = System.currentTimeMillis();
  
          return;
  
      }
  
      if (RECORD_LENGTH > 0) {
  
          int i = imagesIndex++ % images.length;
  
          yuvimage = images[i];
  
          timestamps[i] = 1000 * (System.currentTimeMillis() - startTime);
  
      }
  
          /* get video data */
  
      if (yuvimage != null && recording) {
  
              ((ByteBuffer) yuvimage.image[0].position(0)).put(yuv);
  
  
  
              if (RECORD_LENGTH <= 0) {
  
                  try {
  
                      long t = 1000 * (System.currentTimeMillis() - startTime);
  
                      if (t > recorder.getTimestamp()) {
  
                          recorder.setTimestamp(t);
  
                      }
  
                      recorder.record(yuvimage);
  
                  } catch (FFmpegFrameRecorder.Exception e) {
  
  
  
                      e.printStackTrace();
  
                  }
  
              }
  
          }
  
  }
  
  
  
  public byte [] getNV21(int inputWidth, int inputHeight, Bitmap bitmap) {
  
  
  
      int[] argb = new int[inputWidth * inputHeight];
  
  
  
      bitmap.getPixels(argb, 0, inputWidth, 0, 0, inputWidth, inputHeight);
  
  
  
      byte[] yuv = new byte[inputWidth * inputHeight * 3 / 2];
  
      encodeYUV420SP(yuv, argb, inputWidth, inputHeight);
  
  
  
      bitmap.recycle();
  
      System.out.println(yuv.length + " ");
  
      return yuv;
  
  
  
  }
  
  
  
  void encodeYUV420SP(byte[] yuv420sp, int[] argb, int width, int height) {
  
      final int frameSize = width * height;
  
  
  
      int yIndex = 0;
  
      int uIndex = frameSize;
  
      int vIndex = frameSize;
  
      System.out.println(yuv420sp.length + " " + frameSize);
  
  
  
      int a, R, G, B, Y, U, V;
  
      int index = 0;
  
      for (int j = 0; j < height; j++) {
  
          for (int i = 0; i < width; i++) {
  
  
  
              a = (argb[index] & 0xff000000) >> 24; // a is not used obviously
  
              R = (argb[index] & 0xff0000) >> 16;
  
              G = (argb[index] & 0xff00) >> 8;
  
              B = (argb[index] & 0xff) >> 0;
  
  
  
              // well known RGB to YUV algorithm
  
  
  
              Y = ((66 * R + 129 * G + 25 * B + 128) >> 8) + 16;
  
              U = ((-38 * R - 74 * G + 112 * B + 128) >> 8) + 128;
  
              V = ((112 * R - 94 * G - 18 * B + 128) >> 8) + 128;
  
  
  
              // NV21 has a plane of Y and interleaved planes of VU each sampled by a factor of 2
  
              //    meaning for every 4 Y pixels there are 1 V and 1 U.  Note the sampling is every other
  
              //    pixel AND every other scanline.
  
              yuv420sp[yIndex++] = (byte) ((Y < 0) ? 0 : ((Y > 255) ? 255 : Y));
  
              if (j % 2 == 0 && index % 2 == 0) {
  
                  yuv420sp[uIndex++] = (byte) ((U < 0) ? 0 : ((U > 255) ? 255 : U));
  
                  yuv420sp[vIndex++] = (byte) ((V < 0) ? 0 : ((V > 255) ? 255 : V));
  
              }
  
  
  
              index++;
  
          }
  
      }
  
  }
  
  
  
   .....//.....
  
  
  
   public void addListenerOnButton() {
  
   image = (ImageView) findViewById(R.id.imageView);
  
   image.setDrawingCacheEnabled(true);
  
   image.buildDrawingCache();
  
   bitmap = image.getDrawingCache();
  
   System.out.println(bitmap.getByteCount() + " " );
  
  
  
   button = (Button) findViewById(R.id.btn1);
  
   button.setOnClickListener(new OnClickListener() {
  
  @Override
  
  public void onClick(View view){
  
      image.setImageResource(R.drawable.image1);
  
    }
  
  });
  
  
  
  ......//......

  EDIT 1 :

  I made few changes in the above code :

   record.setOnClickListener(new View.OnClickListener() {
  
          @Override
  
          public void onClick(View v) {
  
              startRecording();
  
              getByte();
  
          }
  
      });
  
  .....//....
  
  
  
  public void getbyte() {
  
      byte[] yuv = getNV21(640, 480, bitmap);

  So now in the console ; i get same yuv length in this method as the yuv length from getNV21 method..

  But now i am getting half screen Black and Half screen green(black above and green below) pixels in the recorded video...

  If i add these lines to onCreate method ;

   image = (ImageView) findViewById(R.id.imageView);
  
   image.setDrawingCacheEnabled(true);
  
   image.buildDrawingCache();
  
   bitmap = image.getDrawingCache();

  I do get distorted frames( frames are 1/4th of the image displayed with mix up of colors here and there) in the video....

  All i am trying to learn is the image processing and flow of Bytes[] from one method to another ; but i am still a noob.. ;

  Kindly help..!

• Anomalie #3760 : Le correcteur typographique ne gère pas le HTML5

  26 mars 2016, par Christian Pierre MOMON

  Grrrrrr, les codes sont escapés dans le titre mais pas dans le texte. Je remets mon texte en faisant apparaître les codes :-/

  Le correcteur typographique fait un super boulot pour le rendu des articles. Par exemple, il transforme « Exemple : » en HTML « Exemple& nbsp ; : ».

  C’est vraiment super, sauf que ce n’est pas compatible avec HTML5 où le & nbsp ; est ignoré (&#160 est attendu à la place). Et donc on obtient des rendus catastrophiques (monstrueux espaces entre «  : » et le mot précédent, etc.). J’ai tenté de mettre «   », même résultat. J’ai tenté de mettre « Exemple& #160 ; : » et j’obtiens « Exemple& #160 ;& nbsp ; : » :-/

  Le HTML5 devenant de plus en plus répandu et étant amené à devenir le DOCTYPE de référence, suggestion d’adapter le module typo pour gérer le HTML5.

  Informations complémentaires :
  - j’utilise SPIP 3.0.17-2+deb8u2 (Debian) ;
  - j’ai activé « Permettre le HTML5 » dans l’interface d’administration ;
  - je mets «  » dans mes entêtes de fichier HTML.

  Avec tous mes encouragements \o/