Recherche avancée

Médias (1)

Mot : - Tags -/vidéo

Autres articles (43)

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

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • Contribute to translation

    13 avril 2011

    You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
    To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
    MediaSPIP is currently available in French and English (...)

Sur d’autres sites (5683)

  • 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;
    
}

  • Anomalie #4257 : Impossible de lire certaines descriptions XML et validation XML bloquée par écran...

    28 décembre 2018

    Au temps pour moi, c’est dans le core et non dans SVP :
    https://core.spip.net/projects/spip/repository/entry/branches/spip-3.2/ecrire/plugins/infos_paquet.php#L81

    1. <span class="CodeRay"><span class="local-variable">$h</span> = <span class="predefined">$GLOBALS</span>[<span class="string"><span class="delimiter">'</span><span class="content">meta</span><span class="delimiter">'</span></span>][<span class="string"><span class="delimiter">'</span><span class="content">adresse_site</span><span class="delimiter">'</span></span>] . <span class="string"><span class="delimiter">'</span><span class="content">/</span><span class="delimiter">'</span></span>
      2. 

    2.         . <span class="predefined">substr</span>(<span class="string"><span class="delimiter">"</span><span class="local-variable">$dir_plugins</span><span class="local-variable">$plug</span><span class="content">/</span><span class="delimiter">"</span></span>, <span class="predefined">strlen</span>(_DIR_RACINE)) . <span class="string"><span class="delimiter">'</span><span class="content">paquet.xml</span><span class="delimiter">'</span></span>;
      3. 

    3. </span>
      4. 

    Télécharger

    En remplaçant $GLOBALS[’meta’][’adresse_site’] . ’/’ par ’../’

    Ça passe. Mais je suppose qu’il y a une syntaxe plus générale pour calculer le chemin relatif à ecrire/

  • fftools/ffmpeg : store stream media type in OutputStream

    11 avril 2023, par Anton Khirnov
    fftools/ffmpeg : store stream media type in OutputStream

    Reduces access to a deeply nested muxer property
    
OutputStream.st->codecpar->codec_type for this fundamental and immutable
    
stream property.
    

    Besides making the code shorter, this will allow making the AVStream
    
(OutputStream.st) private to the muxer in the future.
    • [DH] fftools/ffmpeg.c
    • [DH] fftools/ffmpeg.h
    • [DH] fftools/ffmpeg_mux.c
    • [DH] fftools/ffmpeg_mux_init.c

Navigation