Recherche avancée

Médias (1)

Mot : - Tags -/censure

Autres articles (55)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

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

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-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

Sur d’autres sites (5335)

  • Google Analytics Sampling : Why It Matters and How to Avoid It

    21 octobre 2024, par Daniel Crough — Analytics Tips

    When marketing decisions rely on website analytics, accuracy matters.
    However, Google Analytics and other analytics platforms sample data to
    generate reports, which can sometimes misrepresent the true data trends.

    Read More

  • ffmpeg won't execute properly in google app engine standard nodejs

    3 septembre 2019, par tommyc38

    I have tried for three full days to get GAE (standard - nodejs) to run a simple video transcoder from MOV to MP4 using ffmpeg. I have tried using ffluent-ffmpeg, kicking off a child process (e.g. spawn), and nothing works. As soon as it hits the call to the executable it always errors. I have confirmed ffmpeg is installed and even tried using ffmpeg-static. Moreover, I have it working on my local machine with no problems (using all of the aforementioned ways).

    I have also tried logging the errors and nothing is really all that helpful. I can see its working through any installed package including ffmpeg (system package).

    Below is the pseudo code...step three is where the problem occurs.

    1. Send file name to GAE endpoint
    2. Download the file from google cloud storage to a temp file
    3. Transcode using ffmpeg
    4. Upload temp file to google cloud storage
    5. Remove old google cloud storage file
    6. Remove temp file

    The file I am using to test is 6MB...a 5 second video I took on my iPhone. Thank you in advance.

    UPDATE : I successfully deployed the exact same code to Node Flex environment and everything works great. I wasn’t able to get any errors in the standard environment that directed me where to look but my guess is it has something to do with how it stores the file I pipe into FFMPEG on GAE Node Standard. The docs say its a virtual file system that uses RAM. I’d love to hear if anybody managed to get it working in the standard environment.

  • Revision 93a0189936 : Use 8 threads by default for VP9 encodes BUG=https://code.google.com/p/webm/iss

    4 mars 2015, par Frank Galligan

    Changed Paths :
     Modify /vp9/vp9_cx_iface.c



    Use 8 threads by default for VP9 encodes

    BUG=https://code.google.com/p/webm/issues/detail?id=964

    Change-Id : I70679d0f139b8e0962f7e19eb56b34060953e9b0

Navigation