Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

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

Autres articles (37)

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

  • Changer son thème graphique

    22 février 2011, par

    Le thème graphique ne touche pas à la disposition à proprement dite des éléments dans la page. Il ne fait que modifier l’apparence des éléments.
    Le placement peut être modifié effectivement, mais cette modification n’est que visuelle et non pas au niveau de la représentation sémantique de la page.
    Modifier le thème graphique utilisé
    Pour modifier le thème graphique utilisé, il est nécessaire que le plugin zen-garden soit activé sur le site.
    Il suffit ensuite de se rendre dans l’espace de configuration du (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

Sur d’autres sites (8970)

  • fftools/opt_common : check the return value of av_hwdevice_get_type_name before printi...

    12 septembre 2022, par James Almer
    fftools/opt_common : check the return value of av_hwdevice_get_type_name before printing it

    It may be NULL, as is the case for D3D11VA_VLD.
    

    Running "ffmpeg -h decoder=h264" on a Windows build
    

    Before :
    
Decoder h264 [H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10] :
    
    Supported hardware devices : dxva2 (null) d3d11va cuda
    

    After :
    
Decoder h264 [H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10] :
    
    Supported hardware devices : dxva2 d3d11va cuda
    

    Signed-off-by : James Almer <jamrial@gmail.com>
    • [DH] fftools/opt_common.c

  • FFmpeg : Encode x264 with AMD GPU on Windows ?

    20 septembre 2023, par ZeroTek

    I am currently trying to record a Video on my Lenovo Laptop with its Built-In Webcam using FFmpeg on Windows 10. One of my goals is to keep the CPU Usage as low as possible, that's why i want to push the h264 encoding to the GPU. &#xA;Now it gets a bit tricky here with my Laptop. Because it uses two GPUs. The first GPU is a Intel HD 5500 Graphics Unit as Part of the CPU. This one is most likly used for non-demanding Applications like office etc. to save Energy. The other one is a AMD R5 M330 that will be used for graphic intense applications like gaming.

    &#xA;&#xA;

    Currently, i am using the following command to encode the Webcam Stream on the Intel HD GPU :

    &#xA;&#xA;

    ffmpeg -f dshow -vcodec mjpeg -video_size 1280x720 -framerate 30 video="Lenovo EasyCamera":audio="Mikrofon (Realtek High Definition Audio)" -c:v h264_qsv -g 60 -q 28 -look_ahead 0 -preset:v faster -c:a aac -q:a 0.6 -r 30 output.mp4&#xA;

    &#xA;&#xA;

    This does work so far but it seems this GPU does not have enough Power to keep up with the framerate on higher bitrates or with a high amount of i-frames. The Video starts lacking and skipping frames. If i am using CPU encoding everything works smooth.

    &#xA;&#xA;

    Now that my Laptop got that second AMD GPU with a lot more Power it would be a nice Try to encode on that one, but i can't find any information about how to encode on AMD Hardware on Windows 10. So my question is : How does the ffmpeg command look like to use AMD Hardware for h264 encoding ?

    &#xA;

  • vulkan_decode : remove informative queries

    24 décembre 2024, par Lynne
    vulkan_decode : remove informative queries

    We queried the decoder whether it was able to decode sucessfully, but
    
since we operated asynchronously, we weren't able to do anything with
    
this information but let the user know decoding failed for the previous
    
frame(s).
    

    Since we parse the slice headers ourselves and we're reasonably sure we
    
can decode before actually starting to decode, this was rarely triggered
    
on corrupt data, and hardware's understanding of whether there was an error
    
or not is vague.
    

    There's also a semantic problem with our use of the queries - if there's
    
a seek, we flush, but what happens to the queries is vague according to
    
the spec. Most hardware dealt fine, since queries are nothing more than
    
GPU memory with integers stored. But with Intel, they seem to be more of
    
a register to which a driver must keep track of, leading to issues if there's
    
been a reset (seek) and we query the previous submission before the seek.
    

    Just get rid of them. The query code is still used in encoding.
    

    This fixes seeking with HEVC and AV1 on Intel.
    • [DH] libavcodec/vulkan_decode.c

Navigation