Recherche avancée

Médias (91)

Autres articles (33)

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

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

Sur d’autres sites (9344)

  • rtsp : Use AVERROR() with errno.h error codes for error returns

    11 décembre 2019, par Martin Storsjö
    rtsp : Use AVERROR() with errno.h error codes for error returns

    This particular function is only required to return nonzero on
    
errors, but use the common AVERROR() pattern for consistency.
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DH] libavformat/rtsp.c

  • FFMPEG avformat_open_input returns unpopulated Format context

    21 avril 2013, par Michael IV

    I am trying to load avi and flv files programatically with FFMPEG API.The files seem to get loaded because avformat_open_input doesn't return 0 .But when inspecting AVFormatContext variable for every property in the inspector I am getting just "Unable to read memory" .Here is how I do it :

                av_register_all();
    
    avcodec_register_all();
    
    AVFormatContext *pFormatCtx=avformat_alloc_context();
    

    

    
    if(avformat_open_input(&amp;pFormatCtx,"assest/comp1.avi",NULL,NULL) !=0)
    
    {
    

    
        printf("%s","Movie load Success");
    
    }else{
    

    

    
        printf("%s","Movie load Fail");
    
    }  

    I am using VisualStudio 2010 C++ compiler .Windows 7.

    UPDATE :

    Ok ,Please discard this question.I found the error.It was a stupid typo in the file directory path.

  • Popen.communicate() returns only err when running ffmpeg

    17 février 2013, par Jan Pulpan

    I'm trying to run ffmpeg from python and get some reasonable output. Doesn't matter what ffmpeg's log level is set, the only output I get from Popen.communicate() is err one. The content isn't an error however. I tried the same code to run other commands (ls) and it seems to be Ok with both out and err outputs.

    I checked here and Google and unfortunately found nothing. Most of the examples use os or commands modules, not subprocess.

    This is my test code :

    command = [
    
        &#39;ffmpeg&#39;,
    
        &#39;-v&#39;, &#39;debug&#39;,
    
        &#39;-i&#39;, &#39;1.mov&#39;,
    
        &#39;-vcodec&#39;, &#39;libx264&#39;,
    
        &#39;-profile:v&#39;, &#39;high&#39;,
    
        &#39;-preset&#39;, &#39;slower&#39;,
    
        &#39;-b:v&#39;, &#39;1000k&#39;,
    
        &#39;-vf&#39;, &#39;scale=-1:720&#39;,
    
        &#39;-threads&#39;, &#39;0&#39;, 
    
        &#39;-acodec&#39;, &#39;libfdk_aac&#39;,
    
        &#39;-b:a&#39;, &#39;192k&#39;,
    
        &#39;-y&#39;,   
    
        &#39;2.mp4&#39;,
    
        ]
    
p = subprocess.Popen(command, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
    
out, err =  p.communicate()
    
f = open(&#39;out.log&#39;, &#39;w&#39;)
    
f.write(out)
    
f.close()
    
f = open(&#39;error.log&#39;, &#39;w&#39;)
    
f.write(err)
    
f.close()

    Have you ever see something like this ? Am I doing any mistakes or is there an bug in ffmpeg ?

Navigation