Recherche avancée

Sur d’autres sites (10363)

• Is it possible to re-translate RTMP stream without losing speed ? [closed]

  3 août 2024, par Lunavod

  I've been working on a stream proxy - the idea is that instead of streaming directly to Twitch, OBS streams to a local RTMP server running on the same machine. The server decodes flv from the rtmp stream into rawvideo using ffmpeg, modifies pixels, and encodes back into flv, streaming the result to twitch. Again, using ffmpeg.

  


  However, I was not able to make this setup work reliably - I always run into buffering issues on Twitch. Even if ffmpeg shows a stable bitrate and 60fps, twitch slowly loses buffer size, then pauses to buffer, and then slowly loses buffer again... This results in endlessly growing delays and frequent pauses.

  


  I simplified this setup, removing the rawvideo part together with frame modification. A simplified setup accepts the rtmp stream, and dumps it into FFmpeg, which sends it to Twitch with minimal overhead (I hope).
But even with this setup, Twitch still increases latency, although considerably slower.

  


  The connection between rtmp server and ffmpeg is done with TCP sockets.
I tried using stdin, but it works even worse.
I also tried using windows named pipes but ran into a bottleneck - writing rawvideo from ffmpeg and reading it from script worked fine, as well as writing from a script and reading from ffmpeg. However, running both simultaneously in two different pipes slowed down.

  


  Initially, all of this was written in python, but I also tried using go, hoping that rtmp server realisation in python was the problem.

  


  Am I missing something fundamental here ? Is this idea possible at all ?

  


• arm : check if AS supports .dn

  29 mai 2014, par Janne Grunau

  arm : check if AS supports .dn
  Move the GNU as check before the arch specific asm checks since the .dn
  
  check requires gas compatible assembler.
  Disable the VC-1 motion compensation NEON asm which is the only part
  
  using that directive. The integrated assembler in the upcoming clang 3.5
  
  does not support .dn/.qn without plans to change that. Too much effort
  
  to implement it while it is rarely used.
  http://llvm.org/bugs/show_bug.cgi?id=18199.
  

  • [DH] configure
  • [DH] libavcodec/arm/vc1dsp_init_neon.c
  • [DH] libavcodec/arm/vc1dsp_neon.S

• Documentation #3360 : Mise à jour du profil utilisateur LDAP/SPIP

  18 mai 2016, par svpip -

  b b a écrit :

  Merci pour le retour, la doc me semble claire puisqu’elle ne mentionne pas le champ bio. Aurais-tu une idée de mention à ajouter à l’article pour clarifier la chose ?

  L’utilisateur doit être informé de cette particularité.

  Je propose le texte (à minima dans un premier temps) suivant à intégrer dans http://www.spip.net/fr_article1910.html sous forme de note de bas de page depuis la phrase existante :

  => Les champs remplis sont : nom, login et email qui viennent de LDAP (champs ’cn’, ’uid’ et ’mail’ respectivement) [1]...

  => [1] En complément de ces 3 champs, SPIP propose en option lors de l’installation en mode LDAP, de remplir le champ "bio" pour recevoir les informations issues du champs "description" généralement.
  La valeur récupérée par SPIP depuis le LDAP, lors de la première connexion, ne sera pas mise à jour par la suite.