Recherche avancée

Médias (0)

Mot : - Tags -/publication

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

Autres articles (92)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

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

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

Sur d’autres sites (10009)

  • Failed to hard-ware accelerate video decoding via Tesla P40

    20 mai 2018, par Potemkin

    While I am writing a surveillance video recognition demo, I find it is much slower to simply play a video in the server(Xeon E5-2680 2.4GHz, Tesla P40) than in my laptop(i7-8550 1.8GHz, Intel UHD Graphics 620).

    I use DXVA-Checker to see the video decoder device, and notice that my laptop use the GPU for decoding, but the server use no GPU for the job. Then I check ’nvidia-smi’, and it shows all of GPUs are running in TCC driver model, not WDDM driver model. And I cannot turn it to WDDM because nvidia-smi says it is not supported.

    The video play demo is written via OPENCV, in which the video decoding part is from ffmpeg. The server runs in Windows-server-2012, and my laptop is on Windows 10.

    The question is how can I get the server decoding videos with GPUs, and is this the reason for the slowness or there is something else ?

  • Vc1 video playback jerking

    12 novembre 2015, par kopalvich

    I’m trying to play vc1 coded video in matroska container.

    For that I’m using ffmpeg’s av_read_frame function and a sertain video driver, which requires AVPacket’s data to be prefixed by PES header.
    In AVPacket only dts field is valid, pts is AV_NOPTS_VALUE. I write dts value into PES header instead of pts.

    Video driver logs constant framerate change from 23976 to 24000 and vice versa. The video jerks. Although I put framerate into PES header (value 23976 is what ffmpeg’s probing gives), but apparently, it’s changing according to current packet’s pts.

    I tried to look at AVCodecParserContext’s pts_dts_delta and dts_ref_dts_delta but they are of AV_NOPTS_VALUE, its pts and dts are the same as of AVPacket

    Please advise how to get proper pts values, or what to do to solve it.

    Thanks.

    EDIT :
    I saw in ffplay.c they use av_frame_get_best_effort_timestamp but that’s after decoding by ffmpeg’s means, which I cannot afford.

  • hwcontext_qsv : Try to select a matching VAAPI device by default

    6 mai 2019, par Mark Thompson
    hwcontext_qsv : Try to select a matching VAAPI device by default

    Tries to find a device backed by the i915 kernel driver and loads the iHD
    
VAAPI driver to use with it.  This reduces confusion on machines with
    
multiple DRM devices and removes the surprising requirement to set the
    
LIBVA_DRIVER_NAME environment variable to use libmfx at all.
    • [DH] libavutil/hwcontext_qsv.c

Navigation