Recherche avancée

Médias (0)

Mot : - Tags -/images

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

Autres articles (21)

  • MediaSPIP Core : La Configuration

    9 novembre 2010, par

    MediaSPIP Core fournit par défaut trois pages différentes de configuration (ces pages utilisent le plugin de configuration CFG pour fonctionner) : une page spécifique à la configuration générale du squelettes ; une page spécifique à la configuration de la page d’accueil du site ; une page spécifique à la configuration des secteurs ;
    Il fournit également une page supplémentaire qui n’apparait que lorsque certains plugins sont activés permettant de contrôler l’affichage et les fonctionnalités spécifiques (...)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • Emballe médias : à quoi cela sert ?

    4 février 2011, par

    Ce plugin vise à gérer des sites de mise en ligne de documents de tous types.
    Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ;

Sur d’autres sites (2866)

  • how to debug a corrupted video file with ffmpeg ?

    12 janvier 2018, par Blurry Script

    for example I downloaded some film, it is somehow encoded with some program, when I try to use ffmpeg to convert it, let’s say from mkv to mp4, i get an error that :

    [matroska,webm @ 0x1d06640] Read error at pos. 2241497 (0x2233d9)

    now how can I know where is the reason that this happens ? should just avoid this kind of files, or somehow debug it and see what is the reason behind this error ? or maybe skip this error frames, but i dont know how many frames may be like this, what if most of the file is filled with corrupted frames, altough it is playable in the video player

  • FFmpeg : Interpolation for Fade-In

    6 juillet 2017, par Sir Bad News

    I’m currently using the following to fade-in a short film.

    ffmpeg -i input.mp4 -filter:v fade=in:0:360 -c:v libx264 -preset:v slower -crf:v 24 -pix_fmt yuv420p output.mp4

    Everything works as expected ; however, the interpolation of the fade is not what I’m after (seems to be linear). I’d like to play around with exponential, cubic, sinusoidal, etc.

    Is there any way to achieve this with FFmpeg ? The visual material I’m working with is pure white and pure black, and the fade-in as it stands is too harsh ; I can see the material appear almost as soon as the fade starts as a result of the (apparently) linear progression. I’d like it to be more organic.

    Any help greatly appreciated.

  • fftools/ffmpeg : propagate frame durations to packets when encoding

    14 avril 2023, par Anton Khirnov
    fftools/ffmpeg : propagate frame durations to packets when encoding

    Remove now-obsolete code setting packet durations pre-muxing for CFR
    
encoded video.
    

    Changes output in the following FATE tests :
    
* numerous adpcm tests
    
* ffmpeg-filter_complex_audio
    
* lavf-asf
    
* lavf-mkv
    
* lavf-mkv_attachment
    
* matroska-encoding-delay
    
  All of these change due to the fact that the output duration is now
    
  the actual input data duration and does not include padding added by
    
  the encoder.
    

    * apng-osample : less wrong packet durations are now passed to the muxer.
    
  They are not entirely correct, because the first frame duration should
    
  be 3 rather than 2. This is caused by the vsync code and should be
    
  addressed later, but this change is a step in the right direction.
    
* tscc2-mov : last output frame has a duration of 11 rather than 1 - this
    
  corresponds to the duration actually returned by the demuxer.
    
* film-cvid : video frame durations are now 2 rather than 1 - this
    
  corresponds to durations actually returned by the demuxer and matches
    
  the timestamps.
    
* mpeg2-ticket6677 : durations of some video frames are now 2 rather than
    
  1 - this matches the timestamps.
    • [DH] fftools/ffmpeg_enc.c
    • [DH] fftools/ffmpeg_mux.c
    • [DH] tests/ref/acodec/adpcm-ima_wav
    • [DH] tests/ref/acodec/adpcm-ima_wav-trellis
    • [DH] tests/ref/acodec/adpcm-ms
    • [DH] tests/ref/acodec/adpcm-ms-trellis
    • [DH] tests/ref/acodec/adpcm-swf
    • [DH] tests/ref/acodec/adpcm-swf-trellis
    • [DH] tests/ref/acodec/adpcm-swf-wav
    • [DH] tests/ref/acodec/adpcm-yamaha
    • [DH] tests/ref/acodec/adpcm-yamaha-trellis
    • [DH] tests/ref/fate/apng-osample
    • [DH] tests/ref/fate/autorotate
    • [DH] tests/ref/fate/ffmpeg-filter_complex_audio
    • [DH] tests/ref/fate/film-cvid
    • [DH] tests/ref/fate/matroska-encoding-delay
    • [DH] tests/ref/fate/mpeg2-ticket6677
    • [DH] tests/ref/fate/tscc2-mov
    • [DH] tests/ref/lavf/asf
    • [DH] tests/ref/lavf/mkv
    • [DH] tests/ref/lavf/mkv_attachment

Navigation