Recherche avancée

Médias (1)

Mot : - Tags -/ogg

Autres articles (28)

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

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

  • Pas question de marché, de cloud etc...

    10 avril 2011

    Le vocabulaire utilisé sur ce site essaie d’éviter toute référence à la mode qui fleurit allègrement
    sur le web 2.0 et dans les entreprises qui en vivent.
    Vous êtes donc invité à bannir l’utilisation des termes "Brand", "Cloud", "Marché" etc...
    Notre motivation est avant tout de créer un outil simple, accessible à pour tout le monde, favorisant
    le partage de créations sur Internet et permettant aux auteurs de garder une autonomie optimale.
    Aucun "contrat Gold ou Premium" n’est donc prévu, aucun (...)

Sur d’autres sites (5017)

  • configure : add —enable-libvpl option

    3 février 2021, par Haihao Xiang
    configure : add —enable-libvpl option
    

    This allows user to build FFmpeg against Intel oneVPL. oneVPL 2.6
    is the required minimum version when building Intel oneVPL code.

    It will fail to run configure script if both libmfx and libvpl are
    enabled.

    It is recommended to use oneVPL for new work, even for currently available
    hardwares [1]

    Note the preferred child device type is d3d11va for libvpl on Windows.
    The commands below will use d3d11va if d3d11va is available on Windows.
    $ ffmpeg -hwaccel qsv -c:v h264_qsv ...
    $ ffmpeg -qsv_device 0 -hwaccel qsv -c:v h264_qsv ...
    $ ffmpeg -init_hw_device qsv=qsv:hw_any -hwaccel qsv -c:v h264_qsv ...
    $ ffmpeg -init_hw_device qsv=qsv:hw_any,child_device=0 -hwaccel qsv -c:v h264_qsv ...

    User may use child_device_type option to specify child device type to
    dxva2 or derive a qsv device from a dxva2 device
    $ ffmpeg -init_hw_device qsv=qsv:hw_any,child_device=0,child_device_type=dxva2 -hwaccel qsv -c:v h264_qsv ...
    $ ffmpeg -init_hw_device dxva2=d3d9:0 -init_hw_device qsv=qsv@d3d9 -hwaccel qsv -c:v h264_qsv ...

    [1] https://www.intel.com/content/www/us/en/develop/documentation/upgrading-from-msdk-to-onevpl/top.html

    • [DH] configure
  • Cannot merge audio and video streams from ytdl-core

    20 août 2022, par Abhigyan Kumar

    I am trying to merge ytdl-core video only and audio only streams and sending the merged stream are response to user (for download in browser). With JavaScript only, its working perfectly fine. But typeScript is saying child process stdio is undefined

    


    import express, { Request } from "express";
import ytdl from "ytdl-core";
import cp from "child_process";
import ffmpeg from "ffmpeg-static";    
app.get("/downloadmerged", (req, res) => {
res.setHeader("Content-Type", "video/mp4");
res.setHeader(
  `Content-Disposition`,
  `attachment; filename="Merged.mp4"`
);
  const ref = "https://www.youtube.com/watch?v=aR-KAldshAE";
  const audio = ytdl(ref, { filter: "audioonly", quality: "highestaudio" });
  const video = ytdl(ref, { filter: "videoonly", quality: "highestvideo" });
  const ffmpegProcess = cp.spawn(
    ffmpeg,
    [
      // Remove ffmpeg's console spamming
      "-loglevel",
      "0",
      "-hide_banner",
      // 3 second audio offset
      "-itsoffset",
      "3.0",
      "-i",
      "pipe:3",
      "-i",
      "pipe:4",
      // Rescale the video
      "-vf",
      "scale=320:240",
      // Choose some fancy codes
      "-c:v",
      "libx265",
      "-x265-params",
      "log-level=0",
      "-c:a",
      "flac",
      // Define output container
      "-f",
      "matroska",
      "pipe:5",
    ],
    {
      windowsHide: true,
      stdio: [
        /* Standard: stdin, stdout, stderr */
        "inherit",
        "inherit",
        "inherit",
        /* Custom: pipe:3, pipe:4, pipe:5 */
        "pipe",
        "pipe",
        "pipe",
      ],
    }
  );
  ffmpegProcess.on("close", () => {
    process.stdout.write("\n\n\n");
    console.log("done");
  });
 
  audio.pipe(ffmpegProcess.stdio[3]);
  video.pipe(ffmpegProcess.stdio[4]);
  ffmpegProcess.stdio[5].pipe(res);
});


    


    line ffmpegProcess.stdio[3] and ffmpegProcess.stdio[4] are giving type error

    


    Argument of type 'Readable | Writable | null | undefined' is not assignable to parameter of type 'WritableStream'.Type 'undefined' is not assignable to type 'WritableStream'

  


    


  • How to store output of ffmpeg in a variable using NodeJS / execFile and ffmpeg ?

    22 août 2022, par Radespy

    I'm running an Electron app which uses the 'ffmpeg-static-electron' package to process a local video file.

    


    I am trying to store the output as a buffer in a variable for subsequent processing.

    


    Using IPC, I can successfully execute the following in the main.js file (running Node), which produces a cropped video file.

    


    const { execFile } = require("child-process")
const ffmpeg = require("ffmpeg-static-electron")

ipcMain.on("crop_video", () => {

execFile(
    `${ffmpeg.path}`,
    [
      "-i",
      `${testVideoCropPath}`,
      "-filter:v",
      `crop=600:600:100:100`,
      "-preset",
      "fast",
      "-progress",
      "pipe:1",
      `${path.join(desktopDirPath, "cropped-video.mp4")}`,
    ],
    (error, stdout, stderr) => {
      if (error) {
        console.error("stderr", stderr);
        throw error;
      }
      console.log("Success", stdout);
    }
  );
})


    


    Here's the output :

    


    Success frame=238
[1] fps=0.0
...
[1] dup_frames=0
[1] drop_frames=0
[1] speed=8.23x
[1] progress=end


    


    What I wish to do is to store the cropped-video as a buffer in a variable.

    


    To experiment, I tried :

    


    ipcMain.on("crop_video", () => {

const test = execFile(
    `${ffmpeg.path}`,
    [
      "-i",
      `${testVideoCropPath}`,
      "-filter:v",
      `crop=600:600:100:100`,
      "-preset",
      "fast",
      `${path.join(desktopDirPath, "cropped-video.mp4")}`,
       "pipe:1",
    ],
    (error, stdout, stderr) => {
      if (error) {
        console.error("stderr", stderr);
        throw error;
      }
      console.log("Success", stdout);
    }
  );

   test.on('data', (data) => {console.log(typeof data)}
})


    


    Which doesn't print anything to the console.

    


    How can I access sdout in buffer format ?

    


    Is there a way to store the output with something like :

    


    test.on('data', (data)=> {
let var = Buffer.from(data)})


    


    Thanks.