Recherche avancée

Médias (1)

Mot : - Tags -/Christian Nold

Autres articles (98)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

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

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

Sur d’autres sites (10854)

  • yasm is installed in my system but in some other folder

    22 octobre 2014, par janpal

    I am trying to install ffmpeg and x264. For this to install I have followed the instructions given in "https://ffmpeg.org/trac/ffmpeg/wiki/UbuntuCompilationGuide". I have installed yasm and checked by using the command yasm —version it showing the successfully installed version. But when I try to install ffmpeg its throwing an error like yasm not found. I have referred some sites its intend me to check the path. yasm default path is /usr/local/bin but in my system its showing as /home/janpal/bin/yasm. I tried it as a root user also. Can somebody help me to install this in the correct path. I am using ubuntu 10.04

  • Node Video Transcoder - File System [closed]

    12 avril 2021, par mike varela

    I'm building a node video transcode system using fluent-ffmpeg and express. I'm investigating RabbitMQ as well but in the meantime I'm trying to find out if I'm able to transcode on the LAN without having to upload a file. Basically, this express server will sit internally in our company. Users will hit this via internal IP and a browser. Ideally they could click a button to select a video and then open a path browser to choose the location of the processed file and hit go. In this scenario, they wouldn't need to upload the video to the server for processing and then download the processed version.

    


    I'm wondering if this is possible ?

    


  • New FATE Test Coverage System

    10 août 2010, par Multimedia Mike — FATE Server

    I’ve been feeling a bit scattered for the last week since I was fired from my volunteer position as the FFmpeg QA manager, wondering if there is anything I should attempt to do with the project. It can’t be denied that the new system is working well. But one area I’ve wondered about is test coverage.

    Under my old regime I tracked test coverage as a wiki page which was a highly flawed method— tedious and error-prone. There are those 2 adjectives again— tedious and error-prone ; whenever I see those, I search for automation methods. I think that might be more plausible thanks to the new FATE’s tighter integration with the FFmpeg build system.

    I don’t think anyone is working on this problem so I wanted to toss out a brainstorm :

    1. First, run ’ffmpeg -formats’, ’ffmpeg -codecs’, etc. and parse the output to collect a list of all the features (full list : -formats, -codecs, -bsfs, -protocols, -filters, -pix_fmts). Transform these lists into a standardized list of features, e.g., "DEVSD  ffvhuff         Huffyuv FFmpeg variant" represents features ’decode-video-ffvhuff’, ’encode-video-ffvhuff’, ’ffvhuff-horizband’, and ’ffvhuff-dr1’.
    2. Next, tag each individual test spec with the features that it exercises. E.g., test ’fate-vqa-cc’ exercises features ’demux-wsvqa’, ’decode-video-vqavideo’, and ’decode-audio-adpcm_ima_ws’.
    3. Finally, compare the data from parts 1 and 2. Print a list of all the features that are not exercised in FATE.

    I think a lot of this could be implemented at the GNU make level. Then again, I’m no expert on GNU make syntax so I may be overestimating its capabilities. Or there might be simpler ways to automatically track test coverage stats based on the improved testing infrastructure.

Navigation