Recherche avancée

Médias (1)

Mot : - Tags -/artwork

Autres articles (39)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

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

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

Sur d’autres sites (5932)

  • FFmpeg stucks for few seconds on start

    7 février 2018, par tarasmorskyi

    I’m trying to cut and resize video on Android(but it is similar on MacOS) , but when I run the ffmpeg command it returns me

    frame= 0 fps=0.0 q=0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed=

    It repeats for about 20 sec (I have 4K video with 3 sec duration).

    Is there any way to improve process speed ? Here is example of my ffmpeg command

    ffmpeg -y -i input.mp4 -ss 00:01.82 -to 00:02.94 -vf scale=500:1024 -c:v libx264 -c:a aac -b:v 500k -b:a 96k output.mp4

  • FFProbe generated data don't seem to agree with calculated data using ffmpeg libraries

    18 janvier 2020, par ark1974

    Using ffmpeg library avformat I am trying to check if the ffprobe generated data agrees with the data generated by the library. The code objective is to try to seek to the nearest key frame. When trying to seek at 100 frame or less, the codes returns 0 all the time.
    When trying to seek at 200 frame, the codes returns 4 all the time. But the result ie 4th frame don’t seem to be right. Where am I wrong ? Is my time_base conversion to actual frame faulty ?

    The test result using ffprobe

    Filename = test.mp4  
    
Duration = 00:00:10.56 
    
Fps = 25
    
Total frames = 256   
    
The key frames pkt_pts_time are at 2.120000  and 0.000000 (using -skip_frame nokey )
    
Corresponding pkt_duration_time: 0.040000 and 0.040000 (  same, why?)

    Abstract of the code :

    // Objective: seek to the nearest key frame
    
frameIndex = 200;
    
int64_t timeBase = (int64_t(pCodecCtx->time_base.num) * AV_TIME_BASE) / int64_t(pCodecCtx->time_base.den);  
    
int64_t seekTarget = int64_t(frameIndex) * timeBase;
    

    
if (av_seek_frame(pFormatCtx, -1, seekTarget, AVSEEK_FLAG_FRAME | AVSEEK_FLAG_BACKWARD) < 0) return -1;
    

    
//convert the time_base to actual frame
    
auto time2frame = [&](int64_t tb) {
    
    return tb * int64_t(pCodecCtx->time_base.den) / (int64_t(pCodecCtx->time_base.num) * AV_TIME_BASE);
    
};
    

    
AVPacket avPacket;
    
int result = av_read_frame(pFormatCtx, &avPacket);
    
if (result == 0) {
    

    
    auto dts = avPacket.dts;
    
    auto pts = avPacket.pts;
    
    auto idx = avPacket.stream_index;
    
    auto f = time2frame(pts); // expecting the actual frame here
    
    std::cout << dts << pts << idx << f;
    
}

  • Merge pull request #253 from zeroclipboard/origins-array-bug

    17 octobre 2013, par jonrohan
    Merge pull request #253 from zeroclipboard/origins-array-bug

    Array.push returns a number, not an array.

Navigation