
Recherche avancée
Autres articles (56)
-
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users. -
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
-
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs
Sur d’autres sites (8526)
-
Extend + scale a portrait video so the aspect ratio stays and the black borders become a blurry version of the video
24 avril 2017, par P. DeeI have a 720 x 1280 pixels video. How do I extend and scale it to 1920 x 1080 such that the aspect ratio is being kept and the black borders are a blurry version of the video, so you don’t really notice that it’s just a small vertical stripe.
Example
I started with
ffmpeg -i video720x1280.mp4 -vf "scale=608:1080,pad=width=1920:height=1080:x=656:y=0:color=black" video1920x1080.mp4
-
Lossless codec for bayer data
21 août 2016, par vhdirkI’m working with lots of camera’s which capture in BG bayer pattern natively.
Now, every time I record some data, I save it to the disk in the raw bayer pattern, in an avi container. The problem is, that this really adds up after a while. After one year of research, I have close to 4TB of data...
So I’m looking for a lossless codec to compress this data. I know I could use libx264 (with —qp 0), or huffYUV, dirac or jpeg2000, but they all assume you have RGB or YUV data. It’s easy enough to convert the bayered data to RGB, and then compress it, but it kind of defeats the purpose of compression if you first triple the data. This would also mean that the demoasicing artefacts introduced by debayering would also be in my source data, which is also not too great. It would be nice to have a codec that can work on the bayered data directly.
Even more nice would be that the solution would involve a codec that is already supported by gstreamer (or ffmpeg), since that’s what I am already using.
-
fluent-ffmpeg is having trouble setting creation_time (metadata) for mp4 video
26 février 2023, par LycalopXSo, basically, I have 2000 photos/videos that are, incorrectly, saved with random creation dates, and I wish to try and organize them. And, the solution I found was : getting the correct time through their name (they are already all named correctly), in the following format :


YYMMDD HH:MM:SS


That way, as I didn't want to go one by one writing all of the correct timestamps, I tried to change the metadata for all the files using javascript, and chose Fluent-FFMPeg for the job. I have ffmpeg installed on my computer, and I can successfully change the date of an MP4 file using the following command, in Windows Powershell (for that mp4 video) :


ffmpeg -i 20150408_143303.mp4 -metadata creation_time="2015-05-08T17:33:03.000Z" newFile.mp4



But, the code I wrote doesn't seem to work, at least to change the date of the file. I tested most of the metadata fields (author, title, etc.), and it seems to work fine with them, just not the Media Creation Date (creation_time).


Here is the code, for reference :


// node-module
 var ffmpeg = require('fluent-ffmpeg');

 // File location
 const filePath = './'
 var fileName = "20150408_143303.mp4"


 var year = fileName.slice(0, 4)
 var month = fileName.slice(4, 6)
 var day = fileName.slice(6, 8)
 var hours = fileName.slice(9, 11)
 var minutes = fileName.slice(11, 13)
 var seconds = fileName.slice(13, 15)

 var date = new Date(year, month, day, hours, minutes, seconds)

 //2015-05-08T17:33:03.000Z
 console.log(date)


 // First try (doesn't work)
 const file = filePath + fileName
 ffmpeg(file).inputOptions(`-metadata`, `title="Movie"`)


 // ffmpeg -i 20150408_143303.mp4 -metadata creation_time="2015-05-08T17:33:03.000Z" newFile.mp4

 // second try
 ffmpeg.ffprobe(file, function(err, metadata) {

 ffmpeg(file)
 .inputFormat('mp4')
 .outputOptions([`-metadata`, `creation_time=${date}`])
 .save('newFile.mp4')
 .on("progress", function(progress) {
 console.log("Processing: " + progress.timemark);
 })
 .on("error", function(err, stdout, stderr) {
 console.log("Cannot process video: " + err.message);
 })
 .on("end", function(stdout, stderr) {
 console.log((metadata.format.tags))
 })
 .run();

 })



Console.log : https://imgur.com/a/gR93xLE

There are no console errors, and everything seems to run smoothly, but the creation_time really does not change. Any idea as to why this is occurring is very welcome...