
Recherche avancée
Autres articles (80)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, 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 (...) -
Amélioration de la version de base
13 septembre 2013Jolie sélection multiple
Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)
Sur d’autres sites (9867)
-
ffmpeg and Red5 Issue : Increase in number of ffmpeg simultaneous streams to Red5 resulting in packet loss
30 octobre 2014, par kajarigdI have a screen sharing app written in flex, using which one person can share his screen with another person via Red5 server (Version : 1.0.3). Platform is Windows Server 2008. Now, I want to load test this Red 5 server to find out maximum how many simultaneous screen sharing session it can allow, without any quality compromise. By quality I mean, speed of transmission and no data loss during transmission. I simulated the load using ffmpeg command.
For this, instead of transmitting a live captured screen, I am transmitting (uploading) a FLV file stored in my local to the Red5 server using ffmpeg command. In the receiving client side, I am starting to download (transmitting) this same FLV file after 5 secs since the upload has started. This is working fine when I am running this test for less than 10 pairs of upstreaming-downstreaming sessions. But, when the number is increasing beyond 10, I am observing significant packet loss in transmission.
Here are the commands I am running in a loop. The loop count is the number of streaming pairs.
- upstreaming :
ffmpeg -re -i -f flv -ar 22050 "rtmp://" -report
- downstreaming :
ffmpeg -re -i "rtmp:// live=1" -report
The and are set in such a way, that in the downstream I will download the same uploaded file. "rtmp ://" are the same in both the cases. I am not doing the upstream in record mode, hence, no physical file is getting saved in the server side. When I am analyzing the file I received in the receiving client side, it is a poor quality video due to frame loss. Uploading and downloading machines are two different machines. I ran the test for many hours, repeating the same 10 simultaneous streaming sets. Each set is consistently giving the same results.
What is puzzling me is, this is working fine without any packet loss for less that 10 simultaneous streaming. I searched about it in various forums, but none of the answers were applicable for this scenario. For a while I was thinking that Red5 has limited capacity, but I found many posts saying Red5 can easily scale up to take very big load. Does that mean, the problem is in my configuration ? I am not sure which are to focus on.
An example log snippet :
Lots of missing data at downstream side. For e.g. between frames 101 and 102 there is a difference of 25 sec. On replaying the video there is a stoppage for this much time.In this time gap all the frames are lost.
frame= 101 fps=1.0 q=14.5 size= 2650kB time=00:01:41.00 bitrate= 214.9kbits/s
frame= 102 fps=1.0 q=13.2 size= 2763kB time=00:02:06.00 bitrate= 179.6kbits/sAny help is appreciated !
- upstreaming :
-
A Beginner’s Guide to Omnichannel Analytics
14 avril 2024, par Erin -
How to Implement Cross-Channel Analytics : A Guide for Marketers
17 avril 2024, par Erin