Recherche avancée

Médias (91)

Autres articles (54)

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

  • Librairies et binaires spécifiques au traitement vidéo et sonore

    31 janvier 2010, par

    Les logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
    Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
    Binaires complémentaires et facultatifs flvtool2 : (...)

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

Sur d’autres sites (11095)

  • Extract files from mpeg video

    28 octobre 2013, par A Dark Divided Gem

    Videos created with Camtasia can be shared on the web by exporting the project for the TechSmith Smart Player. The video is exported in the "H264 - MPEG-4 AVC (part10) (avc1)" codec and the export also includes other custom XML, JavaScript and SWF files used by the TechSmith Smart Player.

    These custom files are also "burnt" into the video itself. For example the contents of the XML file can be viewed when opening the MP4 video in a text editor. This allows other services to only ask for the MP4 file when uploading Camtasia videos.

    Therefore my question is how do you extract text and binary files from a MP4 video file ? For this project I am limited to Java but I am happy to call an external executable as well.

    I tried the "-dump_attachment" option in FFmpeg but that didn't work and I am out of ideas.

    C :\Users\Desktop>ffmpeg -dump_attachment:t "" -i getting-started-project.mp4
    ffmpeg version N-57448-gc78a416 Copyright (c) 2000-2013 the FFmpeg developers
      built on Oct 26 2013 18:08:54 with gcc 4.8.2 (GCC)
      configuration : —enable-gpl —enable-version3 —disable-w32threads —enable-av
    isynth —enable-bzlib —enable-fontconfig —enable-frei0r —enable-gnutls —enab
    le-iconv —enable-libass —enable-libbluray —enable-libcaca —enable-libfreetyp
    e —enable-libgsm —enable-libilbc —enable-libmodplug —enable-libmp3lame —ena
    ble-libopencore-amrnb —enable-libopencore-amrwb —enable-libopenjpeg —enable-l
    ibopus —enable-librtmp —enable-libschroedinger —enable-libsoxr —enable-libsp
    eex —enable-libtheora —enable-libtwolame —enable-libvidstab —enable-libvo-aa
    cenc —enable-libvo-amrwbenc —enable-libvorbis —enable-libvpx —enable-libwavp
    ack —enable-libx264 —enable-libxavs —enable-libxvid —enable-zlib
      libavutil      52. 47.101 / 52. 47.101
      libavcodec     55. 38.101 / 55. 38.101
      libavformat    55. 19.104 / 55. 19.104
      libavdevice    55.  5.100 / 55.  5.100
      libavfilter     3. 89.100 /  3. 89.100
      libswscale      2.  5.101 /  2.  5.101
      libswresample   0. 17.104 /  0. 17.104
      libpostproc    52.  3.100 / 52.  3.100
    Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'getting-started-project.mp4' :
      Metadata :
        major_brand : mp42
        minor_version : 0
        compatible_brands : isommp42
        creation_time : 2013-10-24 15:53:19
        artist :
        description :
        title : Untitled
      Duration : 00:05:41.12, start : 0.000000, bitrate : 314 kb/s
        Stream #0:0(eng) : Video : h264 (Baseline) (avc1 / 0x31637661), yuv420p(tv), 6
    40x360 [SAR 1:1 DAR 16:9], 185 kb/s, 30 fps, 30 tbr, 30k tbn, 60 tbc (default)
        Metadata :
          creation_time : 2013-10-24 15:53:19
          handler_name : Mainconcept MP4 Video Media Handler
        Stream #0:1(eng) : Audio : aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 12
    5 kb/s (default)
        Metadata :
          creation_time : 2013-10-24 15:53:19
          handler_name : Mainconcept MP4 Sound Media Handler
     At least one output file must be specified

    Update : It appears the XML is contained within a custom UUID atom and I just need a way of extracting that.

    Thanks

  • FFMpeg metadata issue

    12 février 2015, par TameHog

    whenever I run ffmpeg -i filename it returns something like this :

    Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    creation_time   : 2010-07-16 18:33:45
    Duration: 00:00:24.00, start: 0.000000, bitrate: 2443 kb/s
    Stream #0:0(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 127 kb/s
    Metadata:
     creation_time   : 2010-07-16 18:33:45
     handler_name    : Mainconcept MP4 Sound Media Handler
    Stream #0:1(eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 640x480 [SAR 1:1 DAR 4:3], 2311 kb/s, 30 fps, 30 tbr, 30k tbn, 60 tbc
    Metadata:
     creation_time   : 2010-07-16 18:33:46
     handler_name    : Mainconcept MP4 Video Media Handler

    Except when I run it from java using :

    ProcessBuilder pb = new ProcessBuilder(new String[]{"ffmpeg", "-i", "filename"});
       pb.redirectErrorStream(true);
       try{
           Process p = pb.start();

           BufferedReader br = new BufferedReader(new InputStreamReader(p.getInputStream()));
           String bs = "";
           while(br.readLine() != null){
               bs += br.readLine();
               bs += "\n";
           }
           return bs;
       }catch(IOException e){
           e.printStackTrace();
       }

    it gives me this :

         built on Jun 17 2013 23:20:06 with gcc 4.6 (GCC)
     Metadata:
       minor_version   : 0
       creation_time   : 2010-07-16 18:33:45
       Stream #0:0(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 127 kb/s
         creation_time   : 2010-07-16 18:33:45
       Stream #0:1(eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 640x480 [SAR 1:1 DAR     4:3], 2311 kb/s, 30 fps, 30 tbr, 30k tbn, 60 tbc
             creation_time   : 2010-07-16 18:33:46
       At least one output file must be specified

    How come when I run it from cmd I get way more data ? Can anybody tell me what I am doing wrong ?

  • Mingw-w64 - printf does not work

    27 décembre 2013, par Gosha U.

    First I wanted to modificate ffplay according to my requirments. Then I noticed that original ffplay from my build can't play some video files, but it didn't write any message to console. Then I noticed that ffmpeg also don't write any usage message when I run it without params. But it works. If I run it from terminal it's like running asynchronously ! The terminal just shows next row. I mean it asks for a next command. But the ffmpeg process is visible in task manager and it writes the output video file what I had requested !

    I created following souce file. I have modified the Makefile. So it have built the exe-file works just the same way. I have no idea how it can be.

    #include
    #include "cmdutils.h"

    const char program_name[] = "hello";
    const int program_birth_year = 2013;

    void show_help_default(const char *opt, const char *arg)
    {
       printf("zxcvbnm\n");
    }

    int main(int argc, char **argv)
    {
       printf("1234567890\n");
       return 0;
    }

    And after that I created real hello world app with MinGW-w64 and qmake without eny extra libs. And its printf does not work.

    I want to prevent this behavior.

    I want to make printf working in traditional manner.

    How I build FFmpeg :

    PKG_CONFIG_PATH=/home/developer/workspace/MinGW32fs/lib/pkgconfig/ \
    SDL_CONFIG=/home/developer/workspace/MinGW32fs/bin/sdl-config \
    ./configure \
     --prefix=/home/developer/workspace/MinGW32fs \
     --extra-ldflags="-L/home/developer/workspace/MinGW32fs/lib" \
     --extra-cflags="-I/home/developer/workspace/MinGW32fs/include" \
     --arch=x86 --target-os=mingw32 --cross-prefix=i686-w64-mingw32-  \
     --pkg-config=pkg-config   --enable-libtheora --enable-libvorbis --enable-libvpx \
     --enable-outdev=sdl --enable-shared --disable-static \
     --disable-doc --disable-manpages --disable-podpages

    make