Recherche avancée

Médias (1)

Mot : - Tags -/framasoft

Autres articles (69)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

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

  • ERROR in ./node_modules/fluent-ffmpeg/index.js Module not found : Error : Can't resolve './lib-cov/fluent-ffmpeg'

    3 octobre 2023, par yasgur99

    When I do yarn add fluent-ffmpeg i get this issue :

    



    WARNING in ./node_modules/electron-debug/index.js 96:45-58
Critical dependency: the request of a dependency is an expression
 @ dll renderer

WARNING in ./node_modules/electron-debug/index.js 97:61-74
Critical dependency: the request of a dependency is an expression
 @ dll renderer

WARNING in ./node_modules/fluent-ffmpeg/lib/options/misc.js 27:21-40
Critical dependency: the request of a dependency is an expression
 @ ./node_modules/fluent-ffmpeg/lib/fluent-ffmpeg.js
 @ ./node_modules/fluent-ffmpeg/index.js
 @ dll renderer

ERROR in ./node_modules/fluent-ffmpeg/index.js
Module not found: Error: Can't resolve './lib-cov/fluent-ffmpeg' in '/Users/yasgur99/Documents/desktopapp/node_modules/fluent-ffmpeg'
 @ ./node_modules/fluent-ffmpeg/index.js 1:48-82
 @ dll renderer


    



    They said they fixed it in this GitIssue : here

    



    Anyone have any advice ?

    



    Some notes : Im using babel, I'm building an electron application

    


  • The problem of code that generated typescript (node-fluent-ffmpeg module)

    10 décembre 2022, par Steve Rock

    This is my typescript code :

    



    import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';
import { FfmpegCommand } from 'fluent-ffmpeg'

async function bootstrap() {
  const app = await NestFactory.create(AppModule);
  let test

  try {
    test = new FfmpegCommand('./adventure.mkv');
  } catch (error) {
    console.log(error);

  }

  await app.listen(3000);
}

bootstrap();


    



    Generated Javascript code :

    



    "use strict";
var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, generator) {
    function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }
    return new (P || (P = Promise))(function (resolve, reject) {
        function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }
        function rejected(value) { try { step(generator["throw"](value)); } catch (e) { reject(e); } }
        function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }
        step((generator = generator.apply(thisArg, _arguments || [])).next());
    });
};
Object.defineProperty(exports, "__esModule", { value: true });
const core_1 = require("@nestjs/core");
const app_module_1 = require("./app.module");
const fluent_ffmpeg_1 = require("fluent-ffmpeg");
function bootstrap() {
    return __awaiter(this, void 0, void 0, function* () {
        const app = yield core_1.NestFactory.create(app_module_1.AppModule);
        let test;
        try {
            test = new fluent_ffmpeg_1.FfmpegCommand('./adventure.mkv');
        }
        catch (error) {
            console.log(error);
        }
        yield app.listen(3000);
    });
}
bootstrap();
//# sourceMappingURL=main.js.map


    



    When I run this application I've next error :

    



    main.ts:12
message :"fluent_ffmpeg_1.FfmpegCommand is not a constructor"
stack :"TypeError : fluent_ffmpeg_1.FfmpegCommand is not a constructor\n at c :\nest\dist\src\main.js:20:20\n at Generator.next ()\n at fulfilled (c :\nest\dist\src\main.js:5:58)\n at process._tickCallback (internal/process/next_tick.js:68:7)\n at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)\n at startup (internal/bootstrap/node.js:283:19)\n at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)"

    



    That's beacause this raw test = new fluent_ffmpeg_1.FfmpegCommand('./adventure.mkv'). When I change this on just test = new fluent_ffmpeg_1('./adventure.mkv') I haven't the error. Do you know how to fix it. If you know where are ffmpeg exapmles on typescript please share with me :)

    


  • Connecting ffmpeg java module to named pipe

    27 novembre 2019, par Ehsan5

    I want to extract the output of folowing ffmpeg Module with the help of Named pipe. I am currently having problems with communication of ffmpeg and named pipe, but thank you for explaining how to extract stream bytes from output named pipe and convert it to images.

    My code gives socket connection error when using named pipe. I have used method that suggested in ffmpeg main page (pipe:0 for input and pipe:1 for output) but because it is not named pipe I cannot use it in the client side. It should be noted that named pipe is opened successfully with jna win32 module.

    This is server side code(but i tested it with \\.\pipe\PIPE also) :

    FFmpegBuilder builder = new FFmpegBuilder()
    .setInput(input.getPath())
    .addOutput(" -f avi pipe:1 ")
    .addExtraArgs(videoFilterStr)
    .done();
    UUID caller = UUID.randomUUID();
    try {FFmpegHelper.builder().progressListener().build().run(builder, caller)...