
Recherche avancée
Autres articles (16)
-
Installation en mode ferme
4 février 2011, parLe mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
C’est la méthode que nous utilisons sur cette même plateforme.
L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...) -
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) (...)
-
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 (6685)
-
Cant rotate video Android FFMPEG
24 novembre 2016, par ashishguptabnsI am using https://github.com/WritingMinds/ffmpeg-android-java. Can trim, join mp4 files but not able to rotate and speed up/down.
Tried almost all SO answers but no luck.
I am using latest Android Studio.
D/ffmpeg_work: [-noautorotate, -i, /storage/emulated/0/Pictures/VideoApp/v_1479895157.mp4, -vf, transpose=1, /storage/emulated/0/Pictures/VideoApp/v_1480001945.mp4]
D/FFmpeg: Running publishing updates method
D/ffmpeg_work: onProgress: ffmpeg version n3.0.1 Copyright (c) 2000-2016 the FFmpeg developers
D/ffmpeg_work: onProgress: built with gcc 4.8 (GCC)
D/ffmpeg_work: onProgress: configuration: --target-os=linux --cross-prefix=/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi- --arch=arm --cpu=cortex-a8 --enable-runtime-cpudetect --sysroot=/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-libass --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-fontconfig --enable-pthreads --disable-debug --disable-ffserver --enable-version3 --enable-hardcoded-tables --disable-ffplay --disable-ffprobe --enable-gpl --enable-yasm --disable-doc --disable-shared --enable-static --pkg-config=/home/vagrant/SourceCode/ffmpeg-android/ffmpeg-pkg-config --prefix=/home/vagrant/SourceCode/ffmpeg-android/build/armeabi-v7a --extra-cflags='-I/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all' --extra-ldflags='-L/home/vagrant/SourceCode/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-libs='-lpng -lexpat -lm' --extra-cxxflags=
D/ffmpeg_work: onProgress: libavutil 55. 17.103 / 55. 17.103
D/ffmpeg_work: onProgress: libavcodec 57. 24.102 / 57. 24.102
D/ffmpeg_work: onProgress: libavformat 57. 25.100 / 57. 25.100
D/ffmpeg_work: onProgress: libavdevice 57. 0.101 / 57. 0.101
D/ffmpeg_work: onProgress: libavfilter 6. 31.100 / 6. 31.100
D/ffmpeg_work: onProgress: libswscale 4. 0.100 / 4. 0.100
D/ffmpeg_work: onProgress: libswresample 2. 0.101 / 2. 0.101
D/ffmpeg_work: onProgress: libpostproc 54. 0.100 / 54. 0.100
D/ffmpeg_work: onProgress: Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/emulated/0/Pictures/VideoApp/v_1479895157.mp4':
D/ffmpeg_work: onProgress: Metadata:
D/ffmpeg_work: onProgress: major_brand : isom
D/ffmpeg_work: onProgress: minor_version : 512
D/ffmpeg_work: onProgress: compatible_brands: isomiso2avc1mp41
D/ffmpeg_work: onProgress: encoder : Lavf57.25.100
D/ffmpeg_work: onProgress: Duration: 00:00:09.88, start: -3.000000, bitrate: 1816 kb/s
D/ffmpeg_work: onProgress: Stream #0:0(eng): Video: h264 (Baseline) (avc1 / 0x31637661), yuv420p, 1280x960, 1755 kb/s, 4.46 fps, 7.50 tbr, 90k tbn, 180k tbc (default)
D/ffmpeg_work: onProgress: Metadata:
D/ffmpeg_work: onProgress: rotate : 270
D/ffmpeg_work: onProgress: handler_name : VideoHandler
D/ffmpeg_work: onProgress: Side data:
D/ffmpeg_work: onProgress: displaymatrix: rotation of 90.00 degrees
D/ffmpeg_work: onProgress: Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 96 kb/s (default)
D/ffmpeg_work: onProgress: Metadata:
D/ffmpeg_work: onProgress: handler_name : SoundHandlerTried these also :
[-noautorotate, -i, /storage/emulated/0/Pictures/VideoApp/v_1479895157.mp4, -filter:v, transpose=1, /storage/emulated/0/Pictures/VideoApp/v_1480002208.mp4]
[-noautorotate, -i, /storage/emulated/0/Pictures/VideoApp/v_1479895157.mp4, -filter:v, transpose=1, -metadata:s:v, rotate=0, /storage/emulated/0/Pictures/VideoApp/v_1480002275.mp4]
[-noautorotate, -i, /storage/emulated/0/Pictures/VideoApp/v_1479895157.mp4, -vf, transpose=1, /storage/emulated/0/Pictures/VideoApp/v_1480002362.mp4]After this nothing happens in both cases
-
How to stream and play video using ffplay without buffering
3 novembre 2014, par grzebykI want to stream a live webcam video and display it on android device with the lowest latency possible. I am streaming video from a computer over rtsp protocol and I am able to watch the stream with 150ms latency on the second computer using
ffplay -fflags nobuffer rtsp://xxx.xxx.xxx.xxx:port/test.sdp
command.So far I have successfully compiled ffmpeg4android library. Unfortunately this library uses NDK which I am not familiar with. All I want to do is to be able to invoke the same command and display the video on the android SurfaceView.
How can I call for such command ?
-
Revision 32453 : on renomme xcache en memoization, puisque c’est de ca qu’il s’agit ...
29 octobre 2009, par fil@… — Logon renomme xcache en memoization, puisque c’est de ca qu’il s’agit http://fr.wikipedia.org/wiki/Memoization (merci a Thomas Sutton)
le memo filecache.inc se limite a 164 fichiers, ce qui fait qu’il n’y a plus besoin de garbage collector