
Recherche avancée
Autres articles (90)
-
Gestion des droits de création et d’édition des objets
8 février 2011, parPar défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;
-
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 (6220)
-
Proportion for the values of maxrate, mnrate and bufsize for encoding videos for streaming purpose and past duration too large warning
15 décembre 2015, par himanshu nautiyalcan you please tell me about minrate, maxrate and bufsize. And is it necessary to give maxrate and minrate for encoding videos for streaming purpose. Actually I understood the meaning and functions of minrate, maxrate and bufsize through ffmpeg documents but I am not finding any solution of what would be difference in between the values of these three.
for example : I am using this command
ffmpeg -y -i testing.mp4 -c:a libfdk_aac -ac 2 -ab 128k -c:v libx264 -r 24 -g 24 -b:v 2m -maxrate 1m -bufsize 1m -vf scale=1920*1080 aa.mp4but I am not sure if this -b:v 2m -maxrate 1m bufsize 1m is in correct propotions or not. My output is fine but I don’t want any problem on working real time. Moreover, I am also getting the following warning
Past duration 0.634361 too large
Past duration 0.674370 too large
Past duration 0.714363 too large 0kB time=00:00:01.32 bitrate= 0.3kbits/sPast duration 0.754372 too large
Past duration 0.794365 too large
Past duration 0.834373 too large
Past duration 0.874367 too large
Past duration 0.914360 too large
Past duration 0.954369 too largethanks in advance
-
avcodec/cbs_h2645 : Treat slices without data as invalid
9 décembre 2019, par Andreas Rheinhardtavcodec/cbs_h2645 : Treat slices without data as invalid
Slices that end after their header (meaning slices after the header
without any data before the rbsp_stop_one_bit or possibly without any
rbsp_stop_one_bit at all) are invalid and are now dropped. This ensures
that one doesn't run into two asserts in cbs_h2645_write_slice_data().Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
Fixes : 19629/clusterfuzz-testcase-minimized-ffmpeg_BSF_H264_METADATA_fuzzer-5676822528524288
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc> -
hevc : Simplify logical check
2 octobre 2015, par Vittorio Giovara