Advanced search

Medias (1)

Tag: - Tags -/publicité

Other articles (41)

  • Participer à sa traduction

    10 April 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • Les statuts des instances de mutualisation

    13 March 2010, by

    Pour des raisons de compatibilité générale du plugin de gestion de mutualisations avec les fonctions originales de SPIP, les statuts des instances sont les mêmes que pour tout autre objets (articles...), seuls leurs noms dans l’interface change quelque peu.
    Les différents statuts possibles sont : prepa (demandé) qui correspond à une instance demandée par un utilisateur. Si le site a déjà été créé par le passé, il est passé en mode désactivé. publie (validé) qui correspond à une instance validée par un (...)

  • MediaSPIP 0.1 Beta version

    25 April 2011, by

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

On other websites (4725)

  • Which directory should i put FFmpeg? [duplicate]

    25 July 2020, by 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 July 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.

  • avcodec/h264: Keep a reference to the last picture for EC

    11 January 2015, by Michael Niedermayer
    avcodec/h264: Keep a reference to the last picture for EC
    

    This and the next commit improve error concealment for
    green-block-artifacts-from-canon-100-hs.MOV

    Signed-off-by: Michael Niedermayer <michaelni@gmx.at>

    • [DH] libavcodec/h264.c
    • [DH] libavcodec/h264.h
    • [DH] libavcodec/h264_refs.c
    • [DH] libavcodec/h264_slice.c