Recherche avancée

Médias (17)

Mot : - Tags -/wired

Autres articles (97)

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

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

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

  • 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 ?