
Recherche avancée
Autres articles (37)
-
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
Submit enhancements and plugins
13 avril 2011If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone. -
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" (...)
Sur d’autres sites (4724)
-
Merge commit ’781a25e9c419dd66063597cc5d70e8919de60561’
17 septembre 2015, par Hendrik LeppkesMerge commit ’781a25e9c419dd66063597cc5d70e8919de60561’
* commit ’781a25e9c419dd66063597cc5d70e8919de60561’ :
checkasm : v210 : Fix array overwriteMerged-by : Hendrik Leppkes <h.leppkes@gmail.com>
-
Intermitent Connection Issues for FFMPEG Stream capture
22 novembre 2014, par Quentin SpottiswoodeI intend to create a Python shell script to open a connection to an MP3 stream and record the stream over a specified period and save the file to a .mp3 file for distribution. ffmpeg will likely be involved through a shell command, rather than using any kind of python wrapper class.
Occasionally, the source of the stream may encounter connection issues with the internet, resulting in the listening client (ffmpeg) losing it’s connection with the host. Currently ffmpeg discards the recording entirely and forgets about attempting to reconnect to the host.
having had a look through ffmpeg’s extensive documentation, I found myself very confused...
- Is there some method to retain the recording up to the point of the connection failure ?
- Is there a method of automatically re-connecting to the stream when the host reappears, or do I have to catch the error and try a certain number of times ?
- Is there a method of passing the error to the python script in order to create a suitable response ?
Many thanks for your insight :)
-
param_parse : Fix framerate rounding issues
27 juillet 2015, par Henrik Gramner