Recherche avancée

Médias (0)

Mot : - Tags -/navigation

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

Autres articles (59)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

  • Personnaliser les catégories

    21 juin 2013, par

    Formulaire de création d’une catégorie
    Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
    Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire.
    Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
    Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

Sur d’autres sites (8387)

  • av_format/hlsenc : fix %v handling by format_name function

    17 juin 2019, par Bodecs Bela
    av_format/hlsenc : fix %v handling by format_name function
    

    Hi All,

    When multiple variant streams are specified by var_stream_map option, %v
    placeholder in various names ensures that each variant has its unique
    names. Most of %v handlng is done in format_name function. Currently
    in this function the result buffer is the same as the
    input pattern buffer, so you must allocate it before calling format_name
    function. It also means, that it is silently assumed that the result
    string will NOT be
    longer that the pattern string. It is true most of the time, because %v
    may appear only once in the pattern string and number of variant streams
    is less than 100 in practical cases. But theoretically it will fail if
    specified number of variant streams is greater than 100 (i.e. longer
    than 2 digits).
    This patch fixes this behaviour by altering format_name function to
    allocate the
    result buffer and return it to the caller.

    Please, review this patch.

    best,

    Bela
    >From 6377ebee8a106a9684d41b270c7d6c8e57cd3e7b Mon Sep 17 00:00:00 2001
    From : Bela Bodecs <bodecsb@vivanet.hu>
    Date : Mon, 17 Jun 2019 14:31:36 +0200
    Subject : [PATCH] av_format/hlsenc : fix %v handling by format_name function

    When multiple variant streams are specified by var_stream_map option, %v
    placeholder in various names ensures that each variant has its unique
    names. Most of %v handlng is done in format_name function. Currently
    in this function the result buffer is the same as the input pattern
    buffer, so you must allocate it before calling format_name function. It
    also means, that it is silently assumed that the result string will NOT
    be longer that the pattern string. It is true most of the time, because
    %v may appear only once in the pattern string and number of variant
    streams is less than 100 in practical cases. But theoretically it will
    fail if specified number of variant streams is greater than 100. This
    patch fixes this behaviour by altering format_name function to allocate
    the result buffer and return it to the caller.

    Signed-off-by : Bela Bodecs <bodecsb@vivanet.hu>

    • [DH] libavformat/hlsenc.c
  • How to convert a 16:9 video to 4:3 video with top & bottom blurred video bars by using ffmpeg ?

    27 décembre 2018, par Wai Gyi

    I would like to convert a landscape video to a square video with blur bars at top and bottom.

    I tried to adapt the commands from the following link but not succeeded.

    FFmpeg : How to convert horizontal video 16:9 to vertical video 9:16, with blurred background on top and bottom sides

    So, can someone share a ffmpeg command with me ?

    Thank you very much for your help.

    Update : I tried again and get a working command. Please check and review.

       ffmpeg -i in.mp4 -lavfi "[0:v]scale=iw:iw*3/4,boxblur=luma_radius=min(h\,w)/40:luma_power=3:chroma_radius=min(cw\,ch)/40:chroma_power=1[bg];[bg][0:v]overlay=(W-w)/2:(H-h)/2,setsar=1,crop=h=iw*3/4" out.mp4
  • moviepy ffmpeg stderr to tkinter interface

    1er avril 2018, par Alexander Perlman

    Hi stackoverflow community,

    I’m a novice python hobbyist. I wrote a python / ffmpeg script using moviepy that batch concatenates videos. I then designed an interface using tkinter.

    Now I want to redirect the stderr output from FFMPEG to the tkinter interface so that users can review the progress directly in app instead of needing the Sublime text console.

    I’ve done a lot of research but I’m in way over my head. Any tips would be greatly appreciated.

    Here’s the moviepy component. The gui is pretty cut and dry

    #import video clips
    mainvid = VideoFileClip(fullpath, audio=True)
    intro = VideoFileClip("intro.mp4", audio=True)
    black = VideoFileClip("black1s.mp4", audio=True)

    #concatenate video clips
    final = concatenate_videoclips([black, intro, mainvid, black]) final.fps=24

    #actually write file
    final.write_videofile(output, audio=True, audio_fps=48000, ffmpeg_params=[ "-r","24000/1001", "-b:v", "50M", "-level:v", "4.1", "-c:a", "libvo_aacenc", "-b:a", "256K", "-colorspace", "bt709"])