Recherche avancée

Sur d’autres sites (13459)

• Anomalie #3635 : Pouvoir déplacer les rubriques qui contiennent des brèves avec le plugin plan

  11 février 2017

  Les brèves sont forcément attachées à un secteur (pas à une rubrique directement quoi). Lorsqu’on déplace une rubrique qui a des brèves ailleurs, les brèves sont réaffectées au secteur de la rubrique de destination (si on coche la case de confirmation).

  Dans le cas du plan, actuellement effectivement, c’est comme si on ne cochait pas la case de confirmation.
  Est-ce une bonne idée de rendre transparent cette action de réaffectation des brèves d’une rubrique au secteur si on déplace une rubrique ?
  En tout cas ça serait dans https://zone.spip.org/trac/spip-zone/browser/_core_/plugins/plan/action/deplacer_objets.php#L60 actuellement :

  $modifs = array(’id_parent’ => $id_rubrique_new) ;
  // exception pour confirmer automatiquement le déplacement des brèves (ou autres).
  if ($objet == ’rubrique’) 
      $modifs[’confirme_deplace’] = ’oui’ ;
  
  

• Remove Plan 9 support

  29 novembre 2016, par Diego Biurrun

  Remove Plan 9 support
  Supporting the system was a nice joke for the 9 release, but it has
  
  run its course. Nowadays Plan 9 receives no testing and has no
  
  practical usefulness.
  

  • [DBH] Makefile
  • [DBH] compat/plan9/head
  • [DBH] compat/plan9/main.c
  • [DBH] compat/plan9/printf
  • [DBH] configure
  • [DBH] doc/platform.texi
  • [DBH] libavformat/os_support.h
  • [DBH] library.mak
  • [DBH] tests/checkasm/Makefile

• YUV8_420P - AVFrame conversion hazard (only Y plan)

  4 mai 2017, par Flow

  I’m working on a FFMPEG application. The goal is to convert a picture (YUV input format) to an AVFrame to be able to process it (by applying a specific filter) and then realize the invert conversion to redirect it to the output.

  Although some filters as drawgrid or noise are perfectly working, filters which apply some "space transformation" (as a "crop" or a "hflip") seem to affect only over the Y component. The colors of the output pictures aren’t filtered which leads to an unsatisfying result.

  I’m asking myself why I have such a result but I didn’t reach to find the problem origin.

  Here is the part of cod which convert the YUV picture to an AVFrame :

  unsigned int i = 0;
  
  int number_common_channels = MIN(IMAGEFORMAT_COMPONENTS, AV_NUM_DATA_POINTERS);
  
  
  
  // Transfer the image informations (width, height, pitch and data)
  
  if ((av_im->width = yuv_im->width[0]) <= 0)
  
  {
  
      cu_printf(ERROR, "Width of destination picture null or negative");
  
      return -1;
  
  }
  
  if((av_im->height = yuv_im->height[0]) <= 0)
  
  {
  
      cu_printf(ERROR, "Height of destination picture null or negative");
  
      return -1;
  
  }
  
  for (i=0; i < number_common_channels; i++)
  
  {
  
      av_im->linesize[i] = yuv_im->pitch[i];
  
      av_im->data[i] = yuv_im->data[i];
  
  }

  If necessary, I can transmit you other parts of the cod where the problem could be. Thanks for your cooperation.

  Flow.

  EDIT 1 : After some researches, it would be possible the problem came from my function which initializes the filter graph. Actually, I used the FFMPEG example given on their website to make it and I deleted the options to the pixel format list because I thought it was useless. It’s possible this function and more precisely the av_opt_set_int_list could be the key, but I don’t reach to find a good example using it. Also, another function, av_opt_set_pixel_fmt was created in the last FFMPEG versions and this could be well to try using it, but I don’t know how to do. So please if someone has a good example with that, I’ll took it with hapiness.

  EDIT 2 : The problem came from the way I copied my data back after the filter was applied. Closed.