Recherche avancée

Médias (91)

Autres articles (82)

  • Le plugin : Gestion de la mutualisation

    2 mars 2010, par

    Le plugin de Gestion de mutualisation permet de gérer les différents canaux de mediaspip depuis un site maître. Il a pour but de fournir une solution pure SPIP afin de remplacer cette ancienne solution.
    Installation basique
    On installe les fichiers de SPIP sur le serveur.
    On ajoute ensuite le plugin "mutualisation" à la racine du site comme décrit ici.
    On customise le fichier mes_options.php central comme on le souhaite. Voilà pour l’exemple celui de la plateforme mediaspip.net :
    < ?php (...)

  • Gestion de la ferme

    2 mars 2010, par

    La ferme est gérée dans son ensemble par des "super admins".
    Certains réglages peuvent être fais afin de réguler les besoins des différents canaux.
    Dans un premier temps il utilise le plugin "Gestion de mutualisation"

  • La gestion des forums

    3 novembre 2011, par

    Si les forums sont activés sur le site, les administrateurs ont la possibilité de les gérer depuis l’interface d’administration ou depuis l’article même dans le bloc de modification de l’article qui se trouve dans la navigation de la page.
    Accès à l’interface de modération des messages
    Lorsqu’il est identifié sur le site, l’administrateur peut procéder de deux manières pour gérer les forums.
    S’il souhaite modifier (modérer, déclarer comme SPAM un message) les forums d’un article particulier, il a à sa (...)

Sur d’autres sites (13243)

  • Revision eca93642e2 : Add a speed feature to give the tighter search range Add a speed feature to giv

    14 août 2014, par Pengchong Jin

    Changed Paths :
     Modify /vp9/encoder/vp9_encodeframe.c


     Modify /vp9/encoder/vp9_speed_features.c


     Modify /vp9/encoder/vp9_speed_features.h



    Add a speed feature to give the tighter search range

    Add a speed feature to give the tighter partition search
    range. Before partition search, calculate the histogram
    of the partition sizes of the left, above and previous
    co-located blocks of the current block. If the variance of
    observed partition sizes is small enough, adjust the search
    range around the mean partition size, which will be tigher.

    The feature is currently turned on at speed 2. Experiments on
    sample youtube clips show on average the runtime is reduced
    by 3-7%.

    For hard stdhd clips :
    park_joy_1080p @ 15000kbps : 509251 ms -> 491953 ms (3.3%)
    pedestrian_area_1080p @ 2000kbps : 223941 ms -> 214226 ms (4.3%)

    The PSNR performance is changed :
    derf : -0.112%
    yt : -0.099%
    hd : -0.090%
    stdhd :-0.102%

    Change-Id : Ie205ec5325bf92ec5676c243e30ba9d0adca10f2

  • Revision 9f79259e54 : adapt the adjustment limit for rate correction factor in RTC mode Rate correcti

    13 novembre 2014, par Yaowu Xu

    Changed Paths :
     Modify /vp9/encoder/vp9_ratectrl.c



    adapt the adjustment limit for rate correction factor in RTC mode

    Rate correction factor is used to correct the estimated rate for any
    given quantizer, and feeds into rate control for quantizer selection.
    We make use of the actual bits used to calculate this rate correction
    factor with an adjustment limit to prevent over-adjustment.

    This commit adapts the adjustment limit to the difference between the
    estimated bits and the actual bits, allows the adjustment limit to vary
    between 0.125 (when estimate is close to actual) and 0.625 (when there
    is >10X factor off between estimated and actual bits). By doing this,
    the commit appears to have largely corrected two observed issues :
    1. Adjustment is too slow when the actual bits used is way off from
    estimate due to the small adjustment limit.
    2. Extreme oscillating quantizer choices due to the feedback loop.

    Change-Id : I4ee148d2c9d26d173b6c48011313ddb07ce2d7d6

  • Make video frames from a livestream identifiable across multiple clients

    23 septembre 2016, par mschwaig

    I need to distribute a video stream from a live source to several clients with the additional requirement that each frame is identifiable across all clients.

    I have already done research into the topic, and I have arrived at a possible solution that I can share. My solution seems suboptimal and this is my first experience of working with video streams, so I want to see if somebody knows a better way.

    The reason why I need to be able to identify specific frames within the video stream is that the streaming clients need to be able to talk about the time differences between events each of them identifies in their video stream.

    A little clarifying example

    I want to enable the following interaction :

    • Two client applications Dewey and Stevie connect to the streaming server
    • Dewey displays the stream and Stevie saves it to disk
    • Dewey identifies a specific video frame that is of interest to Stevie, so he wants to tell Stevie about it
    • Dewey extracts some identifying information from the video frame and sends it to Stevie
    • Stevie uses the identifying information to extract the same frame from the copy of the livestream he is currently saving

    Dewey cannot send the frame to Stevie directly, because Malcolm and Reese also want to tell him about specific video frames and Stevie is interested in the time difference between their findings.

    Suggested solution

    The solution that I found was using ffserver to broadcast a RTP stream and use the timestamps from the RTCP packets to identify frames. These timestamps are normally used to synchronize audio and video, and not to provide a shared timeline across several clients, which is why I am skeptical this is the best way to solve my problem.

    It also seems beneficial to have frame numbers, like an increasing counter of frames instead of arbitrary timestamps which increase by some perhaps varying offset as for my application I also have to reference neighboring frames and it seems easier to compute time differences from frame numbers, than the other way around.