Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (80)

  • 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 (...)

  • Les vidéos

    21 avril 2011, par

    Comme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
    Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
    Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...)

  • Les sons

    15 mai 2013, par

Sur d’autres sites (4435)

  • 1.3.11 - fixed slideshow problem that was introduced in 1.3.10 and added slight improvements.

    19 octobre 2010, par Jack Moore

    m README m colorbox/jquery.colorbox-min.js m colorbox/jquery.colorbox.js 1.3.11 - fixed slideshow problem that was introduced in 1.3.10 and added slight improvements.

  • 1.3.11 - fixed slideshow problem that was introduced in 1.3.10 and added slight improvements.

    19 octobre 2010, par Jack Moore

    m README m colorbox/jquery.colorbox-min.js m colorbox/jquery.colorbox.js 1.3.11 - fixed slideshow problem that was introduced in 1.3.10 and added slight improvements.

  • Python Azure Function Blob trigger concurrency problem

    22 août 2024, par Mihai Podaru

    I developed an OCR in python using pytesseract and cv2. It takes files for a blob container and extracts text from them. I deployed it to an Azure Function container. I used a container because I need system dependencies (poppler-utils tesseract-ocr ffmpeg libsm6 libxext6).

    


    If I simulate the function locally using Azurite I am able to process multiple files at a time. But if I deploy it to Azure, if I upload 2 files at once, the CPU goes to 100% and blocks there. I figured there is a concurrency problem, because it runs well if I configure the host file like this

    


    "extensions": {
    "blobs": {
      "maxDegreeOfParallelism": 1,
      ...
    }
}


    


    Can I do something about it or are the libraries/dependencies not compatible with concurrency ?

    


Navigation