Recherche avancée

Médias (91)

Autres articles (67)

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

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

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

  • How is the FFMPEG x264 result bitrate calculated ?

    12 septembre 2022, par secondplace

    When encoding in x264 (libx264) there is a listing at the end showing different encoding stats. I noticed that the Bitrate is too high. I was wondering how this can be.

    


    Here is an example :

    


    frame=177719 fps= 24 q=-1.0 Lsize= 4768888kB time=02:03:35.74 bitrate=5268.1kbits/s dup=0 drop=43 speed=1.01x
video:4186558kB audio:579355kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.062419%


    


    From the first two result lines I can grab the stream size and stream duration. From that i can calculate the overall bitrate

    


    (4186558 * 8) / 7415.744 = 4516.39970311812


    


    However the last FFMPEG output shows an additional 108.4kb/s :

    


    [libx264 @ 0000026e1011f440] kb/s:4624.79


    


    When I use MediaInfo to get the stream size and stream duration it's also a little different.

    


    (4192906.438 * 8) / 7415.742 = 4523.24952836817


    


    The manual calculations from FFMPEG and MediaInfo are close enough and not significantly different however where are the 100kb/s+ from FFMPEG results coming from ?

    


    Edit :

    


    I just found out that using --parsespeed=1 in MediaInfo CLI will give more accurate results for Variable Bitrates. Default is 0.5.

    


  • How is the FFMPEG x264 result bitrate calculated ?

    12 septembre 2022, par secondplace

    When encoding in x264 (libx264) there is a listing at the end showing different encoding stats. I noticed that the Bitrate is too high. I was wondering how this can be.

    


    Here is an example :

    


    frame=177719 fps= 24 q=-1.0 Lsize= 4768888kB time=02:03:35.74 bitrate=5268.1kbits/s dup=0 drop=43 speed=1.01x
video:4186558kB audio:579355kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.062419%


    


    From the first two result lines I can grab the stream size and stream duration. From that i can calculate the overall bitrate

    


    (4186558 * 8) / 7415.744 = 4516.39970311812


    


    However the last FFMPEG output shows an additional 108.4kb/s :

    


    [libx264 @ 0000026e1011f440] kb/s:4624.79


    


    When I use MediaInfo to get the stream size and stream duration it's also a little different.

    


    (4192906.438 * 8) / 7415.742 = 4523.24952836817


    


    The manual calculations from FFMPEG and MediaInfo are close enough and not significantly different however where are the 100kb/s+ from FFMPEG results coming from ?

    


    Edit :

    


    I just found out that using --parsespeed=1 in MediaInfo CLI will give more accurate results for Variable Bitrates. Default is 0.5.

    


  • Read id3 tag from ffmpeg-converted mp3 files

    14 octobre 2012, par payal

    I have the below script for reading the id3 tag for mp3 files. I have checked manually that id3 tags are there in mp3 files but my output always returns for a few files :
    MP3 file does not have any ID3 tag!

    I am converting these files from ffmpeg. When I run the below code for original files, it shows the id3 tags, but when I run the script for converted files (by ffmpeg), it is not showing any id3 tags . I have downloaded both original and converted files and checked them and found that both files have exactly the same tags but the below code gives the error message anyway.

    Here is the code :

     <?php
    
 $mp3 = "4.mp3"; //The mp3 file.
    

    
 $filesize = filesize($mp3);
    
 $file = fopen("4.mp3", "r");
    

    
 fseek($file, -128, SEEK_END); // It reads the 
    

    
 $tag = fread($file, 3);
    

    
 if($tag == "TAG")
    
 {
    
     $data["title"] = trim(fread($file, 30));
    

    
     $data["artist"] = trim(fread($file, 30));
    

    
     $data["album"] = trim(fread($file, 30));
    

    
     $data["year"] = trim(fread($file, 4));
    

    
      $data["genre"] = trim(fread($file, 1));
    

    

    

    
   }
    
   else
    
     die("MP3 file does not have any ID3 tag!");
    

    
   fclose($file);
    

    
   while(list($key, $value) = each($data))
    
   {
    
     print("$key: $value<br />\r\n");    
    
  }
    
 ?>    

Navigation