
Recherche avancée
Médias (1)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (98)
-
Personnaliser les catégories
21 juin 2013, parFormulaire de création d’une catégorie
Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
On peut modifier ce formulaire dans la partie :
Administration > Configuration des masques de formulaire.
Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...) -
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...) -
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...)
Sur d’autres sites (9434)
-
Libvpx unknown encoder with php exec
5 juin 2016, par Justin TullockI have centos7 with ffmpeg compiled with libvpx. I can run
ffmpeg -i gif.gif -c:v libvpx -crf 12 -b:v 500K webm.webm
which works perfectly but when I try the same command with php exec() it returns this :
{array(16) { [0]=> string(66) "ffmpeg version 2.6.8 Copyright (c) 2000-2016
the FFmpeg developers" [1]=> string(55) " built with gcc 4.8.5 (GCC)
20150623 (Red Hat 4.8.5-4)" [2]=> string(1053) " configuration: --
refix=/usr --bindir=/usr/bin --datadir=/usr/share/ffmpeg --
incdir=/usr/include/ffmpeg --libdir=/usr/lib64 --mandir=/usr/share/man --
arch=x86_64 --optflags='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -
fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-
switches -m64 -mtune=generic' --enable-bzlib --disable-crystalhd --enable-
gnutls --enable-ladspa --enable-libass --enable-libcdio --enable-libdc1394 -
-enable-libfaac --enable-nonfree --enable-libfdk-aac --enable-nonfree --
disable-indev=jack --enable-libfreetype --enable-libgsm --enable-libmp3lame
--enable-openal --enable-libopenjpeg --enable-libopus --enable-libpulse --
enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora
--enable-libvorbis --enable-libv4l2 --enable-libx264 --enable-libx265 --
enable-libxvid --enable-x11grab --enable-avfilter --enable-avresample --
enable-postproc --enable-pthreads --disable-static --enable-shared --enable-
gpl --disable-debug --disable-stripping --shlibdir=/usr/lib64 --enable-
runtime-cpudetect" [3]=> string(40) " libavutil 54. 20.100 / 54. 20.100"
[4]=> string(40) " libavcodec 56. 26.100 / 56. 26.100" [5]=> string(40) "
libavformat 56. 25.101 / 56. 25.101" [6]=> string(40) " libavdevice 56.
4.100 / 56. 4.100" [7]=> string(40) " libavfilter 5. 11.102 / 5. 11.102"
[8]=> string(40) " libavresample 2. 1. 0 / 2. 1. 0" [9]=> string(40) "
libswscale 3. 1.101 / 3. 1.101" [10]=> string(40) " libswresample 1. 1.100 /
1. 1.100" [11]=> string(40) " libpostproc 53. 3.100 / 53. 3.100" [12]=>
string(30) "Input #0, gif, from 'gif.gif':" [13]=> string(29) " Duration:
N/A, bitrate: N/A" [14]=> string(76) " Stream #0:0: Video: gif, bgra,
563x307, 25 fps, 25 tbr, 100 tbn, 100 tbc" [15]=> string(24) "Unknown
encoder 'libvpx'" } int(1)ffmpeg -v returns this
ffmpeg version N-80161-g7e0623b Copyright (c) 2000-2016 the FFmpeg developers
built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-4)
configuration: --enable-libvpx
libavutil 55. 24.100 / 55. 24.100
libavcodec 57. 44.100 / 57. 44.100
libavformat 57. 37.101 / 57. 37.101
libavdevice 57. 0.101 / 57. 0.101
libavfilter 6. 46.100 / 6. 46.100
libswscale 4. 1.100 / 4. 1.100
libswresample 2. 0.101 / 2. 0.101What am I missing ?
-
Video width is different in different devices
8 novembre 2017, par DavidI have a special video when i want to get this video’s width code returns different value for Samsung galaxy s6 and Samsung note 3. I tested many different codes and libraries, but result is the same.
in Samsung galaxy s6 : 640x480
in Samsung note 3 : 853x480
when I open this video with Gspot program it shows :Recommended Display Size : 853x480
and this is the same value is returned by our IOS app tested in Iphone 7. aspect radio is not the same and this is big problem.
here is some of codes I tested :
(1)
MediaMetadataRetriever metaRetriever = new MediaMetadataRetriever();
metaRetriever.setDataSource(path);
Bitmap bmp = metaRetriever.getFrameAtTime(-1);
int height = bmp.getHeight();
int width = bmp.getWidth();(2)
MediaPlayer myMediaPlayer= MediaPlayer.create(ApplicationLoader.applicationContext,
Uri.fromFile(new File(path)));
width = myMediaPlayer.getVideoWidth();
height = myMediaPlayer.getVideoHeight();(3)
MediaMetadataRetriever metaRetriever = new MediaMetadataRetriever();
metaRetriever.setDataSource(path);
String heights = metaRetriever.extractMetadata(MediaMetadataRetriever.METADATA_KEY_VIDEO_HEIGHT);
String widths = metaRetriever.extractMetadata(MediaMetadataRetriever.METADATA_KEY_VIDEO_WIDTH);
int height = Integer.valueOf(heights);
int width = Integer.valueOf(widths);(4)
MediaPlayer myMediaPlayer= MediaPlayer.create(ApplicationLoader.applicationContext, Uri.fromFile(new File(path)));
myMediaPlayer.setOnVideoSizeChangedListener((mp, width, height) -> {
int videoWidth = width;
int videoHeight = height;
);
myMediaPlayer.setDataSource(path);
myMediaPlayer.prepare();FFmpegMediaMetadataRetriever, FFmpeg Java, ExoPlayer and some other libraries returns the same result.
-
Specifying input duration of .aac with ffmpeg
28 septembre 2020, par JademaloI had an error with an mp4 recording, and after recovering the video and audio streams I've still got an issue. The aac audio file is 160kb/s CBR. However, ffmpeg returns this when trying to work with it ;


[aac @ 000001187e6944c0] Estimating duration from bitrate, this may be inaccurate
Input #0, aac, from 'result.aac':
 Duration: 00:38:41.01, bitrate: 174 kb/s
 Stream #0:0: Audio: aac (LC), 44100 Hz, stereo, fltp, 174 kb/s



That duration and bitrate is totally wrong. It should be 42 minutes long, and it definitely has a bitrate of 160 kb/s.


This results in the audio being very inconsistently timed, as well as having all sorts of other issues. It's very weird.


Is there any way I can specify that the input is 160 cbr to try and wrangle it back into a usable file ?