
Recherche avancée
Autres articles (67)
-
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...) -
Possibilité de déploiement en ferme
12 avril 2011, parMediaSPIP peut être installé comme une ferme, avec un seul "noyau" hébergé sur un serveur dédié et utilisé par une multitude de sites différents.
Cela permet, par exemple : de pouvoir partager les frais de mise en œuvre entre plusieurs projets / individus ; de pouvoir déployer rapidement une multitude de sites uniques ; d’éviter d’avoir à mettre l’ensemble des créations dans un fourre-tout numérique comme c’est le cas pour les grandes plate-formes tout public disséminées sur le (...) -
Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs
12 avril 2011, parLa manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras.
Sur d’autres sites (9109)
-
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) -
avcodec/proresenc_anatoliy : support for more color matrix for proresenc
5 novembre 2019, par Limin Wangavcodec/proresenc_anatoliy : support for more color matrix for proresenc
Please tested with below command :
./ffmpeg -i ../fate-suite/mpeg2/t.mpg -c:v prores_aw -color_primaries bt2020 -colorspace bt2020_ncl -color_trc smpte2084 -an output.movmediainfo outout.mov
...
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant./ffmpeg -i ../fate-suite/mpeg2/t.mpg -c:v prores_aw -color_primaries bt2020 -colorspace bt2020_ncl -color_trc arib-std-b67 -an output.mov
mediainfo outout.mov
...
Color primaries : BT.2020
Transfer characteristics : HLG
Matrix coefficients : BT.2020 non-constantSigned-off-by : Limin Wang <lance.lmwang@gmail.com>
-
FFMPEG not found error while attempting to implement ffmpeg into discord bot
17 février 2020, par Ravenr_While implementing a music feature into my node.js discord.js discord bot, I got an error claiming that it cant find FFMPEG. I reinstalled ffmpeg 3 times to no avail.
This is the full error
2020-02-17T01:48:30.403766+00:00 app[worker.1]: (node:4) UnhandledPromiseRejectionWarning: Error: FFMPEG not found
2020-02-17T01:48:30.403797+00:00 app[worker.1]: at Function.selectFfmpegCommand (/app/node_modules/prism-media/src/transcoders/ffmpeg/Ffmpeg.js:46:13)
2020-02-17T01:48:30.403798+00:00 app[worker.1]: at new FfmpegTranscoder (/app/node_modules/prism-media/src/transcoders/ffmpeg/Ffmpeg.js:7:37)
2020-02-17T01:48:30.403798+00:00 app[worker.1]: at new MediaTranscoder (/app/node_modules/prism-media/src/transcoders/MediaTranscoder.js:10:19)
2020-02-17T01:48:30.403799+00:00 app[worker.1]: at new Prism (/app/node_modules/prism-media/src/Prism.js:5:23)
2020-02-17T01:48:30.403799+00:00 app[worker.1]: at new VoiceConnection (/app/node_modules/discord.js/src/client/voice/VoiceConnection.js:46:18)
2020-02-17T01:48:30.403800+00:00 app[worker.1]: at /app/node_modules/discord.js/src/client/voice/ClientVoiceManager.js:63:22
2020-02-17T01:48:30.403800+00:00 app[worker.1]: at new Promise (<anonymous>)
2020-02-17T01:48:30.403801+00:00 app[worker.1]: at ClientVoiceManager.joinChannel (/app/node_modules/discord.js/src/client/voice/ClientVoiceManager.js:45:12)
2020-02-17T01:48:30.403801+00:00 app[worker.1]: at VoiceChannel.join (/app/node_modules/discord.js/src/structures/VoiceChannel.js:130:30)
2020-02-17T01:48:30.403802+00:00 app[worker.1]: at Object.execute (/app/commands/play.js:31:64)
2020-02-17T01:48:30.404044+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: 2)
2020-02-17T01:48:30.404052+00:00 app[worker.1]: (node:4) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
</anonymous>This is the code
const ytdl = require("ytdl-core");
module.exports = {
name: 'play',
description: 'initiates music methods of the bot',
execute(msg, args){
var servers = {};
function play(connection, msg){
var server = servers[msg.guild.id];
server.dispatcher = connection.playStream(ytdl(server.queue[0], {filter: "audioonly"}));
server.queue.shift();
server.dispatcher.on("end", function(){
if(server.queue[0]){
play(connection, msg);
}else{
connection.disconnect();
}
});
}
if(!args[1]) return msg.channel.send("you need to provide a link");
if(!msg.member.voiceChannel) return msg.channel.send("You must be in a voice channel to use this feature");
if(!servers[msg.guild.id]) servers[msg.guild.id] = {
queue: []
}
var server = servers[msg.guild.id];
server.queue.push(args[1]);
if(!msg.guild.voiceConnection) msg.member.voiceChannel.join().then(function(connection){
play(connection, msg);
})
}
}I have no idea what the issue is. I am using heroku to deploy if that matters at all.