Changes between Initial Version and Version 1 of Ticket #19604, comment 10


Ignore:
Timestamp:
04/10/2024 02:18:49 AM (12 months ago)
Author:
ken@…

Legend:

Unmodified
Added
Removed
Modified

  • TabularUnified Ticket #19604, comment 10

    initial v1  
    66> Thanks, I guess the most severe thing will be qtwebengine this time...
    77
    8 I've just cloned current branches of qtwebengine and its chromium stuff. In 112-based chromium it looks as if they took it between 6.1 and 6 - the Changelog has items for
     8I've just cloned current branches of qtwebengine and its chromium stuff. In 118-based chromium it looks as if they took it between 6.0 and 6.1 - the Changelog has items for
    99{{{
    1010Entries are sorted chronologically from oldest to youngest within each release,
    … …  
    1212
    1313version <next>:
     14- libaribcaption decoder
     15- Playdate video decoder and demuxer
     16- Extend VAAPI support for libva-win32 on Windows
     17[...]
     18
     19- Bitstream filter for converting VVC from MP4 to Annex B
     20
     21version 6.0:
    1422- Radiance HDR image support
    1523- ddagrab (Desktop Duplication) video capture filter
    1624- ffmpeg -shortest_buf_duration option
    1725- ffmpeg now requires threading to be built
    18 - ffmpeg now runs every muxer in a separate thread
    19 - Add new mode to cropdetect filter to detect crop-area based on motion vectors and edges
    20 [...]
    21 - media100 to mjpegb bsf
    22 - ffmpeg CLI new option: -fix_sub_duration_heartbeat
    23 
    24 
    25 version 5.1:
    26 - add ipfs/ipns gateway support
    27 - dialogue enhance audio filter
    28 - dropped obsolete XvMC hwaccel
    2926[...]
    3027}}}
    3128So it seems to be reasonably current. Using the shipped ffmpeg in qtwebengine-6.7 probably won't cause any more vulnerabilities than the backlog of chromium issues still to be backported.
     29
     30Edit: I thought 6.6 was using 112-based, it is actually 118-based, details amended.