Recherche avancée

Médias (1)

Mot : - Tags -/bug

Autres articles (111)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

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

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

Sur d’autres sites (7453)

  • Where to inject code to print out motion vectors and DC coefficients inside ffmpeg lib

    12 juin 2018, par Kindermann

    For research purposes, I need to extract information about motion vectors and DC coefficients from an MPEG4 video.

    I have inserted many printf into virtually each function inside mpeg4videodec.c and recompiled the ffmpeg library then executed demuxing_decoding.c which is available at : http://ffmpeg.org/doxygen/trunk/demuxing_decoding_8c-example.html

    Surprisingly none of those printf I inserted was shown in the console. Can you give me some hints which file(s) in the ffmpeg library should I touch in order to print out MVectors and DC coefficients of a MPEG4 video file ?

  • Where to inject code to print out motion vectors and DC coefficients inside ffmpeg lib

    6 mai 2016, par Kindermann

    For research purposes, I need to extract information about motion vectors and DC coefficients from an MPEG4 video.

    I have inserted many printf into virtually each function inside mpeg4videodec.c and recompiled the ffmpeg library then executed demuxing_decoding.c which is available at : http://ffmpeg.org/doxygen/trunk/demuxing_decoding_8c-example.html

    Surprisingly none of those printf I inserted was shown in the console. Can you give me some hints which file(s) in the ffmpeg library should I touch in order to print out MVectors and DC coefficients of a MPEG4 video file ?

  • ffmpeg unexpected exit code 1 for -list_devices and -list_options

    8 janvier 2024, par djvg

    Description

    


    If I run any of the following commands from the examples in the documentation, using ffmpeg 4.2.2 on Windows 10, the requested information is successfully displayed in the console, but the process exits with exit code 1, instead of the expected 0 (success).

    


    ffmpeg -list_devices true -f dshow -i dummy

ffmpeg -list_options true -f dshow -i video="MyCamera"


    


    As far as I know, exit code 1 on Windows implies "Incorrect function", so I consider this behavior to be unexpected.

    


    If I stream camera input to disk, using e.g. ffmpeg -f dshow -i video="MyCamera" "myfile.mp4", then stop using q, the exit code is 0, as expected.

    


    Question

    


    Does the exit code 1 constitute normal behavior for ffmpeg, or am I doing something wrong ?

    


    Relevance

    


    When running the commands manually, from the command line, the exit code does not make much difference, as long as the requested information is displayed.

    


    However, when running the commands programmatically, it may cause trouble. For example, using Python's subprocess.run(..., check=True), the nonzero exit code causes a CalledProcessError.

    


    Of course there are ways around this, e.g. use check=False, but the point is that a workaround would not be necessary if ffmpeg behaved as expected, i.e. returned 0.