
Recherche avancée
Autres articles (63)
-
List of compatible distributions
26 avril 2011, parThe table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...) -
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 ;
-
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
Sur d’autres sites (11481)
-
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