
Recherche avancée
Médias (1)
-
SPIP - plugins - embed code - Exemple
2 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
Autres articles (78)
-
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 ;
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
(Dés)Activation de fonctionnalités (plugins)
18 février 2011, parPour gérer l’ajout et la suppression de fonctionnalités supplémentaires (ou plugins), MediaSPIP utilise à partir de la version 0.2 SVP.
SVP permet l’activation facile de plugins depuis l’espace de configuration de MediaSPIP.
Pour y accéder, il suffit de se rendre dans l’espace de configuration puis de se rendre sur la page "Gestion des plugins".
MediaSPIP est fourni par défaut avec l’ensemble des plugins dits "compatibles", ils ont été testés et intégrés afin de fonctionner parfaitement avec chaque (...)
Sur d’autres sites (8888)
-
lavu,lavfi,ffmpeg : Remove experimental OpenCL API
14 novembre 2017, par Mark Thompsonlavu,lavfi,ffmpeg : Remove experimental OpenCL API
This was added in early 2013 and abandoned several months later ; as far as
I can tell, there are no external users. Future OpenCL use will be via
hwcontext, which requires neither special OpenCL-only API nor global state
in libavutil.All internal users are also deleted - this is just the unsharp filter
(replaced by unsharp_opencl, which is more flexible) and the deshake filter
(no replacement).- [DH] configure
- [DH] doc/APIchanges
- [DH] doc/filters.texi
- [DH] doc/utils.texi
- [DH] fftools/Makefile
- [DH] fftools/cmdutils.h
- [DH] fftools/cmdutils_opencl.c
- [DH] libavfilter/Makefile
- [DH] libavfilter/allfilters.c
- [DH] libavfilter/deshake.h
- [DH] libavfilter/deshake_opencl.c
- [DH] libavfilter/deshake_opencl.h
- [DH] libavfilter/deshake_opencl_kernel.h
- [DH] libavfilter/opencl_allkernels.c
- [DH] libavfilter/opencl_allkernels.h
- [DH] libavfilter/unsharp.h
- [DH] libavfilter/unsharp_opencl.c
- [DH] libavfilter/unsharp_opencl.h
- [DH] libavfilter/unsharp_opencl_kernel.h
- [DH] libavfilter/vf_deshake.c
- [DH] libavfilter/vf_unsharp.c
- [DH] libavutil/Makefile
- [DH] libavutil/opencl.c
- [DH] libavutil/opencl.h
- [DH] libavutil/opencl_internal.c
- [DH] libavutil/opencl_internal.h
-
On WebP and Academic Exercises
2 octobre 2010, par Multimedia Mike — GeneralYesterday, Google released a new still image format called WebP. To those skilled in the art, this new format will be recognizable as a single VP8 golden frame with a 20-byte header slapped on the front (and maybe a little metadata thrown in for good measure). We have a MultimediaWiki page and a sample ready to go.
Further, I submitted a patch to ffmpeg-devel for FFmpeg’s img2 handling system to decode these files. FFmpeg should support processing these files soon… if anyone cares. This leads into…
The Point, or Lack Thereof
Since yesterday’s release, I have read a whirlwind of commentary about this format, much of it critical and of the “what’s the point ?” variety. For my part, I can respect academic exercises, a.k.a., just trying random stuff to see if you can make it work. That’s pretty much this blog’s entire raison d’être. But WebP transcends mere academic exercise ; Google seems to be trying to push it as a new web standard. I don’t see how the format can go anywhere based on criticisms raised elsewhere — e.g., see Dark Shikari’s thoughtful write-up — which basically boil down to WebP not solving any real problems, technical, legal, or otherwise.How did WebP come to be ? I strongly suspect some engineers noticed that JPEG is roughly the same as an MPEG-1 intraframe, so why not create a new still frame format based on VP8 intraframes ? Again, I can respect that thinking– I have pondered how a still image format would perform if based on VP3/Theora or Sorenson Video 1.
Technically
Google claims a significant size savings for WebP vs. standard JPEG. Assuming that’s true (and there will be no shortage of blog posts to the contrary), it will still be some time before WebP support will find its way into the majority of the web browser population.But this got me thinking about possible interim solutions. A website could store images compressed in both formats if it so chose. Then it could serve up a WebM image if the browser could support it, as indicated by the ‘Accept’ header in the HTTP request. It seems that a website might have to reference a generic image name such as
<img src="some-picture.image">
; the web server would have to recognize the .image extension and map it to either a .jpg or a .webp image depending on what the browser claims it is capable of displaying.Leftovers
I appreciate that Dark Shikari has once again stuck his neck out and made a valiant — though often futile — effort to educate the internet’s masses. I long ago resigned myself to the fact that many people aren’t going to understand many of the most basic issues surrounding multimedia technology (i.e., moving pictures synchronized with audio). But apparently, this extends to still image formats as well. It was simultaneously humorous and disheartening to see commenters who don’t even understand the application of, e.g., PNG vs. JPEG : Ahem, “We already have a great replacement for jpg : .PNG”. Coupled with the typical accusations of MPEG tribalism, I remain impressed D. Shikari finds the will to bother.Still, I appreciate that the discussion has introduced me to some new image formats of which I was previously unaware, such as PGF and JPEG XR.
-
FFmpeg.js Extract images (jpeg/png) from MP4 file
5 août 2017, par Anuragh27cronyI’m trying to extract images/frames from a mp4 on client side with the help of ffmpeg.js.
Equivalent Ffmpeg command :
ffmpeg -i Sample.mp4 -r 1 output%d.png
However i could try to create webm file from jpeg files but i couldn’t do the reverse and ends up with following error message
Unable to find a suitable output format for ’output%d.png’
Here is the code i’m trying to use.
var ffmpeg = require("ffmpeg.js/ffmpeg-mp4");
var fs = require("fs");
var stdout = "";
var stderr = "";
var testData = new Uint8Array(fs.readFileSync("Sample.mp4"));
var result = ffmpeg({
MEMFS: [{name: "Sample.mp4", data: testData}],
stdin: function() {},
arguments: ["-i", "Sample.mp4","-r","1", "output%d.png"],
});
console.log(result.MEMFS.length)
if(result.MEMFS.length>0){
var out = result.MEMFS[0].data;
fs.writeFileSync("test.jpg", Buffer(out.data));
}Console Output
ffmpeg version n3.1.2 Copyright (c) 2000-2016 the FFmpeg developers
built with emcc (Emscripten gcc/clang-like replacement) 1.36.7 ()
configuration: --cc=emcc --enable-cross-compile --target-os=none --arch=x86 --disable-runtime-cpudetect --disable-asm --disable-fast-unaligned --disable-pthreads --disable-w32threads --di
sable-os2threads --disable-debug --disable-stripping --disable-all --enable-ffmpeg --enable-avcodec --enable-avformat --enable-avutil --enable-swresample --enable-swscale --enable-avfilter
--disable-network --disable-d3d11va --disable-dxva2 --disable-vaapi --disable-vda --disable-vdpau --enable-decoder=vp8 --enable-decoder=vp9 --enable-decoder=theora --enable-decoder=mpeg2vid
eo --enable-decoder=mpeg4 --enable-decoder=h264 --enable-decoder=hevc --enable-decoder=png --enable-decoder=mjpeg --enable-decoder=vorbis --enable-decoder=opus --enable-decoder=mp3 --enable
-decoder=ac3 --enable-decoder=aac --enable-decoder=ass --enable-decoder=ssa --enable-decoder=srt --enable-decoder=webvtt --enable-demuxer=matroska --enable-demuxer=ogg --enable-demuxer=avi
--enable-demuxer=mov --enable-demuxer=flv --enable-demuxer=mpegps --enable-demuxer=image2 --enable-demuxer=mp3 --enable-demuxer=concat --enable-protocol=file --enable-filter=aresample --ena
ble-filter=scale --enable-filter=crop --enable-filter=overlay --disable-bzlib --disable-iconv --disable-libxcb --disable-lzma --disable-sdl --disable-securetransport --disable-xlib --disabl
e-zlib --enable-encoder=libx264 --enable-encoder=libmp3lame --enable-encoder=aac --enable-muxer=mp4 --enable-muxer=mp3 --enable-muxer=null --enable-gpl --enable-libmp3lame --enable-libx264
--extra-cflags=-I../lame/dist/include --extra-ldflags=-L../lame/dist/lib
libavutil 55. 28.100 / 55. 28.100
libavcodec 57. 48.101 / 57. 48.101
libavformat 57. 41.100 / 57. 41.100
libavfilter 6. 47.100 / 6. 47.100
libswscale 4. 1.100 / 4. 1.100
libswresample 2. 1.100 / 2. 1.100
[h264 @ 0x809d50] Warning: not compiled with thread support, using thread emulation
[aac @ 0x80e640] Warning: not compiled with thread support, using thread emulation
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Sample.mp4':
Metadata:
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf57.56.100
Duration: 00:01:00.00, start: 0.000000, bitrate: 137 kb/s
Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 360x214, 113 kb/s, 1 fps, 1 tbr, 16384 tbn, 32768 tbc (default)
Metadata:
handler_name : VideoHandler
Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 22050 Hz, mono, fltp, 23 kb/s (default)
Metadata:
handler_name : SoundHandler
[NULL @ 0x810d00] Unable to find a suitable output format for 'output%d.png'
output%d.png: Invalid argument