Recherche avancée

Médias (0)

Mot : - Tags -/presse-papier

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

Autres articles (100)

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

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

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (9343)

  • converting with the same quality

    26 mai 2019, par Sherkhan Azimov

    ffmpeg -i cam2.DAT -qscale:v cam2.avi
    When run, this returns "At least one output file must be specified", what am I missing ?
    Probably, there is another method to convert with the same quality ?

  • avfilter/vf_paletteuse : Fix leaks of AVFilterFormats on error

    7 août 2020, par Andreas Rheinhardt
    avfilter/vf_paletteuse : Fix leaks of AVFilterFormats on error

    The paletteuse's query_formats function allocated three AVFilterFormats
    
before storing them permanently. If allocating one of them failed, the
    
three AVFilterFormats structures would be freed with av_freep() which
    
does not free separately allocated subelements (namely the formats
    
array) which leak.
    

    Furthermore, if storing one of the first two fails, the function simply
    
returns and the ones not yet stored leak.
    

    These leaks have been fixed by only creating a new AVFilterFormats after
    
the last one has already been permanently stored. Furthermore, it is
    
enough to check whether the elements have been properly stored as
    
ff_formats_ref() by design returns AVERROR(ENOMEM) if it is provided a
    
NULL AVFilterFormats *.
    

    Fixes Coverity issues #1270818 and #1270819.
    

    Reviewed-by : Nicolas George <george@nsup.org>
    
Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
    • [DH] libavfilter/vf_paletteuse.c

  • How to extract frame types along with motion vectors using extract_mvs.c from ffmpeg

    26 février 2018, par helmo

    I have been researching ways to get frame types (I, P, B) along with the motion vector data returned from extract_mvs.c in the examples folder in ffmpeg.

    The extract_mvs.c file after it is compiled, returns information like this :

    framenum,source,blockw,blockh,srcx,srcy,dstx,dsty,flags
    
2,-1,16,16,   8,   8,   8,   8,0x0
    
2, 1,16,16,   8,   8,   8,   8,0x0
    
2, 1,16,16,  24,   8,  24,   8,0x0
    
2, 1,16,16,  40,   8,  40,   8,0x0
    
2, 1,16,16,  56,   8,  56,   8,0x0
    
2, 1,16,16,  72,   8,  72,   8,0x0
    
2, 1,16,16,  88,   8,  88,   8,0x0
    
...
    
297, 1,16,16, 248, 280, 248, 280,0x0
    
297, 1,16,16, 264, 280, 264, 280,0x0
    
297,-1,16,16, 278, 279, 280, 280,0x0
    
297, 1,16,16, 280, 280, 280, 280,0x0
    
297, 1,16,16, 296, 280, 296, 280,0x0
    
297, 1,16,16, 312, 280, 312, 280,0x0
    
297, 1,16,16, 328, 280, 328, 280,0x0
    
297, 1,16,16, 344, 280, 344, 280,0x0

    Along with this information, I would like to output frame type so that I know framenum = 2 is, for example, a ’B’ frame.

    I tried different things, one of which was using a separate command :

    ffprobe input.mp4 -show_frames | grep -E 'pict_type|coded_picture_number'

    But the problem with this command is that it returns data like :

    pict_type=I
    
coded_picture_number=0
    
pict_type=B
    
coded_picture_number=2
    
pict_type=P
    
coded_picture_number=1
    
pict_type=B
    
coded_picture_number=4
    
pict_type=P
    
coded_picture_number=3
    
....
    
pict_type=P
    
coded_picture_number=293
    
pict_type=B
    
coded_picture_number=297
    
pict_type=B
    
coded_picture_number=296

    And there is no much I can relate here between coded_picture_number and framenum. The former starts counting from 0 and the later from 2. I assume framenum starting from 2, means the count from this variable is actually from 1, and it ignored 1 in the extraction process as it is maybe an I frame thus no motion vectors.

    So, how can we use only extract_mvs.c to get not only that information it provides but also the frame types in the returned table. Any hints either syntax/command-wise or in editing the c file would be appreciated. Thanks in advance.

Navigation