Recherche avancée

Médias (0)

Mot : - Tags -/logo

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

Autres articles (54)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

Sur d’autres sites (7085)

  • How to calculate ffmpeg output file size ?

    25 septembre 2011, par poundifdef

    I am using ffmpeg to convert home videos to DVD format and want to calculate the output file size before doing the conversion.

    My input file has a bit rate of 7700 kbps and is 114 seconds long. The audio bitrate is 256 kbit (per second ?) The input file is 77MB. To get this information I ran :

    mplayer -vo null -ao null -frames 0 -identify input.MOD

    So in theory, the input file should have (roughly) a file size of :

    ((7700 / 8) * 114) / 1024

    That is, (7700 / 8) is kilobytes/second, multiplied by 114 seconds, and then converted to megabytes. This gives me 107MB, which is way beyond my 77. Thus I am skeptical of his formula.

    That said, after converting the video :

    ffmpeg -i input.MOD -y -target ntsc-dvd -sameq -aspect 4:3 output.mpg

    The numbers seem to make more sense. Bitrate is 9000 kbps, and applying the above formula, I get 125MB, and my actual output file size is 126MB.

    So, two questions :

    1. How do I factor the audio bitrate into this calculation ? Is it additive (video file size + audio file size) ?

    2. Do DVDs always have a 9000 kilobit/second rate ? Is that the definition of a DVD ? Or might that change depending on video quality of my input video ? What does "-target ntsc-dvd" guarantee about my video ?

    3. Why does my input file not "match" the calculation, but the output file does ? Is there some other variable I'm not accounting for ?

    What is the correct way to calculate filesize ?

  • AVCodecContext settings for H264 (1080i)

    23 septembre 2013, par moose

    I'm trying to configure x264 for 1080i capturing. Most of these settings below are found in different examples. However, compiled together they don't work. ffmpeg API reports no error, but avcodec_encode_video() always returns zero.

    Some of the numbers are strange to me... for example, gop_size. Isn't 250 too high ?

    Event you can't offer the final answer, I'm still interested in any kind of comment on this subject.

    pCodecContext->codec_type              = AVMEDIA_TYPE_VIDEO;
    pCodecContext->codec_id                = CODEC_ID_H264;

    pCodecContext->coder_type              = FF_CODER_TYPE_AC;
    pCodecContext->flags                  |= CODEC_FLAG_LOOP_FILTER | CODEC_FLAG_INTERLACED_ME | CODEC_FLAG_INTERLACED_DCT;
    pCodecContext->me_cmp                 |= 1;
    pCodecContext->partitions             |= X264_PART_I8X8 | X264_PART_I4X4 | X264_PART_P8X8 | X264_PART_B8X8;
    pCodecContext->me_method               = ME_UMH;
    pCodecContext->me_subpel_quality       = 8;
    pCodecContext->me_range                = 16;

    pCodecContext->bit_rate                = 10 * 1024 * 1024; // 10 Mbps??
    pCodecContext->width                   = 1920;
    pCodecContext->height                  = 1080;

    pCodecContext->time_base.num           = 1;    // 25 fps
    pCodecContext->time_base.den           = 25;   // 25 fps

    pCodecContext->gop_size                = 250; // 250
    pCodecContext->keyint_min              = 25;
    pCodecContext->scenechange_threshold   = 40;
    pCodecContext->i_quant_factor          = 0.71f;
    pCodecContext->b_frame_strategy        = 1;
    pCodecContext->qcompress               = 0.6f;
    pCodecContext->qmin                    = 10;
    pCodecContext->qmax                    = 51;
    pCodecContext->max_qdiff               = 4;
    pCodecContext->max_b_frames            = 3;
    pCodecContext->refs                    = 4;
    pCodecContext->directpred              = 3;
    pCodecContext->trellis                 = 1;
    pCodecContext->flags2                 |= CODEC_FLAG2_WPRED | CODEC_FLAG2_MIXED_REFS | CODEC_FLAG2_8X8DCT | CODEC_FLAG2_FASTPSKIP;  // wpred+mixed_refs+dct8x8+fastpskip
    pCodecContext->weighted_p_pred         = 2; // not implemented with interlaced ??
    pCodecContext->crf                     = 22;

    pCodecContext->pix_fmt                 = PIX_FMT_YUV420P;

    pCodecContext->thread_count            = 0;
  • What is the meaning of the hexadecimal value that follows the avc1 in an m3u8 variant playlist

    16 février 2013, par Anand

    From this apple's sample variant playlist

    https://devimages.apple.com.edgekey.net/resources/http-streaming/examples/bipbop_4x3/bipbop_4x3_variant.m3u8

    i see hexadecimal numbers follow the av1 like avc1.4d4015,avc1.4d401e,avc1.4d401e,avc1.4d401f can anybody know what is the meaning of them