QtCS2024 FFmpeg in Qt Multimedia: Difference between revisions
m (Adding notes from the presentation) |
(→Notes) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Session Summary== | ==Session Summary== | ||
In this session, we will look at the core functionalities of Qt Multimedia, address the challenges of ensuring consistent behavior across various platforms, and discuss our strategic transition to FFmpeg as a cross-platform backend. This move from native platform backends to FFmpeg has implications for both Qt contributors and users. We encourage an open and constructive discussion on the direction we are taking. | [[File:FFmpeg in Qt Multimedia.pdf|thumb]] | ||
In this session, we will look at the core functionalities of Qt Multimedia, address the challenges of ensuring consistent behavior across various platforms, and discuss our strategic transition to FFmpeg as a cross-platform backend. This move from native platform backends to FFmpeg has implications for both Qt contributors and users. We encourage an open and constructive discussion on the direction we are taking. | |||
==Session Owners== | ==Session Owners== | ||
| Line 6: | Line 7: | ||
==Notes== | ==Notes== | ||
Questions and discussions: | |||
Latest revision as of 16:15, 17 September 2024
Session Summary
In this session, we will look at the core functionalities of Qt Multimedia, address the challenges of ensuring consistent behavior across various platforms, and discuss our strategic transition to FFmpeg as a cross-platform backend. This move from native platform backends to FFmpeg has implications for both Qt contributors and users. We encourage an open and constructive discussion on the direction we are taking.
Session Owners
Jøger Hansegård, Artem Dyomin, and Maycon Stamboroski
Notes
Questions and discussions:
What to do about native backends on 6.8.
- Suggestion: make them opt-in
- KDE point of view: android is causing the most pain. FFmpeg is painful to cross compile to android. For simple camera access the native backend is better. Think about simple use cases where codecs aren't needed
It is possible to build ffmpeg with a super minimal configuration to have it in a small size.
How about reduce the support for native backend to the minimal basic use cases? -> Seems to be an acceptable approach