Recherche avancée

Médias (91)

Autres articles (78)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

Sur d’autres sites (6578)

  • vframes option ignored in ffmpeg ?

    25 mars 2016, par cooper

    I have a directory that contains 2001 PNG files. I can convert all of the frames to an mp4 video using ffmpeg and the following command :

    ffmpeg -framerate 60 -start_number 0 \
    
-i pic.comp2.%07d.png -c:v libx264 -r 30 \
    
-pix_fmt yuv420p input1ia.mp4

    This works fine. However, I am creating a more complicated application that needs to read only the first 1020 files in the directory (specifically 0 thru 1019). Some googling around led me to the -vframes option. My problem is — it seems to get ignored or at least interpreted differently than I expect.

    My modified command looks like :

    ffmpeg -framerate 60 -start_number 0 \
    
-i pic.comp2.%07d.png -vframes 1020 -c:v libx264 
    
-r 30 -pix_fmt yuv420p input1.mp4

    It seems like many other people doing the same thing as me do not encounter this issue. So I did some more digging. I tried changing vframes from 1020 to -vframes 20, and this seemed to work properly. So now I am thinking it might be some kind of mismatch between -framerate and -r ?

    The full resultant video is 33 sec long... which makes sense mathematically.

     1 sec
    
 ---------   x  2001 frames = 33.35 seconds
    
 60 frames

    That’s why I thought that specifying 1/2 of the PNGs as the ’end point’ would result in a video of the first 16-17 seconds. But I always get the full length video from using the -vframes option.

    I assume my input to -vframes must be incorrect mathematically, since a small number of frames seems to work. However, I do not understand why.

    The most educated guess I can seem to make is that it is reading the PNGs as 60fps (-framerate), but the -r makes the output video 30fps or something ? However, then I would assume that the full output video would not be 33 seconds long.

  • vframes option ignored in ffmpeg ?

    25 mars 2016, par cooper

    I have a directory that contains 2001 PNG files. I can convert all of the frames to an mp4 video using ffmpeg and the following command :

    ffmpeg -framerate 60 -start_number 0 \
    
-i pic.comp2.%07d.png -c:v libx264 -r 30 \
    
-pix_fmt yuv420p input1ia.mp4

    This works fine. However, I am creating a more complicated application that needs to read only the first 1020 files in the directory (specifically 0 thru 1019). Some googling around led me to the -vframes option. My problem is — it seems to get ignored or at least interpreted differently than I expect.

    My modified command looks like :

    ffmpeg -framerate 60 -start_number 0 \
    
-i pic.comp2.%07d.png -vframes 1020 -c:v libx264 
    
-r 30 -pix_fmt yuv420p input1.mp4

    It seems like many other people doing the same thing as me do not encounter this issue. So I did some more digging. I tried changing vframes from 1020 to -vframes 20, and this seemed to work properly. So now I am thinking it might be some kind of mismatch between -framerate and -r ?

    The full resultant video is 33 sec long... which makes sense mathematically.

     1 sec
    
 ---------   x  2001 frames = 33.35 seconds
    
 60 frames

    That’s why I thought that specifying 1/2 of the PNGs as the ’end point’ would result in a video of the first 16-17 seconds. But I always get the full length video from using the -vframes option.

    I assume my input to -vframes must be incorrect mathematically, since a small number of frames seems to work. However, I do not understand why.

    The most educated guess I can seem to make is that it is reading the PNGs as 60fps (-framerate), but the -r makes the output video 30fps or something ? However, then I would assume that the full output video would not be 33 seconds long.

  • avutil/pixfmt : improve definition of AVColorRange

    18 septembre 2020, par Jan Ekström
    avutil/pixfmt : improve definition of AVColorRange

    As it was brought up that the current documentation leaves things
    
as specific to YCbCr only, ICtCp and RGB are now mentioned.
    
Additionally, the specifications on which these definitions of
    
narrow and full range are defined are mentioned.
    

    This way, the documentation of AVColorRange should now match how
    
most people seem to read interpret it at this point, and thus
    
flagging RGB AVFrames as full range is valid not only according to
    
common sense, but also the enum definition.
    • [DH] libavutil/pixfmt.h

Navigation