
Recherche avancée
Médias (1)
-
SPIP - plugins - embed code - Exemple
2 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
Autres articles (108)
-
Les vidéos
21 avril 2011, parComme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...) -
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 ;
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
Sur d’autres sites (8579)
-
avformat/hls, dashdec : Don't use AV_OPT flags in av_dict_set()
15 mai 2022, par Andreas Rheinhardtavformat/hls, dashdec : Don't use AV_OPT flags in av_dict_set()
av_dict_set() expects a different set of flags, namely the AV_DICT_*
flags. Using AV_OPT_FLAG_DECODING_PARAM (or any AV_OPT_FLAG_*) ic
av_dict_set() is therefore completely wrong and given that av_dict_set()
just doesn't care about whether the string it receives has anything
to do with a decoding parameter or not, it should just be removed
without replacement.
(The numerical value of AV_OPT_FLAG_DECODING_PARAM currently coincides
with AV_DICT_IGNORE_SUFFIX. Given that the dictionaries we are dealing
with here are always empty (i.e. NULL) before the calls to
av_dict_set(), this flag changes nothing. It would be different if
it were equal to one of the AV_DICT_DONT_STRDUP_* values.)Reviewed-by : Jan Ekström <jeebjp@gmail.com>
Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com> -
Docker build dependent on host Ubuntu version not on the actual Docker File
26 mars 2021, par user8912375I'm facing an issue with my docker build.


I have a dockerfile as follow :


FROM python:3.6


RUN apt-get update && apt-get install -y libav-tools 
....



The issue I'm facing is that I'm getting this error when building on ubuntu:20.04 LTS


E: Package 'libav-tools' has no installation candidate



I made some research and found out that
ffmpeg
should be a replacement forlibav-tools


FROM python:3.6


RUN apt-get update && apt-get install -y ffmpeg 
....



I tried again without any issue.


but when I tried to build the same image with
ffmpeg
on ubuntu:16.04 xenial I'm getting a message that

E: Package 'ffmpeg' has no installation candidate



after that, I replace the
ffmpeg
withlibav-tools
and it worked on ubuntu:16.04

I'm confused now why docker build is dependant on the host ubuntu version that I'm using and not the actual dockerfile.


shouldn't docker build be coherent whatever the ubuntu version I'm using.


-
id3v2 : prefer TDRC for date over TDRL.
4 novembre 2014, par Benoit Fouetid3v2 : prefer TDRC for date over TDRL.
TDRL is what we used as a replacement of TYER, and, according to
http://id3.org/id3v2.4.0-changes :
TYER - Year
This frame is replaced by the TDRC frame, ’Recording time’
[F:4.2.5].
So change TDRL usages to TDRC.Fixes ticket #3694
Signed-off-by : Michael Niedermayer <michaelni@gmx.at>