
Recherche avancée
Autres articles (65)
-
Mise à jour de la version 0.1 vers 0.2
24 juin 2013, parExplications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...) -
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
-
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 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 (...)
Sur d’autres sites (10147)
-
Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
28 août 2020, par bbdangarI am using this library : com.arthenica:mobile-ffmpeg-full:4.4


Getting this error message while running the command :


final String command = "-y -i "+ inputPath +" -ar 22050 -hls_list_size 1000000 -hls_time 2 -s 640x360 " + outputPath;



here is the complete code :


private void convertVideo() {
 String inputPath = "/storage/emulated/0/Download/video.mp4";
 String outputPath = "/storage/emulated/0/Download/output.m3u8";
 final String command = "-y -i "+ inputPath +" -ar 22050 -hls_list_size 1000000 -hls_time 2 -s 640x360 " + outputPath;
 FFmpeg.executeAsync(command, new ExecuteCallback() {
 @Override
 public void apply(long executionId, int returnCode) {

 if (returnCode == RETURN_CODE_SUCCESS) {
 Log.i(TAG, "Command execution completed successfully.");
 } else if (returnCode == RETURN_CODE_CANCEL) {
 Log.i(TAG, "Command execution cancelled by user.");
 } else {
 Log.i(TAG, String.format("Command execution failed with rc=%d and the output below.", returnCode));
 Config.printLastCommandOutput(Log.INFO);
 }
 }
 });

 }



here is output log :


2020-08-28 07:05:59.355 10725-10820 W/mobile-ffmpeg: [graph 0 input from stream 0:0 @ 0xe2306c80] sws_param option is deprecated and ignored
2020-08-28 07:05:59.448 10725-10820 E/mobile-ffmpeg: [h264_v4l2m2m @ 0xcb442c00] can't configure encoder
2020-08-28 07:05:59.448 10725-10820 E/mobile-ffmpeg: Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
2020-08-28 07:05:59.463 10725-10820 I/mobile-ffmpeg: Conversion failed!
2020-08-28 07:05:59.465 10725-10725 I/mobile-ffmpeg: ffmpeg version v4.4-dev-416 Copyright (c) 2000-2020 the FFmpeg developers



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