
Recherche avancée
Médias (3)
-
MediaSPIP Simple : futur thème graphique par défaut ?
26 septembre 2013, par
Mis à jour : Octobre 2013
Langue : français
Type : Video
-
GetID3 - Bloc informations de fichiers
9 avril 2013, par
Mis à jour : Mai 2013
Langue : français
Type : Image
-
GetID3 - Boutons supplémentaires
9 avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
Autres articles (112)
-
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...) -
Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs
12 avril 2011, parLa manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras.
Sur d’autres sites (7461)
-
Processing Frames of Screen Recording in Node Usin FFMPEG
28 septembre 2020, par The42ndTurtleI am trying to capture my screen using Node.JS and FFMPEG, and I have gotten as far as saving an flv file, but I am unable to process the frames real-time.


My code so far is


const ffmpeg = require('ffmpeg-static');
const {spawn} = require('child_process');
const {createWriteStream} = require('fs');

const canvas = document.querySelector('#canvas');
const ctx = canvas.getContext('2d');

const process = spawn(
 ffmpeg,
 ["-f", "gdigrab", "-framerate", "30", "-i", "desktop", '-crf', '0', '-preset', 'ultrafast', '-f', 'flv', '-'],
 { stdio: "pipe" }
);


const stream = process.stdout;

const file = createWriteStream('capture.flv');
stream.pipe(file);

stream.on('data', chunk => {
 const base64 = chunk.toString('base64');
 const data = `data:image/png;base64,${base64}`;

 const image = new Image();
 image.src = data;
 ctx.drawImage(image, 0, 0);
});




The output.flv file that is created is fine, but the image getting created in the stream does not seem to be a valid image. When I log the base64 and try just turning the single string into an image, it appears to be invalid image data. I want to use the stream to capture each frame of the stream.


-
ffmpeg/sox audio processing : Merging files with envelope changes
2 octobre 2020, par March HareSo I have two audio files. One is a music bed with an intro that segues into a looping music clip (let's call this *1). The second is the voice over audio track (referenced as *2, length n).


Audio *1 is fixed, while the voice over (*2) is downloaded about 3 times a day, and can vary in length. *1 is longer than we ever expect *2 to be.


What I need to do is


- 

- Alter the overall gain of *1 to -7.5 dB
- Begin merging VO *2 at time m, while reducing the volume envelope of *1 by -11 dB. This is fixed based on the length of the intro.
- Fade everything out to -∞ dB around the end of *2
- Trim off the silence at the end.
For reference, the total length of the final track should be m+n.










Unfortunately, I'm not versed enough with ffmpeg or sox to know exactly what I'm after here, and a lot of the examples tend to do one thing or another and aren't always clear when combining happens. I didn't get a lot of prior notice about this coming down the pipeline, so I'd like to get something relatively quick. We're able to do all of this stuff nicely in Adobe Audition (and I can do something similar in Audacity), but the idea is to automate it. For our envelope adjustments, we were just using linear ramps rather than smoothsteps, and that sounded fine.


The TLDR : The VO track *2 governs how long the file winds up being, while audio bed *1 needs to be ducked when *2 begins, and the whole thing faded out right when *2 ends.


We also have an automation system (radio station automation, specialized for something different than I need), so in a pinch if we have to just cut off the audio at the end of *2, we can get the fadeout from the radio automation system.


I've been using the information at this link to some effect (specifically the bit about ffmpeg volumes), but it still isn't dynamic enough for the situation.
Envelope pattern in SoX (Sound eXchange) or ffmpeg


Anyone have any advice on this one ? I've got Sox and ffmpeg available, and if need be I can probably install other tools as well.


-
avfilter/af_aiir : implement parallel processing
15 octobre 2020, par Paul B Mahol