Recherche avancée

Médias (2)

Mot : - Tags -/media

Autres articles (99)

  • 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.

  • MediaSPIP v0.2

    21 juin 2013, par

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

  • Evolution #3560 (Nouveau) : Supprimer l’option expérimentale Google Closure Compiler

    1er octobre 2015, par b b

    Je viens donc de faire le test avec et sans : aucune différence !

    Référence : http://thread.gmane.org/gmane.comp.web.spip.user/194959/focus=66521

  • Can't access Google Cloud Platform hosted rtsp stream externally

    1er novembre 2023, par Nikos Daskalas

    I have been trying to host a video to rtsp stream on a gcp vm instance.

    


    My steps were :

    


    a) Set up an external ip to my vm, and setup firewall rules to allow traffick.

    


    b)Install mediamtx to my vm and start a server with ./mediamtx

    


    c)install ffmpeg and stream my video with : ffmpeg -i video.mp4 -rtsp_transport tcp -f rtsp rtsp ://externalip:8554/live.stream

    


    The stream runs locally, but when I try to access in with vlc or ffplay rtsp ://externalip:8554/live.stream, I cannot connect. I tried to ping the server from the client side, and it works ok.

    


    What am I missing ? Are there any more configurations I need to do to my project ?

    


  • What google cloud service can be used to process files stored in Firebase Cloud Storage with FFmpeg ? [closed]

    1er mai 2021, par uponly

    I am building a ReactJs app and I am trying to figure out a way to process files (images, videos, and audio of any type) that are stored in my Firebase storage bucket using FFmpeg. Currently, I have set up the functionality for allowing the user to upload files to my storage bucket, and a corresponding URL link is stored in a document in Firestore.

    


    Ideally, I'd love to do this with Cloud Functions HTTP triggers because I have all of that setup already. It would be nice to just call an HTTP trigger to process the file after it has been uploaded. However, after a bit of research, my current understanding is to somehow deploy my app using a flexible Google App Engine environment because apparently, it is the only way to set a manual timeout in case I have to process a long, high-quality video, for example. Thus I wouldn't be able to use Cloud Functions because there is a very short timeout period which may lead to the files not being fully processed.

    


    Here is the user flow I am trying to achieve, which may help make things more clear :

    


      

    1. [Done] The user uploads a file (image, audio, or video) to Firebase cloud storage. A URL is also stored in their corresponding user document in Firestore.
    2. 


    3. [Here and the steps onward are what I am trying to achieve] After the file has been stored, I'd like to kick off some sort of function that grabs the newly stored file and begin to process it in the cloud.
    4. 


    5. Store the newly processed file back into the Cloud Storage bucket
    6. 


    7. Allow the user to preview the processed file (by streaming it ideally, if possible).
    8. 


    


    In steps 2 and onward, I am just generally confused about what Google service I should be using to process my file in the cloud with FFmpeg. As well as how I can connect it to my React app, client-side. If I have to go the Google App Engine route, how do I go about connecting app engine to my React App such that I don't have to build my app and deploy it, as my app is still in development ?

    


    This is not a coding question so I apologize if this is the wrong place to post in. I am new to all this, any and all help is greatly appreciated. Thank you.