
Recherche avancée
Médias (1)
-
Carte de Schillerkiez
13 mai 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Texte
Autres articles (73)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...) -
(Dés)Activation de fonctionnalités (plugins)
18 février 2011, parPour gérer l’ajout et la suppression de fonctionnalités supplémentaires (ou plugins), MediaSPIP utilise à partir de la version 0.2 SVP.
SVP permet l’activation facile de plugins depuis l’espace de configuration de MediaSPIP.
Pour y accéder, il suffit de se rendre dans l’espace de configuration puis de se rendre sur la page "Gestion des plugins".
MediaSPIP est fourni par défaut avec l’ensemble des plugins dits "compatibles", ils ont été testés et intégrés afin de fonctionner parfaitement avec chaque (...)
Sur d’autres sites (8240)
-
im currently trying to concat multiple videos from a array of videos in state with react native ffmpeg but its showing no object or file
20 août 2020, par Suraj LallaI'm trying to concat videos from an array of videos in react native state using react-native ffmpeg,but the error is showing no file created, please help ,
im trying to add an array of objects containing the video uri


-
Revised FATE Test Spec System
9 juin 2010, par Multimedia Mike — FATE ServerFATE involves some database tables that define the test specifications. Like everything else in FATE, the concept could use some improvement. After I prototyped an improved, multithreaded testing client, the next logical revision seemed to be the test spec system.
History
The test spec system has been handled by a single table that includes an FFmpeg command line (with a few possible modifiers thrown in), an integer ID, a human-friendly ID, a description, the expected command line return code, the expected command output, a maximum runtime, and a Boolean to indicate whether the test is to be considered active.Adjunct to this test database is a large corpus of test media named the FATE suite.
At first, the FATE testing script used a direct MySQL database protocol to query the test specs from the server before every build/test cycle. I soon realized this was ludicrously inefficient since the test specs don’t change that often. So I cached the tests in a static file to be retrieved via HTTP, first in Python’s "pickled" (serialized) format, then in an SQLite database.
Planned Upgrades
There are 2 major features I would like to build into the system going forward :- The ability to version the entire suite so that it’s possible to test old branches of FFmpeg
- Another database field to indicate which, if any, other test specs must be executed before this spec can be executed
I think I will take this opportunity to switch the test cache serialization format to JSON. I switched from Python pickling to SQLite because the latter was more portable between languages. JSON has that same benefit. Further, working with JSON data doesn’t require a round trip to disk (i.e., want to generate an SQLite database for sending via HTTP ? It needs to go onto disk first. It’s possible to create and manipulate a database entirely in memory but not fetch the bits).
Things To Research
- Pondering how version control systems operate and what they have to teach regarding how to version this data (including the question of whether I can just use an existing version control mechanism instead of creating my own system)
- Efficient caching mechanism
- Tagging test specs for alternate purposes such as longevity testing
- Learn about web form programming in the 21st century so that it’s not quite as painful to maintain the system.
Preliminary Versioning Concept
Here is one approach I am thinking of : Create test groups. Each test spec is assigned to at least one test group. I can think of at least 2 groups : functional (the base test set in existence that validates functionality) and profiling (the projected test set that will be used for ongoing performance and memory profiling). The web frontend will allow for the creation of labels that will apply to a single group. Doing so will apply that label to all active tests in the group. -
Workaround for webbrowsers buffering live webm streams and introducing a delay (how to play live webm stream)
8 juillet 2014, par CoryGI have webm streams coming from an ffserver (16 streams), managed to get all 16 to load at once within a browser, but whether I am playing just one or 16 there is a delay of 3-5 seconds introduced due to either buffering or the handshake plus some kind of compensation to try and sync the timestamps by the browser itself, which leads to my question :
Is it possible to force a browser playing a webm stream via HTML5’s video tag (I only really care about Chrome, but it’s happening in Firefox too) to play from the actual most recent frame (clients and servers share a common NTP server over the LAN, so they are guaranteed to be synced, if that is a factor) as opposed to maintaining a buffer of several seconds and playing from the start of that buffer ?