
Recherche avancée
Médias (1)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (68)
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP 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" (...) -
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)
Sur d’autres sites (10307)
-
Which directory should i put FFmpeg ? [duplicate]
25 juillet 2020, par Panda Gaming23I 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 2020En 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, Yejundoc/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)