
Recherche avancée
Autres articles (61)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
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 (...)
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)
Sur d’autres sites (7185)
-
ffmpeg - over 1000 files into a mp4
20 octobre 2013, par FabrizioI am using FreeBSD and ffmpeg and I am trying to convert over 1000 files into an mp4. Keep in mind that I am completely NEW to ffmpeg and that in the future I might have up to 3600 images.
I was thinking that simply executing :
ffmpeg -i /usr/local/www/tmp/phpFa5LT3/*.jpg -r 2 output.mp4
would work, but I keep getting
ffmpeg version 0.7.12, Copyright (c) 2000-2011 the FFmpeg developers
built on Jun 9 2013 12:48:13 with gcc 4.2.1 20070831 patched [FreeBSD]
configuration: --prefix=/usr/local --mandir=/usr/local/man --enable-shared --enable-gpl --enable-postproc --enable-avfilter --enable-pthreads --enable-memalign-hack --enable-runtime-cpudetect --cc=cc --extra-cflags='-msse -I/usr/local/include/vorbis -I/usr/local/include' --extra-ldflags='-L/usr/local/lib ' --extra-libs=-pthread --disable-debug --disable-libaacplus --disable-indev=alsa --disable-outdev=alsa --disable-libopencore-amrnb --disable-libopencore-amrwb --disable-libcelt --disable-libdirac --disable-libfaac --enable-libfreetype --enable-frei0r --disable-libgsm --disable-libmp3lame --enable-libopencv --enable-libopenjpeg --disable-librtmp --enable-libschroedinger --disable-ffplay --disable-libspeex --enable-libtheora --disable-vaapi --disable-vdpau --disable-libvo-aacenc --disable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid
libavutil 50. 43. 0 / 50. 43. 0
libavcodec 52.123. 0 / 52.123. 0
libavformat 52.111. 0 / 52.111. 0
libavdevice 52. 5. 0 / 52. 5. 0
libavfilter 1. 80. 0 / 1. 80. 0
libswscale 0. 14. 1 / 0. 14. 1
libpostproc 51. 2. 0 / 51. 2. 0
Input #0, image2, from '20131019205500.jpg':
Duration: 00:00:00.50, start: 0.000000, bitrate: N/A
Stream #0.0: Video: mjpeg, yuvj420p, 320x240 [PAR 96:96 DAR 4:3], 2 tbr, 2 tbn, 2 tbc
Too many output filesWhen I try :
ffmpeg -y -f image2 -r 4 -i /usr/local/www/tmp/phpFa5LT3/%14d.jpg output.mp4
I get :
[same output but last line reads]
/usr/local/www/tmp/phpFa5LT3/%12d.jpg: No such file or directoryIf I reduce the number of files to just a 100 or so, I can do it without any problems... Do you know what the problem might be ?
#ulimit -a
cpu time (seconds, -t) unlimited
file size (512-blocks, -f) unlimited
data seg size (kbytes, -d) 33554432
stack size (kbytes, -s) 524288
core file size (512-blocks, -c) unlimited
max memory size (kbytes, -m) unlimited
locked memory (kbytes, -l) unlimited
max user processes (-u) 5547
open files (-n) 230400
virtual mem size (kbytes, -v) unlimited
swap limit (kbytes, -w) unlimited
sbsize (bytes, -b) unlimited
pseudo-terminals (-p) unlimited -
Creating an Init file from existing non-fragmented, segmented MP4 files
20 novembre 2018, par slhckI am performing chunked encodes of longer video files, where I’ve split the original file into individual sequences that I have encoded separately. These sequences are files of different length, depending on where the scene cuts appear—they may be between 2 and 5 seconds long. They all start with an I-frame and are standalone.
My encoded sequences are all MP4s, e.g. :
test_0000.mp4
test_0001.mp4
test_0002.mp4
test_0003.mp4
test_0004.mp4They all have common properties :
$ mp4info test_0000.mp4
File:
major brand: isom
minor version: 200
compatible brand: isom
compatible brand: iso2
compatible brand: mp41
fast start: no
Movie:
duration: 2016 ms
time scale: 1000
fragments: no
...Now, in order to play those with a DASH player, I have to create an initialization segment and individual fragmented MP4s.
I could generate the fragmented MP4s via
mp4fragment
which I run on each standalone MP4 file :$ mp4info test_0000.m4s
File:
major brand: isom
minor version: 200
compatible brand: isom
compatible brand: iso2
compatible brand: mp41
compatible brand: iso5
fast start: yes
Movie:
duration: 2016 ms
time scale: 1000
fragments: yes
...But obviously, these are now not according to spec, and all contain a
moov
atom :What I’d need is individual media segments with only one
moof
andmdat
box, which then require an initialization segment with only amoov
box.How can I generate that from the existing, already encoded segments ?
I know this appears like an XY problem. In principle, I could already segment my original file directly after encoding, and run those encodes at the same time, e.g. using ffmpeg’s
dash
muxer, or MP4Box, however :- There is almost no control over the resulting segment sizes, with respect to minimum and maximum duration
- This approach does not parallelize
I have also checked Bento4 ; it does not seem to offer this functionality. Neither does FFmpeg. MP4Box behaves similarly. They all assume you have one long file to start with.
I see I could splice off the
ftyp
andmoov
boxes from these “fake fragments” in order to create an initialization segment. But I would end up with segments containing multiplemoof
andmdat
boxes, which is not according to the specification – it only allows one fragment and media data box :4. Media Segments
[…] one optional Segment Type Box (styp) followed by a single Movie Fragment Box (moof) followed by one or more Media Data Boxes (mdat).
I guess I can live with this the
styp
not being present. -
fftools/graphprint : Add execution graph printing
15 mai, par softworkzfftools/graphprint : Add execution graph printing
The key benefits are :
Different to other graph printing methods, this is outputting :
- all graphs with runtime state
(including auto-inserted filters)
- each graph with its inputs and outputs
- all filters with their in- and output pads
- all connections between all input- and output pads
- for each connection :
- the runtime-negotiated format and media type
- the hw context
- if video hw context, both : hw pixfmt + sw pixfmtOutput can either be printed to stdout or written to specified file
Output is machine-readable
Use the same output implementation as ffprobe, supporting multiple
formatsSigned-off-by : softworkz <softworkz@hotmail.com>
- [DH] doc/ffmpeg.texi
- [DH] fftools/Makefile
- [DH] fftools/ffmpeg.c
- [DH] fftools/ffmpeg.h
- [DH] fftools/ffmpeg_filter.c
- [DH] fftools/ffmpeg_opt.c
- [DH] fftools/graph/graphprint.c
- [DH] fftools/graph/graphprint.h
- [DH] fftools/textformat/avtextformat.c
- [DH] fftools/textformat/avtextformat.h
- [DH] fftools/textformat/tf_mermaid.c
- [DH] fftools/textformat/tf_mermaid.h