Recherche avancée

Médias (91)

Autres articles (35)

  • L’espace de configuration de MediaSPIP

    29 novembre 2010, par

    L’espace de configuration de MediaSPIP est réservé aux administrateurs. Un lien de menu "administrer" est généralement affiché en haut de la page [1].
    Il permet de configurer finement votre site.
    La navigation de cet espace de configuration est divisé en trois parties : la configuration générale du site qui permet notamment de modifier : les informations principales concernant le site (...)

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

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

Sur d’autres sites (5736)

  • avcodec : export motion vectors in frame side data on demand

    16 juillet 2014, par Clément Bœsch
    avcodec : export motion vectors in frame side data on demand

    The reasoning behind this addition is that various third party
    
applications are interested in getting some motion information out of a
    
video "for free" when it is available.
    

    It was considered to export other information as well (such as the intra
    
information about the block, or the quantization) but the structure
    
might have ended up into a half full-generic, half full of codec
    
specific cruft. If more information is necessary, it should either be
    
added in the "flags" field of the AVMotionVector structure, or in
    
another side-data.
    

    This commit also includes an example exporting them in a CSV stream.
    • [DH] .gitignore
    • [DH] configure
    • [DH] doc/APIchanges
    • [DH] doc/Makefile
    • [DH] doc/codecs.texi
    • [DH] doc/examples/Makefile
    • [DH] doc/examples/extract_mvs.c
    • [DH] libavcodec/avcodec.h
    • [DH] libavcodec/mpegvideo.c
    • [DH] libavcodec/options_table.h
    • [DH] libavutil/Makefile
    • [DH] libavutil/frame.c
    • [DH] libavutil/frame.h
    • [DH] libavutil/motion_vector.h
    • [DH] libavutil/version.h

  • avformat/hls : reduce default max reload to 3

    15 mai 2023, par Michael Niedermayer
    avformat/hls : reduce default max reload to 3

    The 1000 did result in the appearance of a never ending reload loop
    

    The RFC mandates that "If the client reloads a Playlist file and finds that it has not
    
changed, then it MUST wait for a period of one-half the target
    
duration before retrying." and if it has changed
    
"the client MUST wait for at least the target duration before attempting to reload the
    
Playlist file again"
    

    Trying to reload 3 times seems a better default than 1000 given these
    
durations
    

    Issue found by : Сергей Колесников
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavformat/hls.c

  • Using Node.js module fluent-ffmpeg to convert video but my files end up corrupt

    28 juin 2017, par El Guapo

    i am writing a node based media encoding tool and have found a few good node packages that will help me to do this, but the output files are either totally corrupt or it only encodes half the video.

    The main node package i am using is fluent-ffmpeg, and i am trying it with the following code :

    var ffmpeg = require('fluent-ffmpeg');
    

    
var proc = new ffmpeg({ source: 'uploads/robocop-tlr1_h480p.mov', nolog: false})
    
  .withVideoCodec('libx264')
    
  .withVideoBitrate(800)
    
  .withAudioCodec('libvo_aacenc')
    
  .withAudioBitrate('128k')
    
  .withAudioChannels(2)
    
  .toFormat('mp4')
    
  .saveToFile('output/robocop.mp4',
    
    function(retcode, error){
    
        console.log('file has been converted succesfully');
    
});

    There is not a problem with the source video as i encoded it just fine using FFmpeg normally with the following comand line string (i run it from a batch file) :

    "c:\ffmpeg\bin\ffmpeg.exe" -i %1 -acodec libvo_aacenc -b:a 128k -ac 2 -vcodec libx264 -b:v 800k -f mp4 "../output/robocop2.mp4"

    Any ideas what i am doing wrong here ?

Navigation