Recherche avancée

Médias (91)

Autres articles (68)

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

Sur d’autres sites (9875)

  • avcodec/h264dec : apply H.274 film grain

    17 août 2021, par Niklas Haas
    avcodec/h264dec : apply H.274 film grain
    

    Because we need access to ref frames without film grain applied, we have
    to add an extra AVFrame to H264Picture to avoid messing with the
    original. This requires some amount of overhead to make the reference
    moves work out, but it allows us to benefit from frame multithreading
    for film grain application "for free".

    Unfortunately, this approach requires twice as much RAM to be constantly
    allocated for ref frames, due to the need for an extra buffer per
    H264Picture. In theory, we could get away with freeing up this memory as
    soon as it's no longer needed (since ref frames do not need film grain
    buffers any longer), but trying to call ff_thread_release_buffer() from
    output_frame() conflicts with possible later accesses to that same frame
    and I'm not sure how to synchronize that well.

    Tested on all three cases of (no fg), (fg present but exported) and (fg
    present and not exported), with and without threading.

    Co-authored-by : James Almer <jamrial@gmail.com>
    Signed-off-by : Niklas Haas <git@haasn.dev>
    Signed-off-by : James Almer <jamrial@gmail.com>

    • [DH] libavcodec/h264_picture.c
    • [DH] libavcodec/h264_slice.c
    • [DH] libavcodec/h264dec.c
    • [DH] libavcodec/h264dec.h
  • avcodec/h264_picture : don't assume Film Grain Params side data will be present

    17 octobre 2021, par James Almer
    avcodec/h264_picture : don't assume Film Grain Params side data will be present
    

    If a decoding error happens before frame side data is allocated, this assert may be
    triggered. And since applying film grain is not enforced (we just warn it wasn't
    applied and move on), we can just do that in such scenarios.

    Fixes : Assertion failure
    Fixes : clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_H264_fuzzer-5528650032742400

    Signed-off-by : James Almer <jamrial@gmail.com>

    • [DH] libavcodec/h264_picture.c
  • Stream RTSP from ONVIF general camera to Youtube

    4 septembre 2017, par Samul

    I have a wifi camera that uses RTSP/ONVIF protocol and after reading FFMPEG docs and some threads at Google I am trying to broadcast the stream to Youtube. So I started a broadcast at youtube and in my computer in ffmpeg I executed this command :

    ffmpeg -f lavfi -i anullsrc -rtsp_transport udp -i rtsp://200.193.21.176:6002/onvif1 -tune zerolatency -vcodec libx264 -t 12:00:00 -pix_fmt + -c:v copy -c:a aac -strict experimental -f flv rtmp://x.rtmp.youtube.com/live2/private_key

    The command above looks like it’s correct cause it ouputs constantly something like this :

    log of ffmpeg

    The problem is that at YOUTUBE it still says I am offline. Why ?