
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 (20)
-
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 (...)
-
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
-
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...)
Sur d’autres sites (4136)
-
lavc : don’t set AVFrame.pts to random numbers in decoders.
27 octobre 2013, par Anton Khirnov -
OS X Mavericks broken OpenCV VideoCapture frame numbers ?
20 novembre 2013, par MattPFresh install of Mavericks, managed to install ffmpeg via homebrew and compile the latest OpenCV at time of writing. My code is written in Python (though this shouldn't affect this issue) and basically navigates a video file using the
VideoCapture
class with the properties set frame position and get current position.The issue is, on prior versions of OS X, various Linux and Windows boxes, this works without issue. Each frame number is of the format i.0, where i is the current frame number (why it is a float anyway is confusing, alas it's how OpenCV gives it back). However, on this setup I get frame progressions like :
0.0 -> 1.3972597329753 -> 2.999999999 -> 3.9999999 -> 5.0 -> 6.252323552
This makes using the properties for getting / setting the current frame position impossible and, as one would imagine, causes the automated playback thereof to fail. I can only assume ffmpeg is reporting things odd such that OpenCV is incorrectly calculating frames, but have been unable to rectify this.
Has anyone any insight into the problem, and/or possible solution ? Thanks.
-
Updated CommonJS support and version numbers.
1er janvier 2015, par blueimpUpdated CommonJS support and version numbers.