Recherche avancée

Médias (3)

Mot : - Tags -/image

Autres articles (20)

  • Personnaliser les catégories

    21 juin 2013, par

    Formulaire de création d’une catégorie
    Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
    Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire.
    Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
    Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

Sur d’autres sites (4304)

  • Is there a way to run a ffmpeg command based on the videos resolution ?

    15 avril 2022, par William Lee

    As an example, if a video has a maximum resolution of 480p, DO NOT convert it to 1080p, just convert it from 144p to 480p.

    


    Is there any way that this is possible ?

    


  • FFprobe reading incorrect resolution value despite players rendering it correctly

    24 juillet 2015, par Boehmi

    I’m creating a video from a stream with the help of FFMPEG and I also use FFPROBE to gather information for use on a status page like resolution, codecs et cetera.

    When FFProbe parses my video for information, I get a resolution value of 544x576 (almost a square !), but an aspect ratio of 16:9.

    These values are consistent on both the input stream and my saved video.

    When I watch the video in the standard HTML5 Player, VLC or FFPLAY however, I get a video with the proportions of 16:9 and a resolution (measured using an image editing program) of 1024x576 that does look native and not stretched in any way.

    Even if I re-encode the video using slightly different codecs, this incorrect resolution value persists, even though every player I use displays it correctly.

    This is slightly inconvenient because I am relying on getting the correct resolution value from the video for further processing.

    I’m also using a recent FFMPEG+FFPROBE version that was compiled on the 15th of July.

    Is this a bug within FFMPEG or is there anything I’m doing wrong ?

    Used command lines :

    FFMPEG :

    ffmpeg -i source -loglevel debug -vcodec copy -acodec copy -bsf:a aac_adtstoasc -movflags +faststart -t 360 -y video.mp4

    FFPROBE (I parse the output of this directly and save the values) :

    ffprobe -i source -show_format -show_streams

    FFProbe output :

    width=544
    height=576
    coded_width=544
    coded_height=576
    has_b_frames=2
    sample_aspect_ratio=32:17
    display_aspect_ratio=16:9

    I can see that the sample aspect ratio is different from the display aspect ratio, but how come the video looks proper in 16:9 when it’s supposedly encoded at a near square resolution ?

  • parseutil : Add more resolution aliases

    17 juillet 2015, par Luca Barbato
    parseutil : Add more resolution aliases
    

    Add DCI 2k and 4k and uhd1 and uhd2.

    • [DH] doc/avconv.texi
    • [DH] libavutil/parseutils.c