Recherche avancée
Autres articles (50)
-
Les formats acceptés
28 janvier 2010, parLes commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
ffmpeg -codecs ffmpeg -formats
Les format videos acceptés en entrée
Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
Les formats vidéos de sortie possibles
Dans un premier temps on (...) -
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
Utilisation et configuration du script
19 janvier 2011, parInformations spécifiques à la distribution Debian
Si vous utilisez cette distribution, vous devrez activer les dépôts "debian-multimedia" comme expliqué ici :
Depuis la version 0.3.1 du script, le dépôt peut être automatiquement activé à la suite d’une question.
Récupération du script
Le script d’installation peut être récupéré de deux manières différentes.
Via svn en utilisant la commande pour récupérer le code source à jour :
svn co (...)
Sur d’autres sites (5820)
-
How to load test FFMPEG streams to NGINX RTMP server without Server error : Already publishing ?
23 novembre 2022, par NavMy objective is to have an EC2 server running NGINX with RTMP module, and another EC2 server running multiple FFMPEG processes in the background, which stream a video to the first EC2 server. The video is stored on the second EC2 server. The idea is to measure the amount of CPU and RAM consumed and to see if the streaming fails at any point due to the server being overloaded. This would help identify the load a server can support, and help decide how many servers are required when handling
nnumber of simultaneous users.

This is the script I tried using :


#!/usr/bin/env bash
for i in {1..10}; do
 ffmpeg -nostdin -re -i myVideo.mp4 -c:v copy -c:a aac -ar 44100 -ac 1 -f flv rtmp://<first server="server" ipv4="ipv4" address="address">/mystream &
done;
</first>

When running the script, I get this error :


Stream mapping:
 Stream #0:0 -> #0:0 (copy)
 Stream #0:1 -> #0:1 (aac (native) -> aac (native))
[rtmp @ 0x55a0c3a4bc0] Server error: Already publishing
rtmp://<ip address="address">/mystream: Operation not permitted
[rtmp @ 0x55d9d5bc0c0] Server error: Already publishing
rtmp://<ip address="address">/mystream: Operation not permitted
Stream mapping:
 Stream #0:0 -> #0:0 (copy)
 Stream #0:1 -> #0:1 (aac (native) -> aac (native))
Stream mapping:
 Stream #0:0 -> #0:0 (copy)
 Stream #0:1 -> #0:1 (aac (native) -> aac (native))
Stream mapping:
[rtmp @ 0x55779e9bc0] [rtmp @ 0x55dd17e1bc0] Server error: Already publishing
Server error: Already publishing
rtmp://<ip address="address">/mystream: Operation not permitted
rtmp://<ip address="address">/mystream: Operation not permitted
 Stream #0:0 -> #0:0 (copy)
 Stream #0:1 -> #0:1 (aac (native) -> aac (native))
[rtmp @ 0x55c06b6dbc0] Server error: Already publishing
rtmp://<ip address="address">/mystream: Operation not permitted
[rtmp @ 0x56210db9bc0] Server error: Already publishing
rtmp://<ip address="address">/mystream: Operation not permitted
</ip></ip></ip></ip></ip></ip>

Should I use different ports for each FFMPEG streaming command ? So I'd have to enable a range of ports on the EC2 instance and specify a different port in the URL of the FFMPEG RTMP command and also allow multiple ports in NGINX-RTMP config ? Does anyone know a good way to do load testing for RTMP without errors ? How would I know if the server is unable to handle the load ? Would packets start dropping ? How would it be measured ? It's not necessary to use FFMPEG. Anything is fine, but tools like Apache Bench don't seem to be for RTMP.


-
Anomalie #3386 : Spip derrière Varnish : port non-standard dans l’URL ?
26 octobre 2016, par Yohann PrigentNe faut-il pas utiliser la fonction getallheaders() pour récupérer ces entêtes, même en cas d’un Reverse Proxy Apache ?
-
Install FFMPEG on WAMP
15 septembre 2023, par nico55555I've probably spent over 12 hours trying to install FFMPEG on WAMP. I'm aware that other people have had this question answered on this site, however it does not work for my setup.



I have tried the below :



Download ffmpeg_new
Copy php_ffmpeg.dll from the php5 folder to the C:\wamp\bin\php\php5.2.9-2\ext
Copy files from common to the windows/system32 folder
Add extension=php_ffmpeg.dll to php.ini file
Restarted all services (Apache, PHP...)



My current setup is PHP 5.2.1, Apache 2.0.63. I have a Windows 7 64bit computer.



I get the following error in my PHP error log :



[22-Jun-2012 01:39:31] PHP Warning : PHP Startup : Unable to load dynamic library 'c :/wamp/bin/php/php5.2.1/ext/php_ffmpeg.dll' - The specified module could not be found.
 in Unknown on line 0



Obviously I have placed the module in the ext folder.



Phpinfo.php verifies that the FFMPEG module is not being loaded. I have tried installing PHP 5.3 (with a later FFMPEG version), 5.2.6 and 5.2.9-2, but the module still fails to load. Is there anything else I should try ? Does having a 64bit Windows 7 computer make any difference ?


Syndiquer tout le site
