
Recherche avancée
Médias (1)
-
La conservation du net art au musée. Les stratégies à l’œuvre
26 mai 2011
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (99)
-
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 (...) -
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 ;
Sur d’autres sites (10283)
-
av1/h264_metadata : Don't reinitialize data
20 juin 2019, par Andreas Rheinhardtav1/h264_metadata : Don't reinitialize data
If the relevant elements (the color description elements for AV1 and the
VUI elements in general for H.264 (since 1156b507)) are absent, then their
correct values (usually meaning unknown) have already been inferred by
the reading process, so that it is unnecessary to initialize them again
in the av1/h264_metadata filters even when they were initially absent.Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
-
dnxhddec : Decode and use interlace mb flag
26 septembre 2015, par Christophe Gisquetdnxhddec : Decode and use interlace mb flag
This bit is 1 in some samples, and seems to coincide with interlaced
mbs and CID1260. 2008 specs do not know about it, and maintain qscale
is 11 bits. This looks oversized, but may help larger bitdepths.Currently, it leads to an obviously incorrect qscale value, meaning
its syntax is shifted by 1. However, reading 11 bits also leads to
obviously incorrect decoding : qscale seems to be 10 bits.However, as most profiles still have 11bits qscale, the feature is
restricted to the CID1260 profile (this flag is dependent on
a higher-level flag located in the header).The encoder writes 12 bits of syntax, last and first bits always 0,
which is now somewhat inconsistent with the decoder, but ends up with
the same effect (progressive + reserved bit).Signed-off-by : Vittorio Giovara <vittorio.giovara@gmail.com>
-
JavaCV FFmpegFrameRecorder properties explanation needed
29 décembre 2014, par LeronI’m using
FFmpegFrameRecorder
to get the video input from my webcam and record it into a video file. The problem is that I’m building my application using a few different demo source codes that I found and I use properties some of which are not completely clear to me.First, here is my code snippet :
FFmpegFrameRecorder recorder = new FFmpegFrameRecorder(FILENAME, grabber.getImageWidth(),grabber.getImageHeight());
recorder.setVideoCodec(13);
recorder.setFormat("mp4");
recorder.setPixelFormat(avutil.PIX_FMT_YUV420P);
recorder.setFrameRate(30);
recorder.setVideoBitrate(10 * 1024 * 1024);
recorder.start();- setVideoCodec(13) - What is the meaning of this
(13)
how can I understand what actual codec stands behind any number ? - setPixelFormat - Just get this, don’t know what it’s doing in general
- setFrameRate(30) - I think this should be pretty clear but still what is the logic behind what frame rate we choose (isn’t the high the better ?)
- setVideoBitrate(10*1024*1024) - again almost no idea what this does and what’s the logic behind the numbers ?
At the end I just want to mention one last problem that I get recording video like this. If the actual length of the video is let’s say 20secs. When I play the video file created from the program it runs significantly faster. Can’t tell if it’s exactly 2 times faster than it should be but in general if I record a 20sec video then it’s played for about 10secs. What may cause this and how can I fix it ?
- setVideoCodec(13) - What is the meaning of this