Recherche avancée

Médias (0)

Mot : - Tags -/api

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (111)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

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

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

Sur d’autres sites (13963)

  • Rate-Control management in ffmpeg

    28 février 2014, par alexbuisson

    Hi I try to understand how ffmpeg wrap its rc_max_rate parameters to the x264 parameters
    and I'm wondering what the following code means ? It's a piece of code coming from ffmpeg/libavcodec/mpeg_video_enc.c but the commit log is not explicit and I don't know from where those Magic Number come from !

    So if you have an idea or an URL that can explain why those formula where implemented, it will be useful.

    if (avctx->rc_max_rate && !avctx->rc_buffer_size) {
    
        switch(avctx->codec_id) {
    
        case AV_CODEC_ID_MPEG1VIDEO:
    
        case AV_CODEC_ID_MPEG2VIDEO:
    
            avctx->rc_buffer_size = FFMAX(avctx->rc_max_rate, 15000000) * 112L / 15000000 * 16384;
    
            break;
    
        case AV_CODEC_ID_MPEG4:
    
        case AV_CODEC_ID_MSMPEG4V1:
    
        case AV_CODEC_ID_MSMPEG4V2:
    
        case AV_CODEC_ID_MSMPEG4V3:
    
            if       (avctx->rc_max_rate >= 15000000) {
    
                avctx->rc_buffer_size = 320 + (avctx->rc_max_rate - 15000000L) * (760-320) / (38400000 - 15000000);
    
            } else if(avctx->rc_max_rate >=  2000000) {
    
                avctx->rc_buffer_size =  80 + (avctx->rc_max_rate -  2000000L) * (320- 80) / (15000000 -  2000000);
    
            } else if(avctx->rc_max_rate >=   384000) {
    
                avctx->rc_buffer_size =  40 + (avctx->rc_max_rate -   384000L) * ( 80- 40) / ( 2000000 -   384000);
    
            } else
    
                avctx->rc_buffer_size = 40;
    
            avctx->rc_buffer_size *= 16384;
    
            break;
    
        }
    
        if (avctx->rc_buffer_size) {
    
            av_log(avctx, AV_LOG_INFO, "Automatically choosing VBV buffer size of %d kbyte\n", avctx->rc_buffer_size/8192);
    
        }
    
    }

  • lavc/qsvenc : update the selection of bitrate control method

    1er février 2024, par Haihao Xiang
    lavc/qsvenc : update the selection of bitrate control method

    The default method is changed to CQP
    

    Signed-off-by : Haihao Xiang <haihao.xiang@intel.com>
    • [DH] Changelog
    • [DH] doc/encoders.texi
    • [DH] libavcodec/qsvenc.c
    • [DH] libavcodec/qsvenc_av1.c
    • [DH] libavcodec/qsvenc_h264.c
    • [DH] libavcodec/qsvenc_hevc.c
    • [DH] libavcodec/qsvenc_mpeg2.c
    • [DH] libavcodec/qsvenc_vp9.c

  • FFMPEG problem with concat outpoint option

    8 juillet 2021, par DavidB

    Trying to concatenate MP4 files

    &#xA;

    ffmpeg -f concat -i c.txt -c copy concat.mp4&#xA;

    &#xA;

    c.txt file content

    &#xA;

    ffconcat version 1.0&#xA;file first.mp4&#xA;outpoint 55000.0&#xA;file sec.mp4&#xA;

    &#xA;

    it is done but takes a too long time, and during processing throws a lot of errors

    &#xA;

    [mp4 @ 0000020447e51100] pts has no value&#xA;[mp4 @ 0000020447e51100] Application provided duration: 2266868961 / timestamp: 2425630048 is out of range for mov/mp4 format&#xA;[mp4 @ 0000020447e51100] pts has no value&#xA;[mp4 @ 0000020447e51100] Application provided duration: 2266869984 / timestamp: 2425631072 is out of range for mov/mp4 format&#xA;[mp4 @ 0000020447e51100] pts has no value&#xA;[mp4 @ 0000020447e51100] Application provided duration: 2266871007 / timestamp: 2425632096 is out of range for mov/mp4 format&#xA;[mp4 @ 0000020447e51100] pts has no value&#xA;[mp4 @ 0000020447e51100] Application provided duration: 2266872030 / timestamp: 2425633120 is out of range for mov/mp4 format&#xA;[mp4 @ 0000020447e51100] pts has no value&#xA;[mp4 @ 0000020447e51100] Application provided duration: 2266873053 / timestamp: 2425634144 is out of range for mov/mp4 format&#xA;&#xA;frame=111223 fps=11907 q=-1.0 Lsize=   19922kB time=15:18:27.42 bitrate=   3.0kbits/s speed=5.9e&#x2B;03x&#xA;video:14229kB audio:2597kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 18.403999%&#xA;

    &#xA;

    I noticed that somehow it depends on file size or duration (e.g. if outpoint is 50000.0 it is ok and no errors) but I cannot get what is the exact problem.

    &#xA;

Navigation