
Recherche avancée
Autres articles (50)
-
Participer à sa traduction
10 avril 2011Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
Actuellement MediaSPIP n’est disponible qu’en français et (...) -
Les formats acceptés
28 janvier 2010, parLes commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
ffmpeg -codecs ffmpeg -formats
Les format videos acceptés en entrée
Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
Les formats vidéos de sortie possibles
Dans un premier temps on (...) -
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 (...)
Sur d’autres sites (6787)
-
FFmpeg video has an excessively long duration
8 juillet 2023, par daraemWhen using ytdl-core and ffmpeg-static to download high quality youtube videos, the output video is supposedly thousands of hours long, which makes it not let me advance the video in a media player. The error only occurs in windows 10 players. In VLC or Discord it does not happen.


res.header("Content-Disposition", `attachment; filename=video.mp4`)

 let video = ytdl(link, {
 filter: 'videoonly'
 })
 let audio = ytdl(link, {
 filter: 'audioonly',
 highWaterMark: 1 << 25
 });
 const ffmpegProcess = cp.spawn(ffmpeg, [
 '-i', `pipe:3`,
 '-i', `pipe:4`,
 '-map', '1:0',
 '-map', '0:0',
 '-vcodec', 'libx264',
 '-c:v', 'libx264',
 '-c:a', 'aac',
 '-crf', '27',
 '-preset', 'veryslow',
 '-b:v', '1500k',
 '-b:a', '128k',
 '-movflags', 'frag_keyframe+empty_moov',
 '-f', 'mp4',
 '-loglevel', 'error',
 '-',
 ], {
 stdio: [
 'pipe', 'pipe', 'pipe', 'pipe', 'pipe',
 ],
 });
 
 video.pipe(ffmpegProcess.stdio[3]);
 audio.pipe(ffmpegProcess.stdio[4]);
 ffmpegProcess.stdio[1].pipe(res);
 
 let ffmpegLogs = ''
 
 ffmpegProcess.stdio[2].on(
 'data',
 (chunk) => {
 ffmpegLogs += chunk.toString()
 }
 )
 
 ffmpegProcess.on(
 'exit',
 (exitCode) => {
 if (exitCode === 1) {
 console.error(ffmpegLogs)
 }
 }
 )



I've tried changing the codecs options. But I'm not sure what I'm doing


-
ffmpeg does not recognize long string filter in execv
4 mai 2023, par incertiaI am writing some simple python script to call ffmpeg and concat some clips together. However, it doesn't work for reasons I am unable to explain.


below is a working version of the code after some debugging


inputs = sorted(list(askopenfilenames()))
n = len(inputs)

filter = []
for i in range(n):
 filter.append("[{}:v]".format(i))
 filter.append("[{}:a]".format(i))
filter.append("concat={}:v=1:a=1".format(n))
filter.append("[v]")
filter.append("[a]")
filter = " ".join(filter)

fargs = zip(itertools.repeat('-i'), inputs)
fargs = itertools.chain(
 ["ffmpeg"],
 itertools.chain.from_iterable(fargs),
 ["-filter_complex", '"{}"'.format(filter), "-vsync", "vfr", "-map", "[v]", "-map", "[a]"],
 ["-c:v", "libx264", "-crf", "{}".format(quality)],
 ["-c:a", "aac", "-b:a", "192k"],
 [out]
 )

os.execvp("ffmpeg", list(fargs))



but the entire
fargs
construction causesffmpeg
to complain about the filter chain when quotes are not utilized. e.g. by utilizing the below process

fargs = itertools.chain(
 ["ffmpeg", "-loglevel", "debug"],
 itertools.chain.from_iterable(fargs),
 #["-filter_complex", '"{}"'.format(filter), "-vsync", "vfr", "-map", "[v]", "-map", "[a]"],
 ["-filter_complex", filter, "-vsync", "vfr", "-map", "[v]", "-map", "[a]"],
 ["-c:v", "libx264", "-crf", "{}".format(quality)],
 ["-c:a", "aac", "-b:a", "192k"],
 [out]
 )



we see that
ffmpeg
somehow sees this as multiple arguments

Reading option '-filter_complex' ... matched as option 'filter_complex' (create a complex filtergraph) with argument '[0:v]'.
Reading option '[0:a]' ... matched as output url.
Reading option '[1:v]' ... matched as output url.
Reading option '[1:a]' ... matched as output url.
Reading option '[2:v]' ... matched as output url.
Reading option '[2:a]' ... matched as output url.
Reading option 'concat=3:v=1:a=1' ... matched as output url.
Reading option '[v]' ... matched as output url.
Reading option '[a]' ... matched as output url.



even though a simple
print(list(fargs))
yields

['ffmpeg', '-loglevel', 'debug', '-i', 'a.mp4', '-i', 'b.mp4', '-i', 'c.mp4', '-filter_complex', '[0:v] [0:a] [1:v] [1:a] [2:v] [2:a] concat=3:v=1:a=1 [v] [a]', '-vsync', 'vfr', '-map', '[v]', '-map', '[a]', '-c:v', 'libx264', '-crf', '20', '-c:a', 'aac', '-b:a', '192k', 'asdf.mp4']



implying that the long filter string is being passed to ffmpeg as a single argument.


-
nodejs fluent-ffmpeg split long file into multiple small files based on seconds given
9 mars 2023, par Mahesh DamaI want to split 10 minute audio mp3 file to 10 different 1 minute files using
fluent-ffmpeg
package innodejs
.
We can do this forffmpeg
package using the following command

ffmpeg -i file.wav -f segment -segment_time 60 -c copy parts/output%09d.wav



But I want the same functionality in
fluent-ffmpeg
fornodejs
. What is the name of the method ?

return ffmpeg(audioFile)
 .toFormat('wav')
 .audioChannels(1)
 .audioFrequency(44100)
 .audioBitrate('128')
 .on('error', (err) => {
 //error
 })
 .on('progress', (progress) => {
 //progress
 })
 .on('end', () => {
 // on complete
 })



I tried looking at documentation for the segment feature for
fluent-ffmpeg
but couldn't get any solution.