Recherche avancée

Médias (1)

Mot : - Tags -/getid3

Autres articles (111)

  • Possibilité de déploiement en ferme

    12 avril 2011, par

    MediaSPIP peut être installé comme une ferme, avec un seul "noyau" hébergé sur un serveur dédié et utilisé par une multitude de sites différents.
    Cela permet, par exemple : de pouvoir partager les frais de mise en œuvre entre plusieurs projets / individus ; de pouvoir déployer rapidement une multitude de sites uniques ; d’éviter d’avoir à mettre l’ensemble des créations dans un fourre-tout numérique comme c’est le cas pour les grandes plate-formes tout public disséminées sur le (...)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Selection of projects using MediaSPIP

    2 mai 2011, par

    The examples below are representative elements of MediaSPIP specific uses for specific projects.
    MediaSPIP farm @ Infini
    The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)

Sur d’autres sites (8203)

  • lavu/hwcontext_qsv : add support for AV_PIX_FMT_VUYX on Linux

    6 septembre 2022, par Haihao Xiang
    lavu/hwcontext_qsv : add support for AV_PIX_FMT_VUYX on Linux

    AV_PIX_FMT_VUYX is used for 8bit 4:4:4 content in FFmpeg VAAPI, so
    
AV_PIX_FMT_VUYX should be used for 8bit 4:4:4 content in FFmpeg QSV too
    
because QSV is based on VAAPI on Linux. However the SDK only declares
    
support for AYUV and does nothing with the alpha, so this commit fudged
    
a mapping between AV_PIX_FMT_VUYX and MFX_FOURCC_AYUV.
    

    Reviewed-by : Philip Langdale <philipl@overt.org>
    
Signed-off-by : Haihao Xiang <haihao.xiang@intel.com>
    • [DH] libavutil/hwcontext_qsv.c

  • lavu/hwcontext_qsv : Make sure hardware vendor is Intel for qsv on d3d11va

    28 novembre 2023, par Haihao Xiang
    lavu/hwcontext_qsv : Make sure hardware vendor is Intel for qsv on d3d11va

    When multiple hardwares are available, the default one might not be
    
Intel Hardware. We can use option vendor_id to choose the required
    
vendor.
    

    Tested-by : Artem Galin <artem.galin@intel.com>
    
Signed-off-by : Haihao Xiang <haihao.xiang@intel.com>
    • [DH] libavutil/hwcontext_qsv.c

  • lavc/vaapi_h264 : Fix merging fields in DPB with missing references

    8 mai 2024, par David Rosca
    lavc/vaapi_h264 : Fix merging fields in DPB with missing references

    If there are missing references, h264 decode does error concealment
    
by copying previous refs which means there will be duplicated surfaces.
    
Check long_ref and frame_idx in addition to surface when looking for
    
the other field to avoid trying to merge with wrong picture.
    
Also allow to merge with multiple pictures in case there are duplicates
    
of the other field.
    

    Signed-off-by : David Rosca <nowrep@gmail.com>
    
Signed-off-by : Haihao Xiang <haihao.xiang@intel.com>
    • [DH] libavcodec/vaapi_h264.c

Navigation