
Recherche avancée
Autres articles (51)
-
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 -
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 -
Support de tous types de médias
10 avril 2011Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)
Sur d’autres sites (10119)
-
Adding a custom filter to FFmpeg
16 juillet 2024, par AbhimanyuI am looking to configure and compile FFmpeg with custom filter.
custom filters are available on this git repository which is compiled with older ffmpeg version
https://github.com/numberwolf/FFmpeg-PlusPlus


I am following the steps mentioned on the ffmpeg official website
https://github.com/FFmpeg/FFmpeg/blob/master/doc/writing_filters.txt


I am getting warning plusglshader filter is unknown and same for all other filters


Here are my steps :


First, create your filter source files in the libavfilter directory :


`libavfilter/vf_plusglshader.c
libavfilter/vf_pipglshader.c
libavfilter/vf_lutglshader.c
libavfilter/vf_fadeglshader.c`



Update the FFmpeg build system by adding your new filter files to libavfilter/Makefile :


I am getting following below steps


First, create your filter source files in the libavfilter directory :


`libavfilter/vf_plusglshader.c
libavfilter/vf_pipglshader.c
libavfilter/vf_lutglshader.c
libavfilter/vf_fadeglshader.c`



Update the FFmpeg build system by adding your new filter files to libavfilter/Makefile :


`OBJS-$(CONFIG_PLUSGLSHADER_FILTER) += vf_plusglshader.o
OBJS-$(CONFIG_PIPGLSHADER_FILTER) += vf_pipglshader.o
OBJS-$(CONFIG_LUTGLSHADER_FILTER) += vf_lutglshader.o
OBJS-$(CONFIG_FADEGLSHADER_FILTER) += vf_fadeglshader.o`



In libavfilter/allfilters.c, add your filter declarations :


`extern const AVFilter ff_vf_plusglshader;
extern const AVFilter ff_vf_pipglshader;
extern const AVFilter ff_vf_lutglshader;
extern const AVFilter ff_vf_fadeglshader;`



In libavfilter/filter_list.c (not allfilters.c), add your filters to the filter_list array :


`static const AVFilter * const filter_list[] = {
 // ... existing filters ...
 &ff_vf_plusglshader,
 &ff_vf_pipglshader,
 &ff_vf_lutglshader,
 &ff_vf_fadeglshader,
 NULL
};`



In libavfilter/allfilters.c, add your filter declarations :


`extern const AVFilter ff_vf_plusglshader;
extern const AVFilter ff_vf_pipglshader;
extern const AVFilter ff_vf_lutglshader;
extern const AVFilter ff_vf_fadeglshader;`



In libavfilter/filter_list.c (not allfilters.c), add your filters to the filter_list array :


`static const AVFilter * const filter_list[] = {
 // ... existing filters ...
 &ff_vf_plusglshader,
 &ff_vf_pipglshader,
 &ff_vf_lutglshader,
 &ff_vf_fadeglshader,
 NULL
};`



