Recherche avancée

Médias (1)

Mot : - Tags -/belgique

Autres articles (79)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 est la première version de MediaSPIP stable.
    Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

Sur d’autres sites (12258)

  • 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)...
  • react-native-ffmpeg : Native module cannot be null (ios) and null is not an object (evaluating 'RNFFmpegModule.enableLogEvents') (android)

    4 mars 2020, par foxtrotuniform6969

    I have a basic expo project that I’ve eject as expokit, and proceeded to run expo install react-native-ffmpeg. When then running expo start I was greeted with Native module cannot be null on my iOS device and null is not an object (evaluating  'RNFFmpegModule.enableLogEvents').

    After that, I re-read the react-native-ffmpeg documentation and added pod 'react-native-ffmpeg', :podspec => '../node_modules/react-native-ffmpeg/ios/react-native-ffmpeg.podspec' to my ios/Podfile and ran pod install. Still no luck.

    After that, I deleted the node_modules folder and yarn.lock file, re-ran yarn, went into the ios directory, deleted the Pods folder and Podfile.lock file and re-ran pod install and still had no luck !

    The error is less than helpful. Any ideas where to look ?