Recherche avancée

Médias (91)

Autres articles (76)

  • 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 tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

Sur d’autres sites (4968)

  • ffmpeg : is vidstab multithreaded, and/or is there a way to make it perform better on a very high # of cores ?

    30 juillet 2016, par ljwobker

    I’m working on a project where I use the vidstab ffmpeg plugin to stabilize some videos. I’m lucky enough to have access to an extremely fast x86 machine (2 socket, 16 core, 32 thread) but I can’t seem to keep it busy and I’m trying to figure out if it’s a limitation of the toolchain or the config/commands. The workflow is basically 3 steps :

    1. crop the video in terms of both time and dimension (ffmpeg "crop"
      filter)
    2. run vidstabdetect to identify the transformation corrections
    3. run vidstabtransform to apply the transformation and output the
      final video

    When I run the transcode script on this machine, the "crop" pass executes extremely fast, and the htop output from the machine clearly shows all 32 cores(threads) running at nearly 100%.

    When I run the pass with vidstabdetect, htop clearly shows one core running at/near 100%, with all of the other cores hovering in the "few percent" range, and total CPU utilization for the parent PID hovers near 130%. This leads me to believe there must be only one main processing thread, but also several other smaller threads that are consuming at least some parallel time.

    the vidstabtransform pass looks similar, with one core constantly near 100%, and the rest of the cores hovering in the few percent.

    As far as I can tell, there is no way to parallelize the two vidstab processes, as the transform step is completely dependent on the results of the detection pass. There is a single pass option described in the vidstab docs, but the quality isn’t as good so I’m trying to avoid that.

  • Announcing Piwik will end PHP 5.3 support in six months (May 2015)

    20 octobre 2014, par Piwik Core Team — Community

    This post is an important announcement concerning all Piwik users who are using PHP 5.3.x to run Piwik. Piwik project will end support for PHP 5.3 in about six months in May 2015.

    All Piwik users are encouraged to upgrade to the latest PHP 5.5 or PHP 5.6 which brings huge benefits in terms of performance, memory usage, security and overall stability.

    Why is this important ?

    The PHP version 5.3 has reached its End of Life (EOL). Using this old version may expose you to security vulnerabilities and bugs that have been fixed in more recent versions of PHP.

    If you are still using PHP 5.3, note that Piwik will stop supporting this PHP version in May 2015. Around this time Piwik will start requiring PHP 5.4.

    Upgrade your PHP version before it’s too late !

    Learn more

    Learn more about Piwik release schedule :

  • Announcing Piwik will end PHP 5.3 support in six months (May 2015)

    20 octobre 2014, par Piwik Core Team — Community

    This post is an important announcement concerning all Piwik users who are using PHP 5.3.x to run Piwik. Piwik project will end support for PHP 5.3 in about six months in May 2015.

    All Piwik users are encouraged to upgrade to the latest PHP 5.5 or PHP 5.6 which brings huge benefits in terms of performance, memory usage, security and overall stability.

    Why is this important ?

    The PHP version 5.3 has reached its End of Life (EOL). Using this old version may expose you to security vulnerabilities and bugs that have been fixed in more recent versions of PHP.

    If you are still using PHP 5.3, note that Piwik will stop supporting this PHP version in May 2015. Around this time Piwik will start requiring PHP 5.4.

    Upgrade your PHP version before it’s too late !

    Learn more

    Learn more about Piwik release schedule :

Navigation