
Recherche avancée
Autres articles (57)
-
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 ;
-
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 (...)
Sur d’autres sites (4062)
-
Unknown Codec error at ffserver
23 mai 2016, par PotatoI installed ffmpeg following this page, https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu
As you see I enabled x264.
But when I run ffserver, I get/etc/ffserver.conf:16: Unknown VideoCodec: libx264
/etc/ffserver.conf:24: Unknown AudioCodec: libfaacMy conf file is
HTTPPort 8080
RTSPPort 8090
HTTPBindAddress 0.0.0.0
RTSPBindAddress 0.0.0.0
MaxClients 1000
MaxBandwidth 1000000
<feed>
Launch ffmpeg -f v4l2 -i /dev/video0 -f alsa -ac 1 -i hw:1
FileMaxSize 400K
</feed>
<stream>
Format rtp
Feed feed1.ffm
VideoCodec libx264
VideoFrameRate 24
VideoBitRate 100
VideoSize 320x240
#AVPresetVideo default
#AVPresetVideo baseline
AVOptionVideo flags +global_header
AudioCodec libfaac
AudioBitRate 32
AudioChannels 1
AudioSampleRate 22050
AVOptionAudio flags +global_header
</stream>Well, what can I do more.
-
Bash script to convert music from one directory into another
26 octobre 2014, par SinTransI’ve modified this script from the arch forums : https://wiki.archlinux.org/index.php/Convert_Flac_to_Mp3#With_FFmpeg
I’m trying to find specific file types in a directory structure, convert them to another music file type, and place them in a "converted" directory that maintains the same directory structure.
I’m stuck at stripping the string
$b
of its file name.$b
holds the string./converted/alt-j/2012\ an\ awesome\ wave/01\ Intro.flac
Is there a way I can remove the file name from the string ? I don’t think ffmpeg can create/force parent directories of output files.
#!/bin/bash
# file convert script
find -type f -name "*.flac" -print0 | while read -d $'\0' a; do
b=${a/.\//.\/converted/}
< /dev/null ffmpeg -i "$a" "${b[@]/%flac/ogg}"
#echo "${b[@]/%flac/ogg}" -
Performant AV1 encoding, does it exist ?
29 novembre 2022, par V OI'm developing a VoD application as a white label product that runs in a SaaS context using K8s. To enable streaming, I take the input video and re-convert it into HLS segments in multiple version and codecs to reach maximum compatibility.


Yesterday I started implementing AV1 as codec, as it will in near future detach h264 as it's more efficient with the same level of compatibility across all the available browsers.
That was the point where things started to get strange, as I want to have this codec instead of h264 ^^.


If you take a look at the following doc pages from ffmpeg : https://trac.ffmpeg.org/wiki/Encode/AV1


You will notice that there are 3 main encoders available to handle encoding to av1. These are : libaom, SVT-AV1 and rav1e. No matter which one of these I try, the performance is slow, even slower than with HEVC. Recently I came along a news article about Netflix and that they are upgrading their library to AV1. If I take a look at the numbers of media elements Netflix offers, the amount is just huge, and I really don't understand how they did it. From what I know, SVT-AV1 is developed by Netflix in cooperation with Intel, So I assume they somehow rely on hardware encoding using an Intel CPU extension.


Does somebody maybe know more and how they did it ? I really can't imagine that they just do CPU only encoding. A movie would take days to get encoded.


Thanks in advance