Recherche avancée

Médias (0)

Mot : - Tags -/content

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (111)

  • 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 (...)

  • Personnaliser les catégories

    21 juin 2013, par

    Formulaire de création d’une catégorie
    Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
    Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire.
    Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
    Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (12631)

  • I use msys2 compile ffmpeg which Support Nividia hardware acceleration,the error [on hold]

    11 juillet 2017, par 秦先生

    I use msys2 compile ffmpeg which Support nividia hardware acceleration, I’ll do it in accordance with the requirements of nividia ’s document.
    When I execute ./configure command,this is the error ,the log file ffbuild/config.log contain this error.
    my command : ./configure —enable-nonfree —enable-nvenc —enable-cuda —enable-cuvid —enabl e-libnpp —extra-cflags=-Ilocal/include —extra-cflags=-I../include —extra-ldflag s=-L../lib

    the error : : note : this is the location of the previous definition
    gcc -L../lib -Wl,—nxcompat,—dynamicbase -Wl,—high-entropy-va -Wl,—as-needed -Wl,—image-base,0x140000000 -o /tmp/ffconf.eoLFY0Lt.exe /tmp/ffconf.Z00DOpJQ.o -lnppi -lnppc -lm -pthread -pthread -lpsapi -ladvapi32 -lshell32
    ../lib/nppc.lib(nppc64_80.dll.b) :(.text+0x2) : relocation truncated to fit : R_X86_64_32 against symbol `__imp_nppGetLibVersion’ defined in .idata$5 section in ../lib/nppc.lib(nppc64_80.dll.b)
    collect2 : error : ld returned 1 exit status
    ERROR : libnpp not found

    My computer configuration : cpu:intel(R) core(TM) i3-4170 3.70HZ RAM 16GB operate system win7 64 bit

    I used software : ffmpeg 3.2.4 gcc 5.3.0

  • {configure,avcodec/libx264} : remove separate x264_csp_bgr check

    1er juillet 2021, par Jan Ekström
    configure,avcodec/libx264 : remove separate x264_csp_bgr check

    We already require X264_BUILD >= 118, which includes an unconditional
    
definition of X264_CSP_BGR in itself, thus making this check
    
effectively always true.
    • [DH] configure
    • [DH] libavcodec/libx264.c

  • avcodec/omx : Fix handling of fragmented buffers

    17 janvier 2019, par Dave Stevenson
    avcodec/omx : Fix handling of fragmented buffers

    See https://trac.ffmpeg.org/ticket/7687
    

    If an encoded frame is returned split over two or more
    
IL buffers due to the size, then there is a race between
    
whether get_buffer will fail, return NULL, and a truncated
    
frame is passed on, or IL will return the remaining part
    
of the encoded frame.
    
If get_buffer returns NULL, part of the frame is left behind
    
in the codec, and will be collected on the next call. That
    
then leaves a frame stuck in the codec. Repeat enough times
    
and the codec FIFO is full, and the pipeline stalls.
    

    A performance improvement in the Raspberry Pi firmware means
    
that the timing has changed, and now frequently drops into the
    
case where get_buffer returns NULL.
    

    Add code such that should a buffer be received without
    
OMX_BUFFERFLAG_ENDOFFRAME that get_buffer is called with wait
    
set, so we wait for the remainder of the frame.
    
This code has been made conditional on the Pi build in case
    
other IL implementations don't handle ENDOFFRAME correctly.
    

    Signed-off-by : Dave Stevenson <dave.stevenson@raspberrypi.org>
    
Signed-off-by : Aman Gupta <aman@tmm1.net>
    
Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DH] libavcodec/omx.c

Navigation