Bug 2215700 - Intel MediaSDK discontinued upstream
Summary: Intel MediaSDK discontinued upstream
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: intel-mediasdk
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Dominik 'Rathann' Mierzejewski
QA Contact: Fedora Extras Quality Assurance
URL: https://github.com/Intel-Media-SDK/Me...
Whiteboard:
Depends On: 2215745
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-17 15:08 UTC by Dominik 'Rathann' Mierzejewski
Modified: 2024-02-02 14:29 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-02-02 14:29:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
RPM Fusion 6711 0 P1 RESOLVED Switch to oneVPL (Intel MediaSDK is EOL) 2024-04-09 22:31:16 UTC

Description Dominik 'Rathann' Mierzejewski 2023-06-17 15:08:34 UTC
Intel MediaSDK is no longer developed by Intel. The remaining consumers in Fedora and RPM Fusion are:

Fedora:
opencv

RPM Fusion:
compat-ffmpeg4
HandBrake
vlc

Reproducible: Always

Comment 1 Yaakov Selkowitz 2024-01-10 16:51:51 UTC
opencv has since switched to oneVPL.

VLC has an open MR upstream: https://code.videolan.org/videolan/vlc/-/merge_requests/3843

However, note that oneVPL itself (which iiuc is just a dispatcher) still uses intel-mediasdk, so it would seem to need to remain for a while.

FWIW https://github.com/intel/libvpl/tree/master/examples/tutorials/01_transition is enlightening on this subject.

Comment 2 Yaakov Selkowitz 2024-01-10 17:22:28 UTC
vlc-3.0.20-7 will switch from direct use of libmfx to oneVPL.  That will leave oneVPL as the only direct consumer of intel-mediasdk in Fedora, which seems to be the desired state.

Comment 3 Dominik 'Rathann' Mierzejewski 2024-02-02 14:29:14 UTC
oneVPL only Recommends: intel-mediasdk, so it's not even a hard dependency. Anyway, I think we're done migrating, so closing.


Note You need to log in before you can comment on or make changes to this bug.