Recherche avancée

Médias (1)

Mot : - Tags -/net art

Autres articles (94)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 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 (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

Sur d’autres sites (3766)

  • FFMPEG re-broadcast/proxy MJPEG stream

    10 septembre 2022, par Ollie Pugh

    I have an MJPEG stream coming from an RPI on my home network and have an NGINX acting as a proxy on an EC2.

    


    For the camera access the flow of stream to the user is the following

    


    RPi -> mjpeg-proxy (running on EC2) -> NGINX (running on same EC2) -> user

    


    the point of mjpeg-proxy is to reduce the load on the RPi and only have one stream to the Pi and allow the EC2 to distribute that one stream.

    


    Now this work fine-ish from my PC (on same network as Pi) the streams work perfectly. But when it comes to my phone on roaming data, the stream is super choppy and the latency grows massively (this project needs minimal latency, like sub 300ms).

    


    I can't understand why this would happen ? Because even when running of my local PC its going through the Proxy hosted in the cloud, so its not as if its an advantage to it being local ?

    


    the stream is fine on another device, e.g. my laptop, but thats on the same network as the RPi. But like I said, it shouldn't makea difference as its going through a proxy !

    


    I was wondering if using FFMPEG to re-stream the mjpeg stream would be beneficial as node is notoriously slow. But I don't really want to be writing my own mjpeg-proxy in C++ to speed this all up.

    


    I have looked online for answers to FFMPEG MJPEG proxy and have been very unsuccesful

    


  • doc/default.css + doc/t2h.init : New styles

    24 septembre 2013, par Timothy Gu
    doc/default.css + doc/t2h.init : New styles

    The main motive of this commit is to make the offline copy of the HTML doc as
    
pretty as the online (ffmpeg.org) one. This also introduced new styles for
    
<h2> to <h4>.
    

    Signed-off-by : Timothy Gu <timothygu99@gmail.com>
    
Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
    • [DH] doc/default.css
    • [DH] doc/t2h.init

  • FFmpeg : building example C codes

    23 février 2021, par J. S.

    I have configured and compiled the FFmpeg library using this link :&#xA;https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu

    &#xA;&#xA;

    Now, I am trying to build example C codes provided by FFmpeg from here :&#xA;https://github.com/FFmpeg/FFmpeg/tree/master/doc/examples

    &#xA;&#xA;

    However, when I run make install-examples or make install (suggested by /example/README), I receive this kind of message :

    &#xA;&#xA;

    &#xA;

    make : *** No rule to make target '/doc/examples/README', needed by&#xA; 'install-examples'. Stop.

    &#xA;

    &#xA;&#xA;

    I thought this may be due to the rules not being in the correct MakeFile format (I am not sure why they refers to README). How should I go about in fixing this and compiling the example codes ? I have tried to find solutions about this, but there doesn't seem to be much information online.

    &#xA;&#xA;

    Thank you.

    &#xA;

Navigation