Recherche avancée

Médias (91)

Autres articles (12)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

  • Ajouter notes et légendes aux images

    7 février 2011, par

    Pour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
    Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
    Modification lors de l’ajout d’un média
    Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...)

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

  • Stream to / from FLV

    18 août 2015, par MKN Web Solutions

    Is it possible to stream to an FLV (via exec ffmpeg) and have a client from from that FLV for real time stream (http).

    I’m not sure if this is something of RTMPT, but I’ve seen sites that use FLV to stream. I currently already use HLS and DASH, I’m just trying to experiment with other channels.

  • How to recover video from H264 frames and timestamps [closed]

    10 juin 2024, par kokosda

    My service receives H264 frames and some metadata related to them like Timestamp from MS Teams.

    


    Observations :

    


      

    • Those frames are inter-frame compressed.

      • 


    • Resolution of those frames can change.

      • 


    • Timestamps are like this one 39264692280552704. That represents year 125 if fed to .NET consturctor new DateTime(39264692280552704), so I need to add 1899 years to get a real date.

      • 


    • I can wrap the sequence to a playable mp4 container with ffmpeg -i input.h264 -c copy output.mp4, however it is not what I want because the resulting video plays too fast, like on fast forward. Thus, I would like those timestamps would be considered to recover a real timeline.

      • 


    


    I merged all the H264 frames in one file like input.h264 and saved all the timestamps in another file like metadata.json. In metadata.json, each object describes a single frame from input.h264.

    


    My question is how to recover the source video from frames and timestamps that I received from Teams ? Particularly, using FFMPEG.

    


  • lavu : fix memory leaks by using a mutex instead of atomics

    14 novembre 2014, par wm4
    lavu : fix memory leaks by using a mutex instead of atomics

    The buffer pool has to atomically add and remove entries from the linked
    
list of available buffers. This was done by removing the entire list
    
with a CAS operation, working on it, and then setting it back again
    
(using a retry-loop in case another thread was doing the same thing).
    

    This could effectively cause memory leaks : while a thread was working on
    
the buffer list, other threads would allocate new buffers, increasing
    
the pool’s total size. There was no real leak, but since these extra
    
buffers were not needed, but not free’d either (except when the buffer
    
pool was destroyed), this had the same effects as a real leak. For some
    
reason, growth was exponential, and could easily kill the process due
    
to OOM in real-world uses.
    

    Fix this by using a mutex to protect the list operations. The fancy
    
way atomics remove the whole list to work on it is not needed anymore,
    
which also avoids the situation which was causing the leak.
    

    Signed-off-by : Anton Khirnov <anton@khirnov.net>
    • [DH] libavutil/buffer.c
    • [DH] libavutil/buffer_internal.h

Navigation