Recherche avancée

Médias (1)

Mot : - Tags -/publier

Autres articles (104)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

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

  • Gestion de la ferme

    2 mars 2010, par

    La ferme est gérée dans son ensemble par des "super admins".
    Certains réglages peuvent être fais afin de réguler les besoins des différents canaux.
    Dans un premier temps il utilise le plugin "Gestion de mutualisation"

Sur d’autres sites (6564)

  • Generating 64kbps audio-only mpegts for HTTP Live segmenter to meet 64kbps audio only requirement

    14 juin 2013, par Pobre

    I am trying to convert our mp4 files into mpeg-ts and segment it into .ts files for my iphone app to play. I am using Carson McDonalds's HTTP-Live-Video-Stream-Segmenter-and-Distributor to do that.

    I got his stuff complied and working correctly. I am currently trying to meet Apple's requirement where I need to provide a baseline 64 kbps audio only stream to my m3u8 playlist.
    Carson doesn't seem to have a profile for that.

    I need to be able to generate 64kbps audio-only stream from mp4, and turn that into mpeg-ts for the segmenter into ts. I am trying to find the right ffmpeg command that will validate without problem using Apple's mediastreamvalidator.

    So far I modified an existing encoding profile to try to achieve 64kbps total :

    ffmpeg -er 4 -i %s -f mpegts -acodec libmp3lame -ar 22050 -ab 32k -s 240x180 -vcodec libx264 -b 16k -flags +loop+mv4 -cmp 256 -partitions +parti4x4+partp8x8+partb8x8 -subq 7 -trellis 1 -refs 5 -coder 0 -me_range 16 -keyint_min 25 -sc_threshold 40 -i_qfactor 0.71 -bt 64k -maxrate 16k -bufsize 16k -rc_eq 'blurCplx^(1-qComp)' -qcomp 0.6 -qmin 10 -qmax 51 -qdiff 4 -level 30 -aspect 4:3 -r 10 -g 30 -async 2 - | %s %s %s %s %s

    but then when I try to validate it using mediastreamvalidator, it gives error after few ts :

    Playlist Validation : OK

    Segments :

    sample_cell_4x3_64k-00001.ts :

    WARNING : Media segment exceeds target duration of 10.00 seconds by 1.30 seconds (segment duration is 11.30 seconds)

    sample_cell_4x3_64k-00002.ts :

    WARNING : Media segment exceeds target duration of 10.00 seconds by 1.40 seconds (segment duration is 11.40 seconds)

    ....
    ....

    sample_cell_4x3_64k-00006.ts :

    ERROR : (-1) Unknown video codec : 1836069494 (program 0, track 0)
    ERROR : (-1) failed to parse segment as either an MPEG-2 TS or an ES

    sample_cell_4x3_64k-00007.ts :

    ERROR : (-1) Unknown video codec : 1836069494 (program 0, track 0)
    ERROR : (-1) failed to parse segment as either an MPEG-2 TS or an ES

    ....
    ....
    Average segment duration : 10.26 seconds
    Average segment bitrate : 376797.92 bps
    Average segment structural overhead : 349242.17 bps (92.69 %)

    Is there someway I can generate this correctly with just audio which totals 64kbps and turn it into mpeg-ts ready to be segmented and validated correctly ?

    Am I approaching the problem right ?

  • convert .mts to flv using ffmpeg and file size will 300 mb and more [closed]

    20 juin 2013, par user1966466

    i have problem , when i have uploaded video and convert to flv for all formate .

    my code is not working when i have used .mts formate and size 300 MB and more

    if(move_uploaded_file($tmp, $path.$video_name_extension)){

       exec("/usr/local/bin/ffmpeg -i courses/$video_name_extension  -ar 44100  -ab 128k  -r 25  -vcodec flv -crf 15 -b 700000 courses/$video_name");          
       exec("/usr/local/bin/ffmpeg  -itsoffset -4  -i courses/$video_name_extension -vcodec mjpeg -vframes 1 -an -f rawvideo -s 320x240 courses/$video_image");


           $cmd = "/usr/local/bin/ffmpeg -i courses/$video_name 2>&1";
           if (preg_match('/Duration: ((\d+):(\d+):(\d+))/s', `$cmd`, $time)) {
              $total = ($time[2] * 3600) + ($time[3] * 60) + $time[4];            
           }
           exec($cmd);
           $time = convertToHHMMSS($total);
           //echo "updated 2";
       //  exit;
           mysql_query("INSERT INTO tbl_teacher_video (user_id,title,video,video_image,duration,arts_name,video_type,added_on) VALUES ('".$_SESSION['id']."','$txt','$video_name','$video_image','$time','".$_POST['courseradio']."','2','".date('Y-m-d')."')");
           unlink('courses/'.$video_name_extension);
  • Revision c24d922396 : Add averaging-SAD functions for 8-point comp-inter motion search. Makes first 5

    25 juin 2013, par Ronald S. Bultje

    Changed Paths :
     Modify /vp9/common/vp9_rtcd_defs.sh


     Modify /vp9/encoder/vp9_mcomp.c


     Modify /vp9/encoder/vp9_onyx_if.c


     Modify /vp9/encoder/vp9_sad_c.c


     Modify /vp9/encoder/vp9_variance.h


     Modify /vp9/encoder/x86/vp9_sad_sse2.asm



    Add averaging-SAD functions for 8-point comp-inter motion search.

    Makes first 50 frames of bus @ 1500kbps encode from 3min22.7 to 3min18.2,
    i.e. 2.3% faster. In addition, use the sub_pixel_avg functions to calc
    the variance of the averaging predictor. This is slightly suboptimal
    because the function is subpixel-position-aware, but it will (at least
    for the SSE2 version) not actually use a bilinear filter for a full-pixel
    position, thus leading to approximately the same performance compared to
    if we implemented an actual average-aware full-pixel variance function.
    That gains another 0.3 seconds (i.e. encode time goes to 3min17.4), thus
    leading to a total gain of 2.7%.

    Change-Id : I3f059d2b04243921868cfed2568d4fa65d7b5acd