Recherche avancée

Médias (0)

Mot : - Tags -/xmp

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

Autres articles (112)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

Sur d’autres sites (11560)

  • Introducing WebM, an open web media project

    20 mai 2010, par noreply@blogger.com (christosap)

    A key factor in the web’s success is that its core technologies such as HTML, HTTP, TCP/IP, etc. are open and freely implementable. Though video is also now core to the web experience, there is unfortunately no open and free video format that is on par with the leading commercial choices. To that end, we are excited to introduce WebM, a broadly-backed community effort to develop a world-class media format for the open web.

    WebM includes :

    • VP8, a high-quality video codec we are releasing today under a BSD-style, royalty-free license
    • Vorbis, an already open source and broadly implemented audio codec
    • a container format based on a subset of the Matroska media container

    The team that created VP8 have been pioneers in video codec development for over a decade. VP8 delivers high quality video while efficiently adapting to the varying processing and bandwidth conditions found on today’s broad range of web-connected devices. VP8’s efficient bandwidth usage will mean lower serving costs for content publishers and high quality video for end-users. The codec’s relative simplicity makes it easy to integrate into existing environments and requires less manual tuning to produce high quality results. These existing attributes and the rapid innovation we expect through the open-development process make VP8 well suited for the unique requirements of video on the web.

    A developer preview of WebM and VP8, including source code, specs, and encoding tools is available today at www.webmproject.org.

    We want to thank the many industry leaders and web community members who are collaborating on the development of WebM and integrating it into their products. Check out what Mozilla, Opera, Google Chrome, Adobe, and many others below have to say about the importance of WebM to the future of web video.


    Telestream

    Posted by Jeremy Doig, Engineering Director of video and Mike Jazayeri, Group Product Manager, Google

  • Introducing WebM, an open web media project

    19 mai 2010, par noreply@blogger.com (christosap)

    A key factor in the web’s success is that its core technologies such as HTML, HTTP, TCP/IP, etc. are open and freely implementable. Though video is also now core to the web experience, there is unfortunately no open and free video format that is on par with the leading commercial choices. To that end, we are excited to introduce WebM, a broadly-backed community effort to develop a world-class media format for the open web.

    WebM includes :

    • VP8, a high-quality video codec we are releasing today under a BSD-style, royalty-free license
    • Vorbis, an already open source and broadly implemented audio codec
    • a container format based on a subset of the Matroska media container

    The team that created VP8 have been pioneers in video codec development for over a decade. VP8 delivers high quality video while efficiently adapting to the varying processing and bandwidth conditions found on today’s broad range of web-connected devices. VP8’s efficient bandwidth usage will mean lower serving costs for content publishers and high quality video for end-users. The codec’s relative simplicity makes it easy to integrate into existing environments and requires less manual tuning to produce high quality results. These existing attributes and the rapid innovation we expect through the open-development process make VP8 well suited for the unique requirements of video on the web.

    A developer preview of WebM and VP8, including source code, specs, and encoding tools is available today at www.webmproject.org.

    We want to thank the many industry leaders and web community members who are collaborating on the development of WebM and integrating it into their products. Check out what Mozilla, Opera, Google Chrome, Adobe, and many others below have to say about the importance of WebM to the future of web video.


    Telestream

    Posted by Jeremy Doig, Engineering Director of video and Mike Jazayeri, Group Product Manager, Google

  • avutils/hwcontext : When deriving a hwdevice, search for existing device in both direc...

    25 novembre 2021, par Soft Works
    avutils/hwcontext : When deriving a hwdevice, search for existing device in both directions

    The test /libavutil/tests/hwdevice checks that when deriving a device
    
from a source device and then deriving back to the type of the source
    
device, the result is matching the original source device, i.e. the
    
derivation mechanism doesn't create a new device in this case.
    

    Previously, this test was usually passed, but only due to two different
    
kind of flaws :
    

    1. The test covers only a single level of derivation (and back)
    

    It derives device Y from device X and then Y back to the type of X and
    
checks whether the result matches X.
    

    What it doesn't check for, are longer chains of derivation like :
    

    CUDA1 > OpenCL2 > CUDA3 and then back to OpenCL4
    

    In that case, the second derivation returns the first device (CUDA3 ==
    
CUDA1), but when deriving OpenCL4, hwcontext.c was creating a new
    
OpenCL4 context instead of returning OpenCL2, because there was no link
    
from CUDA1 to OpenCL2 (only backwards from OpenCL2 to CUDA1)
    

    If the test would check for two levels of derivation, it would have
    
failed.
    

    This patch fixes those (yet untested) cases by introducing forward
    
references (derived_device) in addition to the existing back references
    
(source_device).
    

    2. hwcontext_qsv didn't properly set the source_device
    

    In case of QSV, hwcontext_qsv creates a source context internally
    
(vaapi, dxva2 or d3d11va) without calling av_hwdevice_ctx_create_derived
    
and without setting source_device.
    

    This way, the hwcontext test ran successful, but what practically
    
happened, was that - for example - deriving vaapi from qsv didn't return
    
the original underlying vaapi device and a new one was created instead :
    
Exactly what the test is intended to detect and prevent. It just
    
couldn't do so, because the original device was hidden (= not set as the
    
source_device of the QSV device).
    

    This patch properly makes these setting and fixes all derivation
    
scenarios.
    

    (at a later stage, /libavutil/tests/hwdevice should be extended to check
    
longer derivation chains as well)
    

    Reviewed-by : Lynne <dev@lynne.ee>
    
Reviewed-by : Anton Khirnov <anton@khirnov.net>
    
Tested-by : Wenbin Chen <wenbin.chen@intel.com>
    
Signed-off-by : softworkz <softworkz@hotmail.com>
    
Signed-off-by : Haihao Xiang <haihao.xiang@intel.com>
    • [DH] libavutil/hwcontext.c
    • [DH] libavutil/hwcontext.h
    • [DH] libavutil/hwcontext_internal.h
    • [DH] libavutil/hwcontext_qsv.c

Navigation