
Recherche avancée
Médias (91)
-
Spitfire Parade - Crisis
15 mai 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Audio
-
Wired NextMusic
14 mai 2011, par
Mis à jour : Février 2012
Langue : English
Type : Video
-
Video d’abeille en portrait
14 mai 2011, par
Mis à jour : Février 2012
Langue : français
Type : Video
-
Sintel MP4 Surround 5.1 Full
13 mai 2011, par
Mis à jour : Février 2012
Langue : English
Type : Video
-
Carte de Schillerkiez
13 mai 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Texte
-
Publier une image simplement
13 avril 2011, par ,
Mis à jour : Février 2012
Langue : français
Type : Video
Autres articles (61)
-
Gestion des droits de création et d’édition des objets
8 février 2011, parPar défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;
-
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
-
Dépôt de média et thèmes par FTP
31 mai 2013, parL’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)
Sur d’autres sites (7312)
-
make webbased ffmpeg-live transcoder on linux for multiple streams
11 juillet 2017, par Dlniya DlzarHi I am planning to make webbased ffmpeg-live transcoder on linux for multiple streams .
Using ffmpeg and ngnix-rtmp is the basic that i found and planning to do it
my plan is (Web interface for adding and modifying streams (name ,input,output..)
in database , database i mean (json file). and execute ffmpeg command depend on the JSON file (now one more thing i want to do , is to monitor streams based on
nginx-rtmp-module/stat.xsl
git https://github.com/arut/nginx-rtmp-module/blob/master/stat.xsl
and restart streams if there is problem , like no audio or picture
whats is best structure to do it ?? which language is good to do the proccess
is there any missing knowledges ?? is there any other better way in your mind ?? -
Correcting the variable name in an ffmpeg subtitle script
21 juin 2017, par Steven FoongI have 175 mp4 video files and subtitle files with the extension .ass. Unfortunately, my smart TV is not able to read those subtitles. I plan to burn (hardcode) the subtitles into the video.
I use this command :
ffmpeg -i orgvideo.mp4 -vf subtitles="subtitle.ass" newvideo.mp4 <br />
It works. So I plan to use a
bash
script to automate the process.Everything in the script is working but the
ffmpeg
command line isn’t able to retrieve the subtitle variable.After googling around, I found that my file name has special character and space, that causes my script to fail. If the video file name and the subtitle file is simple, then the script should be no problem.
This is my script :
for f in *.mp4
do
new="${f%%.mp4} (CHT).mp4"
subtitle="${f%%.mp4}.chi.ass"
< /dev/null ffmpeg -i "$f" -vf subtitles="$subtitle" "$new"
doneThe
ffmpeg
line is having problems reading the subtitle file variable. Can anyone help ? -
Cloud Functions for Firebase : completing long processes without touching maximum timeout
17 février, par Scott EwingI have to transcode videos from webm to mp4 when they're uploaded to firebase storage. I have a code demo here that works, but if the uploaded video is too large, firebase functions will time out on me before the conversion is finished. I know it's possible to increase the timeout limit for the function, but that seems messy, since I can't ever confirm the process will take less time than the timeout limit.



Is there some way to stop firebase from timing out without just increasing the maximum timeout limit ?



If not, is there a way to complete time consuming processes (like video conversion) while still having each process start using firebase function triggers ?



If even completing time consuming processes using firebase functions isn't something that really exists, is there some way to speed up the conversion of fluent-ffmpeg without touching the quality that much ? (I realize this part is a lot to ask. I plan on lowering the quality if I absolutely have to, as the reason webms are being converted to mp4 is for IOS devices)



For reference, here's the main portion of the demo I mentioned. As I said before, the full code can be seen here, but this section of the code copied over is the part that creates the Promise that makes sure the transcoding finishes. The full code is only 70 something lines, so it should be relatively easy to go through if needed.



const functions = require('firebase-functions');
const mkdirp = require('mkdirp-promise');
const gcs = require('@google-cloud/storage')();
const Promise = require('bluebird');
const ffmpeg = require('fluent-ffmpeg');
const ffmpeg_static = require('ffmpeg-static');




(There's a bunch of text parsing code here, followed by this next chunk of code inside an onChange event)



function promisifyCommand (command) {
 return new Promise( (cb) => {
 command
 .on( 'end', () => { cb(null) } )
 .on( 'error', (error) => { cb(error) } )
 .run();
 })
}
return mkdirp(tempLocalDir).then(() => {
 console.log('Directory Created')
 //Download item from bucket
 const bucket = gcs.bucket(object.bucket);
 return bucket.file(filePath).download({destination: tempLocalFile}).then(() => {
 console.log('file downloaded to convert. Location:', tempLocalFile)
 cmd = ffmpeg({source:tempLocalFile})
 .setFfmpegPath(ffmpeg_static.path)
 .inputFormat(fileExtension)
 .output(tempLocalMP4File)
 cmd = promisifyCommand(cmd)
 return cmd.then(() => {
 //Getting here takes forever, because video transcoding takes forever!
 console.log('mp4 created at ', tempLocalMP4File)
 return bucket.upload(tempLocalMP4File, {
 destination: MP4FilePath
 }).then(() => {
 console.log('mp4 uploaded at', filePath);
 });
 })
 });
 });