
Recherche avancée
Médias (1)
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
Autres articles (66)
-
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
Amélioration de la version de base
13 septembre 2013Jolie sélection multiple
Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)
Sur d’autres sites (13474)
-
Solution Merge mp3+mp4 together with FFMPEG or other
7 juin 2018, par SandyUgaleI have been working on a project where I have .mp3 and video file (.MP4). I have FFMG on my AWS server and I’m providing both to FFMPEG give me complete video file with provided audio file. Then I send this file to my AWS S3 and then fetch this video as needed in my web app.
Problem/Use Case :
If I have 10 mp3 and 10 mp4 video files then I have to wait the until it complete all videos then only I can send them on S3, so Im waiting for long as number goes up.
Can I control this ?
Solution-1 : Don’t need to wait for loop
Meaning instead of starting all merging together parallel I would like merging to be done one by one. Referencing above example
First merge of 1.mp3 + 1. Mp4= 1.mp4 (complete file) –upload s3.
Second merge of 2.mp3 + 2. Mp4= 2.mp4 (complete file) –upload s3.
Tenth merge of 10.mp3 + 10. Mp4= 10.mp4 (complete file) –upload s3.Solution-2 : send video as they ready
How I can know which video has been ready to send to s3 ?
Solution-3 : other service
Is there any other online API or services where I can pass mp3 + mp4 and give me video url simply after merging so technically video will hosted on either their platform or on my S3 doest matter.
-
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>