Recherche avancée

Médias (17)

Mot : - Tags -/wired

Autres articles (63)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • Emballe médias : à quoi cela sert ?

    4 février 2011, par

    Ce plugin vise à gérer des sites de mise en ligne de documents de tous types.
    Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ;

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

Sur d’autres sites (6293)

  • libavformat stuck in ff_network_wait_fd

    3 juin 2020, par Daniel

    I'm using libavformat for remuxing some live video feeds (rtsp).

    



    I can't really create a minimal reproducable example, because the issue is not reproducable, but I have an attached debugger and if I have any minimal chance to examine the root cause I'd not skip any chance.

    



    The stream is opened via avformat_open_input, and there is a custom IO for writing the output (avformat_alloc_output_context2).

    



    The problem is that avformat is stuck in ff_network_wait_fd, at least by gdb :

    



    #0  0xb673e120 in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x004a3ff4 in ff_network_wait_fd (fd=-1357954584, write=1) at libavformat/network.c:72
#2  0xaf0f428e in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)


    



    There was a network failure during the connection or the stream and I have not got any aggressive stream closing mechanism (everything is non blocking, there is no waits, sleeps, everything is event-based by libev).

    



    This just happened once during one month so it's very hard to reproduce but it is still running and gdb is attached.

    



    I'm curious if I have any chance to dig deeper. The stack seems corrupted and also the fd seems invalid for what ff_network_wait_fd waits for.

    



    Also, I never call ff_network_wait_fd directly, but there is an alternative : ff_network_wait_fd_timeout. Is it possible to ask libavformat to use this alternative so it won't block my thread if there is unreliable network ?

    


  • How to install ffmpeg on UBI docker images ?

    7 janvier 2024, par S. D.

    I'm looking for a simple way to install ffmpeg in a UBI8 (ubi-minimal) docker image.

    


    I tried running in the dockerfile the following :

    


    RUN microdnf upgrade
RUN microdnf install ffmpeg


    


    And I'm getting :

    


    ------
 > [7/8] RUN microdnf install ffmpeg:
#11 0.375
#11 0.375 (microdnf:1): librhsm-WARNING **: 07:58:19.229: Found 0 entitlement certificates
#11 0.375
#11 0.375 (microdnf:1): librhsm-WARNING **: 07:58:19.230: Found 0 entitlement certificates
#11 0.519 error: No package matches 'ffmpeg'
------
executor failed running [/bin/sh -c microdnf install ffmpeg]: exit code: 1



    


    How can ffmpeg be easily installed on UBI 8 ?

    


    Note : I tried referring to numerous references on the web that explain how that may be done, such as this one and this as well, but UBI seems to be working differently.

    


  • Anomalie #4128 : Bug de génération de boucle avec les modèles Spip

    11 avril 2018, par b b

    Un truc que je ne comprends pas, c’est que tu signales dans les points 7 & 8 que "Cela fonctionne sur la version minimal mais pas sur la version production." & "Le bug n’apparait plus..". Tu as donc trouvé l’origine du problème ou non ?

Navigation