Recherche avancée
Médias (3)
-
The Slip - Artworks
26 septembre 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Texte
-
Podcasting Legal guide
16 mai 2011, par
Mis à jour : Mai 2011
Langue : English
Type : Texte
-
Creativecommons informational flyer
16 mai 2011, par
Mis à jour : Juillet 2013
Langue : English
Type : Texte
Autres articles (73)
-
Personnaliser les catégories
21 juin 2013, parFormulaire de création d’une catégorie
Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
On peut modifier ce formulaire dans la partie :
Administration > Configuration des masques de formulaire.
Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...) -
Configurer la prise en compte des langues
15 novembre 2010, parAccéder à la configuration et ajouter des langues prises en compte
Afin de configurer la prise en compte de nouvelles langues, il est nécessaire de se rendre dans la partie "Administrer" du site.
De là, dans le menu de navigation, vous pouvez accéder à une partie "Gestion des langues" permettant d’activer la prise en compte de nouvelles langues.
Chaque nouvelle langue ajoutée reste désactivable tant qu’aucun objet n’est créé dans cette langue. Dans ce cas, elle devient grisée dans la configuration et (...) -
Le profil des utilisateurs
12 avril 2011, parChaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)
Sur d’autres sites (8437)
-
Transcode GCS files using ffmpeg
12 août 2020, par hudsonhooperMy ultimate goal is to transcode video files uploaded to one GCS bucket, transcode them for HLS using App Engine, then store them in another bucket for streaming. I started with code someone else made which closely fit my use case. Right now I just have it set up to save the files as mp4 to see if it works and I receive no error messages and is logs 'Success' to the console but when I check GCS the output file it has created is only around a kb (basically its just the metadata). I believe the issue has to do with the
.pipe(remoteWriteStream, { end: true });line and something with ffmpeg because if I instead run the lineoriginStream.pipe(remoteWriteStream, {end: true});to test the.pipefunctionality I get what I'd expect (a copy of the file of the correct size). I've seen a lot of other people such as here use essentially the same method just with cloud functions and have success. Any idea where I went wrong ?


import { Storage } from '@google-cloud/storage';

import ffmpegInstaller from '@ffmpeg-installer/ffmpeg';
import ffmpeg from 'fluent-ffmpeg';

ffmpeg.setFfmpegPath(ffmpegInstaller.path);

export default async function transcode(
 //My try
 name: String,
 bucket: String,
 suffix: String,
 size: String,

): Promise<void> {
 return new Promise((resolve, reject) => {
 const storage = new Storage();

 const originBucket = storage.bucket(bucket);
 const destinationBucket = storage.bucket('storieshls-2e4b1');

 const originFile = originBucket.file(name);
 const originStream = originFile.createReadStream();

 const remoteWriteStream = destinationBucket.file(name.replace(".MOV", ".mp4")).createWriteStream({
 metadata: {
 contentType: 'video/mp4', // This could be whatever else you are transcoding to
 },
 });

 //originStream.pipe(remoteWriteStream, {end: true});

 ffmpeg()
 .input(originStream)
 .outputOptions('-c:v copy') // Change these options to whatever suits your needs
 .outputOptions('-c:a aac')
 .outputOptions('-b:a 160k')
 .outputOptions('-f mp4')
 .outputOptions('-preset fast')
 .outputOptions('-movflags frag_keyframe+empty_moov')
 .on('start', cmdLine => {
 console.log(`[${suffix}] Started FFMpeg`, cmdLine);
 })
 .on('end', () => {
 console.log(`[${suffix}] Success!.`);
 resolve();
 })
 .on('error', (err: Error, stdout, stderr) => {
 console.log(`[${suffix}] Error:`, err.message);
 console.error('stdout:', stdout);
 console.error('stderr:', stderr);

 reject();
 })
 .pipe(remoteWriteStream, { end: true });
 });
}
</void>

-
How to add a watermark to video on firebase storage using ffmpeg
31 décembre 2020, par awabsI am trying to add a watermark to a video using firebase functions and ffmpeg, but I do know the right code for it. I know is that ffmpen is now available in google cloud env so this approach should work.
Any help is appreciated.


const functions = require('firebase-functions');
const { Storage } = require('@google-cloud/storage');
const projectId = 'video-demo-a57fa';
let gcs = new Storage ({
 projectId
});
const os =require('os');
const path =require('path');
const spawn = require('child-process-promise').spawn;


