Recherche avancée

Médias (0)

Mot : - Tags -/tags

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

Autres articles (27)

  • Librairies et logiciels spécifiques aux médias

    10 décembre 2010, par

    Pour un fonctionnement correct et optimal, plusieurs choses sont à prendre en considération.
    Il est important, après avoir installé apache2, mysql et php5, d’installer d’autres logiciels nécessaires dont les installations sont décrites dans les liens afférants. Un ensemble de librairies multimedias (x264, libtheora, libvpx) utilisées pour l’encodage et le décodage des vidéos et sons afin de supporter le plus grand nombre de fichiers possibles. Cf. : ce tutoriel ; FFMpeg avec le maximum de décodeurs et (...)

  • Other interesting software

    13 avril 2011, par

    We don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
    The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
    We don’t know them, we didn’t try them, but you can take a peek.
    Videopress
    Website : http://videopress.com/
    License : GNU/GPL v2
    Source code : (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

Sur d’autres sites (3410)

  • Why ffmpeg print SAR instead of PAR ?

    10 juillet 2016, par Jofsey

    If my knowledge is correct, SAR (Storage Aspect Ratio) is the ratio of pixel dimensions.
    For example, a 640 × 480 video has a SAR of 640/480 = 4:3.

    Whereas PAR (Pixel Aspect Ratio) is ratio of pixel height and width, and most of modern videos have square PAR (1:1).

    But when I tried to check it with ffmpeg -i I got square SAR instead of square PAR for all test videos.

    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 1758 kb/s, 24.99 fps, 25 tbr, 25 tbn, 50 tbc
    Stream #0:0(und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 540x360  [SAR 1:1 DAR 3:2], 386 kb/s, 25 fps, 25 tbr, 25 tbn, 50 tbc
    Stream #0:0(und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p,  450x360 [SAR 1:1 DAR 5:4], 328 kb/s, 25 fps, 25 tbr, 25 tbn, 50 tbc

    Is it ffmpeg bug or my mistake ?

  • Merge commit ’5372cda67109848d22146289e401669266217e80’

    19 septembre 2013, par Michael Niedermayer
    Merge commit ’5372cda67109848d22146289e401669266217e80’
    

    * commit ’5372cda67109848d22146289e401669266217e80’ :
    rv10 : Validate the dimensions set from the container

    This check could be replaced by a width==0||height==0

    Merged-by : Michael Niedermayer <michaelni@gmx.at>

    • [DH] libavcodec/rv10.c
  • How to find the actual size occupied by an AVFrame ?

    23 septembre 2013, par jsp99

    The main task at hand is to find the actual size of a decoded AVFrame.

    Here is some background information about the problem -
    I wrote a program which takes as input a media file and displays all the video frames of the file, on the screen. My Code (written in C using SDL and ffmpeg) worked perfectly with .wmv files. When it came to .mkv files, it failed (SIGSEGV) due to the following reason :

    Example : Suppose I have a decoded frame from my video stream of file (filename.mkv) in AVFrame *pFrame. The frame has a pix_fmt (pFrame->pix_fmt) of yuv420p. It has dimensions 640 * 346. The Y-plane has it's linesize (pFrame->linesize[0]) as 672.

    I think you get the point here. When I use avpicture_get_size() to get the size of the frame, it calculates a wrong size. It takes pix_fmt, width and height as arguments. Nowhere does it consider 672 instead of 640.

    avpicture_get_size() : Calculates the size in bytes that a picture of the given width and height would occupy if stored in the given picture format.

    I got around this problem by adding some yuv420p frame specific code, which can find the size of the frame in situations like above.

    • Can someone explain why are most of the decoded frames (from video streams of most of the formats) this way ? And why is it not this way with the wmv format ?

    But if I have to find the actual size occupied by an AVFrame of another format (Eg: yuv410p), I have to write the format specific code again. Coming to the main problem,

    • How can I find the actual size occupied the decoded AVFrame (size in bytes occupied by the data of the AVFrame) ?

    • I tried using av_image_get_buffer_size(), but I couldn't understand how to use the align parameter. Can someone explain the usage of the parameter align ? Tried using many other functions in pixdesc.c, but I am missing something.