Recherche avancée

Médias (17)

Mot : - Tags -/wired

Autres articles (65)

  • 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 (...)

  • 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 (...)

  • 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 (9026)

  • FFmpeg av_read_frame not reading frames properly ?

    2 août 2016, par Sir DrinksCoffeeALot

    Alright, so I’ve downloaded some raw UHD sequences in .yuv format and encoded them with ffmpeg in .mp4 container (h264 4:4:4, 100% quality, 25fps). When i use ffprobe to find out how many frames are encoded i get 600, so that’s 24 secs of video.

    BUT, when i run those encoded video sequences through av_read_frame i only get like 40-50% of frames processed before av_read_frame returns error code -12. So I’m wild guessing that there are some data packages in middle of the streams which get read by av_read_frame and forces a function to return -12.

    What my questions are, how should i deal with this problem so i can encode full number of frames (600) ? When av_read_frame returns value different from 0 should i av_free_packet and proceed to read next frame ? Since av_read_frame returns values < 0 for error codes, which error code is used for EOF so i can insulate end of file code ?

  • FFmpeg av_read_frame not reading frames properly ?

    16 juin 2019, par Sir DrinksCoffeeALot

    Alright, so I’ve downloaded some raw UHD sequences in .yuv format and encoded them with ffmpeg in .mp4 container (h264 4:4:4, 100% quality, 25fps). When i use ffprobe to find out how many frames are encoded i get 600, so that’s 24 secs of video.

    BUT, when i run those encoded video sequences through av_read_frame i only get like 40-50% of frames processed before av_read_frame returns error code -12. So I’m wild guessing that there are some data packages in middle of the streams which get read by av_read_frame and forces a function to return -12.

    What my questions are, how should i deal with this problem so i can encode full number of frames (600) ? When av_read_frame returns value different from 0 should i av_free_packet and proceed to read next frame ? Since av_read_frame returns values < 0 for error codes, which error code is used for EOF so i can insulate end of file code ?

  • avcodec/movtextdec : Skip empty styles

    17 octobre 2020, par Andreas Rheinhardt
    avcodec/movtextdec : Skip empty styles
    

    They would either lead to unnecessary ASS tags being emitted (namely
    tags that are reset immediately thereafter) or would lead to problems
    when parsing : e.g. if a zero-length style immediately follows another
    style, the current code will end the preceding style and set the
    zero-length style as the next potentially active style, but it is only
    tested for activation when the next character is parsed at which point
    the current offset is already greater than both the starting as well
    as the end offset of the empty style. It will therefore neither be
    opened nor closed and all subsequent styles will be ignored.

    Reviewed-by : Philip Langdale <philipl@overt.org>
    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavcodec/movtextdec.c