exports.addLogo = functions.storage.object().onFinalize(event =>{
 
 const bucket =event.bucket;
 const contentType =event.contentType;
 const filePath =event.name;
 console.log(path.dirname(filePath));

 console.log('File change detected, function execution started');


 if (path.basename(filePath).startsWith('resized-')) {
 console.log('We already renamed that file!');
 return;
 }

 const destBucket = gcs.bucket(bucket);
 const tmpFilePath = path.join(os.tmpdir(), path.basename(filePath));
 const metadata = { contentType: contentType };
 return destBucket.file(filePath).download({
 destination: tmpFilePath
 }).then(()=>{
 return spawn('ffmpeg',['-i', 'video.mp4'], tmpFilePath )
 }).then(() => {
 console.log(tmpFilePath);
 return destBucket.upload(tmpFilePath, {
 destination: path.dirname(filePath)+'/resized-' + path.basename(filePath),
 metadata: metadata
 
 })
 }).catch(err=>{
 console.log(err);
 });
})


-
Creating GIF with FFMPEG in AWS Lambda creates an empty gif ?
29 décembre 2020, par blablubla12I'm trying to create a gif using an existing command (which I have no idea what it's doing as I don't really understand ffmpeg). That command worked perfectly on a C# Console App (as a string), however once I migrated to AWS Lambda (Node.js 12.x - which I'm also new at) it uploads an empty gif (0 B). Here is a part of the code :


const bucket = eventObject.BucketName;
const srcKey = eventObject.ObjectKey;
const target = s3.getSignedUrl('getObject', { Bucket: bucket, Key: srcKey, Expires: 1000 });
const overlayTarget = s3.getSignedUrl('getObject', { Bucket: bucket, Key: 'overlays/overlay.png', Expires: 1000 });
const fileName = guid + "_gif.gif";
const tempPath = '/tmp/' + fileName;

function CreateGif() {
 return new Promise((resolve, reject) => {

 const ffmpeg = spawn(ffmpegPath, [
 "-ss",
 eventObject.GifTimecode,
 "-i",
 target,
 "-i",
 overlayTarget,
 "-filter_complex",
 `[0:v] trim = duration = ${eventObject.GifDuration}, setpts = PTS - STARTPTS, scale = 450:-1[trimmed]; [trimmed] split[trimmed1][trimmed2]; [trimmed2] reverse[rev]; [trimmed1] [rev] concat=n=2:v=1:a=0 [v]; [v] [1:v] overlay=0:0:format=rgb[overlayed]; [overlayed] split[a][b]; [a] palettegen=stats_mode=diff[palette]; [b] [palette] paletteuse=bayer:bayer_scale=3.5[out] `,
 "-map",
 '[out]',
 tempPath
 ]);

 ffmpeg.stderr.setEncoding('utf8');
 ffmpeg.stderr.on('data', (data) => {
 console.log(data);
 });

 ffmpeg.on('close', function (code) {
 console.log('closed');
 resolve();
 });

 ffmpeg.on('error', function (err) {
 console.log(err);
 reject();
 throw new Error(err);
 });
 });
}

function uploadToS3() {
 return new Promise((resolve, reject) => {
 let tmpFile = createReadStream(tempPath);

 var params = {
 Bucket: bucket,
 Key: 'gifs/' + fileName,
 Body: tmpFile,
 ContentType: `image/gif`
 };

 s3.upload(params, function (err, data) {
 if (err) {
 console.log(err);
 reject();
 }
 console.log(`successful upload to ${bucket}/${fileName}`);
 resolve();
 });
 });
}

await CreateGif();
await uploadToS3();


I'm sure the issue is the args that are being passed, however I've not found a way to separate the args in the array in a way that works.


Here's the same command in C# (this one works fine) :


var command = "-ss " + timeCode + " -i "
 + "\"" + videoPath + "\""
 + " -i "
 + "\"" + path + "/" + imageOverlayFilePath + "\" "
 + " -filter_complex "
 + "\""
 + $"[0:v] trim = duration = {gifDuration}, setpts = PTS - STARTPTS, scale = 450:-1[trimmed]; [trimmed] split[trimmed1][trimmed2]; [trimmed2] reverse[rev]; [trimmed1] [rev] concat=n=2:v=1:a=0 [v]; [v] [1:v] overlay=0:0:format=rgb[overlayed]; [overlayed] split[a][b]; [a] palettegen=stats_mode=diff[palette]; [b] [palette] paletteuse=bayer:bayer_scale=3.5[out] "
 + "\""
 + " -map [out] "
 + "\"" + output + "\"";


How do I separate the command string in the args array
spawn(ffmpegPath, [])

Syndiquer tout le site
