Recherche avancée

Médias (0)

Mot : - Tags -/auteurs

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

Autres articles (35)

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

  • Other interesting software

    13 avril 2011, par

    We don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
    The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
    We don’t know them, we didn’t try them, but you can take a peek.
    Videopress
    Website : http://videopress.com/
    License : GNU/GPL v2
    Source code : (...)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

Sur d’autres sites (7424)

  • Node-Fluent-ffmpeg stops with Error initializing complex filters. Invalid argument

    28 août 2020, par V.Panichkin

    I use node-fluent-ffmpeg to generate ffmpeg command. I created a node.js app, but it throws an exception :

    


    Error: ffmpeg exited with code 1: Error initializing complex filters.&#xA;Invalid argument&#xA;&#xA;    at ChildProcess.<anonymous> (/home/victor/Documents/work/recorder_ws/node_modules/fluent-ffmpeg/lib/processor.js:182:22)&#xA;    at ChildProcess.emit (events.js:315:20)&#xA;    at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)&#xA;</anonymous>

    &#xA;

    The command that was generated by Node-Fluent-Ffmpeg is

    &#xA;

    ffmpeg -i /home/user/videos/1.webm -i /home/user/videos/3.webm -i /home/user/videos/4.webm -i /home/user/videos/5.webm -y -filter_complex "[0:v] scale=qvga [a0];[1:v] scale=qvga [a1];[2:v] scale=qvga [a2];[3:v] scale=qvga [a3];[a0][a1][a2][a3]xstack=inputs=4:layout=0_0|w0_0|0_h0|w0_h0[out]" -map "[out]" -c:v libx264 -t &#x27;30&#x27;  ./server-generated.mkv&#xA;

    &#xA;

    I checked it several times and didn't find any problem. Afterwards, I run this generated command directly in the console and it works fine.

    &#xA;

    Could someone tell me why node-fluent-ffmpeg cannot run this command with a valid ffmpeg command and throws invalid argument exception ?

    &#xA;

  • Error : ffmpeg exited with code 2 - Docker Container

    15 avril 2020, par Vincenzo Asta

    I created a Docker Container that when I run I get this error (Why do I get this error ? It works locally) :

    &#xA;&#xA;

    {&#xA;    "message": "Error: ffmpeg exited with code 2&#xA;    at ChildProcess.<anonymous> (/app/lib/node_modules/fluent-ffmpeg/lib/processor.js:182:22)&#xA;    at emitTwo (events.js:126:13)&#xA;    at ChildProcess.emit (events.js:214:7)&#xA;    at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)"&#xA;}&#xA;</anonymous>

    &#xA;&#xA;

    Below, the part of code where I get the error (in particular the execution goes into reject) :

    &#xA;&#xA;

    var ffmpeg = require(&#x27;fluent-ffmpeg&#x27;);&#xA;&#xA;module.exports = (sourcePath, outputPath, af, outputFormat="mp3") => {&#xA;    return new Promise((resolve, reject) => {&#xA;        let proc = new ffmpeg({ source: sourcePath, nolog: true });&#xA;        proc.audioQuality(0);&#xA;        proc.audioFilters(af);&#xA;        proc.setFfmpegPath(__dirname &#x2B; "/ffmpeg-20180325-5b31dd1-win64-static/bin/ffmpeg.exe");&#xA;        proc.toFormat(outputFormat).on(&#x27;end&#x27;, function () {&#xA;            resolve();&#xA;        })&#xA;        .on(&#x27;error&#x27;, function (err) {&#xA;            reject(err);&#xA;        })&#xA;            .saveToFile(outputPath);&#xA;    })&#xA;}&#xA;

    &#xA;&#xA;

    My Dockerfile :

    &#xA;&#xA;

    FROM node:8.11.1&#xA;&#xA;WORKDIR /app&#xA;&#xA;COPY package*.json /app/&#xA;&#xA;RUN npm install&#xA;&#xA;COPY . /app/&#xA;&#xA;EXPOSE 8000&#xA;&#xA;CMD [ "node", "app.js" ]&#xA;

    &#xA;&#xA;

    My package.json :

    &#xA;&#xA;

    {&#xA;  "name": "",&#xA;  "version": "1.0.0",&#xA;  "description": "",&#xA;  "main": "app.js",&#xA;  "author": "",&#xA;  "license": "ISC",&#xA;  "dependencies": {&#xA;    "express": "^4.16.4",&#xA;    "azure-storage": "^2.1.0",&#xA;    "crypto": "^0.0.3",&#xA;    "ffmpeg": "^0.0.4",&#xA;    "ffmpeg-normalize": "^1.3.0",&#xA;    "fluent-ffmpeg": "^2.1.2",&#xA;    "fs": "^0.0.1-security",&#xA;    "jmespath": "0.15.0",&#xA;    "mp3-duration": "^1.1.0",&#xA;    "striptags": "^3.1.1"&#xA;  }&#xA;}&#xA;

    &#xA;

  • Nix package : Pass build flag —extra-cflags to ffmpeg at compile time

    13 mai 2024, par catleeball

    I'm a little inexperienced with Nix and NixOS and am struggling a bit with this ffmpeg source build. Any advice is appreciated !

    &#xA;

    Goal

    &#xA;

    Build ffmpeg from source with --extra-cflags="-pipe -O3 -march=znver3 -ffat-lto-objects", ideally using a flake or overlay or similar so that I can build off the existing ffmpeg nix package and maybe even reproducible builds.

    &#xA;

    Attempts

    &#xA;

    I've been trying to follow different advice I've seen online, but looking at ffmpeg in nixpkgs, I'm not sure what I could patch or override. Since configureFlags happens inside the stdenv.mkderivation block, when I try to override it, it doesn't seem to have scope into this variable (and since the derivation explicitly sets onfigurePlatforms = [];, I'm not sure if that would clobber the override changes unless I tried to override the whole long derivation).

    &#xA;

    Looking at the ffmpeg configure script, it seemed like environment variable cflags / cxxflags won't be respected, but it will take them from the --extra-cflags argument, but I could be missing something.

    &#xA;

    Flake attempt

    &#xA;

    Here's an example flake.nix I forked from an example I saw at this github repo

    &#xA;

    {&#xA;  description = "A full build of ffmpeg, including the proprietary stuff";&#xA;&#xA;  inputs.nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable";&#xA;  inputs.flake-utils.url = "github:numtide/flake-utils";&#xA;&#xA;  outputs = { self, nixpkgs, flake-utils }:&#xA;    flake-utils.lib.eachDefaultSystem (system:&#xA;      let&#xA;        pkgs = import nixpkgs {&#xA;          inherit system;&#xA;          config.allowUnfree = true;&#xA;        };&#xA;&#xA;        overrides = {&#xA;          ffmpeg = pkgs.ffmpeg-full;&#xA;          # If this did work, I&#x27;m not sure how it would combine with the derivation in the existing package, e.g. if it would get overridden&#xA;          configureFlags = [ "--extra-cflags -march=znver3 -O3 -pipe -ffat-lto-objects" ];&#xA;          withHeadlessDeps = true;&#xA;          nonfreeLicensing = true;&#xA;          # more options here once things are working above&#xA;        };&#xA;      in&#xA;      rec {&#xA;        packages.ffmpeg-custom = pkgs.ffmpeg-full.override overrides;&#xA;        defaultPackage = packages.ffmpeg-custom;&#xA;      }&#xA;    );&#xA;}&#xA;

    &#xA;

    when building with nix profile install, I encounter the error :

    &#xA;

           error: function &#x27;anonymous lambda&#x27; called with unexpected argument &#x27;configureFlags&#x27;&#xA;&#xA;       at /nix/store/d9wpzgyjlpw1424kw2lyilah6690fnk3-source/pkgs/development/libraries/ffmpeg-full/default.nix:1:1:&#xA;&#xA;            1| { lib, stdenv, buildPackages, ffmpeg, addOpenGLRunpath, pkg-config, perl, texinfo, yasm&#xA;             | ^&#xA;            2| /*&#xA;

    &#xA;

    presumably since configureFlags is defined in the derivation in the original package.

    &#xA;

    Overlay in configuration.nix attempt

    &#xA;

    I tried adding this to my /etc/nixos/configuration.nix also without success :

    &#xA;

    nixpkgs.overlays = [&#xA;  (self: super: {&#xA;    ffmpeg-full = super.ffmpeg-full.override {&#xA;      configureFlags = [&#xA;        "--enable-hardcoded-tables"&#xA;        "--extra-cflags -march=znver3 -O3 -pipe -ffat-lto-objects"&#xA;      ] &#x2B;&#x2B; super.ffmpeg-full.configureFlags;&#xA;    };&#xA;  })&#xA;];&#xA;

    &#xA;

    when building with nixos-rebuild switch I get the same error :

    &#xA;

           error: function &#x27;anonymous lambda&#x27; called with unexpected argument &#x27;configureFlags&#x27;&#xA;&#xA;       at /nix/store/amxbqlhq11xfrbs4vdsyi04fap0abx0v-nixos-23.11/nixos/pkgs/development/libraries/ffmpeg/generic.nix:3:1:&#xA;&#xA;            2|&#xA;            3| { lib, stdenv, buildPackages, removeReferencesTo, addOpenGLRunpath, pkg-config, perl, texinfo, yasm&#xA;             | ^&#xA;            4|&#xA;

    &#xA;

    Context

    &#xA;

    I have a NixOS machine that does very long-running ffmpeg encodes nearly all the time. I was hoping to rebuild headless ffmpeg with more aggressive cflags and maybe some extra options. I hope to benchmark performance differences between different builds.

    &#xA;

    I'll probably use this as an excuse to also build ffmpeg with some extra nonfree dependencies too.

    &#xA;