Recherche avancée

Médias (91)

Autres articles (56)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

Sur d’autres sites (6846)

  • How can I use ffmpeg library with react on client side ? Any guide ? [closed]

    6 janvier 2023, par Mehdi Saqlen

    I have heard about web assembly. Web assembly allows us to use C++ libraries on browsers, so how can I use the FFmpeg library on the client-side with react.js ? If you know how to implement this please share with me what you know about this.

    


    Please share with me how can I learn FFmpeg completely with web assembly ?

    


  • Is it possible to stream the output of an ffmpeg command to a client with dot net core ?

    11 mars 2021, par Inondle

    I'm trying to take two videos and transform them with ffmpeg into a single video. It works great if you take the two videos, run them through ffmpeg and then serve that file up via an API. Unfortunately the upper range for these videos is 20 minutes, and this method takes too long to create the full video ( 30 seconds w/ ultrafast).

    


    I had an idea to stream the output of the ffmpeg command to the client which would eliminate the need to wait for ffmpeg to create the whole video. I've tried to proof this out myself and haven't had much success. It could be my inexperience with streams, or this could be impossible.

    


    Does anyone know if my idea to stream the in-progress output of ffmpeg is possible / feasible ?

    


  • Forwarding RTSP streams to client from private networked server via proxy

    21 juin 2016, par beNerd

    I have a setup where I have two physical machines (remote VPSes) :

    1. Server One - This has good processing power in terms of hardware and it’s IP can’t be accessed publicly. It’s private networked to a proxy (server 2) i.e it can only be accessed by the proxy server. Running nodejs/expressjs and ffmpeg/ffserver on ubuntu.

    2. Server Two : Reverse Proxy. Publicly accessible. Implements nginx which pipes the requests to Server One.

    Now, I have client apps that needs to play RTSP streams configured in the FFSERVER residing on Server One. Since I cannot access server one directly and only via proxy, I need a mechanism where I can accept RTSP requests on my nodejs api (which receives requests from nginx proxy via proxy pass config block), do some validations (session tokens here) and then when validated, contact the underlying ffserver asking for the stream. As soon as I receive the stream, I should be able to forward to the asking client.

    Possible ? How ?

Navigation