Recherche avancée

Sur d’autres sites (6896)

• Anomalie #4119 (En cours) : Page gestion des plugins : Selecteur d’action mal positionné quand on ...

  28 mars 2018, par jean marie

  Quand on sélectionne un ou plusieurs plugins à mettre à jour via SVP et qu’on descend en bas de page pour valider, la liste déroulante est sur Désactiver par défaut alors qu’on est en train de faire une action de mise à jour.
  C’est casse gueule (j’ai désactivé plusieurs plugins au lieu de les mettre à jour).

  C’est bien adapté si on n’active pas la mise à jour via SVP :
  - soit on est sur la page des plugins actifs et on ne peut que les désactiver
  - soit est sur la page des plugins inactifs et on ne peut que les activer.
  Mais si on active la mise à jour, il y a un 3e choix : les mettre à jour. Dans ce cas, est-ce que la liste ne devrait pas être par défaut sur un champ "choisir quoi faire" ?

  Souci présent uniquement quand on coche manuellement les plugins (pour n’en mettre que certains à jour) pas quand on clique sur "Cocher les mises à jour" (ping b_b :) ).

  Sur spip-dev : https://www.mail-archive.com/spip-dev@rezo.net/msg66339.html

• Ffmpeg command not streaming to youtube [closed]

  21 avril, par Ahmed Seddik Bouchiba

  I'm trying to stream my desktop (from an X11 session) to YouTube Live using ffmpeg. I'm running this on a Linux machine with an active X server, and I set the DISPLAY variable accordingly (:0 in most cases).

  


  Here's the ffmpeg command I've tried :

  


  ffmpeg -loglevel info \
    -probesize ${PROBESIZE} -analyzeduration ${ANALYZE_DURATION} \
    -f x11grab -video_size ${VIDEO_SIZE} -r ${FRAME_RATE} -draw_mouse 0 -i ${DISPLAY} \
    -f alsa -i default \
    -deinterlace -vcodec libx264 -pix_fmt yuv420p -preset fast \
    -r 30 -g 60 -b:v 2000k -bufsize 4000k \
    -acodec libmp3lame -ar 44100 -b:a 128k \
    -map 0:v:0 -map 1:a:0 -vsync 0 \
    -f flv "${RTMP_URL}" &


  


  Environment variables are set correctly (DISPLAY, VIDEO_SIZE, FRAME_RATE, etc.), and I replaced $RTMP_URL with the correct YouTube RTMP endpoint (e.g., rtmp ://a.rtmp.youtube.com/live2/). But nothing seems to work — the stream never starts or appears on YouTube, and sometimes I get timeout or "connection refused" errors.

  


  I've checked :

  


  That I'm logged into an active X session

  


  That I have access to the display (even tried xhost +)

  


  That ffmpeg has access to ALSA (sound seems okay)

  


  Questions :

  


  Am I missing something in my command ?

  


  Is there a better way to stream both screen and audio from an X server to YouTube Live ?

  


  Could this be a codec or YouTube-specific format issue ?

  


  Any help or working examples would be really appreciated. Thanks !

  


• avcodec/nvenc : De-compensate aspect ratio compensation of DVD-like content.

  28 janvier 2015, par Philip Langdale

  avcodec/nvenc : De-compensate aspect ratio compensation of DVD-like content.
  For reasons we are not privy to, nvidia decided that the nvenc encoder
  
  should apply aspect ratio compensation to ’DVD like’ content, assuming that
  
  the content is not bt.601 compliant, but needs to be bt.601 compliant. In
  
  this context, that means that they make the following, questionable,
  
  assumptions :
  1) If the input dimensions are 720x480 or 720x576, assume the content has
  
  an active area of 704x480 or 704x576.
  2) Assume that whatever the input sample aspect ratio is, it does not account
  
  for the difference between ’physical’ and ’active’ dimensions.
  From, these assumptions, they then conclude that they can ’help’, by adjusting
  
  the sample aspect ratio by a factor of 45/44. And indeed, if you wanted to
  
  display only the 704 wide active area with the same aspect ratio as the full
  
  720 wide image - this would be the correct adjustment factor, but what if you
  
  don’t ? And more importantly, what if you’re used to ffmpeg not making this kind
  
  of adjustment at encode time - because none of the other encoders do this !
  And, what if you had already accounted for bt.601 and your input had the
  
  correct attributes ? Well, it’s going to apply the compensation anyway !
  
  So, if you take some content, and feed it through nvenc repeatedly, it
  
  will keep scaling the aspect ratio every time, stretching your video out
  
  more and more and more.
  So, clearly, regardless of whether you want to apply bt.601 aspect ratio
  
  adjustments or not, this is not the way to do it. With any other ffmpeg
  
  encoder, you would do it as part of defining your input paramters or
  
  do the adjustment at playback time, and there’s no reason by nvenc
  
  should be any different.
  This change adds some logic to undo the compensation that nvenc would
  
  otherwise do.
  nvidia engineers have told us that they will work to make this
  
  compensation mechanism optional in a future release of the nvenc
  
  SDK. At that point, we can adapt accordingly.
  Signed-off-by : Philip Langdale <philipl@overt.org>
  
  Reviewed-by : Timo Rothenpieler <timo@rothenpieler.org>
  
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavcodec/nvenc.c