
Recherche avancée
Médias (1)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (96)
-
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 ;
-
Ecrire une actualité
21 juin 2013, parPrésentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
Vous pouvez personnaliser le formulaire de création d’une actualité.
Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...) -
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
Sur d’autres sites (4996)
-
avfilter/vf_libplacebo : remove deprecated field
13 mars 2023, par Niklas Haasavfilter/vf_libplacebo : remove deprecated field
This has not been functional since a year ago, including in our current
minimum dependency of libplacebo (v4.192.0). It also causes build errors
against libplacebo v6, so it needs to be removed from the code. We can
keep the option around for now, but it should also be removed soon.Signed-off-by : Niklas Haas <git@haasn.dev>
Signed-off-by : James Almer <jamrial@gmail.com> -
FFmpeg plus the - c:v copy parameter - force_ key_ Frames won't work ?
26 février 2023, par xiaoliuI understand that the -force_key_frames parameter is to insert key frames into the video


Because the generated ts fragment is very different from the specified -hls_time parameter, the -force_key_frame parameter is added. I have 20T video resources. In order to speed up the encoding time, I chose -c:v copy not to encode, but this -force_key_frames has no effect. Is there any way to make TS fragments accurate without sacrificing coding time and ensuring image quality and storage space。


I have tried NVENC coding, but the image quality is too poor. In order to achieve the image quality of -crf 23 level, it needs more storage space than the original file


Thank you for your advice


I tried -c:v copy -f segment -segment_time parameter, we have also tried nvenc coding -preset p7 -cq 20 and libx264 -preset veryslow -crf 23.


Although nvenc is fast, it sacrifices image quality and storage space. Although libx264 improves image quality and storage space, it may be next year to transcode 20T video


-
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...