Recherche avancée

Médias (91)

Autres articles (39)

  • 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

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

Sur d’autres sites (6262)

  • libswcale : Fix possible string overflow in test.

    12 mai 2019, par Adam Richter
    libswcale : Fix possible string overflow in test.

    In libswcale/tests/swcale.c, the function fileTest() calls sscanf in
    
an argument of "%12s" on character srcStr[] and dstStr[], which are
    
only 12 bytes.  So, if the input string is 12 characters, a
    
terminating null byte can be written past the end of these arrays.
    

    This bug was found by cppcheck.
    

    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libswscale/tests/swscale.c

  • avisynth : Make sure the filename passed to Avisynth is in the right code page

    21 juin 2013, par Oka Motofumi
    avisynth : Make sure the filename passed to Avisynth is in the right code page

    Avisynth is a non-unicode application and cannot accept UTF-8
    
characters. Therefore, the input filename should be converted to
    
the code page that it expects.
    

    Signed-off-by : Derek Buitenhuis <derek.buitenhuis@gmail.com>
    • [DH] libavformat/avisynth.c

  • FFmpeg pass arguments in a text file

    30 novembre 2023, par yazanpro

    I'm trying to get around the 32767 characters limit regarding the command line length in Windows (sometimes it's less than that). I have a large number of boxes that I'm trying to draw on a video. Typically I can concatenate the draw commands using a comma (,) like so (the following command draws two boxes) :

    &#xA;&#xA;

    ffmpeg -i input.mp4 -vf "drawbox=enable=&#x27;between(t, 1.5, 4)&#x27; : x=100 : y=100 : w=200 : h=200 : color=green,drawbox=enable=&#x27;between(t, 9, 18)&#x27; : x=500 : y=10 : w=150 : h=150 : color=red" -codec:a copy output.mp4&#xA;

    &#xA;&#xA;

    However since I have many boxes to draw, the length of the entire command becomes too large.

    &#xA;&#xA;

    Does FFmpeg offer a way to pass all arguments in a text file instead of literal text ? Something like this :

    &#xA;&#xA;

    ffmpeg content(ffmpegCmd.txt)&#xA;

    &#xA;&#xA;

    If that's not possible, is it possible to "buffer" the arguments into separate commands while exporting the result only in the last command ?

    &#xA;

Navigation