Recherche avancée

Médias (91)

Autres articles (53)

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

  • Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs

    12 avril 2011, par

    La manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
    Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras.

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

Sur d’autres sites (13552)

  • Revision 5b756748fd : tests : clear system state after non-API calls add ClearSystemState() to reset M

    18 juin 2013, par James Zern

    Changed Paths :
     Add /test/clear_system_state.h


     Modify /test/idct_test.cc


     Modify /test/intrapred_test.cc


     Modify /test/pp_filter_test.cc


     Modify /test/sad_test.cc


     Modify /test/sixtap_predict_test.cc


     Modify /test/subtract_test.cc


     Modify /test/test.mk


     Modify /test/variance_test.cc



    tests : clear system state after non-API calls

    add ClearSystemState() to reset MMX registers avoiding corrupting
    subsequent tests.

    Change-Id : I668deb09aa7aa467709776e5819f936910698bc0

  • New FATE Test Coverage System

    10 août 2010, par Multimedia Mike — FATE Server

    I’ve been feeling a bit scattered for the last week since I was fired from my volunteer position as the FFmpeg QA manager, wondering if there is anything I should attempt to do with the project. It can’t be denied that the new system is working well. But one area I’ve wondered about is test coverage.

    Under my old regime I tracked test coverage as a wiki page which was a highly flawed method— tedious and error-prone. There are those 2 adjectives again— tedious and error-prone ; whenever I see those, I search for automation methods. I think that might be more plausible thanks to the new FATE’s tighter integration with the FFmpeg build system.

    I don’t think anyone is working on this problem so I wanted to toss out a brainstorm :

    1. First, run ’ffmpeg -formats’, ’ffmpeg -codecs’, etc. and parse the output to collect a list of all the features (full list : -formats, -codecs, -bsfs, -protocols, -filters, -pix_fmts). Transform these lists into a standardized list of features, e.g., "DEVSD  ffvhuff         Huffyuv FFmpeg variant" represents features ’decode-video-ffvhuff’, ’encode-video-ffvhuff’, ’ffvhuff-horizband’, and ’ffvhuff-dr1’.
    2. Next, tag each individual test spec with the features that it exercises. E.g., test ’fate-vqa-cc’ exercises features ’demux-wsvqa’, ’decode-video-vqavideo’, and ’decode-audio-adpcm_ima_ws’.
    3. Finally, compare the data from parts 1 and 2. Print a list of all the features that are not exercised in FATE.

    I think a lot of this could be implemented at the GNU make level. Then again, I’m no expert on GNU make syntax so I may be overestimating its capabilities. Or there might be simpler ways to automatically track test coverage stats based on the improved testing infrastructure.

  • Transcode video with ffmpeg can't play by Win10 system player ?

    16 juin 2017, par wzjing

     I’m doing a video transcoder demo with ffmpeg lib and libx264 lib. I already can transcode video successully, but the output video can only play by some powerful player like VLC. I need it can be played by the Win10 system player and the Android system player. I hava found the reason may be encode AVCodecContext args. I try to copy those args frome decode AVCodecContext, the output can be played by Win10 defualt player, but the video became totally black.
     Here is my encode AVCodecContext args :

           encoder = avcodec_find_encoder(AV_CODEC_ID_H264);

           if (!encoder) {
               av_log(NULL, AV_LOG_FATAL, "Necessary encoder not found\n");
               return AVERROR_INVALIDDATA;
           }
           enc_ctx = avcodec_alloc_context3(encoder);
           enc_ctx->height = output_height;
           enc_ctx->width = output_width;
           enc_ctx->sample_aspect_ratio = dec_ctx->sample_aspect_ratio;
           enc_ctx->bit_rate = 1000000;

           /* take first format from list of supported formats */
           if (encoder->pix_fmts)
               enc_ctx->pix_fmt = AV_PIX_FMT_YUV420P;
           else
               enc_ctx->pix_fmt = dec_ctx->pix_fmt;

           enc_ctx->time_base = av_inv_q(dec_ctx->framerate);
           enc_ctx->gop_size = 12;
           av_opt_set(enc_ctx->priv_data, "preset", "slow", 0);
           av_opt_set(enc_ctx->priv_data, "tune", "zerolatency", 0);

           enc_ctx->profile = FF_PROFILE_H264_HIGH;
           enc_ctx->codec_type = AVMEDIA_TYPE_VIDEO;      

           enc_ctx->codec_tag = 0;