Recherche avancée

Médias (0)

Mot : - Tags -/organisation

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

Autres articles (19)

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

  • Le plugin : Podcasts.

    14 juillet 2010, par

    Le problème du podcasting est à nouveau un problème révélateur de la normalisation des transports de données sur Internet.
    Deux formats intéressants existent : Celui développé par Apple, très axé sur l’utilisation d’iTunes dont la SPEC est ici ; Le format "Media RSS Module" qui est plus "libre" notamment soutenu par Yahoo et le logiciel Miro ;
    Types de fichiers supportés dans les flux
    Le format d’Apple n’autorise que les formats suivants dans ses flux : .mp3 audio/mpeg .m4a audio/x-m4a .mp4 (...)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 is the first MediaSPIP stable release.
    Its official release date is June 21, 2013 and is announced here.
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

Sur d’autres sites (5034)

  • avcodec/libjxl.h : include version.h

    23 janvier 2024, par Leo Izen
    avcodec/libjxl.h : include version.h
    

    This file has been exported since our minimum required version (0.7.0),
    but it wasn't documented. Instead it was transitively included by
    <jxl/decode.h> (but not jxl/encode.h), which ffmpeg relied on.

    libjxl broke its API in libjxl/libjxl@66b959239355aef5255 by removing
    the transitive include of version.h, and they do not plan on adding
    it back. Instead they are choosing to leave the API backwards-
    incompatible with downstream callers written for some fairly recent
    versions of their API.

    As a result, we include <jxl/version.h> to continue to build against
    more recent versions of libjxl. The version macros removed are also
    present in that file, so we no longer need to redefine them.

    Signed-off-by : Leo Izen <leo.izen@gmail.com>

    • [DH] libavcodec/libjxl.h
  • How to read frames of a video and write them on another video output using FFMPEG and nodejs

    29 décembre 2023, par Aviato

    I am working on a project where I need to process video frames one at a time in Node.js. I aim to avoid storing all frames in memory or the filesystem due to resource constraints. I plan to use the ffmpeg from child processes for video processing.&#xA;I tried reading a video file and then output frames of it in the filesystem first for testing purposes :-

    &#xA;

    const ffmpegProcess = spawn(&#x27;ffmpeg&#x27;, [&#xA;  &#x27;-i&#x27;, videoFile,&#xA;  &#x27;testfolder/%04d.png&#x27; // Output frames to stdout&#xA;]);&#xA;

    &#xA;

    and the above code works fine, it saves the video frames as png files in the filesystem. Now instead of saving them in the file system, I want to read the frames on at a time and use a image manipulation library and than write the final edited frames to another video as output

    &#xA;

    I tried this :-

    &#xA;

    const ffmpegProcess = spawn(&#x27;ffmpeg&#x27;, [&#xA;  &#x27;-i&#x27;, videoFile,&#xA;  &#x27;pipe:1&#x27; // Output frames to stdout&#xA;]);&#xA;&#xA;const ffmpegOutputProcess = spawn(&#x27;ffmpeg&#x27;, [&#xA;  &#x27;-i&#x27;, &#x27;-&#x27;,&#xA;  &#x27;outputFileName.mp4&#x27;&#xA;  ]);&#xA;&#xA;ffmpegProcess.stdout.on(&#x27;data&#x27;, (data) => {&#xA;  // Process the frame data as needed&#xA;  console.log(&#x27;Received frame data:&#x27;);&#xA;  ffmpegOutputProcess.stdin.write(data)&#xA;});&#xA;&#xA;ffmpegProcess.on(&#x27;close&#x27;, (code) => {&#xA;  if (code !== 0) {&#xA;    console.error(`ffmpeg process exited with code ${code}`);&#xA;  } else {&#xA;    console.log(&#x27;ffmpeg process successfully completed&#x27;);&#xA;    &#xA;  }&#xA;});&#xA;&#xA;// Handle errors&#xA;ffmpegProcess.on(&#x27;error&#x27;, (err) => {&#xA;  console.error(&#x27;Error while spawning ffmpeg:&#x27;, err);&#xA;});&#xA;

    &#xA;

    But when I tried above code and also some other modifications in the input and output suffix in the command I got problems as below :-

    &#xA;

      &#xA;
    1. ffmpeg process exited with code 1
    2. &#xA;

    3. The final output video was corrupted when trying to initializing the filters for commands :-
    4. &#xA;

    &#xA;

    &#xA;const ffmpegProcess = spawn(&#x27;ffmpeg&#x27;, [&#xA; &#x27;-i&#x27;, videoFile,&#xA; &#x27;-f&#x27;, &#x27;rawvideo&#x27;,&#xA; &#x27;-pix_fmt&#x27;, &#x27;rgb24&#x27;,&#xA; &#x27;pipe:1&#x27; // Output frames to stdout&#xA;]);&#xA;&#xA;const ffmpegOutputCommand = [&#xA; &#x27;-f&#x27;, &#x27;rawvideo&#x27;,&#xA; &#x27;-pix_fmt&#x27;, &#x27;rgb24&#x27;,&#xA; &#x27;-s&#x27;, &#x27;1920x1080&#x27;,&#xA; &#x27;-r&#x27;, &#x27;30&#x27;,&#xA; &#x27;-i&#x27;, &#x27;-&#x27;,&#xA; &#x27;-c:v&#x27;, &#x27;libx264&#x27;,&#xA; &#x27;-pix_fmt&#x27;, &#x27;yuv420p&#x27;,&#xA; outputFileName&#xA;];&#xA;

    &#xA;

    Thank you so much in advance :)

    &#xA;

  • Processing video frame by frame in AWS Lambda with Node.js and FFmpeg [closed]

    29 décembre 2023, par Aviato

    I am working on a project where I need to process video frames one at a time in an AWS Lambda function using Node.js. My goal is to avoid storing all frames in memory or the filesystem due to resource constraints. I plan to use the fluent-ffmpeg library or ffmpeg from child processes for video processing.

    &#xA;

    In the past, I used OpenCV to process videos and frames without writing the frames on the disk or storing all the frames at once on the memory itself. But now as I am using node js, its a little hard to set up the code using ffmpeg, etc.

    &#xA;

    Here is a small snippet from what I did with opencv :-

    &#xA;

    import cv2&#xA;&#xA;cap = cv2.VideoCapture(video_file)&#xA;&#xA;out = cv2.VideoWriter(&#x27;output.mp4&#x27;, fourcc, fps, (width, height))&#xA;&#xA;def generate_frame():&#xA;        while cap.isOpened():&#xA;            code, frame = cap.read()&#xA;            if code:&#xA;                yield frame&#xA;            else:&#xA;                print("completed")&#xA;                break&#xA;&#xA;for i, frame in enumerate(generate_frame()):&#xA;          # Now we can process the video frames directly and write them on the output opencv&#xA;          out.write(editing_frames)&#xA;

    &#xA;

    Additionally, I intend to leverage image processing libraries like Sharp and the Canvas API to edit individual frames before assembling the final video. I am looking for help in handling video frames efficiently within the constraints of AWS Lambda.

    &#xA;

    Any insights, code snippets, or recommendations would be greatly appreciated. Thank you !

    &#xA;