
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 (74)
-
Mise à jour de la version 0.1 vers 0.2
24 juin 2013, parExplications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...) -
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 ;
-
Ecrire une actualité
21 juin 2013, parPrésentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
Vous pouvez personnaliser le formulaire de création d’une actualité.
Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)
Sur d’autres sites (13369)
-
where can one find old patches/curated versions of ffmpeg for qsv (mpeg2_qsv) ?
10 avril 2023, par CodeCalffor the past year or so the mpeg2_qsv encoder in ffmpeg/libmfx has been broken due to a idr interval problem (sends only one idr frame at the start of the video rather than sending idr frames at a certain interval) i have found a solution/workaround by adding the idr-interval option defined in h264_qsv.c to the mpeg2_qsv.c provided in ffmpeg it does work but the quality of the output is subpar even after applying heavy post processing filters and i have been working on this exact platform for the past 4 years so i know for a fact that it used to work way better hence i have been trying to revert the changes made to ffmpeg in the past 1-2 years unsuccessfully as i am not able to find old patches that i could use as reference.


i understand that for this problem a lot of people suggest using ffmpeg 2.8 which apparently is the best for old qsv behaviour but due to mediasdk version mismatches i haven't been able to build it successfully on any new OS after ubuntu 18.04 but i cannot use ubuntu 18.04 or below because of a hardware issue on my platform which messes with the xserver introducing a lot of weird errors if anyone has any suggestions of how i can overcome this then please help as i am all ears


i am new to this website so i apologize in advance if i have made a mistake in asking this question.


thank you for your patience and guidance


-
Compiled FFmpeg for Android with enabled libmp3lame
11 juillet 2015, par Pepa ZapletalI´m using in my app ffmpeg library. I downloaded compiled version of this library from :
https://github.com/guardianproject/android-ffmpeg-java
But I need it with libmp3lame. I found this :
https://github.com/lokeshj/android-ffmpeg-build
and it works on Android 4.0+ but not on Android 5.0+ because this compiled library does not support PIE.
I don´t have Linux so I cannot compile library with libmp3lame and PIE support. Can someone upload this library (with libmp3lame) somewhere ? I think it will help a lot of people.
Thanks !
-
FFMPEG and AWS Mountpoint random write output error
25 septembre 2023, par Juan Manuel MartiI'm testing the new feature in AWS with mountpoint-s3 to read and write directly to S3 the video files to encode. I've crossed a problem with random writes with the output that is not supported.


This is the error :


mountpoint_s3::fuse: write failed: upload error: out of order write; expected offset 3461864 but got 36



This was discussed with the people that created mountpoint on github and they asked me :


Is there any way your ffmpeg workload can be configured to not require random write access to the files?



Does anyone know any command that could force FFMPEG to avoid any random write ?


This is my command at the moment :


ffmpeg -i inputfile -map 0:a:1 -metadata language=ENG -c:v libx265 -b:v 5000K -minrate 5000K -maxrate 5000K -bufsize 6000K -g 12 -pix_fmt yuv422p10le -r 30000/1001 -profile:v main422-10 -level 4.1 -aspect 16:9 -x265-params no-scenecut:open-gop:min-keyint=72:keyint=72:-colorprim=bt709 -vf "scale=1920:-1" -c:a aac -ar 48000 -rematrix_maxval 1.0 -ac 2 -b:a 192k -y outputfile