Recherche avancée

Médias (2)

Mot : - Tags -/documentation

Autres articles (39)

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

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

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

  • Saving Uncompressed Video Files using OpenCv, Gstreamer, and/or FFMPEG ?

    21 septembre 2022, par adav0033

    I have been trying to implement the cv::VideoWriter function from OpenCV to generate a an uncompressed video file. I started this because of a statement within the OpenCV Documentation which I will link here along with the statement.

    


    cv::VideoWriter::VideoWriter    (   const String &  filename,
int     fourcc,
double  fps,
Size    frameSize,
bool    isColor = true 
)       


    


    "If FFMPEG is enabled, using codec=0 ; fps=0 ; you can create an uncompressed (raw) video file."

    


    Ref. https://docs.opencv.org/3.4/dd/d9e/classcv_1_1VideoWriter.html

    


    However whilst troubleshooting the function I came across the refuting statement,

    


    " VideoCapture and VideoWriter do not provide interface to access raw compressed video stream, except maybe MJPEG in some cases.
Make sure you actually use FFmpeg backend by setting apiPreference parameter : VideoWriter("outfile.avi", cv2.CAP_FFMPEG, ...)"

    


    Ref. https://github.com/opencv/opencv/issues/14573

    


    I am now confused about how I go about writing the cv::VideoWriter function to satisfy the requirements to create an uncompressed video file (.avi) and if it is even possible. If it is not possible how do I achieve the outcome of saving an raw uncompressed video file, as I assume it would use some combination of FFMPEG, OpenCV,or Gstreamer.

    


    Note : My code is implemented in c++

    


  • Saving Raw Uncompressed Video Files using OpenCv, Gstreamer, and/or FFMPEG ?

    20 septembre 2022, par adav0033

    I have been trying to implement the cv::VideoWriter function from OpenCV to generate a an uncompressed (raw) video file. I started this because of a statement within the OpenCV Documentation which I will link here along with the statement.

    


    cv::VideoWriter::VideoWriter    (   const String &  filename,
int     fourcc,
double  fps,
Size    frameSize,
bool    isColor = true 
)       


    


    "If FFMPEG is enabled, using codec=0 ; fps=0 ; you can create an uncompressed (raw) video file."

    


    Ref. https://docs.opencv.org/3.4/dd/d9e/classcv_1_1VideoWriter.html

    


    However whilst troubleshooting the function I came across the refuting statement,

    


    " VideoCapture and VideoWriter do not provide interface to access raw compressed video stream, except maybe MJPEG in some cases.
Make sure you actually use FFmpeg backend by setting apiPreference parameter : VideoWriter("outfile.avi", cv2.CAP_FFMPEG, ...)"

    


    Ref. https://github.com/opencv/opencv/issues/14573

    


    I am now confused about how I go about writing the cv::VideoWriter function to satisfy the requirements to create a raw uncompressed video file (.avi) and if it is even possible. If it is not possible how do I achieve the outcome of saving an raw uncompressed video file, as I assume it would use some combination of FFMPEG, OpenCV,or Gstreamer.

    


    Note : My code is implemented in c++

    


  • How to stop perl buffering ffmpeg output

    4 février 2017, par Sebastian King

    I am trying to have a Perl program process the output of an ffmpeg encode, however my test program only seems to receive the output of ffmpeg in periodic chunks, thus I am assuming there is some sort of buffering going on. How can I make it process it in real-time ?

    My test program (the tr command is there because I thought maybe ffmpeg’s carriage returns were causing perl to see one big long line or something) :

    #!/usr/bin/perl

    $i = "test.mkv"; # big file, long encode time
    $o = "test.mp4";

    open(F, "-|", "ffmpeg -y -i '$i' '$o' 2>&1 | tr '\r' '\n'")
           or die "oh no";

    while(<f>) {
           print "A12345: $_"; # some random text so i know the output was processed in perl
    }
    </f>

    Everything works fine when I replace the ffmpeg command with this script :

    #!/bin/bash

    echo "hello";

    for i in `seq 1 10`; do
           sleep 1;
           echo "hello $i";
    done

    echo "bye";

    When using the above script I see the output each second as it happens. With ffmpeg it is some 5-10 seconds or so until it outputs and will output sometimes 100 lines each output.

    I have tried using the program unbuffer ahead of ffmpeg in the command call but it seems to have no effect. Is it perhaps the 2>&amp;1 that might be buffering ?
    Any help is much appreciated.

    If you are unfamiliar with ffmpeg’s output, it outputs a bunch of file information and stuff to STDOUT and then during encoding it outputs lines like

    frame=  332 fps= 93 q=28.0 size=     528kB time=00:00:13.33 bitrate= 324.2kbits/s speed=3.75x

    which begin with carriage returns instead of new lines (hence tr) on STDERR (hence 2>&amp;1).