
Recherche avancée
Médias (1)
-
The Slip - Artworks
26 septembre 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Texte
Autres articles (85)
-
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 ;
-
Ecrire une actualité
21 juin 2013, parPrésentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
Vous pouvez personnaliser le formulaire de création d’une actualité.
Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)
Sur d’autres sites (6824)
-
Redirect ffmpeg console output to a string or a file in C++
21 juillet 2019, par NeoFahrenheitI’m trying to use ffmpeg to do some operations for me. It’s really simple for now. I want to omit the ffmpeg output in my console, either redirecting them to strings or a .txt file that I can control. I’m on Windows 10.
I have tried _popen (with and "r" and "w") and system("ffmpeg command > output.txt")’, with no success.
#include <iostream>
#include
using namespace std;
#define BUFSIZE 256
int main()
{
/* 1.
x = system("ffmpeg -i video.mp4 -i audio.mp4 -c copy output.mp4 > output.txt");
*/
/* 2.
FILE* p;
p = _popen("ffmpeg -i video.mp4 -i audio.mp4 -c copy output.mp4", "w");
_pclose(p);
*/
/* 3.
char cmd[200] = { "ffmpeg -i video.mp4 -i audio.mp4 -c copy output.mp4" };
char buf[BUFSIZE];
FILE* fp;
if ((fp = _popen(cmd, "r")) == NULL) {
printf("Error opening pipe!\n");
return -1;
}
while (fgets(buf, BUFSIZE, fp) != NULL) {
// Do whatever you want here...
// printf("OUTPUT: %s", buf);
}
if (_pclose(fp)) {
printf("Command not found or exited with error status\n");
return -1;
}
*/
return 0;
}
</iostream>Further in the development, I would like to know when the ffmpeg process finished (maybe I can monitor the ffmpeg return value ?) or to display only the last line if the some error occurred.
-
Why is ffmpeg taking up so much memory when I try to stop a livestream ?
4 juillet 2019, par FiskFan1999When the ffmpeg function is running, there are no problems with memory and everything runs smoothly. However, when I attempt to stop the stream/ffmpeg by pressing q (or ctrl-c), ffmpeg freezes, doesn’t take any other inputs, and suddenly takes up an obscene amount of memory.
I am using ffmpeg to livestream on youtube. I am using a MacBook Mid 2015 running macOS Mojave.
here is the function I am using with ffmpeg.
ffmpeg -re -f lavfi -i testsrc2=s=1280x720:r=60 -re -i "INPUT FILE.mp3" -vcodec libx264 -pix_fmt yuv420p -preset "ultrafast" -r 60 -g 120 -b:v 6168000 -filter_complex "[0]scale=1280:720;[1]aloop=start=0:size=202*44100:loop=-1" -acodec libmp3lame -ar 44100 -threads 3 -b:a 640000 -qscale:a 5 -bufsize 512k -f flv ${YOUTUBE_URL}/${KEY}
The command runs perfectly and as expected while it is running. At this point, in Activity Monitor I can see that ffmpeg seems to peak to about 101 MB. When I press q, which is the button to end the encoding, if the stream had been going for about ten minutes ffmpeg freezes and in Activity monitor the ffmpeg command appears to climb to several gigabytes of memory without any sign of stopping. The most I have noticed is about 6 GB before I killed the command. Ffmpeg seems to be writing almost a gigabyte of data into memory a second. In fact, this slows down my computer when it occurs and threatens to completely fill up my memory.
When this occurs, there are no error messages (except for warnings about running out of memory) and the terminal running ffmpeg seems to not respond to any kill commands, and the only way to alleviate the situation is to force close the terminal window itself.
I’m wondering if somehow I am creating a memory leak issue or if I wrote something wrong or didn’t include something that would be necessary for live-streaming with ffmpeg.
-
When I use Fluent-Ffmpeg to access Ffmpeg, there are two different threads but I dont want it
25 mars 2019, par Ahmet Hakan BillurI try to broadcast with rtsp live stream from IP camera on web app that is improved with node.js-jsmpeg([a link]https://www.npmjs.com/package/fluent-ffmpeg !), web socket, html5(canvas).Everything ok that live streaming works but missing frame and high CPU usaged by streaming on web app and I try to reduce so I can intervene ffmpeg with fluent-ffmpeg but when I monitor CPU usaged I can see there 2 different threads following as and look at screenshot of CPU ;
ffmpeg -rtsp_trasport tcp -i rtsp ://10.6.0.225 -f mpeg1video - is worked by jsmpeg and canvas/html5
index.html
<div><canvas width="640" height="360"></canvas></div>
div><canvas width="640" height="360"></canvas>
<code class="echappe-js"><script type="text/javascript" src='http://stackoverflow.com/feeds/tag/jsLib/jsmpeg.js'></script><script type="text/javascript" src='http://stackoverflow.com/feeds/tag/jsLib/ffmpegUtil.js'></script>
<script type="text/javascript"><br />
var canvas = document.getElementById('videoCanvas');<br />
var ws = new WebSocket("ws://10.6.0.206:9999")<br />
var player = new jsmpeg(ws, {canvas:canvas, autoplay:true,audio:false,loop: true});<br />
</script>other one /usr/bin/ffmpeg -i rtsp ://10.6.0.225 -y out.ts is work by following piece of code in app.js
Stream = require('node-rtsp-stream');
stream = new Stream({
name: 'name',
streamUrl: 'rtsp://10.6.0.225',
wsPort: 9999
});
var ffmpeg = require('fluent-ffmpeg');
var proc = new ffmpeg();
proc
.addInput('rtsp://10.6.0.225')
.on('start', function(ffmpegCommand) {
/// log something maybe
console.log('start-->'+ffmpegCommand)
})
.on('progress', function(data) {
/// do stuff with progress data if you want
console.log('progress-->'+data)
})
.on('end', function() {
/// encoding is complete, so callback or move on at this point
console.log('end-->')
})
.on('error', function(error) {
/// error handling
console.log('error-->'+error)
})
.output('out.ts')
.run();and then I don’t want to get two different ffmpeg command threads in there.
Does anyone have an idea ?
Thanks in advice.