Recherche avancée

Médias (0)

Mot : - Tags -/metadatas

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (9)

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

  • Gestion générale des documents

    13 mai 2011, par

    MédiaSPIP ne modifie jamais le document original mis en ligne.
    Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
    Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...)

  • Les vidéos

    21 avril 2011, par

    Comme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
    Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
    Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...)

Sur d’autres sites (5286)

  • Use ffmpeg to segment streaming video

    7 juin 2016, par Marc

    Suppose I have a streaming video URL rtsp ://whatever and I wish to store that video stream to my file system as a series of files off approximately the same size or duration. Ideally I would like to store the files with a start and stop timestamp as part of the filename, and each file should be such that it can stand on its own to be displayed as a video file if someone wants to view it. I understand that ffmpeg has a segment command option that allows me to segment by time and store in a series of files like outfile%3d.dat or whatever. But suppose I want to do this perpetually and cycle the files (age out old ones) when the total size of all the saved files exceeds a specific value. For example, suppose I want to save the most recent 500GB of video from this streaming URL and keep doing this day after day continuously into the distant future. What happens to the output filename after outfile999.dat is saved ? Does the count start over at 0 ? Or does ffmpeg just stop or crash ? Is there an ffmpeg command that can segment and age out old files, or is this something I would have to do running another program simultaneously or would I have to hack into ffmpeg itself to do this ? I’m pretty new to ffmpeg so any suggestions you ffmpeg experts might have on how to do this would be welcome. I also welcome suggestions for other command line Linux tools that might be better for this application.

    UPDATE : So it turns out that ffmpeg has a segmenter built in, and I can segment the files such that the filenames have the video start datetime as part of the filename. I used a command like this :

    ffmpeg -i rtsp://camera_feed_url_here -c copy -f segment -segment_list out.list -segment_time 900 \ -segment_atclocktime 1 -strftime 1 "%Y-%m-%d_%H-%M-%S.mkv"

    That’s the good news. The bad news is that when I run this command, after about 1 minute it just throws this error and stops :

    rtsp ://camera_feed_url_here : Invalid data found when processing input

    No other error or diagnostic mesages are printed out. Even when I run with -loglevel debug, it just seems to die with this error message.

    When I built ffmpeg, used this :

    ./configure --enable-demux='rtsp,rtp,sdp,flac,gif,image2,image2pipe,matrosk' --enable-network --enable-protocols --enable-decoder=h264

    Any ideas what I’m doing wrong and how I can make this error go away ?

  • Use ffmpeg to segment streaming video

    4 décembre 2022, par Marc

    Suppose I have a streaming video URL rtsp ://whatever and I wish to store that video stream to my file system as a series of files off approximately the same size or duration. Ideally I would like to store the files with a start and stop timestamp as part of the filename, and each file should be such that it can stand on its own to be displayed as a video file if someone wants to view it. I understand that ffmpeg has a segment command option that allows me to segment by time and store in a series of files like outfile%3d.dat or whatever. But suppose I want to do this perpetually and cycle the files (age out old ones) when the total size of all the saved files exceeds a specific value. For example, suppose I want to save the most recent 500GB of video from this streaming URL and keep doing this day after day continuously into the distant future. What happens to the output filename after outfile999.dat is saved ? Does the count start over at 0 ? Or does ffmpeg just stop or crash ? Is there an ffmpeg command that can segment and age out old files, or is this something I would have to do running another program simultaneously or would I have to hack into ffmpeg itself to do this ? I'm pretty new to ffmpeg so any suggestions you ffmpeg experts might have on how to do this would be welcome. I also welcome suggestions for other command line Linux tools that might be better for this application.

    



    UPDATE : So it turns out that ffmpeg has a segmenter built in, and I can segment the files such that the filenames have the video start datetime as part of the filename. I used a command like this :

    



    ffmpeg -i rtsp://camera_feed_url_here -c copy -f segment -segment_list out.list -segment_time 900 \ -segment_atclocktime 1 -strftime 1 "%Y-%m-%d_%H-%M-%S.mkv"


    



    That's the good news. The bad news is that when I run this command, after about 1 minute it just throws this error and stops :

    



    rtsp ://camera_feed_url_here : Invalid data found when processing input

    



    No other error or diagnostic mesages are printed out. Even when I run with -loglevel debug, it just seems to die with this error message.

    



    When I built ffmpeg, used this :

    



    ./configure --enable-demux='rtsp,rtp,sdp,flac,gif,image2,image2pipe,matrosk' --enable-network --enable-protocols --enable-decoder=h264


    



    Any ideas what I'm doing wrong and how I can make this error go away ?

    


  • Compiling FFmpeg staticly using NDK error - Not position independent executables executable

    27 février 2017, par David Barishev

    I have been trying to compile ffmpeg into a static library in order to use it in my android application, but i couldn’t get it to work.

    Im working with FFmpeg 3.2.4, and ndk r13b, using bash on windows 10(Ubuntu 14.04).

    Here is what i did :

    • I made a stand alone toolchain for x86_64 and api 21 using :
      python make_standalone_toolchain.py --api 21 --arch x86_64 --install-dir {}

    • Made a configuration script :

      ./configure \
      --target-os=android                                     \
      --arch=x86_64                                              \
      --prefix=/home/david/ffmpeg_x86_64_build                          \
      --cross-prefix=/home/david/x86_64_toolchain/bin/x86_64-linux-android-\
      --sysroot=/home/david/x86_64_toolchain/sysroot                    \
      --enable-cross-compile                                  \
      --pkg-config-flags="--static"                           \
      --enable-ffmpeg                                         \
      --disable-ffplay                                        \
      --disable-ffprobe                                       \
      --disable-ffserver                                      \
      --disable-doc                                           \
      --disable-htmlpages                                     \
      --disable-manpages                                      \
      --disable-podpages                                      \
      --disable-txtpages                                      \
      --extra-cflags="-fPIC"                                  \
      --extra-cxxflags="-fPIC"
      --disable-shared --enable-static \
      --enable-yasm

      make
      make install

    It produced an FFmpeg executable, however when i ran it on my API 23 emulator, i got an error message :error: only position independent executables (PIE) are supported.
    Even that i used -fPic

    How can i fix it ? Also i’m not sure about my configuration, there wasn’t up to date sources on how to compile it correctly for every ABI (arm,arm64,x86,x86_64,mips,mips64) that i need for my application.
    I have seen many script, and im not too familiar with compiling native code, so i wasn’t sure what settings i need, for example like C flags and etc.

    To be precise on how i tried to configure FFmpeg :

    • I need a static library
    • I Only need the ffmpeg command line utility
    • I want to compile the library for every ABI i listed above.This configuration tried to compile for x86_64.
    • Running on android of course

    I would greatly appreciate some help on how to configure and compile this correctly.