
Recherche avancée
Médias (1)
-
GetID3 - Bloc informations de fichiers
9 avril 2013, par
Mis à jour : Mai 2013
Langue : français
Type : Image
Autres articles (50)
-
Participer à sa traduction
10 avril 2011Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
Actuellement MediaSPIP n’est disponible qu’en français et (...) -
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
-
Les formats acceptés
28 janvier 2010, parLes commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
ffmpeg -codecs ffmpeg -formats
Les format videos acceptés en entrée
Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
Les formats vidéos de sortie possibles
Dans un premier temps on (...)
Sur d’autres sites (8799)
-
How to read .mp4 files in opencv
9 mai 2016, par NoahI am totally newbie in OpenCV, C++. Trying to read an
mp4
video but found OpenCV does not supportmp4
, it only readsavi
(I am not sure whether I am write or wrong). After an online research came to knowffmpeg
is the best option to convertmp4
toavi
for further processing.I am using OpenCV 3.0 with visual studio 2012. I saw there is a
dll
file,opencv_ffmpeg300.dll
in OpenCVC:\opencv\build\x86\vc11\bin
folder. Is there any way I can use thisdll
file to read and convert my video ?It will be really appreciating if someone can provide me some guidelines, I am lost in the OpenCV world totally.
For video,
Video I/O:
Video for Windows: YES
DC1394 1.x: NO
DC1394 2.x: NO
FFMPEG: YES (prebuilt binaries)
codec: YES (ver 55.18.102)
format: YES (ver 55.12.100)
util: YES (ver 52.38.100)
swscale: YES (ver 2.3.100)
resample: NO
gentoo-style: YES
OpenNI: NO
OpenNI PrimeSensor Modules: NO
OpenNI2: NO
PvAPI: NO
GigEVisionSDK: NO
DirectShow: YES
Media Foundation: NO
XIMEA: NO
Intel PerC: NO -
avcodec/mpegaudiodec_template : Check CRCs for layer1 and layer2
3 août 2020, par Michael Niedermayeravcodec/mpegaudiodec_template : Check CRCs for layer1 and layer2
This differs from the MPEG specification as the actual real world
files do compute their CRC over variable areas and not the fixed
ones listed in the specification. This is also the reason for
the complexity of this code and the need to perform the CRC
check for layer2 in the middle of layer2 decoding.Reviewed-by : Lynne <dev@lynne.ee>
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc> -
avcodec/vdpau : Support for VDPAU accelerated HEVC decoding
13 juin 2015, par Philip Langdaleavcodec/vdpau : Support for VDPAU accelerated HEVC decoding
This change introduces basic support for HEVC decoding through vdpau.
Right now, there are problems with the nvidia driver/library implementation
that mean that frames are incorrectly laid out in memory when they are
returned from the decoder, and it is normally impossible to recover the
complete decoded frame due to loss of data from alignment inconsistencies.I obviously hope that nvidia will be fixing it in due course - I’ve verified
the problems exist with their example application.As such, this support is not useful for any real world application, but I
believe that it is correct (with the caveat that the mangled frames may hide
problems) and will work properly once the nvidia problem is fixed.Right now it appears that any file encoded by x265 or nvenc is decoded
correctly, but that’s because these files don’t use a bunch of HEVC
features.Quick summary :
Features that seem to work :
1) Short Term References
2) Scaling Lists
3) TilingFeatures with known problems :
1) Long Term References
It’s hard to tell what’s going on here. After I read the nvidia example
app that does not set the IsLongTerm flag on LTRs, and changed my code,
a bunch of frames using LTR started to display correctly, but there
are still samples with glitches that are related to LTRs.In terms of real world files, both x265 and nvenc only use short term
refs from this list. The divx encoder seems similar.Signed-off-by : Philip Langdale <philipl@overt.org>