Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP 0.2

Autres articles (72)

  • Récupération d’informations sur le site maître à l’installation d’une instance

    26 novembre 2010, par

    Utilité
    Sur le site principal, une instance de mutualisation est définie par plusieurs choses : Les données dans la table spip_mutus ; Son logo ; Son auteur principal (id_admin dans la table spip_mutus correspondant à un id_auteur de la table spip_auteurs)qui sera le seul à pouvoir créer définitivement l’instance de mutualisation ;
    Il peut donc être tout à fait judicieux de vouloir récupérer certaines de ces informations afin de compléter l’installation d’une instance pour, par exemple : récupérer le (...)

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

  • 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 (5154)

  • flv demuxer supports live rtmp inputs but there is no any info about it in the docs.

    24 décembre 2016, par Bela Bodecs
    flv demuxer supports live rtmp inputs but there is no any info about it in the docs.

    Signed-off-by : Bela Bodecs <bodecsb@vivanet.hu>
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] doc/demuxers.texi

  • doc/encoders : partially rewrite and reformat libx264 docs

    23 juillet 2013, par Timothy Gu
    doc/encoders : partially rewrite and reformat libx264 docs

    Format is based on the thread :
    
"[PATCH] doc/encoders : Add libopus encoder doc" (06-28-2013)
    
http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/165368/
    

    Also merge the two option sections (Mapping and Private options).
    

    Patch partially edited by Stefano Sabatini.
    

    Signed-off-by : Stefano Sabatini <stefasab@gmail.com>
    • [DH] doc/encoders.texi

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

    &#xA;

    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.

    &#xA;

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

    &#xA;

      &#xA;
    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. &#xA;

    2. [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.

      3. &#xA;

    3. Store the newly processed file back into the Cloud Storage bucket

      4. &#xA;

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

      5. &#xA;

    &#xA;

    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 ?

    &#xA;

    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.

    &#xA;

Navigation