Recherche avancée

Médias (91)

Autres articles (45)

  • Personnaliser les catégories

    21 juin 2013, par

    Formulaire de création d’une catégorie
    Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
    Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire.
    Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
    Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)

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

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

  • AWS Lambda function execution for video

    11 avril, par Abinaya

    I am trying to run my application as Lambda, I am not getting successful eexecution everytime. Its like inconsistent results over testing.

    


    The application uses files from S3 bucket as input, once I have tried to execute Lambda with input being a simple 2 sec long mp4 video using FFMPEG in my application for processing. Lambda executed for 4 or 5 times (not everytime). I was able to see the FFMPEG commands and logs on AWS Log output screen.
he cloudwatch logs on the last execution of this :

    


    ffmpeg version 4.4.2-0ubuntu0.22.04.1 Copyright (c) 2000-2021 the FFmpeg developers

built with gcc 11 (Ubuntu 11.2.0-19ubuntu1)

configuration: --prefix=/usr --extra-version=0ubuntu0.22.04.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared

libavutil 56. 70.100 / 56. 70.100

libavcodec 58.134.100 / 58.134.100

libavformat 58. 76.100 / 58. 76.100

libavdevice 58. 13.100 / 58. 13.100

libavfilter 7.110.100 / 7.110.100

libswscale 5. 9.100 / 5. 9.100

libswresample 3. 9.100 / 3. 9.100

libpostproc 55. 9.100 / 55. 9.100

END RequestId: a7e397a7-ef1b-44c5-9877-e60a55665fc8

REPORT RequestId: a7e397a7-ef1b-44c5-9877-e60a55665fc8 Duration: 255111.29 ms Billed Duration: 255000 ms Memory Size: 1024 MB Max Memory Used: 177 MB 


    


    In short, I have created a console application that uses a model (let's say onnx model). This model is utilized in such a way that when my application is started, input is downloaded from s3, once any objects are detected in the input video I am trying to convert that into rendered output video with the use of FFMPEG

    


    Generated output was also uploaded to S3 bucket in .flv format. Sometimes the Output is 0KB .Since then I haven't encountered successful execution for my video case though nothing have been modified in my image that is using to execute the Lambda. What would be the reason for such inconsistent action throughout my testing ?

    


    I am expecting to have a successful output again, consistently. I have run the same application on ubuntu environment inside docker container, it generated output video and uploaded to S3, working as expected. The same docker image was pushed to ECR and I get no output. Is Lambda not compatible for FFMPEG usage ?
I have been struggling with this issue for days, Any help would be appreciated.

    


  • Can VLC's method for estimating the duration of a video be reproduced by the means of ffmpeg ?

    28 février, par archie

    This may seem to duplicate previous questions but it does not, as far as I can tell.

    


    I have a bash script for indexing images and videos to a thumbnails database. A user of my script complained that some videos of hers are skipped over with an error message "corrupted metadata" even though VLC can play them smoothly. These are about 10 videos out of some 15 thousand, but I'd like to solve the problem.

    


    I will focus on a single video from the bunch. File name : "Paper_and_discussion_M492.mkv", actual duration 02:03:47 (hh:mm:ss). The duration and bitrate fields in the video metadata are missing.

    


    ffmpeg  -hide_banner -i "Paper_and_discussion_M492.mkv" 2> ffmpeg_data.txt


    


    gives the following output :

    


      Input #0, matroska,webm, from 'Paper_and_discussion_M492.mkv':
  Metadata:
    COMPATIBLE_BRANDS: isomiso2avc1mp41
    MAJOR_BRAND     : isom
    MINOR_VERSION   : 512
    ENCODER         : Lavf58.76.100
  Duration: N/A, start: 0.000000, bitrate: N/A
  Stream #0:0: Video: hevc (Main), yuv420p(tv, progressive), 854x480 [SAR 1280:1281 DAR 16:9], 24 fps, 24 tbr, 1k tbn, 24 tbc (default)
    Metadata:
      HANDLER_NAME    : VideoHandler
      VENDOR_ID       : [0][0][0][0]
      ENCODER         : Lavc58.134.100 libx265
  Stream #0:1: Audio: vorbis, 44100 Hz, stereo, fltp (default)
    Metadata:
      HANDLER_NAME    : SoundHandler
      VENDOR_ID       : [0][0][0][0]
      ENCODER         : Lavc58.134.100 libvorbis
At least one output file must be specified


    


    Therefore, as expected,

    


    ffprobe -i <file> -show_entries format=duration -v quiet -of csv="p=0"&#xA;</file>

    &#xA;

    returns "N/A".

    &#xA;

    Decoding the whole file does work :

    &#xA;

    ffprobe -show_entries stream=r_frame_rate,nb_read_frames -select_streams v -count_frames -of compact=p=0:nk=1 -v 0 "Paper_and_discussion_M492.mkv"&#xA;

    &#xA;

    but it obviously takes a lot of time, especially for a > 2 hours video.

    &#xA;

    The "faster answer" proposed by LSerni in https://superuser.com/questions/1179000/ffmpeg-get-duration-of-video-file-without-meta-data should give an estimate of duration based on bitrate ; but bitrate is also "N/A" in the incriminated file(s). Their command-line solution based on ffmpeg ends with an error "division by zero".

    &#xA;

    However, if I open the file with VLC, it plays ok and VLC immediately shows the duration of the file as 02:03:47. I have checked that duration is precise. Search and jump are also very fast : if I skip 1 hr, playback promptly resumes at the right time.

    &#xA;

    So, a doubt is gnawing at me : How does VLC succeed where I consistently fail ? It must have a way for recovering data that I might also be able to use to produce a correct estimate of duration.

    &#xA;

    My question is : is it possible to reproduce VLC's method (or equivalent) by means of ffmpeg ?

    &#xA;

  • avformat/flacdec : Return correct error-codes on read-failure

    26 janvier 2023, par Ulrik
    avformat/flacdec : Return correct error-codes on read-failure
    

    Forward errors from `avio_read` directly. When `avio_read` sees EOF before
    expected bytes can be read, consistently return `AVERROR_INVALIDDATA`

    We used to return `AVERROR(AVERROR_INVALIDDATA)` when failing to read
    metadata block headers. `AVERROR_INVALIDDATA` is already negative, so
    wrapping in `AVERROR` leads to double-negation.

    We used to return `AVERROR(EIO)` when failing to read extended metadata.
    However, many times, the IO-layer is not at fault, the input data is simply
    corrupted (truncated), so we return `AVERROR_INVALIDDATA` here as well.

    — -

    Tomas : changed to use AVERROR_EOF

    • [DH] libavformat/flacdec.c