Recherche avancée

Médias (91)

Autres articles (96)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    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 (...)

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

  • Installation en mode standalone

    4 février 2011, par

    L’installation de la distribution MediaSPIP se fait en plusieurs étapes : la récupération des fichiers nécessaires. À ce moment là deux méthodes sont possibles : en installant l’archive ZIP contenant l’ensemble de la distribution ; via SVN en récupérant les sources de chaque modules séparément ; la préconfiguration ; l’installation définitive ;
    [mediaspip_zip]Installation de l’archive ZIP de MediaSPIP
    Ce mode d’installation est la méthode la plus simple afin d’installer l’ensemble de la distribution (...)

Sur d’autres sites (12272)

  • Which directory should i put FFmpeg ? [duplicate]

    25 juillet 2020, par Panda Gaming23

    I am making a discord bot and I get the following error

    


    node:4) UnhandledPromiseRejectionWarning: Error: FFmpeg/avconv not found!

2020-07-25T01:00:13.991518+00:00 app[worker.1]:     at Function.getInfo (/app/node_modules/prism-media/src/core/FFmpeg.js:130:11)

2020-07-25T01:00:13.991519+00:00 app[worker.1]:     at Function.create (/app/node_modules/prism-media/src/core/FFmpeg.js:143:38)

2020-07-25T01:00:13.991519+00:00 app[worker.1]:     at new FFmpeg (/app/node_modules/prism-media/src/core/FFmpeg.js:44:27)

2020-07-25T01:00:13.991520+00:00 app[worker.1]:     at AudioPlayer.playUnknown (/app/node_modules/discord.js/src/client/voice/player/BasePlayer.js:47:20)

2020-07-25T01:00:13.991520+00:00 app[worker.1]:     at VoiceConnection.play (/app/node_modules/discord.js/src/client/voice/util/PlayInterface.js:71:28)

2020-07-25T01:00:13.991522+00:00 app[worker.1]:     at play (/app/commands/play.js:14:34)

2020-07-25T01:00:13.991522+00:00 app[worker.1]:     at /app/commands/play.js:42:5

2020-07-25T01:00:13.991522+00:00 app[worker.1]:     at processTicksAndRejections (internal/process/task_queues.js:97:5)

2020-07-25T01:00:13.991629+00:00 app[worker.1]: (node:4) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)



    


    Here is the code

    


    const ytdl = require("ytdl-core");
const Discord = require("discord.js");

var servers = {};

module.exports = {
  name: "play",
  description: "this is a music play command!",
  execute(message, args) {
  
  function play(connection, message) {
        var server = servers[message.guild.id];
        
        server.dispatcher = connection.play(ytdl(server.queue[0], {filter: "audioonly"}));
        
        server.queue.shift();
        
        server.dispatcher.on("end", function () {
            if(server.queue[0]){
                play(connection, message);
            }
            else {connection.disconnect();}
        })
    }
    if (!args[0]) {
      message.channel.send("you need to provide a link!");
      return;
    }

    if (!message.member.voice.channel) {
      message.channel.send("you must be in ||a|| voice channel to play the bot!");
      return;
    }

    if (!servers[message.guild.id]) servers[message.guild.id] = { queue: [] };
    
    var server = servers[message.guild.id];
    
    server.queue.push(args[0]);
     
    if (!message.member.voice.connection) message.member.voice.channel.join().then(function(connection) {
    play(connection, message);
    })
  },
};


    


    I would like to know which directory I should put FFmpeg.

    


    I would also like to know if the FFmpeg executable has to be in a folder or compressed or if i can just place the executable in a certain directory

    


    I am hosting my bot using Heroku on a Mac using Discord.js V12

    


    Please help.

    


    Thanks !

    


  • Nomenclature #4519 (Nouveau) : Renommage de terminologie (blacklist / whitelist)

    13 juillet 2020

    En lisant la compilation [PHP Annotated – June 2020](https://blog.jetbrains.com/phpstorm/2020/06/php-annotated-june-2020/) on tombe sur ce point :

    [[RFC] Change terminology to ExcludeList](https://wiki.php.net/rfc/change-terminology-to-excludelist) — The topic of renaming offensive terms has not been overlooked by the PHP world either. There have been [heated discussions](https://externals.io/message/110515) in the Internals.
    In the PHP core, the change affects only one thing : the configuration directive `opcache.blacklist_filename` should be renamed to `opcache.exclude_list_filename`.
    Many other PHP tools have already made changes in this regard : [PHPUnit](https://github.com/sebastianbergmann/phpunit/blob/master/ChangeLog-9.3.md#930---2020-08-07), [Drupal](https://www.drupal.org/project/drupal/issues/2993575), [Xdebug](https://github.com/xdebug/xdebug/commit/63b43b51e43b794cf8cd740e54089b2b7320fbe1), [Yii](https://github.com/yiisoft/yii2/pull/18104), [Composer](https://github.com/composer/composer/pull/8957) (+ [working with non-master Git branches](https://blog.packagist.com/composer-and-default-git-branches/)).

    C’est certainement intéressant aussi de songer à ces renommages chez nous également, utilisés à quelques endroits.

  • doc/muxers.texi : fix build issue for unknown command

    18 avril 2021, par Guo, Yejun
    doc/muxers.texi : fix build issue for unknown command
    

    The build log :
    ** Unknown command `@code' (left as is) (in src/doc/muxers.texi l. 2020)
    *** '' without macro. Before : -map option with the ffmpeg CLI tool. (in src/doc/muxers.texi l. 2020)
    *** '' without opening '' before : option with the ffmpeg CLI tool. (in src/doc/muxers.texi l. 2020)

    • [DH] doc/muxers.texi