`


-
FFMpeg Android Stagefright SIGSEGV error (h264 decode)
19 avril 2013, par Sergey OchkurI need to decode h264 file to YUV on Android 2.3+. As I understand I need to communicate with Stagefright, as it`s the only way now, after closing access with OpenMAX IL implementations. I have used FFmpeg 0.10 (and tried 0.9/0.9.1..) for this issue, compiled it with NDK7 (and also tried NDK6b with the same result) :
ffmpeg version 0.10 Copyright (c) 2000-2012 the FFmpeg developers
built on Jan 28 2012 14:42:37 with gcc 4.4.3
configuration: --target-os=linux --cross-prefix=arm-linux-androideabi- --arch=arm --cpu=armv7-a --sysroot=/home/grid/Android/Android_NDK/platforms/android-9/arch-arm --disable-avdevice --disable-decoder=h264 --disable-decoder=h264_vdpau --enable-libstagefright-h264 --prefix=build/stagefright/armeabi-v7a --extra-cflags='-Iandroid-source/frameworks/base/include -Iandroid-source/system/core/include -Iandroid-source/frameworks/base/media/libstagefright -Iandroid-source/frameworks/base/include/media/stagefright/openmax -I/home/grid/Android/Android_NDK/sources/cxx-stl/system/include -march=armv7-a -mfloat-abi=softfp -mfpu=neon' --extra-ldflags='-Wl,--fix-cortex-a8 -Landroid-libs -Wl,-rpath-link,android-libs' --extra-cxxflags='-Wno-multichar -fno-exceptions -fno-rtti'
libavutil 51. 34.101 / 51. 34.101
libavcodec 53. 60.100 / 53. 60.100
libavformat 53. 31.100 / 53. 31.100
libavfilter 2. 60.100 / 2. 60.100
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 6.100 / 0. 6.100
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...Hardware : Beagleboard-Xm + TI Android 2.3 (official)
So, entering next command give me error with 480p :
ffmpeg -i /sdcard/Video/480p.mp4Stopped (signal) ffmpeg -i /sdcard/Video/480p.mp4
Full Android "answer" from ADB Logcat :
http://pastebin.com/76JLgtXXAndroid-developers, does anybody know what this error means and how to deal with it ?
I tried to make DSP window bigger, but with no luck.
Commands like "stagefright /sdcard/Video/480p.mp4" works fine.P.S. Additionally I found that on some bigger files (720p) Android answers next :
[libstagefright_h264 @ 0xd479b0] Decode failed : 80000000
-
FFMpeg Concatenation Filters : Stream specifier ':0' in filtergraph matches no streams
8 décembre 2018, par Anthony EdenI am developing an application that relies heavily on FFMpeg to perform various transformations on audio files. I am currently testing my FFMpeg configuration on the command line.
I am trying to concatenate multiple audio files which are in different formats (Primarily MP3, MP2 & WAV). I have been using the official TRAC documentation (https://trac.ffmpeg.org/wiki/How%20to%20concatenate%20(join%2C%20merge)%20media%20files#differentcodec) to help me with this and have created the following command :
ffmpeg -i OHIn.wav -i OHOut.wav -filter_complex '[0:0] [1:0] concat=n=2:a=1 [a]' -map '[a]' output.wav
However, when I run this on Mac OS X using version 2.0.1 of FFMpeg, I get the following error message :
Stream specifier ':0' in filtergraph description [0:0] [1:0] concat=n=2:a=1 [a] matches no streams.
Here is my full output from the terminal :
~/ffmpeg -i OHIn.wav -i OHOut.wav -filter_complex '[0:0] [1:0] concat=n=2:a=1 [a]' -map '[a]' output.wav
ffmpeg version 2.0.1 Copyright (c) 2000-2013 the FFmpeg developers
built on Aug 15 2013 10:56:46 with llvm-gcc 4.2.1 (LLVM build 2336.11.00)
configuration: --prefix=/Volumes/Ramdisk/sw --enable-gpl --enable-pthreads --enable-version3 --enable-libspeex --enable-libvpx --disable-decoder=libvpx --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-avfilter --enable-libopencore_amrwb --enable-libopencore_amrnb --enable-filters --enable-libgsm --arch=x86_64 --enable-runtime-cpudetect
libavutil 52. 38.100 / 52. 38.100
libavcodec 55. 18.102 / 55. 18.102
libavformat 55. 12.100 / 55. 12.100
libavdevice 55. 3.100 / 55. 3.100
libavfilter 3. 79.101 / 3. 79.101
libswscale 2. 3.100 / 2. 3.100
libswresample 0. 17.102 / 0. 17.102
libpostproc 52. 3.100 / 52. 3.100
Guessed Channel Layout for Input Stream #0.0 : stereo
Input #0, wav, from 'OHIn.wav':
Duration: 00:00:06.71, bitrate: 1411 kb/s
Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 44100 Hz, stereo, s16, 1411 kb/s
Guessed Channel Layout for Input Stream #1.0 : stereo
Input #1, wav, from 'OHOut.wav':
Duration: 00:00:07.19, bitrate: 1411 kb/s
Stream #1:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 44100 Hz, stereo, s16, 1411 kb/s
Stream specifier ':0' in filtergraph description [0:0] [1:0] concat=n=2:a=1 [a] matches no streams.I do not understand why this does not work. FFMpeg shows that the streams 0:0 and 1:0 exist in the source files. The only other similar problems online have surrounded the use of the single quote in Windows, however testing of this confirm it does not apply to my Mac command line.
Any help would be much appreciated.