Recherche avancée

Médias (1)

Mot : - Tags -/Rennes

Autres articles (67)

  • Les images

    15 mai 2013
  • Mediabox : ouvrir les images dans l’espace maximal pour l’utilisateur

    8 février 2011, par

    La visualisation des images est restreinte par la largeur accordée par le design du site (dépendant du thème utilisé). Elles sont donc visibles sous un format réduit. Afin de profiter de l’ensemble de la place disponible sur l’écran de l’utilisateur, il est possible d’ajouter une fonctionnalité d’affichage de l’image dans une boite multimedia apparaissant au dessus du reste du contenu.
    Pour ce faire il est nécessaire d’installer le plugin "Mediabox".
    Configuration de la boite multimédia
    Dès (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

Sur d’autres sites (7228)

  • Naming convention to create/merge multiple video files

    25 octobre 2015, par Anay Bose

    I am trying to concat a few .mp4 files. I first create intermediate .mpg clips, and then merge them together with ’cat’ command ; then convert it to .mp4 files

    for example,

    ffmpeg -i input1.mp4 -qscale:v 1 intermediate1.mpg
    ffmpeg -i input2.mp4 -qscale:v 1 intermediate2.mpg

    // Now merge them together

    cat intermediate1.mpg intermediate2.mpg > intermediate_all.mpg
    ffmpeg -i intermediate_all.mpg -qscale:v 2 output.mp4

    Now, I would like to merge all .mpg files within a directory
    the following command works if I have max 9 .mpg files

    cat folder/*.mpg > intermediate_all.mpg

    But, if I got more then 9 .mpg files, the movie sequence breakes, meaning no. 10 clip shows up after no. 1 clip which I do not want. Is there any naming convention that I can follow with ffmpeg. In imagemagick, I can easily use the following syntax and it works, but in ffmpeg it is not working.

    cat folder/%d.mpg or cat folder/%d.mpg[0-10]
  • What does the left_block_options array represent in the fill_decode_neighbors function of FFmpeg?

    28 décembre 2024, par mike xu

    I am studying the source code of FFmpeg, specifically the fill_decode_neighbors function. I am trying to understand how the decoding process works, especially the usage of the left_block_options array.
Here is the relevant code snippet :

    


    static const uint8_t left_block_options[4][32] = {
        { 0, 1, 2, 3, 7, 10, 8, 11, 3 + 0 * 4, 3 + 1 * 4, 3 + 2 * 4, 3 + 3 * 4, 1 + 4 * 4, 1 + 8 * 4, 1 + 5 * 4, 1 + 9 * 4 },
        { 2, 2, 3, 3, 8, 11, 8, 11, 3 + 2 * 4, 3 + 2 * 4, 3 + 3 * 4, 3 + 3 * 4, 1 + 5 * 4, 1 + 9 * 4, 1 + 5 * 4, 1 + 9 * 4 },
        { 0, 0, 1, 1, 7, 10, 7, 10, 3 + 0 * 4, 3 + 0 * 4, 3 + 1 * 4, 3 + 1 * 4, 1 + 4 * 4, 1 + 8 * 4, 1 + 4 * 4, 1 + 8 * 4 },
        { 0, 2, 0, 2, 7, 10, 7, 10, 3 + 0 * 4, 3 + 2 * 4, 3 + 0 * 4, 3 + 2 * 4, 1 + 4 * 4, 1 + 8 * 4, 1 + 4 * 4, 1 + 8 * 4 }
    };


    


    While I understand that this array plays a role in determining neighboring blocks for decoding, I am unclear about :

    


    The specific meaning of the array values.
How this array interacts with the decoding process, especially in relation to intra-prediction or block positioning.
Instead of a detailed explanation, I would greatly appreciate :

    


    Any keywords I can look up to understand this topic better (e.g., terms from the H.264 standard or FFmpeg documentation).
Links to related documentation, articles, or sections in the H.264 specification.
Suggestions on where I might find similar examples or detailed discussions about intra-block neighbor handling in FFmpeg.
Thank you for any resources or pointers you can provide !

    


  • avcodec/v4l2_buffers : Fix infinite loop

    27 octobre 2019, par Andriy Gelman
    avcodec/v4l2_buffers : Fix infinite loop
    

    This part of the code counts the number of planes returned by the v4l2
    device for each queried capture/output buffer.
    When testing the GPU h264 encoder on Nvidia's Jetson Nano, this caused an
    infinite loop because avbuf->buf.length included some empty buffers (i.e.
    where avbuf->buf.m.planes[i].length = 0), meaning that the counter was
    never incremented and break was never reached.
    This is fixed in the commit by using a well defined iteration range.

    Signed-off-by : Aman Gupta <aman@tmm1.net>

    • [DH] libavcodec/v4l2_buffers.c