
Recherche avancée
Autres articles (18)
-
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" (...) -
Other interesting software
13 avril 2011, parWe don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
We don’t know them, we didn’t try them, but you can take a peek.
Videopress
Website : http://videopress.com/
License : GNU/GPL v2
Source code : (...)
Sur d’autres sites (7153)
-
pngdec : set correct range
7 mai 2015, par wm4pngdec : set correct range
AV_PIX_FMT_GRAY8/16 are considered YUV formats, and the color_range is
not set - so the API user will have to assume limitted range. (Unless
the API user adds a special-case for the PNG decoder.)Just export the correct range - full range.
Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
-
rtsp : Don’t warn about unparsed time ranges
22 avril 2015, par Martin Storsjörtsp : Don’t warn about unparsed time ranges
This removes the error logging added in 4e54432164.
This avoids warnings about "Invalid interval start specification ’now’"
for live rtsp streams.We only try to parse some of the many valid values for time ranges
in RTSP - the other ones are fully valid but not interesting for the
use case in rtsp.c, so we shouldn’t warn about them.(Parsing the time ranges is needed to allow seeking, but e.g. setting
the current realtime clock for the start time doesn’t make sense.
av_parse_time has got a different mode for parsing absolute times
as well, which can handle the special case "now", but that doesn’t
make much sense for this particular use in rtsp.c.)Signed-off-by : Martin Storsjö <martin@martin.st>
-
rtsp : Don’t warn about unparsed time ranges
22 avril 2015, par Martin Storsjörtsp : Don’t warn about unparsed time ranges
This removes the error logging added in 4e54432164.
This avoids warnings about "Invalid interval start specification ’now’"
for live rtsp streams.We only try to parse some of the many valid values for time ranges
in RTSP - the other ones are fully valid but not interesting for the
use case in rtsp.c, so we shouldn’t warn about them.(Parsing the time ranges is needed to allow seeking, but e.g. setting
the current realtime clock for the start time doesn’t make sense.
av_parse_time has got a different mode for parsing absolute times
as well, which can handle the special case "now", but that doesn’t
make much sense for this particular use in rtsp.c.)Signed-off-by : Martin Storsjö <martin@martin.st>