Recherche avancée

Médias (1)

Mot : - Tags -/musée

Autres articles (38)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP 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 (8283)

  • How do I limit resources for ffmpeg, called from a python-script, running in a docker container ?

    26 juillet 2019, par wotanii

    I deployed a service, that periodically does video encoding on my server ; And every time it does, all other services slow down significantly. The encoding is hidden under multiple layers of abstraction. Limiting any of those layers would be fine. (e.g. limiting the docker-container would work just as well as limiting the ffmpeg-sub process.)

    My Stack :

    1. VPS (ubuntu:zesty)
    2. docker-compose
    3. docker-container (ubuntu:zesty)
    4. python
    5. ffmpeg (via subprocess.check_call() in python)

    What I want to limit :

    • CPU : single core
    • RAM : max 2 GB
    • HDD : max 4 GB

    It would be possible to recompile ffmpeg if needed.

    What would be the place to put limits in this stack ?

  • FFmpeg post video stream to a webservice cause error 'chunked body too large'

    29 novembre 2017, par W. Dragon

    I have a webservice which is developped by Tornado. Now I use FFmpeg to post video stream data to service. After some time, the process is down and rise an error like :

    [I 170928 07:33:55 http1connection:253] Malformed HTTP message from 172.18.130.125: chunked body too large

    I use command like :

    ffmpeg -s 1240x720 -f video4linux2 -i /dev/video0 -b:v 0 -q:v 1 -f mpegts -c:v mpeg1video -b 800k -r 30 http://10.4.245.152:9090/video/live

    Should I use ffmpeg to continue post video stream to a webservice ?

  • Evolution #3802 (Nouveau) : Rendre obsolète le filtre

    3 juillet 2016, par jluc -

    La doc http://www.spip.net/fr_article1823.html préconise (#LOGO_DOCUMENT comme manière d"afficher une vignette cliquable pointant vers le document multimédia".

    Cette forme d’écriture est dérogatoire : une balise appelée comme filtre. Ne faudrait il déclarer cette écriture obsolète dans SPIP 3.2 puis la virer dans SPIP 3.5 ? Quitte à fournir quelquechose de grammaticalement plus banal pour fournir le même service.
    Outre l’apprentissage de spip, ça simplifiera surement le parseur.

Navigation