
Recherche avancée
Médias (2)
-
GetID3 - Bloc informations de fichiers
9 avril 2013, par
Mis à jour : Mai 2013
Langue : français
Type : Image
-
GetID3 - Boutons supplémentaires
9 avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
Autres articles (105)
-
List of compatible distributions
26 avril 2011, parThe table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...) -
MediaSPIP Core : La Configuration
9 novembre 2010, parMediaSPIP Core fournit par défaut trois pages différentes de configuration (ces pages utilisent le plugin de configuration CFG pour fonctionner) : une page spécifique à la configuration générale du squelettes ; une page spécifique à la configuration de la page d’accueil du site ; une page spécifique à la configuration des secteurs ;
Il fournit également une page supplémentaire qui n’apparait que lorsque certains plugins sont activés permettant de contrôler l’affichage et les fonctionnalités spécifiques (...) -
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 (14234)
-
FFMPEG : Add black frames at start and end of video
7 novembre 2014, par user3729198Im trying to add 10 second of black frames to the beginning of my clip and 30 seconds of black frames at end of clip. This is what I got so far.
ffmpeg -i XX.mp4 -vf "
color=c=black:s=720x576:d=10 [pre] ;
color=c=black:s=720x576:d=30 [post] ;
[pre] [in] [post] concat=n=3" -an -vcodec mpeg2video -pix_fmt yuv422p -s 720v576 -aspect 16:9 -r 25 -minrate 30000k -maxrate 30000k -b 30000k output.mpg
It works in some cases. But Only on specific material with right "SAR" values. But most of the time I get this error.
Input link in1:v0 parameters (size 720x576, SAR 35:24) do not match the corresponding output link in0:v0 parameters (720x576, SAR 1:1)
[Parsed_concat_2 @ 0x7f9853d048c0] Failed to configure output pad on Parsed_concat_2
Is there a way to complement my code or another way to do this ?
-
FFmpeg streaming stuck few minutes after start [closed]
19 février, par josue ramirezSorry for my english ! :D


I'm trying to make a live video stream from my webcam with ffmpeg using Node.


I get the images or frames from ffmpeg via pipe1 on the stdout event and send them via a socket-io client to my angular app to play the stream.


So far the stream starts fine and my angular app can play it fine, but after a certain time (8 minutes or so) ffmpeg stops sending data and the stream in my angular app stops and if I want to start the webcam again it's not possible anymore because it's apparently occupied by another process. I've been trying to figure out what's going on and what I've noticed is that the ffmpeg process just stops and the process is no longer visible with the
top
command (ubuntu), but the child process in node still shows a ffmpeg process as if it were a zombie process.

I've tried running ffmpeg from the terminal to save an mp4 file with the stream and in that case there is no problem, the recording doesn't stop even using pipe1. Only when I run ffmpeg from my Node app, the error occurs.


Does anyone have any idea what could be going on ?


This command is the one that is executed to send the data through pipe1 both from node and from the terminal but it only stops in Node


ffmpeg -f v4l2 -input_format mjpeg -video_size 800x600 -i /dev/video0 -q:v 4 -f image2pipe pipe1



The same thing happens when saving an mp4 video only in Node it fails


ffmpeg -f v4l2 -input_format mjpeg -video_size 800x600 -i /dev/video0 -q:v 4 video.mp4



This is my function that starts the streaming


export const startCamera = () => {
 logger.info('Starting camera ', cameraName);

 const inputFormat = process.platform === 'win32' ? 'dshow' : 'v4l2';

 const ffmpegArgs = [
 '-f', inputFormat, // Formato de entrada según la plataforma
 ];

 if (process.platform === 'linux') {
 ffmpegArgs.push(
 '-input_format', 'mjpeg', // Especificar el formato antes de video_size
 '-video_size', '800x600', // Tamaño de la imagen
 );
 }
 
 ffmpegArgs.push(
 '-i', cameraName, // Dispositivo de entrada
 '-vf', 'fps=15', // Fotogramas por segundo
 '-q:v', '10', // Calidad de video
 '-f', 'image2pipe', // Formato de salida
 'pipe:1' // Salida por stdout
 );

 try {
 logger.info('FFmpeg command: ffmpeg', ffmpegArgs.join(' '));
 ffmpeg = spawn('ffmpeg', ffmpegArgs);
 let cameraOpen = false;
 // Enviar los datos del fotograma a través del WebSocket
 ffmpeg.stdout.on('data', (chunk) => {
 logger.debug(`Sending chunk of ${chunk.length} bytes`);
 if (!cameraOpen) {
 cameraOpen = true;
 serialConnection.connect();
 logger.info('Camera started!!');
 }

 if (streamWS.isActive()) {
 streamWS.send(chunk);
 }
 });
 // Manejo de errores
 ffmpeg.stderr.on('error', (data) => {
 logger.error('FFmpeg Error:', data.toString());
 });

 ffmpeg.on('close', async () => {
 logger.info('Camera closed....', cameraName);
 if (!cameraOpen) {
 await commandWS.send(
 {
 command: COMMANDS.START_STREAM,
 isError: true,
 response: `Error al intentar iniciar la camara ${cameraName}, verificar que la camara se encuentre bien conectada.`,
 },
 COMMANDS_EVENTS.ROBOT_RESPONSE
 );
 }
 cameraOpen = false;
 await serialConnection.close();
 stopCamera();
 await streamWS.disconnectWS();
 });
 } catch (e) {
 logger.error('Error tryng to start the camera...', e);
 }
};



-
FFMpeg generated m3u8 segmented videos takes forever to start playing
20 novembre 2014, par Michael GaylordI am using ffmpeg to generate a segmented list of files in order to stream them to an iOS app. The list of files is generated fine but when it comes time to play them, the video needs to be downloaded in its entirety before playback starts. This behaviour seems to be the case on iOS, Safari and VLC.
Does anybody know why this is happening and how I can improve the performance of playback ? I have complete control over how the files are recorded in iOS, as well as how they are processed. Here is a sample stream :
http://www.bytesizecreations.com/storie-test/hls.m3u8
Here are my ffmpeg commands to generate the segments from the file :
ffmpeg -i joined.ts -flags -global_header -vcodec copy -acodec copy -map 0 -f segment -segment_time 2 -segment_list hls.m3u8 -segment_list_size 999999 -segment_format mpegts out%03d.ts
Here is the output of ffprobe on the file :
libavutil 54. 7.100 / 54. 7.100
libavcodec 56. 1.100 / 56. 1.100
libavformat 56. 4.101 / 56. 4.101
libavdevice 56. 0.100 / 56. 0.100
libavfilter 5. 1.100 / 5. 1.100
libavresample 2. 1. 0 / 2. 1. 0
libswscale 3. 0.100 / 3. 0.100
libswresample 1. 1.100 / 1. 1.100
libpostproc 53. 0.100 / 53. 0.100
Input #0, mpegts, from 'joined.ts':
Duration: 00:00:07.96, start: 1.441667, bitrate: 3899 kb/s
Program 1
Metadata:
service_name : Service01
service_provider: FFmpeg
Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 1280x720, 24 fps, 24 tbr, 90k tbn, 180k tbc
Stream #0:1[0x101](und): Audio: aac ([15][0][0][0] / 0x000F), 44100 Hz, stereo, fltp, 222 kb/s