
Recherche avancée
Médias (1)
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
Autres articles (79)
-
Organiser par catégorie
17 mai 2013, parDans MédiaSPIP, une rubrique a 2 noms : catégorie et rubrique.
Les différents documents stockés dans MédiaSPIP peuvent être rangés dans différentes catégories. On peut créer une catégorie en cliquant sur "publier une catégorie" dans le menu publier en haut à droite ( après authentification ). Une catégorie peut être rangée dans une autre catégorie aussi ce qui fait qu’on peut construire une arborescence de catégories.
Lors de la publication prochaine d’un document, la nouvelle catégorie créée sera proposée (...) -
Récupération d’informations sur le site maître à l’installation d’une instance
26 novembre 2010, parUtilité
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 (...) -
Demande de création d’un canal
12 mars 2010, parEn fonction de la configuration de la plateforme, l’utilisateur peu avoir à sa disposition deux méthodes différentes de demande de création de canal. La première est au moment de son inscription, la seconde, après son inscription en remplissant un formulaire de demande.
Les deux manières demandent les mêmes choses fonctionnent à peu près de la même manière, le futur utilisateur doit remplir une série de champ de formulaire permettant tout d’abord aux administrateurs d’avoir des informations quant à (...)
Sur d’autres sites (4304)
-
What google cloud service can be used to process files stored in Firebase Cloud Storage with FFmpeg ? [closed]
1er mai 2021, par uponlyI 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 :


- 

- [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.
- [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.
- Store the newly processed file back into the Cloud Storage bucket
- Allow the user to preview the processed file (by streaming it ideally, if possible).










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.


-
How I can load testing my web application if I host it in Azure and Google Cloud
29 décembre 2018, par Anirudha GuptaI am trying to stream the video on Youtube using FFmpeg. Earlier I have a preset which is used to stream at lower resolution.
Now I want to send the video as it is. I am trying to use this code
./ffmpeg -re -i "C:\Users\Anirudha\Desktop\abc.mp4" -codec copy -f flv "rtmp://a.rtmp.youtube.com/live2/mykey1"
I got this code from here https://www.wowza.com/docs/how-to-configure-security-using-wowza-streaming-engine-manager
This code is working fine for Wowza but it’s shown running on youtube (in the command line) in Actual it’s not doing anything on the youtube website.
Is there any way to send the file to youtube the file as it is, What I am looking for is I don’t want to do anything on file. Let the resolution same as it is.
-
Why ffmpeg launched on a google cloud function can throw "Error : Output stream error : Maximum call stack size exceeded" ?
15 décembre 2020, par Stepan ShilinI'm trying to process video files with ffmpeg running on google cloud functions. Video files are downloaded from a google file storage, processed in stream by fluent-ffmpeg and streamed to a new google storage file. It works on smaller files but throws an "Output stream error : Maximum call stack size exceeded" on larger files.



I tried running the code on a normal pc, and I haven't encountered this error, even with larger files.



These are the parameters I deploy the function with



gcloud functions deploy $FUNCTION_NAME --runtime nodejs8 --trigger-http --timeout=180 --memory 256




This is the code that processes video



function cutVideo({videoUrl, startTime, duration, dist}) {
 return ffmpeg(videoUrl)
 .outputOptions('-movflags frag_keyframe+empty_moov')
 .videoCodec('copy')
 .audioCodec('copy')
 .format('mp4')
 .setStartTime(startTime)
 .setDuration(duration);
}

const sectionStream = cutVideo({
 videoUrl,
 startTime,
 duration,
 dist: tempFilePath,
});

const outputStream = bucket.file(sectionPath)
.createWriteStream({
 metadata: {
 contentType: config.contentType,
 },
 public: true,
});




Actual error stack looks like this



Error: Output stream error: Maximum call stack size exceeded
 at Pumpify.<anonymous> (/srv/node_modules/fluent-ffmpeg/lib/processor.js:498:34)
 at emitOne (events.js:121:20)
 at Pumpify.emit (events.js:211:7)
 at Pumpify.Duplexify._destroy (/srv/node_modules/duplexify/index.js:191:15)
 at /srv/node_modules/duplexify/index.js:182:10
 at _combinedTickCallback (internal/process/next_tick.js:132:7)
 at process._tickDomainCallback (internal/process/next_tick.js:219:9)
 RangeError: Maximum call stack size exceeded
 at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:28:31)
 at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:37:30)
 at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:37:30)
 at value.map.v (/srv/node_modules/@google-cloud/projectify/build/src/index.js:30:32)
 at Array.map (<anonymous>)
 at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:30:23)
 at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:37:30)
 at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:37:30)
 at value.map.v (/srv/node_modules/@google-cloud/projectify/build/src/index.js:30:32)
 at Array.map (<anonymous>)
</anonymous></anonymous></anonymous>



What could cause this error on a google cloud function ?