Recherche avancée

Médias (0)

Mot : - Tags -/signalement

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

Autres articles (45)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

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

Sur d’autres sites (9698)

  • configure : select iamfenc as movenc dep

    24 février 2024, par Gyan Doshi
    configure : select iamfenc as movenc dep

    Unbreaks movenc compilation in minimal configuration.
    

    Signed-off-by : James Almer <jamrial@gmail.com>
    • [DH] configure

  • Fastest seek speed and decoding with ffmpeg and x265 ProRes

    17 mai 2018, par Christopher Jarvis

    I’m trying to optimize seek speed with x265. No matter what encoding settings I try, ProRes still seeks more quickly/gracefully. This makes sense since it was built for editing, but I’m sure there’s got to be something I’m missing to better improve x265.

    So far, -tune fastdecode, keyint=1, maxrate and -b (to remove B Frame calculations) yield the best results, but they’re still unsatisfactory. I’ve been pouring over the docs but there’s so much jargon I just don’t understand. Perhaps another codec like VP9 / WebM would be better for this purpose ?

    From what I can tell, there’s no bottleneck with CPU, read speed or RAM... or GPU for that matter. Monitoring these processes show minimal drain. Is there just an amount of decoding in a highly compressed format like x265 that can’t be circumvented ?

    Thank you in advance for your help.

  • Revision afd2f68dae : Revert "VP9_COPY_CONVOLVE_SSE2 optimization" This reverts commit a5e97d874b16ae

    5 août 2015, par James Zern

    Changed Paths :
     Modify /vpx_dsp/x86/vpx_convolve_copy_sse2.asm



    Revert "VP9_COPY_CONVOLVE_SSE2 optimization"

    This reverts commit a5e97d874b16ae5826b68515f1e35ffb44361cf8.

    Additionally :
    Revert "vpx_convolve_copy_sse2 : fix win64"

    This reverts commit 22a8474fe7ec30d96f746dc6e4b23771758c071e.

    This change performs poorly on various x86_64 devices affecting
    performance by 1-3% at 1080P. Performance on chromebook like devices was
    mixed neutral to slightly negative, so there should be minimal change
    there.

    Change-Id : I95831233b4b84ee96369baa192a2d4cc7639658c

Navigation